1 This document summarizes new features and bugfixes in each stable release
2 of Tor. If you want to see more detailed descriptions of the changes in
3 each development snapshot, see the ChangeLog file.
5 Changes in version 0.3.0.11 - 2017-09-18
6 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
9 Most significantly, it includes a fix for TROVE-2017-008, a
10 security bug that affects hidden services running with the
11 SafeLogging option disabled. For more information, see
12 https://trac.torproject.org/projects/tor/ticket/23490
14 Note: now that Tor 0.3.1.x is stable and released, support for the
15 0.3.0.x series will end on 26 Jan 2018. For longer term support,
16 either upgrade to the most recent 0.3.1.x release, or downgrade to
17 0.2.9.x for long-term support.
19 o Minor features (code style, backport from 0.3.1.7):
20 - Add "Falls through" comments to our codebase, in order to silence
21 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
22 Stieger. Closes ticket 22446.
25 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
28 o Minor bugfixes (compilation, backport from 0.3.1.7):
29 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
30 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
32 o Minor bugfixes (controller, backport from 0.3.1.7):
33 - Do not crash when receiving a HSPOST command with an empty body.
34 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
35 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
36 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
38 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
39 - When setting the maximum number of connections allowed by the OS,
40 always allow some extra file descriptors for other files. Fixes
41 bug 22797; bugfix on 0.2.0.10-alpha.
43 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
44 - Remove a forgotten debugging message when an introduction point
45 successfully establishes a hidden service prop224 circuit with
47 - Change three other log_warn() for an introduction point to
48 protocol warnings, because they can be failure from the network
49 and are not relevant to the operator. Fixes bug 23078; bugfix on
50 0.3.0.1-alpha and 0.3.0.2-alpha.
53 Changes in version 0.3.0.10 - 2017-08-02
54 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
55 from the current Tor alpha series. OpenBSD users and TPROXY users
56 should upgrade; others are probably okay sticking with 0.3.0.9.
58 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
59 - Tor's repository now includes a Travis Continuous Integration (CI)
60 configuration file (.travis.yml). This is meant to help new
61 developers and contributors who fork Tor to a Github repository be
62 better able to test their changes, and understand what we expect
63 to pass. To use this new build feature, you must fork Tor to your
64 Github account, then go into the "Integrations" menu in the
65 repository settings for your fork and enable Travis, then push
66 your changes. Closes ticket 22636.
68 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
69 - Fix a typo that had prevented TPROXY-based transparent proxying
70 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
71 Patch from "d4fq0fQAgoJ".
73 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
74 - Avoid an assertion failure bug affecting our implementation of
75 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
76 handling of "0xfoo" differs from what we had expected. Fixes bug
77 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
79 o Minor features (backport from 0.3.1.5-alpha):
80 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
83 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
84 - Roll over monthly accounting at the configured hour and minute,
85 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
86 Found by Andrey Karpov with PVS-Studio.
88 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
89 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
90 bugfix on 0.2.8.1-alpha.
91 - Fix warnings when building with libscrypt and openssl scrypt
92 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
93 - When building with certain versions of the mingw C header files,
94 avoid float-conversion warnings when calling the C functions
95 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
98 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
99 - Backport a fix for an "unused variable" warning that appeared
100 in some versions of mingw. Fixes bug 22838; bugfix on
103 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
104 - Avoid Coverity build warnings related to our BUG() macro. By
105 default, Coverity treats BUG() as the Linux kernel does: an
106 instant abort(). We need to override that so our BUG() macro
107 doesn't prevent Coverity from analyzing functions that use it.
108 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
110 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
111 - When rejecting a router descriptor for running an obsolete version
112 of Tor without ntor support, warn about the obsolete tor version,
113 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
115 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
116 - Avoid a sandbox failure when trying to re-bind to a socket and
117 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
119 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
120 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
121 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
124 Changes in version 0.3.0.9 - 2017-06-29
125 Tor 0.3.0.9 fixes a path selection bug that would allow a client
126 to use a guard that was in the same network family as a chosen exit
127 relay. This is a security regression; all clients running earlier
128 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
131 This release also backports several other bugfixes from the 0.3.1.x
134 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
135 - When choosing which guard to use for a circuit, avoid the exit's
136 family along with the exit itself. Previously, the new guard
137 selection logic avoided the exit, but did not consider its family.
138 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
139 006 and CVE-2017-0377.
141 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
142 - Don't block bootstrapping when a primary bridge is offline and we
143 can't get its descriptor. Fixes bug 22325; fixes one case of bug
144 21969; bugfix on 0.3.0.3-alpha.
146 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
147 - When starting with an old consensus, do not add new entry guards
148 unless the consensus is "reasonably live" (under 1 day old). Fixes
149 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
151 o Minor features (geoip):
152 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
155 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
156 - Reject version numbers with non-numeric prefixes (such as +, -, or
157 whitespace). Disallowing whitespace prevents differential version
158 parsing between POSIX-based and Windows platforms. Fixes bug 21507
159 and part of 21508; bugfix on 0.0.8pre1.
161 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
162 - Permit the fchmod system call, to avoid crashing on startup when
163 starting with the seccomp2 sandbox and an unexpected set of
164 permissions on the data directory or its contents. Fixes bug
165 22516; bugfix on 0.2.5.4-alpha.
167 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
168 - Fix a memset() off the end of an array when packing cells. This
169 bug should be harmless in practice, since the corrupted bytes are
170 still in the same structure, and are always padding bytes,
171 ignored, or immediately overwritten, depending on compiler
172 behavior. Nevertheless, because the memset()'s purpose is to make
173 sure that any other cell-handling bugs can't expose bytes to the
174 network, we need to fix it. Fixes bug 22737; bugfix on
175 0.2.4.11-alpha. Fixes CID 1401591.
178 Changes in version 0.3.0.8 - 2017-06-08
179 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
180 remotely crash a hidden service with an assertion failure. Anyone
181 running a hidden service should upgrade to this version, or to some
182 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
184 Tor 0.3.0.8 also includes fixes for several key management bugs
185 that sometimes made relays unreliable, as well as several other
186 bugfixes described below.
188 o Major bugfixes (hidden service, relay, security, backport
190 - Fix a remotely triggerable assertion failure when a hidden service
191 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
192 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
193 - Fix a remotely triggerable assertion failure caused by receiving a
194 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
195 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
198 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
199 - When performing the v3 link handshake on a TLS connection, report
200 that we have the x509 certificate that we actually used on that
201 connection, even if we have changed certificates since that
202 connection was first opened. Previously, we would claim to have
203 used our most recent x509 link certificate, which would sometimes
204 make the link handshake fail. Fixes one case of bug 22460; bugfix
207 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
208 - Regenerate link and authentication certificates whenever the key
209 that signs them changes; also, regenerate link certificates
210 whenever the signed key changes. Previously, these processes were
211 only weakly coupled, and we relays could (for minutes to hours)
212 wind up with an inconsistent set of keys and certificates, which
213 other relays would not accept. Fixes two cases of bug 22460;
214 bugfix on 0.3.0.1-alpha.
215 - When sending an Ed25519 signing->link certificate in a CERTS cell,
216 send the certificate that matches the x509 certificate that we
217 used on the TLS connection. Previously, there was a race condition
218 if the TLS context rotated after we began the TLS handshake but
219 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
222 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
223 - Stop rejecting v3 hidden service descriptors because their size
224 did not match an old padding rule. Fixes bug 22447; bugfix on
227 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
228 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
229 December 2016 (of which ~126 were still functional) with a list of
230 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
231 2017. Resolves ticket 21564.
233 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
234 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
235 bug 22252; bugfix on 0.2.9.3-alpha.
237 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
238 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
239 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
241 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
242 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
243 months, and regenerate it when it is within one month of expiring.
244 Previously, we had generated this certificate at startup with a
245 ten-year lifetime, but that could lead to weird behavior when Tor
246 was started with a grossly inaccurate clock. Mitigates bug 22466;
247 mitigation on 0.3.0.1-alpha.
249 o Minor bugfixes (memory leak, directory authority, backport from
251 - When directory authorities reject a router descriptor due to
252 keypinning, free the router descriptor rather than leaking the
253 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
256 Changes in version 0.3.0.7 - 2017-05-15
257 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
258 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
259 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
260 clients are not affected.
262 o Major bugfixes (hidden service directory, security):
263 - Fix an assertion failure in the hidden service directory code, which
264 could be used by an attacker to remotely cause a Tor relay process to
265 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
266 should upgrade. This security issue is tracked as TROVE-2017-002.
267 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
270 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
273 o Minor features (future-proofing):
274 - Tor no longer refuses to download microdescriptors or descriptors
275 if they are listed as "published in the future". This change will
276 eventually allow us to stop listing meaningful "published" dates
277 in microdescriptor consensuses, and thereby allow us to reduce the
278 resources required to download consensus diffs by over 50%.
279 Implements part of ticket 21642; implements part of proposal 275.
281 o Minor bugfixes (Linux seccomp2 sandbox):
282 - The getpid() system call is now permitted under the Linux seccomp2
283 sandbox, to avoid crashing with versions of OpenSSL (and other
284 libraries) that attempt to learn the process's PID by using the
285 syscall rather than the VDSO code. Fixes bug 21943; bugfix
289 Changes in version 0.3.0.6 - 2017-04-26
290 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
292 With the 0.3.0 series, clients and relays now use Ed25519 keys to
293 authenticate their link connections to relays, rather than the old
294 RSA1024 keys that they used before. (Circuit crypto has been
295 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
296 the guard selection and replacement algorithm to behave more robustly
297 in the presence of unreliable networks, and to resist guard-
300 This series also includes numerous other small features and bugfixes,
301 along with more groundwork for the upcoming hidden-services revamp.
303 Per our stable release policy, we plan to support the Tor 0.3.0
304 release series for at least the next nine months, or for three months
305 after the first stable release of the 0.3.1 series: whichever is
306 longer. If you need a release with long-term support, we recommend
307 that you stay with the 0.2.9 series.
309 Below are the changes since 0.2.9.10. For a list of only the changes
310 since 0.3.0.5-rc, see the ChangeLog file.
312 o Major features (directory authority, security):
313 - The default for AuthDirPinKeys is now 1: directory authorities
314 will reject relays where the RSA identity key matches a previously
315 seen value, but the Ed25519 key has changed. Closes ticket 18319.
317 o Major features (guard selection algorithm):
318 - Tor's guard selection algorithm has been redesigned from the
319 ground up, to better support unreliable networks and restrictive
320 sets of entry nodes, and to better resist guard-capture attacks by
321 hostile local networks. Implements proposal 271; closes
324 o Major features (next-generation hidden services):
325 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
326 prop224 aka "Next Generation Hidden Services". Service and clients
327 don't use this functionality yet. Closes ticket 19043. Based on
328 initial code by Alec Heifetz.
329 - Relays now support the HSDir version 3 protocol, so that they can
330 can store and serve v3 descriptors. This is part of the next-
331 generation onion service work detailled in proposal 224. Closes
334 o Major features (protocol, ed25519 identity keys):
335 - Clients now support including Ed25519 identity keys in the EXTEND2
336 cells they generate. By default, this is controlled by a consensus
337 parameter, currently disabled. You can turn this feature on for
338 testing by setting ExtendByEd25519ID in your configuration. This
339 might make your traffic appear different than the traffic
340 generated by other users, however. Implements part of ticket
341 15056; part of proposal 220.
342 - Relays now understand requests to extend to other relays by their
343 Ed25519 identity keys. When an Ed25519 identity key is included in
344 an EXTEND2 cell, the relay will only extend the circuit if the
345 other relay can prove ownership of that identity. Implements part
346 of ticket 15056; part of proposal 220.
347 - Relays now use Ed25519 to prove their Ed25519 identities and to
348 one another, and to clients. This algorithm is faster and more
349 secure than the RSA-based handshake we've been doing until now.
350 Implements the second big part of proposal 220; Closes
353 o Major features (security):
354 - Change the algorithm used to decide DNS TTLs on client and server
355 side, to better resist DNS-based correlation attacks like the
356 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
357 Feamster. Now relays only return one of two possible DNS TTL
358 values, and clients are willing to believe DNS TTL values up to 3
359 hours long. Closes ticket 19769.
361 o Major bugfixes (client, onion service, also in 0.2.9.9):
362 - Fix a client-side onion service reachability bug, where multiple
363 socks requests to an onion service (or a single slow request)
364 could cause us to mistakenly mark some of the service's
365 introduction points as failed, and we cache that failure so
366 eventually we run out and can't reach the service. Also resolves a
367 mysterious "Remote server sent bogus reason code 65021" log
368 warning. The bug was introduced in ticket 17218, where we tried to
369 remember the circuit end reason as a uint16_t, which mangled
370 negative values. Partially fixes bug 21056 and fixes bug 20307;
371 bugfix on 0.2.8.1-alpha.
373 o Major bugfixes (crash, directory connections):
374 - Fix a rare crash when sending a begin cell on a circuit whose
375 linked directory connection had already been closed. Fixes bug
376 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
378 o Major bugfixes (directory authority):
379 - During voting, when marking a relay as a probable sybil, do not
380 clear its BadExit flag: sybils can still be bad in other ways
381 too. (We still clear the other flags.) Fixes bug 21108; bugfix
384 o Major bugfixes (DNS):
385 - Fix a bug that prevented exit nodes from caching DNS records for
386 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
388 o Major bugfixes (IPv6 Exits):
389 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
390 any IPv6 addresses. Instead, only reject a port over IPv6 if the
391 exit policy rejects that port on more than an IPv6 /16 of
392 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
393 which rejected a relay's own IPv6 address by default. Fixes bug
394 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
396 o Major bugfixes (parsing):
397 - Fix an integer underflow bug when comparing malformed Tor
398 versions. This bug could crash Tor when built with
399 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
400 0.2.9.8, which were built with -ftrapv by default. In other cases
401 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
402 on 0.0.8pre1. Found by OSS-Fuzz.
403 - When parsing a malformed content-length field from an HTTP
404 message, do not read off the end of the buffer. This bug was a
405 potential remote denial-of-service attack against Tor clients and
406 relays. A workaround was released in October 2016, to prevent this
407 bug from crashing Tor. This is a fix for the underlying issue,
408 which should no longer matter (if you applied the earlier patch).
409 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
410 using AFL (http://lcamtuf.coredump.cx/afl/).
412 o Major bugfixes (scheduler):
413 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
414 caused the channel scheduler to behave more or less randomly,
415 rather than preferring channels with higher-priority circuits.
416 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
418 o Major bugfixes (security, also in 0.2.9.9):
419 - Downgrade the "-ftrapv" option from "always on" to "only on when
420 --enable-expensive-hardening is provided." This hardening option,
421 like others, can turn survivable bugs into crashes--and having it
422 on by default made a (relatively harmless) integer overflow bug
423 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
424 bugfix on 0.2.9.1-alpha.
426 o Minor feature (client):
427 - Enable IPv6 traffic on the SocksPort by default. To disable this,
428 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
430 o Minor feature (fallback scripts):
431 - Add a check_existing mode to updateFallbackDirs.py, which checks
432 if fallbacks in the hard-coded list are working. Closes ticket
433 20174. Patch by haxxpop.
435 o Minor feature (protocol versioning):
436 - Add new protocol version for proposal 224. HSIntro now advertises
437 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
439 o Minor features (ciphersuite selection):
440 - Allow relays to accept a wider range of ciphersuites, including
441 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
442 - Clients now advertise a list of ciphersuites closer to the ones
443 preferred by Firefox. Closes part of ticket 15426.
445 o Minor features (controller):
446 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
447 shared-random values to the controller. Closes ticket 19925.
448 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
449 rather than "unrecognized." Closes ticket 20389; patch from
452 o Minor features (controller, configuration):
453 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
454 and so on, now comes with a __*Port variant that will not be saved
455 to the torrc file by the controller's SAVECONF command. This
456 change allows TorBrowser to set up a single-use domain socket for
457 each time it launches Tor. Closes ticket 20956.
458 - The GETCONF command can now query options that may only be
459 meaningful in context-sensitive lists. This allows the controller
460 to query the mixed SocksPort/__SocksPort style options introduced
461 in feature 20956. Implements ticket 21300.
463 o Minor features (diagnostic, directory client):
464 - Warn when we find an unexpected inconsistency in directory
465 download status objects. Prevents some negative consequences of
468 o Minor features (directory authorities):
469 - Directory authorities now reject descriptors that claim to be
470 malformed versions of Tor. Helps prevent exploitation of
472 - Reject version numbers with components that exceed INT32_MAX.
473 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
474 Fixes bug 21450; bugfix on 0.0.8pre1.
476 o Minor features (directory authority):
477 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
478 default) to control whether authorities should try to probe relays
479 by their Ed25519 link keys. This option will go away in a few
480 releases--unless we encounter major trouble in our ed25519 link
481 protocol rollout, in which case it will serve as a safety option.
483 o Minor features (directory cache):
484 - Relays and bridges will now refuse to serve the consensus they
485 have if they know it is too old for a client to use. Closes
488 o Minor features (ed25519 link handshake):
489 - Advertise support for the ed25519 link handshake using the
490 subprotocol-versions mechanism, so that clients can tell which
491 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
493 o Minor features (entry guards):
494 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
495 break regression tests.
496 - Require UseEntryGuards when UseBridges is set, in order to make
497 sure bridges aren't bypassed. Resolves ticket 20502.
499 o Minor features (fallback directories):
500 - Allow 3 fallback relays per operator, which is safe now that we
501 are choosing 200 fallback relays. Closes ticket 20912.
502 - Annotate updateFallbackDirs.py with the bandwidth and consensus
503 weight for each candidate fallback. Closes ticket 20878.
504 - Display the relay fingerprint when downloading consensuses from
505 fallbacks. Closes ticket 20908.
506 - Exclude relays affected by bug 20499 from the fallback list.
507 Exclude relays from the fallback list if they are running versions
508 known to be affected by bug 20499, or if in our tests they deliver
509 a stale consensus (i.e. one that expired more than 24 hours ago).
511 - Make it easier to change the output sort order of fallbacks.
513 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
515 - Require fallback directories to have the same address and port for
516 7 days (now that we have enough relays with this stability).
517 Relays whose OnionOO stability timer is reset on restart by bug
518 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
519 this issue. Closes ticket 20880; maintains short-term fix
521 - Require fallbacks to have flags for 90% of the time (weighted
522 decaying average), rather than 95%. This allows at least 73% of
523 clients to bootstrap in the first 5 seconds without contacting an
524 authority. Part of ticket 18828.
525 - Select 200 fallback directories for each release. Closes
528 o Minor features (fingerprinting resistence, authentication):
529 - Extend the length of RSA keys used for TLS link authentication to
530 2048 bits. (These weren't used for forward secrecy; for forward
531 secrecy, we used P256.) Closes ticket 13752.
533 o Minor features (geoip):
534 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
537 o Minor features (geoip, also in 0.2.9.9):
538 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
541 o Minor features (infrastructure):
542 - Implement smartlist_add_strdup() function. Replaces the use of
543 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
545 o Minor features (linting):
546 - Enhance the changes file linter to warn on Tor versions that are
547 prefixed with "tor-". Closes ticket 21096.
549 o Minor features (logging):
550 - In several places, describe unset ed25519 keys as "<unset>",
551 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
553 o Minor features (portability, compilation):
554 - Autoconf now checks to determine if OpenSSL structures are opaque,
555 instead of explicitly checking for OpenSSL version numbers. Part
557 - Support building with recent LibreSSL code that uses opaque
558 structures. Closes ticket 21359.
560 o Minor features (relay):
561 - We now allow separation of exit and relay traffic to different
562 source IP addresses, using the OutboundBindAddressExit and
563 OutboundBindAddressOR options respectively. Closes ticket 17975.
564 Written by Michael Sonntag.
566 o Minor features (reliability, crash):
567 - Try better to detect problems in buffers where they might grow (or
568 think they have grown) over 2 GB in size. Diagnostic for
571 o Minor features (testing):
572 - During 'make test-network-all', if tor logs any warnings, ask
573 chutney to output them. Requires a recent version of chutney with
574 the 21572 patch. Implements 21570.
576 o Minor bugfix (control protocol):
577 - The reply to a "GETINFO config/names" request via the control
578 protocol now spells the type "Dependent" correctly. This is a
579 breaking change in the control protocol. (The field seems to be
580 ignored by the most common known controllers.) Fixes bug 18146;
581 bugfix on 0.1.1.4-alpha.
582 - The GETINFO extra-info/digest/<digest> command was broken because
583 of a wrong base16 decode return value check, introduced when
584 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
586 o Minor bugfix (logging):
587 - Don't recommend the use of Tor2web in non-anonymous mode.
588 Recommending Tor2web is a bad idea because the client loses all
589 anonymity. Tor2web should only be used in specific cases by users
590 who *know* and understand the issues. Fixes bug 21294; bugfix
593 o Minor bugfixes (bug resilience):
594 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
595 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
596 Hans Jerry Illikainen.
598 o Minor bugfixes (build):
599 - Replace obsolete Autoconf macros with their modern equivalent and
600 prevent similar issues in the future. Fixes bug 20990; bugfix
603 o Minor bugfixes (certificate expiration time):
604 - Avoid using link certificates that don't become valid till some
605 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
607 o Minor bugfixes (client):
608 - Always recover from failures in extend_info_from_node(), in an
609 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
610 bugfix on 0.2.3.1-alpha.
611 - When clients that use bridges start up with a cached consensus on
612 disk, they were ignoring it and downloading a new one. Now they
613 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
615 o Minor bugfixes (code correctness):
616 - Repair a couple of (unreachable or harmless) cases of the risky
617 comparison-by-subtraction pattern that caused bug 21278.
619 o Minor bugfixes (config):
620 - Don't assert on startup when trying to get the options list and
621 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
622 options so of course they aren't ready yet. Fixes bug 21062;
623 bugfix on 0.2.9.3-alpha.
625 o Minor bugfixes (configuration):
626 - Accept non-space whitespace characters after the severity level in
627 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
628 - Support "TByte" and "TBytes" units in options given in bytes.
629 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
630 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
632 o Minor bugfixes (configure, autoconf):
633 - Rename the configure option --enable-expensive-hardening to
634 --enable-fragile-hardening. Expensive hardening makes the tor
635 daemon abort when some kinds of issues are detected. Thus, it
636 makes tor more at risk of remote crashes but safer against RCE or
637 heartbleed bug category. We now try to explain this issue in a
638 message from the configure script. Fixes bug 21290; bugfix
641 o Minor bugfixes (consensus weight):
642 - Add new consensus method that initializes bw weights to 1 instead
643 of 0. This prevents a zero weight from making it all the way to
644 the end (happens in small testing networks) and causing an error.
645 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
647 o Minor bugfixes (crash prevention):
648 - Fix an (currently untriggerable, but potentially dangerous) crash
649 bug when base32-encoding inputs whose sizes are not a multiple of
650 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
652 o Minor bugfixes (dead code):
653 - Remove a redundant check for PidFile changes at runtime in
654 options_transition_allowed(): this check is already performed
655 regardless of whether the sandbox is active. Fixes bug 21123;
656 bugfix on 0.2.5.4-alpha.
658 o Minor bugfixes (descriptors):
659 - Correctly recognise downloaded full descriptors as valid, even
660 when using microdescriptors as circuits. This affects clients with
661 FetchUselessDescriptors set, and may affect directory authorities.
662 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
664 o Minor bugfixes (directory mirrors):
665 - Allow relays to use directory mirrors without a DirPort: these
666 relays need to be contacted over their ORPorts using a begindir
667 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
668 - Clarify the message logged when a remote relay is unexpectedly
669 missing an ORPort or DirPort: users were confusing this with a
670 local port. Fixes another case of bug 20711; bugfix
673 o Minor bugfixes (directory system):
674 - Bridges and relays now use microdescriptors (like clients do)
675 rather than old-style router descriptors. Now bridges will blend
676 in with clients in terms of the circuits they build. Fixes bug
677 6769; bugfix on 0.2.3.2-alpha.
678 - Download all consensus flavors, descriptors, and authority
679 certificates when FetchUselessDescriptors is set, regardless of
680 whether tor is a directory cache or not. Fixes bug 20667; bugfix
681 on all recent tor versions.
683 o Minor bugfixes (documentation):
684 - Update the tor manual page to document every option that can not
685 be changed while tor is running. Fixes bug 21122.
687 o Minor bugfixes (ed25519 certificates):
688 - Correctly interpret ed25519 certificates that would expire some
689 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
691 o Minor bugfixes (fallback directories):
692 - Avoid checking fallback candidates' DirPorts if they are down in
693 OnionOO. When a relay operator has multiple relays, this
694 prioritizes relays that are up over relays that are down. Fixes
695 bug 20926; bugfix on 0.2.8.3-alpha.
696 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
697 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
698 - Stop failing when a relay has no uptime data in
699 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
701 o Minor bugfixes (hidden service):
702 - Clean up the code for expiring intro points with no associated
703 circuits. It was causing, rarely, a service with some expiring
704 introduction points to not open enough additional introduction
705 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
706 - Resolve two possible underflows which could lead to creating and
707 closing a lot of introduction point circuits in a non-stop loop.
708 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
709 - Stop setting the torrc option HiddenServiceStatistics to "0" just
710 because we're not a bridge or relay. Instead, we preserve whatever
711 value the user set (or didn't set). Fixes bug 21150; bugfix
714 o Minor bugfixes (hidden services):
715 - Make hidden services check for failed intro point connections,
716 even when they have exceeded their intro point creation limit.
717 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
718 - Make hidden services with 8 to 10 introduction points check for
719 failed circuits immediately after startup. Previously, they would
720 wait for 5 minutes before performing their first checks. Fixes bug
721 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
722 - Stop ignoring misconfigured hidden services. Instead, refuse to
723 start tor until the misconfigurations have been corrected. Fixes
724 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
727 o Minor bugfixes (IPv6):
728 - Make IPv6-using clients try harder to find an IPv6 directory
729 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
730 - When IPv6 addresses have not been downloaded yet (microdesc
731 consensus documents don't list relay IPv6 addresses), use hard-
732 coded addresses for authorities, fallbacks, and configured
733 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
734 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
736 o Minor bugfixes (memory leak at exit):
737 - Fix a small harmless memory leak at exit of the previously unused
738 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
741 o Minor bugfixes (onion services):
742 - Allow the number of introduction points to be as low as 0, rather
743 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
745 o Minor bugfixes (portability):
746 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
747 It is supported by OpenBSD itself, and also by most OpenBSD
748 variants (such as Bitrig). Fixes bug 20980; bugfix
751 o Minor bugfixes (portability, also in 0.2.9.9):
752 - Avoid crashing when Tor is built using headers that contain
753 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
754 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
756 - Fix Libevent detection on platforms without Libevent 1 headers
757 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
759 o Minor bugfixes (relay):
760 - Avoid a double-marked-circuit warning that could happen when we
761 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
763 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
764 initializing the keys would reset the DataDirectory to 0700
765 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
766 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
768 o Minor bugfixes (testing):
769 - Fix Raspbian build issues related to missing socket errno in
770 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch by "hein".
771 - Remove undefined behavior from the backtrace generator by removing
772 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
773 - Use bash in src/test/test-network.sh. This ensures we reliably
774 call chutney's newer tools/test-network.sh when available. Fixes
775 bug 21562; bugfix on 0.2.9.1-alpha.
777 o Minor bugfixes (tor-resolve):
778 - The tor-resolve command line tool now rejects hostnames over 255
779 characters in length. Previously, it would silently truncate them,
780 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
781 Patch by "junglefowl".
783 o Minor bugfixes (unit tests):
784 - Allow the unit tests to pass even when DNS lookups of bogus
785 addresses do not fail as expected. Fixes bug 20862 and 20863;
786 bugfix on unit tests introduced in 0.2.8.1-alpha
787 through 0.2.9.4-alpha.
789 o Minor bugfixes (util):
790 - When finishing writing a file to disk, if we were about to replace
791 the file with the temporary file created before and we fail to
792 replace it, remove the temporary file so it doesn't stay on disk.
793 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
795 o Minor bugfixes (Windows services):
796 - Be sure to initialize the monotonic time subsystem before using
797 it, even when running as an NT service. Fixes bug 21356; bugfix
800 o Minor bugfixes (Windows):
801 - Check for getpagesize before using it to mmap files. This fixes
802 compilation in some MinGW environments. Fixes bug 20530; bugfix on
803 0.1.2.1-alpha. Reported by "ice".
805 o Code simplification and refactoring:
806 - Abolish all global guard context in entrynodes.c; replace with new
807 guard_selection_t structure as preparation for proposal 271.
809 - Extract magic numbers in circuituse.c into defined variables.
810 - Introduce rend_service_is_ephemeral() that tells if given onion
811 service is ephemeral. Replace unclear NULL-checkings for service
812 directory with this function. Closes ticket 20526.
813 - Refactor circuit_is_available_for_use to remove unnecessary check.
814 - Refactor circuit_predict_and_launch_new for readability and
815 testability. Closes ticket 18873.
816 - Refactor code to manipulate global_origin_circuit_list into
817 separate functions. Closes ticket 20921.
818 - Refactor large if statement in purpose_needs_anonymity to use
819 switch statement instead. Closes part of ticket 20077.
820 - Refactor the hashing API to return negative values for errors, as
821 is done as throughout the codebase. Closes ticket 20717.
822 - Remove data structures that were used to index or_connection
823 objects by their RSA identity digests. These structures are fully
824 redundant with the similar structures used in the
826 - Remove duplicate code in the channel_write_*cell() functions.
827 Closes ticket 13827; patch from Pingl.
828 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
829 use only purpose_needs_anonymity. Closes part of ticket 20077.
830 - The code to generate and parse EXTEND and EXTEND2 cells has been
831 replaced with code automatically generated by the
834 o Documentation (formatting):
835 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
836 blocks were incorrectly appearing. Closes ticket 20885.
838 o Documentation (man page):
839 - Clarify many options in tor.1 and add some min/max values for
840 HiddenService options. Closes ticket 21058.
843 - Change '1' to 'weight_scale' in consensus bw weights calculation
844 comments, as that is reality. Closes ticket 20273. Patch
846 - Clarify that when ClientRejectInternalAddresses is enabled (which
847 is the default), multicast DNS hostnames for machines on the local
848 network (of the form *.local) are also rejected. Closes
850 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
851 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix on 0.2.5.6-alpha.
852 - Include the "TBits" unit in Tor's man page. Fixes part of bug
853 20622; bugfix on 0.2.5.1-alpha.
854 - Small fixes to the fuzzing documentation. Closes ticket 21472.
855 - Stop the man page from incorrectly stating that HiddenServiceDir
856 must already exist. Fixes 20486.
857 - Update the description of the directory server options in the
858 manual page, to clarify that a relay no longer needs to set
859 DirPort in order to be a directory cache. Closes ticket 21720.
862 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
863 limit for relays running on a single IP applies to authority IP
864 addresses as well as to non-authority IP addresses. Closes
866 - The UseDirectoryGuards torrc option no longer exists: all users
867 that use entry guards will also use directory guards. Related to
868 proposal 271; implements part of ticket 20831.
871 - Add tests for networkstatus_compute_bw_weights_v10.
872 - Add unit tests circuit_predict_and_launch_new.
873 - Extract dummy_origin_circuit_new so it can be used by other
875 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
876 from "overcaffeinated".
877 - Perform the coding style checks when running the tests and fail
878 when coding style violations are found. Closes ticket 5500.
881 Changes in version 0.2.9.10 - 2017-03-01
882 Tor 0.2.9.10 backports a security fix from later Tor release. It also
883 includes fixes for some major issues affecting directory authorities,
884 LibreSSL compatibility, and IPv6 correctness.
886 The Tor 0.2.9.x release series is now marked as a long-term-support
887 series. We intend to backport security fixes to 0.2.9.x until at
888 least January of 2020.
890 o Major bugfixes (directory authority, 0.3.0.3-alpha):
891 - During voting, when marking a relay as a probable sybil, do not
892 clear its BadExit flag: sybils can still be bad in other ways
893 too. (We still clear the other flags.) Fixes bug 21108; bugfix
896 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
897 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
898 any IPv6 addresses. Instead, only reject a port over IPv6 if the
899 exit policy rejects that port on more than an IPv6 /16 of
900 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
901 which rejected a relay's own IPv6 address by default. Fixes bug
902 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
904 o Major bugfixes (parsing, also in 0.3.0.4-rc):
905 - Fix an integer underflow bug when comparing malformed Tor
906 versions. This bug could crash Tor when built with
907 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
908 0.2.9.8, which were built with -ftrapv by default. In other cases
909 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
910 on 0.0.8pre1. Found by OSS-Fuzz.
912 o Minor features (directory authorities, also in 0.3.0.4-rc):
913 - Directory authorities now reject descriptors that claim to be
914 malformed versions of Tor. Helps prevent exploitation of
916 - Reject version numbers with components that exceed INT32_MAX.
917 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
918 Fixes bug 21450; bugfix on 0.0.8pre1.
920 o Minor features (geoip):
921 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
924 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
925 - Autoconf now checks to determine if OpenSSL structures are opaque,
926 instead of explicitly checking for OpenSSL version numbers. Part
928 - Support building with recent LibreSSL code that uses opaque
929 structures. Closes ticket 21359.
931 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
932 - Repair a couple of (unreachable or harmless) cases of the risky
933 comparison-by-subtraction pattern that caused bug 21278.
935 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
936 - The tor-resolve command line tool now rejects hostnames over 255
937 characters in length. Previously, it would silently truncate them,
938 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
939 Patch by "junglefowl".
942 Changes in version 0.2.9.9 - 2017-01-23
943 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
944 cause relays and clients to crash, even if they were not built with
945 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
946 versions, and also affects 0.3.0.1-alpha: all relays running an affected
947 version should upgrade.
949 This release also resolves a client-side onion service reachability
950 bug, and resolves a pair of small portability issues.
952 o Major bugfixes (security):
953 - Downgrade the "-ftrapv" option from "always on" to "only on when
954 --enable-expensive-hardening is provided." This hardening option,
955 like others, can turn survivable bugs into crashes -- and having
956 it on by default made a (relatively harmless) integer overflow bug
957 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
958 bugfix on 0.2.9.1-alpha.
960 o Major bugfixes (client, onion service):
961 - Fix a client-side onion service reachability bug, where multiple
962 socks requests to an onion service (or a single slow request)
963 could cause us to mistakenly mark some of the service's
964 introduction points as failed, and we cache that failure so
965 eventually we run out and can't reach the service. Also resolves a
966 mysterious "Remote server sent bogus reason code 65021" log
967 warning. The bug was introduced in ticket 17218, where we tried to
968 remember the circuit end reason as a uint16_t, which mangled
969 negative values. Partially fixes bug 21056 and fixes bug 20307;
970 bugfix on 0.2.8.1-alpha.
972 o Minor features (geoip):
973 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
976 o Minor bugfixes (portability):
977 - Avoid crashing when Tor is built using headers that contain
978 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
979 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
981 - Fix Libevent detection on platforms without Libevent 1 headers
982 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
985 Changes in version 0.2.8.12 - 2016-12-19
986 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
987 below) where Tor clients could crash when attempting to visit a
988 hostile hidden service. Clients are recommended to upgrade as packages
989 become available for their systems.
991 It also includes an updated list of fallback directories, backported
994 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
995 backported to 0.2.8 in the future.
997 o Major bugfixes (parsing, security, backported from 0.2.9.8):
998 - Fix a bug in parsing that could cause clients to read a single
999 byte past the end of an allocated region. This bug could be used
1000 to cause hardened clients (built with --enable-expensive-hardening)
1001 to crash if they tried to visit a hostile hidden service. Non-
1002 hardened clients are only affected depending on the details of
1003 their platform's memory allocator. Fixes bug 21018; bugfix on
1004 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
1005 2016-12-002 and as CVE-2016-1254.
1007 o Minor features (fallback directory list, backported from 0.2.9.8):
1008 - Replace the 81 remaining fallbacks of the 100 originally
1009 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
1010 fallbacks (123 new, 54 existing, 27 removed) generated in December
1011 2016. Resolves ticket 20170.
1013 o Minor features (geoip, backported from 0.2.9.7-rc):
1014 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
1018 Changes in version 0.2.9.8 - 2016-12-19
1019 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
1021 The Tor 0.2.9 series makes mandatory a number of security features
1022 that were formerly optional. It includes support for a new shared-
1023 randomness protocol that will form the basis for next generation
1024 hidden services, includes a single-hop hidden service mode for
1025 optimizing .onion services that don't actually want to be hidden,
1026 tries harder not to overload the directory authorities with excessive
1027 downloads, and supports a better protocol versioning scheme for
1028 improved compatibility with other implementations of the Tor protocol.
1030 And of course, there are numerous other bugfixes and improvements.
1032 This release also includes a fix for a medium-severity issue (bug
1033 21018 below) where Tor clients could crash when attempting to visit a
1034 hostile hidden service. Clients are recommended to upgrade as packages
1035 become available for their systems.
1037 Below are listed the changes since Tor 0.2.8.11. For a list of
1038 changes since 0.2.9.7-rc, see the ChangeLog file.
1040 o New system requirements:
1041 - When building with OpenSSL, Tor now requires version 1.0.1 or
1042 later. OpenSSL 1.0.0 and earlier are no longer supported by the
1043 OpenSSL team, and should not be used. Closes ticket 20303.
1044 - Tor now requires Libevent version 2.0.10-stable or later. Older
1045 versions of Libevent have less efficient backends for several
1046 platforms, and lack the DNS code that we use for our server-side
1047 DNS support. This implements ticket 19554.
1048 - Tor now requires zlib version 1.2 or later, for security,
1049 efficiency, and (eventually) gzip support. (Back when we started,
1050 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
1051 released in 2003. We recommend the latest version.)
1053 o Deprecated features:
1054 - A number of DNS-cache-related sub-options for client ports are now
1055 deprecated for security reasons, and may be removed in a future
1056 version of Tor. (We believe that client-side DNS caching is a bad
1057 idea for anonymity, and you should not turn it on.) The options
1058 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
1059 UseIPv4Cache, and UseIPv6Cache.
1060 - A number of options are deprecated for security reasons, and may
1061 be removed in a future version of Tor. The options are:
1062 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
1063 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
1064 CloseHSClientCircuitsImmediatelyOnTimeout,
1065 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
1066 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
1067 UseNTorHandshake, and WarnUnsafeSocks.
1068 - The *ListenAddress options are now deprecated as unnecessary: the
1069 corresponding *Port options should be used instead. These options
1070 may someday be removed. The affected options are:
1071 ControlListenAddress, DNSListenAddress, DirListenAddress,
1072 NATDListenAddress, ORListenAddress, SocksListenAddress,
1073 and TransListenAddress.
1075 o Major bugfixes (parsing, security, new since 0.2.9.7-rc):
1076 - Fix a bug in parsing that could cause clients to read a single
1077 byte past the end of an allocated region. This bug could be used
1078 to cause hardened clients (built with --enable-expensive-hardening)
1079 to crash if they tried to visit a hostile hidden service. Non-
1080 hardened clients are only affected depending on the details of
1081 their platform's memory allocator. Fixes bug 21018; bugfix on
1082 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
1083 2016-12-002 and as CVE-2016-1254.
1085 o Major features (build, hardening):
1086 - Tor now builds with -ftrapv by default on compilers that support
1087 it. This option detects signed integer overflow (which C forbids),
1088 and turns it into a hard-failure. We do not apply this option to
1089 code that needs to run in constant time to avoid side-channels;
1090 instead, we use -fwrapv in that code. Closes ticket 17983.
1091 - When --enable-expensive-hardening is selected, stop applying the
1092 clang/gcc sanitizers to code that needs to run in constant time.
1093 Although we are aware of no introduced side-channels, we are not
1094 able to prove that there are none. Related to ticket 17983.
1096 o Major features (circuit building, security):
1097 - Authorities, relays, and clients now require ntor keys in all
1098 descriptors, for all hops (except for rare hidden service protocol
1099 cases), for all circuits, and for all other roles. Part of
1101 - Authorities, relays, and clients only use ntor, except for
1102 rare cases in the hidden service protocol. Part of ticket 19163.
1104 o Major features (compilation):
1105 - Our big list of extra GCC warnings is now enabled by default when
1106 building with GCC (or with anything like Clang that claims to be
1107 GCC-compatible). To make all warnings into fatal compilation
1108 errors, pass --enable-fatal-warnings to configure. Closes
1110 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
1111 turn on C and POSIX extensions. (Previously, we attempted to do
1112 this on an ad hoc basis.) Closes ticket 19139.
1114 o Major features (directory authorities, hidden services):
1115 - Directory authorities can now perform the shared randomness
1116 protocol specified by proposal 250. Using this protocol, directory
1117 authorities generate a global fresh random value every day. In the
1118 future, this value will be used by hidden services to select
1119 HSDirs. This release implements the directory authority feature;
1120 the hidden service side will be implemented in the future as part
1121 of proposal 224. Resolves ticket 16943; implements proposal 250.
1123 o Major features (downloading, random exponential backoff):
1124 - When we fail to download an object from a directory service, wait
1125 for an (exponentially increasing) randomized amount of time before
1126 retrying, rather than a fixed interval as we did before. This
1127 prevents a group of Tor instances from becoming too synchronized,
1128 or a single Tor instance from becoming too predictable, in its
1129 download schedule. Closes ticket 15942.
1131 o Major features (resource management):
1132 - Tor can now notice it is about to run out of sockets, and
1133 preemptively close connections of lower priority. (This feature is
1134 off by default for now, since the current prioritizing method is
1135 yet not mature enough. You can enable it by setting
1136 "DisableOOSCheck 0", but watch out: it might close some sockets
1137 you would rather have it keep.) Closes ticket 18640.
1139 o Major features (single-hop "hidden" services):
1140 - Add experimental HiddenServiceSingleHopMode and
1141 HiddenServiceNonAnonymousMode options. When both are set to 1,
1142 every hidden service on that Tor instance becomes a non-anonymous
1143 Single Onion Service. Single Onions make one-hop (direct)
1144 connections to their introduction and rendezvous points. One-hop
1145 circuits make Single Onion servers easily locatable, but clients
1146 remain location-anonymous. This is compatible with the existing
1147 hidden service implementation, and works on the current Tor
1148 network without any changes to older relays or clients. Implements
1149 proposal 260, completes ticket 17178. Patch by teor and asn.
1151 o Major features (subprotocol versions):
1152 - Tor directory authorities now vote on a set of recommended
1153 "subprotocol versions", and on a set of required subprotocol
1154 versions. Clients and relays that lack support for a _required_
1155 subprotocol version will not start; those that lack support for a
1156 _recommended_ subprotocol version will warn the user to upgrade.
1157 This change allows compatible implementations of the Tor protocol(s)
1158 to exist without pretending to be 100% bug-compatible with
1159 particular releases of Tor itself. Closes ticket 19958; implements
1160 part of proposal 264.
1162 o Major bugfixes (circuit building):
1163 - Hidden service client-to-intro-point and service-to-rendezvous-
1164 point circuits use the TAP key supplied by the protocol, to avoid
1165 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
1167 o Major bugfixes (download scheduling):
1168 - Avoid resetting download status for consensuses hourly, since we
1169 already have another, smarter retry mechanism. Fixes bug 8625;
1170 bugfix on 0.2.0.9-alpha.
1171 - If a consensus expires while we are waiting for certificates to
1172 download, stop waiting for certificates.
1173 - If we stop waiting for certificates less than a minute after we
1174 started downloading them, do not consider the certificate download
1175 failure a separate failure. Fixes bug 20533; bugfix
1177 - When using exponential backoff in test networks, use a lower
1178 exponent, so the delays do not vary as much. This helps test
1179 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
1181 o Major bugfixes (exit policies):
1182 - Avoid disclosing exit outbound bind addresses, configured port
1183 bind addresses, and local interface addresses in relay descriptors
1184 by default under ExitPolicyRejectPrivate. Instead, only reject
1185 these (otherwise unlisted) addresses if
1186 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
1187 0.2.7.2-alpha. Patch by teor.
1189 o Major bugfixes (hidden services):
1190 - Allow Tor clients with appropriate controllers to work with
1191 FetchHidServDescriptors set to 0. Previously, this option also
1192 disabled descriptor cache lookup, thus breaking hidden services
1193 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
1194 - Clients now require hidden services to include the TAP keys for
1195 their intro points in the hidden service descriptor. This prevents
1196 an inadvertent upgrade to ntor, which a malicious hidden service
1197 could use to distinguish clients by consensus version. Fixes bug
1198 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
1200 o Major bugfixes (relay, resolver, logging):
1201 - For relays that don't know their own address, avoid attempting a
1202 local hostname resolve for each descriptor we download. This
1203 will cut down on the number of "Success: chose address 'x.x.x.x'"
1204 log lines, and also avoid confusing clock jumps if the resolver
1205 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
1207 o Minor features (port flags):
1208 - Add new flags to the *Port options to give finer control over which
1209 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
1210 and the synthetic flag OnionTrafficOnly, which is equivalent to
1211 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
1212 18693; patch by "teor".
1214 o Minor features (build, hardening):
1215 - Detect and work around a libclang_rt problem that would prevent
1216 clang from finding __mulodi4() on some 32-bit platforms, and thus
1217 keep -ftrapv from linking on those systems. Closes ticket 19079.
1218 - When building on a system without runtime support for the runtime
1219 hardening options, try to log a useful warning at configuration
1220 time, rather than an incomprehensible warning at link time. If
1221 expensive hardening was requested, this warning becomes an error.
1222 Closes ticket 18895.
1224 o Minor features (client, directory):
1225 - Since authorities now omit all routers that lack the Running and
1226 Valid flags, we assume that any relay listed in the consensus must
1227 have those flags. Closes ticket 20001; implements part of
1230 o Minor features (code safety):
1231 - In our integer-parsing functions, ensure that the maximum value we
1232 allow is no smaller than the minimum value. Closes ticket 19063;
1233 patch from "U+039b".
1235 o Minor features (compilation, portability):
1236 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
1239 o Minor features (config):
1240 - Warn users when descriptor and port addresses are inconsistent.
1241 Mitigates bug 13953; patch by teor.
1243 o Minor features (controller):
1244 - Allow controllers to configure basic client authorization on
1245 hidden services when they create them with the ADD_ONION controller
1246 command. Implements ticket 15588. Patch by "special".
1247 - Fire a STATUS_SERVER controller event whenever the hibernation
1248 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
1249 - Implement new GETINFO queries for all downloads that use
1250 download_status_t to schedule retries. This allows controllers to
1251 examine the schedule for pending downloads. Closes ticket 19323.
1253 o Minor features (development tools, etags):
1254 - Teach the "make tags" Makefile target how to correctly find
1255 "MOCK_IMPL" function definitions. Patch from nherring; closes
1258 o Minor features (directory authority):
1259 - After voting, if the authorities decide that a relay is not
1260 "Valid", they no longer include it in the consensus at all. Closes
1261 ticket 20002; implements part of proposal 272.
1262 - Directory authorities now only give the Guard flag to a relay if
1263 they are also giving it the Stable flag. This change allows us to
1264 simplify path selection for clients. It should have minimal effect
1265 in practice, since >99% of Guards already have the Stable flag.
1266 Implements ticket 18624.
1267 - Directory authorities now write their v3-status-votes file out to
1268 disk earlier in the consensus process, so we have a record of the
1269 votes even if we abort the consensus process. Resolves
1272 o Minor features (fallback directory list, new since 0.2.9.7-rc):
1273 - Replace the 81 remaining fallbacks of the 100 originally
1274 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
1275 fallbacks (123 new, 54 existing, 27 removed) generated in December
1276 2016. Resolves ticket 20170.
1278 o Minor features (hidden service):
1279 - Stop being so strict about the payload length of "rendezvous1"
1280 cells. We used to be locked in to the "TAP" handshake length, and
1281 now we can handle better handshakes like "ntor". Resolves
1284 o Minor features (infrastructure, time):
1285 - Tor now includes an improved timer backend, so that we can
1286 efficiently support tens or hundreds of thousands of concurrent
1287 timers, as will be needed for some of our planned anti-traffic-
1288 analysis work. This code is based on William Ahern's "timeout.c"
1289 project, which implements a "tickless hierarchical timing wheel".
1290 Closes ticket 18365.
1291 - Tor now uses the operating system's monotonic timers (where
1292 available) for internal fine-grained timing. Previously we would
1293 look at the system clock, and then attempt to compensate for the
1294 clock running backwards. Closes ticket 18908.
1296 o Minor features (logging):
1297 - Add a set of macros to check nonfatal assertions, for internal
1298 use. Migrating more of our checks to these should help us avoid
1299 needless crash bugs. Closes ticket 18613.
1300 - Provide a more useful warning message when configured with an
1301 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
1302 - When dumping unparseable router descriptors, optionally store them
1303 in separate files, named by digest, up to a configurable size
1304 limit. You can change the size limit by setting the
1305 MaxUnparseableDescSizeToLog option, and disable this feature by
1306 setting that option to 0. Closes ticket 18322.
1308 o Minor features (performance):
1309 - Change the "optimistic data" extension from "off by default" to
1310 "on by default". The default was ordinarily overridden by a
1311 consensus option, but when clients were bootstrapping for the
1312 first time, they would not have a consensus to get the option
1313 from. Changing this default saves a round-trip during startup.
1314 Closes ticket 18815.
1316 o Minor features (relay, usability):
1317 - When the directory authorities refuse a bad relay's descriptor,
1318 encourage the relay operator to contact us. Many relay operators
1319 won't notice this line in their logs, but it's a win if even a few
1320 learn why we don't like what their relay was doing. Resolves
1323 o Minor features (security, TLS):
1324 - Servers no longer support clients that lack AES ciphersuites.
1325 (3DES is no longer considered an acceptable cipher.) We believe
1326 that no such Tor clients currently exist, since Tor has required
1327 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
1329 o Minor features (testing):
1330 - Disable memory protections on OpenBSD when performing our unit
1331 tests for memwipe(). The test deliberately invokes undefined
1332 behavior, and the OpenBSD protections interfere with this. Patch
1333 from "rubiate". Closes ticket 20066.
1334 - Move the test-network.sh script to chutney, and modify tor's test-
1335 network.sh to call the (newer) chutney version when available.
1336 Resolves ticket 19116. Patch by teor.
1337 - Use the lcov convention for marking lines as unreachable, so that
1338 we don't count them when we're generating test coverage data.
1339 Update our coverage tools to understand this convention. Closes
1341 - Our link-handshake unit tests now check that when invalid
1342 handshakes fail, they fail with the error messages we expected.
1343 - Our unit testing code that captures log messages no longer
1344 prevents them from being written out if the user asked for them
1345 (by passing --debug or --info or --notice or --warn to the "test"
1346 binary). This change prevents us from missing unexpected log
1347 messages simply because we were looking for others. Related to
1349 - The unit tests now log all warning messages with the "BUG" flag.
1350 Previously, they only logged errors by default. This change will
1351 help us make our testing code more correct, and make sure that we
1352 only hit this code when we mean to. In the meantime, however,
1353 there will be more warnings in the unit test logs than before.
1354 This is preparatory work for ticket 19999.
1355 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
1356 assertion as a test failure.
1357 - We've done significant work to make the unit tests run faster.
1359 o Minor features (testing, ipv6):
1360 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
1361 tests. Remove bridges+hs, as it's somewhat redundant. This
1362 requires a recent chutney version that supports IPv6 clients,
1363 relays, and authorities. Closes ticket 20069; patch by teor.
1364 - Add the single-onion and single-onion-ipv6 chutney targets to
1365 "make test-network-all". This requires a recent chutney version
1366 with the single onion network flavors (git c72a652 or later).
1367 Closes ticket 20072; patch by teor.
1369 o Minor features (Tor2web):
1370 - Make Tor2web clients respect ReachableAddresses. This feature was
1371 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
1372 0.2.8.7. Implements feature 20034. Patch by teor.
1374 o Minor features (unix domain sockets):
1375 - When configuring a unix domain socket for a SocksPort,
1376 ControlPort, or Hidden service, you can now wrap the address in
1377 quotes, using C-style escapes inside the quotes. This allows unix
1378 domain socket paths to contain spaces. Resolves ticket 18753.
1380 o Minor features (user interface):
1381 - Tor now supports the ability to declare options deprecated, so
1382 that we can recommend that people stop using them. Previously, this
1383 was done in an ad-hoc way. There is a new --list-deprecated-options
1384 command-line option to list all of the deprecated options. Closes
1387 o Minor features (virtual addresses):
1388 - Increase the maximum number of bits for the IPv6 virtual network
1389 prefix from 16 to 104. In this way, the condition for address
1390 allocation is less restrictive. Closes ticket 20151; feature
1393 o Minor bug fixes (circuits):
1394 - Use the CircuitBuildTimeout option whenever
1395 LearnCircuitBuildTimeout is disabled. Previously, we would respect
1396 the option when a user disabled it, but not when it was disabled
1397 because some other option was set. Fixes bug 20073; bugfix on
1398 0.2.4.12-alpha. Patch by teor.
1400 o Minor bugfixes (build):
1401 - The current Git revision when building from a local repository is
1402 now detected correctly when using git worktrees. Fixes bug 20492;
1403 bugfix on 0.2.3.9-alpha.
1405 o Minor bugfixes (relay address discovery):
1406 - Stop reordering IP addresses returned by the OS. This makes it
1407 more likely that Tor will guess the same relay IP address every
1408 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
1409 Reported by René Mayrhofer, patch by "cypherpunks".
1411 o Minor bugfixes (memory allocation):
1412 - Change how we allocate memory for large chunks on buffers, to
1413 avoid a (currently impossible) integer overflow, and to waste less
1414 space when allocating unusually large chunks. Fixes bug 20081;
1415 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
1417 o Minor bugfixes (bootstrap):
1418 - Remember the directory server we fetched the consensus or previous
1419 certificates from, and use it to fetch future authority
1420 certificates. This change improves bootstrapping performance.
1421 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
1423 o Minor bugfixes (circuits):
1424 - Make sure extend_info_from_router() is only called on servers.
1425 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
1427 o Minor bugfixes (client, fascistfirewall):
1428 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
1429 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
1431 o Minor bugfixes (client, unix domain sockets):
1432 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
1433 the client address is meaningless. Fixes bug 20261; bugfix
1436 o Minor bugfixes (code style):
1437 - Fix an integer signedness conversion issue in the case conversion
1438 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
1440 o Minor bugfixes (compilation):
1441 - Build correctly on versions of libevent2 without support for
1442 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
1444 - When building with Clang, use a full set of GCC warnings.
1445 (Previously, we included only a subset, because of the way we
1446 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
1447 - Detect Libevent2 functions correctly on systems that provide
1448 libevent2, but where libevent1 is linked with -levent. Fixes bug
1449 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
1450 - Run correctly when built on Windows build environments that
1451 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
1453 o Minor bugfixes (configuration):
1454 - When parsing quoted configuration values from the torrc file,
1455 handle Windows line endings correctly. Fixes bug 19167; bugfix on
1456 0.2.0.16-alpha. Patch from "Pingl".
1458 o Minor bugfixes (directory authority):
1459 - Authorities now sort the "package" lines in their votes, for ease
1460 of debugging. (They are already sorted in consensus documents.)
1461 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
1462 - Die with a more useful error when the operator forgets to place
1463 the authority_signing_key file into the keys directory. This
1464 avoids an uninformative assert & traceback about having an invalid
1465 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
1466 - When allowing private addresses, mark Exits that only exit to
1467 private locations as such. Fixes bug 20064; bugfix
1469 - When parsing a detached signature, make sure we use the length of
1470 the digest algorithm instead of a hardcoded DIGEST256_LEN in
1471 order to avoid comparing bytes out-of-bounds with a smaller digest
1472 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
1474 o Minor bugfixes (getpass):
1475 - Defensively fix a non-triggerable heap corruption at do_getpass()
1476 to protect ourselves from mistakes in the future. Fixes bug
1477 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
1480 o Minor bugfixes (guard selection):
1481 - Don't mark guards as unreachable if connection_connect() fails.
1482 That function fails for local reasons, so it shouldn't reveal
1483 anything about the status of the guard. Fixes bug 14334; bugfix
1485 - Use a single entry guard even if the NumEntryGuards consensus
1486 parameter is not provided. Fixes bug 17688; bugfix
1489 o Minor bugfixes (hidden services):
1490 - Increase the minimum number of internal circuits we preemptively
1491 build from 2 to 3, so a circuit is available when a client
1492 connects to another onion service. Fixes bug 13239; bugfix
1494 - Allow hidden services to run on IPv6 addresses even when the
1495 IPv6Exit option is not set. Fixes bug 18357; bugfix
1497 - Stop logging intro point details to the client log on certain
1498 error conditions. Fixed as part of bug 20012; bugfix on
1499 0.2.4.8-alpha. Patch by teor.
1500 - When deleting an ephemeral hidden service, close its intro points
1501 even if they are not completely open. Fixes bug 18604; bugfix
1503 - When configuring hidden services, check every hidden service
1504 directory's permissions. Previously, we only checked the last
1505 hidden service. Fixes bug 20529; bugfix on 0.2.6.2-alpha.
1507 o Minor bugfixes (IPv6, testing):
1508 - Check for IPv6 correctly on Linux when running test networks.
1509 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
1511 o Minor bugfixes (Linux seccomp2 sandbox):
1512 - Add permission to run the sched_yield() and sigaltstack() system
1513 calls, in order to support versions of Tor compiled with asan or
1514 ubsan code that use these calls. Now "sandbox 1" and
1515 "--enable-expensive-hardening" should be compatible on more
1516 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
1518 o Minor bugfixes (logging):
1519 - Downgrade a harmless log message about the
1520 pending_entry_connections list from "warn" to "info". Mitigates
1522 - Log a more accurate message when we fail to dump a microdescriptor.
1523 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
1524 - When logging a directory ownership mismatch, log the owning
1525 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
1526 - When we are unable to remove the bw_accounting file, do not warn
1527 if the reason we couldn't remove it was that it didn't exist.
1528 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from pastly.
1530 o Minor bugfixes (memory leak):
1531 - Fix a series of slow memory leaks related to parsing torrc files
1532 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
1533 - Avoid a small memory leak when informing worker threads about
1534 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
1535 - Fix a small memory leak when receiving AF_UNIX connections on a
1536 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
1537 - When moving a signed descriptor object from a source to an
1538 existing destination, free the allocated memory inside that
1539 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
1540 - Fix a memory leak and use-after-free error when removing entries
1541 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
1542 0.2.5.5-alpha. Patch from "cypherpunks".
1543 - Fix a small, uncommon memory leak that could occur when reading a
1544 truncated ed25519 key file. Fixes bug 18956; bugfix
1547 o Minor bugfixes (option parsing):
1548 - Count unix sockets when counting client listeners (SOCKS, Trans,
1549 NATD, and DNS). This has no user-visible behavior changes: these
1550 options are set once, and never read. Required for correct
1551 behavior in ticket 17178. Fixes bug 19677; bugfix on
1552 0.2.6.3-alpha. Patch by teor.
1554 o Minor bugfixes (options):
1555 - Check the consistency of UseEntryGuards and EntryNodes more
1556 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
1558 - Stop changing the configured value of UseEntryGuards on
1559 authorities and Tor2web clients. Fixes bug 20074; bugfix on
1560 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
1563 o Minor bugfixes (relay):
1564 - Ensure relays don't make multiple connections during bootstrap.
1565 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
1566 - Do not try to parallelize workers more than 16x without the user
1567 explicitly configuring us to do so, even if we do detect more than
1568 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
1570 o Minor bugfixes (testing):
1571 - The test-stem and test-network makefile targets now depend only on
1572 the tor binary that they are testing. Previously, they depended on
1573 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
1574 patch from "cypherpunks".
1575 - Allow clients to retry HSDirs much faster in test networks. Fixes
1576 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
1577 - Avoid a unit test failure on systems with over 16 detectable CPU
1578 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
1579 - Let backtrace tests work correctly under AddressSanitizer:
1580 disable ASAN's detection of segmentation faults while running
1581 test_bt.sh, so that we can make sure that our own backtrace
1582 generation code works. Fixes bug 18934; bugfix
1583 on 0.2.5.2-alpha. Patch from "cypherpunks".
1584 - Fix the test-network-all target on out-of-tree builds by using the
1585 correct path to the test driver script. Fixes bug 19421; bugfix
1587 - Stop spurious failures in the local interface address discovery
1588 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
1590 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
1591 removed the ECDH ciphers which caused the tests to fail on
1592 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
1593 - The tor_tls_server_info_callback unit test no longer crashes when
1594 debug-level logging is turned on. Fixes bug 20041; bugfix
1597 o Minor bugfixes (time):
1598 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
1599 bugfix on all released tor versions.
1600 - When computing the difference between two times in milliseconds,
1601 we now round to the nearest millisecond correctly. Previously, we
1602 could sometimes round in the wrong direction. Fixes bug 19428;
1603 bugfix on 0.2.2.2-alpha.
1605 o Minor bugfixes (Tor2web):
1606 - Prevent Tor2web clients from running hidden services: these services
1607 are not anonymous due to the one-hop client paths. Fixes bug
1608 19678. Patch by teor.
1610 o Minor bugfixes (user interface):
1611 - Display a more accurate number of suppressed messages in the log
1612 rate-limiter. Previously, there was a potential integer overflow
1613 in the counter. Now, if the number of messages hits a maximum, the
1614 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
1616 - Fix a typo in the passphrase prompt for the ed25519 identity key.
1617 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
1619 o Code simplification and refactoring:
1620 - Remove redundant declarations of the MIN macro. Closes
1622 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
1623 Closes ticket 18462; patch from "icanhasaccount".
1624 - Split the 600-line directory_handle_command_get function into
1625 separate functions for different URL types. Closes ticket 16698.
1628 - Add module-level internal documentation for 36 C files that
1629 previously didn't have a high-level overview. Closes ticket 20385.
1630 - Correct the IPv6 syntax in our documentation for the
1631 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
1632 - Correct the minimum bandwidth value in torrc.sample, and queue a
1633 corresponding change for torrc.minimal. Closes ticket 20085.
1634 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
1635 ticket 19153. Patch from "U+039b".
1636 - Module-level documentation for several more modules. Closes
1637 tickets 19287 and 19290.
1638 - Document the --passphrase-fd option in the tor manpage. Fixes bug
1639 19504; bugfix on 0.2.7.3-rc.
1640 - Document the default PathsNeededToBuildCircuits value that's used
1641 by clients when the directory authorities don't set
1642 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 0.2.4.10-alpha.
1643 Patch by teor, reported by Jesse V.
1644 - Fix manual for the User option: it takes a username, not a UID.
1645 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
1647 - Fix the description of the --passphrase-fd option in the
1648 tor-gencert manpage. The option is used to pass the number of a
1649 file descriptor to read the passphrase from, not to read the file
1650 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
1653 - We no longer include the (dead, deprecated) bufferevent code in
1654 Tor. Closes ticket 19450. Based on a patch from "U+039b".
1657 - Remove support for "GET /tor/bytes.txt" DirPort request, and
1658 "GETINFO dir-usage" controller request, which were only available
1659 via a compile-time option in Tor anyway. Feature was added in
1660 0.2.2.1-alpha. Resolves ticket 19035.
1661 - There is no longer a compile-time option to disable support for
1662 TransPort. (If you don't want TransPort, just don't use it.) Patch
1663 from "U+039b". Closes ticket 19449.
1666 - Run more workqueue tests as part of "make check". These had
1667 previously been implemented, but you needed to know special
1668 command-line options to enable them.
1669 - We now have unit tests for our code to reject zlib "compression
1670 bombs". (Fortunately, the code works fine.)
1673 Changes in version 0.2.8.11 - 2016-12-08
1674 Tor 0.2.8.11 backports fixes for additional portability issues that
1675 could prevent Tor from building correctly on OSX Sierra, or with
1676 OpenSSL 1.1. Affected users should upgrade; others can safely stay
1679 o Minor bugfixes (portability):
1680 - Avoid compilation errors when building on OSX Sierra. Sierra began
1681 to support the getentropy() and clock_gettime() APIs, but created
1682 a few problems in doing so. Tor 0.2.9 has a more thorough set of
1683 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
1684 monotonic time interfaces. Fixes bug 20865. Bugfix
1687 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
1688 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
1689 architectures. Closes ticket 20588.
1692 Changes in version 0.2.8.10 - 2016-12-02
1693 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
1694 unusable after they left standby mode. It also backports fixes for
1695 a few portability issues and a small but problematic memory leak.
1697 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
1698 - When Tor leaves standby because of a new application request, open
1699 circuits as needed to serve that request. Previously, we would
1700 potentially wait a very long time. Fixes part of bug 19969; bugfix
1703 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
1704 - Clients now respond to new application stream requests immediately
1705 when they arrive, rather than waiting up to one second before
1706 starting to handle them. Fixes part of bug 19969; bugfix
1709 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
1710 - Work around a bug in the OSX 10.12 SDK that would prevent us from
1711 successfully targeting earlier versions of OSX. Resolves
1714 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
1715 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
1716 20551; bugfix on 0.2.1.1-alpha.
1718 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
1719 - Work around a memory leak in OpenSSL 1.1 when encoding public
1720 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
1722 o Minor features (geoip):
1723 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
1727 Changes in version 0.2.8.9 - 2016-10-17
1728 Tor 0.2.8.9 backports a fix for a security hole in previous versions
1729 of Tor that would allow a remote attacker to crash a Tor client,
1730 hidden service, relay, or authority. All Tor users should upgrade to
1731 this version, or to 0.2.9.4-alpha. Patches will be released for older
1734 o Major features (security fixes, also in 0.2.9.4-alpha):
1735 - Prevent a class of security bugs caused by treating the contents
1736 of a buffer chunk as if they were a NUL-terminated string. At
1737 least one such bug seems to be present in all currently used
1738 versions of Tor, and would allow an attacker to remotely crash
1739 most Tor instances, especially those compiled with extra compiler
1740 hardening. With this defense in place, such bugs can't crash Tor,
1741 though we should still fix them as they occur. Closes ticket
1742 20384 (TROVE-2016-10-001).
1744 o Minor features (geoip):
1745 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
1749 Changes in version 0.2.8.8 - 2016-09-23
1750 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
1751 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
1752 who select public relays as their bridges.
1754 o Major bugfixes (crash):
1755 - Fix a complicated crash bug that could affect Tor clients
1756 configured to use bridges when replacing a networkstatus consensus
1757 in which one of their bridges was mentioned. OpenBSD users saw
1758 more crashes here, but all platforms were potentially affected.
1759 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
1761 o Major bugfixes (relay, OOM handler):
1762 - Fix a timing-dependent assertion failure that could occur when we
1763 tried to flush from a circuit after having freed its cells because
1764 of an out-of-memory condition. Fixes bug 20203; bugfix on
1765 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
1768 o Minor feature (fallback directories):
1769 - Remove broken fallbacks from the hard-coded fallback directory
1770 list. Closes ticket 20190; patch by teor.
1772 o Minor features (geoip):
1773 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
1777 Changes in version 0.2.8.7 - 2016-08-24
1778 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
1779 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
1780 who sets the ReachableAddresses option, and all bridges, are strongly
1781 encouraged to upgrade.
1783 o Directory authority changes:
1784 - The "Tonga" bridge authority has been retired; the new bridge
1785 authority is "Bifroest". Closes tickets 19728 and 19690.
1787 o Major bugfixes (client, security):
1788 - Only use the ReachableAddresses option to restrict the first hop
1789 in a path. In earlier versions of 0.2.8.x, it would apply to
1790 every hop in the path, with a possible degradation in anonymity
1791 for anyone using an uncommon ReachableAddress setting. Fixes bug
1792 19973; bugfix on 0.2.8.2-alpha.
1794 o Minor features (geoip):
1795 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
1798 o Minor bugfixes (compilation):
1799 - Remove an inappropriate "inline" in tortls.c that was causing
1800 warnings on older versions of GCC. Fixes bug 19903; bugfix
1803 o Minor bugfixes (fallback directories):
1804 - Avoid logging a NULL string pointer when loading fallback
1805 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
1806 and 0.2.8.1-alpha. Report and patch by "rubiate".
1809 Changes in version 0.2.8.6 - 2016-08-02
1811 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
1813 The Tor 0.2.8 series improves client bootstrapping performance,
1814 completes the authority-side implementation of improved identity
1815 keys for relays, and includes numerous bugfixes and performance
1816 improvements throughout the program. This release continues to
1817 improve the coverage of Tor's test suite. For a full list of
1818 changes since Tor 0.2.7, see the ReleaseNotes file.
1820 Below is a list of the changes since Tor 0.2.7.
1822 o New system requirements:
1823 - Tor no longer attempts to support platforms where the "time_t"
1824 type is unsigned. (To the best of our knowledge, only OpenVMS does
1825 this, and Tor has never actually built on OpenVMS.) Closes
1827 - Tor no longer supports versions of OpenSSL with a broken
1828 implementation of counter mode. (This bug was present in OpenSSL
1829 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
1830 longer runs with, these versions.
1831 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
1832 later (released in 2008 and 2009 respectively). If you are
1833 building Tor from the git repository instead of from the source
1834 distribution, and your tools are older than this, you will need to
1835 upgrade. Closes ticket 17732.
1837 o Directory authority changes:
1838 - Update the V3 identity key for the dannenberg directory authority:
1839 it was changed on 18 November 2015. Closes task 17906. Patch
1841 - Urras is no longer a directory authority. Closes ticket 19271.
1843 o Major features (directory system):
1844 - Include a trial list of default fallback directories, based on an
1845 opt-in survey of suitable relays. Doing this should make clients
1846 bootstrap more quickly and reliably, and reduce the load on the
1847 directory authorities. Closes ticket 15775. Patch by teor.
1848 Candidates identified using an OnionOO script by weasel, teor,
1849 gsathya, and karsten.
1850 - Previously only relays that explicitly opened a directory port
1851 (DirPort) accepted directory requests from clients. Now all
1852 relays, with and without a DirPort, accept and serve tunneled
1853 directory requests that they receive through their ORPort. You can
1854 disable this behavior using the new DirCache option. Closes
1856 - When bootstrapping multiple consensus downloads at a time, use the
1857 first one that starts downloading, and close the rest. This
1858 reduces failures when authorities or fallback directories are slow
1859 or down. Together with the code for feature 15775, this feature
1860 should reduces failures due to fallback churn. Implements ticket
1861 4483. Patch by teor. Implements IPv4 portions of proposal 210 by
1864 o Major features (security, Linux):
1865 - When Tor starts as root on Linux and is told to switch user ID, it
1866 can now retain the capability to bind to low ports. By default,
1867 Tor will do this only when it's switching user ID and some low
1868 ports have been configured. You can change this behavior with the
1869 new option KeepBindCapabilities. Closes ticket 8195.
1871 o Major bugfixes (client, bootstrapping):
1872 - Check if bootstrap consensus downloads are still needed when the
1873 linked connection attaches. This prevents tor making unnecessary
1874 begindir-style connections, which are the only directory
1875 connections tor clients make since the fix for 18483 was merged.
1876 - Fix some edge cases where consensus download connections may not
1877 have been closed, even though they were not needed. Related to fix
1879 - Make relays retry consensus downloads the correct number of times,
1880 rather than the more aggressive client retry count. Fixes part of
1883 o Major bugfixes (dns proxy mode, crash):
1884 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
1885 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
1887 o Major bugfixes (ed25519, voting):
1888 - Actually enable support for authorities to match routers by their
1889 Ed25519 identities. Previously, the code had been written, but
1890 some debugging code that had accidentally been left in the
1891 codebase made it stay turned off. Fixes bug 17702; bugfix
1893 - When collating votes by Ed25519 identities, authorities now
1894 include a "NoEdConsensus" flag if the ed25519 value (or lack
1895 thereof) for a server does not reflect the majority consensus.
1896 Related to bug 17668; bugfix on 0.2.7.2-alpha.
1897 - When generating a vote with keypinning disabled, never include two
1898 entries for the same ed25519 identity. This bug was causing
1899 authorities to generate votes that they could not parse when a
1900 router violated key pinning by changing its RSA identity but
1901 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
1902 18318. Bugfix on 0.2.7.2-alpha.
1904 o Major bugfixes (key management):
1905 - If OpenSSL fails to generate an RSA key, do not retain a dangling
1906 pointer to the previous (uninitialized) key value. The impact here
1907 should be limited to a difficult-to-trigger crash, if OpenSSL is
1908 running an engine that makes key generation failures possible, or
1909 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
1910 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
1913 o Major bugfixes (security, client, DNS proxy):
1914 - Stop a crash that could occur when a client running with DNSPort
1915 received a query with multiple address types, and the first
1916 address type was not supported. Found and fixed by Scott Dial.
1917 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
1919 o Major bugfixes (security, compilation):
1920 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
1921 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
1922 cause a compiler warning, thereby making other checks fail, and
1923 needlessly disabling compiler-hardening support. Fixes one case of
1924 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
1925 - Repair hardened builds under the clang compiler. Previously, our
1926 use of _FORTIFY_SOURCE would conflict with clang's address
1927 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
1929 o Major bugfixes (security, pointers):
1930 - Avoid a difficult-to-trigger heap corruption attack when extending
1931 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
1932 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
1933 Reported by Guido Vranken.
1935 o Major bugfixes (testing):
1936 - Fix a bug that would block 'make test-network-all' on systems where
1937 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
1939 o Major bugfixes (user interface):
1940 - Correctly give a warning in the cases where a relay is specified
1941 by nickname, and one such relay is found, but it is not officially
1942 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
1944 o Minor features (accounting):
1945 - Added two modes to the AccountingRule option: One for limiting
1946 only the number of bytes sent ("AccountingRule out"), and one for
1947 limiting only the number of bytes received ("AccountingRule in").
1948 Closes ticket 15989; patch from "unixninja92".
1950 o Minor features (bug-resistance):
1951 - Make Tor survive errors involving connections without a
1952 corresponding event object. Previously we'd fail with an
1953 assertion; now we produce a log message. Related to bug 16248.
1954 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
1955 level code, to harden against accidental failures to NUL-
1956 terminate. Part of ticket 17852. Patch from jsturgix. Found
1959 o Minor features (build):
1960 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
1961 as having possible IPFW support. Closes ticket 18448. Patch from
1963 - Since our build process now uses "make distcheck", we no longer
1964 force "make dist" to depend on "make check". Closes ticket 17893;
1965 patch from "cypherpunks".
1966 - Tor now builds once again with the recent OpenSSL 1.1 development
1967 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev). We have been
1968 tracking OpenSSL 1.1 development as it has progressed, and fixing
1969 numerous compatibility issues as they arose. See tickets
1970 17549, 17921, 17984, 19499, and 18286.
1971 - When building manual pages, set the timezone to "UTC", so that the
1972 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
1973 Patch from intrigeri.
1975 o Minor features (clients):
1976 - Make clients, onion services, and bridge relays always use an
1977 encrypted begindir connection for directory requests. Resolves
1978 ticket 18483. Patch by teor.
1980 o Minor features (controller):
1981 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
1982 controllers can examine the the reject rules added by
1983 ExitPolicyRejectPrivate. This makes it easier for stem to display
1985 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
1986 tickets 16774 and 17817. Patch by George Tankersley.
1987 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
1988 service descriptor from a service's local hidden service
1989 descriptor cache. Closes ticket 14846.
1991 o Minor features (crypto):
1992 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
1993 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
1995 - Improve performance when hashing non-multiple of 8 sized buffers,
1996 based on Andrew Moon's public domain SipHash-2-4 implementation.
1997 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
1998 - Validate the hard-coded Diffie-Hellman parameters and ensure that
1999 p is a safe prime, and g is a suitable generator. Closes
2001 - When allocating a digest state object, allocate no more space than
2002 we actually need. Previously, we would allocate as much space as
2003 the state for the largest algorithm would need. This change saves
2004 up to 672 bytes per circuit. Closes ticket 17796.
2006 o Minor features (directory downloads):
2007 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
2008 directory mirrors. The default is 1; set it to 0 to disable
2009 fallbacks. Implements ticket 17576. Patch by teor.
2010 - Wait for busy authorities and fallback directories to become non-
2011 busy when bootstrapping. (A similar change was made in 6c443e987d
2012 for directory caches chosen from the consensus.) Closes ticket
2013 17864; patch by teor.
2015 o Minor features (geoip):
2016 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
2019 o Minor features (hidden service directory):
2020 - Streamline relay-side hsdir handling: when relays consider whether
2021 to accept an uploaded hidden service descriptor, they no longer
2022 check whether they are one of the relays in the network that is
2023 "supposed" to handle that descriptor. Implements ticket 18332.
2025 o Minor features (IPv6):
2026 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
2027 to 1, tor prefers IPv6 directory addresses.
2028 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
2029 avoids using IPv4 for client OR and directory connections.
2030 - Add address policy assume_action support for IPv6 addresses.
2031 - Add an argument 'ipv6=address:orport' to the DirAuthority and
2032 FallbackDir torrc options, to specify an IPv6 address for an
2033 authority or fallback directory. Add hard-coded ipv6 addresses for
2034 directory authorities that have them. Closes ticket 17327; patch
2035 from Nick Mathewson and teor.
2036 - Allow users to configure directory authorities and fallback
2037 directory servers with IPv6 addresses and ORPorts. Resolves
2039 - Limit IPv6 mask bits to 128.
2040 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
2041 17638; bugfix on 0.0.2pre8. Patch by teor.
2042 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
2043 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
2044 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
2045 - Warn when comparing against an AF_UNSPEC address in a policy, it's
2046 almost always a bug. Closes ticket 17863; patch by teor.
2047 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
2048 17060; bugfix on 0.2.1.3-alpha. Patch by teor.
2050 o Minor features (Linux seccomp2 sandbox):
2051 - Reject attempts to change our Address with "Sandbox 1" enabled.
2052 Changing Address with Sandbox turned on would never actually work,
2053 but previously it would fail in strange and confusing ways. Found
2056 o Minor features (logging):
2057 - When logging to syslog, allow a tag to be added to the syslog
2058 identity (the string prepended to every log message). The tag can
2059 be configured with SyslogIdentityTag and defaults to none. Setting
2060 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
2063 o Minor features (portability):
2064 - Use timingsafe_memcmp() where available. Closes ticket 17944;
2065 patch from <logan@hackers.mu>.
2067 o Minor features (relay, address discovery):
2068 - Add a family argument to get_interface_addresses_raw() and
2069 subfunctions to make network interface address interogation more
2070 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
2071 types of interfaces from the operating system. Resolves
2073 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
2074 fails to enumerate interface addresses using the platform-specific
2075 API, have it rely on the UDP socket fallback technique to try and
2076 find out what IP addresses (both IPv4 and IPv6) our machine has.
2077 Resolves ticket 17951.
2079 o Minor features (replay cache):
2080 - The replay cache now uses SHA256 instead of SHA1. Implements
2081 feature 8961. Patch by teor, issue reported by rransom.
2083 o Minor features (robustness):
2084 - Exit immediately with an error message if the code attempts to use
2085 Libevent without having initialized it. This should resolve some
2086 frequently-made mistakes in our unit tests. Closes ticket 18241.
2088 o Minor features (security, clock):
2089 - Warn when the system clock appears to move back in time (when the
2090 state file was last written in the future). Tor doesn't know that
2091 consensuses have expired if the clock is in the past. Patch by
2092 teor. Implements ticket 17188.
2094 o Minor features (security, exit policies):
2095 - ExitPolicyRejectPrivate now rejects more private addresses by
2096 default. Specifically, it now rejects the relay's outbound bind
2097 addresses (if configured), and the relay's configured port
2098 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
2099 0.2.0.11-alpha. Patch by teor.
2101 o Minor features (security, memory erasure):
2102 - Make memwipe() do nothing when passed a NULL pointer or buffer of
2103 zero size. Check size argument to memwipe() for underflow. Fixes
2104 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
2106 - Set the unused entries in a smartlist to NULL. This helped catch
2107 a (harmless) bug, and shouldn't affect performance too much.
2108 Implements ticket 17026.
2109 - Use SecureMemoryWipe() function to securely clean memory on
2110 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
2111 Implements feature 17986.
2112 - Use explicit_bzero or memset_s when present. Previously, we'd use
2113 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
2114 from <logan@hackers.mu> and <selven@hackers.mu>.
2116 o Minor features (security, RNG):
2117 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
2118 positively are not allowed to fail. Previously we depended on
2119 internal details of OpenSSL's behavior. Closes ticket 17686.
2120 - Never use the system entropy output directly for anything besides
2121 seeding the PRNG. When we want to generate important keys, instead
2122 of using system entropy directly, we now hash it with the PRNG
2123 stream. This may help resist certain attacks based on broken OS
2124 entropy implementations. Closes part of ticket 17694.
2125 - Use modern system calls (like getentropy() or getrandom()) to
2126 generate strong entropy on platforms that have them. Closes
2129 o Minor features (security, win32):
2130 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
2131 attack. Fixes bug 18123; bugfix on all tor versions. Patch
2134 o Minor features (unix domain sockets):
2135 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
2136 Unix domain sockets without checking the permissions on the parent
2137 directory. (Tor checks permissions by default because some
2138 operating systems only check permissions on the parent directory.
2139 However, some operating systems do look at permissions on the
2140 socket, and tor's default check is unneeded.) Closes ticket 18458.
2143 o Minor features (unix file permissions):
2144 - Defer creation of Unix sockets until after setuid. This avoids
2145 needing CAP_CHOWN and CAP_FOWNER when using systemd's
2146 CapabilityBoundingSet, or chown and fowner when using SELinux.
2147 Implements part of ticket 17562. Patch from Jamie Nguyen.
2148 - If any directory created by Tor is marked as group readable, the
2149 filesystem group is allowed to be either the default GID or the
2150 root user. Allowing root to read the DataDirectory prevents the
2151 need for CAP_READ_SEARCH when using systemd's
2152 CapabilityBoundingSet, or dac_read_search when using SELinux.
2153 Implements part of ticket 17562. Patch from Jamie Nguyen.
2154 - Introduce a new DataDirectoryGroupReadable option. If it is set to
2155 1, the DataDirectory will be made readable by the default GID.
2156 Implements part of ticket 17562. Patch from Jamie Nguyen.
2158 o Minor bugfixes (accounting):
2159 - The max bandwidth when using 'AccountRule sum' is now correctly
2160 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
2163 o Minor bugfixes (assert, portability):
2164 - Fix an assertion failure in memarea.c on systems where "long" is
2165 shorter than the size of a pointer. Fixes bug 18716; bugfix
2168 o Minor bugfixes (bootstrap):
2169 - Consistently use the consensus download schedule for authority
2170 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
2172 o Minor bugfixes (build):
2173 - Avoid spurious failures from configure files related to calling
2174 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
2175 0.2.0.1-alpha. Patch from "cypherpunks".
2176 - Do not link the unit tests against both the testing and non-
2177 testing versions of the static libraries. Fixes bug 18490; bugfix
2179 - Resolve warnings when building on systems that are concerned with
2180 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
2182 - Silence spurious clang-scan warnings in the ed25519_donna code by
2183 explicitly initializing some objects. Fixes bug 18384; bugfix on
2184 0.2.7.2-alpha. Patch by teor.
2185 - When libscrypt.h is found, but no libscrypt library can be linked,
2186 treat libscrypt as absent. Fixes bug 19161; bugfix
2188 - Cause the unit tests to compile correctly on mingw64 versions that
2189 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
2190 - Don't try to use the pthread_condattr_setclock() function unless
2191 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
2192 17819; bugfix on 0.2.6.3-alpha.
2193 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
2195 - Fix search for libevent libraries on OpenBSD (and other systems
2196 that install libevent 1 and libevent 2 in parallel). Fixes bug
2197 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
2198 - Isolate environment variables meant for tests from the rest of the
2199 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
2200 - Mark all object files that include micro-revision.i as depending
2201 on it, so as to make parallel builds more reliable. Fixes bug
2202 17826; bugfix on 0.2.5.1-alpha.
2203 - Remove config.log only from make distclean, not from make clean.
2204 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
2205 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
2207 - Remove an #endif from configure.ac so that we correctly detect the
2208 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
2211 o Minor bugfixes (client, bootstrap):
2212 - Count receipt of new microdescriptors as progress towards
2213 bootstrapping. Previously, with EntryNodes set, Tor might not
2214 successfully repopulate the guard set on bootstrapping. Fixes bug
2215 16825; bugfix on 0.2.3.1-alpha.
2217 o Minor bugfixes (code correctness):
2218 - Fix a bad memory handling bug that would occur if we had queued a
2219 cell on a channel's incoming queue. Fortunately, we can't actually
2220 queue a cell like that as our code is constructed today, but it's
2221 best to avoid this kind of error, even if there isn't any code
2222 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
2223 - Assert that allocated memory held by the reputation code is freed
2224 according to its internal counters. Fixes bug 17753; bugfix
2226 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
2228 - Update to the latest version of Trunnel, which tries harder to
2229 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
2230 by clang address sanitizer. Fixes bug 18373; bugfix
2232 - When closing an entry connection, generate a warning if we should
2233 have sent an end cell for it but we haven't. Fixes bug 17876;
2234 bugfix on 0.2.3.2-alpha.
2236 o Minor bugfixes (configuration):
2237 - Fix a tiny memory leak when parsing a port configuration ending in
2238 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
2240 o Minor bugfixes (containers):
2241 - If we somehow attempt to construct a heap with more than
2242 1073741822 elements, avoid an integer overflow when maintaining
2243 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
2245 o Minor bugfixes (controller, microdescriptors):
2246 - Make GETINFO dir/status-vote/current/consensus conform to the
2247 control specification by returning "551 Could not open cached
2248 consensus..." when not caching consensuses. Fixes bug 18920;
2249 bugfix on 0.2.2.6-alpha.
2251 o Minor bugfixes (crypto):
2252 - Check the return value of HMAC() and assert on failure. Fixes bug
2253 17658; bugfix on 0.2.3.6-alpha. Patch by teor.
2255 o Minor bugfixes (directories):
2256 - When fetching extrainfo documents, compare their SHA256 digests
2257 and Ed25519 signing key certificates with the routerinfo that led
2258 us to fetch them, rather than with the most recent routerinfo.
2259 Otherwise we generate many spurious warnings about mismatches.
2260 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
2261 - When generating a URL for a directory server on an IPv6 address,
2262 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
2263 on 0.2.3.9-alpha. Patch from Malek.
2265 o Minor bugfixes (downloading):
2266 - Predict more correctly whether we'll be downloading over HTTP when
2267 we determine the maximum length of a URL. This should avoid a
2268 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
2271 o Minor bugfixes (exit policies, security):
2272 - Refresh an exit relay's exit policy when interface addresses
2273 change. Previously, tor only refreshed the exit policy when the
2274 configured external address changed. Fixes bug 18208; bugfix on
2275 0.2.7.3-rc. Patch by teor.
2277 o Minor bugfixes (fallback directories):
2278 - Mark fallbacks as "too busy" when they return a 503 response,
2279 rather than just marking authorities. Fixes bug 17572; bugfix on
2280 0.2.4.7-alpha. Patch by teor.
2281 - When requesting extrainfo descriptors from a trusted directory
2282 server, check whether it is an authority or a fallback directory
2283 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
2284 0.2.4.7-alpha. Reported by atagar, patch by teor.
2286 o Minor bugfixes (hidden service, client):
2287 - Handle the case where the user makes several fast consecutive
2288 requests to the same .onion address. Previously, the first six
2289 requests would each trigger a descriptor fetch, each picking a
2290 directory (there are 6 overall) and the seventh one would fail
2291 because no directories were left, thereby triggering a close on
2292 all current directory connections asking for the hidden service.
2293 The solution here is to not close the connections if we have
2294 pending directory fetches. Fixes bug 15937; bugfix
2297 o Minor bugfixes (hidden service, control port):
2298 - Add the onion address to the HS_DESC event for the UPLOADED action
2299 both on success or failure. It was previously hardcoded with
2300 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
2302 o Minor bugfixes (hidden service, directory):
2303 - Bridges now refuse "rendezvous2" (hidden service descriptor)
2304 publish attempts. Suggested by ticket 18332.
2306 o Minor bugfixes (IPv6):
2307 - Update the limits in max_dl_per_request for IPv6 address length.
2308 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
2310 o Minor bugfixes (Linux seccomp2 sandbox):
2311 - Allow more syscalls when running with "Sandbox 1" enabled:
2312 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
2313 some systems, these are required for Tor to start. Fixes bug
2314 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
2315 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
2316 so that get_interface_address6_via_udp_socket_hack() can work.
2317 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
2318 - Allow the setrlimit syscall, and the prlimit and prlimit64
2319 syscalls, which some libc implementations use under the hood.
2320 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
2321 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
2322 enabled and no DNS resolvers configured. This should help TAILS
2323 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
2324 - Fix a crash when using offline master ed25519 keys with the Linux
2325 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
2326 - Allow statistics to be written to disk when "Sandbox 1" is
2327 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
2328 0.2.6.1-alpha respectively.
2330 o Minor bugfixes (logging):
2331 - In log messages that include a function name, use __FUNCTION__
2332 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
2333 with clang __PRETTY_FUNCTION__ has extra information we don't
2334 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
2336 - Remove needless quotes from a log message about unparseable
2337 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
2338 - Scrub service name in "unrecognized service ID" log messages.
2339 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
2340 - When logging information about an unparsable networkstatus vote or
2341 consensus, do not say "vote" when we mean consensus. Fixes bug
2342 18368; bugfix on 0.2.0.8-alpha.
2343 - When we can't generate a signing key because OfflineMasterKey is
2344 set, do not imply that we should have been able to load it. Fixes
2345 bug 18133; bugfix on 0.2.7.2-alpha.
2346 - When logging a malformed hostname received through socks4, scrub
2347 it if SafeLogging says we should. Fixes bug 17419; bugfix
2350 o Minor bugfixes (memory safety):
2351 - Avoid freeing an uninitialized pointer when opening a socket fails
2352 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
2353 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
2355 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
2356 18672; bugfix on 0.2.5.1-alpha.
2357 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
2360 o Minor bugfixes (pluggable transports):
2361 - Avoid reporting a spurious error when we decide that we don't need
2362 to terminate a pluggable transport because it has already exited.
2363 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
2365 o Minor bugfixes (pointer arithmetic):
2366 - Fix a bug in memarea_alloc() that could have resulted in remote
2367 heap write access, if Tor had ever passed an unchecked size to
2368 memarea_alloc(). Fortunately, all the sizes we pass to
2369 memarea_alloc() are pre-checked to be less than 128 kilobytes.
2370 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
2373 o Minor bugfixes (private directory):
2374 - Prevent a race condition when creating private directories. Fixes
2375 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
2376 Patch from jsturgix. Found with Flawfinder.
2378 o Minor bugfixes (relays):
2379 - Check that both the ORPort and DirPort (if present) are reachable
2380 before publishing a relay descriptor. Otherwise, relays publish a
2381 descriptor with DirPort 0 when the DirPort reachability test takes
2382 longer than the ORPort reachability test. Fixes bug 18050; bugfix
2383 on 0.1.0.1-rc. Reported by "starlight", patch by teor.
2384 - Resolve some edge cases where we might launch an ORPort
2385 reachability check even when DisableNetwork is set. Noticed while
2386 fixing bug 18616; bugfix on 0.2.3.9-alpha.
2388 o Minor bugfixes (relays, hidden services):
2389 - Refuse connection requests to private OR addresses unless
2390 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
2391 then refuse to send any cells to a private address. Fixes bugs
2392 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by teor.
2394 o Minor bugfixes (security, hidden services):
2395 - Prevent hidden services connecting to client-supplied rendezvous
2396 addresses that are reserved as internal or multicast. Fixes bug
2397 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
2399 o Minor bugfixes (statistics):
2400 - Consistently check for overflow in round_*_to_next_multiple_of
2401 functions, and add unit tests with additional and maximal values.
2402 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
2403 - Handle edge cases in the laplace functions: avoid division by
2404 zero, avoid taking the log of zero, and silence clang type
2405 conversion warnings using round and trunc. Add unit tests for edge
2406 cases with maximal values. Fixes part of bug 13192; bugfix
2408 - We now include consensus downloads via IPv6 in our directory-
2409 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
2411 o Minor bugfixes (test networks, IPv6):
2412 - Allow internal IPv6 addresses in descriptors in test networks.
2413 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
2416 o Minor bugfixes (testing):
2417 - Check the full results of SHA256 and SHA512 digests in the unit
2418 tests. Bugfix on 0.2.2.4-alpha. Patch by teor.
2419 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
2421 - Fix a small memory leak that would occur when the
2422 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
2423 bugfix on 0.2.5.2-alpha.
2424 - Make unit tests pass on IPv6-only systems, and systems without
2425 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
2426 bugfix on 0.2.7.3-rc. Patch by teor.
2427 - The test for log_heartbeat was incorrectly failing in timezones
2428 with non-integer offsets. Instead of comparing the end of the time
2429 string against a constant, compare it to the output of
2430 format_local_iso_time when given the correct input. Fixes bug
2431 18039; bugfix on 0.2.5.4-alpha.
2432 - We no longer disable assertions in the unit tests when coverage is
2433 enabled. Instead, we require you to say --disable-asserts-in-tests
2434 to the configure script if you need assertions disabled in the
2435 unit tests (for example, if you want to perform branch coverage).
2436 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
2438 o Minor bugfixes (time handling):
2439 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
2440 field. Otherwise, our unit tests crash on Windows. Fixes bug
2441 18977; bugfix on 0.2.2.25-alpha.
2442 - Avoid overflow in tor_timegm when parsing dates in and after 2038
2443 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
2444 0.0.2pre14. Patch by teor.
2446 o Minor bugfixes (tor-gencert):
2447 - Correctly handle the case where an authority operator enters a
2448 passphrase but sends an EOF before sending a newline. Fixes bug
2449 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
2451 o Code simplification and refactoring:
2452 - Clean up a little duplicated code in
2453 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
2455 - Decouple the list of streams waiting to be attached to circuits
2456 from the overall connection list. This change makes it possible to
2457 attach streams quickly while simplifying Tor's callgraph and
2458 avoiding O(N) scans of the entire connection list. Closes
2460 - Extract the more complicated parts of circuit_mark_for_close()
2461 into a new function that we run periodically before circuits are
2462 freed. This change removes more than half of the functions
2463 currently in the "blob". Closes ticket 17218.
2464 - Move logging of redundant policy entries in
2465 policies_parse_exit_policy_internal into its own function. Closes
2466 ticket 17608; patch from "juce".
2467 - Quote all the string interpolations in configure.ac -- even those
2468 which we are pretty sure can't contain spaces. Closes ticket
2469 17744. Patch from zerosion.
2470 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
2471 use them. Closes ticket 17926.
2472 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
2473 inplace, so there's no need to have a separate implementation for
2474 the non-inplace code. Closes ticket 18258. Patch from Malek.
2475 - Simplify return types for some crypto functions that can't
2476 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
2477 - When a direct directory request fails immediately on launch,
2478 instead of relaunching that request from inside the code that
2479 launches it, instead mark the connection for teardown. This change
2480 simplifies Tor's callback and prevents the directory-request
2481 launching code from invoking itself recursively. Closes
2485 - Add a description of the correct use of the '--keygen' command-
2486 line option. Closes ticket 17583; based on text by 's7r'.
2487 - Change build messages to refer to "Fedora" instead of "Fedora
2488 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
2489 Patches from "icanhasaccount" and "cypherpunks".
2490 - Document the contents of the 'datadir/keys' subdirectory in the
2491 manual page. Closes ticket 17621.
2492 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
2493 - Explain actual minima for BandwidthRate. Closes ticket 16382.
2494 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
2495 - Mention torspec URL in the manpage and point the reader to it
2496 whenever we mention a document that belongs in torspce. Fixes
2498 - Stop recommending use of nicknames to identify relays in our
2499 MapAddress documentation. Closes ticket 18312.
2502 - Remove client-side support for connecting to Tor relays running
2503 versions of Tor before 0.2.3.6-alpha. These relays didn't support
2504 the v3 TLS handshake protocol, and are no longer allowed on the
2505 Tor network. Implements the client side of ticket 11150. Based on
2506 patches by Tom van der Woerdt.
2507 - We no longer maintain an internal freelist in memarea.c.
2508 Allocators should be good enough to make this code unnecessary,
2509 and it's doubtful that it ever had any performance benefit.
2512 - Add unit tests to check for common RNG failure modes, such as
2513 returning all zeroes, identical values, or incrementing values
2514 (OpenSSL's rand_predictable feature). Patch by teor.
2515 - Always test both ed25519 backends, so that we can be sure that our
2516 batch-open replacement code works. Part of ticket 16794.
2517 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
2518 portion of ticket 16831.
2519 - Fix several warnings from clang's address sanitizer produced in
2521 - Log more information when the backtrace tests fail. Closes ticket
2522 17892. Patch from "cypherpunks."
2523 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
2524 util_format.c, directory.c, and options_validate.c. Closes tickets
2525 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
2527 - Treat backtrace test failures as expected on FreeBSD until we
2528 solve bug 17808. Closes ticket 18204.
2529 - Unit tests for directory_handle_command_get. Closes ticket 17004.
2530 Patch from Reinaldo de Souza Jr.
2533 Changes in version 0.2.7.6 - 2015-12-10
2534 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
2535 well as a minor bug in hidden service reliability.
2537 o Major bugfixes (guard selection):
2538 - Actually look at the Guard flag when selecting a new directory
2539 guard. When we implemented the directory guard design, we
2540 accidentally started treating all relays as if they have the Guard
2541 flag during guard selection, leading to weaker anonymity and worse
2542 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
2545 o Minor features (geoip):
2546 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
2549 o Minor bugfixes (compilation):
2550 - When checking for net/pfvar.h, include netinet/in.h if possible.
2551 This fixes transparent proxy detection on OpenBSD. Fixes bug
2552 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
2553 - Fix a compilation warning with Clang 3.6: Do not check the
2554 presence of an address which can never be NULL. Fixes bug 17781.
2556 o Minor bugfixes (correctness):
2557 - When displaying an IPv6 exit policy, include the mask bits
2558 correctly even when the number is greater than 31. Fixes bug
2559 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
2560 - The wrong list was used when looking up expired intro points in a
2561 rend service object, causing what we think could be reachability
2562 issues for hidden services, and triggering a BUG log. Fixes bug
2563 16702; bugfix on 0.2.7.2-alpha.
2564 - Fix undefined behavior in the tor_cert_checksig function. Fixes
2565 bug 17722; bugfix on 0.2.7.2-alpha.
2568 Changes in version 0.2.7.5 - 2015-11-20
2569 The Tor 0.2.7 release series is dedicated to the memory of Tor user
2570 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
2571 tirelessly to advocate human rights regardless of national borders,
2572 and oppose the encroachments of mass surveillance. He opposed national
2573 exceptionalism, he brought clarity to legal and policy debates, he
2574 understood and predicted the impact of mass surveillance on the world,
2575 and he laid the groundwork for resisting it. While serving on the Tor
2576 Project's board of directors, he brought us his uncompromising focus
2577 on technical excellence in the service of humankind. Caspar was an
2578 inimitable force for good and a wonderful friend. He was kind,
2579 humorous, generous, gallant, and believed we should protect one
2580 another without exception. We honor him here for his ideals, his
2581 efforts, and his accomplishments. Please honor his memory with works
2582 that would make him proud.
2584 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
2586 The 0.2.7 series adds a more secure identity key type for relays,
2587 improves cryptography performance, resolves several longstanding
2588 hidden-service performance issues, improves controller support for
2589 hidden services, and includes small bugfixes and performance
2590 improvements throughout the program. This release series also includes
2591 more tests than before, and significant simplifications to which parts
2592 of Tor invoke which others. For a full list of changes, see below.
2594 o New system requirements:
2595 - Tor no longer includes workarounds to support Libevent versions
2596 before 1.3e. Libevent 2.0 or later is recommended. Closes
2598 - Tor no longer supports copies of OpenSSL that are missing support
2599 for Elliptic Curve Cryptography. (We began using ECC when
2600 available in 0.2.4.8-alpha, for more safe and efficient key
2601 negotiation.) In particular, support for at least one of P256 or
2602 P224 is now required, with manual configuration needed if only
2603 P224 is available. Resolves ticket 16140.
2604 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
2605 on an operating system that has not upgraded to OpenSSL 1.0 or
2606 later, and you compile Tor from source, you will need to install a
2607 more recent OpenSSL to link Tor against.) These versions of
2608 OpenSSL are still supported by the OpenSSL, but the numerous
2609 cryptographic improvements in later OpenSSL releases makes them a
2610 clear choice. Resolves ticket 16034.
2612 o Major features (controller):
2613 - Add the ADD_ONION and DEL_ONION commands that allow the creation
2614 and management of hidden services via the controller. Closes
2616 - New "GETINFO onions/current" and "GETINFO onions/detached"
2617 commands to get information about hidden services created via the
2618 controller. Part of ticket 6411.
2619 - New HSFETCH command to launch a request for a hidden service
2620 descriptor. Closes ticket 14847.
2621 - New HSPOST command to upload a hidden service descriptor. Closes
2622 ticket 3523. Patch by "DonnchaC".
2624 o Major features (Ed25519 identity keys, Proposal 220):
2625 - Add support for offline encrypted Ed25519 master keys. To use this
2626 feature on your tor relay, run "tor --keygen" to make a new master
2627 key (or to make a new signing key if you already have a master
2628 key). Closes ticket 13642.
2629 - All relays now maintain a stronger identity key, using the Ed25519
2630 elliptic curve signature format. This master key is designed so
2631 that it can be kept offline. Relays also generate an online
2632 signing key, and a set of other Ed25519 keys and certificates.
2633 These are all automatically regenerated and rotated as needed.
2634 Implements part of ticket 12498.
2635 - Directory authorities now vote on Ed25519 identity keys along with
2636 RSA1024 keys. Implements part of ticket 12498.
2637 - Directory authorities track which Ed25519 identity keys have been
2638 used with which RSA1024 identity keys, and do not allow them to
2639 vary freely. Implements part of ticket 12498.
2640 - Microdescriptors now include Ed25519 identity keys. Implements
2641 part of ticket 12498.
2642 - Add a --newpass option to allow changing or removing the
2643 passphrase of an encrypted key with tor --keygen. Implements part
2645 - Add a new OfflineMasterKey option to tell Tor never to try loading
2646 or generating a secret Ed25519 identity key. You can use this in
2647 combination with tor --keygen to manage offline and/or encrypted
2648 Ed25519 keys. Implements ticket 16944.
2649 - On receiving a HUP signal, check to see whether the Ed25519
2650 signing key has changed, and reload it if so. Closes ticket 16790.
2651 - Significant usability improvements for Ed25519 key management. Log
2652 messages are better, and the code can recover from far more
2653 failure conditions. Thanks to "s7r" for reporting and diagnosing
2656 o Major features (ECC performance):
2657 - Improve the runtime speed of Ed25519 signature verification by
2658 using Ed25519-donna's batch verification support. Implements
2660 - Improve the speed of Ed25519 operations and Curve25519 keypair
2661 generation when built targeting 32 bit x86 platforms with SSE2
2662 available. Implements ticket 16535.
2663 - Improve the runtime speed of Ed25519 operations by using the
2664 public-domain Ed25519-donna by Andrew M. ("floodyberry").
2665 Implements ticket 16467.
2666 - Improve the runtime speed of the ntor handshake by using an
2667 optimized curve25519 basepoint scalarmult implementation from the
2668 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
2669 ideas by Adam Langley. Implements ticket 9663.
2671 o Major features (Hidden services):
2672 - Hidden services, if using the EntryNodes option, are required to
2673 use more than one EntryNode, in order to avoid a guard discovery
2674 attack. (This would only affect people who had configured hidden
2675 services and manually specified the EntryNodes option with a
2676 single entry-node. The impact was that it would be easy to
2677 remotely identify the guard node used by such a hidden service.
2678 See ticket for more information.) Fixes ticket 14917.
2679 - Add the torrc option HiddenServiceNumIntroductionPoints, to
2680 specify a fixed number of introduction points. Its maximum value
2681 is 10 and default is 3. Using this option can increase a hidden
2682 service's reliability under load, at the cost of making it more
2683 visible that the hidden service is facing extra load. Closes
2685 - Remove the adaptive algorithm for choosing the number of
2686 introduction points, which used to change the number of
2687 introduction points (poorly) depending on the number of
2688 connections the HS sees. Closes ticket 4862.
2690 o Major features (onion key cross-certification):
2691 - Relay descriptors now include signatures of their own identity
2692 keys, made using the TAP and ntor onion keys. These signatures
2693 allow relays to prove ownership of their own onion keys. Because
2694 of this change, microdescriptors will no longer need to include
2695 RSA identity keys. Implements proposal 228; closes ticket 12499.
2697 o Major bugfixes (client-side privacy, also in 0.2.6.9):
2698 - Properly separate out each SOCKSPort when applying stream
2699 isolation. The error occurred because each port's session group
2700 was being overwritten by a default value when the listener
2701 connection was initialized. Fixes bug 16247; bugfix on
2702 0.2.6.3-alpha. Patch by "jojelino".
2704 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
2705 - Stop refusing to store updated hidden service descriptors on a
2706 client. This reverts commit 9407040c59218 (which indeed fixed bug
2707 14219, but introduced a major hidden service reachability
2708 regression detailed in bug 16381). This is a temporary fix since
2709 we can live with the minor issue in bug 14219 (it just results in
2710 some load on the network) but the regression of 16381 is too much
2711 of a setback. First-round fix for bug 16381; bugfix
2714 o Major bugfixes (hidden services):
2715 - Revert commit that made directory authorities assign the HSDir
2716 flag to relay without a DirPort; this was bad because such relays
2717 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
2719 - When cannibalizing a circuit for an introduction point, always
2720 extend to the chosen exit node (creating a 4 hop circuit).
2721 Previously Tor would use the current circuit exit node, which
2722 changed the original choice of introduction point, and could cause
2723 the hidden service to skip excluded introduction points or
2724 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
2727 o Major bugfixes (memory leaks):
2728 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
2729 17398; bugfix on 0.2.6.1-alpha.
2731 o Major bugfixes (open file limit):
2732 - The open file limit wasn't checked before calling
2733 tor_accept_socket_nonblocking(), which would make Tor exceed the
2734 limit. Now, before opening a new socket, Tor validates the open
2735 file limit just before, and if the max has been reached, return an
2736 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
2738 o Major bugfixes (security, correctness):
2739 - Fix an error that could cause us to read 4 bytes before the
2740 beginning of an openssl string. This bug could be used to cause
2741 Tor to crash on systems with unusual malloc implementations, or
2742 systems with unusual hardening installed. Fixes bug 17404; bugfix
2745 o Major bugfixes (stability, also in 0.2.6.10):
2746 - Stop crashing with an assertion failure when parsing certain kinds
2747 of malformed or truncated microdescriptors. Fixes bug 16400;
2748 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
2749 by "cypherpunks_backup".
2750 - Stop random client-side assertion failures that could occur when
2751 connecting to a busy hidden service, or connecting to a hidden
2752 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
2755 o Minor features (client, SOCKS):
2756 - Add GroupWritable and WorldWritable options to unix-socket based
2757 SocksPort and ControlPort options. These options apply to a single
2758 socket, and override {Control,Socks}SocketsGroupWritable. Closes
2760 - Relax the validation done to hostnames in SOCKS5 requests, and
2761 allow a single trailing '.' to cope with clients that pass FQDNs
2762 using that syntax to explicitly indicate that the domain name is
2763 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
2764 - Relax the validation of hostnames in SOCKS5 requests, allowing the
2765 character '_' to appear, in order to cope with domains observed in
2766 the wild that are serving non-RFC compliant records. Resolves
2769 o Minor features (client-side privacy):
2770 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
2771 lifespan when IsolateSOCKSAuth and streams with SOCKS
2772 authentication are attached to the circuit. This allows
2773 applications like TorBrowser to manage circuit lifetime on their
2774 own. Implements feature 15482.
2775 - When logging malformed hostnames from SOCKS5 requests, respect
2776 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
2778 o Minor features (clock-jump tolerance):
2779 - Recover better when our clock jumps back many hours, like might
2780 happen for Tails or Whonix users who start with a very wrong
2781 hardware clock, use Tor to discover a more accurate time, and then
2782 fix their clock. Resolves part of ticket 8766.
2784 o Minor features (command-line interface):
2785 - Make --hash-password imply --hush to prevent unnecessary noise.
2786 Closes ticket 15542. Patch from "cypherpunks".
2787 - Print a warning whenever we find a relative file path being used
2788 as torrc option. Resolves issue 14018.
2790 o Minor features (compilation):
2791 - Give a warning as early as possible when trying to build with an
2792 unsupported OpenSSL version. Closes ticket 16901.
2793 - Use C99 variadic macros when the compiler is not GCC. This avoids
2794 failing compilations on MSVC, and fixes a log-file-based race
2795 condition in our old workarounds. Original patch from Gisle Vanem.
2797 o Minor features (control protocol):
2798 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
2799 the control protocol. Resolves ticket 15358.
2801 o Minor features (controller):
2802 - Add DirAuthority lines for default directory authorities to the
2803 output of the "GETINFO config/defaults" command if not already
2804 present. Implements ticket 14840.
2805 - Controllers can now use "GETINFO hs/client/desc/id/..." to
2806 retrieve items from the client's hidden service descriptor cache.
2807 Closes ticket 14845.
2808 - Implement a new controller command "GETINFO status/fresh-relay-
2809 descs" to fetch a descriptor/extrainfo pair that was generated on
2810 demand just for the controller's use. Implements ticket 14784.
2812 o Minor features (directory authorities):
2813 - Directory authorities no longer vote against the "Fast", "Stable",
2814 and "HSDir" flags just because they were going to vote against
2815 "Running": if the consensus turns out to be that the router was
2816 running, then the authority's vote should count. Patch from Peter
2817 Retzlaff; closes issue 8712.
2819 o Minor features (directory authorities, security, also in 0.2.6.9):
2820 - The HSDir flag given by authorities now requires the Stable flag.
2821 For the current network, this results in going from 2887 to 2806
2822 HSDirs. Also, it makes it harder for an attacker to launch a sybil
2823 attack by raising the effort for a relay to become Stable to
2824 require at the very least 7 days, while maintaining the 96 hours
2825 uptime requirement for HSDir. Implements ticket 8243.
2827 o Minor features (DoS-resistance):
2828 - Make it harder for attackers to overload hidden services with
2829 introductions, by blocking multiple introduction requests on the
2830 same circuit. Resolves ticket 15515.
2832 o Minor features (geoip):
2833 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
2836 o Minor features (hidden services):
2837 - Add the new options "HiddenServiceMaxStreams" and
2838 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
2839 limit the maximum number of simultaneous streams per circuit, and
2840 optionally tear down the circuit when the limit is exceeded. Part
2842 - Client now uses an introduction point failure cache to know when
2843 to fetch or keep a descriptor in their cache. Previously, failures
2844 were recorded implicitly, but not explicitly remembered. Closes
2846 - Relays need to have the Fast flag to get the HSDir flag. As this
2847 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
2848 drop. This change should make some attacks against the hidden
2849 service directory system harder. Fixes ticket 15963.
2850 - Turn on hidden service statistics collection by setting the torrc
2851 option HiddenServiceStatistics to "1" by default. (This keeps
2852 track only of the fraction of traffic used by hidden services, and
2853 the total number of hidden services in existence.) Closes
2855 - To avoid leaking HS popularity, don't cycle the introduction point
2856 when we've handled a fixed number of INTRODUCE2 cells but instead
2857 cycle it when a random number of introductions is reached, thus
2858 making it more difficult for an attacker to find out the amount of
2859 clients that have used the introduction point for a specific HS.
2860 Closes ticket 15745.
2862 o Minor features (logging):
2863 - Include the Tor version in all LD_BUG log messages, since people
2864 tend to cut and paste those into the bugtracker. Implements
2867 o Minor features (pluggable transports):
2868 - When launching managed pluggable transports on Linux systems,
2869 attempt to have the kernel deliver a SIGTERM on tor exit if the
2870 pluggable transport process is still running. Resolves
2872 - When launching managed pluggable transports, setup a valid open
2873 stdin in the child process that can be used to detect if tor has
2874 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
2875 can be used by implementations to detect this new behavior.
2876 Resolves ticket 15435.
2878 o Minor bugfixes (torrc exit policies):
2879 - In each instance above, usage advice is provided to avoid the
2880 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
2881 16069; bugfix on 0.2.4.7-alpha.
2882 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
2883 produce IPv6 wildcard addresses. Previously they would produce
2884 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
2885 of bug 16069; bugfix on 0.2.4.7-alpha.
2886 - When parsing torrc ExitPolicies, we now issue an info-level
2887 message when expanding an "accept/reject *" line to include both
2888 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
2889 - When parsing torrc ExitPolicies, we now warn for a number of cases
2890 where the user's intent is likely to differ from Tor's actual
2891 behavior. These include: using an IPv4 address with an accept6 or
2892 reject6 line; using "private" on an accept6 or reject6 line; and
2893 including any ExitPolicy lines after accept *:* or reject *:*.
2894 Related to ticket 16069.
2896 o Minor bugfixes (command-line interface):
2897 - When "--quiet" is provided along with "--validate-config", do not
2898 write anything to stdout on success. Fixes bug 14994; bugfix
2900 - When complaining about bad arguments to "--dump-config", use
2902 - Print usage information for --dump-config when it is used without
2903 an argument. Also, fix the error message to use different wording
2904 and add newline at the end. Fixes bug 15541; bugfix
2907 o Minor bugfixes (compilation):
2908 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
2909 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
2910 - Repair compilation with the most recent (unreleased, alpha)
2911 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
2913 o Minor bugfixes (compilation, also in 0.2.6.9):
2914 - Build with --enable-systemd correctly when libsystemd is
2915 installed, but systemd is not. Fixes bug 16164; bugfix on
2916 0.2.6.3-alpha. Patch from Peter Palfrader.
2918 o Minor bugfixes (configuration, unit tests):
2919 - Only add the default fallback directories when the DirAuthorities,
2920 AlternateDirAuthority, and FallbackDir directory config options
2921 are set to their defaults. The default fallback directory list is
2922 currently empty, this fix will only change tor's behavior when it
2923 has default fallback directories. Includes unit tests for
2924 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
2925 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
2927 o Minor bugfixes (controller):
2928 - Add the descriptor ID in each HS_DESC control event. It was
2929 missing, but specified in control-spec.txt. Fixes bug 15881;
2930 bugfix on 0.2.5.2-alpha.
2932 o Minor bugfixes (correctness):
2933 - For correctness, avoid modifying a constant string in
2934 handle_control_postdescriptor. Fixes bug 15546; bugfix
2936 - Remove side-effects from tor_assert() calls. This was harmless,
2937 because we never disable assertions, but it is bad style and
2938 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
2940 - When calling channel_free_list(), avoid calling smartlist_remove()
2941 while inside a FOREACH loop. This partially reverts commit
2942 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
2943 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
2945 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
2946 - Check for failures from crypto_early_init, and refuse to continue.
2947 A previous typo meant that we could keep going with an
2948 uninitialized crypto library, and would have OpenSSL initialize
2949 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
2950 when implementing ticket 4900. Patch by "teor".
2952 o Minor bugfixes (hidden service):
2953 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
2954 a client authorized hidden service. Fixes bug 15823; bugfix
2956 - Remove an extraneous newline character from the end of hidden
2957 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
2959 o Minor bugfixes (Linux seccomp2 sandbox):
2960 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
2961 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
2962 - Allow bridge authorities to run correctly under the seccomp2
2963 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
2964 - Add the "hidserv-stats" filename to our sandbox filter for the
2965 HiddenServiceStatistics option to work properly. Fixes bug 17354;
2966 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
2968 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
2969 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
2970 these when eventfd2() support is missing. Fixes bug 16363; bugfix
2971 on 0.2.6.3-alpha. Patch from "teor".
2973 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
2974 - Allow systemd connections to work with the Linux seccomp2 sandbox
2975 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
2977 - Fix sandboxing to work when running as a relay, by allowing the
2978 renaming of secret_id_key, and allowing the eventfd2 and futex
2979 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
2982 o Minor bugfixes (logging):
2983 - When building Tor under Clang, do not include an extra set of
2984 parentheses in log messages that include function names. Fixes bug
2985 15269; bugfix on every released version of Tor when compiled with
2986 recent enough Clang.
2988 o Minor bugfixes (network):
2989 - When attempting to use fallback technique for network interface
2990 lookup, disregard loopback and multicast addresses since they are
2991 unsuitable for public communications.
2993 o Minor bugfixes (open file limit):
2994 - Fix set_max_file_descriptors() to set by default the max open file
2995 limit to the current limit when setrlimit() fails. Fixes bug
2996 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
2998 o Minor bugfixes (portability):
2999 - Check correctly for Windows socket errors in the workqueue
3000 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
3001 - Try harder to normalize the exit status of the Tor process to the
3002 standard-provided range. Fixes bug 16975; bugfix on every version
3004 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes part
3005 of bug 17151; bugfix on 0.2.5.2-alpha. Patch from Marcin Cieślak.
3007 o Minor bugfixes (relay):
3008 - Ensure that worker threads actually exit when a fatal error or
3009 shutdown is indicated. This fix doesn't currently affect the
3010 behavior of Tor, because Tor workers never indicates fatal error
3011 or shutdown except in the unit tests. Fixes bug 16868; bugfix
3013 - Fix a rarely-encountered memory leak when failing to initialize
3014 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
3016 - Unblock threads before releasing the work queue mutex to ensure
3017 predictable scheduling behavior. Fixes bug 16644; bugfix
3020 o Minor bugfixes (security, exit policies):
3021 - ExitPolicyRejectPrivate now also rejects the relay's published
3022 IPv6 address (if any), and any publicly routable IPv4 or IPv6
3023 addresses on any local interfaces. ticket 17027. Patch by "teor".
3024 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
3026 o Minor bugfixes (statistics):
3027 - Disregard the ConnDirectionStatistics torrc options when Tor is
3028 not a relay since in that mode of operation no sensible data is
3029 being collected and because Tor might run into measurement hiccups
3030 when running as a client for some time, then becoming a relay.
3031 Fixes bug 15604; bugfix on 0.2.2.35.
3033 o Minor bugfixes (systemd):
3034 - Tor's systemd unit file no longer contains extraneous spaces.
3035 These spaces would sometimes confuse tools like deb-systemd-
3036 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
3038 o Minor bugfixes (test networks):
3039 - When self-testing reachability, use ExtendAllowPrivateAddresses to
3040 determine if local/private addresses imply reachability. The
3041 previous fix used TestingTorNetwork, which implies
3042 ExtendAllowPrivateAddresses, but this excluded rare configurations
3043 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
3044 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
3045 issue discovered by CJ Ess.
3047 o Minor bugfixes (tests, also in 0.2.6.9):
3048 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
3049 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
3051 o Code simplification and refactoring:
3052 - Change the function that's called when we need to retry all
3053 downloads so that it only reschedules the downloads to happen
3054 immediately, rather than launching them all at once itself. This
3055 further simplifies Tor's callgraph.
3056 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
3057 to ensure they remain consistent and visible everywhere.
3058 - Move some format-parsing functions out of crypto.c and
3059 crypto_curve25519.c into crypto_format.c and/or util_format.c.
3060 - Move the client-only parts of init_keys() into a separate
3061 function. Closes ticket 16763.
3062 - Move the hacky fallback code out of get_interface_address6() into
3063 separate function and get it covered with unit-tests. Resolves
3065 - Refactor hidden service client-side cache lookup to intelligently
3066 report its various failure cases, and disentangle failure cases
3067 involving a lack of introduction points. Closes ticket 14391.
3068 - Remove some vestigial workarounds for the MSVC6 compiler. We
3069 haven't supported that in ages.
3070 - Remove the unused "nulterminate" argument from buf_pullup().
3071 - Simplify the microdesc_free() implementation so that it no longer
3072 appears (to code analysis tools) to potentially invoke a huge
3073 suite of other microdesc functions.
3074 - Simply the control graph further by deferring the inner body of
3075 directory_all_unreachable() into a callback. Closes ticket 16762.
3076 - The link authentication code has been refactored for better
3077 testability and reliability. It now uses code generated with the
3078 "trunnel" binary encoding generator, to reduce the risk of bugs
3079 due to programmer error. Done as part of ticket 12498.
3080 - Treat the loss of an owning controller as equivalent to a SIGTERM
3081 signal. This removes a tiny amount of duplicated code, and
3082 simplifies our callgraph. Closes ticket 16788.
3083 - Use our own Base64 encoder instead of OpenSSL's, to allow more
3084 control over the output. Part of ticket 15652.
3085 - When generating an event to send to the controller, we no longer
3086 put the event over the network immediately. Instead, we queue
3087 these events, and use a Libevent callback to deliver them. This
3088 change simplifies Tor's callgraph by reducing the number of
3089 functions from which all other Tor functions are reachable. Closes
3091 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
3092 that try to scan or compile every file on Unix won't decide that
3096 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
3097 - Improve the descriptions of statistics-related torrc options in
3098 the manpage to describe rationale and possible uses cases. Fixes
3100 - Improve the layout and formatting of ./configure --help messages.
3101 Closes ticket 15024. Patch from "cypherpunks".
3102 - Include a specific and (hopefully) accurate documentation of the
3103 torrc file's meta-format in doc/torrc_format.txt. This is mainly
3104 of interest to people writing programs to parse or generate torrc
3105 files. This document is not a commitment to long-term
3106 compatibility; some aspects of the current format are a bit
3107 ridiculous. Closes ticket 2325.
3108 - Include the TUNING document in our source tarball. It is referred
3109 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
3111 - Note that HiddenServicePorts can take a unix domain socket. Closes
3113 - Recommend a 40 GB example AccountingMax in torrc.sample rather
3114 than a 4 GB max. Closes ticket 16742.
3115 - Standardize on the term "server descriptor" in the manual page.
3116 Previously, we had used "router descriptor", "server descriptor",
3117 and "relay descriptor" interchangeably. Part of ticket 14987.
3118 - Advise users on how to configure separate IPv4 and IPv6 exit
3119 policies in the manpage and sample torrcs. Related to ticket 16069.
3120 - Fix an error in the manual page and comments for
3121 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
3122 required "ORPort connectivity". While this is true, it is in no
3123 way unique to the HSDir flag. Of all the flags, only HSDirs need a
3124 DirPort configured in order for the authorities to assign that
3125 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
3127 - Fix the usage message of tor-resolve(1) so that it no longer lists
3128 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
3131 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
3132 and always use the internal Base64 decoder. The internal decoder
3133 has been part of tor since 0.2.0.10-alpha, and no one should
3134 be using the OpenSSL one. Part of ticket 15652.
3135 - Remove the 'tor_strclear()' function; use memwipe() instead.
3136 Closes ticket 14922.
3137 - Remove the code that would try to aggressively flush controller
3138 connections while writing to them. This code was introduced in
3139 0.1.2.7-alpha, in order to keep output buffers from exceeding
3140 their limits. But there is no longer a maximum output buffer size,
3141 and flushing data in this way caused some undesirable recursions
3142 in our call graph. Closes ticket 16480.
3143 - The internal pure-C tor-fw-helper tool is now removed from the Tor
3144 distribution, in favor of the pure-Go clone available from
3145 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
3146 used by the C tor-fw-helper are not, in our opinion, very
3147 confidence- inspiring in their secure-programming techniques.
3148 Closes ticket 13338.
3151 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
3152 fingerprinting we now recommend pluggable transports; for forward-
3153 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
3154 - Remove the HidServDirectoryV2 option. Now all relays offer to
3155 store hidden service descriptors. Related to 16543.
3156 - Remove the VoteOnHidServDirectoriesV2 option, since all
3157 authorities have long set it to 1. Closes ticket 16543.
3158 - Remove the undocumented "--digests" command-line option. It
3159 complicated our build process, caused subtle build issues on
3160 multiple platforms, and is now redundant since we started
3161 including git version identifiers. Closes ticket 14742.
3162 - Tor no longer contains checks for ancient directory cache versions
3163 that didn't know about microdescriptors.
3164 - Tor no longer contains workarounds for stat files generated by
3165 super-old versions of Tor that didn't choose guards sensibly.
3168 - The test-network.sh script now supports performance testing.
3169 Requires corresponding chutney performance testing changes. Patch
3170 by "teor". Closes ticket 14175.
3171 - Add a new set of callgraph analysis scripts that use clang to
3172 produce a list of which Tor functions are reachable from which
3173 other Tor functions. We're planning to use these to help simplify
3174 our code structure by identifying illogical dependencies.
3175 - Add new 'test-full' and 'test-full-online' targets to run all
3176 tests, including integration tests with stem and chutney.
3177 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
3178 by-side in the same parent directory. Closes ticket 16903. Patch
3180 - Document use of coverity, clang static analyzer, and clang dynamic
3181 undefined behavior and address sanitizers in doc/HACKING. Include
3182 detailed usage instructions in the blacklist. Patch by "teor".
3183 Closes ticket 15817.
3184 - Make "bridges+hs" the default test network. This tests almost all
3185 tor functionality during make test-network, while allowing tests
3186 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
3187 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
3188 (chutney). Patches by "teor".
3189 - Make the test-workqueue test work on Windows by initializing the
3190 network before we begin.
3191 - New make target (make test-network-all) to run multiple applicable
3192 chutney test cases. Patch from Teor; closes 16953.
3193 - Now that OpenSSL has its own scrypt implementation, add an unit
3194 test that checks for interoperability between libscrypt_scrypt()
3195 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
3196 and rely on EVP_PBE_scrypt() whenever possible. Resolves
3198 - The link authentication protocol code now has extensive tests.
3199 - The relay descriptor signature testing code now has
3201 - The test_workqueue program now runs faster, and is enabled by
3202 default as a part of "make check".
3203 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
3204 functions in dns.c. Implements a portion of ticket 16831.
3205 - Use environment variables rather than autoconf substitutions to
3206 send variables from the build system to the test scripts. This
3207 change should be easier to maintain, and cause 'make distcheck' to
3208 work better than before. Fixes bug 17148.
3209 - When building Tor with testing coverage enabled, run Chutney tests
3210 (if any) using the 'tor-cov' coverage binary.
3211 - When running test-network or test-stem, check for the absence of
3212 stem/chutney before doing any build operations.
3213 - Add a test to verify that the compiler does not eliminate our
3214 memwipe() implementation. Closes ticket 15377.
3215 - Add make rule `check-changes` to verify the format of changes
3216 files. Closes ticket 15180.
3217 - Add unit tests for control_event_is_interesting(). Add a compile-
3218 time check that the number of events doesn't exceed the capacity
3219 of control_event_t.event_mask. Closes ticket 15431, checks for
3220 bugs similar to 13085. Patch by "teor".
3221 - Command-line argument tests moved to Stem. Resolves ticket 14806.
3222 - Integrate the ntor, backtrace, and zero-length keys tests into the
3223 automake test suite. Closes ticket 15344.
3224 - Remove assertions during builds to determine Tor's test coverage.
3225 We don't want to trigger these even in assertions, so including
3226 them artificially makes our branch coverage look worse than it is.
3227 This patch provides the new test-stem-full and coverage-html-full
3228 configure options. Implements ticket 15400.
3229 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
3230 explicitly manage consensus flags in testing networks. Patch by
3231 "robgjansen", modified by "teor". Implements part of ticket 14882.
3232 - Check for matching value in server response in ntor_ref.py. Fixes
3233 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
3235 - Set the severity correctly when testing
3236 get_interface_addresses_ifaddrs() and
3237 get_interface_addresses_win32(), so that the tests fail gracefully
3238 instead of triggering an assertion. Fixes bug 15759; bugfix on
3239 0.2.6.3-alpha. Reported by Nicolas Derive.
3241 Changes in version 0.2.6.10 - 2015-07-12
3242 Tor version 0.2.6.10 fixes some significant stability and hidden
3243 service client bugs, bulletproofs the cryptography init process, and
3244 fixes a bug when using the sandbox code with some older versions of
3245 Linux. Everyone running an older version, especially an older version
3246 of 0.2.6, should upgrade.
3248 o Major bugfixes (hidden service clients, stability):
3249 - Stop refusing to store updated hidden service descriptors on a
3250 client. This reverts commit 9407040c59218 (which indeed fixed bug
3251 14219, but introduced a major hidden service reachability
3252 regression detailed in bug 16381). This is a temporary fix since
3253 we can live with the minor issue in bug 14219 (it just results in
3254 some load on the network) but the regression of 16381 is too much
3255 of a setback. First-round fix for bug 16381; bugfix
3258 o Major bugfixes (stability):
3259 - Stop crashing with an assertion failure when parsing certain kinds
3260 of malformed or truncated microdescriptors. Fixes bug 16400;
3261 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
3262 by "cypherpunks_backup".
3263 - Stop random client-side assertion failures that could occur when
3264 connecting to a busy hidden service, or connecting to a hidden
3265 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
3268 o Minor features (geoip):
3269 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
3270 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
3272 o Minor bugfixes (crypto error-handling):
3273 - Check for failures from crypto_early_init, and refuse to continue.
3274 A previous typo meant that we could keep going with an
3275 uninitialized crypto library, and would have OpenSSL initialize
3276 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
3277 when implementing ticket 4900. Patch by "teor".
3279 o Minor bugfixes (Linux seccomp2 sandbox):
3280 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
3281 these when eventfd2() support is missing. Fixes bug 16363; bugfix
3282 on 0.2.6.3-alpha. Patch from "teor".
3285 Changes in version 0.2.6.9 - 2015-06-11
3286 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
3287 requirements for receiving an HSDir flag, and addresses some other small
3288 bugs in the systemd and sandbox code. Clients using circuit isolation
3289 should upgrade; all directory authorities should upgrade.
3291 o Major bugfixes (client-side privacy):
3292 - Properly separate out each SOCKSPort when applying stream
3293 isolation. The error occurred because each port's session group was
3294 being overwritten by a default value when the listener connection
3295 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
3298 o Minor feature (directory authorities, security):
3299 - The HSDir flag given by authorities now requires the Stable flag.
3300 For the current network, this results in going from 2887 to 2806
3301 HSDirs. Also, it makes it harder for an attacker to launch a sybil
3302 attack by raising the effort for a relay to become Stable which
3303 takes at the very least 7 days to do so and by keeping the 96
3304 hours uptime requirement for HSDir. Implements ticket 8243.
3306 o Minor bugfixes (compilation):
3307 - Build with --enable-systemd correctly when libsystemd is
3308 installed, but systemd is not. Fixes bug 16164; bugfix on
3309 0.2.6.3-alpha. Patch from Peter Palfrader.
3311 o Minor bugfixes (Linux seccomp2 sandbox):
3312 - Fix sandboxing to work when running as a relaymby renaming of
3313 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
3314 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
3315 - Allow systemd connections to work with the Linux seccomp2 sandbox
3316 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
3319 o Minor bugfixes (tests):
3320 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
3321 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
3324 Changes in version 0.2.6.8 - 2015-05-21
3325 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
3326 fixes an authority-side bug in assigning the HSDir flag. All directory
3327 authorities should upgrade.
3329 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
3330 - Revert commit that made directory authorities assign the HSDir
3331 flag to relay without a DirPort; this was bad because such relays
3332 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
3335 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
3336 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
3337 a client authorized hidden service. Fixes bug 15823; bugfix
3340 o Minor features (geoip):
3341 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
3342 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
3346 Changes in version 0.2.6.7 - 2015-04-06
3347 Tor 0.2.6.7 fixes two security issues that could be used by an
3348 attacker to crash hidden services, or crash clients visiting hidden
3349 services. Hidden services should upgrade as soon as possible; clients
3350 should upgrade whenever packages become available.
3352 This release also contains two simple improvements to make hidden
3353 services a bit less vulnerable to denial-of-service attacks.
3355 o Major bugfixes (security, hidden service):
3356 - Fix an issue that would allow a malicious client to trigger an
3357 assertion failure and halt a hidden service. Fixes bug 15600;
3358 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
3359 - Fix a bug that could cause a client to crash with an assertion
3360 failure when parsing a malformed hidden service descriptor. Fixes
3361 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
3363 o Minor features (DoS-resistance, hidden service):
3364 - Introduction points no longer allow multiple INTRODUCE1 cells to
3365 arrive on the same circuit. This should make it more expensive for
3366 attackers to overwhelm hidden services with introductions.
3367 Resolves ticket 15515.
3368 - Decrease the amount of reattempts that a hidden service performs
3369 when its rendezvous circuits fail. This reduces the computational
3370 cost for running a hidden service under heavy load. Resolves
3374 Changes in version 0.2.5.12 - 2015-04-06
3375 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
3376 could be used by an attacker to crash hidden services, or crash clients
3377 visiting hidden services. Hidden services should upgrade as soon as
3378 possible; clients should upgrade whenever packages become available.
3380 This release also backports a simple improvement to make hidden
3381 services a bit less vulnerable to denial-of-service attacks.
3383 o Major bugfixes (security, hidden service):
3384 - Fix an issue that would allow a malicious client to trigger an
3385 assertion failure and halt a hidden service. Fixes bug 15600;
3386 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
3387 - Fix a bug that could cause a client to crash with an assertion
3388 failure when parsing a malformed hidden service descriptor. Fixes
3389 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
3391 o Minor features (DoS-resistance, hidden service):
3392 - Introduction points no longer allow multiple INTRODUCE1 cells to
3393 arrive on the same circuit. This should make it more expensive for
3394 attackers to overwhelm hidden services with introductions.
3395 Resolves ticket 15515.
3398 Changes in version 0.2.4.27 - 2015-04-06
3399 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
3400 could be used by an attacker to crash hidden services, or crash clients
3401 visiting hidden services. Hidden services should upgrade as soon as
3402 possible; clients should upgrade whenever packages become available.
3404 This release also backports a simple improvement to make hidden
3405 services a bit less vulnerable to denial-of-service attacks.
3407 o Major bugfixes (security, hidden service):
3408 - Fix an issue that would allow a malicious client to trigger an
3409 assertion failure and halt a hidden service. Fixes bug 15600;
3410 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
3411 - Fix a bug that could cause a client to crash with an assertion
3412 failure when parsing a malformed hidden service descriptor. Fixes
3413 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
3415 o Minor features (DoS-resistance, hidden service):
3416 - Introduction points no longer allow multiple INTRODUCE1 cells to
3417 arrive on the same circuit. This should make it more expensive for
3418 attackers to overwhelm hidden services with introductions.
3419 Resolves ticket 15515.
3422 Changes in version 0.2.6.6 - 2015-03-24
3423 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
3425 It adds numerous safety, security, correctness, and performance
3426 improvements. Client programs can be configured to use more kinds of
3427 sockets, AutomapHosts works better, the multithreading backend is
3428 improved, cell transmission is refactored, test coverage is much
3429 higher, more denial-of-service attacks are handled, guard selection is
3430 improved to handle long-term guards better, pluggable transports
3431 should work a bit better, and some annoying hidden service performance
3432 bugs should be addressed.
3434 o New compiler and system requirements:
3435 - Tor 0.2.6.x requires that your compiler support more of the C99
3436 language standard than before. The 'configure' script now detects
3437 whether your compiler supports C99 mid-block declarations and
3438 designated initializers. If it does not, Tor will not compile.
3440 We may revisit this requirement if it turns out that a significant
3441 number of people need to build Tor with compilers that don't
3442 bother implementing a 15-year-old standard. Closes ticket 13233.
3443 - Tor no longer supports systems without threading support. When we
3444 began working on Tor, there were several systems that didn't have
3445 threads, or where the thread support wasn't able to run the
3446 threads of a single process on multiple CPUs. That no longer
3447 holds: every system where Tor needs to run well now has threading
3448 support. Resolves ticket 12439.
3450 o Deprecated versions and removed support:
3451 - Tor relays older than 0.2.4.18-rc are no longer allowed to
3452 advertise themselves on the network. Closes ticket 13555.
3453 - Tor clients no longer support connecting to hidden services
3454 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
3455 option has been removed. (There shouldn't be any hidden services
3456 running these versions on the network.) Closes ticket 7803.
3458 o Directory authority changes:
3459 - The directory authority Faravahar has a new IP address. This
3460 closes ticket 14487.
3461 - Remove turtles as a directory authority.
3462 - Add longclaw as a new (v3) directory authority. This implements
3463 ticket 13296. This keeps the directory authority count at 9.
3465 o Major features (bridges):
3466 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
3467 transports if they are configured via the "TOR_PT_PROXY"
3468 environment variable. Implements proposal 232. Resolves
3471 o Major features (changed defaults):
3472 - Prevent relay operators from unintentionally running exits: When a
3473 relay is configured as an exit node, we now warn the user unless
3474 the "ExitRelay" option is set to 1. We warn even more loudly if
3475 the relay is configured with the default exit policy, since this
3476 can indicate accidental misconfiguration. Setting "ExitRelay 0"
3477 stops Tor from running as an exit relay. Closes ticket 10067.
3479 o Major features (client performance, hidden services):
3480 - Allow clients to use optimistic data when connecting to a hidden
3481 service, which should remove a round-trip from hidden service
3482 initialization. See proposal 181 for details. Implements
3485 o Major features (directory system):
3486 - Upon receiving an unparseable directory object, if its digest
3487 matches what we expected, then don't try to download it again.
3488 Previously, when we got a descriptor we didn't like, we would keep
3489 trying to download it over and over. Closes ticket 11243.
3490 - When downloading server- or microdescriptors from a directory
3491 server, we no longer launch multiple simultaneous requests to the
3492 same server. This reduces load on the directory servers,
3493 especially when directory guards are in use. Closes ticket 9969.
3494 - When downloading server- or microdescriptors over a tunneled
3495 connection, do not limit the length of our requests to what the
3496 Squid proxy is willing to handle. Part of ticket 9969.
3497 - Authorities can now vote on the correct digests and latest
3498 versions for different software packages. This allows packages
3499 that include Tor to use the Tor authority system as a way to get
3500 notified of updates and their correct digests. Implements proposal
3501 227. Closes ticket 10395.
3503 o Major features (guards):
3504 - Introduce the Guardfraction feature to improves load balancing on
3505 guard nodes. Specifically, it aims to reduce the traffic gap that
3506 guard nodes experience when they first get the Guard flag. This is
3507 a required step if we want to increase the guard lifetime to 9
3508 months or greater. Closes ticket 9321.
3510 o Major features (hidden services):
3511 - Make HS port scanning more difficult by immediately closing the
3512 circuit when a user attempts to connect to a nonexistent port.
3513 Closes ticket 13667.
3514 - Add a HiddenServiceStatistics option that allows Tor relays to
3515 gather and publish statistics about the overall size and volume of
3516 hidden service usage. Specifically, when this option is turned on,
3517 an HSDir will publish an approximate number of hidden services
3518 that have published descriptors to it the past 24 hours. Also, if
3519 a relay has acted as a hidden service rendezvous point, it will
3520 publish the approximate amount of rendezvous cells it has relayed
3521 the past 24 hours. The statistics themselves are obfuscated so
3522 that the exact values cannot be derived. For more details see
3523 proposal 238, "Better hidden service stats from Tor relays". This
3524 feature is currently disabled by default. Implements feature 13192.
3526 o Major features (performance):
3527 - Make the CPU worker implementation more efficient by avoiding the
3528 kernel and lengthening pipelines. The original implementation used
3529 sockets to transfer data from the main thread to the workers, and
3530 didn't allow any thread to be assigned more than a single piece of
3531 work at once. The new implementation avoids communications
3532 overhead by making requests in shared memory, avoiding kernel IO
3533 where possible, and keeping more requests in flight at once.
3534 Implements ticket 9682.
3536 o Major features (relay):
3537 - Raise the minimum acceptable configured bandwidth rate for bridges
3538 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
3539 20 KiB/sec.) Closes ticket 13822.
3540 - Complete revision of the code that relays use to decide which cell
3541 to send next. Formerly, we selected the best circuit to write on
3542 each channel, but we didn't select among channels in any
3543 sophisticated way. Now, we choose the best circuits globally from
3544 among those whose channels are ready to deliver traffic.
3546 This patch implements a new inter-cmux comparison API, a global
3547 high/low watermark mechanism and a global scheduler loop for
3548 transmission prioritization across all channels as well as among
3549 circuits on one channel. This schedule is currently tuned to
3550 (tolerantly) avoid making changes in network performance, but it
3551 should form the basis for major circuit performance increases in
3552 the future. Code by Andrea; tuning by Rob Jansen; implements
3555 o Major features (sample torrc):
3556 - Add a new, infrequently-changed "torrc.minimal". This file is
3557 similar to torrc.sample, but it will change as infrequently as
3558 possible, for the benefit of users whose systems prompt them for
3559 intervention whenever a default configuration file is changed.
3560 Making this change allows us to update torrc.sample to be a more
3561 generally useful "sample torrc".
3563 o Major features (security, unix domain sockets):
3564 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
3565 applications can reach Tor without having to create AF_INET or
3566 AF_INET6 sockets, meaning they can completely disable their
3567 ability to make non-Tor network connections. To create a socket of
3568 this type, use "SocksPort unix:/path/to/socket". Implements
3570 - Support mapping hidden service virtual ports to AF_UNIX sockets.
3571 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
3572 Implements ticket 11485.
3574 o Major bugfixes (client, automap):
3575 - Repair automapping with IPv6 addresses. This automapping should
3576 have worked previously, but one piece of debugging code that we
3577 inserted to detect a regression actually caused the regression to
3578 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
3579 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
3582 o Major bugfixes (crash, OSX, security):
3583 - Fix a remote denial-of-service opportunity caused by a bug in
3584 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
3587 o Major bugfixes (directory authorities):
3588 - Do not assign the HSDir flag to relays if they are not Valid, or
3589 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
3591 o Major bugfixes (directory bandwidth performance):
3592 - Don't flush the zlib buffer aggressively when compressing
3593 directory information for clients. This should save about 7% of
3594 the bandwidth currently used for compressed descriptors and
3595 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
3597 o Major bugfixes (exit node stability):
3598 - Fix an assertion failure that could occur under high DNS load.
3599 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
3600 diagnosed and fixed by "cypherpunks".
3602 o Major bugfixes (FreeBSD IPFW transparent proxy):
3603 - Fix address detection with FreeBSD transparent proxies, when
3604 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
3607 o Major bugfixes (hidden services):
3608 - When closing an introduction circuit that was opened in parallel
3609 with others, don't mark the introduction point as unreachable.
3610 Previously, the first successful connection to an introduction
3611 point would make the other introduction points get marked as
3612 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
3614 o Major bugfixes (Linux seccomp2 sandbox):
3615 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
3616 crash during attempts to call wait4. Fixes bug 15088; bugfix on
3617 0.2.5.1-alpha. Patch from "sanic".
3619 o Major bugfixes (mixed relay-client operation):
3620 - When running as a relay and client at the same time (not
3621 recommended), if we decide not to use a new guard because we want
3622 to retry older guards, only close the locally-originating circuits
3623 passing through that guard. Previously we would close all the
3624 circuits through that guard. Fixes bug 9819; bugfix on
3625 0.2.1.1-alpha. Reported by "skruffy".
3627 o Major bugfixes (pluggable transports):
3628 - Initialize the extended OR Port authentication cookie before
3629 launching pluggable transports. This prevents a race condition
3630 that occured when server-side pluggable transports would cache the
3631 authentication cookie before it has been (re)generated. Fixes bug
3632 15240; bugfix on 0.2.5.1-alpha.
3634 o Major bugfixes (relay, stability, possible security):
3635 - Fix a bug that could lead to a relay crashing with an assertion
3636 failure if a buffer of exactly the wrong layout is passed to
3637 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
3638 0.2.0.10-alpha. Patch from "cypherpunks".
3639 - Do not assert if the 'data' pointer on a buffer is advanced to the
3640 very end of the buffer; log a BUG message instead. Only assert if
3641 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
3643 o Minor features (build):
3644 - New --disable-system-torrc compile-time option to prevent Tor from
3645 looking for the system-wide torrc or torrc-defaults files.
3646 Resolves ticket 13037.
3648 o Minor features (client):
3649 - Clients are now willing to send optimistic data (before they
3650 receive a 'connected' cell) to relays of any version. (Relays
3651 without support for optimistic data are no longer supported on the
3652 Tor network.) Resolves ticket 13153.
3654 o Minor features (client):
3655 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
3656 is enabled, reject requests with IP addresses as hostnames.
3657 Resolves ticket 13315.
3659 o Minor features (controller):
3660 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
3661 write an unscheduled heartbeat message to the log. Implements
3663 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
3664 events so controllers can observe circuit isolation inputs. Closes
3666 - ControlPort now supports the unix:/path/to/socket syntax as an
3667 alternative to the ControlSocket option, for consistency with
3668 SocksPort and HiddenServicePort. Closes ticket 14451.
3669 - New "GETINFO bw-event-cache" to get information about recent
3670 bandwidth events. Closes ticket 14128. Useful for controllers to
3671 get recent bandwidth history after the fix for ticket 13988.
3672 - Messages about problems in the bootstrap process now include
3673 information about the server we were trying to connect to when we
3674 noticed the problem. Closes ticket 15006.
3676 o Minor features (Denial of service resistance):
3677 - Count the total number of bytes used storing hidden service
3678 descriptors against the value of MaxMemInQueues. If we're low on
3679 memory, and more than 20% of our memory is used holding hidden
3680 service descriptors, free them until no more than 10% of our
3681 memory holds hidden service descriptors. Free the least recently
3682 fetched descriptors first. Resolves ticket 13806.
3683 - When we have recently been under memory pressure (over 3/4 of
3684 MaxMemInQueues is allocated), then allocate smaller zlib objects
3685 for small requests. Closes ticket 11791.
3687 o Minor features (directory authorities):
3688 - Don't list relays with a bandwidth estimate of 0 in the consensus.
3689 Implements a feature proposed during discussion of bug 13000.
3690 - In tor-gencert, report an error if the user provides the same
3691 argument more than once.
3692 - If a directory authority can't find a best consensus method in the
3693 votes that it holds, it now falls back to its favorite consensus
3694 method. Previously, it fell back to method 1. Neither of these is
3695 likely to get enough signatures, but "fall back to favorite"
3696 doesn't require us to maintain support an obsolete consensus
3697 method. Implements part of proposal 215.
3699 o Minor features (geoip):
3700 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
3701 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
3704 o Minor features (guard nodes):
3705 - Reduce the time delay before saving guard status to disk from 10
3706 minutes to 30 seconds (or from one hour to 10 minutes if
3707 AvoidDiskWrites is set). Closes ticket 12485.
3709 o Minor features (heartbeat):
3710 - On relays, report how many connections we negotiated using each
3711 version of the Tor link protocols. This information will let us
3712 know if removing support for very old versions of the Tor
3713 protocols is harming the network. Closes ticket 15212.
3715 o Minor features (hidden service):
3716 - Make Sybil attacks against hidden services harder by changing the
3717 minimum time required to get the HSDir flag from 25 hours up to 96
3718 hours. Addresses ticket 14149.
3719 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
3720 services to disable the anti-scanning feature introduced in
3721 0.2.6.2-alpha. With this option not set, a connection to an
3722 unlisted port closes the circuit. With this option set, only a
3723 RELAY_DONE cell is sent. Closes ticket 14084.
3724 - When re-enabling the network, don't try to build introduction
3725 circuits until we have successfully built a circuit. This makes
3726 hidden services come up faster when the network is re-enabled.
3727 Patch from "akwizgran". Closes ticket 13447.
3728 - When we fail to retrieve a hidden service descriptor, send the
3729 controller an "HS_DESC FAILED" controller event. Implements
3731 - New HiddenServiceDirGroupReadable option to cause hidden service
3732 directories and hostname files to be created group-readable. Patch
3733 from "anon", David Stainton, and "meejah". Closes ticket 11291.
3735 o Minor features (interface):
3736 - Implement "-f -" command-line option to read torrc configuration
3737 from standard input, if you don't want to store the torrc file in
3738 the file system. Implements feature 13865.
3740 o Minor features (logging):
3741 - Add a count of unique clients to the bridge heartbeat message.
3742 Resolves ticket 6852.
3743 - Suppress "router info incompatible with extra info" message when
3744 reading extrainfo documents from cache. (This message got loud
3745 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
3747 - Elevate hidden service authorized-client message from DEBUG to
3748 INFO. Closes ticket 14015.
3749 - On Unix-like systems, you can now use named pipes as the target of
3750 the Log option, and other options that try to append to files.
3751 Closes ticket 12061. Patch from "carlo von lynX".
3752 - When opening a log file at startup, send it every log message that
3753 we generated between startup and opening it. Previously, log
3754 messages that were generated before opening the log file were only
3755 logged to stdout. Closes ticket 6938.
3756 - Add a TruncateLogFile option to overwrite logs instead of
3757 appending to them. Closes ticket 5583.
3758 - Quiet some log messages in the heartbeat and at startup. Closes
3761 o Minor features (portability, Solaris):
3762 - Threads are no longer disabled by default on Solaris; we believe
3763 that the versions of Solaris with broken threading support are all
3764 obsolete by now. Resolves ticket 9495.
3766 o Minor features (relay):
3767 - Re-check our address after we detect a changed IP address from
3768 getsockname(). This ensures that the controller command "GETINFO
3769 address" will report the correct value. Resolves ticket 11582.
3771 - A new AccountingRule option lets Relays set whether they'd like
3772 AccountingMax to be applied separately to inbound and outbound
3773 traffic, or applied to the sum of inbound and outbound traffic.
3774 Resolves ticket 961. Patch by "chobe".
3775 - When identity keypair is generated for first time, log a
3776 congratulatory message that links to the new relay lifecycle
3777 document. Implements feature 10427.
3779 o Minor features (security, memory wiping):
3780 - Ensure we securely wipe keys from memory after
3781 crypto_digest_get_digest and init_curve25519_keypair_from_file
3782 have finished using them. Resolves ticket 13477.
3784 o Minor features (security, out-of-memory handling):
3785 - When handling an out-of-memory condition, allocate less memory for
3786 temporary data structures. Fixes issue 10115.
3787 - When handling an out-of-memory condition, consider more types of
3788 buffers, including those on directory connections, and zlib
3789 buffers. Resolves ticket 11792.
3791 o Minor features (stability):
3792 - Add assertions in our hash-table iteration code to check for
3793 corrupted values that could cause infinite loops. Closes
3796 o Minor features (systemd):
3797 - Various improvements and modernizations in systemd hardening
3798 support. Closes ticket 13805. Patch from Craig Andrews.
3799 - Where supported, when running with systemd, report successful
3800 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
3801 - When running with systemd, support systemd watchdog messages. Part
3802 of ticket 11016. Patch by Michael Scherer.
3804 o Minor features (testing networks):
3805 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
3806 the "Exit" flag regardless of their uptime, bandwidth, or exit
3807 policy. TestingTorNetwork must be set for this option to have any
3808 effect. Previously, authorities would take up to 35 minutes to
3809 give nodes the Exit flag in a test network. Partially implements
3811 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
3812 and the default on a testing network to 2 minutes. Drop the
3813 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
3814 keep the default on a testing network at 30 seconds. This reduces
3815 HS bootstrap time to around 25 seconds. Also, change the default
3816 time in test-network.sh to match. Closes ticket 13401. Patch
3818 - Create TestingDirAuthVoteHSDir to correspond to
3819 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
3820 HSDir flag for the listed relays regardless of uptime or ORPort
3821 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
3822 Partial implementation for ticket 14067. Patch by "teor".
3824 o Minor features (tor2web mode):
3825 - Introduce the config option Tor2webRendezvousPoints, which allows
3826 clients in Tor2webMode to select a specific Rendezvous Point to be
3827 used in HS circuits. This might allow better performance for
3828 Tor2Web nodes. Implements ticket 12844.
3830 o Minor features (transparent proxy):
3831 - Update the transparent proxy option checks to allow for both ipfw
3832 and pf on OS X. Closes ticket 14002.
3833 - Use the correct option when using IPv6 with transparent proxy
3834 support on Linux. Resolves 13808. Patch by Francisco Blas
3837 o Minor features (validation):
3838 - Check all date/time values passed to tor_timegm and
3839 parse_rfc1123_time for validity, taking leap years into account.
3840 Improves HTTP header validation. Implemented with bug 13476.
3841 - In correct_tm(), limit the range of values returned by system
3842 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
3843 This means we don't have to deal with negative or too large dates,
3844 even if a clock is wrong. Otherwise we might fail to read a file
3845 written by us which includes such a date. Fixes bug 13476.
3846 - Stop allowing invalid address patterns like "*/24" that contain
3847 both a wildcard address and a bit prefix length. This affects all
3848 our address-range parsing code. Fixes bug 7484; bugfix
3851 o Minor bugfixes (bridge clients):
3852 - When configured to use a bridge without an identity digest (not
3853 recommended), avoid launching an extra channel to it when
3854 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
3856 o Minor bugfixes (bridges):
3857 - When DisableNetwork is set, do not launch pluggable transport
3858 plugins, and if any are running, terminate them. Fixes bug 13213;
3859 bugfix on 0.2.3.6-alpha.
3861 o Minor bugfixes (C correctness):
3862 - Fix several instances of possible integer overflow/underflow/NaN.
3863 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
3865 - In circuit_build_times_calculate_timeout() in circuitstats.c,
3866 avoid dividing by zero in the pareto calculations. This traps
3867 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
3869 - Fix an integer overflow in format_time_interval(). Fixes bug
3870 13393; bugfix on 0.2.0.10-alpha.
3871 - Set the correct day of year value when the system's localtime(_r)
3872 or gmtime(_r) functions fail to set struct tm. Not externally
3873 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
3874 - Avoid unlikely signed integer overflow in tor_timegm on systems
3875 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
3877 o Minor bugfixes (certificate handling):
3878 - If an authority operator accidentally makes a signing certificate
3879 with a future publication time, do not discard its real signing
3880 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
3881 - Remove any old authority certificates that have been superseded
3882 for at least two days. Previously, we would keep superseded
3883 certificates until they expired, if they were published close in
3884 time to the certificate that superseded them. Fixes bug 11454;
3885 bugfix on 0.2.1.8-alpha.
3887 o Minor bugfixes (client):
3888 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
3889 BadExit flag are not considered worthy candidates. Fixes bug
3890 13066; bugfix on 0.1.2.3-alpha.
3891 - Use the consensus schedule for downloading consensuses, and not
3892 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
3893 - Handle unsupported or malformed SOCKS5 requests properly by
3894 responding with the appropriate error message before closing the
3895 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
3897 o Minor bugfixes (client, automapping):
3898 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
3899 no value follows the option. Fixes bug 14142; bugfix on
3900 0.2.4.7-alpha. Patch by "teor".
3901 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
3902 14195; bugfix on 0.1.0.1-rc.
3903 - Prevent changes to other options from removing the wildcard value
3904 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
3906 - Allow MapAddress and AutomapHostsOnResolve to work together when
3907 an address is mapped into another address type (like .onion) that
3908 must be automapped at resolve time. Fixes bug 7555; bugfix
3911 o Minor bugfixes (client, bridges):
3912 - When we are using bridges and we had a network connectivity
3913 problem, only retry connecting to our currently configured
3914 bridges, not all bridges we know about and remember using. Fixes
3915 bug 14216; bugfix on 0.2.2.17-alpha.
3917 o Minor bugfixes (client, DNS):
3918 - Report the correct cached DNS expiration times on SOCKS port or in
3919 DNS replies. Previously, we would report everything as "never
3920 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
3921 - Avoid a small memory leak when we find a cached answer for a
3922 reverse DNS lookup in a client-side DNS cache. (Remember, client-
3923 side DNS caching is off by default, and is not recommended.) Fixes
3924 bug 14259; bugfix on 0.2.0.1-alpha.
3926 o Minor bugfixes (client, IPv6):
3927 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
3928 flag is not set; and not because the NoIPv4Traffic flag was set.
3929 Previously we'd looked at the NoIPv4Traffic flag for both types of
3930 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
3932 o Minor bugfixes (client, microdescriptors):
3933 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
3934 computing which microdescriptors to download. This keeps us from
3935 erroneous download behavior if two microdescriptor digests ever
3936 have the same first 160 bits. Fixes part of bug 13399; bugfix
3938 - Reset a router's status if its microdescriptor digest changes,
3939 even if the first 160 bits remain the same. Fixes part of bug
3940 13399; bugfix on 0.2.3.1-alpha.
3942 o Minor bugfixes (client, torrc):
3943 - Stop modifying the value of our DirReqStatistics torrc option just
3944 because we're not a bridge or relay. This bug was causing Tor
3945 Browser users to write "DirReqStatistics 0" in their torrc files
3946 as if they had chosen to change the config. Fixes bug 4244; bugfix
3948 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
3949 that our options have changed every time we SIGHUP. Fixes bug
3950 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
3952 o Minor bugfixes (compilation):
3953 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
3955 - Silence clang warnings under --enable-expensive-hardening,
3956 including implicit truncation of 64 bit values to 32 bit, const
3957 char assignment to self, tautological compare, and additional
3958 parentheses around equality tests. Fixes bug 13577; bugfix
3960 - Fix a clang warning about checking whether an address in the
3961 middle of a structure is NULL. Fixes bug 14001; bugfix
3963 - The address of an array in the middle of a structure will always
3964 be non-NULL. clang recognises this and complains. Disable the
3965 tautologous and redundant check to silence this warning. Fixes bug
3966 14001; bugfix on 0.2.1.2-alpha.
3967 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
3968 Addresses ticket 14188.
3969 - Build without warnings with the stock OpenSSL srtp.h header, which
3970 has a duplicate declaration of SSL_get_selected_srtp_profile().
3971 Fixes bug 14220; this is OpenSSL's bug, not ours.
3972 - Do not compile any code related to Tor2Web mode when Tor2Web mode
3973 is not enabled at compile time. Previously, this code was included
3974 in a disabled state. See discussion on ticket 12844.
3975 - Allow our configure script to build correctly with autoconf 2.62
3976 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
3977 - Improve the error message from ./configure to make it clear that
3978 when asciidoc has not been found, the user will have to either add
3979 --disable-asciidoc argument or install asciidoc. Resolves
3982 o Minor bugfixes (controller):
3983 - Report "down" in response to the "GETINFO entry-guards" command
3984 when relays are down with an unreachable_since value. Previously,
3985 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
3986 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
3987 14116; bugfix on 0.2.2.9-alpha.
3989 o Minor bugfixes (controller):
3990 - Return an error when the second or later arguments of the
3991 "setevents" controller command are invalid events. Previously we
3992 would return success while silently skipping invalid events. Fixes
3993 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
3995 o Minor bugfixes (directory authority):
3996 - Allow directory authorities to fetch more data from one another if
3997 they find themselves missing lots of votes. Previously, they had
3998 been bumping against the 10 MB queued data limit. Fixes bug 14261;
3999 bugfix on 0.1.2.5-alpha.
4000 - Do not attempt to download extrainfo documents which we will be
4001 unable to validate with a matching server descriptor. Fixes bug
4002 13762; bugfix on 0.2.0.1-alpha.
4003 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
4004 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
4005 - Enlarge the buffer to read bwauth generated files to avoid an
4006 issue when parsing the file in dirserv_read_measured_bandwidths().
4007 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
4008 - When running as a v3 directory authority, advertise that you serve
4009 extra-info documents so that clients who want them can find them
4010 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
4012 o Minor bugfixes (directory system):
4013 - Always believe that v3 directory authorities serve extra-info
4014 documents, whether they advertise "caches-extra-info" or not.
4015 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
4016 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
4017 Previously, directories offering BRIDGE_DIRINFO and some other
4018 flag (i.e. microdescriptors or extrainfo) would be ignored when
4019 looking for bridges. Partially fixes bug 13163; bugfix
4022 o Minor bugfixes (file handling):
4023 - Stop failing when key files are zero-length. Instead, generate new
4024 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
4025 on all versions of Tor. Patch by "teor".
4026 - Stop generating a fresh .old RSA onion key file when the .old file
4027 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
4028 - Avoid overwriting .old key files with empty key files.
4029 - Skip loading zero-length extrainfo store, router store, stats,
4030 state, and key files.
4031 - Avoid crashing when trying to reload a torrc specified as a
4032 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
4035 o Minor bugfixes (hidden services):
4036 - Close the introduction circuit when we have no more usable intro
4037 points, instead of waiting for it to time out. This also ensures
4038 that no follow-up HS descriptor fetch is triggered when the
4039 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
4040 - When fetching a hidden service descriptor for a down service that
4041 was recently up, do not keep refetching until we try the same
4042 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
4043 - Correctly send a controller event when we find that a rendezvous
4044 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
4045 - Pre-check directory permissions for new hidden-services to avoid
4046 at least one case of "Bug: Acting on config options left us in a
4047 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
4048 - When fetching hidden service descriptors, we now check not only
4049 for whether we got the hidden service we had in mind, but also
4050 whether we got the particular descriptors we wanted. This prevents
4051 a class of inefficient but annoying DoS attacks by hidden service
4052 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
4055 o Minor bugfixes (Linux seccomp2 sandbox):
4056 - Make transparent proxy support work along with the seccomp2
4057 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
4058 by Francisco Blas Izquierdo Riera.
4059 - Fix a memory leak in tor-resolve when running with the sandbox
4060 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
4061 - Allow glibc fatal errors to be sent to stderr before Tor exits.
4062 Previously, glibc would try to write them to /dev/tty, and the
4063 sandbox would trap the call and make Tor exit prematurely. Fixes
4064 bug 14759; bugfix on 0.2.5.1-alpha.
4066 o Minor bugfixes (logging):
4067 - Avoid crashing when there are more log domains than entries in
4068 domain_list. Bugfix on 0.2.3.1-alpha.
4069 - Downgrade warnings about RSA signature failures to info log level.
4070 Emit a warning when an extra info document is found incompatible
4071 with a corresponding router descriptor. Fixes bug 9812; bugfix
4073 - Make connection_ap_handshake_attach_circuit() log the circuit ID
4074 correctly. Fixes bug 13701; bugfix on 0.0.6.
4076 o Minor bugfixes (networking):
4077 - Check for orconns and use connection_or_close_for_error() rather
4078 than connection_mark_for_close() directly in the getsockopt()
4079 failure case of connection_handle_write_impl(). Fixes bug 11302;
4080 bugfix on 0.2.4.4-alpha.
4082 o Minor bugfixes (parsing):
4083 - Stop accepting milliseconds (or other junk) at the end of
4084 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
4085 - Support two-number and three-number version numbers correctly, in
4086 case we change the Tor versioning system in the future. Fixes bug
4087 13661; bugfix on 0.0.8pre1.
4089 o Minor bugfixes (portability):
4090 - Fix the ioctl()-based network interface lookup code so that it
4091 will work on systems that have variable-length struct ifreq, for
4093 - Use the correct datatype in the SipHash-2-4 function to prevent
4094 compilers from assuming any sort of alignment. Fixes bug 15436;
4095 bugfix on 0.2.5.3-alpha.
4097 o Minor bugfixes (preventative security, C safety):
4098 - When reading a hexadecimal, base-32, or base-64 encoded value from
4099 a string, always overwrite the whole output buffer. This prevents
4100 some bugs where we would look at (but fortunately, not reveal)
4101 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
4103 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
4104 just the part that's used. This makes it harder for data leak bugs
4105 to occur in the event of other programming failures. Resolves
4108 o Minor bugfixes (relay):
4109 - When generating our family list, remove spaces from around the
4110 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
4111 - If our previous bandwidth estimate was 0 bytes, allow publishing a
4112 new relay descriptor immediately. Fixes bug 13000; bugfix
4115 o Minor bugfixes (shutdown):
4116 - When shutting down, always call event_del() on lingering read or
4117 write events before freeing them. Otherwise, we risk double-frees
4118 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
4121 o Minor bugfixes (small memory leaks):
4122 - Avoid leaking memory when using IPv6 virtual address mappings.
4123 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
4126 o Minor bugfixes (statistics):
4127 - Increase period over which bandwidth observations are aggregated
4128 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
4130 o Minor bugfixes (systemd support):
4131 - Run correctly under systemd with the RunAsDaemon option set. Fixes
4132 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
4133 - Inform the systemd supervisor about more changes in the Tor
4134 process status. Implements part of ticket 14141. Patch from
4137 o Minor bugfixes (testing networks):
4138 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
4139 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
4140 - Stop using the default authorities in networks which provide both
4141 AlternateDirAuthority and AlternateBridgeAuthority. Partially
4142 fixes bug 13163; bugfix on 0.2.0.13-alpha.
4144 o Minor bugfixes (testing networks, fast startup):
4145 - Allow Tor to build circuits using a consensus with no exits. If
4146 the consensus has no exits (typical of a bootstrapping test
4147 network), allow Tor to build circuits once enough descriptors have
4148 been downloaded. This assists in bootstrapping a testing Tor
4149 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
4151 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
4152 header to directory servers. This allows us to obtain consensuses
4153 promptly when the consensus interval is very short. This assists
4154 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
4155 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
4156 - Stop assuming that private addresses are local when checking
4157 reachability in a TestingTorNetwork. Instead, when testing, assume
4158 all OR connections are remote. (This is necessary due to many test
4159 scenarios running all relays on localhost.) This assists in
4160 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
4161 0.1.0.1-rc. Patch by "teor".
4162 - Avoid building exit circuits from a consensus with no exits. Now
4163 thanks to our fix for 13718, we accept a no-exit network as not
4164 wholly lost, but we need to remember not to try to build exit
4165 circuits on it. Closes ticket 13814; patch by "teor".
4166 - Stop requiring exits to have non-zero bandwithcapacity in a
4167 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
4168 ignore exit bandwidthcapacity. This assists in bootstrapping a
4169 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
4170 on 0.2.0.3-alpha. Patch by "teor".
4171 - Add "internal" to some bootstrap statuses when no exits are
4172 available. If the consensus does not contain Exits, Tor will only
4173 build internal circuits. In this case, relevant statuses will
4174 contain the word "internal" as indicated in the Tor control-
4175 spec.txt. When bootstrap completes, Tor will be ready to build
4176 internal circuits. If a future consensus contains Exits, exit
4177 circuits may become available. Fixes part of bug 13718; bugfix on
4178 0.2.4.10-alpha. Patch by "teor".
4179 - Decrease minimum consensus interval to 10 seconds when
4180 TestingTorNetwork is set, or 5 seconds for the first consensus.
4181 Fix assumptions throughout the code that assume larger intervals.
4182 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
4184 - Avoid excluding guards from path building in minimal test
4185 networks, when we're in a test network and excluding guards would
4186 exclude all relays. This typically occurs in incredibly small tor
4187 networks, and those using "TestingAuthVoteGuard *". Fixes part of
4188 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
4190 o Minor bugfixes (testing):
4191 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
4192 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
4193 - Stop spawn test failures due to a race condition between the
4194 SIGCHLD handler updating the process status, and the test reading
4195 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
4196 - Avoid passing an extra backslash when creating a temporary
4197 directory for running the unit tests on Windows. Fixes bug 12392;
4198 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
4200 o Minor bugfixes (TLS):
4201 - Check more thoroughly throughout the TLS code for possible
4202 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
4204 o Minor bugfixes (transparent proxy):
4205 - Use getsockname, not getsockopt, to retrieve the address for a
4206 TPROXY-redirected connection. Fixes bug 13796; bugfix
4209 o Minor bugfixes (windows):
4210 - Remove code to special-case handling of NTE_BAD_KEYSET when
4211 acquiring windows CryptoAPI context. This error can't actually
4212 occur for the parameters we're providing. Fixes bug 10816; bugfix
4215 o Minor bugfixes (zlib):
4216 - Avoid truncating a zlib stream when trying to finalize it with an
4217 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
4219 o Code simplification and refactoring:
4220 - Change the entry_is_live() function to take named bitfield
4221 elements instead of an unnamed list of booleans. Closes
4223 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
4224 Resolves ticket 12205.
4225 - Use calloc and reallocarray functions instead of multiply-
4226 then-malloc. This makes it less likely for us to fall victim to an
4227 integer overflow attack when allocating. Resolves ticket 12855.
4228 - Use the standard macro name SIZE_MAX, instead of our
4230 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
4231 functions which take them as arguments. Replace 0 with NO_DIRINFO
4232 in a function call for clarity. Seeks to prevent future issues
4234 - Avoid 4 null pointer errors under clang static analysis by using
4235 tor_assert() to prove that the pointers aren't null. Fixes
4237 - Rework the API of policies_parse_exit_policy() to use a bitmask to
4238 represent parsing options, instead of a confusing mess of
4239 booleans. Resolves ticket 8197.
4240 - Introduce a helper function to parse ExitPolicy in
4241 or_options_t structure.
4242 - Move fields related to isolating and configuring client ports into
4243 a shared structure. Previously, they were duplicated across
4244 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
4245 to copy them correctly had been the cause of at least one bug in
4246 the past. Closes ticket 8546.
4247 - Refactor the get_interface_addresses_raw() doom-function into
4248 multiple smaller and simpler subfunctions. Cover the resulting
4249 subfunctions with unit-tests. Fixes a significant portion of
4251 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
4252 only for version <= 0.2.2.24 which is now deprecated. Closes
4254 - Remove a test for a long-defunct broken version-one
4256 - Refactor main loop to extract the 'loop' part. This makes it
4257 easier to run Tor under Shadow. Closes ticket 15176.
4258 - Stop using can_complete_circuits as a global variable; access it
4259 with a function instead.
4260 - Avoid using operators directly as macro arguments: this lets us
4261 apply coccinelle transformations to our codebase more directly.
4262 Closes ticket 13172.
4263 - Combine the functions used to parse ClientTransportPlugin and
4264 ServerTransportPlugin into a single function. Closes ticket 6456.
4265 - Add inline functions and convenience macros for inspecting channel
4266 state. Refactor the code to use convenience macros instead of
4267 checking channel state directly. Fixes issue 7356.
4268 - Document all members of was_router_added_t and rename
4269 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
4270 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
4271 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
4272 constant instead of hardcoded value. Fixes issue 13840.
4273 - Refactor our generic strmap and digestmap types into a single
4274 implementation, so that we can add a new digest256map
4278 - Add a doc/TUNING document with tips for handling large numbers of
4279 TCP connections when running busy Tor relay. Update the warning
4280 message to point to this file when running out of sockets
4281 operating system is allowing to use simultaneously. Resolves
4283 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
4284 for writing the OpenBSD-specific tips. Resolves ticket 13702.
4285 - Make the tor-resolve documentation match its help string and its
4286 options. Resolves part of ticket 14325.
4287 - Log a more useful error message from tor-resolve when failing to
4288 look up a hidden service address. Resolves part of ticket 14325.
4289 - Document the bridge-authority-only 'networkstatus-bridges' file.
4290 Closes ticket 13713; patch from "tom".
4291 - Fix typo in PredictedPortsRelevanceTime option description in
4292 manpage. Resolves issue 13707.
4293 - Stop suggesting that users specify relays by nickname: it isn't a
4294 good idea. Also, properly cross-reference how to specify relays in
4295 all parts of manual documenting options that take a list of
4296 relays. Closes ticket 13381.
4297 - Clarify the HiddenServiceDir option description in manpage to make
4298 it clear that relative paths are taken with respect to the current
4299 working directory. Also clarify that this behavior is not
4300 guaranteed to remain indefinitely. Fixes issue 13913.
4302 o Distribution (systemd):
4303 - systemd unit file: only allow tor to write to /var/lib/tor and
4304 /var/log/tor. The rest of the filesystem is accessible for reading
4305 only. Patch by intrigeri; resolves ticket 12751.
4306 - systemd unit file: ensure that the process and all its children
4307 can never gain new privileges. Patch by intrigeri; resolves
4309 - systemd unit file: set up /var/run/tor as writable for the Tor
4310 service. Patch by intrigeri; resolves ticket 13196.
4312 o Downgraded warnings:
4313 - Don't warn when we've attempted to contact a relay using the wrong
4314 ntor onion key. Closes ticket 9635.
4317 - Remove some lingering dead code that once supported mempools.
4318 Mempools were disabled by default in 0.2.5, and removed entirely
4319 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
4322 o Removed features (directory authorities):
4323 - Remove code that prevented authorities from listing Tor relays
4324 affected by CVE-2011-2769 as guards. These relays are already
4325 rejected altogether due to the minimum version requirement of
4326 0.2.3.16-alpha. Closes ticket 13152.
4327 - The "AuthDirRejectUnlisted" option no longer has any effect, as
4328 the fingerprints file (approved-routers) has been deprecated.
4329 - Directory authorities do not support being Naming dirauths anymore.
4330 The "NamingAuthoritativeDir" config option is now obsolete.
4331 - Directory authorities do not support giving out the BadDirectory
4333 - Directory authorities no longer advertise or support consensus
4334 methods 1 through 12 inclusive. These consensus methods were
4335 obsolete and/or insecure: maintaining the ability to support them
4336 served no good purpose. Implements part of proposal 215; closes
4340 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
4341 longer silently accepted as an alias for "ExitNodes".
4342 - The --enable-mempool and --enable-buf-freelists options, which
4343 were originally created to work around bad malloc implementations,
4344 no longer exist. They were off-by-default in 0.2.5. Closes
4346 - We no longer remind the user about configuration options that have
4347 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
4348 - Remove our old, non-weighted bandwidth-based node selection code.
4349 Previously, we used it as a fallback when we couldn't perform
4350 weighted bandwidth-based node selection. But that would only
4351 happen in the cases where we had no consensus, or when we had a
4352 consensus generated by buggy or ancient directory authorities. In
4353 either case, it's better to use the more modern, better maintained
4354 algorithm, with reasonable defaults for the weights. Closes
4356 - Remove the --disable-curve25519 configure option. Relays and
4357 clients now are required to support curve25519 and the
4359 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
4360 used to be deprecated synonyms for "StrictNodes", are now marked
4361 obsolete. Resolves ticket 12226.
4362 - Clients don't understand the BadDirectory flag in the consensus
4363 anymore, and ignore it.
4365 o Removed platform support:
4366 - We no longer include special code to build on Windows CE; as far
4367 as we know, nobody has used Tor on Windows CE in a very long time.
4368 Closes ticket 11446.
4370 o Testing (test-network.sh):
4371 - Stop using "echo -n", as some shells' built-in echo doesn't
4372 support "-n". Instead, use "/bin/echo -n". Partially fixes
4374 - Stop an apparent test-network hang when used with make -j2. Fixes
4376 - Add a --delay option to test-network.sh, which configures the
4377 delay before the chutney network tests for data transmission.
4378 Partially implements ticket 13161.
4381 - Test that tor does not fail when key files are zero-length. Check
4382 that tor generates new keys, and overwrites the empty key files.
4383 - Test that tor generates new keys when keys are missing
4384 (existing behavior).
4385 - Test that tor does not overwrite key files that already contain
4386 data (existing behavior). Tests bug 13111. Patch by "teor".
4387 - New "make test-stem" target to run stem integration tests.
4388 Requires that the "STEM_SOURCE_DIR" environment variable be set.
4389 Closes ticket 14107.
4390 - Make the test_cmdline_args.py script work correctly on Windows.
4391 Patch from Gisle Vanem.
4392 - Move the slower unit tests into a new "./src/test/test-slow"
4393 binary that can be run independently of the other tests. Closes
4395 - New tests for many parts of channel, relay, and circuitmux
4396 functionality. Code by Andrea; part of 9262.
4397 - New tests for parse_transport_line(). Part of ticket 6456.
4398 - In the unit tests, use chgrp() to change the group of the unit
4399 test temporary directory to the current user, so that the sticky
4400 bit doesn't interfere with tests that check directory groups.
4402 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
4404 - Refactor the function that chooses guard nodes so that it can more
4405 easily be tested; write some tests for it.
4406 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
4407 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
4408 - Create unit tests for format_time_interval(). With bug 13393.
4409 - Add unit tests for tor_timegm signed overflow, tor_timegm and
4410 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
4411 tests (visible) fixes in bug 13476.
4412 - Add a "coverage-html" make target to generate HTML-visualized
4413 coverage results when building with --enable-coverage. (Requires
4414 lcov.) Patch from Kevin Murray.
4415 - Enable the backtrace handler (where supported) when running the
4417 - Revise all unit tests that used the legacy test_* macros to
4418 instead use the recommended tt_* macros. This patch was generated
4419 with coccinelle, to avoid manual errors. Closes ticket 13119.
4421 Changes in version 0.2.5.11 - 2015-03-17
4422 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
4424 It backports several bugfixes from the 0.2.6 branch, including a
4425 couple of medium-level security fixes for relays and exit nodes.
4426 It also updates the list of directory authorities.
4428 o Directory authority changes:
4429 - Remove turtles as a directory authority.
4430 - Add longclaw as a new (v3) directory authority. This implements
4431 ticket 13296. This keeps the directory authority count at 9.
4432 - The directory authority Faravahar has a new IP address. This
4433 closes ticket 14487.
4435 o Major bugfixes (crash, OSX, security):
4436 - Fix a remote denial-of-service opportunity caused by a bug in
4437 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
4440 o Major bugfixes (relay, stability, possible security):
4441 - Fix a bug that could lead to a relay crashing with an assertion
4442 failure if a buffer of exactly the wrong layout was passed to
4443 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
4444 0.2.0.10-alpha. Patch from 'cypherpunks'.
4445 - Do not assert if the 'data' pointer on a buffer is advanced to the
4446 very end of the buffer; log a BUG message instead. Only assert if
4447 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
4449 o Major bugfixes (exit node stability):
4450 - Fix an assertion failure that could occur under high DNS load.
4451 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
4452 diagnosed and fixed by "cypherpunks".
4454 o Major bugfixes (Linux seccomp2 sandbox):
4455 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
4456 crash during attempts to call wait4. Fixes bug 15088; bugfix on
4457 0.2.5.1-alpha. Patch from "sanic".
4459 o Minor features (controller):
4460 - New "GETINFO bw-event-cache" to get information about recent
4461 bandwidth events. Closes ticket 14128. Useful for controllers to
4462 get recent bandwidth history after the fix for ticket 13988.
4464 o Minor features (geoip):
4465 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
4466 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
4469 o Minor bugfixes (client, automapping):
4470 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
4471 no value follows the option. Fixes bug 14142; bugfix on
4472 0.2.4.7-alpha. Patch by "teor".
4473 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
4474 14195; bugfix on 0.1.0.1-rc.
4476 o Minor bugfixes (compilation):
4477 - Build without warnings with the stock OpenSSL srtp.h header, which
4478 has a duplicate declaration of SSL_get_selected_srtp_profile().
4479 Fixes bug 14220; this is OpenSSL's bug, not ours.
4481 o Minor bugfixes (directory authority):
4482 - Allow directory authorities to fetch more data from one another if
4483 they find themselves missing lots of votes. Previously, they had
4484 been bumping against the 10 MB queued data limit. Fixes bug 14261;
4485 bugfix on 0.1.2.5-alpha.
4486 - Enlarge the buffer to read bwauth generated files to avoid an
4487 issue when parsing the file in dirserv_read_measured_bandwidths().
4488 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
4490 o Minor bugfixes (statistics):
4491 - Increase period over which bandwidth observations are aggregated
4492 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
4494 o Minor bugfixes (preventative security, C safety):
4495 - When reading a hexadecimal, base-32, or base-64 encoded value from
4496 a string, always overwrite the whole output buffer. This prevents
4497 some bugs where we would look at (but fortunately, not reveal)
4498 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
4502 Changes in version 0.2.4.26 - 2015-03-17
4503 Tor 0.2.4.26 includes an updated list of directory authorities. It
4504 also backports a couple of stability and security bugfixes from 0.2.5
4507 o Directory authority changes:
4508 - Remove turtles as a directory authority.
4509 - Add longclaw as a new (v3) directory authority. This implements
4510 ticket 13296. This keeps the directory authority count at 9.
4511 - The directory authority Faravahar has a new IP address. This
4512 closes ticket 14487.
4514 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
4515 - Fix an assertion failure that could occur under high DNS load.
4516 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
4517 diagnosed and fixed by "cypherpunks".
4519 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
4520 - Fix a bug that could lead to a relay crashing with an assertion
4521 failure if a buffer of exactly the wrong layout was passed to
4522 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
4523 0.2.0.10-alpha. Patch from 'cypherpunks'.
4524 - Do not assert if the 'data' pointer on a buffer is advanced to the
4525 very end of the buffer; log a BUG message instead. Only assert if
4526 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
4528 o Minor features (geoip):
4529 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
4530 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
4533 Changes in version 0.2.5.10 - 2014-10-24
4534 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
4536 It adds several new security features, including improved
4537 denial-of-service resistance for relays, new compiler hardening
4538 options, and a system-call sandbox for hardened installations on Linux
4539 (requires seccomp2). The controller protocol has several new features,
4540 resolving IPv6 addresses should work better than before, and relays
4541 should be a little more CPU-efficient. We've added support for more
4542 OpenBSD and FreeBSD transparent proxy types. We've improved the build
4543 system and testing infrastructure to allow unit testing of more parts
4544 of the Tor codebase. Finally, we've addressed several nagging pluggable
4545 transport usability issues, and included numerous other small bugfixes
4546 and features mentioned below.
4548 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
4549 have accumulated many known flaws; everyone should upgrade.
4551 o Major features (security):
4552 - The ntor handshake is now on-by-default, no matter what the
4553 directory authorities recommend. Implements ticket 8561.
4554 - Make the "tor-gencert" tool used by directory authority operators
4555 create 2048-bit signing keys by default (rather than 1024-bit, since
4556 1024-bit is uncomfortably small these days). Addresses ticket 10324.
4557 - Warn about attempts to run hidden services and relays in the same
4558 process: that's probably not a good idea. Closes ticket 12908.
4559 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
4560 today support TLS 1.0 or later, so we can safely turn off support
4561 for this old (and insecure) protocol. Fixes bug 13426.
4563 o Major features (relay security, DoS-resistance):
4564 - When deciding whether we have run out of memory and we need to
4565 close circuits, also consider memory allocated in buffers for
4566 streams attached to each circuit.
4568 This change, which extends an anti-DoS feature introduced in
4569 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
4570 better resist more memory-based DoS attacks than before. Since the
4571 MaxMemInCellQueues option now applies to all queues, it is renamed
4572 to MaxMemInQueues. This feature fixes bug 10169.
4573 - Avoid hash-flooding denial-of-service attacks by using the secure
4574 SipHash-2-4 hash function for our hashtables. Without this
4575 feature, an attacker could degrade performance of a targeted
4576 client or server by flooding their data structures with a large
4577 number of entries to be stored at the same hash table position,
4578 thereby slowing down the Tor instance. With this feature, hash
4579 table positions are derived from a randomized cryptographic key,
4580 and an attacker cannot predict which entries will collide. Closes
4582 - If you don't specify MaxMemInQueues yourself, Tor now tries to
4583 pick a good value based on your total system memory. Previously,
4584 the default was always 8 GB. You can still override the default by
4585 setting MaxMemInQueues yourself. Resolves ticket 11396.
4587 o Major features (bridges and pluggable transports):
4588 - Add support for passing arguments to managed pluggable transport
4589 proxies. Implements ticket 3594.
4590 - Bridges now track GeoIP information and the number of their users
4591 even when pluggable transports are in use, and report usage
4592 statistics in their extra-info descriptors. Resolves tickets 4773
4594 - Don't launch pluggable transport proxies if we don't have any
4595 bridges configured that would use them. Now we can list many
4596 pluggable transports, and Tor will dynamically start one when it
4597 hears a bridge address that needs it. Resolves ticket 5018.
4598 - The bridge directory authority now assigns status flags (Stable,
4599 Guard, etc) to bridges based on thresholds calculated over all
4600 Running bridges. Now bridgedb can finally make use of its features
4601 to e.g. include at least one Stable bridge in its answers. Fixes
4604 o Major features (controller):
4605 - Extend ORCONN controller event to include an "ID" parameter,
4606 and add four new controller event types CONN_BW, CIRC_BW,
4607 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
4608 The new events are emitted in private Tor networks only, with the
4609 goal of being able to better track performance and load during
4610 full-network simulations. Implements proposal 218 and ticket 7359.
4612 o Major features (relay performance):
4613 - Speed up server-side lookups of rendezvous and introduction point
4614 circuits by using hashtables instead of linear searches. These
4615 functions previously accounted between 3 and 7% of CPU usage on
4616 some busy relays. Resolves ticket 9841.
4617 - Avoid wasting CPU when extending a circuit over a channel that is
4618 nearly out of circuit IDs. Previously, we would do a linear scan
4619 over possible circuit IDs before finding one or deciding that we
4620 had exhausted our possibilities. Now, we try at most 64 random
4621 circuit IDs before deciding that we probably won't succeed. Fixes
4622 a possible root cause of ticket 11553.
4624 o Major features (seccomp2 sandbox, Linux only):
4625 - Use the seccomp2 syscall filtering facility on Linux to limit
4626 which system calls Tor can invoke. This is an experimental,
4627 Linux-only feature to provide defense-in-depth against unknown
4628 attacks. To try turning it on, set "Sandbox 1" in your torrc
4629 file. Please be ready to report bugs. We hope to add support
4630 for better sandboxing in the future, including more fine-grained
4631 filters, better division of responsibility, and support for more
4632 platforms. This work has been done by Cristian-Matei Toader for
4633 Google Summer of Code. Resolves tickets 11351 and 11465.
4635 o Major features (testing networks):
4636 - Make testing Tor networks bootstrap better: lower directory fetch
4637 retry schedules and maximum interval without directory requests,
4638 and raise maximum download tries. Implements ticket 6752.
4639 - Add make target 'test-network' to run tests on a Chutney network.
4640 Implements ticket 8530.
4642 o Major features (other):
4643 - On some platforms (currently: recent OSX versions, glibc-based
4644 platforms that support the ELF format, and a few other
4645 Unix-like operating systems), Tor can now dump stack traces
4646 when a crash occurs or an assertion fails. By default, traces
4647 are dumped to stderr (if possible) and to any logs that are
4648 reporting errors. Implements ticket 9299.
4650 o Deprecated versions:
4651 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
4652 attention for some while.
4654 o Major bugfixes (security, directory authorities):
4655 - Directory authorities now include a digest of each relay's
4656 identity key as a part of its microdescriptor.
4658 This is a workaround for bug 11743 (reported by "cypherpunks"),
4659 where Tor clients do not support receiving multiple
4660 microdescriptors with the same SHA256 digest in the same
4661 consensus. When clients receive a consensus like this, they only
4662 use one of the relays. Without this fix, a hostile relay could
4663 selectively disable some client use of target relays by
4664 constructing a router descriptor with a different identity and the
4665 same microdescriptor parameters and getting the authorities to
4666 list it in a microdescriptor consensus. This fix prevents an
4667 attacker from causing a microdescriptor collision, because the
4668 router's identity is not forgeable.
4670 o Major bugfixes (openssl bug workaround):
4671 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
4672 1.0.1j, built with the 'no-ssl3' configuration option. Fixes
4673 bug 13471. This is a workaround for an OpenSSL bug.
4675 o Major bugfixes (client):
4676 - Perform circuit cleanup operations even when circuit
4677 construction operations are disabled (because the network is
4678 disabled, or because there isn't enough directory information).
4679 Previously, when we were not building predictive circuits, we
4680 were not closing expired circuits either. Fixes bug 8387; bugfix on
4681 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
4682 became more strict about when we have "enough directory information
4685 o Major bugfixes (client, pluggable transports):
4686 - When managing pluggable transports, use OS notification facilities
4687 to learn if they have crashed, and don't attempt to kill any
4688 process that has already exited. Fixes bug 8746; bugfix
4691 o Major bugfixes (relay denial of service):
4692 - Instead of writing destroy cells directly to outgoing connection
4693 buffers, queue them and intersperse them with other outgoing cells.
4694 This can prevent a set of resource starvation conditions where too
4695 many pending destroy cells prevent data cells from actually getting
4696 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
4697 bugfix on 0.2.0.1-alpha.
4699 o Major bugfixes (relay):
4700 - Avoid queuing or sending destroy cells for circuit ID zero when we
4701 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
4702 Found and fixed by "cypherpunks".
4703 - Fix ORPort reachability detection on relays running behind a
4704 proxy, by correctly updating the "local" mark on the controlling
4705 channel when changing the address of an or_connection_t after the
4706 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
4707 - Use a direct dirport connection when uploading non-anonymous
4708 descriptors to the directory authorities. Previously, relays would
4709 incorrectly use tunnel connections under a fairly wide variety of
4710 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
4711 - When a circuit accidentally has the same circuit ID for its
4712 forward and reverse direction, correctly detect the direction of
4713 cells using that circuit. Previously, this bug made roughly one
4714 circuit in a million non-functional. Fixes bug 12195; this is a
4715 bugfix on every version of Tor.
4717 o Minor features (security):
4718 - New --enable-expensive-hardening option to enable security
4719 hardening options that consume nontrivial amounts of CPU and
4720 memory. Right now, this includes AddressSanitizer and UbSan, which
4721 are supported in newer versions of GCC and Clang. Closes ticket
4723 - Authorities now assign the Guard flag to the fastest 25% of the
4724 network (it used to be the fastest 50%). Also raise the consensus
4725 weight that guarantees the Guard flag from 250 to 2000. For the
4726 current network, this results in about 1100 guards, down from 2500.
4727 This step paves the way for moving the number of entry guards
4728 down to 1 (proposal 236) while still providing reasonable expected
4729 performance for most users. Implements ticket 12690.
4731 o Minor features (security, memory management):
4732 - Memory allocation tricks (mempools and buffer freelists) are now
4733 disabled by default. You can turn them back on with
4734 --enable-mempools and --enable-buf-freelists respectively. We're
4735 disabling these features because malloc performance is good enough
4736 on most platforms, and a similar feature in OpenSSL exacerbated
4737 exploitation of the Heartbleed attack. Resolves ticket 11476.
4739 o Minor features (bridge client):
4740 - Report a more useful failure message when we can't connect to a
4741 bridge because we don't have the right pluggable transport
4742 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
4744 o Minor features (bridge):
4745 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
4746 cookie file for the ExtORPort g+r by default.
4748 o Minor features (bridges, pluggable transports):
4749 - Bridges now write the SHA1 digest of their identity key
4750 fingerprint (that is, a hash of a hash of their public key) to
4751 notice-level logs, and to a new hashed-fingerprint file. This
4752 information will help bridge operators look up their bridge in
4753 Globe and similar tools. Resolves ticket 10884.
4754 - Improve the message that Tor displays when running as a bridge
4755 using pluggable transports without an Extended ORPort listener.
4756 Also, log the message in the log file too. Resolves ticket 11043.
4757 - Add threshold cutoffs to the networkstatus document created by
4758 the Bridge Authority. Fixes bug 1117.
4759 - On Windows, spawn background processes using the CREATE_NO_WINDOW
4760 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
4761 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
4762 Vidalia set this option for us.) Implements ticket 10297.
4764 o Minor features (build):
4765 - The configure script has a --disable-seccomp option to turn off
4766 support for libseccomp on systems that have it, in case it (or
4767 Tor's use of it) is broken. Resolves ticket 11628.
4768 - Assume that a user using ./configure --host wants to cross-compile,
4769 and give an error if we cannot find a properly named
4770 tool-chain. Add a --disable-tool-name-check option to proceed
4771 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
4772 - If we run ./configure and the compiler recognizes -fstack-protector
4773 but the linker rejects it, warn the user about a potentially missing
4774 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
4775 - Add support for `--library-versions` flag. Implements ticket 6384.
4776 - Return the "unexpected sendme" warnings to a warn severity, but make
4777 them rate limited, to help diagnose ticket 8093.
4778 - Detect a missing asciidoc, and warn the user about it, during
4779 configure rather than at build time. Fixes issue 6506. Patch from
4782 o Minor features (client):
4783 - Add a new option, PredictedPortsRelevanceTime, to control how long
4784 after having received a request to connect to a given port Tor
4785 will try to keep circuits ready in anticipation of future requests
4786 for that port. Patch from "unixninja92"; implements ticket 9176.
4788 o Minor features (config options and command line):
4789 - Add an --allow-missing-torrc commandline option that tells Tor to
4790 run even if the configuration file specified by -f is not available.
4791 Implements ticket 10060.
4792 - Add support for the TPROXY transparent proxying facility on Linux.
4793 See documentation for the new TransProxyType option for more
4794 details. Implementation by "thomo". Closes ticket 10582.
4796 o Minor features (config options):
4797 - Config (torrc) lines now handle fingerprints which are missing
4798 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
4799 - Support a --dump-config option to print some or all of the
4800 configured options. Mainly useful for debugging the command-line
4801 option parsing code. Helps resolve ticket 4647.
4802 - Raise awareness of safer logging: notify user of potentially
4803 unsafe config options, like logging more verbosely than severity
4804 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
4805 - Add a new configuration option TestingV3AuthVotingStartOffset
4806 that bootstraps a network faster by changing the timing for
4807 consensus votes. Addresses ticket 8532.
4808 - Add a new torrc option "ServerTransportOptions" that allows
4809 bridge operators to pass configuration parameters to their
4810 pluggable transports. Resolves ticket 8929.
4811 - The config (torrc) file now accepts bandwidth and space limits in
4812 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
4813 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
4816 o Minor features (controller):
4817 - Make the entire exit policy available from the control port via
4818 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
4820 - Because of the fix for ticket 11396, the real limit for memory
4821 usage may no longer match the configured MaxMemInQueues value. The
4822 real limit is now exposed via GETINFO limits/max-mem-in-queues.
4823 - Add a new "HS_DESC" controller event that reports activities
4824 related to hidden service descriptors. Resolves ticket 8510.
4825 - New "DROPGUARDS" controller command to forget all current entry
4826 guards. Not recommended for ordinary use, since replacing guards
4827 too frequently makes several attacks easier. Resolves ticket 9934;
4829 - Implement the TRANSPORT_LAUNCHED control port event that
4830 notifies controllers about new launched pluggable
4831 transports. Resolves ticket 5609.
4833 o Minor features (diagnostic):
4834 - When logging a warning because of bug 7164, additionally check the
4835 hash table for consistency (as proposed on ticket 11737). This may
4836 help diagnose bug 7164.
4837 - When we log a heartbeat, log how many one-hop circuits we have
4838 that are at least 30 minutes old, and log status information about
4839 a few of them. This is an attempt to track down bug 8387.
4840 - When encountering an unexpected CR while writing text to a file on
4841 Windows, log the name of the file. Should help diagnosing
4843 - Give more specific warnings when a client notices that an onion
4844 handshake has failed. Fixes ticket 9635.
4845 - Add significant new logging code to attempt to diagnose bug 12184,
4846 where relays seem to run out of available circuit IDs.
4847 - Improve the diagnostic log message for bug 8387 even further to
4848 try to improve our odds of figuring out why one-hop directory
4849 circuits sometimes do not get closed.
4850 - Add more log messages to diagnose bug 7164, which causes
4851 intermittent "microdesc_free() called but md was still referenced"
4852 warnings. We now include more information, to figure out why we
4853 might be cleaning a microdescriptor for being too old if it's
4854 still referenced by a live node_t object.
4855 - Log current accounting state (bytes sent and received + remaining
4856 time for the current accounting period) in the relay's heartbeat
4857 message. Implements ticket 5526; patch from Peter Retzlaff.
4859 o Minor features (geoip):
4860 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
4863 o Minor features (interface):
4864 - Generate a warning if any ports are listed in the SocksPolicy,
4865 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
4866 AuthDirBadExit options. (These options only support address
4867 ranges.) Fixes part of ticket 11108.
4869 o Minor features (kernel API usage):
4870 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
4871 sockets in a single system call. Implements ticket 5129.
4873 o Minor features (log messages):
4874 - When ServerTransportPlugin is set on a bridge, Tor can write more
4875 useful statistics about bridge use in its extrainfo descriptors,
4876 but only if the Extended ORPort ("ExtORPort") is set too. Add a
4877 log message to inform the user in this case. Resolves ticket 9651.
4878 - When receiving a new controller connection, log the origin address.
4879 Resolves ticket 9698; patch from "sigpipe".
4880 - When logging OpenSSL engine status at startup, log the status of
4881 more engines. Fixes ticket 10043; patch from Joshua Datko.
4883 o Minor features (log verbosity):
4884 - Demote the message that we give when a flushing connection times
4885 out for too long from NOTICE to INFO. It was usually meaningless.
4886 Resolves ticket 5286.
4887 - Don't log so many notice-level bootstrapping messages at startup
4888 about downloading descriptors. Previously, we'd log a notice
4889 whenever we learned about more routers. Now, we only log a notice
4890 at every 5% of progress. Fixes bug 9963.
4891 - Warn less verbosely when receiving a malformed
4892 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
4894 o Minor features (performance):
4895 - If we're using the pure-C 32-bit curve25519_donna implementation
4896 of curve25519, build it with the -fomit-frame-pointer option to
4897 make it go faster on register-starved hosts. This improves our
4898 handshake performance by about 6% on i386 hosts without nacl.
4901 o Minor features (relay):
4902 - If a circuit timed out for at least 3 minutes, check if we have a
4903 new external IP address, and publish a new descriptor with the new
4904 IP address if it changed. Resolves ticket 2454.
4906 o Minor features (testing):
4907 - If Python is installed, "make check" now runs extra tests beyond
4908 the unit test scripts.
4909 - When bootstrapping a test network, sometimes very few relays get
4910 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
4911 specify a set of relays which should be voted Guard regardless of
4912 their uptime or bandwidth. Addresses ticket 9206.
4914 o Minor features (transparent proxy, *BSD):
4915 - Support FreeBSD's ipfw firewall interface for TransPort ports on
4916 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
4917 10267; patch from "yurivict".
4918 - Support OpenBSD's divert-to rules with the pf firewall for
4919 transparent proxy ports. To enable it, set "TransProxyType
4920 pf-divert". This allows Tor to run a TransPort transparent proxy
4921 port on OpenBSD 4.4 or later without root privileges. See the
4922 pf.conf(5) manual page for information on configuring pf to use
4923 divert-to rules. Closes ticket 10896; patch from Dana Koch.
4925 o Minor bugfixes (bridge client):
4926 - Stop accepting bridge lines containing hostnames. Doing so would
4927 cause clients to perform DNS requests on the hostnames, which was
4928 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
4930 o Minor bugfixes (bridges):
4931 - Avoid potential crashes or bad behavior when launching a
4932 server-side managed proxy with ORPort or ExtORPort temporarily
4933 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
4934 - Fix a bug where the first connection works to a bridge that uses a
4935 pluggable transport with client-side parameters, but we don't send
4936 the client-side parameters on subsequent connections. (We don't
4937 use any pluggable transports with client-side parameters yet,
4938 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
4939 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
4941 o Minor bugfixes (build, auxiliary programs):
4942 - Stop preprocessing the "torify" script with autoconf, since
4943 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
4945 - The tor-fw-helper program now follows the standard convention and
4946 exits with status code "0" on success. Fixes bug 9030; bugfix on
4947 0.2.3.1-alpha. Patch by Arlo Breault.
4948 - Corrected ./configure advice for what openssl dev package you should
4949 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
4951 o Minor bugfixes (client):
4952 - Avoid "Tried to open a socket with DisableNetwork set" warnings
4953 when starting a client with bridges configured and DisableNetwork
4954 set. (Tor launcher starts Tor with DisableNetwork set the first
4955 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
4956 - Improve the log message when we can't connect to a hidden service
4957 because all of the hidden service directory nodes hosting its
4958 descriptor are excluded. Improves on our fix for bug 10722, which
4959 was a bugfix on 0.2.0.10-alpha.
4960 - Raise a control port warning when we fail to connect to all of
4961 our bridges. Previously, we didn't inform the controller, and
4962 the bootstrap process would stall. Fixes bug 11069; bugfix on
4964 - Exit immediately when a process-owning controller exits.
4965 Previously, tor relays would wait for a little while after their
4966 controller exited, as if they had gotten an INT signal -- but this
4967 was problematic, since there was no feedback for the user. To do a
4968 clean shutdown, controllers should send an INT signal and give Tor
4969 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
4970 - Stop attempting to connect to bridges before our pluggable
4971 transports are configured (harmless but resulted in some erroneous
4972 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
4973 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
4974 generating incorrect SOCKS5 responses, and confusing client
4975 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
4977 o Minor bugfixes (client, DNSPort):
4978 - When using DNSPort, try to respond to AAAA requests with AAAA
4979 answers. Previously, we hadn't looked at the request type when
4980 deciding which answer type to prefer. Fixes bug 10468; bugfix on
4982 - When receiving a DNS query for an unsupported record type, reply
4983 with no answer rather than with a NOTIMPL error. This behavior
4984 isn't correct either, but it will break fewer client programs, we
4985 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
4988 o Minor bugfixes (client, logging during bootstrap):
4989 - Only report the first fatal bootstrap error on a given OR
4990 connection. This stops us from telling the controller bogus error
4991 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
4992 - Avoid generating spurious warnings when starting with
4993 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
4996 o Minor bugfixes (closing OR connections):
4997 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
4998 check if it's an or_connection_t and correctly call
4999 connection_or_close_for_error() rather than
5000 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
5002 - When closing all connections on setting DisableNetwork to 1, use
5003 connection_or_close_normally() rather than closing OR connections
5004 out from under the channel layer. Fixes bug 11306; bugfix on
5007 o Minor bugfixes (code correctness):
5008 - Previously we used two temporary files when writing descriptors to
5009 disk; now we only use one. Fixes bug 1376.
5010 - Remove an erroneous (but impossible and thus harmless) pointer
5011 comparison that would have allowed compilers to skip a bounds
5012 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
5013 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
5014 - Fix an always-true assertion in pluggable transports code so it
5015 actually checks what it was trying to check. Fixes bug 10046;
5016 bugfix on 0.2.3.9-alpha. Found by "dcb".
5018 o Minor bugfixes (command line):
5019 - Use a single command-line parser for parsing torrc options on the
5020 command line and for finding special command-line options to avoid
5021 inconsistent behavior for torrc option arguments that have the same
5022 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
5024 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
5025 9573; bugfix on 0.0.9pre5.
5027 o Minor bugfixes (compilation):
5028 - Compile correctly with builds and forks of OpenSSL (such as
5029 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
5030 0.2.1.1-alpha. Patch from "dhill".
5031 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
5032 turned off (that is, without support for v2 link handshakes). Fixes
5033 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
5034 - In routerlist_assert_ok(), don't take the address of a
5035 routerinfo's cache_info member unless that routerinfo is non-NULL.
5036 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
5037 - Fix a large number of false positive warnings from the clang
5038 analyzer static analysis tool. This should make real warnings
5039 easier for clang analyzer to find. Patch from "teor". Closes
5041 - Resolve GCC complaints on OpenBSD about discarding constness in
5042 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
5043 on 0.1.1.23. Patch from Dana Koch.
5044 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
5045 treatment of long and time_t as comparable types. Fixes part of
5046 bug 11633. Patch from Dana Koch.
5047 - When deciding whether to build the 64-bit curve25519
5048 implementation, detect platforms where we can compile 128-bit
5049 arithmetic but cannot link it. Fixes bug 11729; bugfix on
5050 0.2.4.8-alpha. Patch from "conradev".
5051 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
5052 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
5053 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
5055 - Build and run correctly on systems like OpenBSD-current that have
5056 patched OpenSSL to remove get_cipher_by_char and/or its
5057 implementations. Fixes issue 13325.
5059 o Minor bugfixes (controller and command-line):
5060 - If changing a config option via "setconf" fails in a recoverable
5061 way, we used to nonetheless write our new control ports to the
5062 file described by the "ControlPortWriteToFile" option. Now we only
5063 write out that file if we successfully switch to the new config
5064 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
5066 o Minor bugfixes (directory server):
5067 - No longer accept malformed http headers when parsing urls from
5068 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
5069 bugfix on 0.0.6pre1.
5070 - When sending a compressed set of descriptors or microdescriptors,
5071 make sure to finalize the zlib stream. Previously, we would write
5072 all the compressed data, but if the last descriptor we wanted to
5073 send was missing or too old, we would not mark the stream as
5074 finished. This caused problems for decompression tools. Fixes bug
5075 11648; bugfix on 0.1.1.23.
5077 o Minor bugfixes (hidden service):
5078 - Only retry attempts to connect to a chosen rendezvous point 8
5079 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
5081 o Minor bugfixes (interface):
5082 - Reject relative control socket paths and emit a warning. Previously,
5083 single-component control socket paths would be rejected, but Tor
5084 would not log why it could not validate the config. Fixes bug 9258;
5085 bugfix on 0.2.3.16-alpha.
5087 o Minor bugfixes (log messages):
5088 - Fix a bug where clients using bridges would report themselves
5089 as 50% bootstrapped even without a live consensus document.
5090 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
5091 - Suppress a warning where, if there's only one directory authority
5092 in the network, we would complain that votes and signatures cannot
5093 be uploaded to other directory authorities. Fixes bug 10842;
5094 bugfix on 0.2.2.26-beta.
5095 - Report bootstrapping progress correctly when we're downloading
5096 microdescriptors. We had updated our "do we have enough microdescs
5097 to begin building circuits?" logic most recently in 0.2.4.10-alpha
5098 (see bug 5956), but we left the bootstrap status event logic at
5099 "how far through getting 1/4 of them are we?" Fixes bug 9958;
5100 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
5102 o Minor bugfixes (logging):
5103 - Downgrade "Unexpected onionskin length after decryption" warning
5104 to a protocol-warn, since there's nothing relay operators can do
5105 about a client that sends them a malformed create cell. Resolves
5106 bug 12996; bugfix on 0.0.6rc1.
5107 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
5108 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
5109 - When logging information about an EXTEND2 or EXTENDED2 cell, log
5110 their names correctly. Fixes part of bug 12700; bugfix
5112 - When logging information about a relay cell whose command we don't
5113 recognize, log its command as an integer. Fixes part of bug 12700;
5114 bugfix on 0.2.1.10-alpha.
5115 - Escape all strings from the directory connection before logging
5116 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
5117 - Squelch a spurious LD_BUG message "No origin circuit for
5118 successful SOCKS stream" in certain hidden service failure cases;
5120 - Downgrade the severity of the 'unexpected sendme cell from client'
5121 from 'warn' to 'protocol warning'. Closes ticket 8093.
5123 o Minor bugfixes (misc code correctness):
5124 - In munge_extrainfo_into_routerinfo(), check the return value of
5125 memchr(). This would have been a serious issue if we ever passed
5126 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
5128 - On the chance that somebody manages to build Tor on a
5129 platform where time_t is unsigned, correct the way that
5130 microdesc_add_to_cache() handles negative time arguments.
5131 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
5132 - Fix various instances of undefined behavior in channeltls.c,
5133 tor_memmem(), and eventdns.c that would cause us to construct
5134 pointers to memory outside an allocated object. (These invalid
5135 pointers were not accessed, but C does not even allow them to
5136 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
5137 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
5138 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
5139 fix some miscellaneous errors in our tests and codebase. Fixes bug
5140 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
5141 - Always check return values for unlink, munmap, UnmapViewOfFile;
5142 check strftime return values more often. In some cases all we can
5143 do is report a warning, but this may help prevent deeper bugs from
5144 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
5146 - Fix numerous warnings from the clang "scan-build" static analyzer.
5147 Some of these are programming style issues; some of them are false
5148 positives that indicated awkward code; some are undefined behavior
5149 cases related to constructing (but not using) invalid pointers;
5150 some are assumptions about API behavior; some are (harmlessly)
5151 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
5152 correct; and one or two are genuine bugs that weren't reachable
5153 from the rest of the program. Fixes bug 8793; bugfixes on many,
5156 o Minor bugfixes (node selection):
5157 - If ExcludeNodes is set, consider non-excluded hidden service
5158 directory servers before excluded ones. Do not consider excluded
5159 hidden service directory servers at all if StrictNodes is
5160 set. (Previously, we would sometimes decide to connect to those
5161 servers, and then realize before we initiated a connection that
5162 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
5164 - If we set the ExitNodes option but it doesn't include any nodes
5165 that have the Exit flag, we would choose not to bootstrap. Now we
5166 bootstrap so long as ExitNodes includes nodes which can exit to
5167 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
5169 o Minor bugfixes (performance):
5170 - Avoid a bug where every successful connection made us recompute
5171 the flag telling us whether we have sufficient information to
5172 build circuits. Previously, we would forget our cached value
5173 whenever we successfully opened a channel (or marked a router as
5174 running or not running for any other reason), regardless of
5175 whether we had previously believed the router to be running. This
5176 forced us to run an expensive update operation far too often.
5177 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
5178 - Avoid using tor_memeq() for checking relay cell integrity. This
5179 removes a possible performance bottleneck. Fixes part of bug
5180 12169; bugfix on 0.2.1.31.
5182 o Minor bugfixes (platform-specific):
5183 - When dumping a malformed directory object to disk, save it in
5184 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
5186 - Don't report failures from make_socket_reuseable() on incoming
5187 sockets on OSX: this can happen when incoming connections close
5188 early. Fixes bug 10081.
5190 o Minor bugfixes (pluggable transports):
5191 - Avoid another 60-second delay when starting Tor in a pluggable-
5192 transport-using configuration when we already have cached
5193 descriptors for our bridges. Fixes bug 11965; bugfix
5196 o Minor bugfixes (protocol correctness):
5197 - When receiving a VERSIONS cell with an odd number of bytes, close
5198 the connection immediately since the cell is malformed. Fixes bug
5199 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
5202 o Minor bugfixes (relay, other):
5203 - We now drop CREATE cells for already-existent circuit IDs and for
5204 zero-valued circuit IDs, regardless of other factors that might
5205 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
5207 - When rejecting DATA cells for stream_id zero, still count them
5208 against the circuit's deliver window so that we don't fail to send
5209 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
5211 o Minor bugfixes (relay, threading):
5212 - Check return code on spawn_func() in cpuworker code, so that we
5213 don't think we've spawned a nonworking cpuworker and write junk to
5214 it forever. Fix related to bug 4345; bugfix on all released Tor
5215 versions. Found by "skruffy".
5216 - Use a pthread_attr to make sure that spawn_func() cannot return an
5217 error while at the same time launching a thread. Fix related to
5218 bug 4345; bugfix on all released Tor versions. Reported
5221 o Minor bugfixes (relays and bridges):
5222 - Avoid crashing on a malformed resolv.conf file when running a
5223 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
5224 - Non-exit relays no longer launch mock DNS requests to check for
5225 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
5226 non-exit relays stopped servicing DNS requests. Fixes bug 965;
5227 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
5228 - Bridges now report complete directory request statistics. Related
5229 to bug 5824; bugfix on 0.2.2.1-alpha.
5230 - Bridges now never collect statistics that were designed for
5231 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
5233 o Minor bugfixes (testing):
5234 - Fix all valgrind warnings produced by the unit tests. There were
5235 over a thousand memory leak warnings previously, mostly produced
5236 by forgetting to free things in the unit test code. Fixes bug
5237 11618, bugfixes on many versions of Tor.
5239 o Minor bugfixes (tor-fw-helper):
5240 - Give a correct log message when tor-fw-helper fails to launch.
5241 (Previously, we would say something like "tor-fw-helper sent us a
5242 string we could not parse".) Fixes bug 9781; bugfix
5245 o Minor bugfixes (trivial memory leaks):
5246 - Fix a small memory leak when signing a directory object. Fixes bug
5247 11275; bugfix on 0.2.4.13-alpha.
5248 - Resolve some memory leaks found by coverity in the unit tests, on
5249 exit in tor-gencert, and on a failure to compute digests for our
5250 own keys when generating a v3 networkstatus vote. These leaks
5251 should never have affected anyone in practice.
5253 o Code simplification and refactoring:
5254 - Remove some old fallback code designed to keep Tor clients working
5255 in a network with only two working relays. Elsewhere in the code we
5256 have long since stopped supporting such networks, so there wasn't
5257 much point in keeping it around. Addresses ticket 9926.
5258 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
5259 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
5260 - Extract the common duplicated code for creating a subdirectory
5261 of the data directory and writing to a file in it. Fixes ticket
5262 4282; patch from Peter Retzlaff.
5263 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
5264 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
5265 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
5266 - Add a set of accessor functions for the circuit timeout data
5267 structure. Fixes ticket 6153; patch from "piet".
5268 - Clean up exit paths from connection_listener_new(). Closes ticket
5269 8789. Patch from Arlo Breault.
5270 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
5271 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
5272 - Use a doubly-linked list to implement the global circuit list.
5273 Resolves ticket 9108. Patch from Marek Majkowski.
5274 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
5275 - Remove constants and tests for PKCS1 padding; it's insecure and
5276 shouldn't be used for anything new. Fixes bug 8792; patch
5278 - Remove instances of strcpy() from the unit tests. They weren't
5279 hurting anything, since they were only in the unit tests, but it's
5280 embarassing to have strcpy() in the code at all, and some analysis
5281 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
5282 0.2.3.8-alpha. Patch from Arlo Breault.
5283 - Remove is_internal_IP() function. Resolves ticket 4645.
5284 - Remove unused function circuit_dump_by_chan from circuitlist.c.
5285 Closes issue 9107; patch from "marek".
5286 - Change our use of the ENUM_BF macro to avoid declarations that
5288 - Get rid of router->address, since in all cases it was just the
5289 string representation of router->addr. Resolves ticket 5528.
5292 - Adjust the URLs in the README to refer to the new locations of
5293 several documents on the website. Fixes bug 12830. Patch from
5295 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
5297 - Update manpage to describe some of the files you can expect to
5298 find in Tor's DataDirectory. Addresses ticket 9839.
5299 - Clean up several option names in the manpage to match their real
5300 names, add the missing documentation for a couple of testing and
5301 directory authority options, remove the documentation for a
5302 V2-directory fetching option that no longer exists. Resolves
5304 - Correct the documenation so that it lists the correct directory
5305 for the stats files. (They are in a subdirectory called "stats",
5307 - In the manpage, move more authority-only options into the
5308 directory authority section so that operators of regular directory
5309 caches don't get confused.
5310 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
5311 11061; bugfix on 0.2.4.7-alpha.
5312 - Resolve warnings from Doxygen.
5313 - Document in the manpage that "KBytes" may also be written as
5314 "kilobytes" or "KB", that "Kbits" may also be written as
5315 "kilobits", and so forth. Closes ticket 9222.
5316 - Document that the ClientOnly config option overrides ORPort.
5317 Our old explanation made ClientOnly sound as though it did
5318 nothing at all. Resolves bug 9059.
5319 - Explain that SocksPolicy, DirPolicy, and similar options don't
5320 take port arguments. Fixes the other part of ticket 11108.
5321 - Fix a comment about the rend_server_descriptor_t.protocols field
5322 to more accurately describe its range. Also, make that field
5323 unsigned, to more accurately reflect its usage. Fixes bug 9099;
5324 bugfix on 0.2.1.5-alpha.
5325 - Fix the manpage's description of HiddenServiceAuthorizeClient:
5326 the maximum client name length is 16, not 19. Fixes bug 11118;
5327 bugfix on 0.2.1.6-alpha.
5330 - The contrib directory has been sorted and tidied. Before, it was
5331 an unsorted dumping ground for useful and not-so-useful things.
5332 Now, it is divided based on functionality, and the items which
5333 seemed to be nonfunctional or useless have been removed. Resolves
5334 ticket 8966; based on patches from "rl1987".
5336 o Removed code and features:
5337 - Clients now reject any directory authority certificates lacking
5338 a dir-key-crosscert element. These have been included since
5339 0.2.1.9-alpha, so there's no real reason for them to be optional
5340 any longer. Completes proposal 157. Resolves ticket 10162.
5341 - Remove all code that existed to support the v2 directory system,
5342 since there are no longer any v2 directory authorities. Resolves
5344 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
5345 options, which were used for designating authorities as "Hidden
5346 service authorities". There has been no use of hidden service
5347 authorities since 0.2.2.1-alpha, when we stopped uploading or
5348 downloading v0 hidden service descriptors. Fixes bug 10881; also
5349 part of a fix for bug 10841.
5350 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
5351 and MTBF calculations, but that nobody was using. Fixes bug 11742.
5352 - The TunnelDirConns and PreferTunnelledDirConns options no longer
5353 exist; tunneled directory connections have been available since
5354 0.1.2.5-alpha, and turning them off is not a good idea. This is a
5355 brute-force fix for 10849, where "TunnelDirConns 0" would break
5357 - Remove all code for the long unused v1 directory protocol.
5358 Resolves ticket 11070.
5359 - Remove all remaining code related to version-0 hidden service
5360 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
5361 the rest of bug 10841.
5362 - Remove migration code from when we renamed the "cached-routers"
5363 file to "cached-descriptors" back in 0.2.0.8-alpha. This
5364 incidentally resolves ticket 6502 by cleaning up the related code
5365 a bit. Patch from Akshay Hebbar.
5367 o Test infrastructure:
5368 - Tor now builds each source file in two modes: a mode that avoids
5369 exposing identifiers needlessly, and another mode that exposes
5370 more identifiers for testing. This lets the compiler do better at
5371 optimizing the production code, while enabling us to take more
5372 radical measures to let the unit tests test things.
5373 - The production builds no longer include functions used only in
5374 the unit tests; all functions exposed from a module only for
5375 unit-testing are now static in production builds.
5376 - Add an --enable-coverage configuration option to make the unit
5377 tests (and a new src/or/tor-cov target) to build with gcov test
5379 - Update to the latest version of tinytest.
5380 - Improve the tinytest implementation of string operation tests so
5381 that comparisons with NULL strings no longer crash the tests; they
5382 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
5383 - New macros in test.h to simplify writing mock-functions for unit
5384 tests. Part of ticket 11507. Patch from Dana Koch.
5385 - We now have rudimentary function mocking support that our unit
5386 tests can use to test functions in isolation. Function mocking
5387 lets the tests temporarily replace a function's dependencies with
5388 stub functions, so that the tests can check the function without
5389 invoking the other functions it calls.
5392 - Complete tests for the status.c module. Resolves ticket 11507.
5393 Patch from Dana Koch.
5394 - Add more unit tests for the <circid,channel>->circuit map, and
5395 the destroy-cell-tracking code to fix bug 7912.
5396 - Unit tests for failing cases of the TAP onion handshake.
5397 - More unit tests for address-manipulation functions.
5399 o Distribution (systemd):
5400 - Include a tor.service file in contrib/dist for use with systemd.
5401 Some distributions will be able to use this file unmodified;
5402 others will need to tweak it, or write their own. Patch from Jamie
5403 Nguyen; resolves ticket 8368.
5404 - Verify configuration file via ExecStartPre in the systemd unit
5405 file. Patch from intrigeri; resolves ticket 12730.
5406 - Explicitly disable RunAsDaemon in the systemd unit file. Our
5407 current systemd unit uses "Type = simple", so systemd does not
5408 expect tor to fork. If the user has "RunAsDaemon 1" in their
5409 torrc, then things won't work as expected. This is e.g. the case
5410 on Debian (and derivatives), since there we pass "--defaults-torrc
5411 /usr/share/tor/tor-service-defaults-torrc" (that contains
5412 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
5416 Changes in version 0.2.4.25 - 2014-10-20
5417 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
5418 (even though POODLE does not affect Tor). It also works around a crash
5419 bug caused by some operating systems' response to the "POODLE" attack
5420 (which does affect Tor).
5422 o Major security fixes (also in 0.2.5.9-rc):
5423 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
5424 today support TLS 1.0 or later, so we can safely turn off support
5425 for this old (and insecure) protocol. Fixes bug 13426.
5427 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
5428 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
5429 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
5430 13471. This is a workaround for an OpenSSL bug.
5433 Changes in version 0.2.4.24 - 2014-09-22
5434 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
5435 connecting to hidden services, and it updates the location of one of
5436 the directory authorities.
5439 - Clients now send the correct address for their chosen rendezvous
5440 point when trying to access a hidden service. They used to send
5441 the wrong address, which would still work some of the time because
5442 they also sent the identity digest of the rendezvous point, and if
5443 the hidden service happened to try connecting to the rendezvous
5444 point from a relay that already had a connection open to it,
5445 the relay would reuse that connection. Now connections to hidden
5446 services should be more robust and faster. Also, this bug meant
5447 that clients were leaking to the hidden service whether they were
5448 on a little-endian (common) or big-endian (rare) system, which for
5449 some users might have reduced their anonymity. Fixes bug 13151;
5450 bugfix on 0.2.1.5-alpha.
5452 o Directory authority changes:
5453 - Change IP address for gabelmoo (v3 directory authority).
5455 o Minor features (geoip):
5456 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
5460 Changes in version 0.2.4.23 - 2014-07-28
5461 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
5462 guard rotation, and also backports several important fixes from the
5463 Tor 0.2.5 alpha release series.
5466 - Clients now look at the "usecreatefast" consensus parameter to
5467 decide whether to use CREATE_FAST or CREATE cells for the first hop
5468 of their circuit. This approach can improve security on connections
5469 where Tor's circuit handshake is stronger than the available TLS
5470 connection security levels, but the tradeoff is more computational
5471 load on guard relays. Implements proposal 221. Resolves ticket 9386.
5472 - Make the number of entry guards configurable via a new
5473 NumEntryGuards consensus parameter, and the number of directory
5474 guards configurable via a new NumDirectoryGuards consensus
5475 parameter. Implements ticket 12688.
5478 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
5479 implementation that caused incorrect results on 32-bit
5480 implementations when certain malformed inputs were used along with
5481 a small class of private ntor keys. This bug does not currently
5482 appear to allow an attacker to learn private keys or impersonate a
5483 Tor server, but it could provide a means to distinguish 32-bit Tor
5484 implementations from 64-bit Tor implementations. Fixes bug 12694;
5485 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
5489 - Warn and drop the circuit if we receive an inbound 'relay early'
5490 cell. Those used to be normal to receive on hidden service circuits
5491 due to bug 1038, but the buggy Tor versions are long gone from
5492 the network so we can afford to resume watching for them. Resolves
5493 the rest of bug 1038; bugfix on 0.2.1.19.
5494 - Correct a confusing error message when trying to extend a circuit
5495 via the control protocol but we don't know a descriptor or
5496 microdescriptor for one of the specified relays. Fixes bug 12718;
5497 bugfix on 0.2.3.1-alpha.
5498 - Avoid an illegal read from stack when initializing the TLS
5499 module using a version of OpenSSL without all of the ciphers
5500 used by the v2 link handshake. Fixes bug 12227; bugfix on
5501 0.2.4.8-alpha. Found by "starlight".
5504 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
5508 Changes in version 0.2.4.22 - 2014-05-16
5509 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
5510 alpha release series. These include blocking all authority signing
5511 keys that may have been affected by the OpenSSL "heartbleed" bug,
5512 choosing a far more secure set of TLS ciphersuites by default, closing
5513 a couple of memory leaks that could be used to run a target relay out
5514 of RAM, and several others.
5516 o Major features (security, backport from 0.2.5.4-alpha):
5517 - Block authority signing keys that were used on authorities
5518 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
5519 don't have any evidence that these keys _were_ compromised; we're
5520 doing this to be prudent.) Resolves ticket 11464.
5522 o Major bugfixes (security, OOM):
5523 - Fix a memory leak that could occur if a microdescriptor parse
5524 fails during the tokenizing step. This bug could enable a memory
5525 exhaustion attack by directory servers. Fixes bug 11649; bugfix
5528 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
5529 - The relay ciphersuite list is now generated automatically based on
5530 uniform criteria, and includes all OpenSSL ciphersuites with
5531 acceptable strength and forward secrecy. Previously, we had left
5532 some perfectly fine ciphersuites unsupported due to omission or
5533 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
5534 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
5535 - Relays now trust themselves to have a better view than clients of
5536 which TLS ciphersuites are better than others. (Thanks to bug
5537 11513, the relay list is now well-considered, whereas the client
5538 list has been chosen mainly for anti-fingerprinting purposes.)
5539 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
5540 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
5541 AES128. Resolves ticket 11528.
5542 - Clients now try to advertise the same list of ciphersuites as
5543 Firefox 28. This change enables selection of (fast) GCM
5544 ciphersuites, disables some strange old ciphers, and stops
5545 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
5546 Resolves ticket 11438.
5548 o Minor bugfixes (configuration, security):
5549 - When running a hidden service, do not allow TunneledDirConns 0:
5550 trying to set that option together with a hidden service would
5551 otherwise prevent the hidden service from running, and also make
5552 it publish its descriptors directly over HTTP. Fixes bug 10849;
5553 bugfix on 0.2.1.1-alpha.
5555 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
5556 - Avoid sending a garbage value to the controller when a circuit is
5557 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
5559 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
5560 - Stop leaking memory when we successfully resolve a PTR record.
5561 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
5563 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
5564 - Avoid 60-second delays in the bootstrapping process when Tor is
5565 launching for a second time while using bridges. Fixes bug 9229;
5566 bugfix on 0.2.0.3-alpha.
5568 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
5569 - Give the correct URL in the warning message when trying to run a
5570 relay on an ancient version of Windows. Fixes bug 9393.
5572 o Minor bugfixes (compilation):
5573 - Fix a compilation error when compiling with --disable-curve25519.
5574 Fixes bug 9700; bugfix on 0.2.4.17-rc.
5577 - Downgrade the warning severity for the the "md was still
5578 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
5579 for trying to diagnose this bug, and the current warning in
5580 earlier versions of tor achieves nothing useful. Addresses warning
5583 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
5584 - When we run out of usable circuit IDs on a channel, log only one
5585 warning for the whole channel, and describe how many circuits
5586 there were on the channel. Fixes part of ticket 11553.
5588 o Minor features (security, backport from 0.2.5.4-alpha):
5589 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
5590 leave the default at 8GBytes), to better support Raspberry Pi
5591 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
5593 o Documentation (backport from 0.2.5.4-alpha):
5594 - Correctly document that we search for a system torrc file before
5595 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
5599 Changes in version 0.2.4.21 - 2014-02-28
5600 Tor 0.2.4.21 further improves security against potential adversaries who
5601 find breaking 1024-bit crypto doable, and backports several stability
5602 and robustness patches from the 0.2.5 branch.
5604 o Major features (client security):
5605 - When we choose a path for a 3-hop circuit, make sure it contains
5606 at least one relay that supports the NTor circuit extension
5607 handshake. Otherwise, there is a chance that we're building
5608 a circuit that's worth attacking by an adversary who finds
5609 breaking 1024-bit crypto doable, and that chance changes the game
5610 theory. Implements ticket 9777.
5613 - Do not treat streams that fail with reason
5614 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
5615 since it could also indicate an ENETUNREACH connection error. Fixes
5616 part of bug 10777; bugfix on 0.2.4.8-alpha.
5618 o Code simplification and refactoring:
5619 - Remove data structures which were introduced to implement the
5620 CellStatistics option: they are now redundant with the new timestamp
5621 field in the regular packed_cell_t data structure, which we did
5622 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
5625 - Always clear OpenSSL bignums before freeing them -- even bignums
5626 that don't contain secrets. Resolves ticket 10793. Patch by
5628 - Build without warnings under clang 3.4. (We have some macros that
5629 define static functions only some of which will get used later in
5630 the module. Starting with clang 3.4, these give a warning unless the
5631 unused attribute is set on them.) Resolves ticket 10904.
5632 - Update geoip and geoip6 files to the February 7 2014 Maxmind
5633 GeoLite2 Country database.
5636 - Set the listen() backlog limit to the largest actually supported
5637 on the system, not to the value in a header file. Fixes bug 9716;
5638 bugfix on every released Tor.
5639 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
5640 exit node as a NOROUTE error, not an INTERNAL error, since they
5641 can apparently happen when trying to connect to the wrong sort
5642 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
5643 - Fix build warnings about missing "a2x" comment when building the
5644 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
5645 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
5646 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
5647 not entirely remove it from the connection lists. Fixes bug 9602;
5648 bugfix on 0.2.4.4-alpha.
5649 - Fix a segmentation fault in our benchmark code when running with
5650 Fedora's OpenSSL package, or any other OpenSSL that provides
5651 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
5652 - Turn "circuit handshake stats since last time" log messages into a
5653 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
5655 o Documentation fixes:
5656 - Document that all but one DirPort entry must have the NoAdvertise
5657 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
5660 Changes in version 0.2.4.20 - 2013-12-22
5661 Tor 0.2.4.20 fixes potentially poor random number generation for users
5662 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
5663 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
5664 and 4) have no state file in their DataDirectory (as would happen on
5665 first start). Users who generated relay or hidden service identity
5666 keys in such a situation should discard them and generate new ones.
5668 This release also fixes a logic error that caused Tor clients to build
5669 many more preemptive circuits than they actually need.
5672 - Do not allow OpenSSL engines to replace the PRNG, even when
5673 HardwareAccel is set. The only default builtin PRNG engine uses
5674 the Intel RDRAND instruction to replace the entire PRNG, and
5675 ignores all attempts to seed it with more entropy. That's
5676 cryptographically stupid: the right response to a new alleged
5677 entropy source is never to discard all previously used entropy
5678 sources. Fixes bug 10402; works around behavior introduced in
5679 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
5681 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
5682 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
5683 - Avoid launching spurious extra circuits when a stream is pending.
5684 This fixes a bug where any circuit that _wasn't_ unusable for new
5685 streams would be treated as if it were, causing extra circuits to
5686 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
5689 - Avoid a crash bug when starting with a corrupted microdescriptor
5690 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
5691 - If we fail to dump a previously cached microdescriptor to disk, avoid
5692 freeing duplicate data later on. Fixes bug 10423; bugfix on
5693 0.2.4.13-alpha. Spotted by "bobnomnom".
5696 Changes in version 0.2.4.19 - 2013-12-11
5697 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
5698 (1986-2013). Aaron worked on diverse projects including helping to guide
5699 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
5700 transparency to the U.S government's PACER documents, and contributing
5701 design and development for Tor and Tor2Web. Aaron was one of the latest
5702 martyrs in our collective fight for civil liberties and human rights,
5703 and his death is all the more painful because he was one of us.
5705 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
5706 a new circuit handshake and link encryption that use ECC to provide
5707 better security and efficiency; makes relays better manage circuit
5708 creation requests; uses "directory guards" to reduce client enumeration
5709 risks; makes bridges collect and report statistics about the pluggable
5710 transports they support; cleans up and improves our geoip database;
5711 gets much closer to IPv6 support for clients, bridges, and relays; makes
5712 directory authorities use measured bandwidths rather than advertised
5713 ones when computing flags and thresholds; disables client-side DNS
5714 caching to reduce tracking risks; and fixes a big bug in bridge
5715 reachability testing. This release introduces two new design
5716 abstractions in the code: a new "channel" abstraction between circuits
5717 and or_connections to allow for implementing alternate relay-to-relay
5718 transports, and a new "circuitmux" abstraction storing the queue of
5719 circuits for a channel. The release also includes many stability,
5720 security, and privacy fixes.
5722 o Major features (new circuit handshake):
5723 - Tor now supports a new circuit extension handshake designed by Ian
5724 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
5725 circuit extension handshake, later called "TAP", was a bit slow
5726 (especially on the relay side), had a fragile security proof, and
5727 used weaker keys than we'd now prefer. The new circuit handshake
5728 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
5729 function, making it significantly more secure than the older
5730 handshake, and significantly faster. Tor can use one of two built-in
5731 pure-C curve25519-donna implementations by Adam Langley, or it
5732 can link against the "nacl" library for a tuned version if present.
5734 The built-in version is very fast for 64-bit systems when building
5735 with GCC. The built-in 32-bit version is still faster than the
5736 old TAP protocol, but using libnacl is better on most such hosts.
5738 Implements proposal 216; closes ticket 7202.
5740 o Major features (better link encryption):
5741 - Relays can now enable the ECDHE TLS ciphersuites when available
5742 and appropriate. These ciphersuites let us negotiate forward-secure
5743 TLS secret keys more safely and more efficiently than with our
5744 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
5745 public relays prefer the (faster) P224 group, and bridges prefer
5746 the (more common) P256 group; you can override this with the
5749 This feature requires clients running 0.2.3.17-beta or later,
5750 and requires both sides to be running OpenSSL 1.0.0 or later
5751 with ECC support. OpenSSL 1.0.1, with the compile-time option
5752 "enable-ec_nistp_64_gcc_128", is highly recommended.
5754 Implements the relay side of proposal 198; closes ticket 7200.
5756 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
5757 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
5758 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
5759 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
5760 them to solve bug 6033.)
5762 o Major features (relay performance):
5763 - Instead of limiting the number of queued onionskins (aka circuit
5764 create requests) to a fixed, hard-to-configure number, we limit
5765 the size of the queue based on how many we expect to be able to
5766 process in a given amount of time. We estimate the time it will
5767 take to process an onionskin based on average processing time
5768 of previous onionskins. Closes ticket 7291. You'll never have to
5769 configure MaxOnionsPending again.
5770 - Relays process the new "NTor" circuit-level handshake requests
5771 with higher priority than the old "TAP" circuit-level handshake
5772 requests. We still process some TAP requests to not totally starve
5773 0.2.3 clients when NTor becomes popular. A new consensus parameter
5774 "NumNTorsPerTAP" lets us tune the balance later if we need to.
5775 Implements ticket 9574.
5777 o Major features (client bootstrapping resilience):
5778 - Add a new "FallbackDir" torrc option to use when we can't use
5779 a directory mirror from the consensus (either because we lack a
5780 consensus, or because they're all down). Currently, all authorities
5781 are fallbacks by default, and there are no other default fallbacks,
5782 but that will change. This option will allow us to give clients a
5783 longer list of servers to try to get a consensus from when first
5784 connecting to the Tor network, and thereby reduce load on the
5785 directory authorities. Implements proposal 206, "Preconfigured
5786 directory sources for bootstrapping". We also removed the old
5787 "FallbackNetworkstatus" option, since we never got it working well
5788 enough to use it. Closes bug 572.
5789 - If we have no circuits open, use a relaxed timeout (the
5790 95th-percentile cutoff) until a circuit succeeds. This heuristic
5791 should allow Tor to succeed at building circuits even when the
5792 network connection drastically changes. Should help with bug 3443.
5794 o Major features (use of guards):
5795 - Support directory guards (proposal 207): when possible, clients now
5796 use their entry guards for non-anonymous directory requests. This
5797 can help prevent client enumeration. Note that this behavior only
5798 works when we have a usable consensus directory, and when options
5799 about what to download are more or less standard. In the future we
5800 should re-bootstrap from our guards, rather than re-bootstrapping
5801 from the preconfigured list of directory sources that ships with
5802 Tor. Resolves ticket 6526.
5803 - Raise the default time that a client keeps an entry guard from
5804 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
5805 2012 paper. (We would make it even longer, but we need better client
5806 load balancing first.) Also, make the guard lifetime controllable
5807 via a new GuardLifetime torrc option and a GuardLifetime consensus
5808 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
5810 o Major features (bridges with pluggable transports):
5811 - Bridges now report the pluggable transports they support to the
5812 bridge authority, so it can pass the supported transports on to
5813 bridgedb and/or eventually do reachability testing. Implements
5815 - Automatically forward the TCP ports of pluggable transport
5816 proxies using tor-fw-helper if PortForwarding is enabled. Implements
5819 o Major features (geoip database):
5820 - Maxmind began labelling Tor relays as being in country "A1",
5821 which breaks by-country node selection inside Tor. Now we use a
5822 script to replace "A1" ("Anonymous Proxy") entries in our geoip
5823 file with real country codes. This script fixes about 90% of "A1"
5824 entries automatically and uses manual country code assignments to
5825 fix the remaining 10%. See src/config/README.geoip for details.
5827 - Add GeoIP database for IPv6 addresses. The new config option
5829 - Update to the October 2 2013 Maxmind GeoLite Country database.
5831 o Major features (IPv6):
5832 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
5833 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
5834 to happen. Implements ticket 5535.
5835 - All kind of relays, not just bridges, can now advertise an IPv6
5836 OR port. Implements ticket 6362.
5837 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
5838 connectivity, then set the IPv6Exit flag to 1. Also make sure your
5839 exit policy reads as you would like: the address * applies to all
5840 address families, whereas *4 is IPv4 address only, and *6 is IPv6
5841 addresses only. On the client side, you'll need to wait for enough
5842 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
5843 and use Socks5. Closes ticket 5547, implements proposal 117 as
5844 revised in proposal 208.
5845 - Bridge authorities now accept IPv6 bridge addresses and include
5846 them in network status documents. Implements ticket 5534.
5847 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
5849 o Major features (directory authorities):
5850 - Directory authorities now prefer using measured bandwidths to
5851 advertised ones when computing flags and thresholds. Resolves
5853 - Directory authorities that vote measured bandwidths about more
5854 than a threshold number of relays now treat relays with
5855 unmeasured bandwidths as having bandwidth 0 when computing their
5856 flags. Resolves ticket 8435.
5857 - Directory authorities now support a new consensus method (17)
5858 where they cap the published bandwidth of relays for which
5859 insufficient bandwidth measurements exist. Fixes part of bug 2286.
5860 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
5861 serve any v2 directory information. Now we can test disabling the
5862 old deprecated v2 directory format, and see whether doing so has
5863 any effect on network load. Begins to fix bug 6783.
5865 o Major features (build and portability):
5866 - Switch to a nonrecursive Makefile structure. Now instead of each
5867 Makefile.am invoking other Makefile.am's, there is a master
5868 Makefile.am that includes the others. This change makes our build
5869 process slightly more maintainable, and improves parallelism for
5870 building with make -j. Original patch by Stewart Smith; various
5871 fixes by Jim Meyering.
5872 - Where available, we now use automake's "silent" make rules by
5873 default, so that warnings are easier to spot. You can get the old
5874 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
5875 - Resume building correctly with MSVC and Makefile.nmake. This patch
5876 resolves numerous bugs and fixes reported by ultramage, including
5877 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
5879 o Security features:
5880 - Switch to a completely time-invariant approach for picking nodes
5881 weighted by bandwidth. Our old approach would run through the
5882 part of the loop after it had made its choice slightly slower
5883 than it ran through the part of the loop before it had made its
5884 choice. Addresses ticket 6538.
5885 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
5886 by tor2web clients allows hidden services to identify tor2web
5887 clients through their repeated selection of the same rendezvous
5888 and introduction point circuit endpoints (their guards). Resolves
5891 o Major bugfixes (relay denial of service):
5892 - When we have too much memory queued in circuits (according to a new
5893 MaxMemInCellQueues option), close the circuits that have the oldest
5894 queued cells, on the theory that those are most responsible for
5895 us running low on memory. This prevents us from running out of
5896 memory as a relay if circuits fill up faster than they can be
5897 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
5898 Tor. This bug is a further fix beyond bug 6252, whose fix was
5899 merged into 0.2.3.21-rc.
5900 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
5901 ID: these could be used to create unexpected streams and circuits
5902 which would count as "present" to some parts of Tor but "absent"
5903 to others, leading to zombie circuits and streams or to a bandwidth
5904 denial-of-service. Fixes bug 7889; bugfix on every released version
5905 of Tor. Reported by "oftc_must_be_destroyed".
5906 - Avoid a bug where our response to TLS renegotiation under certain
5907 network conditions could lead to a busy-loop, with 100% CPU
5908 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
5910 o Major bugfixes (asserts, crashes, leaks):
5911 - Prevent the get_freelists() function from running off the end of
5912 the list of freelists if it somehow gets an unrecognized
5913 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
5915 - Avoid a memory leak where we would leak a consensus body when we
5916 find that a consensus which we couldn't previously verify due to
5917 missing certificates is now verifiable. Fixes bug 8719; bugfix
5919 - If we are unable to save a microdescriptor to the journal, do not
5920 drop it from memory and then reattempt downloading it. Fixes bug
5921 9645; bugfix on 0.2.2.6-alpha.
5922 - Fix an assertion failure that would occur when disabling the
5923 ORPort setting on a running Tor process while accounting was
5924 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
5925 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
5926 when an exit connection with optimistic data succeeds immediately
5927 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
5929 - Fix a memory leak that would occur whenever a configuration
5930 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
5932 o Major bugfixes (relay rate limiting):
5933 - When a TLS write is partially successful but incomplete, remember
5934 that the flushed part has been flushed, and notice that bytes were
5935 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
5936 bugfix on Tor 0.1.0.5-rc.
5937 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
5938 to 1GB/1GB. The previous defaults were intended to be "basically
5939 infinite", but it turns out they're now limiting our 100mbit+
5940 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
5941 last time we raised it).
5942 - No longer stop reading or writing on cpuworker connections when
5943 our rate limiting buckets go empty. Now we should handle circuit
5944 handshake requests more promptly. Resolves bug 9731.
5946 o Major bugfixes (client-side privacy):
5947 - When we mark a circuit as unusable for new circuits, have it
5948 continue to be unusable for new circuits even if MaxCircuitDirtiness
5949 is increased too much at the wrong time, or the system clock jumps
5950 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
5951 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
5952 which have resolved to internal addresses") is set, apply that
5953 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
5954 - When an exit relay rejects a stream with reason "exit policy", but
5955 we only know an exit policy summary (e.g. from the microdesc
5956 consensus) for it, do not mark the relay as useless for all exiting.
5957 Instead, mark just the circuit as unsuitable for that particular
5958 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
5960 o Major bugfixes (stream isolation):
5961 - Allow applications to get proper stream isolation with
5962 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
5963 username/password authentication also offer "no authentication". Tor
5964 had previously preferred "no authentication", so the applications
5965 never actually sent Tor their auth details. Now Tor selects
5966 username/password authentication if it's offered. You can disable
5967 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
5968 bug 8117; bugfix on 0.2.3.3-alpha.
5969 - Follow the socks5 protocol when offering username/password
5970 authentication. The fix for bug 8117 exposed this bug, and it
5971 turns out real-world applications like Pidgin do care. Bugfix on
5972 0.2.3.2-alpha; fixes bug 8879.
5974 o Major bugfixes (client circuit building):
5975 - Alter circuit build timeout measurement to start at the point
5976 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
5977 initialization). This should make our timeout measurements more
5978 uniform. Previously, we were sometimes including ORconn setup time
5979 in our circuit build time measurements. Should resolve bug 3443.
5980 - If the circuit build timeout logic is disabled (via the consensus,
5981 or because we are an authority), then don't build testing circuits.
5982 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
5984 o Major bugfixes (client-side DNS):
5985 - Turn off the client-side DNS cache by default. Updating and using
5986 the DNS cache is now configurable on a per-client-port
5987 level. SOCKSPort, DNSPort, etc lines may now contain
5988 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
5989 cache these types of DNS answers when we receive them from an
5990 exit node in response to an application request on this port, and
5991 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
5992 cached DNS answers of these types, we shouldn't use them. It's
5993 potentially risky to use cached DNS answers at the client, since
5994 doing so can indicate to one exit what answers we've gotten
5995 for DNS lookups in the past. With IPv6, this becomes especially
5996 problematic. Using cached DNS answers for requests on the same
5997 circuit would present less linkability risk, since all traffic
5998 on a circuit is already linkable, but it would also provide
5999 little performance benefit: the exit node caches DNS replies
6000 too. Implements a simplified version of Proposal 205. Implements
6003 o Major bugfixes (hidden service privacy):
6004 - Limit hidden service descriptors to at most ten introduction
6005 points, to slow one kind of guard enumeration. Fixes bug 9002;
6006 bugfix on 0.1.1.11-alpha.
6008 o Major bugfixes (directory fetching):
6009 - If the time to download the next old-style networkstatus is in
6010 the future, do not decline to consider whether to download the
6011 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
6013 - We used to always request authority certificates by identity digest,
6014 meaning we'd get the newest one even when we wanted one with a
6015 different signing key. Then we would complain about being given
6016 a certificate we already had, and never get the one we really
6017 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
6018 resource to request the one we want. Fixes bug 5595; bugfix on
6021 o Major bugfixes (bridge reachability):
6022 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
6023 previously they did not, which prevented them from receiving
6024 successful connections from relays for self-test or bandwidth
6025 testing. Also, when a relay is extending a circuit to a bridge,
6026 it needs to send a NETINFO cell, even when the bridge hasn't sent
6027 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
6029 o Major bugfixes (control interface):
6030 - When receiving a new configuration file via the control port's
6031 LOADCONF command, do not treat the defaults file as absent.
6032 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
6034 o Major bugfixes (directory authorities):
6035 - Stop marking every relay as having been down for one hour every
6036 time we restart a directory authority. These artificial downtimes
6037 were messing with our Stable and Guard flag calculations. Fixes
6038 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
6039 - When computing directory thresholds, ignore any rejected-as-sybil
6040 nodes during the computation so that they can't influence Fast,
6041 Guard, etc. (We should have done this for proposal 109.) Fixes
6043 - When marking a node as a likely sybil, reset its uptime metrics
6044 to zero, so that it cannot time towards getting marked as Guard,
6045 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
6047 - Fix a bug in the voting algorithm that could yield incorrect results
6048 when a non-naming authority declared too many flags. Fixes bug 9200;
6049 bugfix on 0.2.0.3-alpha.
6051 o Internal abstraction features:
6052 - Introduce new channel_t abstraction between circuits and
6053 or_connection_t to allow for implementing alternate OR-to-OR
6054 transports. A channel_t is an abstract object which can either be a
6055 cell-bearing channel, which is responsible for authenticating and
6056 handshaking with the remote OR and transmitting cells to and from
6057 it, or a listening channel, which spawns new cell-bearing channels
6058 at the request of remote ORs. Implements part of ticket 6465.
6059 - Make a channel_tls_t subclass of channel_t, adapting it to the
6060 existing or_connection_t code. The V2/V3 protocol handshaking
6061 code which formerly resided in command.c has been moved below the
6062 channel_t abstraction layer and may be found in channeltls.c now.
6063 Implements the rest of ticket 6465.
6064 - Introduce new circuitmux_t storing the queue of circuits for
6065 a channel; this encapsulates and abstracts the queue logic and
6066 circuit selection policy, and allows the latter to be overridden
6067 easily by switching out a policy object. The existing EWMA behavior
6068 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
6070 o New build requirements:
6071 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
6072 strongly recommended.
6073 - Tor maintainers now require Automake version 1.9 or later to build
6074 Tor from the Git repository. (Automake is not required when building
6075 from a source distribution.)
6077 o Minor features (protocol):
6078 - No longer include the "opt" prefix when generating routerinfos
6079 or v2 directories: it has been needless since Tor 0.1.2. Closes
6081 - Reject EXTEND cells sent to nonexistent streams. According to the
6082 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
6083 we were only checking for stream IDs that were currently in use.
6084 Found while hunting for more instances of bug 6271. Bugfix on
6085 0.0.2pre8, which introduced incremental circuit construction.
6086 - Tor relays and clients now support a better CREATE/EXTEND cell
6087 format, allowing the sender to specify multiple address, identity,
6088 and handshake types. Implements Robert Ransom's proposal 200;
6090 - Reject as invalid most directory objects containing a NUL.
6091 Belt-and-suspender fix for bug 8037.
6093 o Minor features (security):
6094 - Clear keys and key-derived material left on the stack in
6095 rendservice.c and rendclient.c. Check return value of
6096 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
6097 These fixes should make us more forward-secure against cold-boot
6098 attacks and the like. Fixes bug 2385.
6099 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
6100 Irix's random() only return 15 bits; Solaris's random() returns more
6101 bits but its RAND_MAX says it only returns 15, and so on. Motivated
6102 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
6104 o Minor features (control protocol):
6105 - Add a "GETINFO signal/names" control port command. Implements
6107 - Provide default values for all options via "GETINFO config/defaults".
6108 Implements ticket 4971.
6109 - Allow an optional $ before the node identity digest in the
6110 controller command GETINFO ns/id/<identity>, for consistency with
6111 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
6112 - Add CACHED keyword to ADDRMAP events in the control protocol
6113 to indicate whether a DNS result will be cached or not. Resolves
6115 - Generate bootstrapping status update events correctly when fetching
6116 microdescriptors. Fixes bug 9927.
6118 o Minor features (path selection):
6119 - When deciding whether we have enough descriptors to build circuits,
6120 instead of looking at raw relay counts, look at which fraction
6121 of (bandwidth-weighted) paths we're able to build. This approach
6122 keeps clients from building circuits if their paths are likely to
6123 stand out statistically. The default fraction of paths needed is
6124 taken from the consensus directory; you can override it with the
6125 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
6126 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
6127 and we have GeoIP information, also exclude all nodes with unknown
6128 countries "??" and "A1". This behavior is controlled by the
6129 new GeoIPExcludeUnknown option: you can make such nodes always
6130 excluded with "GeoIPExcludeUnknown 1", and disable the feature
6131 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
6132 gets you the default behavior. Implements feature 7706.
6134 o Minor features (hidden services):
6135 - Improve circuit build timeout handling for hidden services.
6136 In particular: adjust build timeouts more accurately depending
6137 upon the number of hop-RTTs that a particular circuit type
6138 undergoes. Additionally, launch intro circuits in parallel
6139 if they timeout, and take the first one to reply as valid.
6140 - The Tor client now ignores sub-domain components of a .onion
6141 address. This change makes HTTP "virtual" hosting
6142 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
6143 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
6144 hosted on the same hidden service. Implements proposal 204.
6145 - Enable Tor to read configuration, state, and key information from
6146 a FIFO. Previously Tor would only read from files with a positive
6147 stat.st_size. Code from meejah; fixes bug 6044.
6149 o Minor features (clients):
6150 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
6151 microdescriptor-related dir requests, and only fall back to normal
6152 descriptors if none of their bridges can handle microdescriptors
6153 (as opposed to the fix in ticket 4013, which caused them to fall
6154 back to normal descriptors if *any* of their bridges preferred
6155 them). Resolves ticket 4994.
6156 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
6157 TCP ports to forward. In the past it only accepted two ports:
6158 the ORPort and the DirPort.
6160 o Minor features (protecting client timestamps):
6161 - Clients no longer send timestamps in their NETINFO cells. These were
6162 not used for anything, and they provided one small way for clients
6163 to be distinguished from each other as they moved from network to
6164 network or behind NAT. Implements part of proposal 222.
6165 - Clients now round timestamps in INTRODUCE cells down to the nearest
6166 10 minutes. If a new Support022HiddenServices option is set to 0, or
6167 if it's set to "auto" and the feature is disabled in the consensus,
6168 the timestamp is sent as 0 instead. Implements part of proposal 222.
6169 - Stop sending timestamps in AUTHENTICATE cells. This is not such
6170 a big deal from a security point of view, but it achieves no actual
6171 good purpose, and isn't needed. Implements part of proposal 222.
6172 - Reduce down accuracy of timestamps in hidden service descriptors.
6173 Implements part of proposal 222.
6175 o Minor features (bridges):
6176 - Make bridge relays check once a minute for whether their IP
6177 address has changed, rather than only every 15 minutes. Resolves
6179 - Bridge statistics now count bridge clients connecting over IPv6:
6180 bridge statistics files now list "bridge-ip-versions" and
6181 extra-info documents list "geoip6-db-digest". The control protocol
6182 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
6183 implementation by "shkoo", addressing ticket 5055.
6184 - Add a new torrc option "ServerTransportListenAddr" to let bridge
6185 operators select the address where their pluggable transports will
6186 listen for connections. Resolves ticket 7013.
6187 - Randomize the lifetime of our SSL link certificate, so censors can't
6188 use the static value for filtering Tor flows. Resolves ticket 8443;
6189 related to ticket 4014 which was included in 0.2.2.33.
6191 o Minor features (relays):
6192 - Option OutboundBindAddress can be specified multiple times and
6193 accepts IPv6 addresses. Resolves ticket 6876.
6195 o Minor features (IPv6, client side):
6196 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
6197 prefer to hand out virtual IPv6 addresses, since there are more of
6198 them and we can't run out. To override this behavior and make IPv4
6199 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
6200 or DNSPort you're using for resolving. Implements ticket 7571.
6201 - AutomapHostsOnResolve responses are now randomized, to avoid
6202 annoying situations where Tor is restarted and applications
6203 connect to the wrong addresses.
6204 - Never try more than 1000 times to pick a new virtual address when
6205 AutomapHostsOnResolve is set. That's good enough so long as we
6206 aren't close to handing out our entire virtual address space;
6207 if you're getting there, it's best to switch to IPv6 virtual
6210 o Minor features (IPv6, relay/authority side):
6211 - New config option "AuthDirHasIPv6Connectivity 1" that directory
6212 authorities should set if they have IPv6 connectivity and want to
6213 do reachability tests for IPv6 relays. Implements feature 5974.
6214 - A relay with an IPv6 OR port now sends that address in NETINFO
6215 cells (in addition to its other address). Implements ticket 6364.
6217 o Minor features (directory authorities):
6218 - Directory authorities no long accept descriptors for any version of
6219 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
6220 These versions are insecure, unsupported, or both. Implements
6222 - When directory authorities are computing thresholds for flags,
6223 never let the threshold for the Fast flag fall below 4096
6224 bytes. Also, do not consider nodes with extremely low bandwidths
6225 when deciding thresholds for various directory flags. This change
6226 should raise our threshold for Fast relays, possibly in turn
6227 improving overall network performance; see ticket 1854. Resolves
6229 - Directory authorities now include inside each vote a statement of
6230 the performance thresholds they used when assigning flags.
6231 Implements ticket 8151.
6232 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
6233 in directory authority votes to describe whether they have enough
6234 measured bandwidths to ignore advertised (relay descriptor)
6235 bandwidth claims. Resolves ticket 8711.
6237 o Minor features (path bias detection):
6238 - Path Use Bias: Perform separate accounting for successful circuit
6239 use. Keep separate statistics on stream attempt rates versus stream
6240 success rates for each guard. Provide configurable thresholds to
6241 determine when to emit log messages or disable use of guards that
6242 fail too many stream attempts. Resolves ticket 7802.
6243 - Create three levels of Path Bias log messages, as opposed to just
6244 two. These are configurable via consensus as well as via the torrc
6245 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
6246 The default values are 0.70, 0.50, and 0.30 respectively.
6247 - Separate the log message levels from the decision to drop guards,
6248 which also is available via torrc option PathBiasDropGuards.
6249 PathBiasDropGuards still defaults to 0 (off).
6250 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
6251 in combination with PathBiasExtremeRate.
6252 - Increase the default values for PathBiasScaleThreshold and
6253 PathBiasCircThreshold from (200, 20) to (300, 150).
6254 - Add in circuit usage accounting to path bias. If we try to use a
6255 built circuit but fail for any reason, it counts as path bias.
6256 Certain classes of circuits where the adversary gets to pick your
6257 destination node are exempt from this accounting. Usage accounting
6258 can be specifically disabled via consensus parameter or torrc.
6259 - Convert all internal path bias state to double-precision floating
6260 point, to avoid roundoff error and other issues.
6261 - Only record path bias information for circuits that have completed
6262 *two* hops. Assuming end-to-end tagging is the attack vector, this
6263 makes us more resilient to ambient circuit failure without any
6264 detection capability loss.
6266 o Minor features (build):
6267 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
6268 dhill. Resolves ticket 6982.
6269 - Compile on win64 using mingw64. Fixes bug 7260; patches from
6271 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
6272 separate error codes; or at least, don't break for that reason.
6273 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
6275 o Build improvements (autotools):
6276 - Warn if building on a platform with an unsigned time_t: there
6277 are too many places where Tor currently assumes that time_t can
6278 hold negative values. We'd like to fix them all, but probably
6280 - Do not report status verbosely from autogen.sh unless the -v flag
6281 is specified. Fixes issue 4664. Patch from Onizuka.
6282 - Detect and reject attempts to build Tor with threading support
6283 when OpenSSL has been compiled without threading support.
6285 - Try to detect if we are ever building on a platform where
6286 memset(...,0,...) does not set the value of a double to 0.0. Such
6287 platforms are permitted by the C standard, though in practice
6288 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
6289 currently support them, but it's better to detect them and fail
6290 than to perform erroneously.
6291 - We no longer warn so much when generating manpages from their
6293 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
6294 the signs of types during autoconf. This is better than our old
6295 approach, which didn't work when cross-compiling.
6297 o Minor features (log messages, warnings):
6298 - Detect when we're running with a version of OpenSSL other than the
6299 one we compiled with. This conflict has occasionally given people
6300 hard-to-track-down errors.
6301 - Warn users who run hidden services on a Tor client with
6302 UseEntryGuards disabled that their hidden services will be
6303 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
6304 attack which motivated Tor to support entry guards in the first
6305 place). Resolves ticket 6889.
6306 - Warn when we are binding low ports when hibernation is enabled;
6307 previously we had warned when we were _advertising_ low ports with
6308 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
6309 - Issue a warning when running with the bufferevents backend enabled.
6310 It's still not stable, and people should know that they're likely
6311 to hit unexpected problems. Closes ticket 9147.
6313 o Minor features (log messages, notices):
6314 - Refactor resolve_my_address() so it returns the method by which we
6315 decided our public IP address (explicitly configured, resolved from
6316 explicit hostname, guessed from interfaces, learned by gethostname).
6317 Now we can provide more helpful log messages when a relay guesses
6318 its IP address incorrectly (e.g. due to unexpected lines in
6319 /etc/hosts). Resolves ticket 2267.
6320 - Track how many "TAP" and "NTor" circuit handshake requests we get,
6321 and how many we complete, and log it every hour to help relay
6322 operators follow trends in network load. Addresses ticket 9658.
6324 o Minor features (log messages, diagnostics):
6325 - If we fail to free a microdescriptor because of bug 7164, log
6326 the filename and line number from which we tried to free it.
6327 - We compute the overhead from passing onionskins back and forth to
6328 cpuworkers, and report it when dumping statistics in response to
6329 SIGUSR1. Supports ticket 7291.
6330 - Add another diagnostic to the heartbeat message: track and log
6331 overhead that TLS is adding to the data we write. If this is
6332 high, we are sending too little data to SSL_write at a time.
6333 Diagnostic for bug 7707.
6334 - Log packaged cell fullness as part of the heartbeat message.
6335 Diagnosis to try to determine the extent of bug 7743.
6336 - Add more detail to a log message about relaxed timeouts, to help
6338 - When learning a fingerprint for a bridge, log its corresponding
6339 transport type. Implements ticket 7896.
6340 - Warn more aggressively when flushing microdescriptors to a
6341 microdescriptor cache fails, in an attempt to mitigate bug 8031,
6342 or at least make it more diagnosable.
6343 - Improve the log message when "Bug/attack: unexpected sendme cell
6344 from client" occurs, to help us track bug 8093.
6345 - Improve debugging output to help track down bug 8185 ("Bug:
6346 outgoing relay cell has n_chan==NULL. Dropping.")
6348 o Minor features (log messages, quieter bootstrapping):
6349 - Log fewer lines at level "notice" about our OpenSSL and Libevent
6350 versions and capabilities when everything is going right. Resolves
6351 part of ticket 6736.
6352 - Omit the first heartbeat log message, because it never has anything
6353 useful to say, and it clutters up the bootstrapping messages.
6354 Resolves ticket 6758.
6355 - Don't log about reloading the microdescriptor cache at startup. Our
6356 bootstrap warnings are supposed to tell the user when there's a
6357 problem, and our bootstrap notices say when there isn't. Resolves
6358 ticket 6759; bugfix on 0.2.2.6-alpha.
6359 - Don't log "I learned some more directory information" when we're
6360 reading cached directory information. Reserve it for when new
6361 directory information arrives in response to a fetch. Resolves
6363 - Don't complain about bootstrapping problems while hibernating.
6364 These complaints reflect a general code problem, but not one
6365 with any problematic effects (no connections are actually
6366 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
6368 o Minor features (testing):
6369 - In our testsuite, create temporary directories with a bit more
6370 entropy in their name to make name collisions less likely. Fixes
6372 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
6373 (P-256) Diffie-Hellman handshakes to src/or/bench.
6374 - Add benchmark functions to test onion handshake performance.
6377 - The DirServer option is now DirAuthority, for consistency with
6378 current naming patterns. You can still use the old DirServer form.
6380 o Minor bugfixes (protocol):
6381 - Fix the handling of a TRUNCATE cell when it arrives while the
6382 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
6383 - When a Tor client gets a "truncated" relay cell, the first byte of
6384 its payload specifies why the circuit was truncated. We were
6385 ignoring this 'reason' byte when tearing down the circuit, resulting
6386 in the controller not being told why the circuit closed. Now we
6387 pass the reason from the truncated cell to the controller. Bugfix
6388 on 0.1.2.3-alpha; fixes bug 7039.
6389 - Fix a misframing issue when reading the version numbers in a
6390 VERSIONS cell. Previously we would recognize [00 01 00 02] as
6391 'version 1, version 2, and version 0x100', when it should have
6392 only included versions 1 and 2. Fixes bug 8059; bugfix on
6393 0.2.0.10-alpha. Reported pseudonymously.
6394 - Make the format and order of STREAM events for DNS lookups
6395 consistent among the various ways to launch DNS lookups. Fixes
6396 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
6398 o Minor bugfixes (syscalls and disk interaction):
6399 - Always check the return values of functions fcntl() and
6400 setsockopt(). We don't believe these are ever actually failing in
6401 practice, but better safe than sorry. Also, checking these return
6402 values should please analysis tools like Coverity. Patch from
6403 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
6404 - Avoid double-closing the listener socket in our socketpair()
6405 replacement (used on Windows) in the case where the addresses on
6406 our opened sockets don't match what we expected. Fixes bug 9400;
6407 bugfix on 0.0.2pre7. Found by Coverity.
6408 - Correctly store microdescriptors and extrainfo descriptors that
6409 include an internal NUL byte. Fixes bug 8037; bugfix on
6410 0.2.0.1-alpha. Bug reported by "cypherpunks".
6411 - If for some reason we fail to write a microdescriptor while
6412 rebuilding the cache, do not let the annotations from that
6413 microdescriptor linger in the cache file, and do not let the
6414 microdescriptor stay recorded as present in its old location.
6415 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
6416 - Use direct writes rather than stdio when building microdescriptor
6417 caches, in an attempt to mitigate bug 8031, or at least make it
6420 o Minor fixes (config options):
6421 - Warn and fail if a server is configured not to advertise any
6422 ORPorts at all. (We need *something* to put in our descriptor,
6423 or we just won't work.)
6424 - Behave correctly when the user disables LearnCircuitBuildTimeout
6425 but doesn't tell us what they would like the timeout to be. Fixes
6426 bug 6304; bugfix on 0.2.2.14-alpha.
6427 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
6428 to start with a triple-underscore so the controller won't touch it.
6429 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
6430 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
6431 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
6432 - When autodetecting the number of CPUs, use the number of available
6433 CPUs in preference to the number of configured CPUs. Inform the
6434 user if this reduces the number of available CPUs. Fixes bug 8002;
6435 bugfix on 0.2.3.1-alpha.
6436 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
6437 - Make it an error when you set EntryNodes but disable UseGuardNodes,
6438 since it will (surprisingly to some users) ignore EntryNodes. Fixes
6439 bug 8180; bugfix on 0.2.3.11-alpha.
6440 - Avoid overflows when the user sets MaxCircuitDirtiness to a
6441 ridiculously high value, by imposing a (ridiculously high) 30-day
6442 maximum on MaxCircuitDirtiness.
6444 o Minor bugfixes (control protocol):
6445 - Stop sending a stray "(null)" in some cases for the server status
6446 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
6448 - The ADDRMAP command can no longer generate an ill-formed error
6449 code on a failed MAPADDRESS. It now says "internal" rather than
6450 an English sentence fragment with spaces in the middle. Bugfix on
6453 o Minor bugfixes (clients / edges):
6454 - When we receive a RELAY_END cell with the reason DONE, or with no
6455 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
6456 status as "connection refused". Previously we reported these cases
6457 as success but then immediately closed the connection. Fixes bug
6458 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
6459 - If the guard we choose first doesn't answer, we would try the
6460 second guard, but once we connected to the second guard we would
6461 abandon it and retry the first one, slowing down bootstrapping.
6462 The fix is to treat all our initially chosen guards as acceptable
6463 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
6464 - When choosing which stream on a formerly stalled circuit to wake
6465 first, make better use of the platform's weak RNG. Previously,
6466 we had been using the % ("modulo") operator to try to generate a
6467 1/N chance of picking each stream, but this behaves badly with
6468 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
6471 o Minor bugfixes (path bias detection):
6472 - If the state file's path bias counts are invalid (presumably from a
6473 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
6474 additional checks and log messages to the scaling of Path Bias
6475 counts, in case there still are remaining issues with scaling.
6476 Should help resolve bug 8235.
6477 - Prevent rounding error in path bias counts when scaling
6478 them down, and use the correct scale factor default. Also demote
6479 some path bias related log messages down a level and make others
6480 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
6481 - Remove a source of rounding error during path bias count scaling;
6482 don't count cannibalized circuits as used for path bias until we
6483 actually try to use them; and fix a circuit_package_relay_cell()
6484 warning message about n_chan==NULL. Fixes bug 7802.
6485 - Paste the description for PathBias parameters from the man
6486 page into or.h, so the code documents them too. Fixes bug 7982;
6487 bugfix on 0.2.3.17-beta.
6489 o Minor bugfixes (relays):
6490 - Stop trying to resolve our hostname so often (e.g. every time we
6491 think about doing a directory fetch). Now we reuse the cached
6492 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
6493 and 2410 (bugfix on 0.1.2.2-alpha).
6494 - When examining the list of network interfaces to find our address,
6495 do not consider non-running or disabled network interfaces. Fixes
6496 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
6498 o Minor bugfixes (blocking resistance):
6499 - Only disable TLS session ticket support when running as a TLS
6500 server. Now clients will blend better with regular Firefox
6501 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
6503 o Minor bugfixes (IPv6):
6504 - Use square brackets around IPv6 addresses in numerous places
6505 that needed them, including log messages, HTTPS CONNECT proxy
6506 requests, TransportProxy statefile entries, and pluggable transport
6507 extra-info lines. Fixes bug 7011; patch by David Fifield.
6509 o Minor bugfixes (directory authorities):
6510 - Reject consensus votes with more than 64 known-flags. We aren't even
6511 close to that limit yet, and our code doesn't handle it correctly.
6512 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
6513 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
6514 bugfix on 0.2.0.3-alpha.
6516 o Minor bugfixes (memory leaks):
6517 - Avoid leaking memory if we fail to compute a consensus signature
6518 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
6519 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
6520 on 0.2.1.1-alpha; fixes bug 7816.
6521 - Fix a memory leak during safe-cookie controller authentication.
6522 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
6523 - Free some more still-in-use memory at exit, to make hunting for
6524 memory leaks easier. Resolves bug 7029.
6526 o Minor bugfixes (code correctness):
6527 - Increase the width of the field used to remember a connection's
6528 link protocol version to two bytes. Harmless for now, since the
6529 only currently recognized versions are one byte long. Reported
6530 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
6531 - Fix a crash when debugging unit tests on Windows: deallocate a
6532 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
6533 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
6534 - When detecting the largest possible file descriptor (in order to
6535 close all file descriptors when launching a new program), actually
6536 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
6537 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
6539 - Avoid a crash if we fail to generate an extrainfo descriptor.
6540 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
6542 - Avoid an off-by-one error when checking buffer boundaries when
6543 formatting the exit status of a pluggable transport helper.
6544 This is probably not an exploitable bug, but better safe than
6545 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
6547 - Get rid of a couple of harmless clang warnings, where we compared
6548 enums to ints. These warnings are newly introduced in clang 3.2.
6550 o Minor bugfixes (code cleanliness):
6551 - Avoid use of reserved identifiers in our C code. The C standard
6552 doesn't like us declaring anything that starts with an
6553 underscore, so let's knock it off before we get in trouble. Fix
6554 for bug 1031; bugfix on the first Tor commit.
6555 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
6556 with large values. This situation was untriggered, but nevertheless
6557 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
6558 - Fix an impossible buffer overrun in the AES unit tests. Fixes
6559 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
6560 - Fix handling of rendezvous client authorization types over 8.
6561 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
6562 - Remove a couple of extraneous semicolons that were upsetting the
6563 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
6564 bugfix on 0.2.2.1-alpha.
6565 - When complaining about a client port on a public address, log
6566 which address we're complaining about. Fixes bug 4020; bugfix on
6567 0.2.3.3-alpha. Patch by Tom Fitzhenry.
6569 o Minor bugfixes (log messages, warnings):
6570 - If we encounter a write failure on a SOCKS connection before we
6571 finish our SOCKS handshake, don't warn that we closed the
6572 connection before we could send a SOCKS reply. Fixes bug 8427;
6573 bugfix on 0.1.0.1-rc.
6574 - Fix a directory authority warn caused when we have a large amount
6575 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
6576 - Downgrade "Failed to hand off onionskin" messages to "debug"
6577 severity, since they're typically redundant with the "Your computer
6578 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
6579 - Avoid spurious warnings when configuring multiple client ports of
6580 which only some are nonlocal. Previously, we had claimed that some
6581 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
6584 o Minor bugfixes (log messages, other):
6585 - Fix log messages and comments to avoid saying "GMT" when we mean
6586 "UTC". Fixes bug 6113.
6587 - When rejecting a configuration because we were unable to parse a
6588 quoted string, log an actual error message. Fixes bug 7950; bugfix
6590 - Correctly recognize that [::1] is a loopback address. Fixes
6591 bug 8377; bugfix on 0.2.1.3-alpha.
6592 - Don't log inappropriate heartbeat messages when hibernating: a
6593 hibernating node is _expected_ to drop out of the consensus,
6594 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
6595 bugfix on 0.2.3.1-alpha.
6596 - Eliminate several instances where we use "Nickname=ID" to refer to
6597 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
6598 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
6601 o Minor bugfixes (build):
6602 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
6603 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
6604 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
6606 o Documentation fixes:
6607 - Make the torify manpage no longer refer to tsocks; torify hasn't
6608 supported tsocks since 0.2.3.14-alpha.
6609 - Make the tor manpage no longer reference tsocks.
6610 - Fix the GeoIPExcludeUnknown documentation to refer to
6611 ExcludeExitNodes rather than the currently nonexistent
6612 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
6613 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
6615 - Say "KBytes" rather than "KB" in the man page (for various values
6616 of K), to further reduce confusion about whether Tor counts in
6617 units of memory or fractions of units of memory. Resolves ticket 7054.
6618 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
6619 names match. Fixes bug 7768.
6620 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
6621 message is logged at notice, not at info.
6622 - Clarify the usage and risks of setting the ContactInfo torrc line
6623 for your relay or bridge. Resolves ticket 9854.
6624 - Add anchors to the manpage so we can link to the html version of
6625 the documentation for specific options. Resolves ticket 9866.
6626 - Replace remaining references to DirServer in man page and
6627 log entries. Resolves ticket 10124.
6630 - Stop exporting estimates of v2 and v3 directory traffic shares
6631 in extrainfo documents. They were unneeded and sometimes inaccurate.
6632 Also stop exporting any v2 directory request statistics. Resolves
6634 - Drop support for detecting and warning about versions of Libevent
6635 before 1.3e. Nothing reasonable ships with them any longer; warning
6636 the user about them shouldn't be needed. Resolves ticket 6826.
6637 - Now that all versions before 0.2.2.x are disallowed, we no longer
6638 need to work around their missing features. Remove a bunch of
6642 - The tor-tsocks.conf is no longer distributed or installed. We
6643 recommend that tsocks users use torsocks instead. Resolves
6645 - Remove some of the older contents of doc/ as obsolete; move others
6646 to torspec.git. Fixes bug 8965.
6648 o Code simplification:
6649 - Avoid using character buffers when constructing most directory
6650 objects: this approach was unwieldy and error-prone. Instead,
6651 build smartlists of strings, and concatenate them when done.
6652 - Rename "isin" functions to "contains", for grammar. Resolves
6654 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
6655 with the natural logarithm function from the system libm. Resolves
6657 - Start using OpenBSD's implementation of queue.h, so that we don't
6658 need to hand-roll our own pointer and list structures whenever we
6659 need them. (We can't rely on a sys/queue.h, since some operating
6660 systems don't have them, and the ones that do have them don't all
6661 present the same extensions.)
6662 - Start using OpenBSD's implementation of queue.h (originally by
6664 - Enhance our internal sscanf replacement so that we can eliminate
6665 the last remaining uses of the system sscanf. (Though those uses
6666 of sscanf were safe, sscanf itself is generally error prone, so
6667 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
6669 - Replace all calls to snprintf() outside of src/ext with
6670 tor_snprintf(). Also remove the #define to replace snprintf with
6671 _snprintf on Windows; they have different semantics, and all of
6672 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
6675 - Add a wrapper function for the common "log a message with a
6677 - Split the onion.c file into separate modules for the onion queue
6678 and the different handshakes it supports.
6679 - Move the client-side address-map/virtual-address/DNS-cache code
6680 out of connection_edge.c into a new addressmap.c module.
6681 - Move the entry node code from circuitbuild.c to its own file.
6682 - Move the circuit build timeout tracking code from circuitbuild.c
6684 - Source files taken from other packages now reside in src/ext;
6685 previously they were scattered around the rest of Tor.
6686 - Move the generic "config" code into a new file, and have "config.c"
6687 hold only torrc- and state-related code. Resolves ticket 6823.
6688 - Move the core of our "choose a weighted element at random" logic
6689 into its own function, and give it unit tests. Now the logic is
6690 testable, and a little less fragile too.
6691 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
6692 - Move last_reachable and testing_since from routerinfo_t to node_t.
6693 Implements ticket 5529.
6694 - Add replaycache_t structure, functions and unit tests, then refactor
6695 rend_service_introduce() to be more clear to read, improve, debug,
6696 and test. Resolves bug 6177.
6699 - Remove some now-needless code that tried to aggressively flush
6700 OR connections as data was added to them. Since 0.2.0.1-alpha, our
6701 cell queue logic has saved us from the failure mode that this code
6702 was supposed to prevent. Removing this code will limit the number
6703 of baroque control flow paths through Tor's network logic. Reported
6704 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
6705 - Remove unused code for parsing v1 directories and "running routers"
6706 documents. Fixes bug 6887.
6707 - Remove the marshalling/unmarshalling code for sending requests to
6708 cpuworkers over a socket, and instead just send structs. The
6709 recipient will always be the same Tor binary as the sender, so
6710 any encoding is overkill.
6711 - Remove the testing_since field of node_t, which hasn't been used
6712 for anything since 0.2.0.9-alpha.
6713 - Finally remove support for malloc_good_size and malloc_usable_size.
6714 We had hoped that these functions would let us eke a little more
6715 memory out of our malloc implementation. Unfortunately, the only
6716 implementations that provided these functions are also ones that
6717 are already efficient about not overallocation: they never got us
6718 more than 7 or so bytes per allocation. Removing them saves us a
6719 little code complexity and a nontrivial amount of build complexity.
6722 Changes in version 0.2.3.25 - 2012-11-19
6723 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
6724 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
6725 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
6726 programmer, and friend. Unstinting in his dedication to the cause of
6727 freedom, he inspired and helped many of us as we began our work on
6728 anonymity, and inspires us still. Please honor his memory by writing
6729 software to protect people's freedoms, and by helping others to do so.
6731 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
6732 significantly reduced directory overhead (via microdescriptors),
6733 enormous crypto performance improvements for fast relays on new
6734 enough hardware, a new v3 TLS handshake protocol that can better
6735 resist fingerprinting, support for protocol obfuscation plugins (aka
6736 pluggable transports), better scalability for hidden services, IPv6
6737 support for bridges, performance improvements like allowing clients
6738 to skip the first round-trip on the circuit ("optimistic data") and
6739 refilling token buckets more often, a new "stream isolation" design
6740 to isolate different applications on different circuits, and many
6741 stability, security, and privacy fixes.
6743 Major features (v3 directory protocol):
6744 - Clients now use microdescriptors instead of regular descriptors
6745 to build circuits. Microdescriptors are authority-generated
6746 summaries of regular descriptors' contents, designed to change very
6747 rarely (see proposal 158 for details). This feature is designed
6748 to save bandwidth, especially for clients on slow internet
6749 connections. Use "UseMicrodescriptors 0" to disable it.
6750 - Caches now download, cache, and serve microdescriptors, as well
6751 as multiple "flavors" of the consensus, including a flavor that
6752 describes microdescriptors.
6754 o Major features (build hardening):
6755 - Enable gcc and ld hardening by default. Resolves ticket 5210.
6757 o Major features (relay scaling):
6758 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
6759 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
6760 vectorized AES implementations as appropriate. These can be much,
6761 much faster than other AES implementations.
6762 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
6763 implementation. It makes AES_CTR about 7% faster than our old one
6764 (which was about 10% faster than the one OpenSSL used to provide).
6765 Resolves ticket 4526.
6766 - Use OpenSSL's EVP interface for AES encryption, so that all AES
6767 operations can use hardware acceleration (if present). Resolves
6769 - Unconditionally use OpenSSL's AES implementation instead of our
6770 old built-in one. OpenSSL's AES has been better for a while, and
6771 relatively few servers should still be on any version of OpenSSL
6772 that doesn't have good optimized assembly AES.
6774 o Major features (blocking resistance):
6775 - Update TLS cipher list to match Firefox 8 and later. Resolves
6777 - Remove support for clients falsely claiming to support standard
6778 ciphersuites that they can actually provide. As of modern OpenSSL
6779 versions, it's not necessary to fake any standard ciphersuite,
6780 and doing so prevents us from using better ciphersuites in the
6781 future, since servers can't know whether an advertised ciphersuite
6782 is really supported or not. Some hosts -- notably, ones with very
6783 old versions of OpenSSL or where OpenSSL has been built with ECC
6784 disabled -- will stand out because of this change; TBB users should
6785 not be affected. Implements the client side of proposal 198.
6786 - Implement a new handshake protocol (v3) for authenticating Tors to
6787 each other over TLS. It should be more resistant to fingerprinting
6788 than previous protocols, and should require less TLS hacking for
6789 future Tor implementations. Implements proposal 176.
6790 - Allow variable-length padding cells, to disguise the length of
6791 Tor's TLS records. Implements part of proposal 184.
6792 - While we're trying to bootstrap, record how many TLS connections
6793 fail in each state, and report which states saw the most failures
6794 in response to any bootstrap failures. This feature may speed up
6795 diagnosis of censorship events. Implements ticket 3116.
6797 o Major features (pluggable transports):
6798 - Clients and bridges can now be configured to use a separate
6799 "transport" proxy. This approach makes the censorship arms race
6800 easier by allowing bridges to use protocol obfuscation plugins.
6801 Implements proposal 180 (tickets 2841 and 3472).
6803 o Major features (DoS resistance):
6804 - Now that Tor 0.2.0.x is completely deprecated, enable the final
6805 part of "Proposal 110: Avoiding infinite length circuits" by
6806 refusing all circuit-extend requests that do not use a relay_early
6807 cell. This change helps Tor resist a class of denial-of-service
6808 attacks by limiting the maximum circuit length.
6809 - Tear down the circuit if we get an unexpected SENDME cell. Clients
6810 could use this trick to make their circuits receive cells faster
6811 than our flow control would have allowed, or to gum up the network,
6812 or possibly to do targeted memory denial-of-service attacks on
6813 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
6814 from July 2002, before the release of Tor 0.0.0.
6816 o Major features (hidden services):
6817 - Adjust the number of introduction points that a hidden service
6818 will try to maintain based on how long its introduction points
6819 remain in use and how many introductions they handle. Fixes
6821 - Add a "tor2web mode" for clients that want to connect to hidden
6822 services non-anonymously (and possibly more quickly). As a safety
6823 measure to try to keep users from turning this on without knowing
6824 what they are doing, tor2web mode must be explicitly enabled at
6825 compile time, and a copy of Tor compiled to run in tor2web mode
6826 cannot be used as a normal Tor client. Implements feature 2553.
6828 o Major features (IPv6):
6829 - Clients can now connect to private bridges over IPv6. Bridges
6830 still need at least one IPv4 address in order to connect to
6831 other relays. Note that we don't yet handle the case where the
6832 user has two bridge lines for the same bridge (one IPv4, one
6833 IPv6). Implements parts of proposal 186.
6835 o Major features (directory authorities):
6836 - Use a more secure consensus parameter voting algorithm. Now at
6837 least three directory authorities or a majority of them must
6838 vote on a given parameter before it will be included in the
6839 consensus. Implements proposal 178.
6840 - Remove the artificially low cutoff of 20KB to guarantee the Fast
6841 flag. In the past few years the average relay speed has picked
6842 up, and while the "top 7/8 of the network get the Fast flag" and
6843 "all relays with 20KB or more of capacity get the Fast flag" rules
6844 used to have the same result, now the top 7/8 of the network has
6845 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
6847 o Major features (performance):
6848 - Exit nodes now accept and queue data on not-yet-connected streams.
6849 Previously, the client wasn't allowed to send data until the
6850 stream was connected, which slowed down all connections. This
6851 change will enable clients to perform a "fast-start" on streams
6852 and send data without having to wait for a confirmation that the
6853 stream has opened. Patch from Ian Goldberg; implements the server
6854 side of Proposal 174.
6855 - When using an exit relay running 0.2.3.x, clients can now
6856 "optimistically" send data before the exit relay reports that
6857 the stream has opened. This saves a round trip when starting
6858 connections where the client speaks first (such as web browsing).
6859 This behavior is controlled by a consensus parameter (currently
6860 disabled). To turn it on or off manually, use the "OptimisticData"
6861 torrc option. Implements proposal 181; code by Ian Goldberg.
6862 - Add a new TokenBucketRefillInterval option to refill token buckets
6863 more frequently than once per second. This should improve network
6864 performance, alleviate queueing problems, and make traffic less
6865 bursty. Implements proposal 183; closes ticket 3630. Design by
6866 Florian Tschorsch and Björn Scheuermann; implementation by
6868 - Raise the threshold of server descriptors needed (75%) and exit
6869 server descriptors needed (50%) before we will declare ourselves
6870 bootstrapped. This will make clients start building circuits a
6871 little later, but makes the initially constructed circuits less
6872 skewed and less in conflict with further directory fetches. Fixes
6875 o Major features (relays):
6876 - Relays now try regenerating and uploading their descriptor more
6877 frequently if they are not listed in the consensus, or if the
6878 version of their descriptor listed in the consensus is too
6879 old. This fix should prevent situations where a server declines
6880 to re-publish itself because it has done so too recently, even
6881 though the authorities decided not to list its recent-enough
6882 descriptor. Fix for bug 3327.
6884 o Major features (stream isolation):
6885 - You can now configure Tor so that streams from different
6886 applications are isolated on different circuits, to prevent an
6887 attacker who sees your streams as they leave an exit node from
6888 linking your sessions to one another. To do this, choose some way
6889 to distinguish the applications: have them connect to different
6890 SocksPorts, or have one of them use SOCKS4 while the other uses
6891 SOCKS5, or have them pass different authentication strings to the
6892 SOCKS proxy. Then, use the new SocksPort syntax to configure the
6893 degree of isolation you need. This implements Proposal 171.
6894 - There's a new syntax for specifying multiple client ports (such as
6895 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
6896 multiple *Port entries with full addr:port syntax on each.
6897 The old *ListenAddress format is still supported, but you can't
6898 mix it with the new *Port syntax.
6900 o Major features (bufferevents):
6901 - Tor can now optionally build with the "bufferevents" buffered IO
6902 backend provided by Libevent 2. To use this feature, make sure you
6903 have the latest possible version of Libevent, and pass the
6904 --enable-bufferevents flag to configure when building Tor from
6905 source. This feature will make our networking code more flexible,
6906 let us stack layers on each other, and let us use more efficient
6907 zero-copy transports where available.
6908 - Add experimental support for running on Windows with IOCP and no
6909 kernel-space socket buffers. This feature is controlled by a new
6910 "UserspaceIOCPBuffers" config option (off by default), which has
6911 no effect unless Tor has been built with bufferevents enabled,
6912 you're running on Windows, and you've set "DisableIOCP 0". In the
6913 long run, this may help solve or mitigate bug 98.
6915 o Major features (path selection):
6916 - The EntryNodes option can now include country codes like {de} or IP
6917 addresses or network masks. Previously we had disallowed these
6918 options because we didn't have an efficient way to keep the list up
6919 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
6922 o Major features (port forwarding):
6923 - Add support for automatic port mapping on the many home routers
6924 that support NAT-PMP or UPnP. To build the support code, you'll
6925 need to have the libnatpnp library and/or the libminiupnpc library,
6926 and you'll need to enable the feature specifically by passing
6927 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
6928 it on, use the new PortForwarding option.
6930 o Major features (logging):
6931 - Add a new 'Heartbeat' log message type to periodically log a message
6932 describing Tor's status at level Notice. This feature is meant for
6933 operators who log at notice, and want to make sure that their Tor
6934 server is still working. Implementation by George Kadianakis.
6935 - Make logging resolution configurable with a new LogTimeGranularity
6936 option, and change the default from 1 millisecond to 1 second.
6937 Implements enhancement 1668.
6939 o Major features (other):
6940 - New "DisableNetwork" config option to prevent Tor from launching any
6941 connections or accepting any connections except on a control port.
6942 Bundles and controllers can set this option before letting Tor talk
6943 to the rest of the network, for example to prevent any connections
6944 to a non-bridge address. Packages like Orbot can also use this
6945 option to instruct Tor to save power when the network is off.
6946 - Try to use system facilities for enumerating local interface
6947 addresses, before falling back to our old approach (which was
6948 binding a UDP socket, and calling getsockname() on it). That
6949 approach was scaring OS X users whose draconian firewall
6950 software warned about binding to UDP sockets regardless of
6951 whether packets were sent. Now we try to use getifaddrs(),
6952 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
6953 system supports. Resolves ticket 1827.
6954 - Add experimental support for a "defaults" torrc file to be parsed
6955 before the regular torrc. Torrc options override the defaults file's
6956 options in the same way that the command line overrides the torrc.
6957 The SAVECONF controller command saves only those options which
6958 differ between the current configuration and the defaults file. HUP
6959 reloads both files. Implements task 4552.
6961 o New directory authorities:
6962 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
6963 authority. Closes ticket 5749.
6965 o Security/privacy fixes:
6966 - Avoid read-from-freed-memory and double-free bugs that could occur
6967 when a DNS request fails while launching it. Fixes bug 6480;
6968 bugfix on 0.2.0.1-alpha.
6969 - Reject any attempt to extend to an internal address. Without
6970 this fix, a router could be used to probe addresses on an internal
6971 network to see whether they were accepting connections. Fixes bug
6972 6710; bugfix on 0.0.8pre1.
6973 - Close any connection that sends unrecognized junk before the TLS
6974 handshake. Solves an issue noted in bug 4369.
6975 - The advertised platform of a relay now includes only its operating
6976 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
6977 its service pack level (for Windows) or its CPU architecture
6978 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
6979 can insert an extra string in the platform line by setting the
6980 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
6981 - Disable TLS session tickets. OpenSSL's implementation was giving
6982 our TLS session keys the lifetime of our TLS context objects, when
6983 perfect forward secrecy would want us to discard anything that
6984 could decrypt a link connection as soon as the link connection
6985 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
6986 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
6987 - Tor tries to wipe potentially sensitive data after using it, so
6988 that if some subsequent security failure exposes Tor's memory,
6989 the damage will be limited. But we had a bug where the compiler
6990 was eliminating these wipe operations when it decided that the
6991 memory was no longer visible to a (correctly running) program,
6992 hence defeating our attempt at defense in depth. We fix that
6993 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
6994 is unlikely to optimize away. Future versions of Tor may use
6995 a less ridiculously heavy approach for this. Fixes bug 7352.
6996 Reported in an article by Andrey Karpov.
6998 o Major bugfixes (crashes and asserts):
6999 - Avoid a pair of double-free and use-after-mark bugs that can
7000 occur with certain timings in canceled and re-received DNS
7001 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
7002 - Fix a denial of service attack by which any directory authority
7003 could crash all the others, or by which a single v2 directory
7004 authority could crash everybody downloading v2 directory
7005 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
7006 - Fix an assert that directory authorities could trigger on sighup
7007 during some configuration state transitions. We now don't treat
7008 it as a fatal error when the new descriptor we just generated in
7009 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
7010 - Avoid segfault when starting up having run with an extremely old
7011 version of Tor and parsing its state file. Fixes bug 6801; bugfix
7014 o Major bugfixes (clients):
7015 - If we are unable to find any exit that supports our predicted ports,
7016 stop calling them predicted, so that we don't loop and build
7017 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
7018 which introduced predicted ports.
7019 - Check at each new consensus whether our entry guards were picked
7020 long enough ago that we should rotate them. Previously, we only
7021 did this check at startup, which could lead to us holding a guard
7022 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
7023 - When fetching a bridge descriptor from a bridge authority,
7024 always do so anonymously, whether we have been able to open
7025 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
7026 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
7027 but we'll need to wait for bug 6010 before it's actually usable.
7029 o Major bugfixes (directory voting):
7030 - Check more thoroughly to prevent a rogue authority from
7031 double-voting on any consensus directory parameter. Previously,
7032 authorities would crash in this case if the total number of
7033 votes for any parameter exceeded the number of active voters,
7034 but would let it pass otherwise. Partially fixes bug 5786; bugfix
7036 - When computing weight parameters, behave more robustly in the
7037 presence of a bad bwweightscale value. Previously, the authorities
7038 would crash if they agreed on a sufficiently broken weight_scale
7039 value; now, they use a reasonable default and carry on. Fixes the
7040 rest of bug 5786; bugfix on 0.2.2.17-alpha.
7041 - If authorities are unable to get a v2 consensus document from other
7042 directory authorities, they no longer fall back to fetching
7043 them from regular directory caches. Fixes bug 5635; bugfix on
7044 0.2.2.26-beta, where routers stopped downloading v2 consensus
7047 o Major bugfixes (relays):
7048 - Fix a bug handling SENDME cells on nonexistent streams that could
7049 result in bizarre window values. Report and patch contributed
7050 pseudonymously. Fixes part of bug 6271. This bug was introduced
7051 before the first Tor release, in svn commit r152.
7052 - Don't update the AccountingSoftLimitHitAt state file entry whenever
7053 tor gets started. This prevents a wrong average bandwidth
7054 estimate, which would cause relays to always start a new accounting
7055 interval at the earliest possible moment. Fixes bug 2003; bugfix
7056 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
7057 immensely in tracking this bug down.
7058 - Fix a possible crash bug when checking for deactivated circuits
7059 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
7060 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
7061 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
7062 connections. This change should allow busy exit relays to stop
7063 running out of available sockets as quickly. Fixes bug 4950;
7064 bugfix on 0.2.2.26-beta.
7066 o Major bugfixes (blocking resistance):
7067 - Bridges no longer include their address in NETINFO cells on outgoing
7068 OR connections, to allow them to blend in better with clients.
7069 Removes another avenue for enumerating bridges. Reported by
7070 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
7071 cells were introduced.
7072 - Warn the user when HTTPProxy, but no other proxy type, is
7073 configured. This can cause surprising behavior: it doesn't send
7074 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
7075 directory traffic only. Resolves ticket 4663.
7077 o Major bugfixes (hidden services):
7078 - Improve hidden service robustness: when an attempt to connect to
7079 a hidden service ends, be willing to refetch its hidden service
7080 descriptors from each of the HSDir relays responsible for them
7081 immediately. Previously, we would not consider refetching the
7082 service's descriptors from each HSDir for 15 minutes after the last
7083 fetch, which was inconvenient if the hidden service was not running
7084 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
7085 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
7086 They used to check that the timestamp was within 30 minutes
7087 of their system clock, so they could cap the size of their
7088 replay-detection cache, but that approach unnecessarily refused
7089 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
7090 the v3 intro-point protocol (the first one which sent a timestamp
7091 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
7092 - When one of a hidden service's introduction points appears to be
7093 unreachable, stop trying it. Previously, we would keep trying
7094 to build circuits to the introduction point until we lost the
7095 descriptor, usually because the user gave up and restarted Tor.
7096 Fixes part of bug 3825.
7098 o Changes to default torrc file:
7099 - Stop listing "socksport 9050" in torrc.sample. We open a socks
7100 port on 9050 by default anyway, so this should not change anything
7102 - Stop mentioning the deprecated *ListenAddress options in
7103 torrc.sample. Fixes bug 5438.
7104 - Document unit of bandwidth-related options in sample torrc.
7106 - Fix broken URLs in the sample torrc file, and tell readers about
7107 the OutboundBindAddress, ExitPolicyRejectPrivate, and
7108 PublishServerDescriptor options. Addresses bug 4652.
7110 o Minor features (directory authorities):
7111 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
7112 change when the authority is deciding whether to accept a newly
7113 uploaded descriptor. Implements ticket 6423.
7114 - Directory authorities are now a little more lenient at accepting
7115 older router descriptors, or newer router descriptors that don't
7116 make big changes. This should help ameliorate past and future
7117 issues where routers think they have uploaded valid descriptors,
7118 but the authorities don't think so. Fix for ticket 2479.
7119 - Authority operators can now vote for all relays in a given
7120 set of countries to be BadDir/BadExit/Invalid/Rejected.
7121 - Provide two consensus parameters (FastFlagMinThreshold and
7122 FastFlagMaxThreshold) to control the range of allowable bandwidths
7123 for the Fast directory flag. These allow authorities to run
7124 experiments on appropriate requirements for being a "Fast" node.
7125 The AuthDirFastGuarantee config value still applies. Implements
7128 o Minor features (bridges / bridge authorities):
7129 - Make bridge SSL certificates a bit more stealthy by using random
7130 serial numbers, in the same fashion as OpenSSL when generating
7131 self-signed certificates. Implements ticket 4584.
7132 - Tag a bridge's descriptor as "never to be sent unencrypted".
7133 This shouldn't matter, since bridges don't open non-anonymous
7134 connections to the bridge authority and don't allow unencrypted
7135 directory connections from clients, but we might as well make
7136 sure. Closes bug 5139.
7137 - The Bridge Authority now writes statistics on how many bridge
7138 descriptors it gave out in total, and how many unique descriptors
7139 it gave out. It also lists how often the most and least commonly
7140 fetched descriptors were given out, as well as the median and
7141 25th/75th percentile. Implements tickets 4200 and 4294.
7143 o Minor features (IPv6):
7144 - Make the code that clients use to detect an address change be
7145 IPv6-aware, so that it won't fill clients' logs with error
7146 messages when trying to get the IPv4 address of an IPv6
7147 connection. Implements ticket 5537.
7148 - Relays now understand an IPv6 address when they get one from a
7149 directory server. Resolves ticket 4875.
7151 o Minor features (hidden services):
7152 - Expire old or over-used hidden service introduction points.
7153 Required by fix for bug 3460.
7154 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
7155 public key replay-detection cache from 60 minutes to 5 minutes. This
7156 replay-detection cache is now used only to detect multiple
7157 INTRODUCE2 cells specifying the same rendezvous point, so we can
7158 avoid launching multiple simultaneous attempts to connect to it.
7159 - When a hidden service's introduction point times out, consider
7160 trying it again during the next attempt to connect to the
7161 HS. Previously, we would not try it again unless a newly fetched
7162 descriptor contained it. Required by fixes for bugs 1297 and 3825.
7164 o Minor features (relays):
7165 - Relays now include a reason for regenerating their descriptors
7166 in an HTTP header when uploading to the authorities. This will
7167 make it easier to debug descriptor-upload issues in the future.
7168 - Turn on directory request statistics by default and include them in
7169 extra-info descriptors. Don't break if we have no GeoIP database.
7170 - Replace files in stats/ rather than appending to them. Now that we
7171 include statistics in extra-info descriptors, it makes no sense to
7172 keep old statistics forever. Implements ticket 2930.
7173 - Relays that set "ConnDirectionStatistics 1" write statistics on the
7174 bidirectional use of connections to disk every 24 hours.
7175 - Add a GeoIP file digest to the extra-info descriptor. Implements
7178 o Minor features (new config options):
7179 - New config option "DynamicDHGroups" (disabled by default) provides
7180 each bridge with a unique prime DH modulus to be used during
7181 SSL handshakes. This option attempts to help against censors
7182 who might use the Apache DH modulus as a static identifier for
7183 bridges. Addresses ticket 4548.
7184 - New config option "DisableDebuggerAttachment" (on by default)
7185 to prevent basic debugging attachment attempts by other processes.
7186 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
7187 - Ordinarily, Tor does not count traffic from private addresses (like
7188 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
7189 There is now a new option, CountPrivateBandwidth, to disable this
7190 behavior. Patch from Daniel Cagara.
7192 o Minor features (different behavior for old config options):
7193 - Allow MapAddress directives to specify matches against super-domains,
7194 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
7195 Implements issue 933.
7196 - Don't disable the DirPort when we cannot exceed our AccountingMax
7197 limit during this interval because the effective bandwidthrate is
7198 low enough. This is useful in a situation where AccountMax is only
7199 used as an additional safeguard or to provide statistics.
7200 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
7201 implements ticket 3439.
7202 - When configuring a large set of nodes in EntryNodes, and there are
7203 enough of them listed as Guard so that we don't need to consider
7204 the non-guard entries, prefer the ones listed with the Guard flag.
7205 - If you set the NumCPUs option to 0, Tor will now try to detect how
7206 many CPUs you have. This is the new default behavior.
7207 - The NodeFamily option -- which let you declare that you want to
7208 consider nodes to be part of a family whether they list themselves
7209 that way or not -- now allows IP address ranges and country codes.
7211 o Minor features (new command-line config behavior):
7212 - Slightly change behavior of "list" options (that is, config
7213 options that can appear more than once) when they appear both in
7214 torrc and on the command line. Previously, the command-line options
7215 would be appended to the ones from torrc. Now, the command-line
7216 options override the torrc options entirely. This new behavior
7217 allows the user to override list options (like exit policies and
7218 ports to listen on) from the command line, rather than simply
7219 appending to the list.
7220 - You can get the old (appending) command-line behavior for "list"
7221 options by prefixing the option name with a "+".
7222 - You can remove all the values for a "list" option from the command
7223 line without adding any new ones by prefixing the option name
7226 o Minor features (controller, new events):
7227 - Extend the control protocol to report flags that control a circuit's
7228 path selection in CIRC events and in replies to 'GETINFO
7229 circuit-status'. Implements part of ticket 2411.
7230 - Extend the control protocol to report the hidden service address
7231 and current state of a hidden-service-related circuit in CIRC
7232 events and in replies to 'GETINFO circuit-status'. Implements part
7234 - Include the creation time of a circuit in CIRC and CIRC2
7235 control-port events and the list produced by the 'GETINFO
7236 circuit-status' control-port command.
7237 - Add a new CONF_CHANGED event so that controllers can be notified
7238 of any configuration changes made by other controllers, or by the
7239 user. Implements ticket 1692.
7240 - Add a new SIGNAL event to the controller interface so that
7241 controllers can be notified when Tor handles a signal. Resolves
7242 issue 1955. Patch by John Brooks.
7244 o Minor features (controller, new getinfo options):
7245 - Expose our view of whether we have gone dormant to the controller,
7246 via a new "GETINFO dormant" value. Torbutton and other controllers
7247 can use this to avoid doing periodic requests through Tor while
7248 it's dormant (bug 4718). Resolves ticket 5954.
7249 - Add a new GETINFO option to get total bytes read and written. Patch
7250 from pipe, revised by atagar. Resolves ticket 2345.
7251 - Implement new GETINFO controller fields to provide information about
7252 the Tor process's pid, euid, username, and resource limits.
7254 o Minor features (controller, other):
7255 - Allow controllers to request an event notification whenever a
7256 circuit is cannibalized or its purpose is changed. Implements
7257 part of ticket 3457.
7258 - Use absolute path names when reporting the torrc filename in the
7259 control protocol, so a controller can more easily find the torrc
7260 file. Resolves bug 1101.
7261 - When reporting the path to the cookie file to the controller,
7262 give an absolute path. Resolves ticket 4881.
7264 o Minor features (log messages):
7265 - Add more information to a log statement that might help track down
7266 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
7267 non-IP address" messages (or any Bug messages, for that matter!),
7268 please let us know about it.
7269 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
7270 EntryNodes will have no effect. Resolves issue 2571.
7271 - Try to make the introductory warning message that Tor prints on
7272 startup more useful for actually finding help and information.
7273 Resolves ticket 2474.
7274 - When the system call to create a listener socket fails, log the
7275 error message explaining why. This may help diagnose bug 4027.
7277 o Minor features (other):
7278 - When we fail to initialize Libevent, retry with IOCP disabled so we
7279 don't need to turn on multi-threading support in Libevent, which in
7280 turn requires a working socketpair(). This is a workaround for bug
7281 4457, which affects Libevent versions from 2.0.1-alpha through
7283 - When starting as root and then changing our UID via the User
7284 control option, and we have a ControlSocket configured, make sure
7285 that the ControlSocket is owned by the same account that Tor will
7286 run under. Implements ticket 3421; fix by Jérémy Bobbio.
7287 - Accept attempts to include a password authenticator in the
7288 handshake, as supported by SOCKS5. This handles SOCKS clients that
7289 don't know how to omit a password when authenticating. Resolves
7291 - Check for and recover from inconsistency in the microdescriptor
7292 cache. This will make it harder for us to accidentally free a
7293 microdescriptor without removing it from the appropriate data
7294 structures. Fixes issue 3135; issue noted by "wanoskarnet".
7295 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
7297 o Minor bugfixes (code security):
7298 - Prevent a null-pointer dereference when receiving a data cell
7299 for a nonexistent stream when the circuit in question has an
7300 empty deliver window. We don't believe this is triggerable,
7301 since we don't currently allow deliver windows to become empty,
7302 but the logic is tricky enough that it's better to make the code
7303 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
7304 - Fix a (harmless) integer overflow in cell statistics reported by
7305 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
7306 - Fix our implementation of crypto_random_hostname() so it can't
7307 overflow on ridiculously large inputs. (No Tor version has ever
7308 provided this kind of bad inputs, but let's be correct in depth.)
7309 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
7310 - Add a (probably redundant) memory clear between iterations of
7311 the router status voting loop, to prevent future coding errors
7312 where data might leak between iterations of the loop. Resolves
7315 o Minor bugfixes (wrapper functions):
7316 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
7317 utility function used in the control-port code). This shouldn't
7318 ever happen unless Tor is completely out of memory, but if it did
7319 happen and Tor somehow recovered from it, Tor could have sent a log
7320 message to a control port in the middle of a reply to a controller
7321 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
7322 - Fix some (not actually triggerable) buffer size checks in usage of
7323 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
7325 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
7326 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
7327 - Enforce correct return behavior of tor_vsscanf() when the '%%'
7328 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
7329 - Make our replacement implementation of strtok_r() compatible with
7330 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
7331 bugfix on 0.2.2.1-alpha.
7332 - Find more places in the code that should have been testing for
7333 invalid sockets using the SOCKET_OK macro. Required for a fix
7334 for bug 4533. Bugfix on 0.2.2.28-beta.
7336 o Minor bugfixes (code correctness):
7337 - Check return value of fputs() when writing authority certificate
7338 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
7339 - When building Tor on Windows with -DUNICODE (not default), ensure
7340 that error messages, filenames, and DNS server names are always
7341 NUL-terminated when we convert them to a single-byte encoding.
7342 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
7343 - Fix a memory leak when trying to launch a DNS request when the
7344 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
7346 - Correct file sizes when reading binary files on Cygwin, to avoid
7347 a bug where Tor would fail to read its state file. Fixes bug 6844;
7348 bugfix on 0.1.2.7-alpha.
7349 - Make sure to set *socket_error in all error cases in
7350 connection_connect(), so it can't produce a warning about
7351 errno being zero from errno_to_orconn_end_reason(). Bugfix on
7352 0.2.1.1-alpha; resolves ticket 6028.
7353 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
7354 bug 4532; found by "troll_un".
7356 o Minor bugfixes (clients):
7357 - Allow one-hop directory-fetching circuits the full "circuit build
7358 timeout" period, rather than just half of it, before failing them
7359 and marking the relay down. This fix should help reduce cases where
7360 clients declare relays (or worse, bridges) unreachable because
7361 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
7362 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
7364 - Ensure we don't cannibalize circuits that are longer than three hops
7365 already, so we don't end up making circuits with 5 or more
7366 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
7367 0.1.0.1-rc which introduced cannibalization.
7369 o Minor bugfixes (relays):
7370 - Don't publish a new relay descriptor when we reload our onion key,
7371 unless the onion key has actually changed. Fixes bug 3263 and
7372 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
7373 - When relays refuse a "create" cell because their queue of pending
7374 create cells is too big (typically because their cpu can't keep up
7375 with the arrival rate), send back reason "resource limit" rather
7376 than reason "internal", so network measurement scripts can get a
7377 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
7378 - Exit nodes don't need to fetch certificates for authorities that
7379 they don't recognize; only directory authorities, bridges,
7380 and caches need to do that. Fixes part of bug 2297; bugfix on
7383 o Minor bugfixes (directory authority / mirrors):
7384 - Avoid O(n^2) performance characteristics when parsing a large
7385 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
7386 - Authorities no longer include any router in their microdescriptor
7387 consensuses for which they couldn't generate or agree on a
7388 microdescriptor. Fixes the second piece of bug 6404; fix on
7390 - When checking for requested signatures on the latest consensus
7391 before serving it to a client, make sure to check the right
7392 consensus flavor. Bugfix on 0.2.2.6-alpha.
7393 - Fix an edge case where TestingTorNetwork is set but the authorities
7394 and relays all have an uptime of zero, so the private Tor network
7395 could briefly lack support for hidden services. Fixes bug 3886;
7396 bugfix on 0.2.2.18-alpha.
7397 - Directory caches no longer refuse to clean out descriptors because
7398 of missing v2 networkstatus documents, unless they're configured
7399 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
7400 0.2.2.26-beta. Patch by Daniel Bryg.
7401 - Don't serve or accept v2 hidden service descriptors over a relay's
7402 DirPort. It's never correct to do so, and disabling it might
7403 make it more annoying to exploit any bugs that turn up in the
7404 descriptor-parsing code. Fixes bug 7149.
7406 o Minor bugfixes (hidden services, client-side):
7407 - Assert that hidden-service-related operations are not performed
7408 using single-hop circuits. Previously, Tor would assert that
7409 client-side streams are not attached to single-hop circuits,
7410 but not that other sensitive operations on the client and service
7411 side are not performed using single-hop circuits. Fixes bug 3332;
7413 - Avoid undefined behavior when parsing the list of supported
7414 rendezvous/introduction protocols in a hidden service descriptor.
7415 Previously, Tor would have confused (as-yet-unused) protocol version
7416 numbers greater than 32 with lower ones on many platforms. Fixes
7417 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
7418 - Don't close hidden service client circuits which have almost
7419 finished connecting to their destination when they reach
7420 the normal circuit-build timeout. Previously, we would close
7421 introduction circuits which are waiting for an acknowledgement
7422 from the introduction point, and rendezvous circuits which have
7423 been specified in an INTRODUCE1 cell sent to a hidden service,
7424 after the normal CBT. Now, we mark them as 'timed out', and launch
7425 another rendezvous attempt in parallel. This behavior change can
7426 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
7427 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
7429 o Minor bugfixes (hidden services, service-side):
7430 - Don't close hidden-service-side rendezvous circuits when they
7431 reach the normal circuit-build timeout. This behavior change can
7432 be disabled using the new
7433 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
7434 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
7435 - Don't launch more than 10 service-side introduction-point circuits
7436 for a hidden service in five minutes. Previously, we would consider
7437 launching more introduction-point circuits if at least one second
7438 had passed without any introduction-point circuits failing. Fixes
7439 bug 4607; bugfix on 0.0.7pre1.
7441 o Minor bugfixes (config option behavior):
7442 - If the user tries to set MyFamily on a bridge, refuse to
7443 do so, and warn about the security implications. Fixes bug 4657;
7444 bugfix on 0.2.0.3-alpha.
7445 - The "--quiet" and "--hush" options now apply not only to Tor's
7446 behavior before logs are configured, but also to Tor's behavior in
7447 the absense of configured logs. Fixes bug 3550; bugfix on
7449 - Change the AllowDotExit rules so they should actually work.
7450 We now enforce AllowDotExit only immediately after receiving an
7451 address via SOCKS or DNSPort: other sources are free to provide
7452 .exit addresses after the resolution occurs. Fixes bug 3940;
7453 bugfix on 0.2.2.1-alpha.
7454 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
7455 don't depend on the consensus parameters or compute adaptive
7456 timeouts when it is disabled. Fixes bug 5049; bugfix on
7458 - After we pick a directory mirror, we would refuse to use it if
7459 it's in our ExcludeExitNodes list, resulting in mysterious failures
7460 to bootstrap for people who just wanted to avoid exiting from
7461 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
7462 - When told to add a bridge with the same digest as a preexisting
7463 bridge but a different addr:port, change the addr:port as
7464 requested. Previously we would not notice the change. Fixes half
7465 of bug 5603; fix on 0.2.2.26-beta.
7467 o Minor bugfixes (controller):
7468 - Allow manual 'authenticate' commands to the controller interface
7469 from netcat (nc) as well as telnet. We were rejecting them because
7470 they didn't come with the expected whitespace at the end of the
7471 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
7472 - Report a real bootstrap problem to the controller on router
7473 identity mismatch. Previously we just said "foo", which probably
7474 made a lot of sense at the time. Fixes bug 4169; bugfix on
7476 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
7477 option is set to 0 (which Vidalia version 0.2.16 now does when
7478 a SAVECONF attempt fails), perform other actions that SIGHUP
7479 usually causes (like reopening the logs). Fixes bug 5095; bugfix
7481 - Correctly handle checking the permissions on the parent
7482 directory of a control socket in the root directory. Bug found
7483 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
7485 - End AUTHCHALLENGE error messages (in the control protocol) with
7486 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
7488 o Minor bugfixes (network reading/writing):
7489 - Disable writing on marked-for-close connections when they are
7490 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
7491 bug 5263; bugfix on 0.0.2pre13, where we first added a special
7492 case for flushing marked connections.
7493 - Make sure that there are no unhandled pending TLS errors before
7494 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
7495 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
7496 Bugfix on 0.1.0.5-rc; fixes bug 4528.
7497 - Detect SSL handshake even when the initial attempt to write the
7498 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
7499 - If the client fails to set a reasonable set of ciphersuites
7500 during its v2 handshake renegotiation, allow the renegotiation to
7501 continue nevertheless (i.e. send all the required certificates).
7502 Fixes bug 4591; bugfix on 0.2.0.20-rc.
7504 o Minor bugfixes (other):
7505 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
7506 resource exhaustion, so that clients can adjust their load to
7507 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
7508 started using END_STREAM_REASON_RESOURCELIMIT.
7509 - Don't check for whether the address we're using for outbound
7510 connections has changed until after the outbound connection has
7511 completed. On Windows, getsockname() doesn't succeed until the
7512 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
7513 - Don't hold a Windows file handle open for every file mapping;
7514 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
7516 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
7517 bugfix on 0.2.1.10-alpha.
7518 - If we fail to write a microdescriptor to the disk cache, do not
7519 continue replacing the old microdescriptor file. Fixes bug 2954;
7520 bugfix on 0.2.2.6-alpha.
7522 o Minor bugfixes (log messages, path selection):
7523 - Downgrade "set buildtimeout to low value" messages to "info"
7524 severity; they were never an actual problem, there was never
7525 anything reasonable to do about them, and they tended to spam logs
7526 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
7527 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
7528 more information to it, so that we can track it down in case it
7529 returns again. Mitigates bug 5235.
7530 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
7531 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
7532 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
7533 - Issue a log message if a guard completes less than 40% of your
7534 circuits. Threshold is configurable by torrc option
7535 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
7536 additional, off-by-default code to disable guards which fail too
7537 many circuits. Addresses ticket 5458.
7539 o Minor bugfixes (log messages, client):
7540 - Downgrade "Got a certificate, but we already have it" log messages
7541 from warning to info, except when we're a dirauth. Fixes bug 5238;
7542 bugfix on 0.2.1.7-alpha.
7543 - Fix the log message describing how we work around discovering
7544 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
7545 4837; bugfix on 0.2.2.9-alpha.
7546 - When logging about a disallowed .exit name, do not also call it
7547 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
7548 - Fix a log message suggesting that people contact a non-existent
7549 email address. Fixes bug 3448.
7550 - Rephrase the log message emitted if the TestSocks check is
7551 successful. Patch from Fabian Keil; fixes bug 4094.
7552 - Log (at debug level) whenever a circuit's purpose is changed.
7553 - Log SSL state transitions at log level DEBUG, log domain
7554 HANDSHAKE. This can be useful for debugging censorship events.
7555 Implements ticket 3264.
7556 - We now log which torrc file we're using on startup. Implements
7558 - Rate-limit log messages when asked to connect anonymously to
7559 a private address. When these hit, they tended to hit fast and
7560 often. Also, don't bother trying to connect to addresses that we
7561 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
7562 reply makes us think we have been lied to, even when the address the
7563 client tried to connect to was "localhost." Resolves ticket 2822.
7565 o Minor bugfixes (log messages, non-client):
7566 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
7567 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
7568 - Don't log that we have "decided to publish new relay descriptor"
7569 unless we are actually publishing a descriptor. Fixes bug 3942;
7570 bugfix on 0.2.2.28-beta.
7571 - Log which authority we're missing votes from when we go to fetch
7572 them from the other auths.
7573 - Replace "Sending publish request" log messages with "Launching
7574 upload", so that they no longer confusingly imply that we're
7575 sending something to a directory we might not even be connected
7576 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
7577 - Warn when Tor is configured to use accounting in a way that can
7578 link a hidden service to some other hidden service or public
7579 address. Resolves ticket 6490.
7580 - Fix a minor formatting issue in one of tor-gencert's error messages.
7584 - Update to the latest version of the tinytest unit testing framework.
7585 This includes a couple of bugfixes that can be relevant for
7586 running forked unit tests on Windows, and removes all reserved
7588 - Avoid a false positive in the util/threads unit test by increasing
7589 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
7590 - Make it possible to set the TestingTorNetwork configuration
7591 option using AlternateDirAuthority and AlternateBridgeAuthority
7592 as an alternative to setting DirServer. Addresses ticket 6377.
7593 - Add a unit test for the environment_variable_names_equal() function.
7594 - A wide variety of new unit tests by Esteban Manchado Velázquez.
7595 - Numerous new unit tests for functions in util.c and address.c by
7597 - The long-disabled benchmark tests are now split into their own
7598 ./src/test/bench binary.
7599 - The benchmark tests can now use more accurate timers than
7600 gettimeofday() when such timers are available.
7601 - Use tt_assert(), not tor_assert(), for checking for test failures.
7602 This makes the unit tests more able to go on in the event that
7605 o Build improvements:
7606 - Use the dead_strip option when building Tor on OS X. This reduces
7607 binary size by almost 19% when linking openssl and libevent
7608 statically, which we do for Tor Browser Bundle.
7609 - Provide a better error message about possible OSX Asciidoc failure
7610 reasons. Fixes bug 6436.
7611 - Detect attempts to build Tor on (as yet hypothetical) versions
7612 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
7613 fix for bug 4533. Bugfix on 0.2.2.28-beta.
7614 - On Windows, we now define the _WIN32_WINNT macros only if they
7615 are not already defined. This lets the person building Tor decide,
7616 if they want, to require a later version of Windows.
7617 - Our autogen.sh script now uses autoreconf to launch autoconf,
7618 automake, and so on. This is more robust against some of the failure
7619 modes associated with running the autotools pieces on their own.
7620 - Running "make version" now displays the version of Tor that
7621 we're about to build. Idea from katmagic; resolves issue 4400.
7622 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
7623 on 0.2.2.4-alpha; fixes bug 3427.
7624 - New --enable-static-tor configure option for building Tor as
7625 statically as possible. Idea, general hackery and thoughts from
7626 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
7628 - Limited, experimental support for building with nmake and MSVC.
7630 o Build requirements:
7631 - Building Tor with bufferevent support now requires Libevent
7632 2.0.13-stable or later. Previous versions of Libevent had bugs in
7633 SSL-related bufferevents and related issues that would make Tor
7634 work badly with bufferevents. Requiring 2.0.13-stable also allows
7635 Tor with bufferevents to take advantage of Libevent APIs
7636 introduced after 2.0.8-rc.
7637 - Our build system requires automake 1.6 or later to create the
7638 Makefile.in files. Previously, you could have used 1.4.
7639 This only affects developers and people building Tor from git;
7640 people who build Tor from the source distribution without changing
7641 the Makefile.am files should be fine.
7642 - Detect when we try to build on a platform that doesn't define
7643 AF_UNSPEC to 0. We don't work there, so refuse to compile.
7645 o Build fixes (compile/link):
7646 - Format more doubles with %f, not %lf. Patch from grarpamp to make
7647 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
7649 - When building with --enable-static-tor on OpenBSD, do not
7650 erroneously attempt to link -lrt. Fixes bug 5103.
7651 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
7652 that IPv6 stuff will compile on MSVC, and compilation issues
7653 will be easier to track down. Fixes bug 5861.
7654 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
7655 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
7656 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
7657 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
7659 o Build fixes (other):
7660 - Use the _WIN32 macro throughout our code to detect Windows.
7661 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
7663 - Properly handle the case where the build-tree is not the same
7664 as the source tree when generating src/common/common_sha1.i,
7665 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
7666 bugfix on 0.2.0.1-alpha.
7667 - During configure, search for library containing cos function as
7668 libm lives in libcore on some platforms (BeOS/Haiku). Linking
7669 against libm was hard-coded before. Fixes the first part of bug
7670 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
7672 - Prevent a false positive from the check-spaces script, by disabling
7673 the "whitespace between function name and (" check for functions
7676 o Packaging (RPM) changes:
7677 - Update our default RPM spec files to work with mock and rpmbuild
7678 on RHEL/Fedora. They have an updated set of dependencies and
7679 conflicts, a fix for an ancient typo when creating the "_tor"
7680 user, and better instructions. Thanks to Ondrej Mikle for the
7681 patch series. Fixes bug 6043.
7682 - On OpenSUSE, create the /var/run/tor directory on startup if it
7683 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
7685 o Code refactoring (safety):
7686 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
7687 10 lines. Also, don't nest them. Doing so in the past has
7688 led to hard-to-debug code. The new style is to use the
7689 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
7690 - Use macros to indicate OpenSSL versions, so we don't need to worry
7691 about accidental hexadecimal bit shifts.
7692 - Use tor_sscanf() in place of scanf() in more places through the
7693 code. This makes us a little more locale-independent, and
7694 should help shut up code-analysis tools that can't tell
7695 a safe sscanf string from a dangerous one.
7696 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
7697 - Use the smartlist_add_asprintf() alias more consistently.
7699 o Code refactoring (consolidate):
7700 - A major revision to our internal node-selecting and listing logic.
7701 Tor already had at least two major ways to look at the question of
7702 "which Tor servers do we know about": a list of router descriptors,
7703 and a list of entries in the current consensus. With
7704 microdescriptors, we're adding a third. Having so many systems
7705 without an abstraction layer over them was hurting the codebase.
7706 Now, we have a new "node_t" abstraction that presents a consistent
7707 interface to a client's view of a Tor node, and holds (nearly) all
7708 of the mutable state formerly in routerinfo_t and routerstatus_t.
7709 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
7710 Libevent's notion of cached time when possible.
7711 - Remove duplicate code for invoking getrlimit() from control.c.
7712 - Use OpenSSL's built-in SSL_state_string_long() instead of our
7713 own homebrewed ssl_state_to_string() replacement. Patch from
7714 Emile Snyder. Fixes bug 4653.
7715 - Change the symmetric cipher interface so that creating and
7716 initializing a stream cipher are no longer separate functions.
7718 o Code refactoring (separate):
7719 - Make a new "entry connection" struct as an internal subtype of "edge
7720 connection", to simplify the code and make exit connections smaller.
7721 - Split connection_about_to_close() into separate functions for each
7723 - Rewrite the listener-selection logic so that parsing which ports
7724 we want to listen on is now separate from binding to the ports
7727 o Code refactoring (name changes):
7728 - Rename a handful of old identifiers, mostly related to crypto
7729 structures and crypto functions. By convention, our "create an
7730 object" functions are called "type_new()", our "free an object"
7731 functions are called "type_free()", and our types indicate that
7732 they are types only with a final "_t". But a handful of older
7733 types and functions broke these rules, with function names like
7734 "type_create" or "subsystem_op_type", or with type names like
7736 - Rename Tor functions that turn strings into addresses, so that
7737 "parse" indicates that no hostname resolution occurs, and
7738 "lookup" indicates that hostname resolution may occur. This
7739 should help prevent mistakes in the future. Fixes bug 3512.
7740 - Use the name "CERTS" consistently to refer to the new cell type;
7741 we were calling it CERT in some places and CERTS in others.
7742 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
7743 invalid value, rather than just -1.
7744 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
7745 can pick them up when the tests aren't disabled. Bugfix on
7746 0.2.2.4-alpha which introduced tinytest.
7748 o Code refactoring (other):
7749 - Defensively refactor rend_mid_rendezvous() so that protocol
7750 violations and length checks happen in the beginning. Fixes
7752 - Remove the pure attribute from all functions that used it
7753 previously. In many cases we assigned it incorrectly, because the
7754 functions might assert or call impure functions, and we don't have
7755 evidence that keeping the pure attribute is worthwhile. Implements
7756 changes suggested in ticket 4421.
7757 - Move the replay-detection cache for the RSA-encrypted parts of
7758 INTRODUCE2 cells to the introduction point data structures.
7759 Previously, we would use one replay-detection cache per hidden
7760 service. Required by fix for bug 3460.
7761 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
7762 no longer link against Libevent: they never used it, but
7763 our library structure used to force them to link it.
7765 o Removed features and files:
7766 - Remove all internal support for unpadded RSA. We never used it, and
7767 it would be a bad idea to start.
7768 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
7770 - Remove some redundant #include directives throughout the code.
7771 Patch from Andrea Gelmini.
7772 - Remove some old code to remember statistics about which descriptors
7773 we've served as a directory mirror. The feature wasn't used and
7774 is outdated now that microdescriptors are around.
7775 - Remove some old code to work around even older versions of Tor that
7776 used forked processes to handle DNS requests. Such versions of Tor
7777 are no longer in use as relays.
7778 - The "torify" script no longer supports the "tsocks" socksifier
7779 tool, since tsocks doesn't support DNS and UDP right for Tor.
7780 Everyone should be using torsocks instead. Fixes bugs 3530 and
7781 5180. Based on a patch by "ugh".
7782 - Remove the torrc.bridge file: we don't use it for anything, and
7783 it had become badly desynchronized from torrc.sample. Resolves
7787 - Begin a doc/state-contents.txt file to explain the contents of
7788 the Tor state file. Fixes bug 2987.
7789 - Clarify the documentation for the Alternate*Authority options.
7791 - Document the --defaults-torrc option, and the new semantics for
7792 overriding, extending, and clearing lists of options. Closes
7794 - Add missing man page documentation for consensus and microdesc
7795 files. Resolves ticket 6732.
7796 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
7798 o Documentation fixes:
7799 - Improve the manual's documentation for the NT Service command-line
7800 options. Addresses ticket 3964.
7801 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
7802 - Document the changes to the ORPort and DirPort options, and the
7803 fact that {OR/Dir}ListenAddress is now unnecessary (and
7804 therefore deprecated). Resolves ticket 5597.
7805 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
7806 - Clarify that hidden services are TCP only. Fixes bug 6024.
7809 Changes in version 0.2.2.39 - 2012-09-11
7810 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
7814 - Fix an assertion failure in tor_timegm() that could be triggered
7815 by a badly formatted directory object. Bug found by fuzzing with
7816 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
7817 - Do not crash when comparing an address with port value 0 to an
7818 address policy. This bug could have been used to cause a remote
7819 assertion failure by or against directory authorities, or to
7820 allow some applications to crash clients. Fixes bug 6690; bugfix
7824 Changes in version 0.2.2.38 - 2012-08-12
7825 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
7826 attack that could in theory leak path information.
7829 - Avoid an uninitialized memory read when reading a vote or consensus
7830 document that has an unrecognized flavor name. This read could
7831 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
7832 - Try to leak less information about what relays a client is
7833 choosing to a side-channel attacker. Previously, a Tor client would
7834 stop iterating through the list of available relays as soon as it
7835 had chosen one, thus finishing a little earlier when it picked
7836 a router earlier in the list. If an attacker can recover this
7837 timing information (nontrivial but not proven to be impossible),
7838 they could learn some coarse-grained information about which relays
7839 a client was picking (middle nodes in particular are likelier to
7840 be affected than exits). The timing attack might be mitigated by
7841 other factors (see bug 6537 for some discussion), but it's best
7842 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
7845 Changes in version 0.2.2.37 - 2012-06-06
7846 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
7847 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
7851 - Work around a bug in OpenSSL that broke renegotiation with TLS
7852 1.1 and TLS 1.2. Without this workaround, all attempts to speak
7853 the v2 Tor connection protocol when both sides were using OpenSSL
7854 1.0.1 would fail. Resolves ticket 6033.
7855 - When waiting for a client to renegotiate, don't allow it to add
7856 any bytes to the input buffer. This fixes a potential DoS issue.
7857 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
7858 - Fix an edge case where if we fetch or publish a hidden service
7859 descriptor, we might build a 4-hop circuit and then use that circuit
7860 for exiting afterwards -- even if the new last hop doesn't obey our
7861 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
7864 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
7865 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
7868 - Tell GCC and Clang to check for any errors in format strings passed
7869 to the tor_v*(print|scan)f functions.
7872 Changes in version 0.2.2.36 - 2012-05-24
7873 Tor 0.2.2.36 updates the addresses for two of the eight directory
7874 authorities, fixes some potential anonymity and security issues,
7875 and fixes several crash bugs.
7877 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
7878 known flaws, and nobody should be using them. You should upgrade. If
7879 you're using a Linux or BSD and its packages are obsolete, stop using
7880 those packages and upgrade anyway.
7882 o Directory authority changes:
7883 - Change IP address for maatuska (v3 directory authority).
7884 - Change IP address for ides (v3 directory authority), and rename
7888 - When building or running with any version of OpenSSL earlier
7889 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
7890 versions have a bug (CVE-2011-4576) in which their block cipher
7891 padding includes uninitialized data, potentially leaking sensitive
7892 information to any peer with whom they make a SSLv3 connection. Tor
7893 does not use SSL v3 by default, but a hostile client or server
7894 could force an SSLv3 connection in order to gain information that
7895 they shouldn't have been able to get. The best solution here is to
7896 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
7897 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
7898 to make sure that the bug can't happen.
7899 - Never use a bridge or a controller-supplied node as an exit, even
7900 if its exit policy allows it. Found by wanoskarnet. Fixes bug
7901 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
7902 and 0.2.0.3-alpha (for bridge-purpose descriptors).
7903 - Only build circuits if we have a sufficient threshold of the total
7904 descriptors that are marked in the consensus with the "Exit"
7905 flag. This mitigates an attack proposed by wanoskarnet, in which
7906 all of a client's bridges collude to restrict the exit nodes that
7907 the client knows about. Fixes bug 5343.
7908 - Provide controllers with a safer way to implement the cookie
7909 authentication mechanism. With the old method, if another locally
7910 running program could convince a controller that it was the Tor
7911 process, then that program could trick the controller into telling
7912 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
7913 authentication method uses a challenge-response approach to prevent
7914 this attack. Fixes bug 5185; implements proposal 193.
7917 - Avoid logging uninitialized data when unable to decode a hidden
7918 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
7919 - Avoid a client-side assertion failure when receiving an INTRODUCE2
7920 cell on a general purpose circuit. Fixes bug 5644; bugfix on
7922 - Fix builds when the path to sed, openssl, or sha1sum contains
7923 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
7925 - Correct our replacements for the timeradd() and timersub() functions
7926 on platforms that lack them (for example, Windows). The timersub()
7927 function is used when expiring circuits, while timeradd() is
7928 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
7929 bugfix on 0.2.2.24-alpha.
7930 - Fix the SOCKET_OK test that we use to tell when socket
7931 creation fails so that it works on Win64. Fixes part of bug 4533;
7932 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
7935 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
7936 Fixes bug 5346; bugfix on 0.0.8pre3.
7937 - Make our number-parsing functions always treat too-large values
7938 as an error, even when those values exceed the width of the
7939 underlying type. Previously, if the caller provided these
7940 functions with minima or maxima set to the extreme values of the
7941 underlying integer type, these functions would return those
7942 values on overflow rather than treating overflow as an error.
7943 Fixes part of bug 5786; bugfix on 0.0.9.
7944 - Older Linux kernels erroneously respond to strange nmap behavior
7945 by having accept() return successfully with a zero-length
7946 socket. When this happens, just close the connection. Previously,
7947 we would try harder to learn the remote address: but there was
7948 no such remote address to learn, and our method for trying to
7949 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
7950 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
7951 - Correct parsing of certain date types in parse_http_time().
7952 Without this patch, If-Modified-Since would behave
7953 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
7954 Esteban Manchado Velázques.
7955 - Change the BridgePassword feature (part of the "bridge community"
7956 design, which is not yet implemented) to use a time-independent
7957 comparison. The old behavior might have allowed an adversary
7958 to use timing to guess the BridgePassword value. Fixes bug 5543;
7959 bugfix on 0.2.0.14-alpha.
7960 - Detect and reject certain misformed escape sequences in
7961 configuration values. Previously, these values would cause us
7962 to crash if received in a torrc file or over an authenticated
7963 control port. Bug found by Esteban Manchado Velázquez, and
7964 independently by Robert Connolly from Matta Consulting who further
7965 noted that it allows a post-authentication heap overflow. Patch
7966 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
7967 bugfix on 0.2.0.16-alpha.
7968 - Fix a compile warning when using the --enable-openbsd-malloc
7969 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
7970 - During configure, detect when we're building with clang version
7971 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
7972 CFLAGS. clang doesn't support them yet.
7973 - When sending an HTTP/1.1 proxy request, include a Host header.
7974 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
7975 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
7976 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
7977 - If we hit the error case where routerlist_insert() replaces an
7978 existing (old) server descriptor, make sure to remove that
7979 server descriptor from the old_routers list. Fix related to bug
7980 1776. Bugfix on 0.2.2.18-alpha.
7982 o Minor bugfixes (documentation and log messages):
7983 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
7984 Fixes bug 4856; bugfix on Tor 0.0.6.
7985 - Update "ClientOnly" man page entry to explain that there isn't
7986 really any point to messing with it. Resolves ticket 5005.
7987 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
7988 directory authority option (introduced in Tor 0.2.2.34).
7989 - Downgrade the "We're missing a certificate" message from notice
7990 to info: people kept mistaking it for a real problem, whereas it
7991 is seldom the problem even when we are failing to bootstrap. Fixes
7992 bug 5067; bugfix on 0.2.0.10-alpha.
7993 - Correctly spell "connect" in a log message on failure to create a
7994 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
7995 - Clarify the behavior of MaxCircuitDirtiness with hidden service
7996 circuits. Fixes issue 5259.
7999 - Directory authorities now reject versions of Tor older than
8000 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
8001 inclusive. These versions accounted for only a small fraction of
8002 the Tor network, and have numerous known security issues. Resolves
8004 - Update to the May 1 2012 Maxmind GeoLite Country database.
8007 - When sending or relaying a RELAY_EARLY cell, we used to convert
8008 it to a RELAY cell if the connection was using the v1 link
8009 protocol. This was a workaround for older versions of Tor, which
8010 didn't handle RELAY_EARLY cells properly. Now that all supported
8011 versions can handle RELAY_EARLY cells, and now that we're enforcing
8012 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
8013 remove this workaround. Addresses bug 4786.
8016 Changes in version 0.2.2.35 - 2011-12-16
8017 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
8018 buffers code. Absolutely everybody should upgrade.
8020 The bug relied on an incorrect calculation when making data continuous
8021 in one of our IO buffers, if the first chunk of the buffer was
8022 misaligned by just the wrong amount. The miscalculation would allow an
8023 attacker to overflow a piece of heap-allocated memory. To mount this
8024 attack, the attacker would need to either open a SOCKS connection to
8025 Tor's SocksPort (usually restricted to localhost), or target a Tor
8026 instance configured to make its connections through a SOCKS proxy
8027 (which Tor does not do by default).
8029 Good security practice requires that all heap-overflow bugs should be
8030 presumed to be exploitable until proven otherwise, so we are treating
8031 this as a potential code execution attack. Please upgrade immediately!
8032 This bug does not affect bufferevents-based builds of Tor. Special
8033 thanks to "Vektor" for reporting this issue to us!
8035 Tor 0.2.2.35 also fixes several bugs in previous versions, including
8036 crash bugs for unusual configurations, and a long-term bug that
8037 would prevent Tor from starting on Windows machines with draconian
8040 With this release, we remind everyone that 0.2.0.x has reached its
8041 formal end-of-life. Those Tor versions have many known flaws, and
8042 nobody should be using them. You should upgrade -- ideally to the
8043 0.2.2.x series. If you're using a Linux or BSD and its packages are
8044 obsolete, stop using those packages and upgrade anyway.
8046 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
8047 longer receive support after some time in early 2012.
8050 - Fix a heap overflow bug that could occur when trying to pull
8051 data into the first chunk of a buffer, when that chunk had
8052 already had some data drained from it. Fixes CVE-2011-2778;
8053 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
8054 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
8055 that it doesn't attempt to allocate a socketpair. This could cause
8056 some problems on Windows systems with overzealous firewalls. Fix for
8057 bug 4457; workaround for Libevent versions 2.0.1-alpha through
8059 - If we mark an OR connection for close based on a cell we process,
8060 don't process any further cells on it. We already avoid further
8061 reads on marked-for-close connections, but now we also discard the
8062 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
8063 which was the first version where we might mark a connection for
8064 close based on processing a cell on it.
8065 - Correctly sanity-check that we don't underflow on a memory
8066 allocation (and then assert) for hidden service introduction
8067 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
8068 bugfix on 0.2.1.5-alpha.
8069 - Fix a memory leak when we check whether a hidden service
8070 descriptor has any usable introduction points left. Fixes bug
8071 4424. Bugfix on 0.2.2.25-alpha.
8072 - Don't crash when we're running as a relay and don't have a GeoIP
8073 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
8074 we've had in the 0.2.3.x branch already.
8075 - When running as a client, do not print a misleading (and plain
8076 wrong) log message that we're collecting "directory request"
8077 statistics: clients don't collect statistics. Also don't create a
8078 useless (because empty) stats file in the stats/ directory. Fixes
8079 bug 4353; bugfix on 0.2.2.34.
8082 - Detect failure to initialize Libevent. This fix provides better
8083 detection for future instances of bug 4457.
8084 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
8085 function. This was eating up hideously large amounts of time on some
8086 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
8087 - Resolve an integer overflow bug in smartlist_ensure_capacity().
8088 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
8090 - Don't warn about unused log_mutex in log.c when building with
8091 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
8092 0.1.0.6-rc which introduced --disable-threads.
8093 - When configuring, starting, or stopping an NT service, stop
8094 immediately after the service configuration attempt has succeeded
8095 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
8096 - When sending a NETINFO cell, include the original address
8097 received for the other side, not its canonical address. Found
8098 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
8099 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
8100 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
8101 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
8102 occurred when a client tried to fetch a descriptor for a bridge
8103 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
8104 - Backport fixes for a pair of compilation warnings on Windows.
8105 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
8106 - If we had ever tried to call tor_addr_to_str on an address of
8107 unknown type, we would have done a strdup on an uninitialized
8108 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
8109 Reported by "troll_un".
8110 - Correctly detect and handle transient lookup failures from
8111 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
8112 Reported by "troll_un".
8113 - Fix null-pointer access that could occur if TLS allocation failed.
8114 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
8115 - Use tor_socket_t type for listener argument to accept(). Fixes bug
8116 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
8119 - Add two new config options for directory authorities:
8120 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
8121 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
8122 that is always sufficient to satisfy the bandwidth requirement for
8123 the Guard flag. Now it will be easier for researchers to simulate
8124 Tor networks with different values. Resolves ticket 4484.
8125 - When Tor ignores a hidden service specified in its configuration,
8126 include the hidden service's directory in the warning message.
8127 Previously, we would only tell the user that some hidden service
8128 was ignored. Bugfix on 0.0.6; fixes bug 4426.
8129 - Update to the December 6 2011 Maxmind GeoLite Country database.
8131 o Packaging changes:
8132 - Make it easier to automate expert package builds on Windows,
8133 by removing an absolute path from makensis.exe command.
8136 Changes in version 0.2.1.32 - 2011-12-16
8137 Tor 0.2.1.32 backports important security and privacy fixes for
8138 oldstable. This release is intended only for package maintainers and
8139 others who cannot use the 0.2.2 stable series. All others should be
8140 using Tor 0.2.2.x or newer.
8142 The Tor 0.2.1.x series will reach formal end-of-life some time in
8143 early 2012; we will stop releasing patches for it then.
8145 o Major bugfixes (also included in 0.2.2.x):
8146 - Correctly sanity-check that we don't underflow on a memory
8147 allocation (and then assert) for hidden service introduction
8148 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
8149 bugfix on 0.2.1.5-alpha.
8150 - Fix a heap overflow bug that could occur when trying to pull
8151 data into the first chunk of a buffer, when that chunk had
8152 already had some data drained from it. Fixes CVE-2011-2778;
8153 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
8156 - Update to the December 6 2011 Maxmind GeoLite Country database.
8159 Changes in version 0.2.2.34 - 2011-10-26
8160 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
8161 can deanonymize Tor users. Everybody should upgrade.
8163 The attack relies on four components: 1) Clients reuse their TLS cert
8164 when talking to different relays, so relays can recognize a user by
8165 the identity key in her cert. 2) An attacker who knows the client's
8166 identity key can probe each guard relay to see if that identity key
8167 is connected to that guard relay right now. 3) A variety of active
8168 attacks in the literature (starting from "Low-Cost Traffic Analysis
8169 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
8170 discover the guard relays that a Tor user visiting the website is using.
8171 4) Clients typically pick three guards at random, so the set of guards
8172 for a given user could well be a unique fingerprint for her. This
8173 release fixes components #1 and #2, which is enough to block the attack;
8174 the other two remain as open research problems. Special thanks to
8175 "frosty_un" for reporting the issue to us!
8177 Clients should upgrade so they are no longer recognizable by the TLS
8178 certs they present. Relays should upgrade so they no longer allow a
8179 remote attacker to probe them to test whether unpatched clients are
8180 currently connected to them.
8182 This release also fixes several vulnerabilities that allow an attacker
8183 to enumerate bridge relays. Some bridge enumeration attacks still
8184 remain; see for example proposal 188.
8186 o Privacy/anonymity fixes (clients):
8187 - Clients and bridges no longer send TLS certificate chains on
8188 outgoing OR connections. Previously, each client or bridge would
8189 use the same cert chain for all outgoing OR connections until
8190 its IP address changes, which allowed any relay that the client
8191 or bridge contacted to determine which entry guards it is using.
8192 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
8193 - If a relay receives a CREATE_FAST cell on a TLS connection, it
8194 no longer considers that connection as suitable for satisfying a
8195 circuit EXTEND request. Now relays can protect clients from the
8196 CVE-2011-2768 issue even if the clients haven't upgraded yet.
8197 - Directory authorities no longer assign the Guard flag to relays
8198 that haven't upgraded to the above "refuse EXTEND requests
8199 to client connections" fix. Now directory authorities can
8200 protect clients from the CVE-2011-2768 issue even if neither
8201 the clients nor the relays have upgraded yet. There's a new
8202 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
8203 to let us transition smoothly, else tomorrow there would be no
8206 o Privacy/anonymity fixes (bridge enumeration):
8207 - Bridge relays now do their directory fetches inside Tor TLS
8208 connections, like all the other clients do, rather than connecting
8209 directly to the DirPort like public relays do. Removes another
8210 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
8211 - Bridges relays now build circuits for themselves in a more similar
8212 way to how clients build them. Removes another avenue for
8213 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
8214 when bridges were introduced.
8215 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
8216 that they initiated. Relays could distinguish incoming bridge
8217 connections from client connections, creating another avenue for
8218 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
8219 Found by "frosty_un".
8222 - Fix a crash bug when changing node restrictions while a DNS lookup
8223 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
8225 - Don't launch a useless circuit after failing to use one of a
8226 hidden service's introduction points. Previously, we would
8227 launch a new introduction circuit, but not set the hidden service
8228 which that circuit was intended to connect to, so it would never
8229 actually be used. A different piece of code would then create a
8230 new introduction circuit correctly. Bug reported by katmagic and
8231 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
8234 - Change an integer overflow check in the OpenBSD_Malloc code so
8235 that GCC is less likely to eliminate it as impossible. Patch
8236 from Mansour Moufid. Fixes bug 4059.
8237 - When a hidden service turns an extra service-side introduction
8238 circuit into a general-purpose circuit, free the rend_data and
8239 intro_key fields first, so we won't leak memory if the circuit
8240 is cannibalized for use as another service-side introduction
8241 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
8242 - Bridges now skip DNS self-tests, to act a little more stealthily.
8243 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
8244 bridges. Patch by "warms0x".
8245 - Fix internal bug-checking logic that was supposed to catch
8246 failures in digest generation so that it will fail more robustly
8247 if we ask for a nonexistent algorithm. Found by Coverity Scan.
8248 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
8249 - Report any failure in init_keys() calls launched because our
8250 IP address has changed. Spotted by Coverity Scan. Bugfix on
8251 0.1.1.4-alpha; fixes CID 484.
8253 o Minor bugfixes (log messages and documentation):
8254 - Remove a confusing dollar sign from the example fingerprint in the
8255 man page, and also make the example fingerprint a valid one. Fixes
8256 bug 4309; bugfix on 0.2.1.3-alpha.
8257 - The next version of Windows will be called Windows 8, and it has
8258 a major version of 6, minor version of 2. Correctly identify that
8259 version instead of calling it "Very recent version". Resolves
8260 ticket 4153; reported by funkstar.
8261 - Downgrade log messages about circuit timeout calibration from
8262 "notice" to "info": they don't require or suggest any human
8263 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
8264 bugfix on 0.2.2.14-alpha.
8267 - Turn on directory request statistics by default and include them in
8268 extra-info descriptors. Don't break if we have no GeoIP database.
8269 Backported from 0.2.3.1-alpha; implements ticket 3951.
8270 - Update to the October 4 2011 Maxmind GeoLite Country database.
8273 Changes in version 0.2.1.31 - 2011-10-26
8274 Tor 0.2.1.31 backports important security and privacy fixes for
8275 oldstable. This release is intended only for package maintainers and
8276 others who cannot use the 0.2.2 stable series. All others should be
8277 using Tor 0.2.2.x or newer.
8279 o Security fixes (also included in 0.2.2.x):
8280 - Replace all potentially sensitive memory comparison operations
8281 with versions whose runtime does not depend on the data being
8282 compared. This will help resist a class of attacks where an
8283 adversary can use variations in timing information to learn
8284 sensitive data. Fix for one case of bug 3122. (Safe memcmp
8285 implementation by Robert Ransom based partially on code by DJB.)
8286 - Fix an assert in parsing router descriptors containing IPv6
8287 addresses. This one took down the directory authorities when
8288 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
8290 o Privacy/anonymity fixes (also included in 0.2.2.x):
8291 - Clients and bridges no longer send TLS certificate chains on
8292 outgoing OR connections. Previously, each client or bridge would
8293 use the same cert chain for all outgoing OR connections until
8294 its IP address changes, which allowed any relay that the client
8295 or bridge contacted to determine which entry guards it is using.
8296 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
8297 - If a relay receives a CREATE_FAST cell on a TLS connection, it
8298 no longer considers that connection as suitable for satisfying a
8299 circuit EXTEND request. Now relays can protect clients from the
8300 CVE-2011-2768 issue even if the clients haven't upgraded yet.
8301 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
8302 that they initiated. Relays could distinguish incoming bridge
8303 connections from client connections, creating another avenue for
8304 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
8305 Found by "frosty_un".
8306 - When receiving a hidden service descriptor, check that it is for
8307 the hidden service we wanted. Previously, Tor would store any
8308 hidden service descriptors that a directory gave it, whether it
8309 wanted them or not. This wouldn't have let an attacker impersonate
8310 a hidden service, but it did let directories pre-seed a client
8311 with descriptors that it didn't want. Bugfix on 0.0.6.
8312 - Avoid linkability based on cached hidden service descriptors: forget
8313 all hidden service descriptors cached as a client when processing a
8314 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
8315 - Make the bridge directory authority refuse to answer directory
8316 requests for "all" descriptors. It used to include bridge
8317 descriptors in its answer, which was a major information leak.
8318 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
8319 - Don't attach new streams to old rendezvous circuits after SIGNAL
8320 NEWNYM. Previously, we would keep using an existing rendezvous
8321 circuit if it remained open (i.e. if it were kept open by a
8322 long-lived stream, or if a new stream were attached to it before
8323 Tor could notice that it was old and no longer in use). Bugfix on
8324 0.1.1.15-rc; fixes bug 3375.
8326 o Minor bugfixes (also included in 0.2.2.x):
8327 - When we restart our relay, we might get a successful connection
8328 from the outside before we've started our reachability tests,
8329 triggering a warning: "ORPort found reachable, but I have no
8330 routerinfo yet. Failing to inform controller of success." This
8331 bug was harmless unless Tor is running under a controller
8332 like Vidalia, in which case the controller would never get a
8333 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
8335 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
8336 enabled. Fixes bug 1526.
8337 - Remove undocumented option "-F" from tor-resolve: it hasn't done
8338 anything since 0.2.1.16-rc.
8339 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
8340 None of the cases where we did this before were wrong, but by making
8341 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
8342 - Fix a rare crash bug that could occur when a client was configured
8343 with a large number of bridges. Fixes bug 2629; bugfix on
8344 0.2.1.2-alpha. Bugfix by trac user "shitlei".
8345 - Correct the warning displayed when a rendezvous descriptor exceeds
8346 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
8348 - Fix an uncommon assertion failure when running with DNSPort under
8349 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
8350 - When warning about missing zlib development packages during compile,
8351 give the correct package names. Bugfix on 0.2.0.1-alpha.
8352 - Require that introduction point keys and onion keys have public
8353 exponent 65537. Bugfix on 0.2.0.10-alpha.
8354 - Do not crash when our configuration file becomes unreadable, for
8355 example due to a permissions change, between when we start up
8356 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
8358 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
8360 - Always NUL-terminate the sun_path field of a sockaddr_un before
8361 passing it to the kernel. (Not a security issue: kernels are
8362 smart enough to reject bad sockaddr_uns.) Found by Coverity;
8363 CID #428. Bugfix on Tor 0.2.0.3-alpha.
8364 - Don't stack-allocate the list of supplementary GIDs when we're
8365 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
8366 could take up to 256K, which is way too much stack. Found by
8367 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
8369 o Minor bugfixes (only in 0.2.1.x):
8370 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
8371 rely on them. Bugfix on 0.2.1.30.
8372 - Use git revisions instead of svn revisions when generating our
8373 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
8375 o Minor features (also included in 0.2.2.x):
8376 - Adjust the expiration time on our SSL session certificates to
8377 better match SSL certs seen in the wild. Resolves ticket 4014.
8378 - Allow nameservers with IPv6 address. Resolves bug 2574.
8379 - Update to the October 4 2011 Maxmind GeoLite Country database.
8382 Changes in version 0.2.2.33 - 2011-09-13
8383 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
8384 TLS handshake that makes relays and bridges that run this new version
8385 reachable from Iran again.
8388 - Avoid an assertion failure when reloading a configuration with
8389 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
8390 3923; bugfix on 0.2.2.25-alpha.
8392 o Minor features (security):
8393 - Check for replays of the public-key encrypted portion of an
8394 INTRODUCE1 cell, in addition to the current check for replays of
8395 the g^x value. This prevents a possible class of active attacks
8396 by an attacker who controls both an introduction point and a
8397 rendezvous point, and who uses the malleability of AES-CTR to
8398 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
8399 that these attacks are infeasible (requiring the attacker to send
8400 on the order of zettabytes of altered cells in a short interval),
8401 but we'd rather block them off in case there are any classes of
8402 this attack that we missed. Reported by Willem Pinckaers.
8405 - Adjust the expiration time on our SSL session certificates to
8406 better match SSL certs seen in the wild. Resolves ticket 4014.
8407 - Change the default required uptime for a relay to be accepted as
8408 a HSDir (hidden service directory) from 24 hours to 25 hours.
8409 Improves on 0.2.0.10-alpha; resolves ticket 2649.
8410 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
8411 authorities to abstain from voting on assignment of the HSDir
8412 consensus flag. Related to bug 2649.
8413 - Update to the September 6 2011 Maxmind GeoLite Country database.
8415 o Minor bugfixes (documentation and log messages):
8416 - Correct the man page to explain that HashedControlPassword and
8417 CookieAuthentication can both be set, in which case either method
8418 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
8419 when we decided to allow these config options to both be set. Issue
8421 - Demote the 'replay detected' log message emitted when a hidden
8422 service receives the same Diffie-Hellman public key in two different
8423 INTRODUCE2 cells to info level. A normal Tor client can cause that
8424 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
8425 fixes part of bug 2442.
8426 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
8427 level. There is nothing that a hidden service's operator can do
8428 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
8430 - Clarify a log message specifying the characters permitted in
8431 HiddenServiceAuthorizeClient client names. Previously, the log
8432 message said that "[A-Za-z0-9+-_]" were permitted; that could have
8433 given the impression that every ASCII character between "+" and "_"
8434 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
8437 - Provide a substitute implementation of lround() for MSVC, which
8438 apparently lacks it. Patch from Gisle Vanem.
8439 - Clean up some code issues that prevented Tor from building on older
8440 BSDs. Fixes bug 3894; reported by "grarpamp".
8441 - Search for a platform-specific version of "ar" when cross-compiling.
8442 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
8445 Changes in version 0.2.2.32 - 2011-08-27
8446 The Tor 0.2.2 release series is dedicated to the memory of Andreas
8447 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
8448 a founder of the PETS community, a leader in our field, a mentor,
8449 and a friend. He left us with these words: "I had the possibility
8450 to contribute to this world that is not as it should be. I hope I
8451 could help in some areas to make the world a better place, and that
8452 I could also encourage other people to be engaged in improving the
8453 world. Please, stay engaged. This world needs you, your love, your
8454 initiative -- now I cannot be part of that anymore."
8456 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
8457 ready. More than two years in the making, this release features improved
8458 client performance and hidden service reliability, better compatibility
8459 for Android, correct behavior for bridges that listen on more than
8460 one address, more extensible and flexible directory object handling,
8461 better reporting of network statistics, improved code security, and
8462 many many other features and bugfixes.
8464 o Major features (client performance):
8465 - When choosing which cells to relay first, relays now favor circuits
8466 that have been quiet recently, to provide lower latency for
8467 low-volume circuits. By default, relays enable or disable this
8468 feature based on a setting in the consensus. They can override
8469 this default by using the new "CircuitPriorityHalflife" config
8470 option. Design and code by Ian Goldberg, Can Tang, and Chris
8472 - Directory authorities now compute consensus weightings that instruct
8473 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
8474 and no flag. Clients use these weightings to distribute network load
8475 more evenly across these different relay types. The weightings are
8476 in the consensus so we can change them globally in the future. Extra
8477 thanks to "outofwords" for finding some nasty security bugs in
8478 the first implementation of this feature.
8480 o Major features (client performance, circuit build timeout):
8481 - Tor now tracks how long it takes to build client-side circuits
8482 over time, and adapts its timeout to local network performance.
8483 Since a circuit that takes a long time to build will also provide
8484 bad performance, we get significant latency improvements by
8485 discarding the slowest 20% of circuits. Specifically, Tor creates
8486 circuits more aggressively than usual until it has enough data
8487 points for a good timeout estimate. Implements proposal 151.
8488 - Circuit build timeout constants can be controlled by consensus
8489 parameters. We set good defaults for these parameters based on
8490 experimentation on broadband and simulated high-latency links.
8491 - Circuit build time learning can be disabled via consensus parameter
8492 or by the client via a LearnCircuitBuildTimeout config option. We
8493 also automatically disable circuit build time calculation if either
8494 AuthoritativeDirectory is set, or if we fail to write our state
8495 file. Implements ticket 1296.
8497 o Major features (relays use their capacity better):
8498 - Set SO_REUSEADDR socket option on all sockets, not just
8499 listeners. This should help busy exit nodes avoid running out of
8500 useable ports just because all the ports have been used in the
8501 near past. Resolves issue 2850.
8502 - Relays now save observed peak bandwidth throughput rates to their
8503 state file (along with total usage, which was already saved),
8504 so that they can determine their correct estimated bandwidth on
8505 restart. Resolves bug 1863, where Tor relays would reset their
8506 estimated bandwidth to 0 after restarting.
8507 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
8508 should give us approximately 40-50% more Guard-flagged nodes,
8509 improving the anonymity the Tor network can provide and also
8510 decreasing the dropoff in throughput that relays experience when
8511 they first get the Guard flag.
8512 - Directory authorities now take changes in router IP address and
8513 ORPort into account when determining router stability. Previously,
8514 if a router changed its IP or ORPort, the authorities would not
8515 treat it as having any downtime for the purposes of stability
8516 calculation, whereas clients would experience downtime since the
8517 change would take a while to propagate to them. Resolves issue 1035.
8518 - New AccelName and AccelDir options add support for dynamic OpenSSL
8519 hardware crypto acceleration engines.
8521 o Major features (relays control their load better):
8522 - Exit relays now try harder to block exit attempts from unknown
8523 relays, to make it harder for people to use them as one-hop proxies
8524 a la tortunnel. Controlled by the refuseunknownexits consensus
8525 parameter (currently enabled), or you can override it on your
8526 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
8527 based on a variant of proposal 163.
8528 - Add separate per-conn write limiting to go with the per-conn read
8529 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
8530 but never per-conn write limits.
8531 - New consensus params "bwconnrate" and "bwconnburst" to let us
8532 rate-limit client connections as they enter the network. It's
8533 controlled in the consensus so we can turn it on and off for
8534 experiments. It's starting out off. Based on proposal 163.
8536 o Major features (controllers):
8537 - Export GeoIP information on bridge usage to controllers even if we
8538 have not yet been running for 24 hours. Now Vidalia bridge operators
8539 can get more accurate and immediate feedback about their
8540 contributions to the network.
8541 - Add an __OwningControllerProcess configuration option and a
8542 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
8543 that when it exits, Tor will shut down. Implements feature 3049.
8545 o Major features (directory authorities):
8546 - Directory authorities now create, vote on, and serve multiple
8547 parallel formats of directory data as part of their voting process.
8548 Partially implements Proposal 162: "Publish the consensus in
8550 - Directory authorities now agree on and publish small summaries
8551 of router information that clients can use in place of regular
8552 server descriptors. This transition will allow Tor 0.2.3 clients
8553 to use far less bandwidth for downloading information about the
8554 network. Begins the implementation of Proposal 158: "Clients
8555 download consensus + microdescriptors".
8556 - The directory voting system is now extensible to use multiple hash
8557 algorithms for signatures and resource selection. Newer formats
8558 are signed with SHA256, with a possibility for moving to a better
8559 hash algorithm in the future.
8560 - Directory authorities can now vote on arbitary integer values as
8561 part of the consensus process. This is designed to help set
8562 network-wide parameters. Implements proposal 167.
8564 o Major features and bugfixes (node selection):
8565 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
8566 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
8567 options. Previously, we had been ambiguous in describing what
8568 counted as an "exit" node, and what operations exactly "StrictNodes
8569 0" would permit. This created confusion when people saw nodes built
8570 through unexpected circuits, and made it hard to tell real bugs from
8571 surprises. Now the intended behavior is:
8572 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
8573 a node that delivers user traffic outside the Tor network.
8574 . "Entry", in the context of EntryNodes, means a node used as the
8575 first hop of a multihop circuit. It doesn't include direct
8576 connections to directory servers.
8577 . "ExcludeNodes" applies to all nodes.
8578 . "StrictNodes" changes the behavior of ExcludeNodes only. When
8579 StrictNodes is set, Tor should avoid all nodes listed in
8580 ExcludeNodes, even when it will make user requests fail. When
8581 StrictNodes is *not* set, then Tor should follow ExcludeNodes
8582 whenever it can, except when it must use an excluded node to
8583 perform self-tests, connect to a hidden service, provide a
8584 hidden service, fulfill a .exit request, upload directory
8585 information, or fetch directory information.
8586 Collectively, the changes to implement the behavior fix bug 1090.
8587 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
8588 change during a config reload, mark and discard all our origin
8589 circuits. This fix should address edge cases where we change the
8590 config options and but then choose a circuit that we created before
8592 - Make EntryNodes config option much more aggressive even when
8593 StrictNodes is not set. Before it would prepend your requested
8594 entrynodes to your list of guard nodes, but feel free to use others
8595 after that. Now it chooses only from your EntryNodes if any of
8596 those are available, and only falls back to others if a) they're
8597 all down and b) StrictNodes is not set.
8598 - Now we refresh your entry guards from EntryNodes at each consensus
8599 fetch -- rather than just at startup and then they slowly rot as
8600 the network changes.
8601 - Add support for the country code "{??}" in torrc options like
8602 ExcludeNodes, to indicate all routers of unknown country. Closes
8604 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
8605 a node is listed in both, it's treated as excluded.
8606 - ExcludeNodes now applies to directory nodes -- as a preference if
8607 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
8608 Don't exclude all the directory authorities and set StrictNodes to 1
8609 unless you really want your Tor to break.
8610 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
8611 - ExcludeExitNodes now overrides .exit requests.
8612 - We don't use bridges listed in ExcludeNodes.
8613 - When StrictNodes is 1:
8614 . We now apply ExcludeNodes to hidden service introduction points
8615 and to rendezvous points selected by hidden service users. This
8616 can make your hidden service less reliable: use it with caution!
8617 . If we have used ExcludeNodes on ourself, do not try relay
8618 reachability self-tests.
8619 . If we have excluded all the directory authorities, we will not
8620 even try to upload our descriptor if we're a relay.
8621 . Do not honor .exit requests to an excluded node.
8622 - When the set of permitted nodes changes, we now remove any mappings
8623 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
8625 - We never cannibalize a circuit that had excluded nodes on it, even
8626 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
8627 - Improve log messages related to excluded nodes.
8629 o Major features (misc):
8630 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
8631 to help Tor build correctly for Android phones.
8632 - The options SocksPort, ControlPort, and so on now all accept a
8633 value "auto" that opens a socket on an OS-selected port. A
8634 new ControlPortWriteToFile option tells Tor to write its
8635 actual control port or ports to a chosen file. If the option
8636 ControlPortFileGroupReadable is set, the file is created as
8637 group-readable. Now users can run two Tor clients on the same
8638 system without needing to manually mess with parameters. Resolves
8639 part of ticket 3076.
8640 - Tor now supports tunneling all of its outgoing connections over
8641 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
8642 configuration options. Code by Christopher Davis.
8644 o Code security improvements:
8645 - Replace all potentially sensitive memory comparison operations
8646 with versions whose runtime does not depend on the data being
8647 compared. This will help resist a class of attacks where an
8648 adversary can use variations in timing information to learn
8649 sensitive data. Fix for one case of bug 3122. (Safe memcmp
8650 implementation by Robert Ransom based partially on code by DJB.)
8651 - Enable Address Space Layout Randomization (ASLR) and Data Execution
8652 Prevention (DEP) by default on Windows to make it harder for
8653 attackers to exploit vulnerabilities. Patch from John Brooks.
8654 - New "--enable-gcc-hardening" ./configure flag (off by default)
8655 to turn on gcc compile time hardening options. It ensures
8656 that signed ints have defined behavior (-fwrapv), enables
8657 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
8658 with canaries (-fstack-protector-all), turns on ASLR protection if
8659 supported by the kernel (-fPIE, -pie), and adds additional security
8660 related warnings. Verified to work on Mac OS X and Debian Lenny.
8661 - New "--enable-linker-hardening" ./configure flag (off by default)
8662 to turn on ELF specific hardening features (relro, now). This does
8663 not work with Mac OS X or any other non-ELF binary format.
8664 - Always search the Windows system directory for system DLLs, and
8665 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
8666 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
8667 current and future memory pages via mlockall(). On supported
8668 platforms (modern Linux and probably BSD but not Windows or OS X),
8669 this should effectively disable any and all attempts to page out
8670 memory. This option requires that you start your Tor as root --
8671 if you use DisableAllSwap, please consider using the User option
8672 to properly reduce the privileges of your Tor.
8674 o Major bugfixes (crashes):
8675 - Fix crash bug on platforms where gmtime and localtime can return
8676 NULL. Windows 7 users were running into this one. Fixes part of bug
8677 2077. Bugfix on all versions of Tor. Found by boboper.
8678 - Introduce minimum/maximum values that clients will believe
8679 from the consensus. Now we'll have a better chance to avoid crashes
8680 or worse when a consensus param has a weird value.
8681 - Fix a rare crash bug that could occur when a client was configured
8682 with a large number of bridges. Fixes bug 2629; bugfix on
8683 0.2.1.2-alpha. Bugfix by trac user "shitlei".
8684 - Do not crash when our configuration file becomes unreadable, for
8685 example due to a permissions change, between when we start up
8686 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
8688 - If we're in the pathological case where there's no exit bandwidth
8689 but there is non-exit bandwidth, or no guard bandwidth but there
8690 is non-guard bandwidth, don't crash during path selection. Bugfix
8692 - Fix a crash bug when trying to initialize the evdns module in
8693 Libevent 2. Bugfix on 0.2.1.16-rc.
8695 o Major bugfixes (stability):
8696 - Fix an assert in parsing router descriptors containing IPv6
8697 addresses. This one took down the directory authorities when
8698 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
8699 - Fix an uncommon assertion failure when running with DNSPort under
8700 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
8701 - Treat an unset $HOME like an empty $HOME rather than triggering an
8702 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
8703 - More gracefully handle corrupt state files, removing asserts
8704 in favor of saving a backup and resetting state.
8705 - Instead of giving an assertion failure on an internal mismatch
8706 on estimated freelist size, just log a BUG warning and try later.
8707 Mitigates but does not fix bug 1125.
8708 - Fix an assert that got triggered when using the TestingTorNetwork
8709 configuration option and then issuing a GETINFO config-text control
8710 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
8711 - If the cached cert file is unparseable, warn but don't exit.
8713 o Privacy fixes (relays/bridges):
8714 - Don't list Windows capabilities in relay descriptors. We never made
8715 use of them, and maybe it's a bad idea to publish them. Bugfix
8717 - If the Nickname configuration option isn't given, Tor would pick a
8718 nickname based on the local hostname as the nickname for a relay.
8719 Because nicknames are not very important in today's Tor and the
8720 "Unnamed" nickname has been implemented, this is now problematic
8721 behavior: It leaks information about the hostname without being
8722 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
8723 introduced the Unnamed nickname. Reported by tagnaq.
8724 - Maintain separate TLS contexts and certificates for incoming and
8725 outgoing connections in bridge relays. Previously we would use the
8726 same TLS contexts and certs for incoming and outgoing connections.
8727 Bugfix on 0.2.0.3-alpha; addresses bug 988.
8728 - Maintain separate identity keys for incoming and outgoing TLS
8729 contexts in bridge relays. Previously we would use the same
8730 identity keys for incoming and outgoing TLS contexts. Bugfix on
8731 0.2.0.3-alpha; addresses the other half of bug 988.
8732 - Make the bridge directory authority refuse to answer directory
8733 requests for "all descriptors". It used to include bridge
8734 descriptors in its answer, which was a major information leak.
8735 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
8737 o Privacy fixes (clients):
8738 - When receiving a hidden service descriptor, check that it is for
8739 the hidden service we wanted. Previously, Tor would store any
8740 hidden service descriptors that a directory gave it, whether it
8741 wanted them or not. This wouldn't have let an attacker impersonate
8742 a hidden service, but it did let directories pre-seed a client
8743 with descriptors that it didn't want. Bugfix on 0.0.6.
8744 - Start the process of disabling ".exit" address notation, since it
8745 can be used for a variety of esoteric application-level attacks
8746 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
8748 - Reject attempts at the client side to open connections to private
8749 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
8750 a randomly chosen exit node. Attempts to do so are always
8751 ill-defined, generally prevented by exit policies, and usually
8752 in error. This will also help to detect loops in transparent
8753 proxy configurations. You can disable this feature by setting
8754 "ClientRejectInternalAddresses 0" in your torrc.
8755 - Log a notice when we get a new control connection. Now it's easier
8756 for security-conscious users to recognize when a local application
8757 is knocking on their controller door. Suggested by bug 1196.
8759 o Privacy fixes (newnym):
8760 - Avoid linkability based on cached hidden service descriptors: forget
8761 all hidden service descriptors cached as a client when processing a
8762 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
8763 - On SIGHUP, do not clear out all TrackHostExits mappings, client
8764 DNS cache entries, and virtual address mappings: that's what
8765 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
8766 - Don't attach new streams to old rendezvous circuits after SIGNAL
8767 NEWNYM. Previously, we would keep using an existing rendezvous
8768 circuit if it remained open (i.e. if it were kept open by a
8769 long-lived stream, or if a new stream were attached to it before
8770 Tor could notice that it was old and no longer in use). Bugfix on
8771 0.1.1.15-rc; fixes bug 3375.
8773 o Major bugfixes (relay bandwidth accounting):
8774 - Fix a bug that could break accounting on 64-bit systems with large
8775 time_t values, making them hibernate for impossibly long intervals.
8776 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
8777 - Fix a bug in bandwidth accounting that could make us use twice
8778 the intended bandwidth when our interval start changes due to
8779 daylight saving time. Now we tolerate skew in stored vs computed
8780 interval starts: if the start of the period changes by no more than
8781 50% of the period's duration, we remember bytes that we transferred
8782 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
8784 o Major bugfixes (bridges):
8785 - Bridges now use "reject *:*" as their default exit policy. Bugfix
8786 on 0.2.0.3-alpha. Fixes bug 1113.
8787 - If you configure your bridge with a known identity fingerprint,
8788 and the bridge authority is unreachable (as it is in at least
8789 one country now), fall back to directly requesting the descriptor
8790 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
8792 - Fix a bug where bridge users who configure the non-canonical
8793 address of a bridge automatically switch to its canonical
8794 address. If a bridge listens at more than one address, it
8795 should be able to advertise those addresses independently and
8796 any non-blocked addresses should continue to work. Bugfix on Tor
8797 0.2.0.3-alpha. Fixes bug 2510.
8798 - If you configure Tor to use bridge A, and then quit and
8799 configure Tor to use bridge B instead (or if you change Tor
8800 to use bridge B via the controller), it would happily continue
8801 to use bridge A if it's still reachable. While this behavior is
8802 a feature if your goal is connectivity, in some scenarios it's a
8803 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
8804 - When the controller configures a new bridge, don't wait 10 to 60
8805 seconds before trying to fetch its descriptor. Bugfix on
8806 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
8808 o Major bugfixes (directory authorities):
8809 - Many relays have been falling out of the consensus lately because
8810 not enough authorities know about their descriptor for them to get
8811 a majority of votes. When we deprecated the v2 directory protocol,
8812 we got rid of the only way that v3 authorities can hear from each
8813 other about other descriptors. Now authorities examine every v3
8814 vote for new descriptors, and fetch them from that authority. Bugfix
8816 - Authorities could be tricked into giving out the Exit flag to relays
8817 that didn't allow exiting to any ports. This bug could screw
8818 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
8819 1238. Bug discovered by Martin Kowalczyk.
8820 - If all authorities restart at once right before a consensus vote,
8821 nobody will vote about "Running", and clients will get a consensus
8822 with no usable relays. Instead, authorities refuse to build a
8823 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
8825 o Major bugfixes (stream-level fairness):
8826 - When receiving a circuit-level SENDME for a blocked circuit, try
8827 to package cells fairly from all the streams that had previously
8828 been blocked on that circuit. Previously, we had started with the
8829 oldest stream, and allowed each stream to potentially exhaust
8830 the circuit's package window. This gave older streams on any
8831 given circuit priority over newer ones. Fixes bug 1937. Detected
8832 originally by Camilo Viecco. This bug was introduced before the
8833 first Tor release, in svn commit r152: it is the new winner of
8834 the longest-lived bug prize.
8835 - Fix a stream fairness bug that would cause newer streams on a given
8836 circuit to get preference when reading bytes from the origin or
8837 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
8838 introduced before the first Tor release, in svn revision r152.
8839 - When the exit relay got a circuit-level sendme cell, it started
8840 reading on the exit streams, even if had 500 cells queued in the
8841 circuit queue already, so the circuit queue just grew and grew in
8842 some cases. We fix this by not re-enabling reading on receipt of a
8843 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
8844 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
8846 - Newly created streams were allowed to read cells onto circuits,
8847 even if the circuit's cell queue was blocked and waiting to drain.
8848 This created potential unfairness, as older streams would be
8849 blocked, but newer streams would gladly fill the queue completely.
8850 We add code to detect this situation and prevent any stream from
8851 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
8854 o Major bugfixes (hidden services):
8855 - Apply circuit timeouts to opened hidden-service-related circuits
8856 based on the correct start time. Previously, we would apply the
8857 circuit build timeout based on time since the circuit's creation;
8858 it was supposed to be applied based on time since the circuit
8859 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
8860 - Improve hidden service robustness: When we find that we have
8861 extended a hidden service's introduction circuit to a relay not
8862 listed as an introduction point in the HS descriptor we currently
8863 have, retry with an introduction point from the current
8864 descriptor. Previously we would just give up. Fixes bugs 1024 and
8865 1930; bugfix on 0.2.0.10-alpha.
8866 - Directory authorities now use data collected from their own
8867 uptime observations when choosing whether to assign the HSDir flag
8868 to relays, instead of trusting the uptime value the relay reports in
8869 its descriptor. This change helps prevent an attack where a small
8870 set of nodes with frequently-changing identity keys can blackhole
8871 a hidden service. (Only authorities need upgrade; others will be
8872 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
8873 - Stop assigning the HSDir flag to relays that disable their
8874 DirPort (and thus will refuse to answer directory requests). This
8875 fix should dramatically improve the reachability of hidden services:
8876 hidden services and hidden service clients pick six HSDir relays
8877 to store and retrieve the hidden service descriptor, and currently
8878 about half of the HSDir relays will refuse to work. Bugfix on
8879 0.2.0.10-alpha; fixes part of bug 1693.
8881 o Major bugfixes (misc):
8882 - Clients now stop trying to use an exit node associated with a given
8883 destination by TrackHostExits if they fail to reach that exit node.
8884 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
8885 - Fix a regression that caused Tor to rebind its ports if it receives
8886 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
8887 - Remove an extra pair of quotation marks around the error
8888 message in control-port STATUS_GENERAL BUG events. Bugfix on
8889 0.1.2.6-alpha; fixes bug 3732.
8891 o Minor features (relays):
8892 - Ensure that no empty [dirreq-](read|write)-history lines are added
8893 to an extrainfo document. Implements ticket 2497.
8894 - When bandwidth accounting is enabled, be more generous with how
8895 much bandwidth we'll use up before entering "soft hibernation".
8896 Previously, we'd refuse new connections and circuits once we'd
8897 used up 95% of our allotment. Now, we use up 95% of our allotment,
8898 AND make sure that we have no more than 500MB (or 3 hours of
8899 expected traffic, whichever is lower) remaining before we enter
8901 - Relays now log the reason for publishing a new relay descriptor,
8902 so we have a better chance of hunting down instances of bug 1810.
8903 Resolves ticket 3252.
8904 - Log a little more clearly about the times at which we're no longer
8905 accepting new connections (e.g. due to hibernating). Resolves
8907 - When AllowSingleHopExits is set, print a warning to explain to the
8908 relay operator why most clients are avoiding her relay.
8909 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
8910 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
8911 clients are already deprecated because of security bugs.
8913 o Minor features (network statistics):
8914 - Directory mirrors that set "DirReqStatistics 1" write statistics
8915 about directory requests to disk every 24 hours. As compared to the
8916 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
8917 improvements: 1) stats are written to disk exactly every 24 hours;
8918 2) estimated shares of v2 and v3 requests are determined as mean
8919 values, not at the end of a measurement period; 3) unresolved
8920 requests are listed with country code '??'; 4) directories also
8921 measure download times.
8922 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
8923 number of exit streams and transferred bytes per port to disk every
8925 - Relays that set "CellStatistics 1" write statistics on how long
8926 cells spend in their circuit queues to disk every 24 hours.
8927 - Entry nodes that set "EntryStatistics 1" write statistics on the
8928 rough number and origins of connecting clients to disk every 24
8930 - Relays that write any of the above statistics to disk and set
8931 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
8932 their extra-info documents. Implements proposal 166.
8934 o Minor features (GeoIP and statistics):
8935 - Provide a log message stating which geoip file we're parsing
8936 instead of just stating that we're parsing the geoip file.
8937 Implements ticket 2432.
8938 - Make sure every relay writes a state file at least every 12 hours.
8939 Previously, a relay could go for weeks without writing its state
8940 file, and on a crash could lose its bandwidth history, capacity
8941 estimates, client country statistics, and so on. Addresses bug 3012.
8942 - Relays report the number of bytes spent on answering directory
8943 requests in extra-info descriptors similar to {read,write}-history.
8944 Implements enhancement 1790.
8945 - Report only the top 10 ports in exit-port stats in order not to
8946 exceed the maximum extra-info descriptor length of 50 KB. Implements
8948 - If writing the state file to disk fails, wait up to an hour before
8949 retrying again, rather than trying again each second. Fixes bug
8950 2346; bugfix on Tor 0.1.1.3-alpha.
8951 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
8952 when we switch from being a public relay to a bridge. Otherwise
8953 there will still be clients that see the relay in their consensus,
8954 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
8956 - Update to the August 2 2011 Maxmind GeoLite Country database.
8958 o Minor features (clients):
8959 - When expiring circuits, use microsecond timers rather than
8960 one-second timers. This can avoid an unpleasant situation where a
8961 circuit is launched near the end of one second and expired right
8962 near the beginning of the next, and prevent fluctuations in circuit
8964 - If we've configured EntryNodes and our network goes away and/or all
8965 our entrynodes get marked down, optimistically retry them all when
8966 a new socks application request appears. Fixes bug 1882.
8967 - Always perform router selections using weighted relay bandwidth,
8968 even if we don't need a high capacity circuit at the time. Non-fast
8969 circuits now only differ from fast ones in that they can use relays
8970 not marked with the Fast flag. This "feature" could turn out to
8971 be a horrible bug; we should investigate more before it goes into
8973 - When we run out of directory information such that we can't build
8974 circuits, but then get enough that we can build circuits, log when
8975 we actually construct a circuit, so the user has a better chance of
8976 knowing what's going on. Fixes bug 1362.
8977 - Log SSL state transitions at debug level during handshake, and
8978 include SSL states in error messages. This may help debug future
8979 SSL handshake issues.
8981 o Minor features (directory authorities):
8982 - When a router changes IP address or port, authorities now launch
8983 a new reachability test for it. Implements ticket 1899.
8984 - Directory authorities now reject relays running any versions of
8985 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
8986 known bugs that keep RELAY_EARLY cells from working on rendezvous
8987 circuits. Followup to fix for bug 2081.
8988 - Directory authorities now reject relays running any version of Tor
8989 older than 0.2.0.26-rc. That version is the earliest that fetches
8990 current directory information correctly. Fixes bug 2156.
8991 - Directory authorities now do an immediate reachability check as soon
8992 as they hear about a new relay. This change should slightly reduce
8993 the time between setting up a relay and getting listed as running
8994 in the consensus. It should also improve the time between setting
8995 up a bridge and seeing use by bridge users.
8996 - Directory authorities no longer launch a TLS connection to every
8997 relay as they startup. Now that we have 2k+ descriptors cached,
8998 the resulting network hiccup is becoming a burden. Besides,
8999 authorities already avoid voting about Running for the first half
9000 hour of their uptime.
9001 - Directory authorities now log the source of a rejected POSTed v3
9002 networkstatus vote, so we can track failures better.
9003 - Backport code from 0.2.3.x that allows directory authorities to
9004 clean their microdescriptor caches. Needed to resolve bug 2230.
9006 o Minor features (hidden services):
9007 - Use computed circuit-build timeouts to decide when to launch
9008 parallel introduction circuits for hidden services. (Previously,
9009 we would retry after 15 seconds.)
9010 - Don't allow v0 hidden service authorities to act as clients.
9011 Required by fix for bug 3000.
9012 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
9013 by fix for bug 3000.
9014 - Make hidden services work better in private Tor networks by not
9015 requiring any uptime to join the hidden service descriptor
9016 DHT. Implements ticket 2088.
9017 - Log (at info level) when purging pieces of hidden-service-client
9018 state because of SIGNAL NEWNYM.
9020 o Minor features (controller interface):
9021 - New "GETINFO net/listeners/(type)" controller command to return
9022 a list of addresses and ports that are bound for listeners for a
9023 given connection type. This is useful when the user has configured
9024 "SocksPort auto" and the controller needs to know which port got
9025 chosen. Resolves another part of ticket 3076.
9026 - Have the controller interface give a more useful message than
9027 "Internal Error" in response to failed GETINFO requests.
9028 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
9029 event, to give information on the current rate of circuit timeouts
9030 over our stored history.
9031 - The 'EXTENDCIRCUIT' control port command can now be used with
9032 a circ id of 0 and no path. This feature will cause Tor to build
9033 a new 'fast' general purpose circuit using its own path selection
9035 - Added a BUILDTIMEOUT_SET controller event to describe changes
9036 to the circuit build timeout.
9037 - New controller command "getinfo config-text". It returns the
9038 contents that Tor would write if you send it a SAVECONF command,
9039 so the controller can write the file to disk itself.
9041 o Minor features (controller protocol):
9042 - Add a new ControlSocketsGroupWritable configuration option: when
9043 it is turned on, ControlSockets are group-writeable by the default
9044 group of the current user. Patch by Jérémy Bobbio; implements
9046 - Tor now refuses to create a ControlSocket in a directory that is
9047 world-readable (or group-readable if ControlSocketsGroupWritable
9048 is 0). This is necessary because some operating systems do not
9049 enforce permissions on an AF_UNIX sockets. Permissions on the
9050 directory holding the socket, however, seems to work everywhere.
9051 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
9052 not. This would lead to a cookie that is still not group readable.
9053 Closes bug 1843. Suggested by katmagic.
9054 - Future-proof the controller protocol a bit by ignoring keyword
9055 arguments we do not recognize.
9057 o Minor features (more useful logging):
9058 - Revise most log messages that refer to nodes by nickname to
9059 instead use the "$key=nickname at address" format. This should be
9060 more useful, especially since nicknames are less and less likely
9061 to be unique. Resolves ticket 3045.
9062 - When an HTTPS proxy reports "403 Forbidden", we now explain
9063 what it means rather than calling it an unexpected status code.
9064 Closes bug 2503. Patch from Michael Yakubovich.
9065 - Rate-limit a warning about failures to download v2 networkstatus
9066 documents. Resolves part of bug 1352.
9067 - Rate-limit the "your application is giving Tor only an IP address"
9068 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
9069 - Rate-limit "Failed to hand off onionskin" warnings.
9070 - When logging a rate-limited warning, we now mention how many messages
9071 got suppressed since the last warning.
9072 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
9073 2 no signature, 4 required" messages about consensus signatures
9074 easier to read, and make sure they get logged at the same severity
9075 as the messages explaining which keys are which. Fixes bug 1290.
9076 - Don't warn when we have a consensus that we can't verify because
9077 of missing certificates, unless those certificates are ones
9078 that we have been trying and failing to download. Fixes bug 1145.
9080 o Minor features (log domains):
9081 - Add documentation for configuring logging at different severities in
9082 different log domains. We've had this feature since 0.2.1.1-alpha,
9083 but for some reason it never made it into the manpage. Fixes
9085 - Make it simpler to specify "All log domains except for A and B".
9086 Previously you needed to say "[*,~A,~B]". Now you can just say
9088 - Add a "LogMessageDomains 1" option to include the domains of log
9089 messages along with the messages. Without this, there's no way
9090 to use log domains without reading the source or doing a lot
9092 - Add a new "Handshake" log domain for activities that happen
9093 during the TLS handshake.
9095 o Minor features (build process):
9096 - Make compilation with clang possible when using
9097 "--enable-gcc-warnings" by removing two warning options that clang
9098 hasn't implemented yet and by fixing a few warnings. Resolves
9100 - Detect platforms that brokenly use a signed size_t, and refuse to
9101 build there. Found and analyzed by doorss and rransom.
9102 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
9104 - Add support for statically linking zlib by specifying
9105 "--enable-static-zlib", to go with our support for statically
9106 linking openssl and libevent. Resolves bug 1358.
9107 - Instead of adding the svn revision to the Tor version string, report
9108 the git commit (when we're building from a git checkout).
9109 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
9111 - New --digests command-line switch to output the digests of the
9112 source files Tor was built with.
9113 - Generate our manpage and HTML documentation using Asciidoc. This
9114 change should make it easier to maintain the documentation, and
9115 produce nicer HTML. The build process fails if asciidoc cannot
9116 be found and building with asciidoc isn't disabled (via the
9117 "--disable-asciidoc" argument to ./configure. Skipping the manpage
9118 speeds up the build considerably.
9120 o Minor features (options / torrc):
9121 - Warn when the same option is provided more than once in a torrc
9122 file, on the command line, or in a single SETCONF statement, and
9123 the option is one that only accepts a single line. Closes bug 1384.
9124 - Warn when the user configures two HiddenServiceDir lines that point
9125 to the same directory. Bugfix on 0.0.6 (the version introducing
9126 HiddenServiceDir); fixes bug 3289.
9127 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
9128 do individual connection-level rate limiting of clients. The torrc
9129 config options with the same names trump the consensus params, if
9130 both are present. Replaces the old "bwconnrate" and "bwconnburst"
9131 consensus params which were broken from 0.2.2.7-alpha through
9132 0.2.2.14-alpha. Closes bug 1947.
9133 - New config option "WarnUnsafeSocks 0" disables the warning that
9134 occurs whenever Tor receives a socks handshake using a version of
9135 the socks protocol that can only provide an IP address (rather
9136 than a hostname). Setups that do DNS locally over Tor are fine,
9137 and we shouldn't spam the logs in that case.
9138 - New config option "CircuitStreamTimeout" to override our internal
9139 timeout schedule for how many seconds until we detach a stream from
9140 a circuit and try a new circuit. If your network is particularly
9141 slow, you might want to set this to a number like 60.
9142 - New options for SafeLogging to allow scrubbing only log messages
9143 generated while acting as a relay. Specify "SafeLogging relay" if
9144 you want to ensure that only messages known to originate from
9145 client use of the Tor process will be logged unsafely.
9146 - Time and memory units in the configuration file can now be set to
9147 fractional units. For example, "2.5 GB" is now a valid value for
9149 - Support line continuations in the torrc config file. If a line
9150 ends with a single backslash character, the newline is ignored, and
9151 the configuration value is treated as continuing on the next line.
9154 o Minor features (unit tests):
9155 - Revise our unit tests to use the "tinytest" framework, so we
9156 can run tests in their own processes, have smarter setup/teardown
9157 code, and so on. The unit test code has moved to its own
9158 subdirectory, and has been split into multiple modules.
9159 - Add a unit test for cross-platform directory-listing code.
9160 - Add some forgotten return value checks during unit tests. Found
9162 - Use GetTempDir to find the proper temporary directory location on
9163 Windows when generating temporary files for the unit tests. Patch
9166 o Minor features (misc):
9167 - The "torify" script now uses torsocks where available.
9168 - Make Libevent log messages get delivered to controllers later,
9169 and not from inside the Libevent log handler. This prevents unsafe
9170 reentrant Libevent calls while still letting the log messages
9172 - Certain Tor clients (such as those behind check.torproject.org) may
9173 want to fetch the consensus in an extra early manner. To enable this
9174 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
9175 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
9176 as only certain clients who must have this information sooner should
9178 - Expand homedirs passed to tor-checkkey. This should silence a
9179 coverity complaint about passing a user-supplied string into
9180 open() without checking it.
9181 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
9182 used on bridges, and it makes bridge scanning somewhat easier.
9183 - Create the /var/run/tor directory on startup on OpenSUSE if it is
9184 not already created. Patch from Andreas Stieger. Fixes bug 2573.
9186 o Minor bugfixes (relays):
9187 - When a relay decides that its DNS is too broken for it to serve
9188 as an exit server, it advertised itself as a non-exit, but
9189 continued to act as an exit. This could create accidental
9190 partitioning opportunities for users. Instead, if a relay is
9191 going to advertise reject *:* as its exit policy, it should
9192 really act with exit policy "reject *:*". Fixes bug 2366.
9193 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
9194 - Publish a router descriptor even if generating an extra-info
9195 descriptor fails. Previously we would not publish a router
9196 descriptor without an extra-info descriptor; this can cause fast
9197 exit relays collecting exit-port statistics to drop from the
9198 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
9199 - When we're trying to guess whether we know our IP address as
9200 a relay, we would log various ways that we failed to guess
9201 our address, but never log that we ended up guessing it
9202 successfully. Now add a log line to help confused and anxious
9203 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
9204 - For bandwidth accounting, calculate our expected bandwidth rate
9205 based on the time during which we were active and not in
9206 soft-hibernation during the last interval. Previously, we were
9207 also considering the time spent in soft-hibernation. If this
9208 was a long time, we would wind up underestimating our bandwidth
9209 by a lot, and skewing our wakeup time towards the start of the
9210 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
9211 - Demote a confusing TLS warning that relay operators might get when
9212 someone tries to talk to their ORPort. It is not the operator's
9213 fault, nor can they do anything about it. Fixes bug 1364; bugfix
9215 - Change "Application request when we're believed to be offline."
9216 notice to "Application request when we haven't used client
9217 functionality lately.", to clarify that it's not an error. Bugfix
9218 on 0.0.9.3; fixes bug 1222.
9220 o Minor bugfixes (bridges):
9221 - When a client starts or stops using bridges, never use a circuit
9222 that was built before the configuration change. This behavior could
9223 put at risk a user who uses bridges to ensure that her traffic
9224 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
9226 - Do not reset the bridge descriptor download status every time we
9227 re-parse our configuration or get a configuration change. Fixes
9228 bug 3019; bugfix on 0.2.0.3-alpha.
9229 - Users couldn't configure a regular relay to be their bridge. It
9230 didn't work because when Tor fetched the bridge descriptor, it found
9231 that it already had it, and didn't realize that the purpose of the
9232 descriptor had changed. Now we replace routers with a purpose other
9233 than bridge with bridge descriptors when fetching them. Bugfix on
9234 0.1.1.9-alpha. Fixes bug 1776.
9235 - In the special case where you configure a public exit relay as your
9236 bridge, Tor would be willing to use that exit relay as the last
9237 hop in your circuit as well. Now we fail that circuit instead.
9238 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
9240 o Minor bugfixes (clients):
9241 - We now ask the other side of a stream (the client or the exit)
9242 for more data on that stream when the amount of queued data on
9243 that stream dips low enough. Previously, we wouldn't ask the
9244 other side for more data until either it sent us more data (which
9245 it wasn't supposed to do if it had exhausted its window!) or we
9246 had completely flushed all our queued data. This flow control fix
9247 should improve throughput. Fixes bug 2756; bugfix on the earliest
9248 released versions of Tor (svn commit r152).
9249 - When a client finds that an origin circuit has run out of 16-bit
9250 stream IDs, we now mark it as unusable for new streams. Previously,
9251 we would try to close the entire circuit. Bugfix on 0.0.6.
9252 - Make it explicit that we don't cannibalize one-hop circuits. This
9253 happens in the wild, but doesn't turn out to be a problem because
9254 we fortunately don't use those circuits. Many thanks to outofwords
9255 for the initial analysis and to swissknife who confirmed that
9256 two-hop circuits are actually created.
9257 - Resolve an edge case in path weighting that could make us misweight
9258 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
9259 - Make the DNSPort option work with libevent 2.x. Don't alter the
9260 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
9262 o Minor bugfixes (directory authorities):
9263 - Make directory authorities more accurate at recording when
9264 relays that have failed several reachability tests became
9265 unreachable, so we can provide more accuracy at assigning Stable,
9266 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
9267 - Directory authorities are now more robust to hops back in time
9268 when calculating router stability. Previously, if a run of uptime
9269 or downtime appeared to be negative, the calculation could give
9270 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
9272 - Directory authorities will now attempt to download consensuses
9273 if their own efforts to make a live consensus have failed. This
9274 change means authorities that restart will fetch a valid
9275 consensus, and it means authorities that didn't agree with the
9276 current consensus will still fetch and serve it if it has enough
9277 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
9278 - Never vote for a server as "Running" if we have a descriptor for
9279 it claiming to be hibernating, and that descriptor was published
9280 more recently than our last contact with the server. Bugfix on
9281 0.2.0.3-alpha; fixes bug 911.
9282 - Directory authorities no longer change their opinion of, or vote on,
9283 whether a router is Running, unless they have themselves been
9284 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
9287 o Minor bugfixes (hidden services):
9288 - Log malformed requests for rendezvous descriptors as protocol
9289 warnings, not warnings. Also, use a more informative log message
9290 in case someone sees it at log level warning without prior
9291 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
9292 - Accept hidden service descriptors if we think we might be a hidden
9293 service directory, regardless of what our consensus says. This
9294 helps robustness, since clients and hidden services can sometimes
9295 have a more up-to-date view of the network consensus than we do,
9296 and if they think that the directory authorities list us a HSDir,
9297 we might actually be one. Related to bug 2732; bugfix on
9299 - Correct the warning displayed when a rendezvous descriptor exceeds
9300 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
9302 - Clients and hidden services now use HSDir-flagged relays for hidden
9303 service descriptor downloads and uploads even if the relays have no
9304 DirPort set and the client has disabled TunnelDirConns. This will
9305 eventually allow us to give the HSDir flag to relays with no
9306 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
9307 - Only limit the lengths of single HS descriptors, even when multiple
9308 HS descriptors are published to an HSDir relay in a single POST
9309 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
9311 o Minor bugfixes (controllers):
9312 - Allow GETINFO fingerprint to return a fingerprint even when
9313 we have not yet built a router descriptor. Fixes bug 3577;
9314 bugfix on 0.2.0.1-alpha.
9315 - Send a SUCCEEDED stream event to the controller when a reverse
9316 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
9317 discovered by katmagic.
9318 - Remove a trailing asterisk from "exit-policy/default" in the
9319 output of the control port command "GETINFO info/names". Bugfix
9321 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
9322 2917. Bugfix on 0.1.1.1-alpha.
9323 - When we restart our relay, we might get a successful connection
9324 from the outside before we've started our reachability tests,
9325 triggering a warning: "ORPort found reachable, but I have no
9326 routerinfo yet. Failing to inform controller of success." This
9327 bug was harmless unless Tor is running under a controller
9328 like Vidalia, in which case the controller would never get a
9329 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
9331 - When a controller changes TrackHostExits, remove mappings for
9332 hosts that should no longer have their exits tracked. Bugfix on
9334 - When a controller changes VirtualAddrNetwork, remove any mappings
9335 for hosts that were automapped to the old network. Bugfix on
9337 - When a controller changes one of the AutomapHosts* options, remove
9338 any mappings for hosts that should no longer be automapped. Bugfix
9340 - Fix an off-by-one error in calculating some controller command
9341 argument lengths. Fortunately, this mistake is harmless since
9342 the controller code does redundant NUL termination too. Found by
9343 boboper. Bugfix on 0.1.1.1-alpha.
9344 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
9345 would return "551 Internal error" rather than "552 Unrecognized key
9346 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
9347 - Don't spam the controller with events when we have no file
9348 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
9349 for log messages was already solved from bug 748.)
9350 - Emit a GUARD DROPPED controller event for a case we missed.
9351 - Ensure DNS requests launched by "RESOLVE" commands from the
9352 controller respect the __LeaveStreamsUnattached setconf options. The
9353 same goes for requests launched via DNSPort or transparent
9354 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
9356 o Minor bugfixes (config options):
9357 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
9358 Change the limit to 512 characters by removing base64 newlines.
9359 Fixes bug 2752. Fix by Michael Yakubovich.
9360 - Complain if PublishServerDescriptor is given multiple arguments that
9361 include 0 or 1. This configuration will be rejected in the future.
9362 Bugfix on 0.2.0.1-alpha; closes bug 1107.
9363 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
9364 Bugfix on 0.2.0.13-alpha; closes bug 928.
9366 o Minor bugfixes (log subsystem fixes):
9367 - When unable to format an address as a string, report its value
9368 as "???" rather than reusing the last formatted address. Bugfix
9370 - Be more consistent in our treatment of file system paths. "~" should
9371 get expanded to the user's home directory in the Log config option.
9372 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
9373 feature for the -f and --DataDirectory options.
9375 o Minor bugfixes (memory management):
9376 - Don't stack-allocate the list of supplementary GIDs when we're
9377 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
9378 could take up to 256K, which is way too much stack. Found by
9379 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
9380 - Save a couple bytes in memory allocation every time we escape
9381 certain characters in a string. Patch from Florian Zumbiehl.
9383 o Minor bugfixes (protocol correctness):
9384 - When checking for 1024-bit keys, check for 1024 bits, not 128
9385 bytes. This allows Tor to correctly discard keys of length 1017
9386 through 1023. Bugfix on 0.0.9pre5.
9387 - Require that introduction point keys and onion handshake keys
9388 have a public exponent of 65537. Starts to fix bug 3207; bugfix
9390 - Handle SOCKS messages longer than 128 bytes long correctly, rather
9391 than waiting forever for them to finish. Fixes bug 2330; bugfix
9392 on 0.2.0.16-alpha. Found by doorss.
9393 - Never relay a cell for a circuit we have already destroyed.
9394 Between marking a circuit as closeable and finally closing it,
9395 it may have been possible for a few queued cells to get relayed,
9396 even though they would have been immediately dropped by the next
9397 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
9398 - Never queue a cell for a circuit that's already been marked
9400 - Fix a spec conformance issue: the network-status-version token
9401 must be the first token in a v3 consensus or vote. Discovered by
9402 "parakeep". Bugfix on 0.2.0.3-alpha.
9403 - A networkstatus vote must contain exactly one signature. Spec
9404 conformance issue. Bugfix on 0.2.0.3-alpha.
9405 - When asked about a DNS record type we don't support via a
9406 client DNSPort, reply with NOTIMPL rather than an empty
9407 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
9408 - Make more fields in the controller protocol case-insensitive, since
9409 control-spec.txt said they were.
9411 o Minor bugfixes (log messages):
9412 - Fix a log message that said "bits" while displaying a value in
9413 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
9415 - Downgrade "no current certificates known for authority" message from
9416 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
9417 - Correctly describe errors that occur when generating a TLS object.
9418 Previously we would attribute them to a failure while generating a
9419 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
9421 - Fix an instance where a Tor directory mirror might accidentally
9422 log the IP address of a misbehaving Tor client. Bugfix on
9424 - Stop logging at severity 'warn' when some other Tor client tries
9425 to establish a circuit with us using weak DH keys. It's a protocol
9426 violation, but that doesn't mean ordinary users need to hear about
9427 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
9428 - If your relay can't keep up with the number of incoming create
9429 cells, it would log one warning per failure into your logs. Limit
9430 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
9432 o Minor bugfixes (build fixes):
9433 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
9434 - When warning about missing zlib development packages during compile,
9435 give the correct package names. Bugfix on 0.2.0.1-alpha.
9436 - Fix warnings that newer versions of autoconf produce during
9437 ./autogen.sh. These warnings appear to be harmless in our case,
9438 but they were extremely verbose. Fixes bug 2020.
9439 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
9442 o Minor bugfixes (portability):
9443 - Write several files in text mode, on OSes that distinguish text
9444 mode from binary mode (namely, Windows). These files are:
9445 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
9446 that collect those statistics; 'client_keys' and 'hostname' for
9447 hidden services that use authentication; and (in the tor-gencert
9448 utility) newly generated identity and signing keys. Previously,
9449 we wouldn't specify text mode or binary mode, leading to an
9450 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
9451 the DirRecordUsageByCountry option which would have triggered
9452 the assertion failure was added), although this assertion failure
9453 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
9454 - Selectively disable deprecation warnings on OS X because Lion
9455 started deprecating the shipped copy of openssl. Fixes bug 3643.
9456 - Use a wide type to hold sockets when built for 64-bit Windows.
9458 - Fix an issue that prevented static linking of libevent on
9459 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
9460 where we introduced the "--with-static-libevent" configure option.
9461 - Fix a bug with our locking implementation on Windows that couldn't
9462 correctly detect when a file was already locked. Fixes bug 2504,
9463 bugfix on 0.2.1.6-alpha.
9464 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
9466 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
9467 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
9470 o Minor bugfixes (code correctness):
9471 - Always NUL-terminate the sun_path field of a sockaddr_un before
9472 passing it to the kernel. (Not a security issue: kernels are
9473 smart enough to reject bad sockaddr_uns.) Found by Coverity;
9474 CID #428. Bugfix on Tor 0.2.0.3-alpha.
9475 - Make connection_printf_to_buf()'s behavior sane. Its callers
9476 expect it to emit a CRLF iff the format string ends with CRLF;
9477 it actually emitted a CRLF iff (a) the format string ended with
9478 CRLF or (b) the resulting string was over 1023 characters long or
9479 (c) the format string did not end with CRLF *and* the resulting
9480 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
9481 fixes part of bug 3407.
9482 - Make send_control_event_impl()'s behavior sane. Its callers
9483 expect it to always emit a CRLF at the end of the string; it
9484 might have emitted extra control characters as well. Bugfix on
9485 0.1.1.9-alpha; fixes another part of bug 3407.
9486 - Make crypto_rand_int() check the value of its input correctly.
9487 Previously, it accepted values up to UINT_MAX, but could return a
9488 negative number if given a value above INT_MAX+1. Found by George
9489 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
9490 - Fix a potential null-pointer dereference while computing a
9491 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
9493 - If we fail to compute the identity digest of a v3 legacy keypair,
9494 warn, and don't use a buffer-full of junk instead. Bugfix on
9495 0.2.1.1-alpha; fixes bug 3106.
9496 - Resolve an untriggerable issue in smartlist_string_num_isin(),
9497 where if the function had ever in the future been used to check
9498 for the presence of a too-large number, it would have given an
9499 incorrect result. (Fortunately, we only used it for 16-bit
9500 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
9501 - Be more careful about reporting the correct error from a failed
9502 connect() system call. Under some circumstances, it was possible to
9503 look at an incorrect value for errno when sending the end reason.
9504 Bugfix on 0.1.0.1-rc.
9505 - Correctly handle an "impossible" overflow cases in connection byte
9506 counting, where we write or read more than 4GB on an edge connection
9507 in a single second. Bugfix on 0.1.2.8-beta.
9508 - Avoid a double mark-for-free warning when failing to attach a
9509 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
9511 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
9512 found by "cypherpunks". This bug was introduced before the first
9513 Tor release, in svn commit r110.
9514 - Fix a bug in bandwidth history state parsing that could have been
9515 triggered if a future version of Tor ever changed the timing
9516 granularity at which bandwidth history is measured. Bugfix on
9518 - Add assertions to check for overflow in arguments to
9519 base32_encode() and base32_decode(); fix a signed-unsigned
9520 comparison there too. These bugs are not actually reachable in Tor,
9521 but it's good to prevent future errors too. Found by doorss.
9522 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
9524 - Set target port in get_interface_address6() correctly. Bugfix
9525 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
9526 - Fix an impossible-to-actually-trigger buffer overflow in relay
9527 descriptor generation. Bugfix on 0.1.0.15.
9528 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
9530 o Minor bugfixes (code improvements):
9531 - After we free an internal connection structure, overwrite it
9532 with a different memory value than we use for overwriting a freed
9533 internal circuit structure. Should help with debugging. Suggested
9535 - If OpenSSL fails to make a duplicate of a private or public key, log
9536 an error message and try to exit cleanly. May help with debugging
9537 if bug 1209 ever remanifests.
9538 - Some options used different conventions for uppercasing of acronyms
9539 when comparing manpage and source. Fix those in favor of the
9540 manpage, as it makes sense to capitalize acronyms.
9541 - Take a first step towards making or.h smaller by splitting out
9542 function definitions for all source files in src/or/. Leave
9543 structures and defines in or.h for now.
9544 - Remove a few dead assignments during router parsing. Found by
9546 - Don't use 1-bit wide signed bit fields. Found by coverity.
9547 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
9548 None of the cases where we did this before were wrong, but by making
9549 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
9550 - The memarea code now uses a sentinel value at the end of each area
9551 to make sure nothing writes beyond the end of an area. This might
9552 help debug some conceivable causes of bug 930.
9553 - Always treat failure to allocate an RSA key as an unrecoverable
9555 - Add some more defensive programming for architectures that can't
9556 handle unaligned integer accesses. We don't know of any actual bugs
9557 right now, but that's the best time to fix them. Fixes bug 1943.
9559 o Minor bugfixes (misc):
9560 - Fix a rare bug in rend_fn unit tests: we would fail a test when
9561 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
9562 on 0.2.0.10-alpha; fixes bug 1808.
9563 - Where available, use Libevent 2.0's periodic timers so that our
9564 once-per-second cleanup code gets called even more closely to
9565 once per second than it would otherwise. Fixes bug 943.
9566 - Ignore OutboundBindAddress when connecting to localhost.
9567 Connections to localhost need to come _from_ localhost, or else
9568 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
9570 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
9572 - If any of the v3 certs we download are unparseable, we should
9573 actually notice the failure so we don't retry indefinitely. Bugfix
9574 on 0.2.0.x; reported by "rotator".
9575 - When Tor fails to parse a descriptor of any kind, dump it to disk.
9576 Might help diagnosing bug 1051.
9577 - Make our 'torify' script more portable; if we have only one of
9578 'torsocks' or 'tsocks' installed, don't complain to the user;
9579 and explain our warning about tsocks better.
9580 - Fix some urls in the exit notice file and make it XHTML1.1 strict
9581 compliant. Based on a patch from Christian Kujau.
9583 o Documentation changes:
9584 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
9585 - Resolve all doxygen warnings except those for missing documentation.
9587 - Add doxygen documentation for more functions, fields, and types.
9588 - Convert the HACKING file to asciidoc, and add a few new sections
9589 to it, explaining how we use Git, how we make changelogs, and
9590 what should go in a patch.
9591 - Document the default socks host and port (127.0.0.1:9050) for
9593 - Removed some unnecessary files from the source distribution. The
9594 AUTHORS file has now been merged into the people page on the
9595 website. The roadmaps and design doc can now be found in the
9596 projects directory in svn.
9598 o Deprecated and removed features (config):
9599 - Remove the torrc.complete file. It hasn't been kept up to date
9600 and users will have better luck checking out the manpage.
9601 - Remove the HSAuthorityRecordStats option that version 0 hidden
9602 service authorities could use to track statistics of overall v0
9603 hidden service usage.
9604 - Remove the obsolete "NoPublish" option; it has been flagged
9605 as obsolete and has produced a warning since 0.1.1.18-rc.
9606 - Caches no longer download and serve v2 networkstatus documents
9607 unless FetchV2Networkstatus flag is set: these documents haven't
9608 haven't been used by clients or relays since 0.2.0.x. Resolves
9611 o Deprecated and removed features (controller):
9612 - The controller no longer accepts the old obsolete "addr-mappings/"
9613 or "unregistered-servers-" GETINFO values.
9614 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
9615 always on; using them is necessary for correct forward-compatible
9618 o Deprecated and removed features (misc):
9619 - Hidden services no longer publish version 0 descriptors, and clients
9620 do not request or use version 0 descriptors. However, the old hidden
9621 service authorities still accept and serve version 0 descriptors
9622 when contacted by older hidden services/clients.
9623 - Remove undocumented option "-F" from tor-resolve: it hasn't done
9624 anything since 0.2.1.16-rc.
9625 - Remove everything related to building the expert bundle for OS X.
9626 It has confused many users, doesn't work right on OS X 10.6,
9627 and is hard to get rid of once installed. Resolves bug 1274.
9628 - Remove support for .noconnect style addresses. Nobody was using
9629 them, and they provided another avenue for detecting Tor users
9630 via application-level web tricks.
9631 - When we fixed bug 1038 we had to put in a restriction not to send
9632 RELAY_EARLY cells on rend circuits. This was necessary as long
9633 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
9634 active. Now remove this obsolete check. Resolves bug 2081.
9635 - Remove workaround code to handle directory responses from servers
9636 that had bug 539 (they would send HTTP status 503 responses _and_
9637 send a body too). Since only server versions before
9638 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
9639 keep the workaround in place.
9640 - Remove the old 'fuzzy time' logic. It was supposed to be used for
9641 handling calculations where we have a known amount of clock skew and
9642 an allowed amount of unknown skew. But we only used it in three
9643 places, and we never adjusted the known/unknown skew values. This is
9644 still something we might want to do someday, but if we do, we'll
9645 want to do it differently.
9646 - Remove the "--enable-iphone" option to ./configure. According to
9647 reports from Marco Bonetti, Tor builds fine without any special
9648 tweaking on recent iPhone SDK versions.
9651 Changes in version 0.2.1.30 - 2011-02-23
9652 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
9653 change is a slight tweak to Tor's TLS handshake that makes relays
9654 and bridges that run this new version reachable from Iran again.
9655 We don't expect this tweak will win the arms race long-term, but it
9656 buys us time until we roll out a better solution.
9659 - Stop sending a CLOCK_SKEW controller status event whenever
9660 we fetch directory information from a relay that has a wrong clock.
9661 Instead, only inform the controller when it's a trusted authority
9662 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
9663 the rest of bug 1074.
9664 - Fix a bounds-checking error that could allow an attacker to
9665 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
9667 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
9668 Tor would ignore their RelayBandwidthBurst setting,
9669 potentially using more bandwidth than expected. Bugfix on
9670 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
9671 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
9672 hidserv" in her torrc. The 'hidserv' argument never controlled
9673 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
9676 - Adjust our TLS Diffie-Hellman parameters to match those used by
9678 - Update to the February 1 2011 Maxmind GeoLite Country database.
9681 - Check for and reject overly long directory certificates and
9682 directory tokens before they have a chance to hit any assertions.
9683 Bugfix on 0.2.1.28. Found by "doorss".
9684 - Bring the logic that gathers routerinfos and assesses the
9685 acceptability of circuits into line. This prevents a Tor OP from
9686 getting locked in a cycle of choosing its local OR as an exit for a
9687 path (due to a .exit request) and then rejecting the circuit because
9688 its OR is not listed yet. It also prevents Tor clients from using an
9689 OR running in the same instance as an exit (due to a .exit request)
9690 if the OR does not meet the same requirements expected of an OR
9691 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
9693 o Packaging changes:
9694 - Stop shipping the Tor specs files and development proposal documents
9695 in the tarball. They are now in a separate git repository at
9696 git://git.torproject.org/torspec.git
9697 - Do not include Git version tags as though they are SVN tags when
9698 generating a tarball from inside a repository that has switched
9699 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
9702 Changes in version 0.2.1.29 - 2011-01-15
9703 Tor 0.2.1.29 continues our recent code security audit work. The main
9704 fix resolves a remote heap overflow vulnerability that can allow remote
9705 code execution. Other fixes address a variety of assert and crash bugs,
9706 most of which we think are hard to exploit remotely.
9708 o Major bugfixes (security):
9709 - Fix a heap overflow bug where an adversary could cause heap
9710 corruption. This bug probably allows remote code execution
9711 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
9713 - Prevent a denial-of-service attack by disallowing any
9714 zlib-compressed data whose compression factor is implausibly
9715 high. Fixes part of bug 2324; reported by "doorss".
9716 - Zero out a few more keys in memory before freeing them. Fixes
9717 bug 2384 and part of bug 2385. These key instances found by
9718 "cypherpunks", based on Andrew Case's report about being able
9719 to find sensitive data in Tor's memory space if you have enough
9720 permissions. Bugfix on 0.0.2pre9.
9722 o Major bugfixes (crashes):
9723 - Prevent calls to Libevent from inside Libevent log handlers.
9724 This had potential to cause a nasty set of crashes, especially
9725 if running Libevent with debug logging enabled, and running
9726 Tor with a controller watching for low-severity log messages.
9727 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
9728 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
9729 underflow errors there too. Fixes the other part of bug 2324.
9730 - Fix a bug where we would assert if we ever had a
9731 cached-descriptors.new file (or another file read directly into
9732 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
9733 on 0.2.1.25. Found by doorss.
9734 - Fix some potential asserts and parsing issues with grossly
9735 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
9738 o Minor bugfixes (other):
9739 - Fix a bug with handling misformed replies to reverse DNS lookup
9740 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
9741 bug reported by doorss.
9742 - Fix compilation on mingw when a pthreads compatibility library
9743 has been installed. (We don't want to use it, so we shouldn't
9744 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
9745 - Fix a bug where we would declare that we had run out of virtual
9746 addresses when the address space was only half-exhausted. Bugfix
9748 - Correctly handle the case where AutomapHostsOnResolve is set but
9749 no virtual addresses are available. Fixes bug 2328; bugfix on
9750 0.1.2.1-alpha. Bug found by doorss.
9751 - Correctly handle wrapping around when we run out of virtual
9752 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
9755 - Update to the January 1 2011 Maxmind GeoLite Country database.
9756 - Introduce output size checks on all of our decryption functions.
9759 - Tor does not build packages correctly with Automake 1.6 and earlier;
9760 added a check to Makefile.am to make sure that we're building with
9761 Automake 1.7 or later.
9762 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
9763 because we built it with a too-old version of automake. Thus that
9764 release broke ./configure --enable-openbsd-malloc, which is popular
9765 among really fast exit relays on Linux.
9768 Changes in version 0.2.1.28 - 2010-12-17
9769 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
9770 exploitable bugs. We also took this opportunity to change the IP address
9771 for one of our directory authorities, and to update the geoip database
9775 - Fix a remotely exploitable bug that could be used to crash instances
9776 of Tor remotely by overflowing on the heap. Remote-code execution
9777 hasn't been confirmed, but can't be ruled out. Everyone should
9778 upgrade. Bugfix on the 0.1.1 series and later.
9780 o Directory authority changes:
9781 - Change IP address and ports for gabelmoo (v3 directory authority).
9784 - Update to the December 1 2010 Maxmind GeoLite Country database.
9787 Changes in version 0.2.1.27 - 2010-11-23
9788 Yet another OpenSSL security patch broke its compatibility with Tor:
9789 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
9790 also took this opportunity to fix several crash bugs, integrate a new
9791 directory authority, and update the bundled GeoIP database.
9794 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
9795 No longer set the tlsext_host_name extension on server SSL objects;
9796 but continue to set it on client SSL objects. Our goal in setting
9797 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
9798 bugfix on 0.2.1.1-alpha.
9799 - Do not log messages to the controller while shrinking buffer
9800 freelists. Doing so would sometimes make the controller connection
9801 try to allocate a buffer chunk, which would mess up the internals
9802 of the freelist and cause an assertion failure. Fixes bug 1125;
9803 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
9804 - Learn our external IP address when we're a relay or bridge, even if
9805 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
9806 where we introduced bridge relays that don't need to publish to
9807 be useful. Fixes bug 2050.
9808 - Do even more to reject (and not just ignore) annotations on
9809 router descriptors received anywhere but from the cache. Previously
9810 we would ignore such annotations at first, but cache them to disk
9811 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
9812 - When you're using bridges and your network goes away and your
9813 bridges get marked as down, recover when you attempt a new socks
9814 connection (if the network is back), rather than waiting up to an
9815 hour to try fetching new descriptors for your bridges. Bugfix on
9816 0.2.0.3-alpha; fixes bug 1981.
9819 - Move to the November 2010 Maxmind GeoLite country db (rather
9820 than the June 2009 ip-to-country GeoIP db) for our statistics that
9821 count how many users relays are seeing from each country. Now we'll
9822 have more accurate data, especially for many African countries.
9824 o New directory authorities:
9825 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
9829 - Fix an assertion failure that could occur in directory caches or
9830 bridge users when using a very short voting interval on a testing
9831 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
9833 - Enforce multiplicity rules when parsing annotations. Bugfix on
9834 0.2.0.8-alpha. Found by piebeer.
9835 - Allow handshaking OR connections to take a full KeepalivePeriod
9836 seconds to handshake. Previously, we would close them after
9837 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
9838 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
9840 - When building with --enable-gcc-warnings on OpenBSD, disable
9841 warnings in system headers. This makes --enable-gcc-warnings
9842 pass on OpenBSD 4.8.
9845 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
9846 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
9847 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
9848 Servers can start sending this code when enough clients recognize
9849 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
9850 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
9851 Patch from mingw-san.
9854 - Remove the old debian/ directory from the main Tor distribution.
9855 The official Tor-for-debian git repository lives at the URL
9856 https://git.torproject.org/debian/tor.git
9857 - Stop shipping the old doc/website/ directory in the tarball. We
9858 changed the website format in late 2010, and what we shipped in
9859 0.2.1.26 really wasn't that useful anyway.
9862 Changes in version 0.2.1.26 - 2010-05-02
9863 Tor 0.2.1.26 addresses the recent connection and memory overload
9864 problems we've been seeing on relays, especially relays with their
9865 DirPort open. If your relay has been crashing, or you turned it off
9866 because it used too many resources, give this release a try.
9868 This release also fixes yet another instance of broken OpenSSL libraries
9869 that was causing some relays to drop out of the consensus.
9872 - Teach relays to defend themselves from connection overload. Relays
9873 now close idle circuits early if it looks like they were intended
9874 for directory fetches. Relays are also more aggressive about closing
9875 TLS connections that have no circuits on them. Such circuits are
9876 unlikely to be re-used, and tens of thousands of them were piling
9877 up at the fast relays, causing the relays to run out of sockets
9878 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
9879 their directory fetches over TLS).
9880 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
9881 that claim to be earlier than 0.9.8m, but which have in reality
9882 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
9883 behavior. Possible fix for some cases of bug 1346.
9884 - Directory mirrors were fetching relay descriptors only from v2
9885 directory authorities, rather than v3 authorities like they should.
9886 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
9887 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
9890 - Finally get rid of the deprecated and now harmful notion of "clique
9891 mode", where directory authorities maintain TLS connections to
9895 - In the util/threads test, no longer free the test_mutex before all
9896 worker threads have finished. Bugfix on 0.2.1.6-alpha.
9897 - The master thread could starve the worker threads quite badly on
9898 certain systems, causing them to run only partially in the allowed
9899 window. This resulted in test failures. Now the master thread sleeps
9900 occasionally for a few microseconds while the two worker-threads
9901 compete for the mutex. Bugfix on 0.2.0.1-alpha.
9904 Changes in version 0.2.1.25 - 2010-03-16
9905 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
9906 prevent relays from guessing their IP address correctly. It also fixes
9907 several minor potential security bugs.
9910 - Fix a regression from our patch for bug 1244 that caused relays
9911 to guess their IP address incorrectly if they didn't set Address
9912 in their torrc and/or their address fails to resolve. Bugfix on
9913 0.2.1.23; fixes bug 1269.
9914 - When freeing a session key, zero it out completely. We only zeroed
9915 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
9916 patched by ekir. Fixes bug 1254.
9919 - Fix a dereference-then-NULL-check sequence when publishing
9920 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
9922 - Fix another dereference-then-NULL-check sequence. Bugfix on
9923 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
9924 - Make sure we treat potentially not NUL-terminated strings correctly.
9925 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
9928 Changes in version 0.2.1.24 - 2010-02-21
9929 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
9933 - Work correctly out-of-the-box with even more vendor-patched versions
9934 of OpenSSL. In particular, make it so Debian and OS X don't need
9935 customized patches to run/build.
9938 Changes in version 0.2.1.23 - 2010-02-13
9939 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
9940 again on the latest OS X, and updates the location of a directory
9943 o Major bugfixes (performance):
9944 - We were selecting our guards uniformly at random, and then weighting
9945 which of our guards we'd use uniformly at random. This imbalance
9946 meant that Tor clients were severely limited on throughput (and
9947 probably latency too) by the first hop in their circuit. Now we
9948 select guards weighted by currently advertised bandwidth. We also
9949 automatically discard guards picked using the old algorithm. Fixes
9950 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
9953 - Make Tor work again on the latest OS X: when deciding whether to
9954 use strange flags to turn TLS renegotiation on, detect the OpenSSL
9955 version at run-time, not compile time. We need to do this because
9956 Apple doesn't update its dev-tools headers when it updates its
9957 libraries in a security patch.
9958 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
9959 that could happen on 32-bit platforms with 64-bit time_t. Also fix
9960 a memory leak when requesting a hidden service descriptor we've
9961 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
9965 - Refactor resolve_my_address() to not use gethostbyname() anymore.
9966 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
9969 - Avoid a mad rush at the beginning of each month when each client
9970 rotates half of its guards. Instead we spread the rotation out
9971 throughout the month, but we still avoid leaving a precise timestamp
9972 in the state file about when we first picked the guard. Improves
9973 over the behavior introduced in 0.1.2.17.
9976 Changes in version 0.2.1.22 - 2010-01-19
9977 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
9978 authorities -- it would tell you its whole history of bridge descriptors
9979 if you make the right directory request. This stable update also
9980 rotates two of the seven v3 directory authority keys and locations.
9982 o Directory authority changes:
9983 - Rotate keys (both v3 identity and relay identity) for moria1
9987 - Stop bridge directory authorities from answering dbg-stability.txt
9988 directory queries, which would let people fetch a list of all
9989 bridge identities they track. Bugfix on 0.2.1.6-alpha.
9992 Changes in version 0.2.1.21 - 2009-12-21
9993 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
9994 library. If you use Tor on Linux / Unix and you're getting SSL
9995 renegotiation errors, upgrading should help. We also recommend an
9996 upgrade if you're an exit relay.
9999 - Work around a security feature in OpenSSL 0.9.8l that prevents our
10000 handshake from working unless we explicitly tell OpenSSL that we
10001 are using SSL renegotiation safely. We are, of course, but OpenSSL
10002 0.9.8l won't work unless we say we are.
10003 - Avoid crashing if the client is trying to upload many bytes and the
10004 circuit gets torn down at the same time, or if the flip side
10005 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
10008 - Do not refuse to learn about authority certs and v2 networkstatus
10009 documents that are older than the latest consensus. This bug might
10010 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
10011 Spotted and fixed by xmux.
10012 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
10013 trigger platform-specific option misparsing case found by Coverity
10015 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
10016 trigger assert. Fixes bug 1173.
10019 Changes in version 0.2.1.20 - 2009-10-15
10020 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
10021 services at once, prepares for more performance improvements, and
10022 fixes a bunch of smaller bugs.
10024 The Windows and OS X bundles also include a more recent Vidalia,
10025 and switch from Privoxy to Polipo.
10027 The OS X installers are now drag and drop. It's best to un-install
10028 Tor/Vidalia and then install this new bundle, rather than upgrade. If
10029 you want to upgrade, you'll need to update the paths for Tor and Polipo
10030 in the Vidalia Settings window.
10033 - Send circuit or stream sendme cells when our window has decreased
10034 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
10035 by Karsten when testing the "reduce circuit window" performance
10036 patch. Bugfix on the 54th commit on Tor -- from July 2002,
10037 before the release of Tor 0.0.0. This is the new winner of the
10039 - Fix a remotely triggerable memory leak when a consensus document
10040 contains more than one signature from the same voter. Bugfix on
10042 - Avoid segfault in rare cases when finishing an introduction circuit
10043 as a client and finding out that we don't have an introduction key
10044 for it. Fixes bug 1073. Reported by Aaron Swartz.
10047 - Tor now reads the "circwindow" parameter out of the consensus,
10048 and uses that value for its circuit package window rather than the
10049 default of 1000 cells. Begins the implementation of proposal 168.
10051 o New directory authorities:
10052 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
10054 - Move moria1 and tonga to alternate IP addresses.
10057 - Fix a signed/unsigned compile warning in 0.2.1.19.
10058 - Fix possible segmentation fault on directory authorities. Bugfix on
10060 - Fix an extremely rare infinite recursion bug that could occur if
10061 we tried to log a message after shutting down the log subsystem.
10062 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
10063 - Fix an obscure bug where hidden services on 64-bit big-endian
10064 systems might mis-read the timestamp in v3 introduce cells, and
10065 refuse to connect back to the client. Discovered by "rotor".
10066 Bugfix on 0.2.1.6-alpha.
10067 - We were triggering a CLOCK_SKEW controller status event whenever
10068 we connect via the v2 connection protocol to any relay that has
10069 a wrong clock. Instead, we should only inform the controller when
10070 it's a trusted authority that claims our clock is wrong. Bugfix
10071 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
10072 - We were telling the controller about CHECKING_REACHABILITY and
10073 REACHABILITY_FAILED status events whenever we launch a testing
10074 circuit or notice that one has failed. Instead, only tell the
10075 controller when we want to inform the user of overall success or
10076 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
10078 - Don't warn when we're using a circuit that ends with a node
10079 excluded in ExcludeExitNodes, but the circuit is not used to access
10080 the outside world. This should help fix bug 1090. Bugfix on
10082 - Work around a small memory leak in some versions of OpenSSL that
10083 stopped the memory used by the hostname TLS extension from being
10087 - Add a "getinfo status/accepted-server-descriptor" controller
10088 command, which is the recommended way for controllers to learn
10089 whether our server descriptor has been successfully received by at
10090 least on directory authority. Un-recommend good-server-descriptor
10091 getinfo and status events until we have a better design for them.
10094 Changes in version 0.2.1.19 - 2009-07-28
10095 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
10099 - Make accessing hidden services on 0.2.1.x work right again.
10100 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
10101 part of patch provided by "optimist".
10104 - When a relay/bridge is writing out its identity key fingerprint to
10105 the "fingerprint" file and to its logs, write it without spaces. Now
10106 it will look like the fingerprints in our bridges documentation,
10107 and confuse fewer users.
10110 - Relays no longer publish a new server descriptor if they change
10111 their MaxAdvertisedBandwidth config option but it doesn't end up
10112 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
10113 fixes bug 1026. Patch from Sebastian.
10114 - Avoid leaking memory every time we get a create cell but we have
10115 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
10116 fixes bug 1034. Reported by BarkerJr.
10119 Changes in version 0.2.1.18 - 2009-07-24
10120 Tor 0.2.1.18 lays the foundations for performance improvements,
10121 adds status events to help users diagnose bootstrap problems, adds
10122 optional authentication/authorization for hidden services, fixes a
10123 variety of potential anonymity problems, and includes a huge pile of
10124 other features and bug fixes.
10126 o Major features (clients):
10127 - Start sending "bootstrap phase" status events to the controller,
10128 so it can keep the user informed of progress fetching directory
10129 information and establishing circuits. Also inform the controller
10130 if we think we're stuck at a particular bootstrap phase. Implements
10132 - Clients replace entry guards that were chosen more than a few months
10133 ago. This change should significantly improve client performance,
10134 especially once more people upgrade, since relays that have been
10135 a guard for a long time are currently overloaded.
10136 - Network status consensus documents and votes now contain bandwidth
10137 information for each relay. Clients use the bandwidth values
10138 in the consensus, rather than the bandwidth values in each
10139 relay descriptor. This approach opens the door to more accurate
10140 bandwidth estimates once the directory authorities start doing
10141 active measurements. Implements part of proposal 141.
10143 o Major features (relays):
10144 - Disable and refactor some debugging checks that forced a linear scan
10145 over the whole server-side DNS cache. These accounted for over 50%
10146 of CPU time on a relatively busy exit node's gprof profile. Also,
10147 disable some debugging checks that appeared in exit node profile
10148 data. Found by Jacob.
10149 - New DirPortFrontPage option that takes an html file and publishes
10150 it as "/" on the DirPort. Now relay operators can provide a
10151 disclaimer without needing to set up a separate webserver. There's
10152 a sample disclaimer in contrib/tor-exit-notice.html.
10154 o Major features (hidden services):
10155 - Make it possible to build hidden services that only certain clients
10156 are allowed to connect to. This is enforced at several points,
10157 so that unauthorized clients are unable to send INTRODUCE cells
10158 to the service, or even (depending on the type of authentication)
10159 to learn introduction points. This feature raises the bar for
10160 certain kinds of active attacks against hidden services. Design
10161 and code by Karsten Loesing. Implements proposal 121.
10162 - Relays now store and serve v2 hidden service descriptors by default,
10163 i.e., the new default value for HidServDirectoryV2 is 1. This is
10164 the last step in proposal 114, which aims to make hidden service
10165 lookups more reliable.
10167 o Major features (path selection):
10168 - ExitNodes and Exclude*Nodes config options now allow you to restrict
10169 by country code ("{US}") or IP address or address pattern
10170 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
10171 refinement to decide what config options should take priority if
10172 you ask to both use a particular node and exclude it.
10174 o Major features (misc):
10175 - When building a consensus, do not include routers that are down.
10176 This cuts down 30% to 40% on consensus size. Implements proposal
10178 - New TestingTorNetwork config option to allow adjustment of
10179 previously constant values that could slow bootstrapping. Implements
10180 proposal 135. Patch from Karsten.
10181 - Convert many internal address representations to optionally hold
10182 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
10183 elements. Make resolver code handle nameservers located at IPv6
10185 - More work on making our TLS handshake blend in: modify the list
10186 of ciphers advertised by OpenSSL in client mode to even more
10187 closely resemble a common web browser. We cheat a little so that
10188 we can advertise ciphers that the locally installed OpenSSL doesn't
10190 - Use the TLS1 hostname extension to more closely resemble browser
10193 o Security fixes (anonymity/entropy):
10194 - Never use a connection with a mismatched address to extend a
10195 circuit, unless that connection is canonical. A canonical
10196 connection is one whose address is authenticated by the router's
10197 identity key, either in a NETINFO cell or in a router descriptor.
10198 - Implement most of proposal 110: The first K cells to be sent
10199 along a circuit are marked as special "early" cells; only K "early"
10200 cells will be allowed. Once this code is universal, we can block
10201 certain kinds of denial-of-service attack by requiring that EXTEND
10202 commands must be sent using an "early" cell.
10203 - Resume using OpenSSL's RAND_poll() for better (and more portable)
10204 cross-platform entropy collection again. We used to use it, then
10205 stopped using it because of a bug that could crash systems that
10206 called RAND_poll when they had a lot of fds open. It looks like the
10207 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
10208 at startup, and to call RAND_poll() when we reseed later only if
10209 we have a non-buggy OpenSSL version.
10210 - When the client is choosing entry guards, now it selects at most
10211 one guard from a given relay family. Otherwise we could end up with
10212 all of our entry points into the network run by the same operator.
10213 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
10214 - Do not use or believe expired v3 authority certificates. Patch
10215 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
10216 - Drop begin cells to a hidden service if they come from the middle
10217 of a circuit. Patch from lark.
10218 - When we erroneously receive two EXTEND cells for the same circuit
10219 ID on the same connection, drop the second. Patch from lark.
10220 - Authorities now vote for the Stable flag for any router whose
10221 weighted MTBF is at least 5 days, regardless of the mean MTBF.
10222 - Clients now never report any stream end reason except 'MISC'.
10223 Implements proposal 148.
10225 o Major bugfixes (crashes):
10226 - Parse dates and IPv4 addresses in a locale- and libc-independent
10227 manner, to avoid platform-dependent behavior on malformed input.
10228 - Fix a crash that occurs on exit nodes when a nameserver request
10229 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
10230 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
10232 - Do not assume that a stack-allocated character array will be
10233 64-bit aligned on platforms that demand that uint64_t access is
10234 aligned. Possible fix for bug 604.
10235 - Resolve a very rare crash bug that could occur when the user forced
10236 a nameserver reconfiguration during the middle of a nameserver
10237 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
10238 - Avoid a "0 divided by 0" calculation when calculating router uptime
10239 at directory authorities. Bugfix on 0.2.0.8-alpha.
10240 - Fix an assertion bug in parsing policy-related options; possible fix
10242 - Rate-limit too-many-sockets messages: when they happen, they happen
10243 a lot and end up filling up the disk. Resolves bug 748.
10244 - Fix a race condition that could cause crashes or memory corruption
10245 when running as a server with a controller listening for log
10247 - Avoid crashing when we have a policy specified in a DirPolicy or
10248 SocksPolicy or ReachableAddresses option with ports set on it,
10249 and we re-load the policy. May fix bug 996.
10250 - Fix an assertion failure on 64-bit platforms when we allocated
10251 memory right up to the end of a memarea, then realigned the memory
10252 one step beyond the end. Fixes a possible cause of bug 930.
10253 - Protect the count of open sockets with a mutex, so we can't
10254 corrupt it when two threads are closing or opening sockets at once.
10255 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
10257 o Major bugfixes (clients):
10258 - Discard router descriptors as we load them if they are more than
10259 five days old. Otherwise if Tor is off for a long time and then
10260 starts with cached descriptors, it will try to use the onion keys
10261 in those obsolete descriptors when building circuits. Fixes bug 887.
10262 - When we choose to abandon a new entry guard because we think our
10263 older ones might be better, close any circuits pending on that
10264 new entry guard connection. This fix should make us recover much
10265 faster when our network is down and then comes back. Bugfix on
10266 0.1.2.8-beta; found by lodger.
10267 - When Tor clients restart after 1-5 days, they discard all their
10268 cached descriptors as too old, but they still use the cached
10269 consensus document. This approach is good for robustness, but
10270 bad for performance: since they don't know any bandwidths, they
10271 end up choosing at random rather than weighting their choice by
10272 speed. Fixed by the above feature of putting bandwidths in the
10275 o Major bugfixes (relays):
10276 - Relays were falling out of the networkstatus consensus for
10277 part of a day if they changed their local config but the
10278 authorities discarded their new descriptor as "not sufficiently
10279 different". Now directory authorities accept a descriptor as changed
10280 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
10281 patch by Sebastian.
10282 - Ensure that two circuits can never exist on the same connection
10283 with the same circuit ID, even if one is marked for close. This
10284 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
10285 - Directory authorities were neglecting to mark relays down in their
10286 internal histories if the relays fall off the routerlist without
10287 ever being found unreachable. So there were relays in the histories
10288 that haven't been seen for eight months, and are listed as being
10289 up for eight months. This wreaked havoc on the "median wfu" and
10290 "median mtbf" calculations, in turn making Guard and Stable flags
10291 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
10294 o Major bugfixes (hidden services):
10295 - When establishing a hidden service, introduction points that
10296 originate from cannibalized circuits were completely ignored
10297 and not included in rendezvous service descriptors. This might
10298 have been another reason for delay in making a hidden service
10299 available. Bugfix from long ago (0.0.9.x?)
10301 o Major bugfixes (memory and resource management):
10302 - Fixed some memory leaks -- some quite frequent, some almost
10303 impossible to trigger -- based on results from Coverity.
10304 - Speed up parsing and cut down on memory fragmentation by using
10305 stack-style allocations for parsing directory objects. Previously,
10306 this accounted for over 40% of allocations from within Tor's code
10307 on a typical directory cache.
10308 - Use a Bloom filter rather than a digest-based set to track which
10309 descriptors we need to keep around when we're cleaning out old
10310 router descriptors. This speeds up the computation significantly,
10311 and may reduce fragmentation.
10313 o New/changed config options:
10314 - Now NodeFamily and MyFamily config options allow spaces in
10315 identity fingerprints, so it's easier to paste them in.
10316 Suggested by Lucky Green.
10317 - Allow ports 465 and 587 in the default exit policy again. We had
10318 rejected them in 0.1.0.15, because back in 2005 they were commonly
10319 misconfigured and ended up as spam targets. We hear they are better
10320 locked down these days.
10321 - Make TrackHostExit mappings expire a while after their last use, not
10322 after their creation. Patch from Robert Hogan.
10323 - Add an ExcludeExitNodes option so users can list a set of nodes
10324 that should be be excluded from the exit node position, but
10325 allowed elsewhere. Implements proposal 151.
10326 - New --hush command-line option similar to --quiet. While --quiet
10327 disables all logging to the console on startup, --hush limits the
10328 output to messages of warning and error severity.
10329 - New configure/torrc options (--enable-geoip-stats,
10330 DirRecordUsageByCountry) to record how many IPs we've served
10331 directory info to in each country code, how many status documents
10332 total we've sent to each country code, and what share of the total
10333 directory requests we should expect to see.
10334 - Make outbound DNS packets respect the OutboundBindAddress setting.
10335 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
10336 - Allow separate log levels to be configured for different logging
10337 domains. For example, this allows one to log all notices, warnings,
10338 or errors, plus all memory management messages of level debug or
10339 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
10340 - Update to the "June 3 2009" ip-to-country file.
10342 o Minor features (relays):
10343 - Raise the minimum rate limiting to be a relay from 20000 bytes
10344 to 20480 bytes (aka 20KB/s), to match our documentation. Also
10345 update directory authorities so they always assign the Fast flag
10346 to relays with 20KB/s of capacity. Now people running relays won't
10347 suddenly find themselves not seeing any use, if the network gets
10349 - If we're a relay and we change our IP address, be more verbose
10350 about the reason that made us change. Should help track down
10351 further bugs for relays on dynamic IP addresses.
10352 - Exit servers can now answer resolve requests for ip6.arpa addresses.
10353 - Implement most of Proposal 152: allow specialized servers to permit
10354 single-hop circuits, and clients to use those servers to build
10355 single-hop circuits when using a specialized controller. Patch
10356 from Josh Albrecht. Resolves feature request 768.
10357 - When relays do their initial bandwidth measurement, don't limit
10358 to just our entry guards for the test circuits. Otherwise we tend
10359 to have multiple test circuits going through a single entry guard,
10360 which makes our bandwidth test less accurate. Fixes part of bug 654;
10361 patch contributed by Josh Albrecht.
10363 o Minor features (directory authorities):
10364 - Try not to open more than one descriptor-downloading connection
10365 to an authority at once. This should reduce load on directory
10366 authorities. Fixes bug 366.
10367 - Add cross-certification to newly generated certificates, so that
10368 a signing key is enough information to look up a certificate. Start
10369 serving certificates by <identity digest, signing key digest>
10370 pairs. Implements proposal 157.
10371 - When a directory authority downloads a descriptor that it then
10372 immediately rejects, do not retry downloading it right away. Should
10373 save some bandwidth on authorities. Fix for bug 888. Patch by
10375 - Directory authorities now serve a /tor/dbg-stability.txt URL to
10376 help debug WFU and MTBF calculations.
10377 - In directory authorities' approved-routers files, allow
10378 fingerprints with or without space.
10380 o Minor features (directory mirrors):
10381 - When a download gets us zero good descriptors, do not notify
10382 Tor that new directory information has arrived.
10383 - Servers support a new URL scheme for consensus downloads that
10384 allows the client to specify which authorities are trusted.
10385 The server then only sends the consensus if the client will trust
10386 it. Otherwise a 404 error is sent back. Clients use this
10387 new scheme when the server supports it (meaning it's running
10388 0.2.1.1-alpha or later). Implements proposal 134.
10390 o Minor features (bridges):
10391 - If the bridge config line doesn't specify a port, assume 443.
10392 This makes bridge lines a bit smaller and easier for users to
10394 - If we're using bridges and our network goes away, be more willing
10395 to forgive our bridges and try again when we get an application
10398 o Minor features (hidden services):
10399 - When the client launches an introduction circuit, retry with a
10400 new circuit after 30 seconds rather than 60 seconds.
10401 - Launch a second client-side introduction circuit in parallel
10402 after a delay of 15 seconds (based on work by Christian Wilms).
10403 - Hidden services start out building five intro circuits rather
10404 than three, and when the first three finish they publish a service
10405 descriptor using those. Now we publish our service descriptor much
10406 faster after restart.
10407 - Drop the requirement to have an open dir port for storing and
10408 serving v2 hidden service descriptors.
10410 o Minor features (build and packaging):
10411 - On Linux, use the prctl call to re-enable core dumps when the User
10413 - Try to make sure that the version of Libevent we're running with
10414 is binary-compatible with the one we built with. May address bug
10416 - Add a new --enable-local-appdata configuration switch to change
10417 the default location of the datadir on win32 from APPDATA to
10418 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
10419 entirely. Patch from coderman.
10420 - Build correctly against versions of OpenSSL 0.9.8 or later that
10421 are built without support for deprecated functions.
10422 - On platforms with a maximum syslog string length, truncate syslog
10423 messages to that length ourselves, rather than relying on the
10424 system to do it for us.
10425 - Automatically detect MacOSX versions earlier than 10.4.0, and
10426 disable kqueue from inside Tor when running with these versions.
10427 We previously did this from the startup script, but that was no
10428 help to people who didn't use the startup script. Resolves bug 863.
10429 - Build correctly when configured to build outside the main source
10430 path. Patch from Michael Gold.
10431 - Disable GCC's strict alias optimization by default, to avoid the
10432 likelihood of its introducing subtle bugs whenever our code violates
10433 the letter of C99's alias rules.
10434 - Change the contrib/tor.logrotate script so it makes the new
10435 logs as "_tor:_tor" rather than the default, which is generally
10436 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
10437 - Change our header file guard macros to be less likely to conflict
10438 with system headers. Adam Langley noticed that we were conflicting
10439 with log.h on Android.
10440 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
10441 and stop using a warning that had become unfixably verbose under
10443 - Use a lockfile to make sure that two Tor processes are not
10444 simultaneously running with the same datadir.
10445 - Allow OpenSSL to use dynamic locks if it wants.
10446 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
10448 o Minor features (controllers):
10449 - When generating circuit events with verbose nicknames for
10450 controllers, try harder to look up nicknames for routers on a
10451 circuit. (Previously, we would look in the router descriptors we had
10452 for nicknames, but not in the consensus.) Partial fix for bug 941.
10453 - New controller event NEWCONSENSUS that lists the networkstatus
10454 lines for every recommended relay. Now controllers like Torflow
10455 can keep up-to-date on which relays they should be using.
10456 - New controller event "clients_seen" to report a geoip-based summary
10457 of which countries we've seen clients from recently. Now controllers
10458 like Vidalia can show bridge operators that they're actually making
10460 - Add a 'getinfo status/clients-seen' controller command, in case
10461 controllers want to hear clients_seen events but connect late.
10462 - New CONSENSUS_ARRIVED event to note when a new consensus has
10463 been fetched and validated.
10464 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
10465 controllers to prevent SIGHUP from reloading the configuration.
10467 - Return circuit purposes in response to GETINFO circuit-status.
10469 - Serve the latest v3 networkstatus consensus via the control
10470 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
10471 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
10472 controller can query our current bootstrap state in case it attaches
10473 partway through and wants to catch up.
10474 - Provide circuit purposes along with circuit events to the controller.
10476 o Minor features (tools):
10477 - Do not have tor-resolve automatically refuse all .onion addresses;
10478 if AutomapHostsOnResolve is set in your torrc, this will work fine.
10479 - Add a -p option to tor-resolve for specifying the SOCKS port: some
10480 people find host:port too confusing.
10481 - Print the SOCKS5 error message string as well as the error code
10482 when a tor-resolve request fails. Patch from Jacob.
10484 o Minor bugfixes (memory and resource management):
10485 - Clients no longer cache certificates for authorities they do not
10486 recognize. Bugfix on 0.2.0.9-alpha.
10487 - Do not use C's stdio library for writing to log files. This will
10488 improve logging performance by a minute amount, and will stop
10489 leaking fds when our disk is full. Fixes bug 861.
10490 - Stop erroneous use of O_APPEND in cases where we did not in fact
10491 want to re-seek to the end of a file before every last write().
10492 - Fix a small alignment and memory-wasting bug on buffer chunks.
10494 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
10495 to avoid unused RAM in buffer chunks and memory pools.
10496 - Reduce the default smartlist size from 32 to 16; it turns out that
10497 most smartlists hold around 8-12 elements tops.
10498 - Make dumpstats() log the fullness and size of openssl-internal
10500 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
10501 patch to their OpenSSL, turn it on to save memory on servers. This
10502 patch will (with any luck) get included in a mainline distribution
10504 - Fix a memory leak when v3 directory authorities load their keys
10505 and cert from disk. Bugfix on 0.2.0.1-alpha.
10506 - Stop using malloc_usable_size() to use more area than we had
10507 actually allocated: it was safe, but made valgrind really unhappy.
10508 - Make the assert_circuit_ok() function work correctly on circuits that
10509 have already been marked for close.
10510 - Fix uninitialized size field for memory area allocation: may improve
10511 memory performance during directory parsing.
10513 o Minor bugfixes (clients):
10514 - Stop reloading the router list from disk for no reason when we
10515 run out of reachable directory mirrors. Once upon a time reloading
10516 it would set the 'is_running' flag back to 1 for them. It hasn't
10517 done that for a long time.
10518 - When we had picked an exit node for a connection, but marked it as
10519 "optional", and it turned out we had no onion key for the exit,
10520 stop wanting that exit and try again. This situation may not
10521 be possible now, but will probably become feasible with proposal
10522 158. Spotted by rovv. Fixes another case of bug 752.
10523 - Fix a bug in address parsing that was preventing bridges or hidden
10524 service targets from being at IPv6 addresses.
10525 - Do not remove routers as too old if we do not have any consensus
10526 document. Bugfix on 0.2.0.7-alpha.
10527 - When an exit relay resolves a stream address to a local IP address,
10528 do not just keep retrying that same exit relay over and
10529 over. Instead, just close the stream. Addresses bug 872. Bugfix
10530 on 0.2.0.32. Patch from rovv.
10531 - Made Tor a little less aggressive about deleting expired
10532 certificates. Partial fix for bug 854.
10533 - Treat duplicate certificate fetches as failures, so that we do
10534 not try to re-fetch an expired certificate over and over and over.
10535 - Do not say we're fetching a certificate when we'll in fact skip it
10536 because of a pending download.
10537 - If we have correct permissions on $datadir, we complain to stdout
10538 and fail to start. But dangerous permissions on
10539 $datadir/cached-status/ would cause us to open a log and complain
10540 there. Now complain to stdout and fail to start in both cases. Fixes
10541 bug 820, reported by seeess.
10543 o Minor bugfixes (bridges):
10544 - When we made bridge authorities stop serving bridge descriptors over
10545 unencrypted links, we also broke DirPort reachability testing for
10546 bridges. So bridges with a non-zero DirPort were printing spurious
10547 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
10548 - Don't allow a bridge to publish its router descriptor to a
10549 non-bridge directory authority. Fixes part of bug 932.
10550 - When we change to or from being a bridge, reset our counts of
10551 client usage by country. Fixes bug 932.
10553 o Minor bugfixes (relays):
10554 - Log correct error messages for DNS-related network errors on
10556 - Actually return -1 in the error case for read_bandwidth_usage().
10557 Harmless bug, since we currently don't care about the return value
10558 anywhere. Bugfix on 0.2.0.9-alpha.
10559 - Provide a more useful log message if bug 977 (related to buffer
10560 freelists) ever reappears, and do not crash right away.
10561 - We were already rejecting relay begin cells with destination port
10562 of 0. Now also reject extend cells with destination port or address
10563 of 0. Suggested by lark.
10564 - When we can't transmit a DNS request due to a network error, retry
10565 it after a while, and eventually transmit a failing response to
10566 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
10567 - Solve a bug that kept hardware crypto acceleration from getting
10568 enabled when accounting was turned on. Fixes bug 907. Bugfix on
10570 - When a canonical connection appears later in our internal list
10571 than a noncanonical one for a given OR ID, always use the
10572 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
10574 - Avoid some nasty corner cases in the logic for marking connections
10575 as too old or obsolete or noncanonical for circuits. Partial
10577 - Fix another interesting corner-case of bug 891 spotted by rovv:
10578 Previously, if two hosts had different amounts of clock drift, and
10579 one of them created a new connection with just the wrong timing,
10580 the other might decide to deprecate the new connection erroneously.
10581 Bugfix on 0.1.1.13-alpha.
10582 - If one win32 nameserver fails to get added, continue adding the
10583 rest, and don't automatically fail.
10584 - Fix a bug where an unreachable relay would establish enough
10585 reachability testing circuits to do a bandwidth test -- if
10586 we already have a connection to the middle hop of the testing
10587 circuit, then it could establish the last hop by using the existing
10588 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
10589 circuits no longer use entry guards in 0.2.1.3-alpha.
10591 o Minor bugfixes (directory authorities):
10592 - Limit uploaded directory documents to be 16M rather than 500K.
10593 The directory authorities were refusing v3 consensus votes from
10594 other authorities, since the votes are now 504K. Fixes bug 959;
10595 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
10596 - Directory authorities should never send a 503 "busy" response to
10597 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
10599 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
10600 headers. Bugfix on 0.2.0.10-alpha.
10602 o Minor bugfixes (hidden services):
10603 - When we can't find an intro key for a v2 hidden service descriptor,
10604 fall back to the v0 hidden service descriptor and log a bug message.
10605 Workaround for bug 1024.
10606 - In very rare situations new hidden service descriptors were
10607 published earlier than 30 seconds after the last change to the
10608 service. (We currently think that a hidden service descriptor
10609 that's been stable for 30 seconds is worth publishing.)
10610 - If a hidden service sends us an END cell, do not consider
10611 retrying the connection; just close it. Patch from rovv.
10612 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
10613 service directories if they have no advertised dir port. Bugfix
10616 o Minor bugfixes (tools):
10617 - In the torify(1) manpage, mention that tsocks will leak your
10620 o Minor bugfixes (controllers):
10621 - If the controller claimed responsibility for a stream, but that
10622 stream never finished making its connection, it would live
10623 forever in circuit_wait state. Now we close it after SocksTimeout
10624 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
10625 - Make DNS resolved controller events into "CLOSED", not
10626 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
10628 - The control port would close the connection before flushing long
10629 replies, such as the network consensus, if a QUIT command was issued
10630 before the reply had completed. Now, the control port flushes all
10631 pending replies before closing the connection. Also fix a spurious
10632 warning when a QUIT command is issued after a malformed or rejected
10633 AUTHENTICATE command, but before the connection was closed. Patch
10634 by Marcus Griep. Fixes bugs 1015 and 1016.
10635 - Fix a bug that made stream bandwidth get misreported to the
10638 o Deprecated and removed features:
10639 - The old "tor --version --version" command, which would print out
10640 the subversion "Id" of most of the source files, is now removed. It
10641 turned out to be less useful than we'd expected, and harder to
10643 - RedirectExits has been removed. It was deprecated since
10645 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
10646 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
10647 - Cell pools are now always enabled; --disable-cell-pools is ignored.
10648 - Directory mirrors no longer fetch the v1 directory or
10649 running-routers files. They are obsolete, and nobody asks for them
10650 anymore. This is the first step to making v1 authorities obsolete.
10651 - Take out the TestVia config option, since it was a workaround for
10652 a bug that was fixed in Tor 0.1.1.21.
10653 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
10654 HiddenServiceExcludeNodes as obsolete: they never worked properly,
10655 and nobody seems to be using them. Fixes bug 754. Bugfix on
10656 0.1.0.1-rc. Patch from Christian Wilms.
10657 - Remove all backward-compatibility code for relays running
10658 versions of Tor so old that they no longer work at all on the
10661 o Code simplifications and refactoring:
10662 - Tool-assisted documentation cleanup. Nearly every function or
10663 static variable in Tor should have its own documentation now.
10664 - Rename the confusing or_is_obsolete field to the more appropriate
10665 is_bad_for_new_circs, and move it to or_connection_t where it
10667 - Move edge-only flags from connection_t to edge_connection_t: not
10668 only is this better coding, but on machines of plausible alignment,
10669 it should save 4-8 bytes per connection_t. "Every little bit helps."
10670 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
10671 for consistency; keep old option working for backward compatibility.
10672 - Simplify the code for finding connections to use for a circuit.
10673 - Revise the connection_new functions so that a more typesafe variant
10674 exists. This will work better with Coverity, and let us find any
10675 actual mistakes we're making here.
10676 - Refactor unit testing logic so that dmalloc can be used sensibly
10677 with unit tests to check for memory leaks.
10678 - Move all hidden-service related fields from connection and circuit
10679 structure to substructures: this way they won't eat so much memory.
10680 - Squeeze 2-5% out of client performance (according to oprofile) by
10681 improving the implementation of some policy-manipulation functions.
10682 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
10683 be more efficient. Formerly it was quadratic in the number of
10684 servers; now it should be linear. Fixes bug 509.
10685 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
10686 and n_conn_id_digest fields into a separate structure that's
10687 only needed when the circuit has not yet attached to an n_conn.
10688 - Optimize out calls to time(NULL) that occur for every IO operation,
10689 or for every cell. On systems like Windows where time() is a
10690 slow syscall, this fix will be slightly helpful.
10693 Changes in version 0.2.0.35 - 2009-06-24
10695 - Avoid crashing in the presence of certain malformed descriptors.
10696 Found by lark, and by automated fuzzing.
10697 - Fix an edge case where a malicious exit relay could convince a
10698 controller that the client's DNS question resolves to an internal IP
10699 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
10702 - Finally fix the bug where dynamic-IP relays disappear when their
10703 IP address changes: directory mirrors were mistakenly telling
10704 them their old address if they asked via begin_dir, so they
10705 never got an accurate answer about their new address, so they
10706 just vanished after a day. For belt-and-suspenders, relays that
10707 don't set Address in their config now avoid using begin_dir for
10708 all direct connections. Should fix bugs 827, 883, and 900.
10709 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
10710 that would occur on some exit nodes when DNS failures and timeouts
10711 occurred in certain patterns. Fix for bug 957.
10714 - When starting with a cache over a few days old, do not leak
10715 memory for the obsolete router descriptors in it. Bugfix on
10716 0.2.0.33; fixes bug 672.
10717 - Hidden service clients didn't use a cached service descriptor that
10718 was older than 15 minutes, but wouldn't fetch a new one either,
10719 because there was already one in the cache. Now, fetch a v2
10720 descriptor unless the same descriptor was added to the cache within
10721 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
10724 Changes in version 0.2.0.34 - 2009-02-08
10725 Tor 0.2.0.34 features several more security-related fixes. You should
10726 upgrade, especially if you run an exit relay (remote crash) or a
10727 directory authority (remote infinite loop), or you're on an older
10728 (pre-XP) or not-recently-patched Windows (remote exploit).
10730 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
10731 have many known flaws, and nobody should be using them. You should
10732 upgrade. If you're using a Linux or BSD and its packages are obsolete,
10733 stop using those packages and upgrade anyway.
10736 - Fix an infinite-loop bug on handling corrupt votes under certain
10737 circumstances. Bugfix on 0.2.0.8-alpha.
10738 - Fix a temporary DoS vulnerability that could be performed by
10739 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
10740 - Avoid a potential crash on exit nodes when processing malformed
10741 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
10742 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
10743 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
10746 - Fix compilation on systems where time_t is a 64-bit integer.
10747 Patch from Matthias Drochner.
10748 - Don't consider expiring already-closed client connections. Fixes
10749 bug 893. Bugfix on 0.0.2pre20.
10752 Changes in version 0.2.0.33 - 2009-01-21
10753 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
10754 useful to users. It also finally fixes a bug where a relay or client
10755 that's been off for many days would take a long time to bootstrap.
10757 This update also fixes an important security-related bug reported by
10758 Ilja van Sprundel. You should upgrade. (We'll send out more details
10759 about the bug once people have had some time to upgrade.)
10762 - Fix a heap-corruption bug that may be remotely triggerable on
10763 some platforms. Reported by Ilja van Sprundel.
10766 - When a stream at an exit relay is in state "resolving" or
10767 "connecting" and it receives an "end" relay cell, the exit relay
10768 would silently ignore the end cell and not close the stream. If
10769 the client never closes the circuit, then the exit relay never
10770 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
10771 reported by "wood".
10772 - When sending CREATED cells back for a given circuit, use a 64-bit
10773 connection ID to find the right connection, rather than an addr:port
10774 combination. Now that we can have multiple OR connections between
10775 the same ORs, it is no longer possible to use addr:port to uniquely
10776 identify a connection.
10777 - Bridge relays that had DirPort set to 0 would stop fetching
10778 descriptors shortly after startup, and then briefly resume
10779 after a new bandwidth test and/or after publishing a new bridge
10780 descriptor. Bridge users that try to bootstrap from them would
10781 get a recent networkstatus but would get descriptors from up to
10782 18 hours earlier, meaning most of the descriptors were obsolete
10783 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
10784 - Prevent bridge relays from serving their 'extrainfo' document
10785 to anybody who asks, now that extrainfo docs include potentially
10786 sensitive aggregated client geoip summaries. Bugfix on
10788 - If the cached networkstatus consensus is more than five days old,
10789 discard it rather than trying to use it. In theory it could be
10790 useful because it lists alternate directory mirrors, but in practice
10791 it just means we spend many minutes trying directory mirrors that
10792 are long gone from the network. Also discard router descriptors as
10793 we load them if they are more than five days old, since the onion
10794 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
10797 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
10798 could make gcc generate non-functional binary search code. Bugfix
10800 - Build correctly on platforms without socklen_t.
10801 - Compile without warnings on solaris.
10802 - Avoid potential crash on internal error during signature collection.
10803 Fixes bug 864. Patch from rovv.
10804 - Correct handling of possible malformed authority signing key
10805 certificates with internal signature types. Fixes bug 880.
10806 Bugfix on 0.2.0.3-alpha.
10807 - Fix a hard-to-trigger resource leak when logging credential status.
10809 - When we can't initialize DNS because the network is down, do not
10810 automatically stop Tor from starting. Instead, we retry failed
10811 dns_init() every 10 minutes, and change the exit policy to reject
10812 *:* until one succeeds. Fixes bug 691.
10813 - Use 64 bits instead of 32 bits for connection identifiers used with
10814 the controller protocol, to greatly reduce risk of identifier reuse.
10815 - When we're choosing an exit node for a circuit, and we have
10816 no pending streams, choose a good general exit rather than one that
10817 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
10818 - Fix another case of assuming, when a specific exit is requested,
10819 that we know more than the user about what hosts it allows.
10820 Fixes one case of bug 752. Patch from rovv.
10821 - Clip the MaxCircuitDirtiness config option to a minimum of 10
10822 seconds. Warn the user if lower values are given in the
10823 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
10824 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
10825 user if lower values are given in the configuration. Bugfix on
10826 0.1.1.17-rc. Patch by Sebastian.
10827 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
10828 the cache because we already had a v0 descriptor with the same ID.
10829 Bugfix on 0.2.0.18-alpha.
10830 - Fix a race condition when freeing keys shared between main thread
10831 and CPU workers that could result in a memory leak. Bugfix on
10832 0.1.0.1-rc. Fixes bug 889.
10833 - Send a valid END cell back when a client tries to connect to a
10834 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
10835 840. Patch from rovv.
10836 - Check which hops rendezvous stream cells are associated with to
10837 prevent possible guess-the-streamid injection attacks from
10838 intermediate hops. Fixes another case of bug 446. Based on patch
10840 - If a broken client asks a non-exit router to connect somewhere,
10841 do not even do the DNS lookup before rejecting the connection.
10842 Fixes another case of bug 619. Patch from rovv.
10843 - When a relay gets a create cell it can't decrypt (e.g. because it's
10844 using the wrong onion key), we were dropping it and letting the
10845 client time out. Now actually answer with a destroy cell. Fixes
10846 bug 904. Bugfix on 0.0.2pre8.
10848 o Minor bugfixes (hidden services):
10849 - Do not throw away existing introduction points on SIGHUP. Bugfix on
10850 0.0.6pre1. Patch by Karsten. Fixes bug 874.
10853 - Report the case where all signatures in a detached set are rejected
10854 differently than the case where there is an error handling the
10856 - When we realize that another process has modified our cached
10857 descriptors, print out a more useful error message rather than
10858 triggering an assertion. Fixes bug 885. Patch from Karsten.
10859 - Implement the 0x20 hack to better resist DNS poisoning: set the
10860 case on outgoing DNS requests randomly, and reject responses that do
10861 not match the case correctly. This logic can be disabled with the
10862 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
10863 of servers that do not reliably preserve case in replies. See
10864 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
10866 - Check DNS replies for more matching fields to better resist DNS
10868 - Never use OpenSSL compression: it wastes RAM and CPU trying to
10869 compress cells, which are basically all encrypted, compressed, or
10873 Changes in version 0.2.0.32 - 2008-11-20
10874 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
10875 packages (and maybe other packages) noticed by Theo de Raadt, fixes
10876 a smaller security flaw that might allow an attacker to access local
10877 services, further improves hidden service performance, and fixes a
10878 variety of other issues.
10881 - The "User" and "Group" config options did not clear the
10882 supplementary group entries for the Tor process. The "User" option
10883 is now more robust, and we now set the groups to the specified
10884 user's primary group. The "Group" option is now ignored. For more
10885 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
10886 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
10887 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
10888 - The "ClientDNSRejectInternalAddresses" config option wasn't being
10889 consistently obeyed: if an exit relay refuses a stream because its
10890 exit policy doesn't allow it, we would remember what IP address
10891 the relay said the destination address resolves to, even if it's
10892 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
10895 - Fix a DOS opportunity during the voting signature collection process
10896 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
10898 o Major bugfixes (hidden services):
10899 - When fetching v0 and v2 rendezvous service descriptors in parallel,
10900 we were failing the whole hidden service request when the v0
10901 descriptor fetch fails, even if the v2 fetch is still pending and
10902 might succeed. Similarly, if the last v2 fetch fails, we were
10903 failing the whole hidden service request even if a v0 fetch is
10904 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
10905 - When extending a circuit to a hidden service directory to upload a
10906 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
10907 requests failed, because the router descriptor has not been
10908 downloaded yet. In these cases, do not attempt to upload the
10909 rendezvous descriptor, but wait until the router descriptor is
10910 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
10911 descriptor from a hidden service directory for which the router
10912 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
10916 - Fix several infrequent memory leaks spotted by Coverity.
10917 - When testing for libevent functions, set the LDFLAGS variable
10918 correctly. Found by Riastradh.
10919 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
10920 bootstrapping with tunneled directory connections. Bugfix on
10921 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
10922 - When asked to connect to A.B.exit:80, if we don't know the IP for A
10923 and we know that server B rejects most-but-not all connections to
10924 port 80, we would previously reject the connection. Now, we assume
10925 the user knows what they were asking for. Fixes bug 752. Bugfix
10926 on 0.0.9rc5. Diagnosed by BarkerJr.
10927 - If we overrun our per-second write limits a little, count this as
10928 having used up our write allocation for the second, and choke
10929 outgoing directory writes. Previously, we had only counted this when
10930 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
10931 Bugfix on 0.2.0.x (??).
10932 - Remove the old v2 directory authority 'lefkada' from the default
10933 list. It has been gone for many months.
10934 - Stop doing unaligned memory access that generated bus errors on
10935 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
10936 - Make USR2 log-level switch take effect immediately. Bugfix on
10939 o Minor bugfixes (controller):
10940 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
10941 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
10944 Changes in version 0.2.0.31 - 2008-09-03
10945 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
10946 a big bug we're seeing where in rare cases traffic from one Tor stream
10947 gets mixed into another stream, and fixes a variety of smaller issues.
10950 - Make sure that two circuits can never exist on the same connection
10951 with the same circuit ID, even if one is marked for close. This
10952 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
10953 - Relays now reject risky extend cells: if the extend cell includes
10954 a digest of all zeroes, or asks to extend back to the relay that
10955 sent the extend cell, tear down the circuit. Ideas suggested
10957 - If not enough of our entry guards are available so we add a new
10958 one, we might use the new one even if it overlapped with the
10959 current circuit's exit relay (or its family). Anonymity bugfix
10960 pointed out by rovv.
10963 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
10964 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
10965 - Correctly detect the presence of the linux/netfilter_ipv4.h header
10966 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
10967 - Pick size of default geoip filename string correctly on windows.
10968 Fixes bug 806. Bugfix on 0.2.0.30.
10969 - Make the autoconf script accept the obsolete --with-ssl-dir
10970 option as an alias for the actually-working --with-openssl-dir
10971 option. Fix the help documentation to recommend --with-openssl-dir.
10972 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
10973 - When using the TransPort option on OpenBSD, and using the User
10974 option to change UID and drop privileges, make sure to open
10975 /dev/pf before dropping privileges. Fixes bug 782. Patch from
10976 Christopher Davis. Bugfix on 0.1.2.1-alpha.
10977 - Try to attach connections immediately upon receiving a RENDEZVOUS2
10978 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
10979 on the client side when connecting to a hidden service. Bugfix
10980 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
10981 - When closing an application-side connection because its circuit is
10982 getting torn down, generate the stream event correctly. Bugfix on
10983 0.1.2.x. Anonymous patch.
10986 Changes in version 0.2.0.30 - 2008-07-15
10987 This new stable release switches to a more efficient directory
10988 distribution design, adds features to make connections to the Tor
10989 network harder to block, allows Tor to act as a DNS proxy, adds separate
10990 rate limiting for relayed traffic to make it easier for clients to
10991 become relays, fixes a variety of potential anonymity problems, and
10992 includes the usual huge pile of other features and bug fixes.
10994 o New v3 directory design:
10995 - Tor now uses a new way to learn about and distribute information
10996 about the network: the directory authorities vote on a common
10997 network status document rather than each publishing their own
10998 opinion. Now clients and caches download only one networkstatus
10999 document to bootstrap, rather than downloading one for each
11000 authority. Clients only download router descriptors listed in
11001 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
11003 - Set up moria1, tor26, and dizum as v3 directory authorities
11004 in addition to being v2 authorities. Also add three new ones:
11005 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
11006 dannenberg (run by CCC).
11007 - Switch to multi-level keys for directory authorities: now their
11008 long-term identity key can be kept offline, and they periodically
11009 generate a new signing key. Clients fetch the "key certificates"
11010 to keep up to date on the right keys. Add a standalone tool
11011 "tor-gencert" to generate key certificates. Implements proposal 103.
11012 - Add a new V3AuthUseLegacyKey config option to make it easier for
11013 v3 authorities to change their identity keys if another bug like
11014 Debian's OpenSSL RNG flaw appears.
11015 - Authorities and caches fetch the v2 networkstatus documents
11016 less often, now that v3 is recommended.
11018 o Make Tor connections stand out less on the wire:
11019 - Use an improved TLS handshake designed by Steven Murdoch in proposal
11020 124, as revised in proposal 130. The new handshake is meant to
11021 be harder for censors to fingerprint, and it adds the ability
11022 to detect certain kinds of man-in-the-middle traffic analysis
11023 attacks. The new handshake format includes version negotiation for
11024 OR connections as described in proposal 105, which will allow us
11025 to improve Tor's link protocol more safely in the future.
11026 - Enable encrypted directory connections by default for non-relays,
11027 so censor tools that block Tor directory connections based on their
11028 plaintext patterns will no longer work. This means Tor works in
11029 certain censored countries by default again.
11030 - Stop including recognizeable strings in the commonname part of
11031 Tor's x509 certificates.
11033 o Implement bridge relays:
11034 - Bridge relays (or "bridges" for short) are Tor relays that aren't
11035 listed in the main Tor directory. Since there is no complete public
11036 list of them, even an ISP that is filtering connections to all the
11037 known Tor relays probably won't be able to block all the bridges.
11038 See doc/design-paper/blocking.pdf and proposal 125 for details.
11039 - New config option BridgeRelay that specifies you want to be a
11040 bridge relay rather than a normal relay. When BridgeRelay is set
11041 to 1, then a) you cache dir info even if your DirPort ins't on,
11042 and b) the default for PublishServerDescriptor is now "bridge"
11043 rather than "v2,v3".
11044 - New config option "UseBridges 1" for clients that want to use bridge
11045 relays instead of ordinary entry guards. Clients then specify
11046 bridge relays by adding "Bridge" lines to their config file. Users
11047 can learn about a bridge relay either manually through word of
11048 mouth, or by one of our rate-limited mechanisms for giving out
11049 bridge addresses without letting an attacker easily enumerate them
11050 all. See https://www.torproject.org/bridges for details.
11051 - Bridge relays behave like clients with respect to time intervals
11052 for downloading new v3 consensus documents -- otherwise they
11053 stand out. Bridge users now wait until the end of the interval,
11054 so their bridge relay will be sure to have a new consensus document.
11056 o Implement bridge directory authorities:
11057 - Bridge authorities are like normal directory authorities, except
11058 they don't serve a list of known bridges. Therefore users that know
11059 a bridge's fingerprint can fetch a relay descriptor for that bridge,
11060 including fetching updates e.g. if the bridge changes IP address,
11061 yet an attacker can't just fetch a list of all the bridges.
11062 - Set up Tonga as the default bridge directory authority.
11063 - Bridge authorities refuse to serve bridge descriptors or other
11064 bridge information over unencrypted connections (that is, when
11065 responding to direct DirPort requests rather than begin_dir cells.)
11066 - Bridge directory authorities do reachability testing on the
11067 bridges they know. They provide router status summaries to the
11068 controller via "getinfo ns/purpose/bridge", and also dump summaries
11069 to a file periodically, so we can keep internal stats about which
11070 bridges are functioning.
11071 - If bridge users set the UpdateBridgesFromAuthority config option,
11072 but the digest they ask for is a 404 on the bridge authority,
11073 they fall back to contacting the bridge directly.
11074 - Bridges always use begin_dir to publish their server descriptor to
11075 the bridge authority using an anonymous encrypted tunnel.
11076 - Early work on a "bridge community" design: if bridge authorities set
11077 the BridgePassword config option, they will serve a snapshot of
11078 known bridge routerstatuses from their DirPort to anybody who
11079 knows that password. Unset by default.
11080 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
11081 report sanitized aggregated summaries in their extra-info documents
11082 privately to the bridge authority, listing which countries are
11083 able to reach them. We hope this mechanism will let us learn when
11084 certain countries start trying to block bridges.
11085 - Bridge authorities write bridge descriptors to disk, so they can
11086 reload them after a reboot. They can also export the descriptors
11087 to other programs, so we can distribute them to blocked users via
11088 the BridgeDB interface, e.g. via https://bridges.torproject.org/
11089 and bridges@torproject.org.
11091 o Tor can be a DNS proxy:
11092 - The new client-side DNS proxy feature replaces the need for
11093 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
11094 for DNS requests on port 9999, use the Tor network to resolve them
11095 anonymously, and send the reply back like a regular DNS server.
11096 The code still only implements a subset of DNS.
11097 - Add a new AutomapHostsOnResolve option: when it is enabled, any
11098 resolve request for hosts matching a given pattern causes Tor to
11099 generate an internal virtual address mapping for that host. This
11100 allows DNSPort to work sensibly with hidden service users. By
11101 default, .exit and .onion addresses are remapped; the list of
11102 patterns can be reconfigured with AutomapHostsSuffixes.
11103 - Add an "-F" option to tor-resolve to force a resolve for a .onion
11104 address. Thanks to the AutomapHostsOnResolve option, this is no
11105 longer a completely silly thing to do.
11107 o Major features (relay usability):
11108 - New config options RelayBandwidthRate and RelayBandwidthBurst:
11109 a separate set of token buckets for relayed traffic. Right now
11110 relayed traffic is defined as answers to directory requests, and
11111 OR connections that don't have any local circuits on them. See
11112 proposal 111 for details.
11113 - Create listener connections before we setuid to the configured
11114 User and Group. Now non-Windows users can choose port values
11115 under 1024, start Tor as root, and have Tor bind those ports
11116 before it changes to another UID. (Windows users could already
11118 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
11119 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
11120 on "vserver" accounts. Patch from coderman.
11122 o Major features (directory authorities):
11123 - Directory authorities track weighted fractional uptime and weighted
11124 mean-time-between failures for relays. WFU is suitable for deciding
11125 whether a node is "usually up", while MTBF is suitable for deciding
11126 whether a node is "likely to stay up." We need both, because
11127 "usually up" is a good requirement for guards, while "likely to
11128 stay up" is a good requirement for long-lived connections.
11129 - Directory authorities use a new formula for selecting which relays
11130 to advertise as Guards: they must be in the top 7/8 in terms of
11131 how long we have known about them, and above the median of those
11132 nodes in terms of weighted fractional uptime.
11133 - Directory authorities use a new formula for selecting which relays
11134 to advertise as Stable: when we have 4 or more days of data, use
11135 median measured MTBF rather than median declared uptime. Implements
11137 - Directory authorities accept and serve "extra info" documents for
11138 routers. Routers now publish their bandwidth-history lines in the
11139 extra-info docs rather than the main descriptor. This step saves
11140 60% (!) on compressed router descriptor downloads. Servers upload
11141 extra-info docs to any authority that accepts them; directory
11142 authorities now allow multiple router descriptors and/or extra
11143 info documents to be uploaded in a single go. Authorities, and
11144 caches that have been configured to download extra-info documents,
11145 download them as needed. Implements proposal 104.
11146 - Authorities now list relays who have the same nickname as
11147 a different named relay, but list them with a new flag:
11148 "Unnamed". Now we can make use of relays that happen to pick the
11149 same nickname as a server that registered two years ago and then
11150 disappeared. Implements proposal 122.
11151 - Store routers in a file called cached-descriptors instead of in
11152 cached-routers. Initialize cached-descriptors from cached-routers
11153 if the old format is around. The new format allows us to store
11154 annotations along with descriptors, to record the time we received
11155 each descriptor, its source, and its purpose: currently one of
11156 general, controller, or bridge.
11158 o Major features (other):
11159 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
11160 Tor can warn and/or refuse connections to ports commonly used with
11161 vulnerable-plaintext protocols. Currently we warn on ports 23,
11162 109, 110, and 143, but we don't reject any. Based on proposal 129
11163 by Kevin Bauer and Damon McCoy.
11164 - Integrate Karsten Loesing's Google Summer of Code project to publish
11165 hidden service descriptors on a set of redundant relays that are a
11166 function of the hidden service address. Now we don't have to rely
11167 on three central hidden service authorities for publishing and
11168 fetching every hidden service descriptor. Implements proposal 114.
11169 - Allow tunnelled directory connections to ask for an encrypted
11170 "begin_dir" connection or an anonymized "uses a full Tor circuit"
11171 connection independently. Now we can make anonymized begin_dir
11172 connections for (e.g.) more secure hidden service posting and
11175 o Major bugfixes (crashes and assert failures):
11176 - Stop imposing an arbitrary maximum on the number of file descriptors
11177 used for busy servers. Bug reported by Olaf Selke; patch from
11179 - Avoid possible failures when generating a directory with routers
11180 with over-long versions strings, or too many flags set.
11181 - Fix a rare assert error when we're closing one of our threads:
11182 use a mutex to protect the list of logs, so we never write to the
11183 list as it's being freed. Fixes the very rare bug 575, which is
11184 kind of the revenge of bug 222.
11185 - Avoid segfault in the case where a badly behaved v2 versioning
11186 directory sends a signed networkstatus with missing client-versions.
11187 - When we hit an EOF on a log (probably because we're shutting down),
11188 don't try to remove the log from the list: just mark it as
11189 unusable. (Bulletproofs against bug 222.)
11191 o Major bugfixes (code security fixes):
11192 - Detect size overflow in zlib code. Reported by Justin Ferguson and
11194 - Rewrite directory tokenization code to never run off the end of
11195 a string. Fixes bug 455. Patch from croup.
11196 - Be more paranoid about overwriting sensitive memory on free(),
11197 as a defensive programming tactic to ensure forward secrecy.
11199 o Major bugfixes (anonymity fixes):
11200 - Reject requests for reverse-dns lookup of names that are in
11201 a private address space. Patch from lodger.
11202 - Never report that we've used more bandwidth than we're willing to
11203 relay: it leaks how much non-relay traffic we're using. Resolves
11205 - As a client, do not believe any server that tells us that an
11206 address maps to an internal address space.
11207 - Warn about unsafe ControlPort configurations.
11208 - Directory authorities now call routers Fast if their bandwidth is
11209 at least 100KB/s, and consider their bandwidth adequate to be a
11210 Guard if it is at least 250KB/s, no matter the medians. This fix
11211 complements proposal 107.
11212 - Directory authorities now never mark more than 2 servers per IP as
11213 Valid and Running (or 5 on addresses shared by authorities).
11214 Implements proposal 109, by Kevin Bauer and Damon McCoy.
11215 - If we're a relay, avoid picking ourselves as an introduction point,
11216 a rendezvous point, or as the final hop for internal circuits. Bug
11217 reported by taranis and lodger.
11218 - Exit relays that are used as a client can now reach themselves
11219 using the .exit notation, rather than just launching an infinite
11220 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
11221 - Fix a bug where, when we were choosing the 'end stream reason' to
11222 put in our relay end cell that we send to the exit relay, Tor
11223 clients on Windows were sometimes sending the wrong 'reason'. The
11224 anonymity problem is that exit relays may be able to guess whether
11225 the client is running Windows, thus helping partition the anonymity
11226 set. Down the road we should stop sending reasons to exit relays,
11227 or otherwise prevent future versions of this bug.
11228 - Only update guard status (usable / not usable) once we have
11229 enough directory information. This was causing us to discard all our
11230 guards on startup if we hadn't been running for a few weeks. Fixes
11232 - When our directory information has been expired for a while, stop
11233 being willing to build circuits using it. Fixes bug 401.
11235 o Major bugfixes (peace of mind for relay operators)
11236 - Non-exit relays no longer answer "resolve" relay cells, so they
11237 can't be induced to do arbitrary DNS requests. (Tor clients already
11238 avoid using non-exit relays for resolve cells, but now servers
11239 enforce this too.) Fixes bug 619. Patch from lodger.
11240 - When we setconf ClientOnly to 1, close any current OR and Dir
11241 listeners. Reported by mwenge.
11243 o Major bugfixes (other):
11244 - If we only ever used Tor for hidden service lookups or posts, we
11245 would stop building circuits and start refusing connections after
11246 24 hours, since we falsely believed that Tor was dormant. Reported
11248 - Add a new __HashedControlSessionPassword option for controllers
11249 to use for one-off session password hashes that shouldn't get
11250 saved to disk by SAVECONF --- Vidalia users were accumulating a
11251 pile of HashedControlPassword lines in their torrc files, one for
11252 each time they had restarted Tor and then clicked Save. Make Tor
11253 automatically convert "HashedControlPassword" to this new option but
11254 only when it's given on the command line. Partial fix for bug 586.
11255 - Patch from "Andrew S. Lists" to catch when we contact a directory
11256 mirror at IP address X and he says we look like we're coming from
11257 IP address X. Otherwise this would screw up our address detection.
11258 - Reject uploaded descriptors and extrainfo documents if they're
11259 huge. Otherwise we'll cache them all over the network and it'll
11260 clog everything up. Suggested by Aljosha Judmayer.
11261 - When a hidden service was trying to establish an introduction point,
11262 and Tor *did* manage to reuse one of the preemptively built
11263 circuits, it didn't correctly remember which one it used,
11264 so it asked for another one soon after, until there were no
11265 more preemptive circuits, at which point it launched one from
11266 scratch. Bugfix on 0.0.9.x.
11268 o Rate limiting and load balancing improvements:
11269 - When we add data to a write buffer in response to the data on that
11270 write buffer getting low because of a flush, do not consider the
11271 newly added data as a candidate for immediate flushing, but rather
11272 make it wait until the next round of writing. Otherwise, we flush
11273 and refill recursively, and a single greedy TLS connection can
11274 eat all of our bandwidth.
11275 - When counting the number of bytes written on a TLS connection,
11276 look at the BIO actually used for writing to the network, not
11277 at the BIO used (sometimes) to buffer data for the network.
11278 Looking at different BIOs could result in write counts on the
11279 order of ULONG_MAX. Fixes bug 614.
11280 - If we change our MaxAdvertisedBandwidth and then reload torrc,
11281 Tor won't realize it should publish a new relay descriptor. Fixes
11282 bug 688, reported by mfr.
11283 - Avoid using too little bandwidth when our clock skips a few seconds.
11284 - Choose which bridge to use proportional to its advertised bandwidth,
11285 rather than uniformly at random. This should speed up Tor for
11286 bridge users. Also do this for people who set StrictEntryNodes.
11288 o Bootstrapping faster and building circuits more intelligently:
11289 - Fix bug 660 that was preventing us from knowing that we should
11290 preemptively build circuits to handle expected directory requests.
11291 - When we're checking if we have enough dir info for each relay
11292 to begin establishing circuits, make sure that we actually have
11293 the descriptor listed in the consensus, not just any descriptor.
11294 - Correctly notify one-hop connections when a circuit build has
11295 failed. Possible fix for bug 669. Found by lodger.
11296 - Clients now hold circuitless TLS connections open for 1.5 times
11297 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
11298 rebuild a new circuit over them within that timeframe. Previously,
11299 they held them open only for KeepalivePeriod (5 minutes).
11301 o Performance improvements (memory):
11302 - Add OpenBSD malloc code from "phk" as an optional malloc
11303 replacement on Linux: some glibc libraries do very poorly with
11304 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
11305 ./configure to get the replacement malloc code.
11306 - Switch our old ring buffer implementation for one more like that
11307 used by free Unix kernels. The wasted space in a buffer with 1mb
11308 of data will now be more like 8k than 1mb. The new implementation
11309 also avoids realloc();realloc(); patterns that can contribute to
11310 memory fragmentation.
11311 - Change the way that Tor buffers data that it is waiting to write.
11312 Instead of queueing data cells in an enormous ring buffer for each
11313 client->OR or OR->OR connection, we now queue cells on a separate
11314 queue for each circuit. This lets us use less slack memory, and
11315 will eventually let us be smarter about prioritizing different kinds
11317 - Reference-count and share copies of address policy entries; only 5%
11318 of them were actually distinct.
11319 - Tune parameters for cell pool allocation to minimize amount of
11321 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
11322 for every single inactive connection_t. Free items from the
11323 4k/16k-buffer free lists when they haven't been used for a while.
11324 - Make memory debugging information describe more about history
11325 of cell allocation, so we can help reduce our memory use.
11326 - Be even more aggressive about releasing RAM from small
11327 empty buffers. Thanks to our free-list code, this shouldn't be too
11328 performance-intensive.
11329 - Log malloc statistics from mallinfo() on platforms where it exists.
11330 - Use memory pools to allocate cells with better speed and memory
11331 efficiency, especially on platforms where malloc() is inefficient.
11332 - Add a --with-tcmalloc option to the configure script to link
11333 against tcmalloc (if present). Does not yet search for non-system
11336 o Performance improvements (socket management):
11337 - Count the number of open sockets separately from the number of
11338 active connection_t objects. This will let us avoid underusing
11339 our allocated connection limit.
11340 - We no longer use socket pairs to link an edge connection to an
11341 anonymous directory connection or a DirPort test connection.
11342 Instead, we track the link internally and transfer the data
11343 in-process. This saves two sockets per "linked" connection (at the
11344 client and at the server), and avoids the nasty Windows socketpair()
11346 - We were leaking a file descriptor if Tor started with a zero-length
11347 cached-descriptors file. Patch by "freddy77".
11349 o Performance improvements (CPU use):
11350 - Never walk through the list of logs if we know that no log target
11351 is interested in a given message.
11352 - Call routerlist_remove_old_routers() much less often. This should
11353 speed startup, especially on directory caches.
11354 - Base64 decoding was actually showing up on our profile when parsing
11355 the initial descriptor file; switch to an in-process all-at-once
11356 implementation that's about 3.5x times faster than calling out to
11358 - Use a slightly simpler string hashing algorithm (copying Python's
11359 instead of Java's) and optimize our digest hashing algorithm to take
11360 advantage of 64-bit platforms and to remove some possibly-costly
11362 - When implementing AES counter mode, update only the portions of the
11363 counter buffer that need to change, and don't keep separate
11364 network-order and host-order counters on big-endian hosts (where
11365 they are the same).
11366 - Add an in-place version of aes_crypt() so that we can avoid doing a
11367 needless memcpy() call on each cell payload.
11368 - Use Critical Sections rather than Mutexes for synchronizing threads
11369 on win32; Mutexes are heavier-weight, and designed for synchronizing
11372 o Performance improvements (bandwidth use):
11373 - Don't try to launch new descriptor downloads quite so often when we
11374 already have enough directory information to build circuits.
11375 - Version 1 directories are no longer generated in full. Instead,
11376 authorities generate and serve "stub" v1 directories that list
11377 no servers. This will stop Tor versions 0.1.0.x and earlier from
11378 working, but (for security reasons) nobody should be running those
11380 - Avoid going directly to the directory authorities even if you're a
11381 relay, if you haven't found yourself reachable yet or if you've
11382 decided not to advertise your dirport yet. Addresses bug 556.
11383 - If we've gone 12 hours since our last bandwidth check, and we
11384 estimate we have less than 50KB bandwidth capacity but we could
11385 handle more, do another bandwidth test.
11386 - Support "If-Modified-Since" when answering HTTP requests for
11387 directories, running-routers documents, and v2 and v3 networkstatus
11388 documents. (There's no need to support it for router descriptors,
11389 since those are downloaded by descriptor digest.)
11390 - Stop fetching directory info so aggressively if your DirPort is
11391 on but your ORPort is off; stop fetching v2 dir info entirely.
11392 You can override these choices with the new FetchDirInfoEarly
11395 o Changed config option behavior (features):
11396 - Configuration files now accept C-style strings as values. This
11397 helps encode characters not allowed in the current configuration
11398 file format, such as newline or #. Addresses bug 557.
11399 - Add hidden services and DNSPorts to the list of things that make
11400 Tor accept that it has running ports. Change starting Tor with no
11401 ports from a fatal error to a warning; we might change it back if
11402 this turns out to confuse anybody. Fixes bug 579.
11403 - Make PublishServerDescriptor default to 1, so the default doesn't
11404 have to change as we invent new directory protocol versions.
11405 - Allow people to say PreferTunnelledDirConns rather than
11406 PreferTunneledDirConns, for those alternate-spellers out there.
11407 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
11408 accommodate the growing number of servers that use the default
11409 and are reaching it.
11410 - Make it possible to enable HashedControlPassword and
11411 CookieAuthentication at the same time.
11412 - When a TrackHostExits-chosen exit fails too many times in a row,
11413 stop using it. Fixes bug 437.
11415 o Changed config option behavior (bugfixes):
11416 - Do not read the configuration file when we've only been told to
11417 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
11418 based on patch from Sebastian Hahn.
11419 - Actually validate the options passed to AuthDirReject,
11420 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
11421 - Make "ClientOnly 1" config option disable directory ports too.
11422 - Don't stop fetching descriptors when FetchUselessDescriptors is
11423 set, even if we stop asking for circuits. Bug reported by tup
11425 - Servers used to decline to publish their DirPort if their
11426 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
11427 they look only at BandwidthRate and RelayBandwidthRate.
11428 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
11429 minus 1 byte: the actual maximum declared bandwidth.
11430 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
11431 - Make the NodeFamilies config option work. (Reported by
11432 lodger -- it has never actually worked, even though we added it
11434 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
11435 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
11437 o New config options:
11438 - New configuration options AuthDirMaxServersPerAddr and
11439 AuthDirMaxServersperAuthAddr to override default maximum number
11440 of servers allowed on a single IP address. This is important for
11441 running a test network on a single host.
11442 - Three new config options (AlternateDirAuthority,
11443 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
11444 user selectively replace the default directory authorities by type,
11445 rather than the all-or-nothing replacement that DirServer offers.
11446 - New config options AuthDirBadDir and AuthDirListBadDirs for
11447 authorities to mark certain relays as "bad directories" in the
11448 networkstatus documents. Also supports the "!baddir" directive in
11449 the approved-routers file.
11450 - New config option V2AuthoritativeDirectory that all v2 directory
11451 authorities must set. This lets v3 authorities choose not to serve
11452 v2 directory information.
11454 o Minor features (other):
11455 - When we're not serving v2 directory information, there is no reason
11456 to actually keep any around. Remove the obsolete files and directory
11457 on startup if they are very old and we aren't going to serve them.
11458 - When we negotiate a v2 link-layer connection (not yet implemented),
11459 accept RELAY_EARLY cells and turn them into RELAY cells if we've
11460 negotiated a v1 connection for their next step. Initial steps for
11462 - When we have no consensus, check FallbackNetworkstatusFile (defaults
11463 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
11464 we can start out knowing some directory caches. We don't ship with
11465 a fallback consensus by default though, because it was making
11466 bootstrapping take too long while we tried many down relays.
11467 - Authorities send back an X-Descriptor-Not-New header in response to
11468 an accepted-but-discarded descriptor upload. Partially implements
11470 - If we find a cached-routers file that's been sitting around for more
11471 than 28 days unmodified, then most likely it's a leftover from
11472 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
11474 - When we (as a cache) download a descriptor because it was listed
11475 in a consensus, remember when the consensus was supposed to expire,
11476 and don't expire the descriptor until then.
11477 - Optionally (if built with -DEXPORTMALLINFO) export the output
11478 of mallinfo via http, as tor/mallinfo.txt. Only accessible
11480 - Tag every guard node in our state file with the version that
11481 we believe added it, or with our own version if we add it. This way,
11482 if a user temporarily runs an old version of Tor and then switches
11483 back to a new one, she doesn't automatically lose her guards.
11484 - When somebody requests a list of statuses or servers, and we have
11485 none of those, return a 404 rather than an empty 200.
11486 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
11488 - Add an HSAuthorityRecordStats option that hidden service authorities
11489 can use to track statistics of overall hidden service usage without
11490 logging information that would be as useful to an attacker.
11491 - Allow multiple HiddenServicePort directives with the same virtual
11492 port; when they occur, the user is sent round-robin to one
11493 of the target ports chosen at random. Partially fixes bug 393 by
11494 adding limited ad-hoc round-robining.
11495 - Revamp file-writing logic so we don't need to have the entire
11496 contents of a file in memory at once before we write to disk. Tor,
11499 o Minor bugfixes (other):
11500 - Alter the code that tries to recover from unhandled write
11501 errors, to not try to flush onto a socket that's given us
11503 - Directory mirrors no longer include a guess at the client's IP
11504 address if the connection appears to be coming from the same /24
11505 network; it was producing too many wrong guesses.
11506 - If we're trying to flush the last bytes on a connection (for
11507 example, when answering a directory request), reset the
11508 time-to-give-up timeout every time we manage to write something
11510 - Reject router descriptors with out-of-range bandwidthcapacity or
11511 bandwidthburst values.
11512 - If we can't expand our list of entry guards (e.g. because we're
11513 using bridges or we have StrictEntryNodes set), don't mark relays
11514 down when they fail a directory request. Otherwise we're too quick
11515 to mark all our entry points down.
11516 - Authorities no longer send back "400 you're unreachable please fix
11517 it" errors to Tor servers that aren't online all the time. We're
11518 supposed to tolerate these servers now.
11519 - Let directory authorities startup even when they can't generate
11520 a descriptor immediately, e.g. because they don't know their
11522 - Correctly enforce that elements of directory objects do not appear
11523 more often than they are allowed to appear.
11524 - Stop allowing hibernating servers to be "stable" or "fast".
11525 - On Windows, we were preventing other processes from reading
11526 cached-routers while Tor was running. (Reported by janbar)
11527 - Check return values from pthread_mutex functions.
11528 - When opening /dev/null in finish_daemonize(), do not pass the
11529 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
11530 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
11532 o Controller features:
11533 - The GETCONF command now escapes and quotes configuration values
11534 that don't otherwise fit into the torrc file.
11535 - The SETCONF command now handles quoted values correctly.
11536 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
11537 ask about source, timestamp of arrival, purpose, etc. We need
11538 something like this to help Vidalia not do GeoIP lookups on bridge
11540 - Allow multiple HashedControlPassword config lines, to support
11541 multiple controller passwords.
11542 - Accept LF instead of CRLF on controller, since some software has a
11543 hard time generating real Internet newlines.
11544 - Add GETINFO values for the server status events
11545 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
11547 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
11548 GETINFO for Torstat to use until it can switch to using extrainfos.
11549 - New config option CookieAuthFile to choose a new location for the
11550 cookie authentication file, and config option
11551 CookieAuthFileGroupReadable to make it group-readable.
11552 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
11553 match requests to applications. Patch from Robert Hogan.
11554 - Add a RESOLVE command to launch hostname lookups. Original patch
11556 - Add GETINFO status/enough-dir-info to let controllers tell whether
11557 Tor has downloaded sufficient directory information. Patch from Tup.
11558 - You can now use the ControlSocket option to tell Tor to listen for
11559 controller connections on Unix domain sockets on systems that
11560 support them. Patch from Peter Palfrader.
11561 - New "GETINFO address-mappings/*" command to get address mappings
11562 with expiry information. "addr-mappings/*" is now deprecated.
11564 - Add a new config option __DisablePredictedCircuits designed for
11565 use by the controller, when we don't want Tor to build any circuits
11567 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
11568 so we can exit from the middle of the circuit.
11569 - Implement "getinfo status/circuit-established".
11570 - Implement "getinfo status/version/..." so a controller can tell
11571 whether the current version is recommended, and whether any versions
11572 are good, and how many authorities agree. Patch from "shibz".
11573 - Controllers should now specify cache=no or cache=yes when using
11574 the +POSTDESCRIPTOR command.
11575 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
11576 Robert Hogan. Fixes the first part of bug 681.
11577 - When reporting clock skew, and we know that the clock is _at least
11578 as skewed_ as some value, but we don't know the actual value,
11579 report the value as a "minimum skew."
11581 o Controller bugfixes:
11582 - Generate "STATUS_SERVER" events rather than misspelled
11583 "STATUS_SEVER" events. Caught by mwenge.
11584 - Reject controller commands over 1MB in length, so rogue
11585 processes can't run us out of memory.
11586 - Change the behavior of "getinfo status/good-server-descriptor"
11587 so it doesn't return failure when any authority disappears.
11588 - Send NAMESERVER_STATUS messages for a single failed nameserver
11590 - When the DANGEROUS_VERSION controller status event told us we're
11591 running an obsolete version, it used the string "OLD" to describe
11592 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
11593 "OBSOLETE" in both cases.
11594 - Respond to INT and TERM SIGNAL commands before we execute the
11595 signal, in case the signal shuts us down. We had a patch in
11596 0.1.2.1-alpha that tried to do this by queueing the response on
11597 the connection's buffer before shutting down, but that really
11598 isn't the same thing at all. Bug located by Matt Edman.
11599 - Provide DNS expiry times in GMT, not in local time. For backward
11600 compatibility, ADDRMAP events only provide GMT expiry in an extended
11601 field. "GETINFO address-mappings" always does the right thing.
11602 - Use CRLF line endings properly in NS events.
11603 - Make 'getinfo fingerprint' return a 551 error if we're not a
11604 server, so we match what the control spec claims we do. Reported
11606 - Fix a typo in an error message when extendcircuit fails that
11607 caused us to not follow the \r\n-based delimiter protocol. Reported
11609 - When tunneling an encrypted directory connection, and its first
11610 circuit fails, do not leave it unattached and ask the controller
11611 to deal. Fixes the second part of bug 681.
11612 - Treat some 403 responses from directory servers as INFO rather than
11613 WARN-severity events.
11615 o Portability / building / compiling:
11616 - When building with --enable-gcc-warnings, check for whether Apple's
11617 warning "-Wshorten-64-to-32" is available.
11618 - Support compilation to target iPhone; patch from cjacker huang.
11619 To build for iPhone, pass the --enable-iphone option to configure.
11620 - Port Tor to build and run correctly on Windows CE systems, using
11621 the wcecompat library. Contributed by Valerio Lupi.
11622 - Detect non-ASCII platforms (if any still exist) and refuse to
11623 build there: some of our code assumes that 'A' is 65 and so on.
11624 - Clear up some MIPSPro compiler warnings.
11625 - Make autoconf search for libevent, openssl, and zlib consistently.
11626 - Update deprecated macros in configure.in.
11627 - When warning about missing headers, tell the user to let us
11628 know if the compile succeeds anyway, so we can downgrade the
11630 - Include the current subversion revision as part of the version
11631 string: either fetch it directly if we're in an SVN checkout, do
11632 some magic to guess it if we're in an SVK checkout, or use
11633 the last-detected version if we're building from a .tar.gz.
11634 Use this version consistently in log messages.
11635 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
11636 - Read resolv.conf files correctly on platforms where read() returns
11637 partial results on small file reads.
11638 - Build without verbose warnings even on gcc 4.2 and 4.3.
11639 - On Windows, correctly detect errors when listing the contents of
11640 a directory. Fix from lodger.
11641 - Run 'make test' as part of 'make dist', so we stop releasing so
11642 many development snapshots that fail their unit tests.
11643 - Add support to detect Libevent versions in the 1.4.x series
11645 - Add command-line arguments to unit-test executable so that we can
11646 invoke any chosen test from the command line rather than having
11647 to run the whole test suite at once; and so that we can turn on
11648 logging for the unit tests.
11649 - Do not automatically run configure from autogen.sh. This
11650 non-standard behavior tended to annoy people who have built other
11652 - Fix a macro/CPP interaction that was confusing some compilers:
11653 some GCCs don't like #if/#endif pairs inside macro arguments.
11655 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
11656 Fixes bug 704; fix from Steven Murdoch.
11657 - Correctly detect transparent proxy support on Linux hosts that
11658 require in.h to be included before netfilter_ipv4.h. Patch
11661 o Logging improvements:
11662 - When we haven't had any application requests lately, don't bother
11663 logging that we have expired a bunch of descriptors.
11664 - When attempting to open a logfile fails, tell us why.
11665 - Only log guard node status when guard node status has changed.
11666 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
11667 make "INFO" 75% less verbose.
11668 - When SafeLogging is disabled, log addresses along with all TLS
11670 - Report TLS "zero return" case as a "clean close" and "IO error"
11671 as a "close". Stop calling closes "unexpected closes": existing
11672 Tors don't use SSL_close(), so having a connection close without
11673 the TLS shutdown handshake is hardly unexpected.
11674 - When we receive a consensus from the future, warn about skew.
11675 - Make "not enough dir info yet" warnings describe *why* Tor feels
11676 it doesn't have enough directory info yet.
11677 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
11678 consumers. (We already do this on HUP.)
11679 - Give more descriptive well-formedness errors for out-of-range
11680 hidden service descriptor/protocol versions.
11681 - Stop recommending that every server operator send mail to tor-ops.
11682 Resolves bug 597. Bugfix on 0.1.2.x.
11683 - Improve skew reporting: try to give the user a better log message
11684 about how skewed they are, and how much this matters.
11685 - New --quiet command-line option to suppress the default console log.
11686 Good in combination with --hash-password.
11687 - Don't complain that "your server has not managed to confirm that its
11688 ports are reachable" if we haven't been able to build any circuits
11690 - Detect the reason for failing to mmap a descriptor file we just
11691 wrote, and give a more useful log message. Fixes bug 533.
11692 - Always prepend "Bug: " to any log message about a bug.
11693 - When dumping memory usage, list bytes used in buffer memory
11695 - When running with dmalloc, dump more stats on hup and on exit.
11696 - Put a platform string (e.g. "Linux i686") in the startup log
11697 message, so when people paste just their logs, we know if it's
11698 OpenBSD or Windows or what.
11699 - When logging memory usage, break down memory used in buffers by
11701 - When we are reporting the DirServer line we just parsed, we were
11702 logging the second stanza of the key fingerprint, not the first.
11703 - Even though Windows is equally happy with / and \ as path separators,
11704 try to use \ consistently on Windows and / consistently on Unix: it
11705 makes the log messages nicer.
11706 - On OSX, stop warning the user that kqueue support in libevent is
11707 "experimental", since it seems to have worked fine for ages.
11709 o Contributed scripts and tools:
11710 - Update linux-tor-prio.sh script to allow QoS based on the uid of
11711 the Tor process. Patch from Marco Bonetti with tweaks from Mike
11713 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
11714 Unix users an easy way to script their Tor process (e.g. by
11715 adjusting bandwidth based on the time of the day).
11716 - In the exitlist script, only consider the most recently published
11717 server descriptor for each server. Also, when the user requests
11718 a list of servers that _reject_ connections to a given address,
11719 explicitly exclude the IPs that also have servers that accept
11720 connections to that address. Resolves bug 405.
11721 - Include a new contrib/tor-exit-notice.html file that exit relay
11722 operators can put on their website to help reduce abuse queries.
11724 o Newly deprecated features:
11725 - The status/version/num-versioning and status/version/num-concurring
11726 GETINFO controller options are no longer useful in the v3 directory
11727 protocol: treat them as deprecated, and warn when they're used.
11728 - The RedirectExits config option is now deprecated.
11730 o Removed features:
11731 - Drop the old code to choke directory connections when the
11732 corresponding OR connections got full: thanks to the cell queue
11733 feature, OR conns don't get full any more.
11734 - Remove the old "dns worker" server DNS code: it hasn't been default
11735 since 0.1.2.2-alpha, and all the servers are using the new
11737 - Remove the code to generate the oldest (v1) directory format.
11738 - Remove support for the old bw_accounting file: we've been storing
11739 bandwidth accounting information in the state file since
11740 0.1.2.5-alpha. This may result in bandwidth accounting errors
11741 if you try to upgrade from 0.1.1.x or earlier, or if you try to
11742 downgrade to 0.1.1.x or earlier.
11743 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
11744 it, it had no AES, and it hasn't seen any security patches since
11746 - Stop overloading the circuit_t.onionskin field for both "onionskin
11747 from a CREATE cell that we are waiting for a cpuworker to be
11748 assigned" and "onionskin from an EXTEND cell that we are going to
11749 send to an OR as soon as we are connected". Might help with bug 600.
11750 - Remove the tor_strpartition() function: its logic was confused,
11751 and it was only used for one thing that could be implemented far
11753 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
11754 and TorControl.py, as they use the old v0 controller protocol,
11755 and are obsoleted by TorFlow anyway.
11756 - Drop support for v1 rendezvous descriptors, since we never used
11757 them anyway, and the code has probably rotted by now. Based on
11758 patch from Karsten Loesing.
11759 - Stop allowing address masks that do not correspond to bit prefixes.
11760 We have warned about these for a really long time; now it's time
11761 to reject them. (Patch from croup.)
11762 - Remove an optimization in the AES counter-mode code that assumed
11763 that the counter never exceeded 2^68. When the counter can be set
11764 arbitrarily as an IV (as it is by Karsten's new hidden services
11765 code), this assumption no longer holds.
11766 - Disable the SETROUTERPURPOSE controller command: it is now
11770 Changes in version 0.1.2.19 - 2008-01-17
11771 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
11772 exit policy a little bit more conservative so it's safer to run an
11773 exit relay on a home system, and fixes a variety of smaller issues.
11776 - Exit policies now reject connections that are addressed to a
11777 relay's public (external) IP address too, unless
11778 ExitPolicyRejectPrivate is turned off. We do this because too
11779 many relays are running nearby to services that trust them based
11780 on network address.
11783 - When the clock jumps forward a lot, do not allow the bandwidth
11784 buckets to become negative. Fixes bug 544.
11785 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
11786 on every successful resolve. Reported by Mike Perry.
11787 - Purge old entries from the "rephist" database and the hidden
11788 service descriptor database even when DirPort is zero.
11789 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
11790 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
11791 crashing or mis-answering these requests.
11792 - When we decide to send a 503 response to a request for servers, do
11793 not then also send the server descriptors: this defeats the whole
11794 purpose. Fixes bug 539.
11797 - Changing the ExitPolicyRejectPrivate setting should cause us to
11798 rebuild our server descriptor.
11799 - Fix handling of hex nicknames when answering controller requests for
11800 networkstatus by name, or when deciding whether to warn about
11801 unknown routers in a config option. (Patch from mwenge.)
11802 - Fix a couple of hard-to-trigger autoconf problems that could result
11803 in really weird results on platforms whose sys/types.h files define
11804 nonstandard integer types.
11805 - Don't try to create the datadir when running --verify-config or
11806 --hash-password. Resolves bug 540.
11807 - If we were having problems getting a particular descriptor from the
11808 directory caches, and then we learned about a new descriptor for
11809 that router, we weren't resetting our failure count. Reported
11811 - Although we fixed bug 539 (where servers would send HTTP status 503
11812 responses _and_ send a body too), there are still servers out there
11813 that haven't upgraded. Therefore, make clients parse such bodies
11814 when they receive them.
11815 - Run correctly on systems where rlim_t is larger than unsigned long.
11816 This includes some 64-bit systems.
11817 - Run correctly on platforms (like some versions of OS X 10.5) where
11818 the real limit for number of open files is OPEN_FILES, not rlim_max
11819 from getrlimit(RLIMIT_NOFILES).
11820 - Avoid a spurious free on base64 failure.
11821 - Avoid segfaults on certain complex invocations of
11822 router_get_by_hexdigest().
11823 - Fix rare bug on REDIRECTSTREAM control command when called with no
11824 port set: it could erroneously report an error when none had
11828 Changes in version 0.1.2.18 - 2007-10-28
11829 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
11830 hidden service introduction that were causing huge delays, and a big
11831 bug that was causing some servers to disappear from the network status
11832 lists for a few hours each day.
11834 o Major bugfixes (crashes):
11835 - If a connection is shut down abruptly because of something that
11836 happened inside connection_flushed_some(), do not call
11837 connection_finished_flushing(). Should fix bug 451:
11838 "connection_stop_writing: Assertion conn->write_event failed"
11839 Bugfix on 0.1.2.7-alpha.
11840 - Fix possible segfaults in functions called from
11841 rend_process_relay_cell().
11843 o Major bugfixes (hidden services):
11844 - Hidden services were choosing introduction points uniquely by
11845 hexdigest, but when constructing the hidden service descriptor
11846 they merely wrote the (potentially ambiguous) nickname.
11847 - Clients now use the v2 intro format for hidden service
11848 connections: they specify their chosen rendezvous point by identity
11849 digest rather than by (potentially ambiguous) nickname. These
11850 changes could speed up hidden service connections dramatically.
11852 o Major bugfixes (other):
11853 - Stop publishing a new server descriptor just because we get a
11854 HUP signal. This led (in a roundabout way) to some servers getting
11855 dropped from the networkstatus lists for a few hours each day.
11856 - When looking for a circuit to cannibalize, consider family as well
11857 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
11858 circuit cannibalization).
11859 - When a router wasn't listed in a new networkstatus, we were leaving
11860 the flags for that router alone -- meaning it remained Named,
11861 Running, etc -- even though absence from the networkstatus means
11862 that it shouldn't be considered to exist at all anymore. Now we
11863 clear all the flags for routers that fall out of the networkstatus
11864 consensus. Fixes bug 529.
11867 - Don't try to access (or alter) the state file when running
11868 --list-fingerprint or --verify-config or --hash-password. Resolves
11870 - When generating information telling us how to extend to a given
11871 router, do not try to include the nickname if it is
11872 absent. Resolves bug 467.
11873 - Fix a user-triggerable segfault in expand_filename(). (There isn't
11874 a way to trigger this remotely.)
11875 - When sending a status event to the controller telling it that an
11876 OR address is reachable, set the port correctly. (Previously we
11877 were reporting the dir port.)
11878 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
11879 command. Bugfix on 0.1.2.17.
11880 - When loading bandwidth history, do not believe any information in
11881 the future. Fixes bug 434.
11882 - When loading entry guard information, do not believe any information
11884 - When we have our clock set far in the future and generate an
11885 onion key, then re-set our clock to be correct, we should not stop
11886 the onion key from getting rotated.
11887 - On some platforms, accept() can return a broken address. Detect
11888 this more quietly, and deal accordingly. Fixes bug 483.
11889 - It's not actually an error to find a non-pending entry in the DNS
11890 cache when canceling a pending resolve. Don't log unless stuff
11891 is fishy. Resolves bug 463.
11892 - Don't reset trusted dir server list when we set a configuration
11893 option. Patch from Robert Hogan.
11896 Changes in version 0.1.2.17 - 2007-08-30
11897 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
11898 X bundles. Vidalia 0.0.14 makes authentication required for the
11899 ControlPort in the default configuration, which addresses important
11900 security risks. Everybody who uses Vidalia (or another controller)
11903 In addition, this Tor update fixes major load balancing problems with
11904 path selection, which should speed things up a lot once many people
11907 o Major bugfixes (security):
11908 - We removed support for the old (v0) control protocol. It has been
11909 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
11910 become more of a headache than it's worth.
11912 o Major bugfixes (load balancing):
11913 - When choosing nodes for non-guard positions, weight guards
11914 proportionally less, since they already have enough load. Patch
11916 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
11917 will allow fast Tor servers to get more attention.
11918 - When we're upgrading from an old Tor version, forget our current
11919 guards and pick new ones according to the new weightings. These
11920 three load balancing patches could raise effective network capacity
11921 by a factor of four. Thanks to Mike Perry for measurements.
11923 o Major bugfixes (stream expiration):
11924 - Expire not-yet-successful application streams in all cases if
11925 they've been around longer than SocksTimeout. Right now there are
11926 some cases where the stream will live forever, demanding a new
11927 circuit every 15 seconds. Fixes bug 454; reported by lodger.
11929 o Minor features (controller):
11930 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
11931 is valid before any authentication has been received. It tells
11932 a controller what kind of authentication is expected, and what
11933 protocol is spoken. Implements proposal 119.
11935 o Minor bugfixes (performance):
11936 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
11937 greatly speeding up loading cached-routers from disk on startup.
11938 - Disable sentinel-based debugging for buffer code: we squashed all
11939 the bugs that this was supposed to detect a long time ago, and now
11940 its only effect is to change our buffer sizes from nice powers of
11941 two (which platform mallocs tend to like) to values slightly over
11942 powers of two (which make some platform mallocs sad).
11944 o Minor bugfixes (misc):
11945 - If exit bandwidth ever exceeds one third of total bandwidth, then
11946 use the correct formula to weight exit nodes when choosing paths.
11947 Based on patch from Mike Perry.
11948 - Choose perfectly fairly among routers when choosing by bandwidth and
11949 weighting by fraction of bandwidth provided by exits. Previously, we
11950 would choose with only approximate fairness, and correct ourselves
11951 if we ran off the end of the list.
11952 - If we require CookieAuthentication but we fail to write the
11953 cookie file, we would warn but not exit, and end up in a state
11954 where no controller could authenticate. Now we exit.
11955 - If we require CookieAuthentication, stop generating a new cookie
11956 every time we change any piece of our config.
11957 - Refuse to start with certain directory authority keys, and
11958 encourage people using them to stop.
11959 - Terminate multi-line control events properly. Original patch
11961 - Fix a minor memory leak when we fail to find enough suitable
11962 servers to choose a circuit.
11963 - Stop leaking part of the descriptor when we run into a particularly
11964 unparseable piece of it.
11967 Changes in version 0.1.2.16 - 2007-08-01
11968 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
11969 remote attacker in certain situations to rewrite the user's torrc
11970 configuration file. This can completely compromise anonymity of users
11971 in most configurations, including those running the Vidalia bundles,
11972 TorK, etc. Or worse.
11974 o Major security fixes:
11975 - Close immediately after missing authentication on control port;
11976 do not allow multiple authentication attempts.
11979 Changes in version 0.1.2.15 - 2007-07-17
11980 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
11981 problems, fixes compilation on BSD, and fixes a variety of other
11982 bugs. Everybody should upgrade.
11984 o Major bugfixes (compilation):
11985 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
11987 o Major bugfixes (crashes):
11988 - Try even harder not to dereference the first character after
11989 an mmap(). Reported by lodger.
11990 - Fix a crash bug in directory authorities when we re-number the
11991 routerlist while inserting a new router.
11992 - When the cached-routers file is an even multiple of the page size,
11993 don't run off the end and crash. (Fixes bug 455; based on idea
11995 - Fix eventdns.c behavior on Solaris: It is critical to include
11996 orconfig.h _before_ sys/types.h, so that we can get the expected
11997 definition of _FILE_OFFSET_BITS.
11999 o Major bugfixes (security):
12000 - Fix a possible buffer overrun when using BSD natd support. Bug
12002 - When sending destroy cells from a circuit's origin, don't include
12003 the reason for tearing down the circuit. The spec says we didn't,
12004 and now we actually don't. Reported by lodger.
12005 - Keep streamids from different exits on a circuit separate. This
12006 bug may have allowed other routers on a given circuit to inject
12007 cells into streams. Reported by lodger; fixes bug 446.
12008 - If there's a never-before-connected-to guard node in our list,
12009 never choose any guards past it. This way we don't expand our
12010 guard list unless we need to.
12012 o Minor bugfixes (guard nodes):
12013 - Weight guard selection by bandwidth, so that low-bandwidth nodes
12014 don't get overused as guards.
12016 o Minor bugfixes (directory):
12017 - Correctly count the number of authorities that recommend each
12018 version. Previously, we were under-counting by 1.
12019 - Fix a potential crash bug when we load many server descriptors at
12020 once and some of them make others of them obsolete. Fixes bug 458.
12022 o Minor bugfixes (hidden services):
12023 - Stop tearing down the whole circuit when the user asks for a
12024 connection to a port that the hidden service didn't configure.
12027 o Minor bugfixes (misc):
12028 - On Windows, we were preventing other processes from reading
12029 cached-routers while Tor was running. Reported by janbar.
12030 - Fix a possible (but very unlikely) bug in picking routers by
12031 bandwidth. Add a log message to confirm that it is in fact
12032 unlikely. Patch from lodger.
12033 - Backport a couple of memory leak fixes.
12034 - Backport miscellaneous cosmetic bugfixes.
12037 Changes in version 0.1.2.14 - 2007-05-25
12038 Tor 0.1.2.14 changes the addresses of two directory authorities (this
12039 change especially affects those who serve or use hidden services),
12040 and fixes several other crash- and security-related bugs.
12042 o Directory authority changes:
12043 - Two directory authorities (moria1 and moria2) just moved to new
12044 IP addresses. This change will particularly affect those who serve
12045 or use hidden services.
12047 o Major bugfixes (crashes):
12048 - If a directory server runs out of space in the connection table
12049 as it's processing a begin_dir request, it will free the exit stream
12050 but leave it attached to the circuit, leading to unpredictable
12051 behavior. (Reported by seeess, fixes bug 425.)
12052 - Fix a bug in dirserv_remove_invalid() that would cause authorities
12053 to corrupt memory under some really unlikely scenarios.
12054 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
12055 - Avoid segfaults when reading from mmaped descriptor file. (Reported
12058 o Major bugfixes (security):
12059 - When choosing an entry guard for a circuit, avoid using guards
12060 that are in the same family as the chosen exit -- not just guards
12061 that are exactly the chosen exit. (Reported by lodger.)
12063 o Major bugfixes (resource management):
12064 - If a directory authority is down, skip it when deciding where to get
12065 networkstatus objects or descriptors. Otherwise we keep asking
12066 every 10 seconds forever. Fixes bug 384.
12067 - Count it as a failure if we fetch a valid network-status but we
12068 don't want to keep it. Otherwise we'll keep fetching it and keep
12069 not wanting to keep it. Fixes part of bug 422.
12070 - If all of our dirservers have given us bad or no networkstatuses
12071 lately, then stop hammering them once per minute even when we
12072 think they're failed. Fixes another part of bug 422.
12075 - Actually set the purpose correctly for descriptors inserted with
12076 purpose=controller.
12077 - When we have k non-v2 authorities in our DirServer config,
12078 we ignored the last k authorities in the list when updating our
12080 - Correctly back-off from requesting router descriptors that we are
12081 having a hard time downloading.
12082 - Read resolv.conf files correctly on platforms where read() returns
12083 partial results on small file reads.
12084 - Don't rebuild the entire router store every time we get 32K of
12085 routers: rebuild it when the journal gets very large, or when
12086 the gaps in the store get very large.
12089 - When routers publish SVN revisions in their router descriptors,
12090 authorities now include those versions correctly in networkstatus
12092 - Warn when using a version of libevent before 1.3b to run a server on
12093 OSX or BSD: these versions interact badly with userspace threads.
12096 Changes in version 0.1.2.13 - 2007-04-24
12097 This release features some major anonymity fixes, such as safer path
12098 selection; better client performance; faster bootstrapping, better
12099 address detection, and better DNS support for servers; write limiting as
12100 well as read limiting to make servers easier to run; and a huge pile of
12101 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
12103 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
12104 of the Freenode IRC network, remembering his patience and vision for
12105 free speech on the Internet.
12107 o Major features, client performance:
12108 - Weight directory requests by advertised bandwidth. Now we can
12109 let servers enable write limiting but still allow most clients to
12110 succeed at their directory requests. (We still ignore weights when
12111 choosing a directory authority; I hope this is a feature.)
12112 - Stop overloading exit nodes -- avoid choosing them for entry or
12113 middle hops when the total bandwidth available from non-exit nodes
12114 is much higher than the total bandwidth available from exit nodes.
12115 - Rather than waiting a fixed amount of time between retrying
12116 application connections, we wait only 10 seconds for the first,
12117 10 seconds for the second, and 15 seconds for each retry after
12118 that. Hopefully this will improve the expected user experience.
12119 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
12120 to open a stream fails; now we do in more cases. This should
12121 make clients able to find a good exit faster in some cases, since
12122 unhandleable requests will now get an error rather than timing out.
12124 o Major features, client functionality:
12125 - Implement BEGIN_DIR cells, so we can connect to a directory
12126 server via TLS to do encrypted directory requests rather than
12127 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
12128 config options if you like. For now, this feature only works if
12129 you already have a descriptor for the destination dirserver.
12130 - Add support for transparent application connections: this basically
12131 bundles the functionality of trans-proxy-tor into the Tor
12132 mainline. Now hosts with compliant pf/netfilter implementations
12133 can redirect TCP connections straight to Tor without diverting
12134 through SOCKS. (Based on patch from tup.)
12135 - Add support for using natd; this allows FreeBSDs earlier than
12136 5.1.2 to have ipfw send connections through Tor without using
12137 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
12139 o Major features, servers:
12140 - Setting up a dyndns name for your server is now optional: servers
12141 with no hostname or IP address will learn their IP address by
12142 asking the directory authorities. This code only kicks in when you
12143 would normally have exited with a "no address" error. Nothing's
12144 authenticated, so use with care.
12145 - Directory servers now spool server descriptors, v1 directories,
12146 and v2 networkstatus objects to buffers as needed rather than en
12147 masse. They also mmap the cached-routers files. These steps save
12149 - Stop requiring clients to have well-formed certificates, and stop
12150 checking nicknames in certificates. (Clients have certificates so
12151 that they can look like Tor servers, but in the future we might want
12152 to allow them to look like regular TLS clients instead. Nicknames
12153 in certificates serve no purpose other than making our protocol
12154 easier to recognize on the wire.) Implements proposal 106.
12156 o Improvements on DNS support:
12157 - Add "eventdns" asynchronous dns library originally based on code
12158 from Adam Langley. Now we can discard the old rickety dnsworker
12159 concept, and support a wider variety of DNS functions. Allows
12160 multithreaded builds on NetBSD and OpenBSD again.
12161 - Add server-side support for "reverse" DNS lookups (using PTR
12162 records so clients can determine the canonical hostname for a given
12163 IPv4 address). Only supported by servers using eventdns; servers
12164 now announce in their descriptors if they don't support eventdns.
12165 - Workaround for name servers (like Earthlink's) that hijack failing
12166 DNS requests and replace the no-such-server answer with a "helpful"
12167 redirect to an advertising-driven search portal. Also work around
12168 DNS hijackers who "helpfully" decline to hijack known-invalid
12169 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
12170 lets you turn it off.
12171 - Servers now check for the case when common DNS requests are going to
12172 wildcarded addresses (i.e. all getting the same answer), and change
12173 their exit policy to reject *:* if it's happening.
12174 - When asked to resolve a hostname, don't use non-exit servers unless
12175 requested to do so. This allows servers with broken DNS to be
12176 useful to the network.
12177 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
12178 useless IPv6 DNS resolves.
12179 - Specify and implement client-side SOCKS5 interface for reverse DNS
12180 lookups (see doc/socks-extensions.txt). Also cache them.
12181 - When we change nameservers or IP addresses, reset and re-launch
12182 our tests for DNS hijacking.
12184 o Improvements on reachability testing:
12185 - Servers send out a burst of long-range padding cells once they've
12186 established that they're reachable. Spread them over 4 circuits,
12187 so hopefully a few will be fast. This exercises bandwidth and
12188 bootstraps them into the directory more quickly.
12189 - When we find our DirPort to be reachable, publish a new descriptor
12190 so we'll tell the world (reported by pnx).
12191 - Directory authorities now only decide that routers are reachable
12192 if their identity keys are as expected.
12193 - Do DirPort reachability tests less often, since a single test
12194 chews through many circuits before giving up.
12195 - Avoid some false positives during reachability testing: don't try
12196 to test via a server that's on the same /24 network as us.
12197 - Start publishing one minute or so after we find our ORPort
12198 to be reachable. This will help reduce the number of descriptors
12199 we have for ourselves floating around, since it's quite likely
12200 other things (e.g. DirPort) will change during that minute too.
12201 - Routers no longer try to rebuild long-term connections to directory
12202 authorities, and directory authorities no longer try to rebuild
12203 long-term connections to all servers. We still don't hang up
12204 connections in these two cases though -- we need to look at it
12205 more carefully to avoid flapping, and we likely need to wait til
12206 0.1.1.x is obsolete.
12208 o Improvements on rate limiting:
12209 - Enable write limiting as well as read limiting. Now we sacrifice
12210 capacity if we're pushing out lots of directory traffic, rather
12211 than overrunning the user's intended bandwidth limits.
12212 - Include TLS overhead when counting bandwidth usage; previously, we
12213 would count only the bytes sent over TLS, but not the bytes used
12215 - Servers decline directory requests much more aggressively when
12216 they're low on bandwidth. Otherwise they end up queueing more and
12217 more directory responses, which can't be good for latency.
12218 - But never refuse directory requests from local addresses.
12219 - Be willing to read or write on local connections (e.g. controller
12220 connections) even when the global rate limiting buckets are empty.
12221 - Flush local controller connection buffers periodically as we're
12222 writing to them, so we avoid queueing 4+ megabytes of data before
12224 - Revise and clean up the torrc.sample that we ship with; add
12225 a section for BandwidthRate and BandwidthBurst.
12227 o Major features, NT services:
12228 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
12229 command-line flag so that admins can override the default by saying
12230 "tor --service install --user "SomeUser"". This will not affect
12231 existing installed services. Also, warn the user that the service
12232 will look for its configuration file in the service user's
12233 %appdata% directory. (We can't do the "hardwire the user's appdata
12234 directory" trick any more, since we may not have read access to that
12236 - Support running the Tor service with a torrc not in the same
12237 directory as tor.exe and default to using the torrc located in
12238 the %appdata%\Tor\ of the user who installed the service. Patch
12240 - Add an --ignore-missing-torrc command-line option so that we can
12241 get the "use sensible defaults if the configuration file doesn't
12242 exist" behavior even when specifying a torrc location on the
12244 - When stopping an NT service, wait up to 10 sec for it to actually
12245 stop. (Patch from Matt Edman; resolves bug 295.)
12247 o Directory authority improvements:
12248 - Stop letting hibernating or obsolete servers affect uptime and
12250 - Stop listing hibernating servers in the v1 directory.
12251 - Authorities no longer recommend exits as guards if this would shift
12252 too much load to the exit nodes.
12253 - Authorities now specify server versions in networkstatus. This adds
12254 about 2% to the size of compressed networkstatus docs, and allows
12255 clients to tell which servers support BEGIN_DIR and which don't.
12256 The implementation is forward-compatible with a proposed future
12257 protocol version scheme not tied to Tor versions.
12258 - DirServer configuration lines now have an orport= option so
12259 clients can open encrypted tunnels to the authorities without
12260 having downloaded their descriptors yet. Enabled for moria1,
12261 moria2, tor26, and lefkada now in the default configuration.
12262 - Add a BadDirectory flag to network status docs so that authorities
12263 can (eventually) tell clients about caches they believe to be
12264 broken. Not used yet.
12265 - Allow authorities to list nodes as bad exits in their
12266 approved-routers file by fingerprint or by address. If most
12267 authorities set a BadExit flag for a server, clients don't think
12268 of it as a general-purpose exit. Clients only consider authorities
12269 that advertise themselves as listing bad exits.
12270 - Patch from Steve Hildrey: Generate network status correctly on
12271 non-versioning dirservers.
12272 - Have directory authorities allow larger amounts of drift in uptime
12273 without replacing the server descriptor: previously, a server that
12274 restarted every 30 minutes could have 48 "interesting" descriptors
12276 - Reserve the nickname "Unnamed" for routers that can't pick
12277 a hostname: any router can call itself Unnamed; directory
12278 authorities will never allocate Unnamed to any particular router;
12279 clients won't believe that any router is the canonical Unnamed.
12281 o Directory mirrors and clients:
12282 - Discard any v1 directory info that's over 1 month old (for
12283 directories) or over 1 week old (for running-routers lists).
12284 - Clients track responses with status 503 from dirservers. After a
12285 dirserver has given us a 503, we try not to use it until an hour has
12286 gone by, or until we have no dirservers that haven't given us a 503.
12287 - When we get a 503 from a directory, and we're not a server, we no
12288 longer count the failure against the total number of failures
12289 allowed for the object we're trying to download.
12290 - Prepare for servers to publish descriptors less often: never
12291 discard a descriptor simply for being too old until either it is
12292 recommended by no authorities, or until we get a better one for
12293 the same router. Make caches consider retaining old recommended
12294 routers for even longer.
12295 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
12296 headers for content, so that we can work better in the presence of
12297 caching HTTP proxies.
12298 - Stop fetching descriptors if you're not a dir mirror and you
12299 haven't tried to establish any circuits lately. (This currently
12300 causes some dangerous behavior, because when you start up again
12301 you'll use your ancient server descriptors.)
12303 o Major fixes, crashes:
12304 - Stop crashing when the controller asks us to resetconf more than
12305 one config option at once. (Vidalia 0.0.11 does this.)
12306 - Fix a longstanding obscure crash bug that could occur when we run
12307 out of DNS worker processes, if we're not using eventdns. (Resolves
12309 - Fix an assert that could trigger if a controller quickly set then
12310 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
12311 - Avoid crash when telling controller about stream-status and a
12312 stream is detached.
12313 - Avoid sending junk to controllers or segfaulting when a controller
12314 uses EVENT_NEW_DESC with verbose nicknames.
12315 - Stop triggering asserts if the controller tries to extend hidden
12316 service circuits (reported by mwenge).
12317 - If we start a server with ClientOnly 1, then set ClientOnly to 0
12318 and hup, stop triggering an assert based on an empty onion_key.
12319 - Mask out all signals in sub-threads; only the libevent signal
12320 handler should be processing them. This should prevent some crashes
12321 on some machines using pthreads. (Patch from coderman.)
12322 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
12324 o Major fixes, anonymity/security:
12325 - Automatically avoid picking more than one node from the same
12326 /16 network when constructing a circuit. Add an
12327 "EnforceDistinctSubnets" option to let people disable it if they
12328 want to operate private test networks on a single subnet.
12329 - When generating bandwidth history, round down to the nearest
12330 1k. When storing accounting data, round up to the nearest 1k.
12331 - When we're running as a server, remember when we last rotated onion
12332 keys, so that we will rotate keys once they're a week old even if
12333 we never stay up for a week ourselves.
12334 - If a client asked for a server by name, and there's a named server
12335 in our network-status but we don't have its descriptor yet, we
12336 could return an unnamed server instead.
12337 - Reject (most) attempts to use Tor circuits with length one. (If
12338 many people start using Tor as a one-hop proxy, exit nodes become
12339 a more attractive target for compromise.)
12340 - Just because your DirPort is open doesn't mean people should be
12341 able to remotely teach you about hidden service descriptors. Now
12342 only accept rendezvous posts if you've got HSAuthoritativeDir set.
12343 - Fix a potential race condition in the rpm installer. Found by
12345 - Do not log IPs with TLS failures for incoming TLS
12346 connections. (Fixes bug 382.)
12348 o Major fixes, other:
12349 - If our system clock jumps back in time, don't publish a negative
12350 uptime in the descriptor.
12351 - When we start during an accounting interval before it's time to wake
12352 up, remember to wake up at the correct time. (May fix bug 342.)
12353 - Previously, we would cache up to 16 old networkstatus documents
12354 indefinitely, if they came from nontrusted authorities. Now we
12355 discard them if they are more than 10 days old.
12356 - When we have a state file we cannot parse, tell the user and
12357 move it aside. Now we avoid situations where the user starts
12358 Tor in 1904, Tor writes a state file with that timestamp in it,
12359 the user fixes her clock, and Tor refuses to start.
12360 - Publish a new descriptor after we hup/reload. This is important
12361 if our config has changed such that we'll want to start advertising
12362 our DirPort now, etc.
12363 - If we are using an exit enclave and we can't connect, e.g. because
12364 its webserver is misconfigured to not listen on localhost, then
12365 back off and try connecting from somewhere else before we fail.
12367 o New config options or behaviors:
12368 - When EntryNodes are configured, rebuild the guard list to contain,
12369 in order: the EntryNodes that were guards before; the rest of the
12370 EntryNodes; the nodes that were guards before.
12371 - Do not warn when individual nodes in the configuration's EntryNodes,
12372 ExitNodes, etc are down: warn only when all possible nodes
12373 are down. (Fixes bug 348.)
12374 - Put a lower-bound on MaxAdvertisedBandwidth.
12375 - Start using the state file to store bandwidth accounting data:
12376 the bw_accounting file is now obsolete. We'll keep generating it
12377 for a while for people who are still using 0.1.2.4-alpha.
12378 - Try to batch changes to the state file so that we do as few
12379 disk writes as possible while still storing important things in
12381 - The state file and the bw_accounting file get saved less often when
12382 the AvoidDiskWrites config option is set.
12383 - Make PIDFile work on Windows.
12384 - Add internal descriptions for a bunch of configuration options:
12385 accessible via controller interface and in comments in saved
12387 - Reject *:563 (NNTPS) in the default exit policy. We already reject
12388 NNTP by default, so this seems like a sensible addition.
12389 - Clients now reject hostnames with invalid characters. This should
12390 avoid some inadvertent info leaks. Add an option
12391 AllowNonRFC953Hostnames to disable this behavior, in case somebody
12392 is running a private network with hosts called @, !, and #.
12393 - Check for addresses with invalid characters at the exit as well,
12394 and warn less verbosely when they fail. You can override this by
12395 setting ServerDNSAllowNonRFC953Addresses to 1.
12396 - Remove some options that have been deprecated since at least
12397 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
12398 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
12399 to set log options. Mark PathlenCoinWeight as obsolete.
12400 - Stop accepting certain malformed ports in configured exit policies.
12401 - When the user uses bad syntax in the Log config line, stop
12402 suggesting other bad syntax as a replacement.
12403 - Add new config option "ResolvConf" to let the server operator
12404 choose an alternate resolve.conf file when using eventdns.
12405 - If one of our entry guards is on the ExcludeNodes list, or the
12406 directory authorities don't think it's a good guard, treat it as
12407 if it were unlisted: stop using it as a guard, and throw it off
12408 the guards list if it stays that way for a long time.
12409 - Allow directory authorities to be marked separately as authorities
12410 for the v1 directory protocol, the v2 directory protocol, and
12411 as hidden service directories, to make it easier to retire old
12412 authorities. V1 authorities should set "HSAuthoritativeDir 1"
12413 to continue being hidden service authorities too.
12414 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
12415 - Make TrackExitHosts case-insensitive, and fix the behavior of
12416 ".suffix" TrackExitHosts items to avoid matching in the middle of
12418 - New DirPort behavior: if you have your dirport set, you download
12419 descriptors aggressively like a directory mirror, whether or not
12420 your ORPort is set.
12423 - Create a new file ReleaseNotes which was the old ChangeLog. The
12424 new ChangeLog file now includes the notes for all development
12426 - Add a new address-spec.txt document to describe our special-case
12427 addresses: .exit, .onion, and .noconnnect.
12428 - Fork the v1 directory protocol into its own spec document,
12429 and mark dir-spec.txt as the currently correct (v2) spec.
12431 o Packaging, porting, and contrib
12432 - "tor --verify-config" now exits with -1(255) or 0 depending on
12433 whether the config options are bad or good.
12434 - The Debian package now uses --verify-config when (re)starting,
12435 to distinguish configuration errors from other errors.
12436 - Adapt a patch from goodell to let the contrib/exitlist script
12437 take arguments rather than require direct editing.
12438 - Prevent the contrib/exitlist script from printing the same
12439 result more than once.
12440 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
12441 - In the hidden service example in torrc.sample, stop recommending
12442 esoteric and discouraged hidden service options.
12443 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
12444 values before failing, and always enables eventdns.
12445 - Try to detect Windows correctly when cross-compiling.
12446 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
12447 Try to fix this in configure.in by checking for most functions
12448 before we check for libevent.
12449 - Update RPMs to require libevent 1.2.
12450 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
12451 or later. Log when we are doing this, so we can diagnose it when
12452 it fails. (Also, recommend libevent 1.1b for kqueue and
12453 win32 methods; deprecate libevent 1.0b harder; make libevent
12454 recommendation system saner.)
12455 - Build with recent (1.3+) libevents on platforms that do not
12456 define the nonstandard types "u_int8_t" and friends.
12457 - Remove architecture from OS X builds. The official builds are
12458 now universal binaries.
12459 - Run correctly on OS X platforms with case-sensitive filesystems.
12460 - Correctly set maximum connection limit on Cygwin. (This time
12462 - Start compiling on MinGW on Windows (patches from Mike Chiussi
12464 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
12465 - Finally fix the openssl warnings from newer gccs that believe that
12466 ignoring a return value is okay, but casting a return value and
12467 then ignoring it is a sign of madness.
12468 - On architectures where sizeof(int)>4, still clamp declarable
12469 bandwidth to INT32_MAX.
12471 o Minor features, controller:
12472 - Warn the user when an application uses the obsolete binary v0
12473 control protocol. We're planning to remove support for it during
12474 the next development series, so it's good to give people some
12476 - Add STREAM_BW events to report per-entry-stream bandwidth
12477 use. (Patch from Robert Hogan.)
12478 - Rate-limit SIGNEWNYM signals in response to controllers that
12479 impolitely generate them for every single stream. (Patch from
12480 mwenge; closes bug 394.)
12481 - Add a REMAP status to stream events to note that a stream's
12482 address has changed because of a cached address or a MapAddress
12484 - Make REMAP stream events have a SOURCE (cache or exit), and
12485 make them generated in every case where we get a successful
12486 connected or resolved cell.
12487 - Track reasons for OR connection failure; make these reasons
12488 available via the controller interface. (Patch from Mike Perry.)
12489 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
12490 can learn when clients are sending malformed hostnames to Tor.
12491 - Specify and implement some of the controller status events.
12492 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
12493 - Reimplement GETINFO so that info/names stays in sync with the
12495 - Implement "GETINFO fingerprint".
12496 - Implement "SETEVENTS GUARD" so controllers can get updates on
12497 entry guard status as it changes.
12498 - Make all connections to addresses of the form ".noconnect"
12499 immediately get closed. This lets application/controller combos
12500 successfully test whether they're talking to the same Tor by
12501 watching for STREAM events.
12502 - Add a REASON field to CIRC events; for backward compatibility, this
12503 field is sent only to controllers that have enabled the extended
12504 event format. Also, add additional reason codes to explain why
12505 a given circuit has been destroyed or truncated. (Patches from
12507 - Add a REMOTE_REASON field to extended CIRC events to tell the
12508 controller why a remote OR told us to close a circuit.
12509 - Stream events also now have REASON and REMOTE_REASON fields,
12510 working much like those for circuit events.
12511 - There's now a GETINFO ns/... field so that controllers can ask Tor
12512 about the current status of a router.
12513 - A new event type "NS" to inform a controller when our opinion of
12514 a router's status has changed.
12515 - Add a GETINFO events/names and GETINFO features/names so controllers
12516 can tell which events and features are supported.
12517 - A new CLEARDNSCACHE signal to allow controllers to clear the
12518 client-side DNS cache without expiring circuits.
12519 - Fix CIRC controller events so that controllers can learn the
12520 identity digests of non-Named servers used in circuit paths.
12521 - Let controllers ask for more useful identifiers for servers. Instead
12522 of learning identity digests for un-Named servers and nicknames
12523 for Named servers, the new identifiers include digest, nickname,
12524 and indication of Named status. Off by default; see control-spec.txt
12525 for more information.
12526 - Add a "getinfo address" controller command so it can display Tor's
12527 best guess to the user.
12528 - New controller event to alert the controller when our server
12529 descriptor has changed.
12530 - Give more meaningful errors on controller authentication failure.
12531 - Export the default exit policy via the control port, so controllers
12532 don't need to guess what it is / will be later.
12534 o Minor bugfixes, controller:
12535 - When creating a circuit via the controller, send a 'launched'
12536 event when we're done, so we follow the spec better.
12537 - Correct the control spec to match how the code actually responds
12538 to 'getinfo addr-mappings/*'. Reported by daejees.
12539 - The control spec described a GUARDS event, but the code
12540 implemented a GUARD event. Standardize on GUARD, but let people
12541 ask for GUARDS too. Reported by daejees.
12542 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
12543 clear the corresponding on_circuit variable, and remember later
12544 that we don't need to send a redundant CLOSED event. (Resolves part
12546 - Report events where a resolve succeeded or where we got a socks
12547 protocol error correctly, rather than calling both of them
12549 - Change reported stream target addresses to IP consistently when
12550 we finally get the IP from an exit node.
12551 - Send log messages to the controller even if they happen to be very
12553 - Flush ERR-level controller status events just like we currently
12554 flush ERR-level log events, so that a Tor shutdown doesn't prevent
12555 the controller from learning about current events.
12556 - Report the circuit number correctly in STREAM CLOSED events. Bug
12557 reported by Mike Perry.
12558 - Do not report bizarre values for results of accounting GETINFOs
12559 when the last second's write or read exceeds the allotted bandwidth.
12560 - Report "unrecognized key" rather than an empty string when the
12561 controller tries to fetch a networkstatus that doesn't exist.
12562 - When the controller does a "GETINFO network-status", tell it
12563 about even those routers whose descriptors are very old, and use
12564 long nicknames where appropriate.
12565 - Fix handling of verbose nicknames with ORCONN controller events:
12566 make them show up exactly when requested, rather than exactly when
12568 - Controller signals now work on non-Unix platforms that don't define
12569 SIGUSR1 and SIGUSR2 the way we expect.
12570 - Respond to SIGNAL command before we execute the signal, in case
12571 the signal shuts us down. Suggested by Karsten Loesing.
12572 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
12574 o Minor features, code performance:
12575 - Major performance improvement on inserting descriptors: change
12576 algorithm from O(n^2) to O(n).
12577 - Do not rotate onion key immediately after setting it for the first
12579 - Call router_have_min_dir_info half as often. (This is showing up in
12580 some profiles, but not others.)
12581 - When using GCC, make log_debug never get called at all, and its
12582 arguments never get evaluated, when no debug logs are configured.
12583 (This is showing up in some profiles, but not others.)
12584 - Statistics dumped by -USR2 now include a breakdown of public key
12585 operations, for profiling.
12586 - Make the common memory allocation path faster on machines where
12587 malloc(0) returns a pointer.
12588 - Split circuit_t into origin_circuit_t and or_circuit_t, and
12589 split connection_t into edge, or, dir, control, and base structs.
12590 These will save quite a bit of memory on busy servers, and they'll
12591 also help us track down bugs in the code and bugs in the spec.
12592 - Use OpenSSL's AES implementation on platforms where it's faster.
12593 This could save us as much as 10% CPU usage.
12595 o Minor features, descriptors and descriptor handling:
12596 - Avoid duplicate entries on MyFamily line in server descriptor.
12597 - When Tor receives a router descriptor that it asked for, but
12598 no longer wants (because it has received fresh networkstatuses
12599 in the meantime), do not warn the user. Cache the descriptor if
12600 we're a cache; drop it if we aren't.
12601 - Servers no longer ever list themselves in their "family" line,
12602 even if configured to do so. This makes it easier to configure
12603 family lists conveniently.
12605 o Minor fixes, confusing/misleading log messages:
12606 - Display correct results when reporting which versions are
12607 recommended, and how recommended they are. (Resolves bug 383.)
12608 - Inform the server operator when we decide not to advertise a
12609 DirPort due to AccountingMax enabled or a low BandwidthRate.
12610 - Only include function names in log messages for info/debug messages.
12611 For notice/warn/err, the content of the message should be clear on
12612 its own, and printing the function name only confuses users.
12613 - Remove even more protocol-related warnings from Tor server logs,
12614 such as bad TLS handshakes and malformed begin cells.
12615 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
12616 when the IP address is mapped through MapAddress to a hostname.
12617 - Fix misleading log messages: an entry guard that is "unlisted",
12618 as well as not known to be "down" (because we've never heard
12619 of it), is not therefore "up".
12621 o Minor fixes, old/obsolete behavior:
12622 - Start assuming we can use a create_fast cell if we don't know
12623 what version a router is running.
12624 - We no longer look for identity and onion keys in "identity.key" and
12625 "onion.key" -- these were replaced by secret_id_key and
12626 secret_onion_key in 0.0.8pre1.
12627 - We no longer require unrecognized directory entries to be
12629 - Drop compatibility with obsolete Tors that permit create cells
12630 to have the wrong circ_id_type.
12631 - Remove code to special-case "-cvs" ending, since it has not
12632 actually mattered since 0.0.9.
12633 - Don't re-write the fingerprint file every restart, unless it has
12636 o Minor fixes, misc client-side behavior:
12637 - Always remove expired routers and networkstatus docs before checking
12638 whether we have enough information to build circuits. (Fixes
12640 - When computing clock skew from directory HTTP headers, consider what
12641 time it was when we finished asking for the directory, not what
12643 - Make our socks5 handling more robust to broken socks clients:
12644 throw out everything waiting on the buffer in between socks
12645 handshake phases, since they can't possibly (so the theory
12646 goes) have predicted what we plan to respond to them.
12647 - Expire socks connections if they spend too long waiting for the
12648 handshake to finish. Previously we would let them sit around for
12649 days, if the connecting application didn't close them either.
12650 - And if the socks handshake hasn't started, don't send a
12651 "DNS resolve socks failed" handshake reply; just close it.
12652 - If the user asks to use invalid exit nodes, be willing to use
12654 - Track unreachable entry guards correctly: don't conflate
12655 'unreachable by us right now' with 'listed as down by the directory
12656 authorities'. With the old code, if a guard was unreachable by us
12657 but listed as running, it would clog our guard list forever.
12658 - Behave correctly in case we ever have a network with more than
12659 2GB/s total advertised capacity.
12660 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
12661 - Fix a memory leak when we ask for "all" networkstatuses and we
12662 get one we don't recognize.
12665 Changes in version 0.1.1.26 - 2006-12-14
12666 o Security bugfixes:
12667 - Stop sending the HttpProxyAuthenticator string to directory
12668 servers when directory connections are tunnelled through Tor.
12669 - Clients no longer store bandwidth history in the state file.
12670 - Do not log introduction points for hidden services if SafeLogging
12674 - Fix an assert failure when a directory authority sets
12675 AuthDirRejectUnlisted and then receives a descriptor from an
12676 unlisted router (reported by seeess).
12679 Changes in version 0.1.1.25 - 2006-11-04
12681 - When a client asks us to resolve (rather than connect to)
12682 an address, and we have a cached answer, give them the cached
12683 answer. Previously, we would give them no answer at all.
12684 - We were building exactly the wrong circuits when we predict
12685 hidden service requirements, meaning Tor would have to build all
12686 its circuits on demand.
12687 - If none of our live entry guards have a high uptime, but we
12688 require a guard with a high uptime, try adding a new guard before
12689 we give up on the requirement. This patch should make long-lived
12690 connections more stable on average.
12691 - When testing reachability of our DirPort, don't launch new
12692 tests when there's already one in progress -- unreachable
12693 servers were stacking up dozens of testing streams.
12695 o Security bugfixes:
12696 - When the user sends a NEWNYM signal, clear the client-side DNS
12697 cache too. Otherwise we continue to act on previous information.
12700 - Avoid a memory corruption bug when creating a hash table for
12702 - Avoid possibility of controller-triggered crash when misusing
12703 certain commands from a v0 controller on platforms that do not
12704 handle printf("%s",NULL) gracefully.
12705 - Avoid infinite loop on unexpected controller input.
12706 - Don't log spurious warnings when we see a circuit close reason we
12707 don't recognize; it's probably just from a newer version of Tor.
12708 - Add Vidalia to the OS X uninstaller script, so when we uninstall
12709 Tor/Privoxy we also uninstall Vidalia.
12712 Changes in version 0.1.1.24 - 2006-09-29
12714 - Allow really slow clients to not hang up five minutes into their
12715 directory downloads (suggested by Adam J. Richter).
12716 - Fix major performance regression from 0.1.0.x: instead of checking
12717 whether we have enough directory information every time we want to
12718 do something, only check when the directory information has changed.
12719 This should improve client CPU usage by 25-50%.
12720 - Don't crash if, after a server has been running for a while,
12721 it can't resolve its hostname.
12722 - When a client asks us to resolve (not connect to) an address,
12723 and we have a cached answer, give them the cached answer.
12724 Previously, we would give them no answer at all.
12727 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12728 - Don't crash when the controller receives a third argument to an
12729 "extendcircuit" request.
12730 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
12731 response; fix error code when "getinfo dir/status/" fails.
12732 - Fix configure.in to not produce broken configure files with
12733 more recent versions of autoconf. Thanks to Clint for his auto*
12735 - Fix security bug on NetBSD that could allow someone to force
12736 uninitialized RAM to be sent to a server's DNS resolver. This
12737 only affects NetBSD and other platforms that do not bounds-check
12739 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
12740 methods: these are known to be buggy.
12741 - If we're a directory mirror and we ask for "all" network status
12742 documents, we would discard status documents from authorities
12743 we don't recognize.
12746 Changes in version 0.1.1.23 - 2006-07-30
12748 - Fast Tor servers, especially exit nodes, were triggering asserts
12749 due to a bug in handling the list of pending DNS resolves. Some
12750 bugs still remain here; we're hunting them.
12751 - Entry guards could crash clients by sending unexpected input.
12752 - More fixes on reachability testing: if you find yourself reachable,
12753 then don't ever make any client requests (so you stop predicting
12754 circuits), then hup or have your clock jump, then later your IP
12755 changes, you won't think circuits are working, so you won't try to
12756 test reachability, so you won't publish.
12759 - Avoid a crash if the controller does a resetconf firewallports
12760 and then a setconf fascistfirewall=1.
12761 - Avoid an integer underflow when the dir authority decides whether
12762 a router is stable: we might wrongly label it stable, and compute
12763 a slightly wrong median stability, when a descriptor is published
12765 - Fix a place where we might trigger an assert if we can't build our
12766 own server descriptor yet.
12769 Changes in version 0.1.1.22 - 2006-07-05
12771 - Fix a big bug that was causing servers to not find themselves
12772 reachable if they changed IP addresses. Since only 0.1.1.22+
12773 servers can do reachability testing correctly, now we automatically
12774 make sure to test via one of these.
12775 - Fix to allow clients and mirrors to learn directory info from
12776 descriptor downloads that get cut off partway through.
12777 - Directory authorities had a bug in deciding if a newly published
12778 descriptor was novel enough to make everybody want a copy -- a few
12779 servers seem to be publishing new descriptors many times a minute.
12781 - Fix a rare bug that was causing some servers to complain about
12782 "closing wedged cpuworkers" and skip some circuit create requests.
12783 - Make the Exit flag in directory status documents actually work.
12786 Changes in version 0.1.1.21 - 2006-06-10
12787 o Crash and assert fixes from 0.1.1.20:
12788 - Fix a rare crash on Tor servers that have enabled hibernation.
12789 - Fix a seg fault on startup for Tor networks that use only one
12790 directory authority.
12791 - Fix an assert from a race condition that occurs on Tor servers
12792 while exiting, where various threads are trying to log that they're
12793 exiting, and delete the logs, at the same time.
12794 - Make our unit tests pass again on certain obscure platforms.
12797 - Add support for building SUSE RPM packages.
12798 - Speed up initial bootstrapping for clients: if we are making our
12799 first ever connection to any entry guard, then don't mark it down
12801 - When only one Tor server in the network is labelled as a guard,
12802 and we've already picked him, we would cycle endlessly picking him
12803 again, being unhappy about it, etc. Now we specifically exclude
12804 current guards when picking a new guard.
12805 - Servers send create cells more reliably after the TLS connection
12806 is established: we were sometimes forgetting to send half of them
12807 when we had more than one pending.
12808 - If we get a create cell that asks us to extend somewhere, but the
12809 Tor server there doesn't match the expected digest, we now send
12810 a destroy cell back, rather than silently doing nothing.
12811 - Make options->RedirectExit work again.
12812 - Make cookie authentication for the controller work again.
12813 - Stop being picky about unusual characters in the arguments to
12814 mapaddress. It's none of our business.
12815 - Add a new config option "TestVia" that lets you specify preferred
12816 middle hops to use for test circuits. Perhaps this will let me
12817 debug the reachability problems better.
12819 o Log / documentation fixes:
12820 - If we're a server and some peer has a broken TLS certificate, don't
12821 log about it unless ProtocolWarnings is set, i.e., we want to hear
12822 about protocol violations by others.
12823 - Fix spelling of VirtualAddrNetwork in man page.
12824 - Add a better explanation at the top of the autogenerated torrc file
12825 about what happened to our old torrc.
12828 Changes in version 0.1.1.20 - 2006-05-23
12829 o Crash and assert fixes from 0.1.0.17:
12830 - Fix assert bug in close_logs() on exit: when we close and delete
12831 logs, remove them all from the global "logfiles" list.
12832 - Fix an assert error when we're out of space in the connection_list
12833 and we try to post a hidden service descriptor (reported by Peter
12835 - Fix a rare assert error when we've tried all intro points for
12836 a hidden service and we try fetching the service descriptor again:
12837 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
12838 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
12839 out and refuse the setconf if it would fail.
12840 - If you specify a relative torrc path and you set RunAsDaemon in
12841 your torrc, then it chdir()'s to the new directory. If you then
12842 HUP, it tries to load the new torrc location, fails, and exits.
12843 The fix: no longer allow a relative path to torrc when using -f.
12844 - Check for integer overflows in more places, when adding elements
12845 to smartlists. This could possibly prevent a buffer overflow
12846 on malicious huge inputs.
12848 o Security fixes, major:
12849 - When we're printing strings from the network, don't try to print
12850 non-printable characters. Now we're safer against shell escape
12851 sequence exploits, and also against attacks to fool users into
12852 misreading their logs.
12853 - Implement entry guards: automatically choose a handful of entry
12854 nodes and stick with them for all circuits. Only pick new guards
12855 when the ones you have are unsuitable, and if the old guards
12856 become suitable again, switch back. This will increase security
12857 dramatically against certain end-point attacks. The EntryNodes
12858 config option now provides some hints about which entry guards you
12859 want to use most; and StrictEntryNodes means to only use those.
12860 Fixes CVE-2006-0414.
12861 - Implement exit enclaves: if we know an IP address for the
12862 destination, and there's a running Tor server at that address
12863 which allows exit to the destination, then extend the circuit to
12864 that exit first. This provides end-to-end encryption and end-to-end
12865 authentication. Also, if the user wants a .exit address or enclave,
12866 use 4 hops rather than 3, and cannibalize a general circ for it
12868 - Obey our firewall options more faithfully:
12869 . If we can't get to a dirserver directly, try going via Tor.
12870 . Don't ever try to connect (as a client) to a place our
12871 firewall options forbid.
12872 . If we specify a proxy and also firewall options, obey the
12873 firewall options even when we're using the proxy: some proxies
12874 can only proxy to certain destinations.
12875 - Make clients regenerate their keys when their IP address changes.
12876 - For the OS X package's modified privoxy config file, comment
12877 out the "logfile" line so we don't log everything passed
12879 - Our TLS handshakes were generating a single public/private
12880 keypair for the TLS context, rather than making a new one for
12881 each new connection. Oops. (But we were still rotating them
12882 periodically, so it's not so bad.)
12883 - When we were cannibalizing a circuit with a particular exit
12884 node in mind, we weren't checking to see if that exit node was
12885 already present earlier in the circuit. Now we are.
12886 - Require server descriptors to list IPv4 addresses -- hostnames
12887 are no longer allowed. This also fixes potential vulnerabilities
12888 to servers providing hostnames as their address and then
12889 preferentially resolving them so they can partition users.
12890 - Our logic to decide if the OR we connected to was the right guy
12891 was brittle and maybe open to a mitm for invalid routers.
12893 o Security fixes, minor:
12894 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
12895 Ian Goldberg can prove things about our handshake protocol more
12897 - Make directory authorities generate a separate "guard" flag to
12898 mean "would make a good entry guard". Clients now honor the
12899 is_guard flag rather than looking at is_fast or is_stable.
12900 - Try to list MyFamily elements by key, not by nickname, and warn
12901 if we've not heard of a server.
12902 - Start using RAND_bytes rather than RAND_pseudo_bytes from
12903 OpenSSL. Also, reseed our entropy every hour, not just at
12904 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
12905 - Refuse server descriptors where the fingerprint line doesn't match
12906 the included identity key. Tor doesn't care, but other apps (and
12907 humans) might actually be trusting the fingerprint line.
12908 - We used to kill the circuit when we receive a relay command we
12909 don't recognize. Now we just drop that cell.
12910 - Fix a bug found by Lasse Overlier: when we were making internal
12911 circuits (intended to be cannibalized later for rendezvous and
12912 introduction circuits), we were picking them so that they had
12913 useful exit nodes. There was no need for this, and it actually
12914 aids some statistical attacks.
12915 - Start treating internal circuits and exit circuits separately.
12916 It's important to keep them separate because internal circuits
12917 have their last hops picked like middle hops, rather than like
12918 exit hops. So exiting on them will break the user's expectations.
12919 - Fix a possible way to DoS dirservers.
12920 - When the client asked for a rendezvous port that the hidden
12921 service didn't want to provide, we were sending an IP address
12922 back along with the end cell. Fortunately, it was zero. But stop
12925 o Packaging improvements:
12926 - Implement --with-libevent-dir option to ./configure. Improve
12927 search techniques to find libevent, and use those for openssl too.
12928 - Fix a couple of bugs in OpenSSL detection. Deal better when
12929 there are multiple SSLs installed with different versions.
12930 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
12931 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
12933 - Make unit tests (and other invocations that aren't the real Tor)
12934 run without launching listeners, creating subdirectories, and so on.
12935 - The OS X installer was adding a symlink for tor_resolve but
12936 the binary was called tor-resolve (reported by Thomas Hardly).
12937 - Now we can target arch and OS in rpm builds (contributed by
12938 Phobos). Also make the resulting dist-rpm filename match the
12940 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
12941 if you log to syslog and want something other than LOG_DAEMON.
12942 - Fix the torify (tsocks) config file to not use Tor for localhost
12944 - Start shipping socks-extensions.txt, tor-doc-unix.html,
12945 tor-doc-server.html, and stylesheet.css in the tarball.
12946 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
12947 They are useless now.
12948 - Add Peter Palfrader's contributed check-tor script. It lets you
12949 easily check whether a given server (referenced by nickname)
12950 is reachable by you.
12951 - Add BSD-style contributed startup script "rc.subr" from Peter
12954 o Directory improvements -- new directory protocol:
12955 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
12956 - Authorities and caches publish individual descriptors (by
12957 digest, by fingerprint, by "all", and by "tell me yours").
12958 - Clients don't download or use the old directory anymore. Now they
12959 download network-statuses from the directory authorities, and
12960 fetch individual server descriptors as needed from mirrors.
12961 - Clients don't download descriptors of non-running servers.
12962 - Download descriptors by digest, not by fingerprint. Caches try to
12963 download all listed digests from authorities; clients try to
12964 download "best" digests from caches. This avoids partitioning
12965 and isolating attacks better.
12966 - Only upload a new server descriptor when options change, 18
12967 hours have passed, uptime is reset, or bandwidth changes a lot.
12968 - Directory authorities silently throw away new descriptors that
12969 haven't changed much if the timestamps are similar. We do this to
12970 tolerate older Tor servers that upload a new descriptor every 15
12971 minutes. (It seemed like a good idea at the time.)
12972 - Clients choose directory servers from the network status lists,
12973 not from their internal list of router descriptors. Now they can
12974 go to caches directly rather than needing to go to authorities
12975 to bootstrap the first set of descriptors.
12976 - When picking a random directory, prefer non-authorities if any
12978 - Add a new flag to network-status indicating whether the server
12979 can answer v2 directory requests too.
12980 - Directory mirrors now cache up to 16 unrecognized network-status
12981 docs, so new directory authorities will be cached too.
12982 - Stop parsing, storing, or using running-routers output (but
12983 mirrors still cache and serve it).
12984 - Clients consider a threshold of "versioning" directory authorities
12985 before deciding whether to warn the user that he's obsolete.
12986 - Authorities publish separate sorted lists of recommended versions
12987 for clients and for servers.
12988 - Change DirServers config line to note which dirs are v1 authorities.
12989 - Put nicknames on the DirServer line, so we can refer to them
12990 without requiring all our users to memorize their IP addresses.
12991 - Remove option when getting directory cache to see whether they
12992 support running-routers; they all do now. Replace it with one
12993 to see whether caches support v2 stuff.
12994 - Stop listing down or invalid nodes in the v1 directory. This
12995 reduces its bulk by about 1/3, and reduces load on mirrors.
12996 - Mirrors no longer cache the v1 directory as often.
12997 - If we as a directory mirror don't know of any v1 directory
12998 authorities, then don't try to cache any v1 directories.
13000 o Other directory improvements:
13001 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
13002 fifth authoritative directory servers.
13003 - Directory authorities no longer require an open connection from
13004 a server to consider him "reachable". We need this change because
13005 when we add new directory authorities, old servers won't know not
13006 to hang up on them.
13007 - Dir authorities now do their own external reachability testing
13008 of each server, and only list as running the ones they found to
13009 be reachable. We also send back warnings to the server's logs if
13010 it uploads a descriptor that we already believe is unreachable.
13011 - Spread the directory authorities' reachability testing over the
13012 entire testing interval, so we don't try to do 500 TLS's at once
13014 - Make the "stable" router flag in network-status be the median of
13015 the uptimes of running valid servers, and make clients pay
13016 attention to the network-status flags. Thus the cutoff adapts
13017 to the stability of the network as a whole, making IRC, IM, etc
13018 connections more reliable.
13019 - Make the v2 dir's "Fast" flag based on relative capacity, just
13020 like "Stable" is based on median uptime. Name everything in the
13021 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
13022 - Retry directory requests if we fail to get an answer we like
13023 from a given dirserver (we were retrying before, but only if
13024 we fail to connect).
13025 - Return a robots.txt on our dirport to discourage google indexing.
13027 o Controller protocol improvements:
13028 - Revised controller protocol (version 1) that uses ascii rather
13029 than binary: tor/doc/control-spec.txt. Add supporting libraries
13030 in python and java and c# so you can use the controller from your
13031 applications without caring how our protocol works.
13032 - Allow the DEBUG controller event to work again. Mark certain log
13033 entries as "don't tell this to controllers", so we avoid cycles.
13034 - New controller function "getinfo accounting", to ask how
13035 many bytes we've used in this time period.
13036 - Add a "resetconf" command so you can set config options like
13037 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
13038 a config option in the torrc with no value, then it clears it
13039 entirely (rather than setting it to its default).
13040 - Add a "getinfo config-file" to tell us where torrc is. Also
13041 expose guard nodes, config options/names.
13042 - Add a "quit" command (when when using the controller manually).
13043 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
13044 stop using any currently-dirty circuits for new streams, so we
13045 don't link new actions to old actions. This also occurs on HUP
13046 or "signal reload".
13047 - If we would close a stream early (e.g. it asks for a .exit that
13048 we know would refuse it) but the LeaveStreamsUnattached config
13049 option is set by the controller, then don't close it.
13050 - Add a new controller event type "authdir_newdescs" that allows
13051 controllers to get all server descriptors that were uploaded to
13052 a router in its role as directory authority.
13053 - New controller option "getinfo desc/all-recent" to fetch the
13054 latest server descriptor for every router that Tor knows about.
13055 - Fix the controller's "attachstream 0" command to treat conn like
13056 it just connected, doing address remapping, handling .exit and
13057 .onion idioms, and so on. Now we're more uniform in making sure
13058 that the controller hears about new and closing connections.
13059 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
13060 the controller. Also, rotate dns and cpu workers if the controller
13061 changes options that will affect them; and initialize the dns
13062 worker cache tree whether or not we start out as a server.
13063 - Add a new circuit purpose 'controller' to let the controller ask
13064 for a circuit that Tor won't try to use. Extend the "extendcircuit"
13065 controller command to let you specify the purpose if you're starting
13066 a new circuit. Add a new "setcircuitpurpose" controller command to
13067 let you change a circuit's purpose after it's been created.
13068 - Let the controller ask for "getinfo dir/server/foo" so it can ask
13069 directly rather than connecting to the dir port. "getinfo
13070 dir/status/foo" also works, but currently only if your DirPort
13072 - Let the controller tell us about certain router descriptors
13073 that it doesn't want Tor to use in circuits. Implement
13074 "setrouterpurpose" and modify "+postdescriptor" to do this.
13075 - If the controller's *setconf commands fail, collect an error
13076 message in a string and hand it back to the controller -- don't
13077 just tell them to go read their logs.
13079 o Scalability, resource management, and performance:
13080 - Fix a major load balance bug: we were round-robin reading in 16 KB
13081 chunks, and servers with bandwidthrate of 20 KB, while downloading
13082 a 600 KB directory, would starve their other connections. Now we
13083 try to be a bit more fair.
13084 - Be more conservative about whether to advertise our DirPort.
13085 The main change is to not advertise if we're running at capacity
13086 and either a) we could hibernate ever or b) our capacity is low
13087 and we're using a default DirPort.
13088 - We weren't cannibalizing circuits correctly for
13089 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
13090 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
13091 build those from scratch. This should make hidden services faster.
13092 - Predict required circuits better, with an eye toward making hidden
13093 services faster on the service end.
13094 - Compress exit policies even more: look for duplicate lines and
13096 - Generate 18.0.0.0/8 address policy format in descs when we can;
13097 warn when the mask is not reducible to a bit-prefix.
13098 - There used to be two ways to specify your listening ports in a
13099 server descriptor: on the "router" line and with a separate "ports"
13100 line. Remove support for the "ports" line.
13101 - Reduce memory requirements in our structs by changing the order
13102 of fields. Replace balanced trees with hash tables. Inline
13103 bottleneck smartlist functions. Add a "Map from digest to void*"
13104 abstraction so we can do less hex encoding/decoding, and use it
13105 in router_get_by_digest(). Many other CPU and memory improvements.
13106 - Allow tor_gzip_uncompress to extract as much as possible from
13107 truncated compressed data. Try to extract as many
13108 descriptors as possible from truncated http responses (when
13109 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
13110 - Make circ->onionskin a pointer, not a static array. moria2 was using
13111 125000 circuit_t's after it had been up for a few weeks, which
13112 translates to 20+ megs of wasted space.
13113 - The private half of our EDH handshake keys are now chosen out
13114 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
13115 - Stop doing the complex voodoo overkill checking for insecure
13116 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
13117 - Do round-robin writes for TLS of at most 16 kB per write. This
13118 might be more fair on loaded Tor servers.
13119 - Do not use unaligned memory access on alpha, mips, or mipsel.
13120 It *works*, but is very slow, so we treat them as if it doesn't.
13122 o Other bugfixes and improvements:
13123 - Start storing useful information to $DATADIR/state, so we can
13124 remember things across invocations of Tor. Retain unrecognized
13125 lines so we can be forward-compatible, and write a TorVersion line
13126 so we can be backward-compatible.
13127 - If ORPort is set, Address is not explicitly set, and our hostname
13128 resolves to a private IP address, try to use an interface address
13129 if it has a public address. Now Windows machines that think of
13130 themselves as localhost can guess their address.
13131 - Regenerate our local descriptor if it's dirty and we try to use
13132 it locally (e.g. if it changes during reachability detection).
13133 This was causing some Tor servers to keep publishing the same
13134 initial descriptor forever.
13135 - Tor servers with dynamic IP addresses were needing to wait 18
13136 hours before they could start doing reachability testing using
13137 the new IP address and ports. This is because they were using
13138 the internal descriptor to learn what to test, yet they were only
13139 rebuilding the descriptor once they decided they were reachable.
13140 - It turns out we couldn't bootstrap a network since we added
13141 reachability detection in 0.1.0.1-rc. Good thing the Tor network
13142 has never gone down. Add an AssumeReachable config option to let
13143 servers and authorities bootstrap. When we're trying to build a
13144 high-uptime or high-bandwidth circuit but there aren't enough
13145 suitable servers, try being less picky rather than simply failing.
13146 - Newly bootstrapped Tor networks couldn't establish hidden service
13147 circuits until they had nodes with high uptime. Be more tolerant.
13148 - Really busy servers were keeping enough circuits open on stable
13149 connections that they were wrapping around the circuit_id
13150 space. (It's only two bytes.) This exposed a bug where we would
13151 feel free to reuse a circuit_id even if it still exists but has
13152 been marked for close. Try to fix this bug. Some bug remains.
13153 - When we fail to bind or listen on an incoming or outgoing
13154 socket, we now close it before refusing, rather than just
13155 leaking it. (Thanks to Peter Palfrader for finding.)
13156 - Fix a file descriptor leak in start_daemon().
13157 - On Windows, you can't always reopen a port right after you've
13158 closed it. So change retry_listeners() to only close and re-open
13159 ports that have changed.
13160 - Workaround a problem with some http proxies that refuse GET
13161 requests that specify "Content-Length: 0". Reported by Adrian.
13162 - Recover better from TCP connections to Tor servers that are
13163 broken but don't tell you (it happens!); and rotate TLS
13164 connections once a week.
13165 - Fix a scary-looking but apparently harmless bug where circuits
13166 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
13167 servers, and never switch to state CIRCUIT_STATE_OPEN.
13168 - Check for even more Windows version flags when writing the platform
13169 string in server descriptors, and note any we don't recognize.
13170 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
13171 get a better idea of why their circuits failed. Not used yet.
13172 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
13173 We don't use them yet, but maybe one day our DNS resolver will be
13174 able to discover them.
13175 - Let people type "tor --install" as well as "tor -install" when they
13176 want to make it an NT service.
13177 - Looks like we were never delivering deflated (i.e. compressed)
13178 running-routers lists, even when asked. Oops.
13179 - We were leaking some memory every time the client changed IPs.
13180 - Clean up more of the OpenSSL memory when exiting, so we can detect
13181 memory leaks better.
13182 - Never call free() on tor_malloc()d memory. This will help us
13183 use dmalloc to detect memory leaks.
13184 - Some Tor servers process billions of cells per day. These
13185 statistics are now uint64_t's.
13186 - Check [X-]Forwarded-For headers in HTTP requests when generating
13187 log messages. This lets people run dirservers (and caches) behind
13188 Apache but still know which IP addresses are causing warnings.
13189 - Fix minor integer overflow in calculating when we expect to use up
13190 our bandwidth allocation before hibernating.
13191 - Lower the minimum required number of file descriptors to 1000,
13192 so we can have some overhead for Valgrind on Linux, where the
13193 default ulimit -n is 1024.
13194 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
13195 and its existence is confusing some users.
13197 o Config option fixes:
13198 - Add a new config option ExitPolicyRejectPrivate which defaults
13199 to on. Now all exit policies will begin with rejecting private
13200 addresses, unless the server operator explicitly turns it off.
13201 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
13202 - Add new ReachableORAddresses and ReachableDirAddresses options
13203 that understand address policies. FascistFirewall is now a synonym
13204 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
13205 - Start calling it FooListenAddress rather than FooBindAddress,
13206 since few of our users know what it means to bind an address
13208 - If the user gave Tor an odd number of command-line arguments,
13209 we were silently ignoring the last one. Now we complain and fail.
13210 This wins the oldest-bug prize -- this bug has been present since
13211 November 2002, as released in Tor 0.0.0.
13212 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
13213 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
13214 it would silently ignore the 6668.
13215 - If we get a linelist or linelist_s config option from the torrc,
13216 e.g. ExitPolicy, and it has no value, warn and skip rather than
13217 silently resetting it to its default.
13218 - Setconf was appending items to linelists, not clearing them.
13219 - Add MyFamily to torrc.sample in the server section, so operators
13220 will be more likely to learn that it exists.
13221 - Make ContactInfo mandatory for authoritative directory servers.
13222 - MaxConn has been obsolete for a while now. Document the ConnLimit
13223 config option, which is a *minimum* number of file descriptors
13224 that must be available else Tor refuses to start.
13225 - Get rid of IgnoreVersion undocumented config option, and make us
13226 only warn, never exit, when we're running an obsolete version.
13227 - Make MonthlyAccountingStart config option truly obsolete now.
13228 - Correct the man page entry on TrackHostExitsExpire.
13229 - Let directory authorities start even if they don't specify an
13230 Address config option.
13231 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
13232 reflect the updated flags in our v2 dir protocol.
13234 o Config option features:
13235 - Add a new config option FastFirstHopPK (on by default) so clients
13236 do a trivial crypto handshake for their first hop, since TLS has
13237 already taken care of confidentiality and authentication.
13238 - Let the user set ControlListenAddress in the torrc. This can be
13239 dangerous, but there are some cases (like a secured LAN) where it
13241 - New config options to help controllers: FetchServerDescriptors
13242 and FetchHidServDescriptors for whether to fetch server
13243 info and hidserv info or let the controller do it, and
13244 PublishServerDescriptor and PublishHidServDescriptors.
13245 - Also let the controller set the __AllDirActionsPrivate config
13246 option if you want all directory fetches/publishes to happen via
13247 Tor (it assumes your controller bootstraps your circuits).
13248 - Add "HardwareAccel" config option: support for crypto hardware
13249 accelerators via OpenSSL. Off by default, until we find somebody
13250 smart who can test it for us. (It appears to produce seg faults
13251 in at least some cases.)
13252 - New config option "AuthDirRejectUnlisted" for directory authorities
13253 as a panic button: if we get flooded with unusable servers we can
13254 revert to only listing servers in the approved-routers file.
13255 - Directory authorities can now reject/invalidate by key and IP,
13256 with the config options "AuthDirInvalid" and "AuthDirReject", or
13257 by marking a fingerprint as "!reject" or "!invalid" (as its
13258 nickname) in the approved-routers file. This is useful since
13259 currently we automatically list servers as running and usable
13260 even if we know they're jerks.
13261 - Add a new config option TestSocks so people can see whether their
13262 applications are using socks4, socks4a, socks5-with-ip, or
13263 socks5-with-fqdn. This way they don't have to keep mucking
13264 with tcpdump and wondering if something got cached somewhere.
13265 - Add "private:*" as an alias in configuration for policies. Now
13266 you can simplify your exit policy rather than needing to list
13267 every single internal or nonroutable network space.
13268 - Accept "private:*" in routerdesc exit policies; not generated yet
13269 because older Tors do not understand it.
13270 - Add configuration option "V1AuthoritativeDirectory 1" which
13271 moria1, moria2, and tor26 have set.
13272 - Implement an option, VirtualAddrMask, to set which addresses
13273 get handed out in response to mapaddress requests. This works
13274 around a bug in tsocks where 127.0.0.0/8 is never socksified.
13275 - Add a new config option FetchUselessDescriptors, off by default,
13276 for when you plan to run "exitlist" on your client and you want
13277 to know about even the non-running descriptors.
13278 - SocksTimeout: How long do we let a socks connection wait
13279 unattached before we fail it?
13280 - CircuitBuildTimeout: Cull non-open circuits that were born
13281 at least this many seconds ago.
13282 - CircuitIdleTimeout: Cull open clean circuits that were born
13283 at least this many seconds ago.
13284 - New config option SafeSocks to reject all application connections
13285 using unsafe socks protocols. Defaults to off.
13287 o Improved and clearer log messages:
13288 - Reduce clutter in server logs. We're going to try to make
13289 them actually usable now. New config option ProtocolWarnings that
13290 lets you hear about how _other Tors_ are breaking the protocol. Off
13292 - Divide log messages into logging domains. Once we put some sort
13293 of interface on this, it will let people looking at more verbose
13294 log levels specify the topics they want to hear more about.
13295 - Log server fingerprint on startup, so new server operators don't
13296 have to go hunting around their filesystem for it.
13297 - Provide dire warnings to any users who set DirServer manually;
13298 move it out of torrc.sample and into torrc.complete.
13299 - Make the log message less scary when all the dirservers are
13300 temporarily unreachable.
13301 - When tor_socketpair() fails in Windows, give a reasonable
13302 Windows-style errno back.
13303 - Improve tor_gettimeofday() granularity on windows.
13304 - We were printing the number of idle dns workers incorrectly when
13306 - Handle duplicate lines in approved-routers files without warning.
13307 - We were whining about using socks4 or socks5-with-local-lookup
13308 even when it's an IP address in the "virtual" range we designed
13309 exactly for this case.
13310 - Check for named servers when looking them up by nickname;
13311 warn when we're calling a non-named server by its nickname;
13312 don't warn twice about the same name.
13313 - Downgrade the dirserver log messages when whining about
13315 - Correct "your server is reachable" log entries to indicate that
13316 it was self-testing that told us so.
13317 - If we're trying to be a Tor server and running Windows 95/98/ME
13318 as a server, explain that we'll likely crash.
13319 - Provide a more useful warn message when our onion queue gets full:
13320 the CPU is too slow or the exit policy is too liberal.
13321 - Don't warn when we receive a 503 from a dirserver/cache -- this
13322 will pave the way for them being able to refuse if they're busy.
13323 - When we fail to bind a listener, try to provide a more useful
13324 log message: e.g., "Is Tor already running?"
13325 - Only start testing reachability once we've established a
13326 circuit. This will make startup on dir authorities less noisy.
13327 - Don't try to upload hidden service descriptors until we have
13328 established a circuit.
13329 - Tor didn't warn when it failed to open a log file.
13330 - Warn when listening on a public address for socks. We suspect a
13331 lot of people are setting themselves up as open socks proxies,
13332 and they have no idea that jerks on the Internet are using them,
13333 since they simply proxy the traffic into the Tor network.
13334 - Give a useful message when people run Tor as the wrong user,
13335 rather than telling them to start chowning random directories.
13336 - Fix a harmless bug that was causing Tor servers to log
13337 "Got an end because of misc error, but we're not an AP. Closing."
13338 - Fix wrong log message when you add a "HiddenServiceNodes" config
13339 line without any HiddenServiceDir line (reported by Chris Thomas).
13340 - Directory authorities now stop whining so loudly about bad
13341 descriptors that they fetch from other dirservers. So when there's
13342 a log complaint, it's for sure from a freshly uploaded descriptor.
13343 - When logging via syslog, include the pid whenever we provide
13344 a log entry. Suggested by Todd Fries.
13345 - When we're shutting down and we do something like try to post a
13346 server descriptor or rendezvous descriptor, don't complain that
13347 we seem to be unreachable. Of course we are, we're shutting down.
13348 - Change log line for unreachability to explicitly suggest /etc/hosts
13349 as the culprit. Also make it clearer what IP address and ports we're
13350 testing for reachability.
13351 - Put quotes around user-supplied strings when logging so users are
13352 more likely to realize if they add bad characters (like quotes)
13354 - NT service patch from Matt Edman to improve error messages on Win32.
13357 Changes in version 0.1.0.17 - 2006-02-17
13358 o Crash bugfixes on 0.1.0.x:
13359 - When servers with a non-zero DirPort came out of hibernation,
13360 sometimes they would trigger an assert.
13362 o Other important bugfixes:
13363 - On platforms that don't have getrlimit (like Windows), we were
13364 artificially constraining ourselves to a max of 1024
13365 connections. Now just assume that we can handle as many as 15000
13366 connections. Hopefully this won't cause other problems.
13368 o Backported features:
13369 - When we're a server, a client asks for an old-style directory,
13370 and our write bucket is empty, don't give it to him. This way
13371 small servers can continue to serve the directory *sometimes*,
13372 without getting overloaded.
13373 - Whenever you get a 503 in response to a directory fetch, try
13374 once more. This will become important once servers start sending
13375 503's whenever they feel busy.
13376 - Fetch a new directory every 120 minutes, not every 40 minutes.
13377 Now that we have hundreds of thousands of users running the old
13378 directory algorithm, it's starting to hurt a lot.
13379 - Bump up the period for forcing a hidden service descriptor upload
13380 from 20 minutes to 1 hour.
13383 Changes in version 0.1.0.16 - 2006-01-02
13384 o Crash bugfixes on 0.1.0.x:
13385 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
13386 corrupting the heap, losing FDs, or crashing when we need to resize
13387 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
13388 - It turns out sparc64 platforms crash on unaligned memory access
13389 too -- so detect and avoid this.
13390 - Handle truncated compressed data correctly (by detecting it and
13392 - Fix possible-but-unlikely free(NULL) in control.c.
13393 - When we were closing connections, there was a rare case that
13394 stomped on memory, triggering seg faults and asserts.
13395 - Avoid potential infinite recursion when building a descriptor. (We
13396 don't know that it ever happened, but better to fix it anyway.)
13397 - We were neglecting to unlink marked circuits from soon-to-close OR
13398 connections, which caused some rare scribbling on freed memory.
13399 - Fix a memory stomping race bug when closing the joining point of two
13400 rendezvous circuits.
13401 - Fix an assert in time parsing found by Steven Murdoch.
13403 o Other bugfixes on 0.1.0.x:
13404 - When we're doing reachability testing, provide more useful log
13405 messages so the operator knows what to expect.
13406 - Do not check whether DirPort is reachable when we are suppressing
13407 advertising it because of hibernation.
13408 - When building with -static or on Solaris, we sometimes needed -ldl.
13409 - One of the dirservers (tor26) changed its IP address.
13410 - When we're deciding whether a stream has enough circuits around
13411 that can handle it, count the freshly dirty ones and not the ones
13412 that are so dirty they won't be able to handle it.
13413 - When we're expiring old circuits, we had a logic error that caused
13414 us to close new rendezvous circuits rather than old ones.
13415 - Give a more helpful log message when you try to change ORPort via
13416 the controller: you should upgrade Tor if you want that to work.
13417 - We were failing to parse Tor versions that start with "Tor ".
13418 - Tolerate faulty streams better: when a stream fails for reason
13419 exitpolicy, stop assuming that the router is lying about his exit
13420 policy. When a stream fails for reason misc, allow it to retry just
13421 as if it was resolvefailed. When a stream has failed three times,
13422 reset its failure count so we can try again and get all three tries.
13425 Changes in version 0.1.0.15 - 2005-09-23
13426 o Bugfixes on 0.1.0.x:
13427 - Reject ports 465 and 587 (spam targets) in default exit policy.
13428 - Don't crash when we don't have any spare file descriptors and we
13429 try to spawn a dns or cpu worker.
13430 - Get rid of IgnoreVersion undocumented config option, and make us
13431 only warn, never exit, when we're running an obsolete version.
13432 - Don't try to print a null string when your server finds itself to
13433 be unreachable and the Address config option is empty.
13434 - Make the numbers in read-history and write-history into uint64s,
13435 so they don't overflow and publish negatives in the descriptor.
13436 - Fix a minor memory leak in smartlist_string_remove().
13437 - We were only allowing ourselves to upload a server descriptor at
13438 most every 20 minutes, even if it changed earlier than that.
13439 - Clean up log entries that pointed to old URLs.
13442 Changes in version 0.1.0.14 - 2005-08-08
13443 o Bugfixes on 0.1.0.x:
13444 - Fix the other half of the bug with crypto handshakes
13446 - Fix an assert trigger if you send a 'signal term' via the
13447 controller when it's listening for 'event info' messages.
13450 Changes in version 0.1.0.13 - 2005-08-04
13451 o Bugfixes on 0.1.0.x:
13452 - Fix a critical bug in the security of our crypto handshakes.
13453 - Fix a size_t underflow in smartlist_join_strings2() that made
13454 it do bad things when you hand it an empty smartlist.
13455 - Fix Windows installer to ship Tor license (thanks to Aphex for
13456 pointing out this oversight) and put a link to the doc directory
13458 - Explicitly set no-unaligned-access for sparc: it turns out the
13459 new gcc's let you compile broken code, but that doesn't make it
13463 Changes in version 0.1.0.12 - 2005-07-18
13464 o New directory servers:
13465 - tor26 has changed IP address.
13467 o Bugfixes on 0.1.0.x:
13468 - Fix a possible double-free in tor_gzip_uncompress().
13469 - When --disable-threads is set, do not search for or link against
13470 pthreads libraries.
13471 - Don't trigger an assert if an authoritative directory server
13472 claims its dirport is 0.
13473 - Fix bug with removing Tor as an NT service: some people were
13474 getting "The service did not return an error." Thanks to Matt
13478 Changes in version 0.1.0.11 - 2005-06-30
13479 o Bugfixes on 0.1.0.x:
13480 - Fix major security bug: servers were disregarding their
13481 exit policies if clients behaved unexpectedly.
13482 - Make OS X init script check for missing argument, so we don't
13483 confuse users who invoke it incorrectly.
13484 - Fix a seg fault in "tor --hash-password foo".
13485 - The MAPADDRESS control command was broken.
13488 Changes in version 0.1.0.10 - 2005-06-14
13490 - Make NT services work and start on startup on Win32 (based on
13491 patch by Matt Edman). See the FAQ entry for details.
13492 - Make 'platform' string in descriptor more accurate for Win32
13493 servers, so it's not just "unknown platform".
13494 - REUSEADDR on normal platforms means you can rebind to the port
13495 right after somebody else has let it go. But REUSEADDR on Win32
13496 means you can bind to the port _even when somebody else already
13497 has it bound_! So, don't do that on Win32.
13498 - Clean up the log messages when starting on Win32 with no config
13500 - Allow seeding the RNG on Win32 even when you're not running as
13501 Administrator. If seeding the RNG on Win32 fails, quit.
13503 o Assert / crash bugs:
13504 - Refuse relay cells that claim to have a length larger than the
13505 maximum allowed. This prevents a potential attack that could read
13506 arbitrary memory (e.g. keys) from an exit server's process
13508 - If unofficial Tor clients connect and send weird TLS certs, our
13509 Tor server triggers an assert. Stop asserting, and start handling
13510 TLS errors better in other situations too.
13511 - Fix a race condition that can trigger an assert when we have a
13512 pending create cell and an OR connection attempt fails.
13515 - Use pthreads for worker processes rather than forking. This was
13516 forced because when we forked, we ended up wasting a lot of
13517 duplicate ram over time.
13518 - Also switch to foo_r versions of some library calls to allow
13519 reentry and threadsafeness.
13520 - Implement --disable-threads configure option. Disable threads on
13521 netbsd and openbsd by default, because they have no reentrant
13522 resolver functions (!), and on solaris since it has other
13524 - Fix possible bug on threading platforms (e.g. win32) which was
13525 leaking a file descriptor whenever a cpuworker or dnsworker died.
13526 - Fix a minor memory leak when somebody establishes an introduction
13527 point at your Tor server.
13528 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
13530 - Add ./configure --with-dmalloc option, to track memory leaks.
13531 - And try to free all memory on closing, so we can detect what
13534 o Protocol correctness:
13535 - When we've connected to an OR and handshaked but didn't like
13536 the result, we were closing the conn without sending destroy
13537 cells back for pending circuits. Now send those destroys.
13538 - Start sending 'truncated' cells back rather than destroy cells
13539 if the circuit closes in front of you. This means we won't have
13540 to abandon partially built circuits.
13541 - Handle changed router status correctly when dirserver reloads
13542 fingerprint file. We used to be dropping all unverified descriptors
13543 right then. The bug was hidden because we would immediately
13544 fetch a directory from another dirserver, which would include the
13545 descriptors we just dropped.
13546 - Revise tor-spec to add more/better stream end reasons.
13547 - Revise all calls to connection_edge_end to avoid sending 'misc',
13548 and to take errno into account where possible.
13549 - Client now retries when streams end early for 'hibernating' or
13550 'resource limit' reasons, rather than failing them.
13551 - Try to be more zealous about calling connection_edge_end when
13552 things go bad with edge conns in connection.c.
13554 o Robustness improvements:
13555 - Better handling for heterogeneous / unreliable nodes:
13556 - Annotate circuits with whether they aim to contain high uptime
13557 nodes and/or high capacity nodes. When building circuits, choose
13559 - This means that every single node in an intro rend circuit,
13560 not just the last one, will have a minimum uptime.
13561 - New config option LongLivedPorts to indicate application streams
13562 that will want high uptime circuits.
13563 - Servers reset uptime when a dir fetch entirely fails. This
13564 hopefully reflects stability of the server's network connectivity.
13565 - If somebody starts his tor server in Jan 2004 and then fixes his
13566 clock, don't make his published uptime be a year.
13567 - Reset published uptime when we wake up from hibernation.
13568 - Introduce a notion of 'internal' circs, which are chosen without
13569 regard to the exit policy of the last hop. Intro and rendezvous
13570 circs must be internal circs, to avoid leaking information. Resolve
13571 and connect streams can use internal circs if they want.
13572 - New circuit pooling algorithm: keep track of what destination ports
13573 we've used recently (start out assuming we'll want to use 80), and
13574 make sure to have enough circs around to satisfy these ports. Also
13575 make sure to have 2 internal circs around if we've required internal
13576 circs lately (and with high uptime if we've seen that lately too).
13577 - Turn addr_policy_compare from a tristate to a quadstate; this should
13578 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
13579 for google.com" problem.
13580 - When a client asks us for a dir mirror and we don't have one,
13581 launch an attempt to get a fresh one.
13582 - First cut at support for "create-fast" cells. Clients can use
13583 these when extending to their first hop, since the TLS already
13584 provides forward secrecy and authentication. Not enabled on
13587 o Reachability testing.
13588 - Your Tor server will automatically try to see if its ORPort and
13589 DirPort are reachable from the outside, and it won't upload its
13590 descriptor until it decides at least ORPort is reachable (when
13591 DirPort is not yet found reachable, publish it as zero).
13592 - When building testing circs for ORPort testing, use only
13593 high-bandwidth nodes, so fewer circuits fail.
13594 - Notice when our IP changes, and reset stats/uptime/reachability.
13595 - Authdirservers don't do ORPort reachability detection, since
13596 they're in clique mode, so it will be rare to find a server not
13597 already connected to them.
13598 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
13602 - Now we allow two unverified servers with the same nickname
13603 but different keys. But if a nickname is verified, only that
13604 nickname+key are allowed.
13605 - If you're an authdirserver connecting to an address:port,
13606 and it's not the OR you were expecting, forget about that
13607 descriptor. If he *was* the one you were expecting, then forget
13608 about all other descriptors for that address:port.
13609 - Allow servers to publish descriptors from 12 hours in the future.
13610 Corollary: only whine about clock skew from the dirserver if
13611 he's a trusted dirserver (since now even verified servers could
13612 have quite wrong clocks).
13613 - Require servers that use the default dirservers to have public IP
13614 addresses. We have too many servers that are configured with private
13615 IPs and their admins never notice the log entries complaining that
13616 their descriptors are being rejected.
13618 o Efficiency improvements:
13619 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
13620 and /dev/poll), and hopefully work better on Windows too.
13621 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
13622 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
13623 - Find libevent even if it's hiding in /usr/local/ and your
13624 CFLAGS and LDFLAGS don't tell you to look there.
13625 - Be able to link with libevent as a shared library (the default
13626 after 1.0d), even if it's hiding in /usr/local/lib and even
13627 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
13628 assuming you're running gcc. Otherwise fail and give a useful
13630 - Switch to a new buffer management algorithm, which tries to avoid
13631 reallocing and copying quite as much. In first tests it looks like
13632 it uses *more* memory on average, but less cpu.
13633 - Switch our internal buffers implementation to use a ring buffer,
13634 to hopefully improve performance for fast servers a lot.
13635 - Reenable the part of the code that tries to flush as soon as an
13636 OR outbuf has a full TLS record available. Perhaps this will make
13637 OR outbufs not grow as huge except in rare cases, thus saving lots
13638 of CPU time plus memory.
13639 - Improve performance for dirservers: stop re-parsing the whole
13640 directory every time you regenerate it.
13641 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
13642 it much faster to look up a circuit for each relay cell.
13643 - Remove most calls to assert_all_pending_dns_resolves_ok(),
13644 since they're eating our cpu on exit nodes.
13645 - Stop wasting time doing a case insensitive comparison for every
13646 dns name every time we do any lookup. Canonicalize the names to
13647 lowercase when you first see them.
13650 - Handle unavailable hidden services better. Handle slow or busy
13651 hidden services better.
13652 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
13653 circ as necessary, if there are any completed ones lying around
13654 when we try to launch one.
13655 - Make hidden services try to establish a rendezvous for 30 seconds
13656 after fetching the descriptor, rather than for n (where n=3)
13657 attempts to build a circuit.
13658 - Adjust maximum skew and age for rendezvous descriptors: let skew
13659 be 48 hours rather than 90 minutes.
13660 - Reject malformed .onion addresses rather then passing them on as
13661 normal web requests.
13664 - More Tor controller support. See
13665 http://tor.eff.org/doc/control-spec.txt for all the new features,
13666 including signals to emulate unix signals from any platform;
13667 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
13668 closestream; closecircuit; etc.
13669 - Encode hashed controller passwords in hex instead of base64,
13670 to make it easier to write controllers.
13671 - Revise control spec and implementation to allow all log messages to
13672 be sent to controller with their severities intact (suggested by
13673 Matt Edman). Disable debug-level logs while delivering a debug-level
13674 log to the controller, to prevent loop. Update TorControl to handle
13675 new log event types.
13677 o New config options/defaults:
13678 - Begin scrubbing sensitive strings from logs by default. Turn off
13679 the config option SafeLogging if you need to do debugging.
13680 - New exit policy: accept most low-numbered ports, rather than
13681 rejecting most low-numbered ports.
13682 - Put a note in the torrc about abuse potential with the default
13684 - Add support for CONNECTing through https proxies, with "HttpsProxy"
13686 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
13687 based on patch from Adam Langley (basic auth only).
13688 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
13689 the fast servers that have been joining lately. (Clients are now
13690 willing to load balance over up to 2 MB of advertised bandwidth
13692 - New config option MaxAdvertisedBandwidth which lets you advertise
13693 a low bandwidthrate (to not attract as many circuits) while still
13694 allowing a higher bandwidthrate in reality.
13695 - Require BandwidthRate to be at least 20kB/s for servers.
13696 - Add a NoPublish config option, so you can be a server (e.g. for
13697 testing running Tor servers in other Tor networks) without
13698 publishing your descriptor to the primary dirservers.
13699 - Add a new AddressMap config directive to rewrite incoming socks
13700 addresses. This lets you, for example, declare an implicit
13701 required exit node for certain sites.
13702 - Add a new TrackHostExits config directive to trigger addressmaps
13703 for certain incoming socks addresses -- for sites that break when
13704 your exit keeps changing (based on patch from Mike Perry).
13705 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
13706 which describes how often we retry making new circuits if current
13707 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
13708 how long we're willing to make use of an already-dirty circuit.
13709 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
13710 a config option "ShutdownWaitLength" (when using kill -INT on
13712 - Fix an edge case in parsing config options: if they say "--"
13713 on the commandline, it's not a config option (thanks weasel).
13714 - New config option DirAllowPrivateAddresses for authdirservers.
13715 Now by default they refuse router descriptors that have non-IP or
13716 private-IP addresses.
13717 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
13718 smart" default value: low for servers and high for clients.
13719 - Some people were putting "Address " in their torrc, and they had
13720 a buggy resolver that resolved " " to 0.0.0.0. Oops.
13721 - If DataDir is ~/.tor, and that expands to /.tor, then default to
13722 LOCALSTATEDIR/tor instead.
13723 - Implement --verify-config command-line option to check if your torrc
13724 is valid without actually launching Tor.
13726 o Logging improvements:
13727 - When dirservers refuse a server descriptor, we now log its
13728 contactinfo, platform, and the poster's IP address.
13729 - Only warn once per nickname from add_nickname_list_to_smartlist()
13730 per failure, so an entrynode or exitnode choice that's down won't
13732 - When we're connecting to an OR and he's got a different nickname/key
13733 than we were expecting, only complain loudly if we're an OP or a
13734 dirserver. Complaining loudly to the OR admins just confuses them.
13735 - Whine at you if you're a server and you don't set your contactinfo.
13736 - Warn when exit policy implicitly allows local addresses.
13737 - Give a better warning when some other server advertises an
13738 ORPort that is actually an apache running ssl.
13739 - If we get an incredibly skewed timestamp from a dirserver mirror
13740 that isn't a verified OR, don't warn -- it's probably him that's
13742 - When a dirserver causes you to give a warn, mention which dirserver
13744 - Initialize libevent later in the startup process, so the logs are
13745 already established by the time we start logging libevent warns.
13746 - Use correct errno on win32 if libevent fails.
13747 - Check and warn about known-bad/slow libevent versions.
13748 - Stop warning about sigpipes in the logs. We're going to
13749 pretend that getting these occassionally is normal and fine.
13751 o New contrib scripts:
13752 - New experimental script tor/contrib/exitlist: a simple python
13753 script to parse directories and find Tor nodes that exit to listed
13755 - New experimental script tor/contrib/ExerciseServer.py (needs more
13756 work) that uses the controller interface to build circuits and
13757 fetch pages over them. This will help us bootstrap servers that
13758 have lots of capacity but haven't noticed it yet.
13759 - New experimental script tor/contrib/PathDemo.py (needs more work)
13760 that uses the controller interface to let you choose whole paths
13762 "<hostname>.<path,separated by dots>.<length of path>.path"
13763 - New contributed script "privoxy-tor-toggle" to toggle whether
13764 Privoxy uses Tor. Seems to be configured for Debian by default.
13765 - Have torctl.in/tor.sh.in check for location of su binary (needed
13769 - chdir() to your datadirectory at the *end* of the daemonize process,
13770 not the beginning. This was a problem because the first time you
13771 run tor, if your datadir isn't there, and you have runasdaemon set
13772 to 1, it will try to chdir to it before it tries to create it. Oops.
13773 - Fix several double-mark-for-close bugs, e.g. where we were finding
13774 a conn for a cell even if that conn is already marked for close.
13775 - Stop most cases of hanging up on a socks connection without sending
13777 - Fix a bug in the RPM package: set home directory for _tor to
13778 something more reasonable when first installing.
13779 - Stop putting nodename in the Platform string in server descriptors.
13780 It doesn't actually help, and it is confusing/upsetting some people.
13781 - When using preferred entry or exit nodes, ignore whether the
13782 circuit wants uptime or capacity. They asked for the nodes, they
13784 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
13785 artificially capped at 500kB.
13786 - Cache local dns resolves correctly even when they're .exit
13788 - If we're hibernating and we get a SIGINT, exit immediately.
13789 - tor-resolve requests were ignoring .exit if there was a working circuit
13790 they could use instead.
13791 - Pay more attention to the ClientOnly config option.
13792 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
13793 installer screens; and don't put stuff into StartupItems unless
13794 the user asks you to.
13797 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
13798 rather than just rejecting it.
13799 - If our clock jumps forward by 100 seconds or more, assume something
13800 has gone wrong with our network and abandon all not-yet-used circs.
13801 - When an application is using socks5, give him the whole variety of
13802 potential socks5 responses (connect refused, host unreachable, etc),
13803 rather than just "success" or "failure".
13804 - A more sane version numbering system. See
13805 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
13806 - Change version parsing logic: a version is "obsolete" if it is not
13807 recommended and (1) there is a newer recommended version in the
13808 same series, or (2) there are no recommended versions in the same
13809 series, but there are some recommended versions in a newer series.
13810 A version is "new" if it is newer than any recommended version in
13812 - Report HTTP reasons to client when getting a response from directory
13813 servers -- so you can actually know what went wrong.
13814 - Reject odd-looking addresses at the client (e.g. addresses that
13815 contain a colon), rather than having the server drop them because
13817 - Stop publishing socksport in the directory, since it's not
13818 actually meant to be public. For compatibility, publish a 0 there
13820 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
13821 cookies to disk and doesn't log each web request to disk. (Thanks
13822 to Brett Carrington for pointing this out.)
13823 - Add OSX uninstall instructions. An actual uninstall script will
13825 - Add "opt hibernating 1" to server descriptor to make it clearer
13826 whether the server is hibernating.
13829 Changes in version 0.0.9.10 - 2005-06-16
13830 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
13831 - Refuse relay cells that claim to have a length larger than the
13832 maximum allowed. This prevents a potential attack that could read
13833 arbitrary memory (e.g. keys) from an exit server's process
13837 Changes in version 0.0.9.9 - 2005-04-23
13838 o Bugfixes on 0.0.9.x:
13839 - If unofficial Tor clients connect and send weird TLS certs, our
13840 Tor server triggers an assert. This release contains a minimal
13841 backport from the broader fix that we put into 0.1.0.4-rc.
13844 Changes in version 0.0.9.8 - 2005-04-07
13845 o Bugfixes on 0.0.9.x:
13846 - We have a bug that I haven't found yet. Sometimes, very rarely,
13847 cpuworkers get stuck in the 'busy' state, even though the cpuworker
13848 thinks of itself as idle. This meant that no new circuits ever got
13849 established. Here's a workaround to kill any cpuworker that's been
13850 busy for more than 100 seconds.
13853 Changes in version 0.0.9.7 - 2005-04-01
13854 o Bugfixes on 0.0.9.x:
13855 - Fix another race crash bug (thanks to Glenn Fink for reporting).
13856 - Compare identity to identity, not to nickname, when extending to
13857 a router not already in the directory. This was preventing us from
13858 extending to unknown routers. Oops.
13859 - Make sure to create OS X Tor user in <500 range, so we aren't
13860 creating actual system users.
13861 - Note where connection-that-hasn't-sent-end was marked, and fix
13862 a few really loud instances of this harmless bug (it's fixed more
13866 Changes in version 0.0.9.6 - 2005-03-24
13867 o Bugfixes on 0.0.9.x (crashes and asserts):
13868 - Add new end stream reasons to maintainance branch. Fix bug where
13869 reason (8) could trigger an assert. Prevent bug from recurring.
13870 - Apparently win32 stat wants paths to not end with a slash.
13871 - Fix assert triggers in assert_cpath_layer_ok(), where we were
13872 blowing away the circuit that conn->cpath_layer points to, then
13873 checking to see if the circ is well-formed. Backport check to make
13874 sure we dont use the cpath on a closed connection.
13875 - Prevent circuit_resume_edge_reading_helper() from trying to package
13876 inbufs for marked-for-close streams.
13877 - Don't crash on hup if your options->address has become unresolvable.
13878 - Some systems (like OS X) sometimes accept() a connection and tell
13879 you the remote host is 0.0.0.0:0. If this happens, due to some
13880 other mis-features, we get confused; so refuse the conn for now.
13882 o Bugfixes on 0.0.9.x (other):
13883 - Fix harmless but scary "Unrecognized content encoding" warn message.
13884 - Add new stream error reason: TORPROTOCOL reason means "you are not
13885 speaking a version of Tor I understand; say bye-bye to your stream."
13886 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
13887 into the future, now that we are more tolerant of skew. This
13888 resolves a bug where a Tor server would refuse to cache a directory
13889 because all the directories it gets are too far in the future;
13890 yet the Tor server never logs any complaints about clock skew.
13891 - Mac packaging magic: make man pages useable, and do not overwrite
13892 existing torrc files.
13893 - Make OS X log happily to /var/log/tor/tor.log
13896 Changes in version 0.0.9.5 - 2005-02-22
13897 o Bugfixes on 0.0.9.x:
13898 - Fix an assert race at exit nodes when resolve requests fail.
13899 - Stop picking unverified dir mirrors--it only leads to misery.
13900 - Patch from Matt Edman to make NT services work better. Service
13901 support is still not compiled into the executable by default.
13902 - Patch from Dmitri Bely so the Tor service runs better under
13903 the win32 SYSTEM account.
13904 - Make tor-resolve actually work (?) on Win32.
13905 - Fix a sign bug when getrlimit claims to have 4+ billion
13906 file descriptors available.
13907 - Stop refusing to start when bandwidthburst == bandwidthrate.
13908 - When create cells have been on the onion queue more than five
13909 seconds, just send back a destroy and take them off the list.
13912 Changes in version 0.0.9.4 - 2005-02-03
13913 o Bugfixes on 0.0.9:
13914 - Fix an assert bug that took down most of our servers: when
13915 a server claims to have 1 GB of bandwidthburst, don't
13917 - Don't crash as badly if we have spawned the max allowed number
13918 of dnsworkers, or we're out of file descriptors.
13919 - Block more file-sharing ports in the default exit policy.
13920 - MaxConn is now automatically set to the hard limit of max
13921 file descriptors we're allowed (ulimit -n), minus a few for
13923 - Give a clearer message when servers need to raise their
13924 ulimit -n when they start running out of file descriptors.
13925 - SGI Compatibility patches from Jan Schaumann.
13926 - Tolerate a corrupt cached directory better.
13927 - When a dirserver hasn't approved your server, list which one.
13928 - Go into soft hibernation after 95% of the bandwidth is used,
13929 not 99%. This is especially important for daily hibernators who
13930 have a small accounting max. Hopefully it will result in fewer
13931 cut connections when the hard hibernation starts.
13932 - Load-balance better when using servers that claim more than
13933 800kB/s of capacity.
13934 - Make NT services work (experimental, only used if compiled in).
13937 Changes in version 0.0.9.3 - 2005-01-21
13938 o Bugfixes on 0.0.9:
13939 - Backport the cpu use fixes from main branch, so busy servers won't
13940 need as much processor time.
13941 - Work better when we go offline and then come back, or when we
13942 run Tor at boot before the network is up. We do this by
13943 optimistically trying to fetch a new directory whenever an
13944 application request comes in and we think we're offline -- the
13945 human is hopefully a good measure of when the network is back.
13946 - Backport some minimal hidserv bugfixes: keep rend circuits open as
13947 long as you keep using them; actually publish hidserv descriptors
13948 shortly after they change, rather than waiting 20-40 minutes.
13949 - Enable Mac startup script by default.
13950 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
13951 - When you update AllowUnverifiedNodes or FirewallPorts via the
13952 controller's setconf feature, we were always appending, never
13954 - When you update HiddenServiceDir via setconf, it was screwing up
13955 the order of reading the lines, making it fail.
13956 - Do not rewrite a cached directory back to the cache; otherwise we
13957 will think it is recent and not fetch a newer one on startup.
13958 - Workaround for webservers that lie about Content-Encoding: Tor
13959 now tries to autodetect compressed directories and compression
13960 itself. This lets us Proxypass dir fetches through apache.
13963 Changes in version 0.0.9.2 - 2005-01-04
13964 o Bugfixes on 0.0.9 (crashes and asserts):
13965 - Fix an assert on startup when the disk is full and you're logging
13967 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
13968 style address, then we'd crash.
13969 - Fix an assert trigger when the running-routers string we get from
13970 a dirserver is broken.
13971 - Make worker threads start and run on win32. Now win32 servers
13973 - Bandaid (not actually fix, but now it doesn't crash) an assert
13974 where the dns worker dies mysteriously and the main Tor process
13975 doesn't remember anything about the address it was resolving.
13977 o Bugfixes on 0.0.9 (Win32):
13978 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
13979 name out of the warning/assert messages.
13980 - Fix a superficial "unhandled error on read" bug on win32.
13981 - The win32 installer no longer requires a click-through for our
13982 license, since our Free Software license grants rights but does not
13984 - Win32: When connecting to a dirserver fails, try another one
13985 immediately. (This was already working for non-win32 Tors.)
13986 - Stop trying to parse $HOME on win32 when hunting for default
13988 - Make tor-resolve.c work on win32 by calling network_init().
13990 o Bugfixes on 0.0.9 (other):
13991 - Make 0.0.9.x build on Solaris again.
13992 - Due to a fencepost error, we were blowing away the \n when reporting
13993 confvalue items in the controller. So asking for multiple config
13994 values at once couldn't work.
13995 - When listing circuits that are pending on an opening OR connection,
13996 if we're an OR we were listing circuits that *end* at us as
13997 being pending on every listener, dns/cpu worker, etc. Stop that.
13998 - Dirservers were failing to create 'running-routers' or 'directory'
13999 strings if we had more than some threshold of routers. Fix them so
14000 they can handle any number of routers.
14001 - Fix a superficial "Duplicate mark for close" bug.
14002 - Stop checking for clock skew for OR connections, even for servers.
14003 - Fix a fencepost error that was chopping off the last letter of any
14004 nickname that is the maximum allowed nickname length.
14005 - Update URLs in log messages so they point to the new website.
14006 - Fix a potential problem in mangling server private keys while
14007 writing to disk (not triggered yet, as far as we know).
14008 - Include the licenses for other free software we include in Tor,
14009 now that we're shipping binary distributions more regularly.
14012 Changes in version 0.0.9.1 - 2004-12-15
14013 o Bugfixes on 0.0.9:
14014 - Make hibernation actually work.
14015 - Make HashedControlPassword config option work.
14016 - When we're reporting event circuit status to a controller,
14017 don't use the stream status code.
14020 Changes in version 0.0.9 - 2004-12-12
14021 o Bugfixes on 0.0.8.1 (Crashes and asserts):
14022 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
14023 write() call will fail and we handle it there.
14024 - When we run out of disk space, or other log writing error, don't
14025 crash. Just stop logging to that log and continue.
14026 - Fix isspace() and friends so they still make Solaris happy
14027 but also so they don't trigger asserts on win32.
14028 - Fix assert failure on malformed socks4a requests.
14029 - Fix an assert bug where a hidden service provider would fail if
14030 the first hop of his rendezvous circuit was down.
14031 - Better handling of size_t vs int, so we're more robust on 64
14034 o Bugfixes on 0.0.8.1 (Win32):
14035 - Make windows sockets actually non-blocking (oops), and handle
14036 win32 socket errors better.
14037 - Fix parse_iso_time on platforms without strptime (eg win32).
14038 - win32: when being multithreaded, leave parent fdarray open.
14039 - Better handling of winsock includes on non-MSV win32 compilers.
14040 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
14042 - Make unit tests work on win32.
14044 o Bugfixes on 0.0.8.1 (Path selection and streams):
14045 - Calculate timeout for waiting for a connected cell from the time
14046 we sent the begin cell, not from the time the stream started. If
14047 it took a long time to establish the circuit, we would time out
14048 right after sending the begin cell.
14049 - Fix router_compare_addr_to_addr_policy: it was not treating a port
14050 of * as always matching, so we were picking reject *:* nodes as
14051 exit nodes too. Oops.
14052 - When read() failed on a stream, we would close it without sending
14053 back an end. So 'connection refused' would simply be ignored and
14054 the user would get no response.
14055 - Stop a sigpipe: when an 'end' cell races with eof from the app,
14056 we shouldn't hold-open-until-flush if the eof arrived first.
14057 - Let resolve conns retry/expire also, rather than sticking around
14059 - Fix more dns related bugs: send back resolve_failed and end cells
14060 more reliably when the resolve fails, rather than closing the
14061 circuit and then trying to send the cell. Also attach dummy resolve
14062 connections to a circuit *before* calling dns_resolve(), to fix
14063 a bug where cached answers would never be sent in RESOLVED cells.
14065 o Bugfixes on 0.0.8.1 (Circuits):
14066 - Finally fix a bug that's been plaguing us for a year:
14067 With high load, circuit package window was reaching 0. Whenever
14068 we got a circuit-level sendme, we were reading a lot on each
14069 socket, but only writing out a bit. So we would eventually reach
14070 eof. This would be noticed and acted on even when there were still
14071 bytes sitting in the inbuf.
14072 - Use identity comparison, not nickname comparison, to choose which
14073 half of circuit-ID-space each side gets to use. This is needed
14074 because sometimes we think of a router as a nickname, and sometimes
14075 as a hex ID, and we can't predict what the other side will do.
14077 o Bugfixes on 0.0.8.1 (Other):
14078 - Fix a whole slew of memory leaks.
14079 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
14080 - If we are using select, make sure we stay within FD_SETSIZE.
14081 - When poll() is interrupted, we shouldn't believe the revents values.
14082 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
14083 and smartlist_len, which are two major profiling offenders.
14084 - If do_hup fails, actually notice.
14085 - Flush the log file descriptor after we print "Tor opening log file",
14086 so we don't see those messages days later.
14087 - Hidden service operators now correctly handle version 1 style
14088 INTRODUCE1 cells (nobody generates them still, so not a critical
14090 - Handle more errnos from accept() without closing the listener.
14091 Some OpenBSD machines were closing their listeners because
14092 they ran out of file descriptors.
14093 - Some people had wrapped their tor client/server in a script
14094 that would restart it whenever it died. This did not play well
14095 with our "shut down if your version is obsolete" code. Now people
14096 don't fetch a new directory if their local cached version is
14098 - Make our autogen.sh work on ksh as well as bash.
14099 - Better torrc example lines for dirbindaddress and orbindaddress.
14100 - Improved bounds checking on parsed ints (e.g. config options and
14101 the ones we find in directories.)
14102 - Stop using separate defaults for no-config-file and
14103 empty-config-file. Now you have to explicitly turn off SocksPort,
14104 if you don't want it open.
14105 - We were starting to daemonize before we opened our logs, so if
14106 there were any problems opening logs, we would complain to stderr,
14107 which wouldn't work, and then mysteriously exit.
14108 - If a verified OR connects to us before he's uploaded his descriptor,
14109 or we verify him and hup but he still has the original TLS
14110 connection, then conn->nickname is still set like he's unverified.
14112 o Code security improvements, inspired by Ilja:
14113 - tor_snprintf wrapper over snprintf with consistent (though not C99)
14115 - Replace sprintf with tor_snprintf. (I think they were all safe, but
14117 - Replace strcpy/strncpy with strlcpy in more places.
14118 - Avoid strcat; use tor_snprintf or strlcat instead.
14120 o Features (circuits and streams):
14121 - New circuit building strategy: keep a list of ports that we've
14122 used in the past 6 hours, and always try to have 2 circuits open
14123 or on the way that will handle each such port. Seed us with port
14124 80 so web users won't complain that Tor is "slow to start up".
14125 - Make kill -USR1 dump more useful stats about circuits.
14126 - When warning about retrying or giving up, print the address, so
14127 the user knows which one it's talking about.
14128 - If you haven't used a clean circuit in an hour, throw it away,
14129 just to be on the safe side. (This means after 6 hours a totally
14130 unused Tor client will have no circuits open.)
14131 - Support "foo.nickname.exit" addresses, to let Alice request the
14132 address "foo" as viewed by exit node "nickname". Based on a patch
14133 from Geoff Goodell.
14134 - If your requested entry or exit node has advertised bandwidth 0,
14136 - Be more greedy about filling up relay cells -- we try reading again
14137 once we've processed the stuff we read, in case enough has arrived
14138 to fill the last cell completely.
14139 - Refuse application socks connections to port 0.
14140 - Use only 0.0.9pre1 and later servers for resolve cells.
14142 o Features (bandwidth):
14143 - Hibernation: New config option "AccountingMax" lets you
14144 set how many bytes per month (in each direction) you want to
14145 allow your server to consume. Rather than spreading those
14146 bytes out evenly over the month, we instead hibernate for some
14147 of the month and pop up at a deterministic time, work until
14148 the bytes are consumed, then hibernate again. Config option
14149 "MonthlyAccountingStart" lets you specify which day of the month
14150 your billing cycle starts on.
14151 - Implement weekly/monthly/daily accounting: now you specify your
14152 hibernation properties by
14153 AccountingMax N bytes|KB|MB|GB|TB
14154 AccountingStart day|week|month [day] HH:MM
14155 Defaults to "month 1 0:00".
14156 - Let bandwidth and interval config options be specified as 5 bytes,
14157 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
14159 o Features (directories):
14160 - New "router-status" line in directory, to better bind each verified
14161 nickname to its identity key.
14162 - Clients can ask dirservers for /dir.z to get a compressed version
14163 of the directory. Only works for servers running 0.0.9, of course.
14164 - Make clients cache directories and use them to seed their router
14165 lists at startup. This means clients have a datadir again.
14166 - Respond to content-encoding headers by trying to uncompress as
14168 - Clients and servers now fetch running-routers; cache
14169 running-routers; compress running-routers; serve compressed
14171 - Make moria2 advertise a dirport of 80, so people behind firewalls
14172 will be able to get a directory.
14173 - Http proxy support
14174 - Dirservers translate requests for http://%s:%d/x to /x
14175 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
14176 be routed through this host.
14177 - Clients ask for /tor/x rather than /x for new enough dirservers.
14178 This way we can one day coexist peacefully with apache.
14179 - Clients specify a "Host: %s%d" http header, to be compatible
14180 with more proxies, and so running squid on an exit node can work.
14181 - Protect dirservers from overzealous descriptor uploading -- wait
14182 10 seconds after directory gets dirty, before regenerating.
14184 o Features (packages and install):
14185 - Add NSI installer contributed by J Doe.
14186 - Apply NT service patch from Osamu Fujino. Still needs more work.
14187 - Commit VC6 and VC7 workspace/project files.
14188 - Commit a tor.spec for making RPM files, with help from jbash.
14189 - Add contrib/torctl.in contributed by Glenn Fink.
14190 - Make expand_filename handle ~ and ~username.
14191 - Use autoconf to enable largefile support where necessary. Use
14192 ftello where available, since ftell can fail at 2GB.
14193 - Ship src/win32/ in the tarball, so people can use it to build.
14194 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
14197 o Features (ui controller):
14198 - Control interface: a separate program can now talk to your
14199 client/server over a socket, and get/set config options, receive
14200 notifications of circuits and streams starting/finishing/dying,
14201 bandwidth used, etc. The next step is to get some GUIs working.
14202 Let us know if you want to help out. See doc/control-spec.txt .
14203 - Ship a contrib/tor-control.py as an example script to interact
14204 with the control port.
14205 - "tor --hash-password zzyxz" will output a salted password for
14206 use in authenticating to the control interface.
14207 - Implement the control-spec's SAVECONF command, to write your
14208 configuration to torrc.
14209 - Get cookie authentication for the controller closer to working.
14210 - When set_conf changes our server descriptor, upload a new copy.
14211 But don't upload it too often if there are frequent changes.
14213 o Features (config and command-line):
14214 - Deprecate unofficial config option abbreviations, and abbreviations
14215 not on the command line.
14216 - Configuration infrastructure support for warning on obsolete
14218 - Give a slightly more useful output for "tor -h".
14219 - Break DirFetchPostPeriod into:
14220 - DirFetchPeriod for fetching full directory,
14221 - StatusFetchPeriod for fetching running-routers,
14222 - DirPostPeriod for posting server descriptor,
14223 - RendPostPeriod for posting hidden service descriptors.
14224 - New log format in config:
14225 "Log minsev[-maxsev] stdout|stderr|syslog" or
14226 "Log minsev[-maxsev] file /var/foo"
14227 - DirPolicy config option, to let people reject incoming addresses
14228 from their dirserver.
14229 - "tor --list-fingerprint" will list your identity key fingerprint
14231 - Make tor --version --version dump the cvs Id of every file.
14232 - New 'MyFamily nick1,...' config option for a server to
14233 specify other servers that shouldn't be used in the same circuit
14234 with it. Only believed if nick1 also specifies us.
14235 - New 'NodeFamily nick1,nick2,...' config option for a client to
14236 specify nodes that it doesn't want to use in the same circuit.
14237 - New 'Redirectexit pattern address:port' config option for a
14238 server to redirect exit connections, e.g. to a local squid.
14239 - Add "pass" target for RedirectExit, to make it easier to break
14240 out of a sequence of RedirectExit rules.
14241 - Make the dirservers file obsolete.
14242 - Include a dir-signing-key token in directories to tell the
14243 parsing entity which key is being used to sign.
14244 - Remove the built-in bulky default dirservers string.
14245 - New config option "Dirserver %s:%d [fingerprint]", which can be
14246 repeated as many times as needed. If no dirservers specified,
14247 default to moria1,moria2,tor26.
14248 - Make 'Routerfile' config option obsolete.
14249 - Discourage people from setting their dirfetchpostperiod more often
14250 than once per minute.
14252 o Features (other):
14253 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
14254 get back to normal.)
14255 - Accept *:706 (silc) in default exit policy.
14256 - Implement new versioning format for post 0.1.
14257 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
14258 log more informatively.
14259 - Check clock skew for verified servers, but allow unverified
14260 servers and clients to have any clock skew.
14261 - Make sure the hidden service descriptors are at a random offset
14262 from each other, to hinder linkability.
14263 - Clients now generate a TLS cert too, in preparation for having
14264 them act more like real nodes.
14265 - Add a pure-C tor-resolve implementation.
14266 - Use getrlimit and friends to ensure we can reach MaxConn (currently
14267 1024) file descriptors.
14268 - Raise the max dns workers from 50 to 100.
14271 Changes in version 0.0.8.1 - 2004-10-13
14273 - Fix a seg fault that can be triggered remotely for Tor
14274 clients/servers with an open dirport.
14275 - Fix a rare assert trigger, where routerinfos for entries in
14276 our cpath would expire while we're building the path.
14277 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14278 - Fix a rare seg fault for people running hidden services on
14279 intermittent connections.
14280 - Fix a bug in parsing opt keywords with objects.
14281 - Fix a stale pointer assert bug when a stream detaches and
14283 - Fix a string format vulnerability (probably not exploitable)
14284 in reporting stats locally.
14285 - Fix an assert trigger: sometimes launching circuits can fail
14286 immediately, e.g. because too many circuits have failed recently.
14287 - Fix a compile warning on 64 bit platforms.
14290 Changes in version 0.0.8 - 2004-08-25
14292 - Made our unit tests compile again on OpenBSD 3.5, and tor
14293 itself compile again on OpenBSD on a sparc64.
14294 - We were neglecting milliseconds when logging on win32, so
14295 everything appeared to happen at the beginning of each second.
14296 - Check directory signature _before_ you decide whether you're
14297 you're running an obsolete version and should exit.
14298 - Check directory signature _before_ you parse the running-routers
14299 list to decide who's running.
14300 - Check return value of fclose while writing to disk, so we don't
14301 end up with broken files when servers run out of disk space.
14302 - Port it to SunOS 5.9 / Athena
14303 - Fix two bugs in saving onion keys to disk when rotating, so
14304 hopefully we'll get fewer people using old onion keys.
14305 - Remove our mostly unused -- and broken -- hex_encode()
14306 function. Use base16_encode() instead. (Thanks to Timo Lindfors
14307 for pointing out this bug.)
14308 - Only pick and establish intro points after we've gotten a
14310 - Fix assert triggers: if the other side returns an address 0.0.0.0,
14311 don't put it into the client dns cache.
14312 - If a begin failed due to exit policy, but we believe the IP
14313 address should have been allowed, switch that router to exitpolicy
14314 reject *:* until we get our next directory.
14316 o Protocol changes:
14317 - 'Extend' relay cell payloads now include the digest of the
14318 intended next hop's identity key. Now we can verify that we're
14319 extending to the right router, and also extend to routers we
14320 hadn't heard of before.
14323 - Tor nodes can now act as relays (with an advertised ORPort)
14324 without being manually verified by the dirserver operators.
14325 - Uploaded descriptors of unverified routers are now accepted
14326 by the dirservers, and included in the directory.
14327 - Verified routers are listed by nickname in the running-routers
14328 list; unverified routers are listed as "$<fingerprint>".
14329 - We now use hash-of-identity-key in most places rather than
14330 nickname or addr:port, for improved security/flexibility.
14331 - AllowUnverifiedNodes config option to let circuits choose no-name
14332 routers in entry,middle,exit,introduction,rendezvous positions.
14333 Allow middle and rendezvous positions by default.
14334 - When picking unverified routers, skip those with low uptime and/or
14335 low bandwidth, depending on what properties you care about.
14336 - ClientOnly option for nodes that never want to become servers.
14337 - Directory caching.
14338 - "AuthoritativeDir 1" option for the official dirservers.
14339 - Now other nodes (clients and servers) will cache the latest
14340 directory they've pulled down.
14341 - They can enable their DirPort to serve it to others.
14342 - Clients will pull down a directory from any node with an open
14343 DirPort, and check the signature/timestamp correctly.
14344 - Authoritative dirservers now fetch directories from other
14345 authdirservers, to stay better synced.
14346 - Running-routers list tells who's down also, along with noting
14347 if they're verified (listed by nickname) or unverified (listed
14349 - Allow dirservers to serve running-router list separately.
14350 This isn't used yet.
14351 - You can now fetch $DIRURL/running-routers to get just the
14352 running-routers line, not the whole descriptor list. (But
14353 clients don't use this yet.)
14354 - Clients choose nodes proportional to advertised bandwidth.
14355 - Clients avoid using nodes with low uptime as introduction points.
14356 - Handle servers with dynamic IP addresses: don't just replace
14357 options->Address with the resolved one at startup, and
14358 detect our address right before we make a routerinfo each time.
14359 - 'FascistFirewall' option to pick dirservers and ORs on specific
14360 ports; plus 'FirewallPorts' config option to tell FascistFirewall
14361 which ports are open. (Defaults to 80,443)
14362 - Try other dirservers immediately if the one you try is down. This
14363 should tolerate down dirservers better now.
14364 - ORs connect-on-demand to other ORs
14365 - If you get an extend cell to an OR you're not connected to,
14366 connect, handshake, and forward the create cell.
14367 - The authoritative dirservers stay connected to everybody,
14368 and everybody stays connected to 0.0.7 servers, but otherwise
14369 clients/servers expire unused connections after 5 minutes.
14370 - When servers get a sigint, they delay 30 seconds (refusing new
14371 connections) then exit. A second sigint causes immediate exit.
14372 - File and name management:
14373 - Look for .torrc if no CONFDIR "torrc" is found.
14374 - If no datadir is defined, then choose, make, and secure ~/.tor
14376 - If torrc not found, exitpolicy reject *:*.
14377 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
14378 - If no nickname is defined, derive default from hostname.
14379 - Rename secret key files, e.g. identity.key -> secret_id_key,
14380 to discourage people from mailing their identity key to tor-ops.
14381 - Refuse to build a circuit before the directory has arrived --
14382 it won't work anyway, since you won't know the right onion keys
14384 - Parse tor version numbers so we can do an is-newer-than check
14385 rather than an is-in-the-list check.
14386 - New socks command 'resolve', to let us shim gethostbyname()
14388 - A 'tor_resolve' script to access the socks resolve functionality.
14389 - A new socks-extensions.txt doc file to describe our
14390 interpretation and extensions to the socks protocols.
14391 - Add a ContactInfo option, which gets published in descriptor.
14392 - Write tor version at the top of each log file
14393 - New docs in the tarball:
14395 - Document that you should proxy your SSL traffic too.
14396 - Log a warning if the user uses an unsafe socks variant, so people
14397 are more likely to learn about privoxy or socat.
14398 - Log a warning if you're running an unverified server, to let you
14399 know you might want to get it verified.
14400 - Change the default exit policy to reject the default edonkey,
14401 kazaa, gnutella ports.
14402 - Add replace_file() to util.[ch] to handle win32's rename().
14403 - Publish OR uptime in descriptor (and thus in directory) too.
14404 - Remember used bandwidth (both in and out), and publish 15-minute
14405 snapshots for the past day into our descriptor.
14406 - Be more aggressive about trying to make circuits when the network
14407 has changed (e.g. when you unsuspend your laptop).
14408 - Check for time skew on http headers; report date in response to
14410 - If the entrynode config line has only one node, don't pick it as
14412 - Add strict{entry|exit}nodes config options. If set to 1, then
14413 we refuse to build circuits that don't include the specified entry
14415 - OutboundBindAddress config option, to bind to a specific
14416 IP address for outgoing connect()s.
14417 - End truncated log entries (e.g. directories) with "[truncated]".
14420 Changes in version 0.0.7.3 - 2004-08-12
14421 o Stop dnsworkers from triggering an assert failure when you
14422 ask them to resolve the host "".
14425 Changes in version 0.0.7.2 - 2004-07-07
14426 o A better fix for the 0.0.0.0 problem, that will hopefully
14427 eliminate the remaining related assertion failures.
14430 Changes in version 0.0.7.1 - 2004-07-04
14431 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
14432 since internally we use 0.0.0.0 to signify "not yet resolved".
14435 Changes in version 0.0.7 - 2004-06-07
14436 o Fixes for crashes and other obnoxious bugs:
14437 - Fix an epipe bug: sometimes when directory connections failed
14438 to connect, we would give them a chance to flush before closing
14440 - When we detached from a circuit because of resolvefailed, we
14441 would immediately try the same circuit twice more, and then
14442 give up on the resolve thinking we'd tried three different
14444 - Limit the number of intro circuits we'll attempt to build for a
14445 hidden service per 15-minute period.
14446 - Check recommended-software string *early*, before actually parsing
14447 the directory. Thus we can detect an obsolete version and exit,
14448 even if the new directory format doesn't parse.
14449 o Fixes for security bugs:
14450 - Remember which nodes are dirservers when you startup, and if a
14451 random OR enables his dirport, don't automatically assume he's
14452 a trusted dirserver.
14454 - Directory connections were asking the wrong poll socket to
14455 start writing, and not asking themselves to start writing.
14456 - When we detached from a circuit because we sent a begin but
14457 didn't get a connected, we would use it again the first time;
14458 but after that we would correctly switch to a different one.
14459 - Stop warning when the first onion decrypt attempt fails; they
14460 will sometimes legitimately fail now that we rotate keys.
14461 - Override unaligned-access-ok check when $host_cpu is ia64 or
14462 arm. Apparently they allow it but the kernel whines.
14463 - Dirservers try to reconnect periodically too, in case connections
14465 - Fix some memory leaks in directory servers.
14466 - Allow backslash in Win32 filenames.
14467 - Made Tor build complain-free on FreeBSD, hopefully without
14468 breaking other BSD builds. We'll see.
14469 - Check directory signatures based on name of signer, not on whom
14470 we got the directory from. This will let us cache directories more
14472 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
14475 - Doxygen markup on all functions and global variables.
14476 - Make directory functions update routerlist, not replace it. So
14477 now directory disagreements are not so critical a problem.
14478 - Remove the upper limit on number of descriptors in a dirserver's
14479 directory (not that we were anywhere close).
14480 - Allow multiple logfiles at different severity ranges.
14481 - Allow *BindAddress to specify ":port" rather than setting *Port
14482 separately. Allow multiple instances of each BindAddress config
14483 option, so you can bind to multiple interfaces if you want.
14484 - Allow multiple exit policy lines, which are processed in order.
14485 Now we don't need that huge line with all the commas in it.
14486 - Enable accept/reject policies on SOCKS connections, so you can bind
14487 to 0.0.0.0 but still control who can use your OP.
14488 - Updated the man page to reflect these features.
14491 Changes in version 0.0.6.2 - 2004-05-16
14492 o Our integrity-checking digest was checking only the most recent cell,
14493 not the previous cells like we'd thought.
14494 Thanks to Stefan Mark for finding the flaw!
14497 Changes in version 0.0.6.1 - 2004-05-06
14498 o Fix two bugs in our AES counter-mode implementation (this affected
14499 onion-level stream encryption, but not TLS-level). It turns
14500 out we were doing something much more akin to a 16-character
14501 polyalphabetic cipher. Oops.
14502 Thanks to Stefan Mark for finding the flaw!
14503 o Retire moria3 as a directory server, and add tor26 as a directory
14507 Changes in version 0.0.6 - 2004-05-02
14509 - Hidden services and rendezvous points are implemented. Go to
14510 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
14511 hidden services. (This only works via a socks4a proxy such as
14512 Privoxy, and currently it's quite slow.)
14513 - We now rotate link (tls context) keys and onion keys.
14514 - CREATE cells now include oaep padding, so you can tell
14515 if you decrypted them correctly.
14516 - Retry stream correctly when we fail to connect because of
14517 exit-policy-reject (should try another) or can't-resolve-address.
14518 - When we hup a dirserver and we've *removed* a server from the
14519 approved-routers list, now we remove that server from the
14520 in-memory directories too.
14521 - Add bandwidthburst to server descriptor.
14522 - Directories now say which dirserver signed them.
14523 - Use a tor_assert macro that logs failed assertions too.
14524 - Since we don't support truncateds much, don't bother sending them;
14525 just close the circ.
14526 - Fetch randomness from /dev/urandom better (not via fopen/fread)
14527 - Better debugging for tls errors
14528 - Set Content-Type on the directory and hidserv descriptor.
14529 - Remove IVs from cipher code, since AES-ctr has none.
14531 - Fix an assert trigger for exit nodes that's been plaguing us since
14532 the days of 0.0.2prexx (thanks weasel!)
14533 - Fix a bug where we were closing tls connections intermittently.
14534 It turns out openssl keeps its errors around -- so if an error
14535 happens, and you don't ask about it, and then another openssl
14536 operation happens and succeeds, and you ask if there was an error,
14537 it tells you about the first error.
14538 - Fix a bug that's been lurking since 27 may 03 (!)
14539 When passing back a destroy cell, we would use the wrong circ id.
14540 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
14541 - Some versions of openssl have an SSL_pending function that erroneously
14542 returns bytes when there is a non-application record pending.
14543 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
14544 o We were using an array of length zero in a few places.
14545 o Win32's gethostbyname can't resolve an IP to an IP.
14546 o Win32's close can't close a socket.
14547 o Handle windows socket errors correctly.
14549 - check for <sys/limits.h> so we build on FreeBSD again, and
14550 <machine/limits.h> for NetBSD.
14553 Changes in version 0.0.5 - 2004-03-30
14554 o Install torrc as torrc.sample -- we no longer clobber your
14556 o Fix mangled-state bug in directory fetching (was causing sigpipes).
14557 o Only build circuits after we've fetched the directory: clients were
14558 using only the directory servers before they'd fetched a directory.
14559 This also means longer startup time; so it goes.
14560 o Fix an assert trigger where an OP would fail to handshake, and we'd
14561 expect it to have a nickname.
14562 o Work around a tsocks bug: do a socks reject when AP connection dies
14563 early, else tsocks goes into an infinite loop.
14564 o Hold socks connection open until reply is flushed (if possible)
14565 o Make exit nodes resolve IPs to IPs immediately, rather than asking
14566 the dns farm to do it.
14567 o Fix c99 aliasing warnings in rephist.c
14568 o Don't include server descriptors that are older than 24 hours in the
14570 o Give socks 'reject' replies their whole 15s to attempt to flush,
14571 rather than seeing the 60s timeout and assuming the flush had failed.
14572 o Clean automake droppings from the cvs repository
14573 o Add in a 'notice' log level for things the operator should hear
14574 but that aren't warnings
14577 Changes in version 0.0.4 - 2004-03-26
14578 o When connecting to a dirserver or OR and the network is down,
14582 Changes in version 0.0.3 - 2004-03-26
14583 o Warn and fail if server chose a nickname with illegal characters
14584 o Port to Solaris and Sparc:
14585 - include missing header fcntl.h
14586 - have autoconf find -lsocket -lnsl automatically
14587 - deal with hardware word alignment
14588 - make uname() work (solaris has a different return convention)
14589 - switch from using signal() to sigaction()
14590 o Preliminary work on reputation system:
14591 - Keep statistics on success/fail of connect attempts; they're published
14592 by kill -USR1 currently.
14593 - Add a RunTesting option to try to learn link state by creating test
14594 circuits, even when SocksPort is off.
14595 - Remove unused open circuits when there are too many.
14598 Changes in version 0.0.2 - 2004-03-19
14599 - Include strlcpy and strlcat for safer string ops
14600 - define INADDR_NONE so we compile (but still not run) on solaris
14603 Changes in version 0.0.2pre27 - 2004-03-14
14605 - Allow internal tor networks (we were rejecting internal IPs,
14606 now we allow them if they're set explicitly).
14607 - And fix a few endian issues.
14610 Changes in version 0.0.2pre26 - 2004-03-14
14612 - If a stream times out after 15s without a connected cell, don't
14613 try that circuit again: try a new one.
14614 - Retry streams at most 4 times. Then give up.
14615 - When a dirserver gets a descriptor from an unknown router, it
14616 logs its fingerprint (so the dirserver operator can choose to
14617 accept it even without mail from the server operator).
14618 - Inform unapproved servers when we reject their descriptors.
14619 - Make tor build on Windows again. It works as a client, who knows
14621 - Clearer instructions in the torrc for how to set up a server.
14622 - Be more efficient about reading fd's when our global token bucket
14623 (used for rate limiting) becomes empty.
14625 - Stop asserting that computers always go forward in time. It's
14627 - When we sent a cell (e.g. destroy) and then marked an OR connection
14628 expired, we might close it before finishing a flush if the other
14629 side isn't reading right then.
14630 - Don't allow dirservers to start if they haven't defined
14631 RecommendedVersions
14632 - We were caching transient dns failures. Oops.
14633 - Prevent servers from publishing an internal IP as their address.
14634 - Address a strcat vulnerability in circuit.c
14637 Changes in version 0.0.2pre25 - 2004-03-04
14639 - Put the OR's IP in its router descriptor, not its fqdn. That way
14640 we'll stop being stalled by gethostbyname for nodes with flaky dns,
14643 - If the user typed in an address that didn't resolve, the server
14647 Changes in version 0.0.2pre24 - 2004-03-03
14649 - Fix an assertion failure in dns.c, where we were trying to dequeue
14650 a pending dns resolve even if it wasn't pending
14651 - Fix a spurious socks5 warning about still trying to write after the
14652 connection is finished.
14653 - Hold certain marked_for_close connections open until they're finished
14654 flushing, rather than losing bytes by closing them too early.
14655 - Correctly report the reason for ending a stream
14656 - Remove some duplicate calls to connection_mark_for_close
14657 - Put switch_id and start_daemon earlier in the boot sequence, so it
14658 will actually try to chdir() to options.DataDirectory
14659 - Make 'make test' exit(1) if a test fails; fix some unit tests
14660 - Make tor fail when you use a config option it doesn't know about,
14661 rather than warn and continue.
14662 - Make --version work
14663 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
14666 Changes in version 0.0.2pre23 - 2004-02-29
14668 - Print a statement when the first circ is finished, so the user
14669 knows it's working.
14670 - If a relay cell is unrecognized at the end of the circuit,
14671 send back a destroy. (So attacks to mutate cells are more
14673 - New config option 'excludenodes' to avoid certain nodes for circuits.
14674 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
14675 so you can collect coredumps there.
14677 - Fix a bug in tls flushing where sometimes data got wedged and
14678 didn't flush until more data got sent. Hopefully this bug was
14679 a big factor in the random delays we were seeing.
14680 - Make 'connected' cells include the resolved IP, so the client
14681 dns cache actually gets populated.
14682 - Disallow changing from ORPort=0 to ORPort>0 on hup.
14683 - When we time-out on a stream and detach from the circuit, send an
14684 end cell down it first.
14685 - Only warn about an unknown router (in exitnodes, entrynodes,
14686 excludenodes) after we've fetched a directory.
14689 Changes in version 0.0.2pre22 - 2004-02-26
14691 - Servers publish less revealing uname information in descriptors.
14692 - More memory tracking and assertions, to crash more usefully when
14694 - If the default torrc isn't there, just use some default defaults.
14695 Plus provide an internal dirservers file if they don't have one.
14696 - When the user tries to use Tor as an http proxy, give them an http
14697 501 failure explaining that we're a socks proxy.
14698 - Dump a new router.desc on hup, to help confused people who change
14699 their exit policies and then wonder why router.desc doesn't reflect
14701 - Clean up the generic tor.sh init script that we ship with.
14703 - If the exit stream is pending on the resolve, and a destroy arrives,
14704 then the stream wasn't getting removed from the pending list. I
14705 think this was the one causing recent server crashes.
14706 - Use a more robust poll on OSX 10.3, since their poll is flaky.
14707 - When it couldn't resolve any dirservers, it was useless from then on.
14708 Now it reloads the RouterFile (or default dirservers) if it has no
14710 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
14711 many users don't even *have* a /usr/local/sbin/.
14714 Changes in version 0.0.2pre21 - 2004-02-18
14716 - There's a ChangeLog file that actually reflects the changelog.
14717 - There's a 'torify' wrapper script, with an accompanying
14718 tor-tsocks.conf, that simplifies the process of using tsocks for
14719 tor. It even has a man page.
14720 - The tor binary gets installed to sbin rather than bin now.
14721 - Retry streams where the connected cell hasn't arrived in 15 seconds
14722 - Clean up exit policy handling -- get the default out of the torrc,
14723 so we can update it without forcing each server operator to fix
14725 - Allow imaps and pop3s in default exit policy
14727 - Prevent picking middleman nodes as the last node in the circuit
14730 Changes in version 0.0.2pre20 - 2004-01-30
14732 - We now have a deb package, and it's in debian unstable. Go to
14733 it, apt-getters. :)
14734 - I've split the TotalBandwidth option into BandwidthRate (how many
14735 bytes per second you want to allow, long-term) and
14736 BandwidthBurst (how many bytes you will allow at once before the cap
14737 kicks in). This better token bucket approach lets you, say, set
14738 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
14739 performance while not exceeding your monthly bandwidth quota.
14740 - Push out a tls record's worth of data once you've got it, rather
14741 than waiting until you've read everything waiting to be read. This
14742 may improve performance by pipelining better. We'll see.
14743 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
14744 from failed circuits (if they haven't been connected yet) and attach
14746 - Expire old streams that haven't managed to connect. Some day we'll
14747 have them reattach to new circuits instead.
14750 - Fix several memory leaks that were causing servers to become bloated
14752 - Fix a few very rare assert triggers. A few more remain.
14753 - Setuid to User _before_ complaining about running as root.
14756 Changes in version 0.0.2pre19 - 2004-01-07
14758 - Fix deadlock condition in dns farm. We were telling a child to die by
14759 closing the parent's file descriptor to him. But newer children were
14760 inheriting the open file descriptor from the parent, and since they
14761 weren't closing it, the socket never closed, so the child never read
14762 eof, so he never knew to exit. Similarly, dns workers were holding
14763 open other sockets, leading to all sorts of chaos.
14764 - New cleaner daemon() code for forking and backgrounding.
14765 - If you log to a file, it now prints an entry at the top of the
14766 logfile so you know it's working.
14767 - The onionskin challenge length was 30 bytes longer than necessary.
14768 - Started to patch up the spec so it's not quite so out of date.
14771 Changes in version 0.0.2pre18 - 2004-01-02
14773 - Fix endian issues with the 'integrity' field in the relay header.
14774 - Fix a potential bug where connections in state
14775 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
14778 Changes in version 0.0.2pre17 - 2003-12-30
14780 - Made --debuglogfile (or any second log file, actually) work.
14781 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
14782 adversary could force us into an infinite loop.
14785 - Each onionskin handshake now includes a hash of the computed key,
14786 to prove the server's identity and help perfect forward secrecy.
14787 - Changed cell size from 256 to 512 bytes (working toward compatibility
14789 - Changed cell length to 2 bytes, and moved it to the relay header.
14790 - Implemented end-to-end integrity checking for the payloads of
14792 - Separated streamid from 'recognized' (otherwise circuits will get
14793 messed up when we try to have streams exit from the middle). We
14794 use the integrity-checking to confirm that a cell is addressed to
14796 - Randomize the initial circid and streamid values, so an adversary who
14797 breaks into a node can't learn how many circuits or streams have
14801 Changes in version 0.0.2pre16 - 2003-12-14
14803 - Fixed a bug that made HUP trigger an assert
14804 - Fixed a bug where a circuit that immediately failed wasn't being
14805 counted as a failed circuit in counting retries.
14808 - Now we close the circuit when we get a truncated cell: otherwise we're
14809 open to an anonymity attack where a bad node in the path truncates
14810 the circuit and then we open streams at him.
14811 - Add port ranges to exit policies
14812 - Add a conservative default exit policy
14813 - Warn if you're running tor as root
14814 - on HUP, retry OR connections and close/rebind listeners
14815 - options.EntryNodes: try these nodes first when picking the first node
14816 - options.ExitNodes: if your best choices happen to include any of
14817 your preferred exit nodes, you choose among just those preferred
14819 - options.ExcludedNodes: nodes that are never picked in path building
14822 Changes in version 0.0.2pre15 - 2003-12-03
14823 o Robustness and bugfixes:
14824 - Sometimes clients would cache incorrect DNS resolves, which would
14825 really screw things up.
14826 - An OP that goes offline would slowly leak all its sockets and stop
14828 - A wide variety of bugfixes in exit node selection, exit policy
14829 handling, and processing pending streams when a new circuit is
14831 - Pick nodes for a path only from those the directory says are up
14832 - Choose randomly from all running dirservers, not always the first one
14833 - Increase allowed http header size for directory fetch.
14834 - Stop writing to stderr (if we're daemonized it will be closed).
14835 - Enable -g always, so cores will be more useful to me.
14836 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
14839 - Wrote a man page. It lists commonly used options.
14842 - Change default loglevel to warn.
14843 - Make PidFile default to null rather than littering in your CWD.
14844 - OnionRouter config option is now obsolete. Instead it just checks
14846 - Moved to a single unified torrc file for both clients and servers.
14849 Changes in version 0.0.2pre14 - 2003-11-29
14850 o Robustness and bugfixes:
14851 - Force the admin to make the DataDirectory himself
14852 - to get ownership/permissions right
14853 - so clients no longer make a DataDirectory and then never use it
14854 - fix bug where a client who was offline for 45 minutes would never
14855 pull down a directory again
14856 - fix (or at least hide really well) the dns assert bug that was
14857 causing server crashes
14858 - warnings and improved robustness wrt clockskew for certs
14859 - use the native daemon(3) to daemonize, when available
14860 - exit if bind() fails
14861 - exit if neither socksport nor orport is defined
14862 - include our own tor_timegm (Win32 doesn't have its own)
14863 - bugfix for win32 with lots of connections
14864 - fix minor bias in PRNG
14865 - make dirserver more robust to corrupt cached directory
14868 - Wrote the design document (woo)
14870 o Circuit building and exit policies:
14871 - Circuits no longer try to use nodes that the directory has told them
14873 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
14874 bitcounts (18.0.0.0/8).
14875 - Make AP connections standby for a circuit if no suitable circuit
14876 exists, rather than failing
14877 - Circuits choose exit node based on addr/port, exit policies, and
14878 which AP connections are standing by
14879 - Bump min pathlen from 2 to 3
14880 - Relay end cells have a payload to describe why the stream ended.
14881 - If the stream failed because of exit policy, try again with a new
14883 - Clients have a dns cache to remember resolved addresses.
14884 - Notice more quickly when we have no working circuits
14887 - APPort is now called SocksPort
14888 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
14890 - RecommendedVersions is now a config variable rather than
14891 hardcoded (for dirservers)
14892 - Reloads config on HUP
14893 - Usage info on -h or --help
14894 - If you set User and Group config vars, it'll setu/gid to them.
14896 Changes in version 0.0.2pre13 - 2003-10-19
14897 o General stability:
14898 - SSL_write no longer fails when it returns WANTWRITE and the number
14899 of bytes in the buf has changed by the next SSL_write call.
14900 - Fix segfault fetching directory when network is down
14901 - Fix a variety of minor memory leaks
14902 - Dirservers reload the fingerprints file on HUP, so I don't have
14903 to take down the network when I approve a new router
14904 - Default server config file has explicit Address line to specify fqdn
14907 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
14908 - Make listener connections not ever alloc bufs
14910 o Autoconf improvements:
14911 - don't clobber an external CFLAGS in ./configure
14912 - Make install now works
14913 - create var/lib/tor on make install
14914 - autocreate a tor.sh initscript to help distribs
14915 - autocreate the torrc and sample-server-torrc with correct paths
14917 o Log files and Daemonizing now work:
14918 - If --DebugLogFile is specified, log to it at -l debug
14919 - If --LogFile is specified, use it instead of commandline
14920 - If --RunAsDaemon is set, tor forks and backgrounds on startup