1 This document summarizes new features and bugfixes in each stable
2 release of Tor. If you want to see more detailed descriptions of the
3 changes in each development snapshot, see the ChangeLog file.
6 Changes in version 0.3.5.11 - 2020-07-09
7 Tor 0.3.5.11 backports fixes from later tor releases, including several
8 usability, portability, and reliability fixes.
10 This release also fixes TROVE-2020-001, a medium-severity denial of
11 service vulnerability affecting all versions of Tor when compiled with
12 the NSS encryption library. (This is not the default configuration.)
13 Using this vulnerability, an attacker could cause an affected Tor
14 instance to crash remotely. This issue is also tracked as CVE-2020-
15 15572. Anybody running a version of Tor built with the NSS library
16 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
19 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
20 - Fix a crash due to an out-of-bound memory access when Tor is
21 compiled with NSS support. Fixes bug 33119; bugfix on
22 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
25 o Major bugfixes (DoS defenses, bridges, pluggable transport, backport from 0.4.3.4-rc):
26 - Fix a bug that was preventing DoS defenses from running on bridges
27 with a pluggable transport. Previously, the DoS subsystem was not
28 given the transport name of the client connection, thus failed to
29 find the GeoIP cache entry for that client address. Fixes bug
30 33491; bugfix on 0.3.3.2-alpha.
32 o Minor features (testing, backport from 0.4.3.4-rc):
33 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
34 variable to specify a list of space-separated test cases that
35 should not be executed. We will use this to disable certain tests
36 that are failing on Appveyor because of mismatched OpenSSL
37 libraries. Part of ticket 33643.
39 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
40 - Use the correct 64-bit printf format when compiling with MINGW on
41 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
43 o Minor bugfix (relay, configuration, backport from 0.4.3.3-alpha):
44 - Warn if the ContactInfo field is not set, and tell the relay
45 operator that not having a ContactInfo field set might cause their
46 relay to get rejected in the future. Fixes bug 33361; bugfix
49 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
50 - Resume use of preemptively-built circuits when UseEntryGuards is set
51 to 0. We accidentally disabled this feature with that config
52 setting, leading to slower load times. Fixes bug 34303; bugfix
55 o Minor bugfixes (compiler compatibility, backport from 0.4.3.5):
56 - Avoid compiler warnings from Clang 10 related to the use of GCC-
57 style "/* falls through */" comments. Both Clang and GCC allow
58 __attribute__((fallthrough)) instead, so that's what we're using
59 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
61 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
62 - Fix a compiler warning on platforms with 32-bit time_t values.
63 Fixes bug 40028; bugfix on 0.3.2.8-rc.
65 o Minor bugfixes (embedded Tor, backport from 0.4.3.1-alpha):
66 - When starting Tor any time after the first time in a process,
67 register the thread in which it is running as the main thread.
68 Previously, we only did this on Windows, which could lead to bugs
69 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
72 o Minor bugfixes (key portability, backport from 0.4.3.4-rc):
73 - When reading PEM-encoded key data, tolerate CRLF line-endings even
74 if we are not running on Windows. Previously, non-Windows hosts
75 would reject these line-endings in certain positions, making
76 certain key files hard to move from one host to another. Fixes bug
77 33032; bugfix on 0.3.5.1-alpha.
79 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
80 - Downgrade a noisy log message that could occur naturally when
81 receiving an extrainfo document that we no longer want. Fixes bug
82 16016; bugfix on 0.2.6.3-alpha.
84 o Minor bugfixes (onion service v3, client, backport from 0.4.3.3-alpha):
85 - Remove a BUG() warning that would cause a stack trace if an onion
86 service descriptor was freed while we were waiting for a
87 rendezvous circuit to complete. Fixes bug 28992; bugfix
90 o Testing (CI, backport from 0.4.3.4-rc):
91 - In our Appveyor Windows CI, copy required DLLs to test and app
92 directories, before running tor's tests. This ensures that tor.exe
93 and test*.exe use the correct version of each DLL. This fix is not
94 required, but we hope it will avoid DLL search issues in future.
95 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
96 - On Appveyor, skip the crypto/openssl_version test, which is
97 failing because of a mismatched library installation. Fix
101 Changes in version 0.4.2.8 - 2020-07-09
102 Tor 0.4.2.8 backports various fixes from later releases, including
103 several that affect usability and portability.
105 This release also fixes TROVE-2020-001, a medium-severity denial of
106 service vulnerability affecting all versions of Tor when compiled with
107 the NSS encryption library. (This is not the default configuration.)
108 Using this vulnerability, an attacker could cause an affected Tor
109 instance to crash remotely. This issue is also tracked as CVE-2020-
110 15572. Anybody running a version of Tor built with the NSS library
111 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
114 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
115 - Fix a crash due to an out-of-bound memory access when Tor is
116 compiled with NSS support. Fixes bug 33119; bugfix on
117 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
120 o Major bugfixes (DoS defenses, bridges, pluggable transport, backport from 0.4.3.4-rc):
121 - Fix a bug that was preventing DoS defenses from running on bridges
122 with a pluggable transport. Previously, the DoS subsystem was not
123 given the transport name of the client connection, thus failed to
124 find the GeoIP cache entry for that client address. Fixes bug
125 33491; bugfix on 0.3.3.2-alpha.
127 o Minor feature (sendme, flow control, backport form 0.4.3.4-rc):
128 - Default to sending SENDME version 1 cells. (Clients are already
129 sending these, because of a consensus parameter telling them to do
130 so: this change only affects what clients would do if the
131 consensus didn't contain a recommendation.) Closes ticket 33623.
133 o Minor features (diagnostic, backport from 0.4.3.3-alpha):
134 - Improve assertions and add some memory-poisoning code to try to
135 track down possible causes of a rare crash (32564) in the EWMA
136 code. Closes ticket 33290.
138 o Minor features (testing, backport from 0.4.3.4-rc):
139 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
140 variable to specify a list of space-separated test cases that
141 should not be executed. We will use this to disable certain tests
142 that are failing on Appveyor because of mismatched OpenSSL
143 libraries. Part of ticket 33643.
145 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
146 - Use the correct 64-bit printf format when compiling with MINGW on
147 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
149 o Minor bugfix (relay, configuration, backport from 0.4.3.3-alpha):
150 - Warn if the ContactInfo field is not set, and tell the relay
151 operator that not having a ContactInfo field set might cause their
152 relay to get rejected in the future. Fixes bug 33361; bugfix
155 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
156 - Resume use of preemptively-built circuits when UseEntryGuards is set
157 to 0. We accidentally disabled this feature with that config
158 setting, leading to slower load times. Fixes bug 34303; bugfix
161 o Minor bugfixes (compiler compatibility, backport from 0.4.3.5):
162 - Avoid compiler warnings from Clang 10 related to the use of GCC-
163 style "/* falls through */" comments. Both Clang and GCC allow
164 __attribute__((fallthrough)) instead, so that's what we're using
165 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
166 - Fix compilation warnings with GCC 10.0.1. Fixes bug 34077; bugfix
169 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
170 - Fix a compiler warning on platforms with 32-bit time_t values.
171 Fixes bug 40028; bugfix on 0.3.2.8-rc.
173 o Minor bugfixes (controller protocol, backport from 0.4.3.2-alpha):
174 - When receiving "ACTIVE" or "DORMANT" signals on the control port,
175 report them as SIGNAL events. Previously we would log a bug
176 warning. Fixes bug 33104; bugfix on 0.4.0.1-alpha.
178 o Minor bugfixes (embedded Tor, backport from 0.4.3.1-alpha):
179 - When starting Tor any time after the first time in a process,
180 register the thread in which it is running as the main thread.
181 Previously, we only did this on Windows, which could lead to bugs
182 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
185 o Minor bugfixes (key portability, backport from 0.4.3.4-rc):
186 - When reading PEM-encoded key data, tolerate CRLF line-endings even
187 if we are not running on Windows. Previously, non-Windows hosts
188 would reject these line-endings in certain positions, making
189 certain key files hard to move from one host to another. Fixes bug
190 33032; bugfix on 0.3.5.1-alpha.
192 o Minor bugfixes (logging, backport from 0.4.3.2-rc):
193 - When logging a bug, do not say "Future instances of this warning
194 will be silenced" unless we are actually going to silence them.
195 Previously we would say this whenever a BUG() check failed in the
196 code. Fixes bug 33095; bugfix on 0.4.1.1-alpha.
198 o Minor bugfixes (logging, backport from 0.4.3.4-rc):
199 - Flush stderr, stdout, and file logs during shutdown, if supported
200 by the OS. This change helps make sure that any final logs are
201 recorded. Fixes bug 33087; bugfix on 0.4.1.6.
203 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
204 - Downgrade a noisy log message that could occur naturally when
205 receiving an extrainfo document that we no longer want. Fixes bug
206 16016; bugfix on 0.2.6.3-alpha.
208 o Minor bugfixes (onion service v3, client, backport from 0.4.3.3-alpha):
209 - Remove a BUG() warning that would cause a stack trace if an onion
210 service descriptor was freed while we were waiting for a
211 rendezvous circuit to complete. Fixes bug 28992; bugfix
214 o Testing (CI, backport from 0.4.3.4-rc):
215 - In our Appveyor Windows CI, copy required DLLs to test and app
216 directories, before running tor's tests. This ensures that tor.exe
217 and test*.exe use the correct version of each DLL. This fix is not
218 required, but we hope it will avoid DLL search issues in future.
219 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
220 - On Appveyor, skip the crypto/openssl_version test, which is
221 failing because of a mismatched library installation. Fix
225 Changes in version 0.4.3.6 - 2020-07-09
226 Tor 0.4.3.6 backports several bugfixes from later releases, including
227 some affecting usability.
229 This release also fixes TROVE-2020-001, a medium-severity denial of
230 service vulnerability affecting all versions of Tor when compiled with
231 the NSS encryption library. (This is not the default configuration.)
232 Using this vulnerability, an attacker could cause an affected Tor
233 instance to crash remotely. This issue is also tracked as CVE-2020-
234 15572. Anybody running a version of Tor built with the NSS library
235 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
238 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
239 - Fix a crash due to an out-of-bound memory access when Tor is
240 compiled with NSS support. Fixes bug 33119; bugfix on
241 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
244 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
245 - Use the correct 64-bit printf format when compiling with MINGW on
246 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
248 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
249 - Resume use of preemptively-built circuits when UseEntryGuards is set
250 to 0. We accidentally disabled this feature with that config
251 setting, leading to slower load times. Fixes bug 34303; bugfix
254 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
255 - Fix a compiler warning on platforms with 32-bit time_t values.
256 Fixes bug 40028; bugfix on 0.3.2.8-rc.
258 o Minor bugfixes (linux seccomp sandbox, nss, backport from 0.4.4.1-alpha):
259 - Fix a startup crash when tor is compiled with --enable-nss and
260 sandbox support is enabled. Fixes bug 34130; bugfix on
261 0.3.5.1-alpha. Patch by Daniel Pinto.
263 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
264 - Downgrade a noisy log message that could occur naturally when
265 receiving an extrainfo document that we no longer want. Fixes bug
266 16016; bugfix on 0.2.6.3-alpha.
268 o Minor bugfixes (manual page, backport from 0.4.4.1-alpha):
269 - Update the man page to reflect that MinUptimeHidServDirectoryV2
270 defaults to 96 hours. Fixes bug 34299; bugfix on 0.2.6.3-alpha.
272 o Minor bugfixes (onion service v3, backport from 0.4.4.1-alpha):
273 - Prevent an assert() that would occur when cleaning the client
274 descriptor cache, and attempting to close circuits for a non-
275 decrypted descriptor (lacking client authorization). Fixes bug
276 33458; bugfix on 0.4.2.1-alpha.
278 o Minor bugfixes (portability, backport from 0.4.4.1-alpha):
279 - Fix a portability error in the configure script, where we were
280 using "==" instead of "=". Fixes bug 34233; bugfix on 0.4.3.5.
282 o Minor bugfixes (relays, backport from 0.4.4.1-alpha):
283 - Stop advertising incorrect IPv6 ORPorts in relay and bridge
284 descriptors, when the IPv6 port was configured as "auto". Fixes
285 bug 32588; bugfix on 0.2.3.9-alpha.
287 o Documentation (backport from 0.4.4.1-alpha):
288 - Fix several doxygen warnings related to imbalanced groups. Closes
292 Changes in version 0.4.3.5 - 2020-05-15
293 Tor 0.4.3.5 is the first stable release in the 0.4.3.x series. This
294 series adds support for building without relay code enabled, and
295 implements functionality needed for OnionBalance with v3 onion
296 services. It includes significant refactoring of our configuration and
297 controller functionality, and fixes numerous smaller bugs and
300 Per our support policy, we support each stable release series for nine
301 months after its first stable release, or three months after the first
302 stable release of the next series: whichever is longer. This means
303 that 0.4.3.x will be supported until around February 2021--later, if
304 0.4.4.x is later than anticipated.
306 Note also that support for 0.4.1.x is about to end on May 20 of this
307 year; 0.4.2.x will be supported until September 15. We still plan to
308 continue supporting 0.3.5.x, our long-term stable series, until
311 Below are the changes since 0.4.2.6. For a list of only the changes
312 since 0.4.3.4-rc, see the ChangeLog file.
314 o New system requirements:
315 - When building Tor, you now need to have Python 3 in order to run
316 the integration tests. (Python 2 is officially unsupported
317 upstream, as of 1 Jan 2020.) Closes ticket 32608.
319 o Major features (build system):
320 - The relay code can now be disabled using the --disable-module-relay
321 configure option. When this option is set, we also disable the
322 dirauth module. Closes ticket 32123.
323 - When Tor is compiled --disable-module-relay, we also omit the code
324 used to act as a directory cache. Closes ticket 32487.
326 o Major features (directory authority, ed25519):
327 - Add support for banning a relay's ed25519 keys in the approved-
328 routers file. This will help us migrate away from RSA keys in the
329 future. Previously, only RSA keys could be banned in approved-
330 routers. Resolves ticket 22029. Patch by Neel Chauhan.
332 o Major features (onion services):
333 - New control port commands to manage client-side onion service
334 authorization credentials. The ONION_CLIENT_AUTH_ADD command adds
335 a credential, ONION_CLIENT_AUTH_REMOVE deletes a credential, and
336 ONION_CLIENT_AUTH_VIEW lists the credentials. Closes ticket 30381.
337 - Introduce a new SocksPort flag, ExtendedErrors, to support more
338 detailed error codes in information for applications that support
339 them. Closes ticket 30382; implements proposal 304.
341 o Major features (proxy):
342 - In addition to its current supported proxy types (HTTP CONNECT,
343 SOCKS4, and SOCKS5), Tor can now make its OR connections through a
344 HAProxy server. A new torrc option was added to specify the
345 address/port of the server: TCPProxy <protocol> <host>:<port>.
346 Currently the only supported protocol for the option is haproxy.
347 Closes ticket 31518. Patch done by Suphanat Chunhapanya (haxxpop).
349 o Major bugfixes (security, denial-of-service):
350 - Fix a denial-of-service bug that could be used by anyone to
351 consume a bunch of CPU on any Tor relay or authority, or by
352 directories to consume a bunch of CPU on clients or hidden
353 services. Because of the potential for CPU consumption to
354 introduce observable timing patterns, we are treating this as a
355 high-severity security issue. Fixes bug 33119; bugfix on
356 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
357 as TROVE-2020-002 and CVE-2020-10592.
359 o Major bugfixes (circuit padding, memory leak):
360 - Avoid a remotely triggered memory leak in the case that a circuit
361 padding machine is somehow negotiated twice on the same circuit.
362 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
363 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
365 o Major bugfixes (directory authority):
366 - Directory authorities will now send a 503 (not enough bandwidth)
367 code to clients when under bandwidth pressure. Known relays and
368 other authorities will always be answered regardless of the
369 bandwidth situation. Fixes bug 33029; bugfix on 0.1.2.5-alpha.
371 o Major bugfixes (DoS defenses, bridges, pluggable transport):
372 - Fix a bug that was preventing DoS defenses from running on bridges
373 with a pluggable transport. Previously, the DoS subsystem was not
374 given the transport name of the client connection, thus failed to
375 find the GeoIP cache entry for that client address. Fixes bug
376 33491; bugfix on 0.3.3.2-alpha.
378 o Major bugfixes (networking):
379 - Correctly handle IPv6 addresses in SOCKS5 RESOLVE_PTR requests,
380 and accept strings as well as binary addresses. Fixes bug 32315;
381 bugfix on 0.3.5.1-alpha.
383 o Major bugfixes (onion service):
384 - Report HS circuit failure back into the HS subsystem so we take
385 appropriate action with regards to the client introduction point
386 failure cache. This improves reachability of onion services, since
387 now clients notice failing introduction circuits properly. Fixes
388 bug 32020; bugfix on 0.3.2.1-alpha.
390 o Minor feature (heartbeat, onion service):
391 - Add the DoS INTRODUCE2 defenses counter to the heartbeat DoS
392 message. Closes ticket 31371.
394 o Minor feature (sendme, flow control):
395 - Default to sending SENDME version 1 cells. (Clients are already
396 sending these, because of a consensus parameter telling them to do
397 so: this change only affects what clients would do if the
398 consensus didn't contain a recommendation.) Closes ticket 33623.
400 o Minor features (best practices tracker):
401 - Practracker now supports a --regen-overbroad option to regenerate
402 the exceptions file, but only to revise exceptions to be _less_
403 tolerant of best-practices violations. Closes ticket 32372.
405 o Minor features (configuration validation):
406 - Configuration validation can now be done by per-module callbacks,
407 rather than a global validation function. This will let us reduce
408 the size of config.c and some of its more cumbersome functions.
411 o Minor features (configuration):
412 - If a configured hardware crypto accelerator in AccelName is
413 prefixed with "!", Tor now exits when it cannot be found. Closes
415 - We now use flag-driven logic to warn about obsolete configuration
416 fields, so that we can include their names. In 0.4.2, we used a
417 special type, which prevented us from generating good warnings.
418 Implements ticket 32404.
420 o Minor features (configure, build system):
421 - Output a list of enabled/disabled features at the end of the
422 configure process in a pleasing way. Closes ticket 31373.
424 o Minor features (continuous integration):
425 - Run Doxygen Makefile target on Travis, so we can learn about
426 regressions in our internal documentation. Closes ticket 32455.
427 - Stop allowing failures on the Travis CI stem tests job. It looks
428 like all the stem hangs we were seeing before are now fixed.
431 o Minor features (controller):
432 - Add stream isolation data to STREAM event. Closes ticket 19859.
433 - Implement a new GETINFO command to fetch microdescriptor
434 consensus. Closes ticket 31684.
436 o Minor features (debugging, directory system):
437 - Don't crash when we find a non-guard with a guard-fraction value
438 set. Instead, log a bug warning, in an attempt to figure out how
439 this happened. Diagnostic for ticket 32868.
441 o Minor features (defense in depth):
442 - Add additional checks around tor_vasprintf() usage, in case the
443 function returns an error. Patch by Tobias Stoeckmann. Fixes
446 o Minor features (developer tools):
447 - Remove the 0.2.9.x series branches from git scripts (git-merge-
448 forward.sh, git-pull-all.sh, git-push-all.sh, git-setup-dirs.sh).
450 - Add a check_cocci_parse.sh script that checks that new code is
451 parseable by Coccinelle. Add an exceptions file for unparseable
452 files, and run the script from travis CI. Closes ticket 31919.
453 - Call the check_cocci_parse.sh script from a 'check-cocci' Makefile
454 target. Closes ticket 31919.
455 - Add a rename_c_identifiers.py tool to rename a bunch of C
456 identifiers at once, and generate a well-formed commit message
457 describing the change. This should help with refactoring. Closes
459 - Add some scripts in "scripts/coccinelle" to invoke the Coccinelle
460 semantic patching tool with the correct flags. These flags are
461 fairly easy to forget, and these scripts should help us use
462 Coccinelle more effectively in the future. Closes ticket 31705.
464 o Minor features (diagnostic):
465 - Improve assertions and add some memory-poisoning code to try to
466 track down possible causes of a rare crash (32564) in the EWMA
467 code. Closes ticket 33290.
469 o Minor features (directory authorities):
470 - Directory authorities now reject descriptors from relays running
471 Tor versions from the 0.2.9 and 0.4.0 series. The 0.3.5 series is
472 still allowed. Resolves ticket 32672. Patch by Neel Chauhan.
474 o Minor features (Doxygen):
475 - Update Doxygen configuration file to a more recent template (from
476 1.8.15). Closes ticket 32110.
477 - "make doxygen" now works with out-of-tree builds. Closes
479 - Make sure that doxygen outputs documentation for all of our C
480 files. Previously, some were missing @file declarations, causing
481 them to be ignored. Closes ticket 32307.
482 - Our "make doxygen" target now respects --enable-fatal-warnings by
483 default, and does not warn about items that are missing
484 documentation. To warn about missing documentation, run configure
485 with the "--enable-missing-doc-warnings" flag: doing so suspends
486 fatal warnings for doxygen. Closes ticket 32385.
488 o Minor features (git scripts):
489 - Add TOR_EXTRA_CLONE_ARGS to git-setup-dirs.sh for git clone
490 customisation. Closes ticket 32347.
491 - Add git-setup-dirs.sh, which sets up an upstream git repository
492 and worktrees for tor maintainers. Closes ticket 29603.
493 - Add TOR_EXTRA_REMOTE_* to git-setup-dirs.sh for a custom extra
494 remote. Closes ticket 32347.
495 - Call the check_cocci_parse.sh script from the git commit and push
496 hooks. Closes ticket 31919.
497 - Make git-push-all.sh skip unchanged branches when pushing to
498 upstream. The script already skipped unchanged test branches.
500 - Make git-setup-dirs.sh create a master symlink in the worktree
501 directory. Closes ticket 32347.
502 - Skip unmodified source files when doing some existing git hook
503 checks. Related to ticket 31919.
505 o Minor features (IPv6, client):
506 - Make Tor clients tell dual-stack exits that they prefer IPv6
507 connections. This change is equivalent to setting the PreferIPv6
508 flag on SOCKSPorts (and most other listener ports). Tor Browser
509 has been setting this flag for some time, and we want to remove a
510 client distinguisher at exits. Closes ticket 32637.
512 o Minor features (portability, android):
513 - When building for Android, disable some tests that depend on $HOME
514 and/or pwdb, which Android doesn't have. Closes ticket 32825.
515 Patch from Hans-Christoph Steiner.
517 o Minor features (relay modularity):
518 - Split the relay and server pluggable transport config code into
519 separate files in the relay module. Disable this code when the
520 relay module is disabled. Closes part of ticket 32213.
521 - When the relay module is disabled, reject attempts to set the
522 ORPort, DirPort, DirCache, BridgeRelay, ExtORPort, or
523 ServerTransport* options, rather than ignoring the values of these
524 options. Closes part of ticket 32213.
525 - When the relay module is disabled, change the default config so
526 that DirCache is 0, and ClientOnly is 1. Closes ticket 32410.
528 o Minor features (release tools):
529 - Port our ChangeLog formatting and sorting tools to Python 3.
532 o Minor features (testing):
533 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
534 variable to specify a list of space-separated test cases that
535 should not be executed. We will use this to disable certain tests
536 that are failing on Appveyor because of mismatched OpenSSL
537 libraries. Part of ticket 33643.
538 - Detect some common failure cases for test_parseconf.sh in
539 src/test/conf_failures. Closes ticket 32451.
540 - Allow test_parseconf.sh to test expected log outputs for successful
541 configs, as well as failed configs. Closes ticket 32451.
542 - The test_parseconf.sh script now supports result variants for any
543 combination of the optional libraries lzma, nss, and zstd. Closes
545 - When running the unit tests on Android, create temporary files in
546 a subdirectory of /data/local/tmp. Closes ticket 32172. Based on a
547 patch from Hans-Christoph Steiner.
549 o Minor features (usability):
550 - Include more information when failing to parse a configuration
551 value. This should make it easier to tell what's going wrong when
552 a configuration file doesn't parse. Closes ticket 33460.
554 o Minor bugfix (relay, configuration):
555 - Warn if the ContactInfo field is not set, and tell the relay
556 operator that not having a ContactInfo field set might cause their
557 relay to get rejected in the future. Fixes bug 33361; bugfix
560 o Minor bugfixes (bridges):
561 - Lowercase the configured value of BridgeDistribution before adding
562 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
564 o Minor bugfixes (build system):
565 - Fix "make autostyle" for out-of-tree builds. Fixes bug 32370;
566 bugfix on 0.4.1.2-alpha.
568 o Minor bugfixes (compiler compatibility):
569 - Avoid compiler warnings from Clang 10 related to the use of GCC-
570 style "/* falls through */" comments. Both Clang and GCC allow
571 __attribute__((fallthrough)) instead, so that's what we're using
572 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
573 - Fix compilation warnings with GCC 10.0.1. Fixes bug 34077; bugfix
576 o Minor bugfixes (configuration handling):
577 - Make control_event_conf_changed() take in a config_line_t instead
578 of a smartlist of alternating key/value entries. Fixes bug 31531;
579 bugfix on 0.2.3.3-alpha. Patch by Neel Chauhan.
580 - Check for multiplication overflow when parsing memory units inside
581 configuration. Fixes bug 30920; bugfix on 0.0.9rc1.
582 - When dumping the configuration, stop adding a trailing space after
583 the option name when there is no option value. This issue only
584 affects options that accept an empty value or list. (Most options
585 reject empty values, or delete the entire line from the dumped
586 options.) Fixes bug 32352; bugfix on 0.0.9pre6.
587 - Avoid changing the user's value of HardwareAccel as stored by
588 SAVECONF, when AccelName is set but HardwareAccel is not. Fixes
589 bug 32382; bugfix on 0.2.2.1-alpha.
590 - When creating a KeyDirectory with the same location as the
591 DataDirectory (not recommended), respect the DataDirectory's
592 group-readable setting if one has not been set for the
593 KeyDirectory. Fixes bug 27992; bugfix on 0.3.3.1-alpha.
595 o Minor bugfixes (continuous integration):
596 - Remove the buggy and unused mirroring job. Fixes bug 33213; bugfix
599 o Minor bugfixes (controller protocol):
600 - When receiving "ACTIVE" or "DORMANT" signals on the control port,
601 report them as SIGNAL events. Previously we would log a bug
602 warning. Fixes bug 33104; bugfix on 0.4.0.1-alpha.
604 o Minor bugfixes (controller):
605 - In routerstatus_has_changed(), check all the fields that are
606 output over the control port. Fixes bug 20218; bugfix
609 o Minor bugfixes (developer tools):
610 - Allow paths starting with ./ in scripts/add_c_file.py. Fixes bug
611 31336; bugfix on 0.4.1.2-alpha.
613 o Minor bugfixes (dirauth module):
614 - Split the dirauth config code into a separate file in the dirauth
615 module. Disable this code when the dirauth module is disabled.
617 - When the dirauth module is disabled, reject attempts to set the
618 AuthoritativeDir option, rather than ignoring the value of the
619 option. Fixes bug 32213; bugfix on 0.3.4.1-alpha.
621 o Minor bugfixes (embedded Tor):
622 - When starting Tor any time after the first time in a process,
623 register the thread in which it is running as the main thread.
624 Previously, we only did this on Windows, which could lead to bugs
625 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
628 o Minor bugfixes (git scripts):
629 - Avoid sleeping before the last push in git-push-all.sh. Closes
631 - Forward all unrecognised arguments in git-push-all.sh to git push.
634 o Minor bugfixes (key portability):
635 - When reading PEM-encoded key data, tolerate CRLF line-endings even
636 if we are not running on Windows. Previously, non-Windows hosts
637 would reject these line-endings in certain positions, making
638 certain key files hard to move from one host to another. Fixes bug
639 33032; bugfix on 0.3.5.1-alpha.
641 o Minor bugfixes (logging):
642 - Stop truncating IPv6 addresses and ports in channel and connection
643 logs. Fixes bug 33918; bugfix on 0.2.4.4-alpha.
644 - Flush stderr, stdout, and file logs during shutdown, if supported
645 by the OS. This change helps make sure that any final logs are
646 recorded. Fixes bug 33087; bugfix on 0.4.1.6.
647 - Stop closing stderr and stdout during shutdown. Closing these file
648 descriptors can hide sanitiser logs. Fixes bug 33087; bugfix
650 - If we encounter a bug when flushing a buffer to a TLS connection,
651 only log the bug once per invocation of the Tor process.
652 Previously we would log with every occurrence, which could cause
653 us to run out of disk space. Fixes bug 33093; bugfix
655 - When logging a bug, do not say "Future instances of this warning
656 will be silenced" unless we are actually going to silence them.
657 Previously we would say this whenever a BUG() check failed in the
658 code. Fixes bug 33095; bugfix on 0.4.1.1-alpha.
660 o Minor bugfixes (onion services v2):
661 - Move a series of v2 onion service warnings to protocol-warning
662 level because they can all be triggered remotely by a malformed
663 request. Fixes bug 32706; bugfix on 0.1.1.14-alpha.
664 - When sending the INTRO cell for a v2 Onion Service, look at the
665 failure cache alongside timeout values to check if the intro point
666 is marked as failed. Previously, we only looked at the relay
667 timeout values. Fixes bug 25568; bugfix on 0.2.7.3-rc. Patch by
670 o Minor bugfixes (onion services v3):
671 - Remove a BUG() warning that would cause a stack trace if an onion
672 service descriptor was freed while we were waiting for a
673 rendezvous circuit to complete. Fixes bug 28992; bugfix
675 - Relax severity of a log message that can appear naturally when
676 decoding onion service descriptors as a relay. Also add some
677 diagnostics to debug any future bugs in that area. Fixes bug
678 31669; bugfix on 0.3.0.1-alpha.
679 - Fix an assertion failure that could result from a corrupted
680 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
681 bugfix on 0.3.3.1-alpha. This issue is also tracked
683 - Properly handle the client rendezvous circuit timeout. Previously
684 Tor would sometimes timeout a rendezvous circuit awaiting the
685 introduction ACK, and find itself unable to re-establish all
686 circuits because the rendezvous circuit timed out too early. Fixes
687 bug 32021; bugfix on 0.3.2.1-alpha.
689 o Minor bugfixes (onion services):
690 - Do not rely on a "circuit established" flag for intro circuits but
691 instead always query the HS circuit map. This is to avoid sync
692 issue with that flag and the map. Fixes bug 32094; bugfix
695 o Minor bugfixes (onion services, all):
696 - In cancel_descriptor_fetches(), use
697 connection_list_by_type_purpose() instead of
698 connection_list_by_type_state(). Fixes bug 32639; bugfix on
699 0.3.2.1-alpha. Patch by Neel Chauhan.
701 o Minor bugfixes (pluggable transports):
702 - When receiving a message on standard error from a pluggable
703 transport, log it at info level, rather than as a warning. Fixes
704 bug 33005; bugfix on 0.4.0.1-alpha.
706 o Minor bugfixes (rust, build):
707 - Fix a syntax warning given by newer versions of Rust that was
708 creating problems for our continuous integration. Fixes bug 33212;
709 bugfix on 0.3.5.1-alpha.
711 o Minor bugfixes (scripts):
712 - Fix update_versions.py for out-of-tree builds. Fixes bug 32371;
713 bugfix on 0.4.0.1-alpha.
715 o Minor bugfixes (testing):
716 - Use the same code to find the tor binary in all of our test
717 scripts. This change makes sure we are always using the coverage
718 binary when coverage is enabled. Fixes bug 32368; bugfix
720 - Stop ignoring "tor --dump-config" errors in test_parseconf.sh.
721 Fixes bug 32468; bugfix on 0.4.2.1-alpha.
722 - Our option-validation tests no longer depend on specially
723 configured non-default, non-passing sets of options. Previously,
724 the tests had been written to assume that options would _not_ be
725 set to their defaults, which led to needless complexity and
726 verbosity. Fixes bug 32175; bugfix on 0.2.8.1-alpha.
728 o Minor bugfixes (TLS bug handling):
729 - When encountering a bug in buf_read_from_tls(), return a "MISC"
730 error code rather than "WANTWRITE". This change might help avoid
731 some CPU-wasting loops if the bug is ever triggered. Bug reported
732 by opara. Fixes bug 32673; bugfix on 0.3.0.4-alpha.
734 o Deprecated features:
735 - Deprecate the ClientAutoIPv6ORPort option. This option was not
736 true "Happy Eyeballs", and often failed on connections that
737 weren't reliably dual-stack. Closes ticket 32942. Patch by
741 - Provide a quickstart guide for a Circuit Padding Framework, and
742 documentation for researchers to implement and study circuit
743 padding machines. Closes ticket 28804.
744 - Add documentation in 'HelpfulTools.md' to describe how to build a
745 tag file. Closes ticket 32779.
746 - Create a high-level description of the long-term software
747 architecture goals. Closes ticket 32206.
748 - Describe the --dump-config command in the manual page. Closes
750 - Unite coding advice from this_not_that.md in torguts repo into our
751 coding standards document. Resolves ticket 31853.
754 - Our Doxygen configuration no longer generates LaTeX output. The
755 reference manual produced by doing this was over 4000 pages long,
756 and generally unusable. Closes ticket 32099.
757 - The option "TestingEstimatedDescriptorPropagationTime" is now
758 marked as obsolete. It has had no effect since 0.3.0.7, when
759 clients stopped rejecting consensuses "from the future". Closes
761 - We no longer support consensus methods before method 28; these
762 methods were only used by authorities running versions of Tor that
763 are now at end-of-life. In effect, this means that clients,
764 relays, and authorities now assume that authorities will be
765 running version 0.3.5.x or later. Closes ticket 32695.
768 - Avoid conflicts between the fake sockets in tor's unit tests, and
769 real file descriptors. Resolves issues running unit tests with
770 GitHub Actions, where the process that embeds or launches the
771 tests has already opened a large number of file descriptors. Fixes
772 bug 33782; bugfix on 0.2.8.1-alpha. Found and fixed by
774 - Add more test cases for tor's UTF-8 validation function. Also,
775 check the arguments passed to the function for consistency. Closes
777 - Improve test coverage for relay and dirauth config code, focusing
778 on option validation and normalization. Closes ticket 32213.
779 - Improve the consistency of test_parseconf.sh output, and run all
780 the tests, even if one fails. Closes ticket 32213.
781 - Run the practracker unit tests in the pre-commit git hook. Closes
784 o Code simplification and refactoring (channel):
785 - Channel layer had a variable length cell handler that was not used
786 and thus removed. Closes ticket 32892.
788 o Code simplification and refactoring (configuration):
789 - Immutability is now implemented as a flag on individual
790 configuration options rather than as part of the option-transition
791 checking code. Closes ticket 32344.
792 - Instead of keeping a list of configuration options to check for
793 relative paths, check all the options whose type is "FILENAME".
794 Solves part of ticket 32339.
795 - Our default log (which ordinarily sends NOTICE-level messages to
796 standard output) is now handled in a more logical manner.
797 Previously, we replaced the configured log options if they were
798 empty. Now, we interpret an empty set of log options as meaning
799 "use the default log". Closes ticket 31999.
800 - Remove some unused arguments from the options_validate() function,
801 to simplify our code and tests. Closes ticket 32187.
802 - Simplify the options_validate() code so that it looks at the
803 default options directly, rather than taking default options as an
804 argument. This change lets us simplify its interface. Closes
806 - Use our new configuration architecture to move most authority-
807 related options to the directory authority module. Closes
809 - When parsing the command line, handle options that determine our
810 "quiet level" and our mode of operation (e.g., --dump-config and
811 so on) all in one table. Closes ticket 32003.
813 o Code simplification and refactoring (controller):
814 - Create a new abstraction for formatting control protocol reply
815 lines based on key-value pairs. Refactor some existing control
816 protocol code to take advantage of this. Closes ticket 30984.
817 - Create a helper function that can fetch network status or
818 microdesc consensuses. Closes ticket 31684.
820 o Code simplification and refactoring (dirauth modularization):
821 - Remove the last remaining HAVE_MODULE_DIRAUTH inside a function.
823 - Replace some confusing identifiers in process_descs.c. Closes
825 - Simplify some relay and dirauth config code. Closes ticket 32213.
827 o Code simplification and refactoring (mainloop):
828 - Simplify the ip_address_changed() function by removing redundant
829 checks. Closes ticket 33091.
831 o Code simplification and refactoring (misc):
832 - Make all the structs we declare follow the same naming convention
833 of ending with "_t". Closes ticket 32415.
834 - Move and rename some configuration-related code for clarity.
836 - Our include.am files are now broken up by subdirectory.
837 Previously, src/core/include.am covered all of the subdirectories
838 in "core", "feature", and "app". Closes ticket 32137.
839 - Remove underused NS*() macros from test code: they make our tests
840 more confusing, especially for code-formatting tools. Closes
843 o Code simplification and refactoring (relay modularization):
844 - Disable relay_periodic when the relay module is disabled. Closes
846 - Disable relay_sys when the relay module is disabled. Closes
849 o Code simplification and refactoring (tool support):
850 - Add numerous missing dependencies to our include files, so that
851 they can be included in different reasonable orders and still
852 compile. Addresses part of ticket 32764.
853 - Fix some parts of our code that were difficult for Coccinelle to
854 parse. Related to ticket 31705.
855 - Fix some small issues in our code that prevented automatic
856 formatting tools from working. Addresses part of ticket 32764.
858 o Documentation (manpage):
859 - Alphabetize the Server and Directory server sections of the tor
860 manpage. Also split Statistics options into their own section of
861 the manpage. Closes ticket 33188. Work by Swati Thacker as part of
862 Google Season of Docs.
863 - Document the __OwningControllerProcess torrc option and specify
864 its polling interval. Resolves issue 32971.
865 - Split "Circuit Timeout" options and "Node Selection" options into
866 their own sections of the tor manpage. Closes tickets 32928 and
867 32929. Work by Swati Thacker as part of Google Season of Docs.
868 - Alphabetize the Client Options section of the tor manpage. Closes
870 - Alphabetize the General Options section of the tor manpage. Closes
872 - In the tor(1) manpage, reword and improve formatting of the
873 COMMAND-LINE OPTIONS and DESCRIPTION sections. Closes ticket
874 32277. Based on work by Swati Thacker as part of Google Season
876 - In the tor(1) manpage, reword and improve formatting of the FILES,
877 SEE ALSO, and BUGS sections. Closes ticket 32176. Based on work by
878 Swati Thacker as part of Google Season of Docs.
880 o Testing (Appveyor CI):
881 - In our Appveyor Windows CI, copy required DLLs to test and app
882 directories, before running tor's tests. This ensures that tor.exe
883 and test*.exe use the correct version of each DLL. This fix is not
884 required, but we hope it will avoid DLL search issues in future.
885 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
886 - On Appveyor, skip the crypto/openssl_version test, which is
887 failing because of a mismatched library installation. Fix
890 o Testing (circuit, EWMA):
891 - Add unit tests for circuitmux and EWMA subsystems. Closes
894 o Testing (Travis CI):
895 - Remove a redundant distcheck job. Closes ticket 33194.
896 - Sort the Travis jobs in order of speed: putting the slowest jobs
897 first takes full advantage of Travis job concurrency. Closes
899 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
900 previously configured to fast_finish (which requires
901 allow_failure), to speed up the build. Closes ticket 33195.
902 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
903 tool to produce detailed diagnostic output. Closes ticket 32792.
906 Changes in version 0.4.2.7 - 2020-03-18
907 This is the third stable release in the 0.4.2.x series. It backports
908 numerous fixes from later releases, including a fix for TROVE-2020-
909 002, a major denial-of-service vulnerability that affected all
910 released Tor instances since 0.2.1.5-alpha. Using this vulnerability,
911 an attacker could cause Tor instances to consume a huge amount of CPU,
912 disrupting their operations for several seconds or minutes. This
913 attack could be launched by anybody against a relay, or by a directory
914 cache against any client that had connected to it. The attacker could
915 launch this attack as much as they wanted, thereby disrupting service
916 or creating patterns that could aid in traffic analysis. This issue
917 was found by OSS-Fuzz, and is also tracked as CVE-2020-10592.
919 We do not have reason to believe that this attack is currently being
920 exploited in the wild, but nonetheless we advise everyone to upgrade
921 as soon as packages are available.
923 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
924 - Fix a denial-of-service bug that could be used by anyone to
925 consume a bunch of CPU on any Tor relay or authority, or by
926 directories to consume a bunch of CPU on clients or hidden
927 services. Because of the potential for CPU consumption to
928 introduce observable timing patterns, we are treating this as a
929 high-severity security issue. Fixes bug 33119; bugfix on
930 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
931 as TROVE-2020-002 and CVE-2020-10592.
933 o Major bugfixes (circuit padding, memory leak, backport from 0.4.3.3-alpha):
934 - Avoid a remotely triggered memory leak in the case that a circuit
935 padding machine is somehow negotiated twice on the same circuit.
936 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
937 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
939 o Major bugfixes (directory authority, backport from 0.4.3.3-alpha):
940 - Directory authorities will now send a 503 (not enough bandwidth)
941 code to clients when under bandwidth pressure. Known relays and
942 other authorities will always be answered regardless of the
943 bandwidth situation. Fixes bug 33029; bugfix on 0.1.2.5-alpha.
945 o Minor features (continuous integration, backport from 0.4.3.2-alpha):
946 - Stop allowing failures on the Travis CI stem tests job. It looks
947 like all the stem hangs we were seeing before are now fixed.
950 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
951 - Lowercase the configured value of BridgeDistribution before adding
952 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
954 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
955 - If we encounter a bug when flushing a buffer to a TLS connection,
956 only log the bug once per invocation of the Tor process.
957 Previously we would log with every occurrence, which could cause
958 us to run out of disk space. Fixes bug 33093; bugfix
961 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
962 - Fix an assertion failure that could result from a corrupted
963 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
964 bugfix on 0.3.3.1-alpha. This issue is also tracked
967 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
968 - Fix a syntax warning given by newer versions of Rust that was
969 creating problems for our continuous integration. Fixes bug 33212;
970 bugfix on 0.3.5.1-alpha.
972 o Testing (Travis CI, backport from 0.4.3.3-alpha):
973 - Remove a redundant distcheck job. Closes ticket 33194.
974 - Sort the Travis jobs in order of speed: putting the slowest jobs
975 first takes full advantage of Travis job concurrency. Closes
977 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
978 previously configured to fast_finish (which requires
979 allow_failure), to speed up the build. Closes ticket 33195.
980 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
981 tool to produce detailed diagnostic output. Closes ticket 32792.
984 Changes in version 0.4.1.9 - 2020-03-18
985 Tor 0.4.1.9 backports important fixes from later Tor releases,
986 including a fix for TROVE-2020-002, a major denial-of-service
987 vulnerability that affected all released Tor instances since
988 0.2.1.5-alpha. Using this vulnerability, an attacker could cause Tor
989 instances to consume a huge amount of CPU, disrupting their operations
990 for several seconds or minutes. This attack could be launched by
991 anybody against a relay, or by a directory cache against any client
992 that had connected to it. The attacker could launch this attack as
993 much as they wanted, thereby disrupting service or creating patterns
994 that could aid in traffic analysis. This issue was found by OSS-Fuzz,
995 and is also tracked as CVE-2020-10592.
997 We do not have reason to believe that this attack is currently being
998 exploited in the wild, but nonetheless we advise everyone to upgrade
999 as soon as packages are available.
1001 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
1002 - Fix a denial-of-service bug that could be used by anyone to
1003 consume a bunch of CPU on any Tor relay or authority, or by
1004 directories to consume a bunch of CPU on clients or hidden
1005 services. Because of the potential for CPU consumption to
1006 introduce observable timing patterns, we are treating this as a
1007 high-severity security issue. Fixes bug 33119; bugfix on
1008 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
1009 as TROVE-2020-002 and CVE-2020-10592.
1011 o Major bugfixes (circuit padding, memory leak, backport from 0.4.3.3-alpha):
1012 - Avoid a remotely triggered memory leak in the case that a circuit
1013 padding machine is somehow negotiated twice on the same circuit.
1014 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
1015 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
1017 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
1018 - Lowercase the configured value of BridgeDistribution before adding
1019 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
1021 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
1022 - If we encounter a bug when flushing a buffer to a TLS connection,
1023 only log the bug once per invocation of the Tor process.
1024 Previously we would log with every occurrence, which could cause
1025 us to run out of disk space. Fixes bug 33093; bugfix
1028 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
1029 - Fix an assertion failure that could result from a corrupted
1030 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
1031 bugfix on 0.3.3.1-alpha. This issue is also tracked
1034 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
1035 - Fix a syntax warning given by newer versions of Rust that was
1036 creating problems for our continuous integration. Fixes bug 33212;
1037 bugfix on 0.3.5.1-alpha.
1039 o Testing (Travis CI, backport from 0.4.3.3-alpha):
1040 - Remove a redundant distcheck job. Closes ticket 33194.
1041 - Sort the Travis jobs in order of speed: putting the slowest jobs
1042 first takes full advantage of Travis job concurrency. Closes
1044 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
1045 previously configured to fast_finish (which requires
1046 allow_failure), to speed up the build. Closes ticket 33195.
1047 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
1048 tool to produce detailed diagnostic output. Closes ticket 32792.
1051 Changes in version 0.3.5.10 - 2020-03-18
1052 Tor 0.3.5.10 backports many fixes from later Tor releases, including a
1053 fix for TROVE-2020-002, a major denial-of-service vulnerability that
1054 affected all released Tor instances since 0.2.1.5-alpha. Using this
1055 vulnerability, an attacker could cause Tor instances to consume a huge
1056 amount of CPU, disrupting their operations for several seconds or
1057 minutes. This attack could be launched by anybody against a relay, or
1058 by a directory cache against any client that had connected to it. The
1059 attacker could launch this attack as much as they wanted, thereby
1060 disrupting service or creating patterns that could aid in traffic
1061 analysis. This issue was found by OSS-Fuzz, and is also tracked
1064 We do not have reason to believe that this attack is currently being
1065 exploited in the wild, but nonetheless we advise everyone to upgrade
1066 as soon as packages are available.
1068 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
1069 - Fix a denial-of-service bug that could be used by anyone to
1070 consume a bunch of CPU on any Tor relay or authority, or by
1071 directories to consume a bunch of CPU on clients or hidden
1072 services. Because of the potential for CPU consumption to
1073 introduce observable timing patterns, we are treating this as a
1074 high-severity security issue. Fixes bug 33119; bugfix on
1075 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
1076 as TROVE-2020-002 and CVE-2020-10592.
1078 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
1079 - Correct how we use libseccomp. Particularly, stop assuming that
1080 rules are applied in a particular order or that more rules are
1081 processed after the first match. Neither is the case! In
1082 libseccomp <2.4.0 this lead to some rules having no effect.
1083 libseccomp 2.4.0 changed how rules are generated, leading to a
1084 different ordering, which in turn led to a fatal crash during
1085 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
1088 o Minor features (continuous integration, backport from 0.4.3.2-alpha):
1089 - Stop allowing failures on the Travis CI stem tests job. It looks
1090 like all the stem hangs we were seeing before are now fixed.
1091 Closes ticket 33075.
1093 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
1094 - Lowercase the configured value of BridgeDistribution before adding
1095 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
1097 o Minor bugfixes (crash, backport from 0.4.2.4-rc):
1098 - When running Tor with an option like --verify-config or
1099 --dump-config that does not start the event loop, avoid crashing
1100 if we try to exit early because of an error. Fixes bug 32407;
1101 bugfix on 0.3.3.1-alpha.
1103 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
1104 - If we encounter a bug when flushing a buffer to a TLS connection,
1105 only log the bug once per invocation of the Tor process.
1106 Previously we would log with every occurrence, which could cause
1107 us to run out of disk space. Fixes bug 33093; bugfix
1110 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
1111 - Fix an assertion failure that could result from a corrupted
1112 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
1113 bugfix on 0.3.3.1-alpha. This issue is also tracked
1116 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
1117 - Fix a syntax warning given by newer versions of Rust that was
1118 creating problems for our continuous integration. Fixes bug 33212;
1119 bugfix on 0.3.5.1-alpha.
1121 o Testing (backport from 0.4.3.1-alpha):
1122 - Re-enable the Travis CI macOS Chutney build, but don't let it
1123 prevent the Travis job from finishing. (The Travis macOS jobs are
1124 slow, so we don't want to have it delay the whole CI process.)
1125 Closes ticket 32629.
1126 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
1127 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
1128 fix the sandbox errors in 32722. Closes ticket 32240.
1130 o Testing (continuous integration, backport from 0.4.3.1-alpha):
1131 - Use zstd in our Travis Linux builds. Closes ticket 32242.
1133 o Testing (Travis CI, backport from 0.4.3.3-alpha):
1134 - Remove a redundant distcheck job. Closes ticket 33194.
1135 - Sort the Travis jobs in order of speed: putting the slowest jobs
1136 first takes full advantage of Travis job concurrency. Closes
1138 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
1139 previously configured to fast_finish (which requires
1140 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
1141 tool to produce detailed diagnostic output. Closes ticket 32792.
1144 Changes in version 0.4.2.6 - 2020-01-30
1145 This is the second stable release in the 0.4.2.x series. It backports
1146 several bugfixes from 0.4.3.1-alpha, including some that had affected
1147 the Linux seccomp2 sandbox or Windows services. If you're running with
1148 one of those configurations, you'll probably want to upgrade;
1149 otherwise, you should be fine with 0.4.2.5.
1151 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
1152 - Correct how we use libseccomp. Particularly, stop assuming that
1153 rules are applied in a particular order or that more rules are
1154 processed after the first match. Neither is the case! In
1155 libseccomp <2.4.0 this led to some rules having no effect.
1156 libseccomp 2.4.0 changed how rules are generated, leading to a
1157 different ordering, which in turn led to a fatal crash during
1158 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
1160 - Fix crash when reloading logging configuration while the
1161 experimental sandbox is enabled. Fixes bug 32841; bugfix on
1162 0.4.1.7. Patch by Peter Gerber.
1164 o Minor bugfixes (correctness checks, backport from 0.4.3.1-alpha):
1165 - Use GCC/Clang's printf-checking feature to make sure that
1166 tor_assertf() arguments are correctly typed. Fixes bug 32765;
1167 bugfix on 0.4.1.1-alpha.
1169 o Minor bugfixes (logging, crash, backport from 0.4.3.1-alpha):
1170 - Avoid a possible crash when trying to log a (fatal) assertion
1171 failure about mismatched magic numbers in configuration objects.
1172 Fixes bug 32771; bugfix on 0.4.2.1-alpha.
1174 o Minor bugfixes (testing, backport from 0.4.3.1-alpha):
1175 - When TOR_DISABLE_PRACTRACKER is set, do not apply it to the
1176 test_practracker.sh script. Doing so caused a test failure. Fixes
1177 bug 32705; bugfix on 0.4.2.1-alpha.
1178 - When TOR_DISABLE_PRACTRACKER is set, log a notice to stderr when
1179 skipping practracker checks. Fixes bug 32705; bugfix
1182 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
1183 - Initialize the publish/subscribe system when running as a windows
1184 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
1186 o Testing (backport from 0.4.3.1-alpha):
1187 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
1188 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
1189 fix the sandbox errors in 32722. Closes ticket 32240.
1190 - Re-enable the Travis CI macOS Chutney build, but don't let it
1191 prevent the Travis job from finishing. (The Travis macOS jobs are
1192 slow, so we don't want to have it delay the whole CI process.)
1193 Closes ticket 32629.
1195 o Testing (continuous integration, backport from 0.4.3.1-alpha):
1196 - Use zstd in our Travis Linux builds. Closes ticket 32242.
1199 Changes in version 0.4.1.8 - 2020-01-30
1200 This release backports several bugfixes from later release series,
1201 including some that had affected the Linux seccomp2 sandbox or Windows
1202 services. If you're running with one of those configurations, you'll
1203 probably want to upgrade; otherwise, you should be fine with your
1204 current version of 0.4.1.x.
1206 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
1207 - Correct how we use libseccomp. Particularly, stop assuming that
1208 rules are applied in a particular order or that more rules are
1209 processed after the first match. Neither is the case! In
1210 libseccomp <2.4.0 this led to some rules having no effect.
1211 libseccomp 2.4.0 changed how rules are generated, leading to a
1212 different ordering, which in turn led to a fatal crash during
1213 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
1215 - Fix crash when reloading logging configuration while the
1216 experimental sandbox is enabled. Fixes bug 32841; bugfix on
1217 0.4.1.7. Patch by Peter Gerber.
1219 o Minor bugfixes (crash, backport form 0.4.2.4-rc):
1220 - When running Tor with an option like --verify-config or
1221 --dump-config that does not start the event loop, avoid crashing
1222 if we try to exit early because of an error. Fixes bug 32407;
1223 bugfix on 0.3.3.1-alpha.
1225 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
1226 - Initialize the publish/subscribe system when running as a windows
1227 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
1229 o Testing (backport from 0.4.3.1-alpha):
1230 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
1231 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
1232 fix the sandbox errors in 32722. Closes ticket 32240.
1233 - Re-enable the Travis CI macOS Chutney build, but don't let it
1234 prevent the Travis job from finishing. (The Travis macOS jobs are
1235 slow, so we don't want to have it delay the whole CI process.)
1236 Closes ticket 32629.
1238 o Testing (continuous integration, backport from 0.4.3.1-alpha):
1239 - Use zstd in our Travis Linux builds. Closes ticket 32242.
1242 Changes in version 0.4.2.5 - 2019-12-09
1243 This is the first stable release in the 0.4.2.x series. This series
1244 improves reliability and stability, and includes several stability and
1245 correctness improvements for onion services. It also fixes many smaller
1246 bugs present in previous series.
1248 Per our support policy, we will support the 0.4.2.x series for nine
1249 months, or until three months after the release of a stable 0.4.3.x:
1250 whichever is longer. If you need longer-term support, please stick
1251 with 0.3.5.x, which will we plan to support until Feb 2022.
1253 Below are the changes since 0.4.1.4-rc. For a complete list of only
1254 the changes since 0.4.2.4-rc, see the ChangeLog file.
1256 o Major features (directory authorities):
1257 - Directory authorities now reject relays running all currently
1258 deprecated release series. The currently supported release series
1259 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
1261 o Major features (onion service v3, denial of service):
1262 - Add onion service introduction denial of service defenses. Intro
1263 points can now rate-limit client introduction requests, using
1264 parameters that can be sent by the service within the
1265 ESTABLISH_INTRO cell. If the cell extension for this is not used,
1266 the intro point will honor the consensus parameters. Closes
1269 o Major bugfixes (circuit build, guard):
1270 - When considering upgrading circuits from "waiting for guard" to
1271 "open", always ignore circuits that are marked for close.
1272 Previously we could end up in the situation where a subsystem is
1273 notified of a circuit opening, but the circuit is still marked for
1274 close, leading to undesirable behavior. Fixes bug 30871; bugfix
1277 o Major bugfixes (crash, Linux, Android):
1278 - Tolerate systems (including some Android installations) where
1279 madvise and MADV_DONTDUMP are available at build-time, but not at
1280 run time. Previously, these systems would notice a failed syscall
1281 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
1282 - Tolerate systems (including some Linux installations) where
1283 madvise and/or MADV_DONTFORK are available at build-time, but not
1284 at run time. Previously, these systems would notice a failed
1285 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
1287 o Major bugfixes (embedded Tor):
1288 - Avoid a possible crash when restarting Tor in embedded mode and
1289 enabling a different set of publish/subscribe messages. Fixes bug
1290 31898; bugfix on 0.4.1.1-alpha.
1292 o Major bugfixes (relay):
1293 - Relays now respect their AccountingMax bandwidth again. When
1294 relays entered "soft" hibernation (which typically starts when
1295 we've hit 90% of our AccountingMax), we had stopped checking
1296 whether we should enter hard hibernation. Soft hibernation refuses
1297 new connections and new circuits, but the existing circuits can
1298 continue, meaning that relays could have exceeded their configured
1299 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
1301 o Major bugfixes (torrc parsing):
1302 - Stop ignoring torrc options after an %include directive, when the
1303 included directory ends with a file that does not contain any
1304 config options (but does contain comments or whitespace). Fixes
1305 bug 31408; bugfix on 0.3.1.1-alpha.
1307 o Major bugfixes (v3 onion services):
1308 - Onion services now always use the exact number of intro points
1309 configured with the HiddenServiceNumIntroductionPoints option (or
1310 fewer if nodes are excluded). Before, a service could sometimes
1311 pick more intro points than configured. Fixes bug 31548; bugfix
1314 o Minor feature (onion services, control port):
1315 - The ADD_ONION command's keyword "BEST" now defaults to ED25519-V3
1316 (v3) onion services. Previously it defaulted to RSA1024 (v2).
1317 Closes ticket 29669.
1319 o Minor features (auto-formatting scripts):
1320 - When annotating C macros, never generate a line that our check-
1321 spaces script would reject. Closes ticket 31759.
1322 - When annotating C macros, try to remove cases of double-negation.
1323 Closes ticket 31779.
1325 o Minor features (best practices tracker):
1326 - Our best-practices tracker now integrates with our include-checker
1327 tool to keep track of how many layering violations we have not yet
1328 fixed. We hope to reduce this number over time to improve Tor's
1329 modularity. Closes ticket 31176.
1330 - Add a TOR_PRACTRACKER_OPTIONS variable for passing arguments to
1331 practracker from the environment. We may want this for continuous
1332 integration. Closes ticket 31309.
1333 - Give a warning rather than an error when a practracker exception
1334 is violated by a small amount, add a --list-overbroad option to
1335 practracker that lists exceptions that are stricter than they need
1336 to be, and provide an environment variable for disabling
1337 practracker. Closes ticket 30752.
1338 - Our best-practices tracker now looks at headers as well as C
1339 files. Closes ticket 31175.
1341 o Minor features (build system):
1342 - Make pkg-config use --prefix when cross-compiling, if
1343 PKG_CONFIG_PATH is not set. Closes ticket 32191.
1344 - Add --disable-manpage and --disable-html-manual options to
1345 configure script. This will enable shortening build times by not
1346 building documentation. Resolves issue 19381.
1348 o Minor features (compilation):
1349 - Log a more useful error message when we are compiling and one of
1350 the compile-time hardening options we have selected can be linked
1351 but not executed. Closes ticket 27530.
1353 o Minor features (configuration):
1354 - The configuration code has been extended to allow splitting
1355 configuration data across multiple objects. Previously, all
1356 configuration data needed to be kept in a single object, which
1357 tended to become bloated. Closes ticket 31240.
1359 o Minor features (continuous integration):
1360 - When building on Appveyor and Travis, pass the "-k" flag to make,
1361 so that we are informed of all compilation failures, not just the
1362 first one or two. Closes ticket 31372.
1363 - When running CI builds on Travis, put some random data in
1364 ~/.torrc, to make sure no tests are reading the Tor configuration
1365 file from its default location. Resolves issue 30102.
1367 o Minor features (debugging):
1368 - Log a nonfatal assertion failure if we encounter a configuration
1369 line whose command is "CLEAR" but which has a nonempty value. This
1370 should be impossible, according to the rules of our configuration
1371 line parsing. Closes ticket 31529.
1373 o Minor features (geoip):
1374 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
1375 Country database. Closes ticket 32685.
1377 o Minor features (git hooks):
1378 - Our pre-commit git hook now checks for a special file before
1379 running practracker, so that practracker only runs on branches
1380 that are based on master. Since the pre-push hook calls the pre-
1381 commit hook, practracker will also only run before pushes of
1382 branches based on master. Closes ticket 30979.
1384 o Minor features (git scripts):
1385 - Add a "--" command-line argument, to separate git-push-all.sh
1386 script arguments from arguments that are passed through to git
1387 push. Closes ticket 31314.
1388 - Add a -r <remote-name> argument to git-push-all.sh, so the script
1389 can push test branches to a personal remote. Closes ticket 31314.
1390 - Add a -t <test-branch-prefix> argument to git-merge-forward.sh and
1391 git-push-all.sh, which makes these scripts create, merge forward,
1392 and push test branches. Closes ticket 31314.
1393 - Add a -u argument to git-merge-forward.sh, so that the script can
1394 re-use existing test branches after a merge failure and fix.
1395 Closes ticket 31314.
1396 - Add a TOR_GIT_PUSH env var, which sets the default git push
1397 command and arguments for git-push-all.sh. Closes ticket 31314.
1398 - Add a TOR_PUSH_DELAY variable to git-push-all.sh, which makes the
1399 script push master and maint branches with a delay between each
1400 branch. These delays trigger the CI jobs in a set order, which
1401 should show the most likely failures first. Also make pushes
1402 atomic by default, and make the script pass any command-line
1403 arguments to git push. Closes ticket 29879.
1404 - Call the shellcheck script from the pre-commit hook. Closes
1406 - Skip pushing test branches that are the same as a remote
1407 maint/release/master branch in git-push-all.sh by default. Add a
1408 -s argument, so git-push-all.sh can push all test branches. Closes
1411 o Minor features (IPv6, logging):
1412 - Log IPv6 addresses as well as IPv4 addresses when describing
1413 routerinfos, routerstatuses, and nodes. Closes ticket 21003.
1415 o Minor features (maintenance scripts):
1416 - Add a Coccinelle script to detect bugs caused by incrementing or
1417 decrementing a variable inside a call to log_debug(). Since
1418 log_debug() is a macro whose arguments are conditionally
1419 evaluated, it is usually an error to do this. One such bug was
1420 30628, in which SENDME cells were miscounted by a decrement
1421 operator inside a log_debug() call. Closes ticket 30743.
1423 o Minor features (onion service v3):
1424 - Do not allow single hop clients to fetch or post an HS descriptor
1425 from an HSDir. Closes ticket 24964.
1427 o Minor features (onion service):
1428 - Disallow single-hop clients at the introduction point. We've
1429 removed Tor2web support a while back and single-hop rendezvous
1430 attempts are blocked at the relays. This change should remove load
1431 off the network from spammy clients. Close ticket 24963.
1433 o Minor features (onion services v3):
1434 - Assist users who try to setup v2 client authorization in v3 onion
1435 services by pointing them to the right documentation. Closes
1438 o Minor features (stem tests):
1439 - Change "make test-stem" so it only runs the stem tests that use
1440 tor. This change makes test-stem faster and more reliable. Closes
1443 o Minor features (testing):
1444 - When running tests that attempt to look up hostnames, replace the
1445 libc name lookup functions with ones that do not actually touch
1446 the network. This way, the tests complete more quickly in the
1447 presence of a slow or missing DNS resolver. Closes ticket 31841.
1448 - Add a script to invoke "tor --dump-config" and "tor
1449 --verify-config" with various configuration options, and see
1450 whether tor's resulting configuration or error messages are what
1451 we expect. Use it for integration testing of our +Option and
1452 /Option flags. Closes ticket 31637.
1453 - Improve test coverage for our existing configuration parsing and
1454 management API. Closes ticket 30893.
1455 - Add integration tests to make sure that practracker gives the
1456 outputs we expect. Closes ticket 31477.
1457 - The practracker self-tests are now run as part of the Tor test
1458 suite. Closes ticket 31304.
1460 o Minor features (testing, continuous integration):
1461 - Disable all but one Travis CI macOS build, to mitigate slow
1462 scheduling of Travis macOS jobs. Closes ticket 32177.
1463 - Run the chutney IPv6 networks as part of Travis CI. Closes
1465 - Simplify the Travis CI build matrix, and optimise for build time.
1466 Closes ticket 31859.
1467 - Use Windows Server 2019 instead of Windows Server 2016 in our
1468 Appveyor builds. Closes ticket 32086.
1470 o Minor features (token bucket):
1471 - Implement a generic token bucket that uses a single counter, for
1472 use in anti-DoS onion service work. Closes ticket 30687.
1474 o Minor bugfixes (Appveyor continuous integration):
1475 - Avoid spurious errors when Appveyor CI fails before the install
1476 step. Fixes bug 31884; bugfix on 0.3.4.2-alpha.
1478 o Minor bugfixes (best practices tracker):
1479 - Fix a few issues in the best-practices script, including tests,
1480 tab tolerance, error reporting, and directory-exclusion logic.
1481 Fixes bug 29746; bugfix on 0.4.1.1-alpha.
1482 - When running check-best-practices, only consider files in the src
1483 subdirectory. Previously we had recursively considered all
1484 subdirectories, which made us get confused by the temporary
1485 directories made by "make distcheck". Fixes bug 31578; bugfix
1488 o Minor bugfixes (build system):
1489 - Interpret "--disable-module-dirauth=no" correctly. Fixes bug
1490 32124; bugfix on 0.3.4.1-alpha.
1491 - Interpret "--with-tcmalloc=no" correctly. Fixes bug 32124; bugfix
1493 - Stop failing when jemalloc is requested, but tcmalloc is not
1494 found. Fixes bug 32124; bugfix on 0.3.5.1-alpha.
1495 - When pkg-config is not installed, or a library that depends on
1496 pkg-config is not found, tell the user what to do to fix the
1497 problem. Fixes bug 31922; bugfix on 0.3.1.1-alpha.
1498 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
1499 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
1501 o Minor bugfixes (chutney, makefiles, documentation):
1502 - "make test-network-all" now shows the warnings from each test-
1503 network.sh run on the console, so developers see new warnings
1504 early. We've also improved the documentation for this feature, and
1505 renamed a Makefile variable so the code is self-documenting. Fixes
1506 bug 30455; bugfix on 0.3.0.4-rc.
1508 o Minor bugfixes (client, onion service v3):
1509 - Fix a BUG() assertion that occurs within a very small race window
1510 between when a client intro circuit opens and when its descriptor
1511 gets cleaned up from the cache. The circuit is now closed early,
1512 which will trigger a re-fetch of the descriptor and continue the
1513 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
1515 o Minor bugfixes (code quality):
1516 - Fix "make check-includes" so it runs correctly on out-of-tree
1517 builds. Fixes bug 31335; bugfix on 0.3.5.1-alpha.
1519 o Minor bugfixes (compilation):
1520 - Add more stub functions to fix compilation on Android with link-
1521 time optimization when --disable-module-dirauth is used.
1522 Previously, these compilation settings would make the compiler
1523 look for functions that didn't exist. Fixes bug 31552; bugfix
1525 - Suppress spurious float-conversion warnings from GCC when calling
1526 floating-point classifier functions on FreeBSD. Fixes part of bug
1527 31687; bugfix on 0.3.1.5-alpha.
1529 o Minor bugfixes (configuration):
1530 - Invalid floating-point values in the configuration file are now
1531 treated as errors in the configuration. Previously, they were
1532 ignored and treated as zero. Fixes bug 31475; bugfix on 0.0.1.
1534 o Minor bugfixes (connections):
1535 - Avoid trying to read data from closed connections, which can cause
1536 needless loops in Libevent and infinite loops in Shadow. Fixes bug
1537 30344; bugfix on 0.1.1.1-alpha.
1539 o Minor bugfixes (controller protocol):
1540 - Fix the MAPADDRESS controller command to accept one or more
1541 arguments. Previously, it required two or more arguments, and
1542 ignored the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
1544 o Minor bugfixes (coverity):
1545 - Add an assertion when parsing a BEGIN cell so that coverity can be
1546 sure that we are not about to dereference a NULL address. Fixes
1547 bug 31026; bugfix on 0.2.4.7-alpha. This is CID 1447296.
1548 - In our siphash implementation, when building for coverity, use
1549 memcpy in place of a switch statement, so that coverity can tell
1550 we are not accessing out-of-bounds memory. Fixes bug 31025; bugfix
1551 on 0.2.8.1-alpha. This is tracked as CID 1447293 and 1447295.
1552 - Fix several coverity warnings from our unit tests. Fixes bug
1553 31030; bugfix on 0.2.4.1-alpha, 0.3.2.1-alpha, and 0.4.0.1-alpha.
1555 o Minor bugfixes (crash):
1556 - When running Tor with an option like --verify-config or
1557 --dump-config that does not start the event loop, avoid crashing
1558 if we try to exit early because of an error. Fixes bug 32407;
1559 bugfix on 0.3.3.1-alpha.
1561 o Minor bugfixes (developer tooling):
1562 - Only log git script changes in the post-merge script when the
1563 merge was to the master branch. Fixes bug 31040; bugfix
1566 o Minor bugfixes (directory authorities):
1567 - Return a distinct status when formatting annotations fails. Fixes
1568 bug 30780; bugfix on 0.2.0.8-alpha.
1570 o Minor bugfixes (error handling):
1571 - Always lock the backtrace buffer before it is used. Fixes bug
1572 31734; bugfix on 0.2.5.3-alpha.
1573 - On abort, try harder to flush the output buffers of log messages.
1574 On some platforms (macOS), log messages could be discarded when
1575 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1576 - Report the tor version whenever an assertion fails. Previously, we
1577 only reported the Tor version on some crashes, and some non-fatal
1578 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1579 - When tor aborts due to an error, close log file descriptors before
1580 aborting. Closing the logs makes some OSes flush log file buffers,
1581 rather than deleting buffered log lines. Fixes bug 31594; bugfix
1584 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6):
1585 - When extracting an IPv6 address from a PF-based proxy, verify that
1586 we are actually configured to receive an IPv6 address, and log an
1587 internal error if not. Fixes part of bug 31687; bugfix
1590 o Minor bugfixes (git hooks):
1591 - Remove a duplicate call to practracker from the pre-push hook. The
1592 pre-push hook already calls the pre-commit hook, which calls
1593 practracker. Fixes bug 31462; bugfix on 0.4.1.1-alpha.
1595 o Minor bugfixes (git scripts):
1596 - Stop hard-coding the bash path in the git scripts. Some OSes don't
1597 have bash in /usr/bin, others have an ancient bash at this path.
1598 Fixes bug 30840; bugfix on 0.4.0.1-alpha.
1599 - Stop hard-coding the tor master branch name and worktree path in
1600 the git scripts. Fixes bug 30841; bugfix on 0.4.0.1-alpha.
1601 - Allow git-push-all.sh to be run from any directory. Previously,
1602 the script only worked if run from an upstream worktree directory.
1603 Closes ticket 31678.
1605 o Minor bugfixes (guards):
1606 - When tor is missing descriptors for some primary entry guards,
1607 make the log message less alarming. It's normal for descriptors to
1608 expire, as long as tor fetches new ones soon after. Fixes bug
1609 31657; bugfix on 0.3.3.1-alpha.
1611 o Minor bugfixes (ipv6):
1612 - Check for private IPv6 addresses alongside their IPv4 equivalents
1613 when authorities check descriptors. Previously, we only checked
1614 for private IPv4 addresses. Fixes bug 31088; bugfix on
1615 0.2.3.21-rc. Patch by Neel Chauhan.
1616 - When parsing microdescriptors, we should check the IPv6 exit
1617 policy alongside IPv4. Previously, we checked both exit policies
1618 for only router info structures, while microdescriptors were
1619 IPv4-only. Fixes bug 27284; bugfix on 0.2.3.1-alpha. Patch by
1622 o Minor bugfixes (logging):
1623 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
1624 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
1625 - Disable backtrace signal handlers when shutting down tor. Fixes
1626 bug 31614; bugfix on 0.2.5.2-alpha.
1627 - Rate-limit our the logging message about the obsolete .exit
1628 notation. Previously, there was no limit on this warning, which
1629 could potentially be triggered many times by a hostile website.
1630 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
1631 - When initialising log domain masks, only set known log domains.
1632 Fixes bug 31854; bugfix on 0.2.1.1-alpha.
1633 - Change log level of message "Hash of session info was not as
1634 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
1636 - Fix a code issue that would have broken our parsing of log domains
1637 as soon as we had 33 of them. Fortunately, we still only have 29.
1638 Fixes bug 31451; bugfix on 0.4.1.4-rc.
1640 o Minor bugfixes (logging, protocol violations):
1641 - Do not log a nonfatal assertion failure when receiving a VERSIONS
1642 cell on a connection using the obsolete v1 link protocol. Log a
1643 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
1645 o Minor bugfixes (mainloop, periodic events, in-process API):
1646 - Reset the periodic events' "enabled" flag when Tor is shut down
1647 cleanly. Previously, this flag was left on, which caused periodic
1648 events not to be re-enabled when Tor was relaunched in-process
1649 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
1652 o Minor bugfixes (memory management):
1653 - Stop leaking a small amount of memory in nt_service_install(), in
1654 unreachable code. Fixes bug 30799; bugfix on 0.2.0.7-alpha. Patch
1657 o Minor bugfixes (modules):
1658 - Explain what the optional Directory Authority module is, and what
1659 happens when it is disabled. Fixes bug 31825; bugfix
1662 o Minor bugfixes (multithreading):
1663 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
1664 31736; bugfix on 0.0.7.
1666 o Minor bugfixes (networking, IP addresses):
1667 - When parsing addresses via Tor's internal DNS lookup API, reject
1668 IPv4 addresses in square brackets, and accept IPv6 addresses in
1669 square brackets. This change completes the work started in 23082,
1670 making address parsing consistent between tor's internal DNS
1671 lookup and address parsing APIs. Fixes bug 30721; bugfix
1673 - When parsing addresses via Tor's internal address:port parsing and
1674 DNS lookup APIs, require IPv6 addresses with ports to have square
1675 brackets. But allow IPv6 addresses without ports, whether or not
1676 they have square brackets. Fixes bug 30721; bugfix
1679 o Minor bugfixes (onion service v3):
1680 - When purging the client descriptor cache, close any introduction
1681 point circuits associated with purged cache entries. This avoids
1682 picking those circuits later when connecting to the same
1683 introduction points. Fixes bug 30921; bugfix on 0.3.2.1-alpha.
1685 o Minor bugfixes (onion services):
1686 - In the hs_ident_circuit_t data structure, remove the unused field
1687 circuit_type and the respective argument in hs_ident_circuit_new().
1688 This field was set by clients (for introduction) and services (for
1689 introduction and rendezvous) but was never used afterwards. Fixes
1690 bug 31490; bugfix on 0.3.2.1-alpha. Patch by Neel Chauhan.
1692 o Minor bugfixes (operator tools):
1693 - Make tor-print-ed-signing-cert(1) print certificate expiration
1694 date in RFC 1123 and UNIX timestamp formats, to make output
1695 machine readable. Fixes bug 31012; bugfix on 0.3.5.1-alpha.
1697 o Minor bugfixes (process management):
1698 - Remove overly strict assertions that triggered when a pluggable
1699 transport failed to launch. Fixes bug 31091; bugfix
1701 - Remove an assertion in the Unix process backend. This assertion
1702 would trigger when we failed to find the executable for a child
1703 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
1705 o Minor bugfixes (relay):
1706 - Avoid crashing when starting with a corrupt keys directory where
1707 the old ntor key and the new ntor key are identical. Fixes bug
1708 30916; bugfix on 0.2.4.8-alpha.
1710 o Minor bugfixes (rust):
1711 - Correctly exclude a redundant rust build job in Travis. Fixes bug
1712 31463; bugfix on 0.3.5.4-alpha.
1713 - Raise the minimum rustc version to 1.31.0, as checked by configure
1714 and CI. Fixes bug 31442; bugfix on 0.3.5.4-alpha.
1716 o Minor bugfixes (sendme, code structure):
1717 - Rename the trunnel SENDME file definition from sendme.trunnel to
1718 sendme_cell.trunnel to avoid having twice sendme.{c|h} in the
1719 repository. Fixes bug 30769; bugfix on 0.4.1.1-alpha.
1721 o Minor bugfixes (statistics):
1722 - Stop removing the ed25519 signature if the extra info file is too
1723 big. If the signature data was removed, but the keyword was kept,
1724 this could result in an unparseable extra info file. Fixes bug
1725 30958; bugfix on 0.2.7.2-alpha.
1727 o Minor bugfixes (subsystems):
1728 - Make the subsystem init order match the subsystem module
1729 dependencies. Call windows process security APIs as early as
1730 possible. Initialize logging before network and time, so that
1731 network and time can use logging. Fixes bug 31615; bugfix
1734 o Minor bugfixes (testing):
1735 - Avoid intermittent test failures due to a test that had relied on
1736 inconsistent timing sources. Fixes bug 31995; bugfix
1738 - When testing port rebinding, don't busy-wait for tor to log.
1739 Instead, actually sleep for a short time before polling again.
1740 Also improve the formatting of control commands and log messages.
1741 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
1742 - Teach the util/socketpair_ersatz test to work correctly when we
1743 have no network stack configured. Fixes bug 30804; bugfix
1746 o Minor bugfixes (tests, SunOS):
1747 - Avoid a map_anon_nofork test failure due to a signed/unsigned
1748 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
1750 o Minor bugfixes (tls, logging):
1751 - Log bugs about the TLS read buffer's length only once, rather than
1752 filling the logs with similar warnings. Fixes bug 31939; bugfix
1755 o Minor bugfixes (v2 single onion services):
1756 - Always retry v2 single onion service intro and rend circuits with
1757 a 3-hop path. Previously, v2 single onion services used a 3-hop
1758 path when rendezvous circuits were retried after a remote or
1759 delayed failure, but a 1-hop path for immediate retries. Fixes bug
1760 23818; bugfix on 0.2.9.3-alpha.
1762 o Minor bugfixes (v3 onion services):
1763 - When cleaning up intro circuits for a v3 onion service, don't
1764 remove circuits that have an established or pending circuit, even
1765 if they ran out of retries. This way, we don't remove a circuit on
1766 its last retry. Fixes bug 31652; bugfix on 0.3.2.1-alpha.
1768 o Minor bugfixes (v3 single onion services):
1769 - Always retry v3 single onion service intro and rend circuits with
1770 a 3-hop path. Previously, v3 single onion services used a 3-hop
1771 path when rend circuits were retried after a remote or delayed
1772 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
1773 bugfix on 0.3.2.1-alpha.
1774 - Make v3 single onion services fall back to a 3-hop intro, when all
1775 intro points are unreachable via a 1-hop path. Previously, v3
1776 single onion services failed when all intro nodes were unreachable
1777 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
1779 o Code simplification and refactoring:
1780 - Refactor connection_control_process_inbuf() to reduce the size of
1781 a practracker exception. Closes ticket 31840.
1782 - Refactor the microdescs_parse_from_string() function into smaller
1783 pieces, for better comprehensibility. Closes ticket 31675.
1784 - Use SEVERITY_MASK_IDX() to find the LOG_* mask indexes in the unit
1785 tests and fuzzers, rather than using hard-coded values. Closes
1787 - Interface for function `decrypt_desc_layer` cleaned up. Closes
1791 - Correct the description of "GuardLifetime". Fixes bug 31189;
1792 bugfix on 0.3.0.1-alpha.
1793 - Make clear in the man page, in both the bandwidth section and the
1794 AccountingMax section, that Tor counts in powers of two, not
1795 powers of ten: 1 GByte is 1024*1024*1024 bytes, not one billion
1796 bytes. Resolves ticket 32106.
1797 - Document the signal-safe logging behaviour in the tor man page.
1798 Also add some comments to the relevant functions. Closes
1800 - Explain why we can't destroy the backtrace buffer mutex. Explain
1801 why we don't need to destroy the log mutex. Closes ticket 31736.
1802 - The Tor source code repository now includes a (somewhat dated)
1803 description of Tor's modular architecture, in doc/HACKING/design.
1804 This is based on the old "tor-guts.git" repository, which we are
1805 adopting and superseding. Closes ticket 31849.
1806 - Improve documentation in circuit padding subsystem. Patch by
1807 Tobias Pulls. Closes ticket 31113.
1808 - Include an example usage for IPv6 ORPort in our sample torrc.
1809 Closes ticket 31320; patch from Ali Raheem.
1810 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
1811 notice.html so that operators no longer have to host it
1812 themselves. Closes ticket 31089.
1815 - No longer include recommended package digests in votes as detailed
1816 in proposal 301. The RecommendedPackages torrc option is
1817 deprecated and will no longer have any effect. "package" lines
1818 will still be considered when computing consensuses for consensus
1819 methods that include them. (This change has no effect on the list
1820 of recommended Tor versions, which is still in use.) Closes
1822 - Remove torctl.in from contrib/dist directory. Resolves
1826 - Require C99 standards-conforming code in Travis CI, but allow GNU
1827 gcc extensions. Also activates clang's -Wtypedef-redefinition
1828 warnings. Build some jobs with -std=gnu99, and some jobs without.
1829 Closes ticket 32500.
1830 - Run shellcheck for all non-third-party shell scripts that are
1831 shipped with Tor. Closes ticket 29533.
1832 - When checking shell scripts, ignore any user-created directories.
1833 Closes ticket 30967.
1835 o Code simplification and refactoring (config handling):
1836 - Extract our variable manipulation code from confparse.c to a new
1837 lower-level typedvar.h module. Closes ticket 30864.
1838 - Lower another layer of object management from confparse.c to a
1839 more general tool. Now typed structure members are accessible via
1840 an abstract type. Implements ticket 30914.
1841 - Move our backend logic for working with configuration and state
1842 files into a lower-level library, since it no longer depends on
1843 any tor-specific functionality. Closes ticket 31626.
1844 - Numerous simplifications in configuration-handling logic: remove
1845 duplicated macro definitions, replace magical names with flags,
1846 and refactor "TestingTorNetwork" to use the same default-option
1847 logic as the rest of Tor. Closes ticket 30935.
1848 - Replace our ad-hoc set of flags for configuration variables and
1849 configuration variable types with fine-grained orthogonal flags
1850 corresponding to the actual behavior we want. Closes ticket 31625.
1852 o Code simplification and refactoring (misc):
1853 - Eliminate some uses of lower-level control reply abstractions,
1854 primarily in the onion_helper functions. Closes ticket 30889.
1855 - Rework bootstrap tracking to use the new publish-subscribe
1856 subsystem. Closes ticket 29976.
1857 - Rewrite format_node_description() and router_get_verbose_nickname()
1858 to use strlcpy() and strlcat(). The previous implementation used
1859 memcpy() and pointer arithmetic, which was error-prone. Closes
1860 ticket 31545. This is CID 1452819.
1861 - Split extrainfo_dump_to_string() into smaller functions. Closes
1863 - Use the ptrdiff_t type consistently for expressing variable
1864 offsets and pointer differences. Previously we incorrectly (but
1865 harmlessly) used int and sometimes off_t for these cases. Closes
1867 - Use the subsystems mechanism to manage the main event loop code.
1868 Closes ticket 30806.
1869 - Various simplifications and minor improvements to the circuit
1870 padding machines. Patch by Tobias Pulls. Closes tickets 31112
1873 o Documentation (hard-coded directories):
1874 - Improve the documentation for the DirAuthority and FallbackDir
1875 torrc options. Closes ticket 30955.
1877 o Documentation (tor.1 man page):
1878 - Fix typo in tor.1 man page: the option is "--help", not "-help".
1879 Fixes bug 31008; bugfix on 0.2.2.9-alpha.
1881 o Testing (continuous integration):
1882 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
1883 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
1884 until we can fix some Bionic permissions issues (see ticket
1885 32240). Related to ticket 31919.
1886 - Install the mingw OpenSSL package in Appveyor. This makes sure
1887 that the OpenSSL headers and libraries match in Tor's Appveyor
1888 builds. (This bug was triggered by an Appveyor image update.)
1889 Fixes bug 32449; bugfix on 0.3.5.6-rc.
1890 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
1893 Changes in version 0.4.1.7 - 2019-12-09
1894 This release backports several bugfixes to improve stability and
1895 correctness. Anyone experiencing build problems or crashes with 0.4.1.6,
1896 including all relays relying on AccountingMax, should upgrade.
1898 o Major features (directory authorities, backport from 0.4.2.2-alpha):
1899 - Directory authorities now reject relays running all currently
1900 deprecated release series. The currently supported release series
1901 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
1903 o Major bugfixes (embedded Tor, backport from 0.4.2.2-alpha):
1904 - Avoid a possible crash when restarting Tor in embedded mode and
1905 enabling a different set of publish/subscribe messages. Fixes bug
1906 31898; bugfix on 0.4.1.1-alpha.
1908 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
1909 - Relays now respect their AccountingMax bandwidth again. When
1910 relays entered "soft" hibernation (which typically starts when
1911 we've hit 90% of our AccountingMax), we had stopped checking
1912 whether we should enter hard hibernation. Soft hibernation refuses
1913 new connections and new circuits, but the existing circuits can
1914 continue, meaning that relays could have exceeded their configured
1915 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
1917 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
1918 - Stop ignoring torrc options after an %include directive, when the
1919 included directory ends with a file that does not contain any
1920 config options (but does contain comments or whitespace). Fixes
1921 bug 31408; bugfix on 0.3.1.1-alpha.
1923 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
1924 - Onion services now always use the exact number of intro points
1925 configured with the HiddenServiceNumIntroductionPoints option (or
1926 fewer if nodes are excluded). Before, a service could sometimes
1927 pick more intro points than configured. Fixes bug 31548; bugfix
1930 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
1931 - When building on Appveyor and Travis, pass the "-k" flag to make,
1932 so that we are informed of all compilation failures, not just the
1933 first one or two. Closes ticket 31372.
1935 o Minor features (geoip, backport from 0.4.2.5):
1936 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
1937 Country database. Closes ticket 32685.
1939 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
1940 - Avoid spurious errors when Appveyor CI fails before the install step.
1941 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
1943 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
1944 - Fix a BUG() assertion that occurs within a very small race window
1945 between when a client intro circuit opens and when its descriptor
1946 gets cleaned up from the cache. The circuit is now closed early,
1947 which will trigger a re-fetch of the descriptor and continue the
1948 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
1950 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
1951 - Avoid trying to read data from closed connections, which can cause
1952 needless loops in Libevent and infinite loops in Shadow. Fixes bug
1953 30344; bugfix on 0.1.1.1-alpha.
1955 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
1956 - On abort, try harder to flush the output buffers of log messages.
1957 On some platforms (macOS), log messages could be discarded when
1958 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1959 - Report the tor version whenever an assertion fails. Previously, we
1960 only reported the Tor version on some crashes, and some non-fatal
1961 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1962 - When tor aborts due to an error, close log file descriptors before
1963 aborting. Closing the logs makes some OSes flush log file buffers,
1964 rather than deleting buffered log lines. Fixes bug 31594; bugfix
1967 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
1968 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
1969 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
1970 - Disable backtrace signal handlers when shutting down tor. Fixes
1971 bug 31614; bugfix on 0.2.5.2-alpha.
1972 - Rate-limit our the logging message about the obsolete .exit
1973 notation. Previously, there was no limit on this warning, which
1974 could potentially be triggered many times by a hostile website.
1975 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
1977 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
1978 - Do not log a nonfatal assertion failure when receiving a VERSIONS
1979 cell on a connection using the obsolete v1 link protocol. Log a
1980 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
1982 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
1983 - Reset the periodic events' "enabled" flag when Tor is shut down
1984 cleanly. Previously, this flag was left on, which caused periodic
1985 events not to be re-enabled when Tor was relaunched in-process
1986 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
1989 o Minor bugfixes (multithreading, backport from 0.4.2.2-alpha):
1990 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
1991 31736; bugfix on 0.0.7.
1993 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
1994 - Remove overly strict assertions that triggered when a pluggable
1995 transport failed to launch. Fixes bug 31091; bugfix
1997 - Remove an assertion in the Unix process backend. This assertion
1998 would trigger when we failed to find the executable for a child
1999 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
2001 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
2002 - Avoid crashing when starting with a corrupt keys directory where
2003 the old ntor key and the new ntor key are identical. Fixes bug
2004 30916; bugfix on 0.2.4.8-alpha.
2006 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
2007 - When testing port rebinding, don't busy-wait for tor to log.
2008 Instead, actually sleep for a short time before polling again.
2009 Also improve the formatting of control commands and log messages.
2010 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
2012 o Minor bugfixes (tests, SunOS, backport from 0.4.2.2-alpha):
2013 - Avoid a map_anon_nofork test failure due to a signed/unsigned
2014 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
2016 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
2017 - Log bugs about the TLS read buffer's length only once, rather than
2018 filling the logs with similar warnings. Fixes bug 31939; bugfix
2021 o Documentation (backport from 0.4.2.2-alpha):
2022 - Explain why we can't destroy the backtrace buffer mutex. Explain
2023 why we don't need to destroy the log mutex. Closes ticket 31736.
2025 o Testing (continuous integration, backport from 0.4.2.3-alpha):
2026 - Disable all but one Travis CI macOS build, to mitigate slow
2027 scheduling of Travis macOS jobs. Closes ticket 32177.
2028 - Run the chutney IPv6 networks as part of Travis CI. Closes
2030 - Simplify the Travis CI build matrix, and optimise for build time.
2031 Closes ticket 31859.
2032 - Use Windows Server 2019 instead of Windows Server 2016 in our
2033 Appveyor builds. Closes ticket 32086.
2035 o Testing (continuous integration, backport from 0.4.2.4-rc):
2036 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
2037 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
2038 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
2039 until we can fix some Bionic permissions issues (see ticket
2040 32240). Related to ticket 31919.
2041 - Install the mingw OpenSSL package in Appveyor. This makes sure
2042 that the OpenSSL headers and libraries match in Tor's Appveyor
2043 builds. (This bug was triggered by an Appveyor image update.)
2044 Fixes bug 32449; bugfix on 0.3.5.6-rc.
2046 o Testing (continuous integration, backport from 0.4.2.5):
2047 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
2048 extensions. Also activates clang's -Wtypedef-redefinition warnings.
2049 Build some jobs with -std=gnu99, and some jobs without.
2050 Closes ticket 32500.
2053 Changes in version 0.4.0.6 - 2019-12-09
2054 This is the second stable release in the 0.4.0.x series. This release
2055 backports several bugfixes to improve stability and correctness. Anyone
2056 experiencing build problems or crashes with 0.4.0.5, including all relays
2057 relying on AccountingMax, should upgrade.
2059 Note that, per our support policy, support for the 0.4.0.x series will end
2060 on 2 Feb 2020. Anyone still running 0.4.0.x should plan to upgrade to the
2061 latest stable release, or downgrade to 0.3.5.x, which will get long-term
2062 support until 1 Feb 2022.
2064 o Directory authority changes (backport from 0.4.1.5):
2065 - The directory authority "dizum" has a new IP address. Closes
2068 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
2069 - Consider our directory information to have changed when our list
2070 of bridges changes. Previously, Tor would not re-compute the
2071 status of its directory information when bridges changed, and
2072 therefore would not realize that it was no longer able to build
2073 circuits. Fixes part of bug 29875.
2074 - Do not count previously configured working bridges towards our
2075 total of working bridges. Previously, when Tor's list of bridges
2076 changed, it would think that the old bridges were still usable,
2077 and delay fetching router descriptors for the new ones. Fixes part
2078 of bug 29875; bugfix on 0.3.0.1-alpha.
2080 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
2081 - When considering upgrading circuits from "waiting for guard" to
2082 "open", always ignore circuits that are marked for close. Otherwise,
2083 we can end up in the situation where a subsystem is notified that
2084 a closing circuit has just opened, leading to undesirable
2085 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
2087 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
2088 - Properly clean up the introduction point map when circuits change
2089 purpose from onion service circuits to pathbias, measurement, or
2090 other circuit types. This should fix some service-side instances
2091 of introduction point failure. Fixes bug 29034; bugfix
2094 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
2095 - Fix an unreachable bug in which an introduction point could try to
2096 send an INTRODUCE_ACK with a status code that Trunnel would refuse
2097 to encode, leading the relay to assert(). We've consolidated the
2098 ABI values into Trunnel now. Fixes bug 30454; bugfix
2100 - Clients can now handle unknown status codes from INTRODUCE_ACK
2101 cells. (The NACK behavior will stay the same.) This will allow us
2102 to extend status codes in the future without breaking the normal
2103 client behavior. Fixes another part of bug 30454; bugfix
2106 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
2107 - Relays now respect their AccountingMax bandwidth again. When
2108 relays entered "soft" hibernation (which typically starts when
2109 we've hit 90% of our AccountingMax), we had stopped checking
2110 whether we should enter hard hibernation. Soft hibernation refuses
2111 new connections and new circuits, but the existing circuits can
2112 continue, meaning that relays could have exceeded their configured
2113 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
2115 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
2116 - Stop ignoring torrc options after an %include directive, when the
2117 included directory ends with a file that does not contain any
2118 config options (but does contain comments or whitespace). Fixes
2119 bug 31408; bugfix on 0.3.1.1-alpha.
2121 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
2122 - Onion services now always use the exact number of intro points
2123 configured with the HiddenServiceNumIntroductionPoints option (or
2124 fewer if nodes are excluded). Before, a service could sometimes
2125 pick more intro points than configured. Fixes bug 31548; bugfix
2128 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
2129 - Add a "--list-modules" command to print a list of which compile-
2130 time modules are enabled. Closes ticket 30452.
2132 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
2133 - Remove sudo configuration lines from .travis.yml as they are no
2134 longer needed with current Travis build environment. Resolves
2137 o Minor features (continuous integration, backport from 0.4.1.4-rc):
2138 - Our Travis configuration now uses Chutney to run some network
2139 integration tests automatically. Closes ticket 29280.
2141 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
2142 - When building on Appveyor and Travis, pass the "-k" flag to make,
2143 so that we are informed of all compilation failures, not just the
2144 first one or two. Closes ticket 31372.
2146 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
2147 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
2148 in December 2018 (of which ~122 were still functional), with a
2149 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
2150 in June 2019. Closes ticket 28795.
2152 o Minor features (geoip, backport from 0.4.2.5):
2153 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
2154 Country database. Closes ticket 32685.
2156 o Minor features (stem tests, backport from 0.4.2.1-alpha):
2157 - Change "make test-stem" so it only runs the stem tests that use
2158 tor. This change makes test-stem faster and more reliable. Closes
2161 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
2162 - Avoid spurious errors when Appveyor CI fails before the install step.
2163 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
2165 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
2166 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
2167 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
2169 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
2170 - Fix a logic error that prevented the SessionGroup sub-option from
2171 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
2173 o Minor bugfixes (circuit padding, backport from 0.4.1.4-rc):
2174 - On relays, properly check that a padding machine is absent before
2175 logging a warning about it being absent. Fixes bug 30649; bugfix
2178 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
2179 - Fix a BUG() assertion that occurs within a very small race window
2180 between when a client intro circuit opens and when its descriptor
2181 gets cleaned up from the cache. The circuit is now closed early,
2182 which will trigger a re-fetch of the descriptor and continue the
2183 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
2185 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
2186 - Don't believe clock skew results from NETINFO cells that appear to
2187 arrive before we sent the VERSIONS cells they are responding to.
2188 Previously, we would accept them up to 3 minutes "in the past".
2189 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
2191 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
2192 - Fix a compilation warning on Windows about casting a function
2193 pointer for GetTickCount64(). Fixes bug 31374; bugfix
2196 o Minor bugfixes (compilation, backport from 0.4.1.5):
2197 - Avoid using labs() on time_t, which can cause compilation warnings
2198 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
2200 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
2201 - Suppress spurious float-conversion warnings from GCC when calling
2202 floating-point classifier functions on FreeBSD. Fixes part of bug
2203 31687; bugfix on 0.3.1.5-alpha.
2205 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
2206 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
2207 due to missing declarations of abort(), and prevent other such
2208 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
2210 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
2211 - Fix a bug that prevented us from supporting SOCKS5 proxies that
2212 want authentication along with configured (but unused!)
2213 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
2215 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
2216 - Avoid trying to read data from closed connections, which can cause
2217 needless loops in Libevent and infinite loops in Shadow. Fixes bug
2218 30344; bugfix on 0.1.1.1-alpha.
2220 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
2221 - Allow the test-stem job to fail in Travis, because it sometimes
2222 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
2223 - Skip test_rebind on macOS in Travis, because it is unreliable on
2224 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
2225 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
2226 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
2228 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
2229 - Avoid a set of possible code paths that could try to use freed
2230 memory in routerlist_free() while Tor was exiting. Fixes bug
2231 31003; bugfix on 0.1.2.2-alpha.
2233 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
2234 - Stop crashing after parsing an unknown descriptor purpose
2235 annotation. We think this bug can only be triggered by modifying a
2236 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
2238 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
2239 - Move the "bandwidth-file-headers" line in directory authority
2240 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
2243 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
2244 - On abort, try harder to flush the output buffers of log messages.
2245 On some platforms (macOS), log messages could be discarded when
2246 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
2247 - Report the tor version whenever an assertion fails. Previously, we
2248 only reported the Tor version on some crashes, and some non-fatal
2249 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
2251 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
2252 - When extracting an IPv6 address from a PF-based proxy, verify that
2253 we are actually configured to receive an IPv6 address, and log an
2254 internal error if not. Fixes part of bug 31687; bugfix
2257 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
2258 - When tor is missing descriptors for some primary entry guards,
2259 make the log message less alarming. It's normal for descriptors to
2260 expire, as long as tor fetches new ones soon after. Fixes bug
2261 31657; bugfix on 0.3.3.1-alpha.
2263 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
2264 - Do not log a warning when running with an OpenSSL version other
2265 than the one Tor was compiled with, if the two versions should be
2266 compatible. Previously, we would warn whenever the version was
2267 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
2269 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
2270 - Change log level of message "Hash of session info was not as
2271 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
2274 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
2275 - Rate-limit our the logging message about the obsolete .exit
2276 notation. Previously, there was no limit on this warning, which
2277 could potentially be triggered many times by a hostile website.
2278 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
2280 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
2281 - Do not log a nonfatal assertion failure when receiving a VERSIONS
2282 cell on a connection using the obsolete v1 link protocol. Log a
2283 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
2285 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
2286 - Reset the periodic events' "enabled" flag when Tor is shut down
2287 cleanly. Previously, this flag was left on, which caused periodic
2288 events not to be re-enabled when Tor was relaunched in-process
2289 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
2292 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
2293 - Avoid a minor memory leak that could occur on relays when failing
2294 to create a "keys" directory. Fixes bug 30148; bugfix
2297 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
2298 - Fix a trivial memory leak when parsing an invalid value
2299 from a download schedule in the configuration. Fixes bug
2300 30894; bugfix on 0.3.4.1-alpha.
2302 o Minor bugfixes (NetBSD, backport from 0.4.1.2-alpha):
2303 - Fix usage of minherit() on NetBSD and other platforms that define
2304 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
2305 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
2307 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
2308 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
2309 implemenation) when failing to load an onion service client
2310 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
2312 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
2313 - When purging the DNS cache because of an out-of-memory condition,
2314 try purging just the older entries at first. Previously, we would
2315 always purge the whole thing. Fixes bug 29617; bugfix
2318 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
2319 - Avoid crashing in our tor_vasprintf() implementation on systems
2320 that define neither vasprintf() nor _vscprintf(). (This bug has
2321 been here long enough that we question whether people are running
2322 Tor on such systems, but we're applying the fix out of caution.)
2323 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
2326 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
2327 - Remove overly strict assertions that triggered when a pluggable
2328 transport failed to launch. Fixes bug 31091; bugfix
2330 - Remove an assertion in the Unix process backend. This assertion
2331 would trigger when we failed to find the executable for a child
2332 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
2334 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
2335 - Avoid crashing when starting with a corrupt keys directory where
2336 the old ntor key and the new ntor key are identical. Fixes bug
2337 30916; bugfix on 0.2.4.8-alpha.
2339 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
2340 - Correctly exclude a redundant rust build job in Travis. Fixes bug
2341 31463; bugfix on 0.3.5.4-alpha.
2343 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
2344 - When testing port rebinding, don't busy-wait for tor to log.
2345 Instead, actually sleep for a short time before polling again.
2346 Also improve the formatting of control commands and log messages.
2347 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
2349 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
2350 - Log bugs about the TLS read buffer's length only once, rather than
2351 filling the logs with similar warnings. Fixes bug 31939; bugfix
2354 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
2355 - Always retry v2 single onion service intro and rend circuits with
2356 a 3-hop path. Previously, v2 single onion services used a 3-hop
2357 path when rendezvous circuits were retried after a remote or
2358 delayed failure, but a 1-hop path for immediate retries. Fixes bug
2359 23818; bugfix on 0.2.9.3-alpha.
2360 - Make v3 single onion services fall back to a 3-hop intro, when all
2361 intro points are unreachable via a 1-hop path. Previously, v3
2362 single onion services failed when all intro nodes were unreachable
2363 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
2365 o Documentation (backport from 0.4.2.1-alpha):
2366 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
2367 notice.html so that operators no longer have to host it
2368 themselves. Closes ticket 31089.
2370 o Testing (backport from 0.4.1.2-alpha):
2371 - Specify torrc paths (with empty files) when launching tor in
2372 integration tests; refrain from reading user and system torrcs.
2373 Resolves issue 29702.
2375 o Testing (continuous integration, backport from 0.4.1.1-alpha):
2376 - In Travis, show stem's tor log after failure. Closes ticket 30234.
2378 o Testing (continuous integration, backport from 0.4.1.5):
2379 - In Travis, make stem log a controller trace to the console, and
2380 tail stem's tor log after failure. Closes ticket 30591.
2381 - In Travis, only run the stem tests that use a tor binary. Closes
2384 o Testing (continuous integration, backport from 0.4.2.3-alpha):
2385 - Disable all but one Travis CI macOS build, to mitigate slow
2386 scheduling of Travis macOS jobs. Closes ticket 32177.
2387 - Run the chutney IPv6 networks as part of Travis CI. Closes
2389 - Simplify the Travis CI build matrix, and optimise for build time.
2390 Closes ticket 31859.
2391 - Use Windows Server 2019 instead of Windows Server 2016 in our
2392 Appveyor builds. Closes ticket 32086.
2394 o Testing (continuous integration, backport from 0.4.2.4-rc):
2395 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
2396 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
2397 until we can fix some Bionic permissions issues (see ticket
2398 32240). Related to ticket 31919.
2399 - Install the mingw OpenSSL package in Appveyor. This makes sure
2400 that the OpenSSL headers and libraries match in Tor's Appveyor
2401 builds. (This bug was triggered by an Appveyor image update.)
2402 Fixes bug 32449; bugfix on 0.3.5.6-rc.
2403 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
2405 o Testing (continuous integration, backport from 0.4.2.5):
2406 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
2407 extensions. Also activates clang's -Wtypedef-redefinition warnings.
2408 Build some jobs with -std=gnu99, and some jobs without.
2409 Closes ticket 32500.
2412 Changes in version 0.3.5.9 - 2019-12-09
2413 Tor 0.3.5.9 backports serveral fixes from later releases, including
2414 several that affect bridge users, relay stability, onion services,
2417 o Directory authority changes (backport from 0.4.1.5):
2418 - The directory authority "dizum" has a new IP address. Closes
2421 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
2422 - Consider our directory information to have changed when our list
2423 of bridges changes. Previously, Tor would not re-compute the
2424 status of its directory information when bridges changed, and
2425 therefore would not realize that it was no longer able to build
2426 circuits. Fixes part of bug 29875.
2427 - Do not count previously configured working bridges towards our
2428 total of working bridges. Previously, when Tor's list of bridges
2429 changed, it would think that the old bridges were still usable,
2430 and delay fetching router descriptors for the new ones. Fixes part
2431 of bug 29875; bugfix on 0.3.0.1-alpha.
2433 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
2434 - When considering upgrading circuits from "waiting for guard" to
2435 "open", always ignore circuits that are marked for close. Otherwise,
2436 we can end up in the situation where a subsystem is notified that
2437 a closing circuit has just opened, leading to undesirable
2438 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
2440 o Major bugfixes (NSS, relay, backport from 0.4.0.4-rc):
2441 - When running with NSS, disable TLS 1.2 ciphersuites that use
2442 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
2443 these ciphersuites don't work -- which caused relays to fail to
2444 handshake with one another when these ciphersuites were enabled.
2445 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
2447 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
2448 - Properly clean up the introduction point map when circuits change
2449 purpose from onion service circuits to pathbias, measurement, or
2450 other circuit types. This should fix some service-side instances
2451 of introduction point failure. Fixes bug 29034; bugfix
2454 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
2455 - Fix an unreachable bug in which an introduction point could try to
2456 send an INTRODUCE_ACK with a status code that Trunnel would refuse
2457 to encode, leading the relay to assert(). We've consolidated the
2458 ABI values into Trunnel now. Fixes bug 30454; bugfix
2460 - Clients can now handle unknown status codes from INTRODUCE_ACK
2461 cells. (The NACK behavior will stay the same.) This will allow us
2462 to extend status codes in the future without breaking the normal
2463 client behavior. Fixes another part of bug 30454; bugfix
2466 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
2467 - Stop ignoring torrc options after an %include directive, when the
2468 included directory ends with a file that does not contain any
2469 config options (but does contain comments or whitespace). Fixes
2470 bug 31408; bugfix on 0.3.1.1-alpha.
2472 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
2473 - Onion services now always use the exact number of intro points
2474 configured with the HiddenServiceNumIntroductionPoints option (or
2475 fewer if nodes are excluded). Before, a service could sometimes
2476 pick more intro points than configured. Fixes bug 31548; bugfix
2479 o Minor features (address selection, backport from 0.4.0.3-alpha):
2480 - Treat the subnet 100.64.0.0/10 as public for some purposes;
2481 private for others. This subnet is the RFC 6598 (Carrier Grade
2482 NAT) IP range, and is deployed by many ISPs as an alternative to
2483 RFC 1918 that does not break existing internal networks. Tor now
2484 blocks SOCKS and control ports on these addresses and warns users
2485 if client ports or ExtORPorts are listening on a RFC 6598 address.
2486 Closes ticket 28525. Patch by Neel Chauhan.
2488 o Minor features (bandwidth authority, backport from 0.4.0.4-rc):
2489 - Make bandwidth authorities ignore relays that are reported in the
2490 bandwidth file with the flag "vote=0". This change allows us to
2491 report unmeasured relays for diagnostic reasons without including
2492 their bandwidth in the bandwidth authorities' vote. Closes
2495 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
2496 - Add a "--list-modules" command to print a list of which compile-
2497 time modules are enabled. Closes ticket 30452.
2499 o Minor features (continuous integration, backport from 0.4.0.4-rc):
2500 - On Travis Rust builds, cleanup Rust registry and refrain from
2501 caching the "target/" directory to speed up builds. Resolves
2504 o Minor features (continuous integration, backport from 0.4.0.5):
2505 - In Travis, tell timelimit to use stem's backtrace signals, and
2506 launch python directly from timelimit, so python receives the
2507 signals from timelimit, rather than make. Closes ticket 30117.
2509 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
2510 - Remove sudo configuration lines from .travis.yml as they are no
2511 longer needed with current Travis build environment. Resolves
2514 o Minor features (continuous integration, backport from 0.4.1.4-rc):
2515 - Our Travis configuration now uses Chutney to run some network
2516 integration tests automatically. Closes ticket 29280.
2518 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
2519 - When building on Appveyor and Travis, pass the "-k" flag to make,
2520 so that we are informed of all compilation failures, not just the
2521 first one or two. Closes ticket 31372.
2523 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
2524 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
2525 in December 2018 (of which ~122 were still functional), with a
2526 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
2527 in June 2019. Closes ticket 28795.
2529 o Minor features (geoip, backport from 0.4.2.5):
2530 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
2531 Country database. Closes ticket 32685.
2533 o Minor features (NSS, diagnostic, backport from 0.4.0.4-rc):
2534 - Try to log an error from NSS (if there is any) and a more useful
2535 description of our situation if we are using NSS and a call to
2536 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
2538 o Minor features (stem tests, backport from 0.4.2.1-alpha):
2539 - Change "make test-stem" so it only runs the stem tests that use
2540 tor. This change makes test-stem faster and more reliable. Closes
2543 o Minor bugfixes (security, backport from 0.4.0.4-rc):
2544 - Verify in more places that we are not about to create a buffer
2545 with more than INT_MAX bytes, to avoid possible OOB access in the
2546 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
2547 fixed by Tobias Stoeckmann.
2548 - Fix a potential double free bug when reading huge bandwidth files.
2549 The issue is not exploitable in the current Tor network because
2550 the vulnerable code is only reached when directory authorities
2551 read bandwidth files, but bandwidth files come from a trusted
2552 source (usually the authorities themselves). Furthermore, the
2553 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
2554 which are not used by any of the current authorities. Fixes bug
2555 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
2558 o Minor bugfix (continuous integration, backport from 0.4.0.4-rc):
2559 - Reset coverage state on disk after Travis CI has finished. This
2560 should prevent future coverage merge errors from causing the test
2561 suite for the "process" subsystem to fail. The process subsystem
2562 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
2564 - Terminate test-stem if it takes more than 9.5 minutes to run.
2565 (Travis terminates the job after 10 minutes of no output.)
2566 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
2568 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
2569 - Avoid spurious errors when Appveyor CI fails before the install step.
2570 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
2572 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
2573 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
2574 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
2576 o Minor bugfixes (C correctness, backport from 0.4.0.4-rc):
2577 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
2578 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
2581 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
2582 - Fix a logic error that prevented the SessionGroup sub-option from
2583 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
2585 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
2586 - Fix a BUG() assertion that occurs within a very small race window
2587 between when a client intro circuit opens and when its descriptor
2588 gets cleaned up from the cache. The circuit is now closed early,
2589 which will trigger a re-fetch of the descriptor and continue the
2590 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
2592 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
2593 - Don't believe clock skew results from NETINFO cells that appear to
2594 arrive before we sent the VERSIONS cells they are responding to.
2595 Previously, we would accept them up to 3 minutes "in the past".
2596 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
2598 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
2599 - Fix a compilation warning on Windows about casting a function
2600 pointer for GetTickCount64(). Fixes bug 31374; bugfix
2603 o Minor bugfixes (compilation, backport from 0.4.0.2-alpha):
2604 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
2605 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
2607 o Minor bugfixes (compilation, backport from 0.4.1.5):
2608 - Avoid using labs() on time_t, which can cause compilation warnings
2609 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
2611 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
2612 - Suppress spurious float-conversion warnings from GCC when calling
2613 floating-point classifier functions on FreeBSD. Fixes part of bug
2614 31687; bugfix on 0.3.1.5-alpha.
2616 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
2617 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
2618 due to missing declarations of abort(), and prevent other such
2619 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
2621 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
2622 - Fix a bug that prevented us from supporting SOCKS5 proxies that
2623 want authentication along with configured (but unused!)
2624 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
2626 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
2627 - Avoid trying to read data from closed connections, which can cause
2628 needless loops in Libevent and infinite loops in Shadow. Fixes bug
2629 30344; bugfix on 0.1.1.1-alpha.
2631 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
2632 - Allow the test-stem job to fail in Travis, because it sometimes
2633 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
2634 - Skip test_rebind on macOS in Travis, because it is unreliable on
2635 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
2636 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
2637 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
2639 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
2640 - Avoid a set of possible code paths that could try to use freed
2641 memory in routerlist_free() while Tor was exiting. Fixes bug
2642 31003; bugfix on 0.1.2.2-alpha.
2644 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
2645 - Stop crashing after parsing an unknown descriptor purpose
2646 annotation. We think this bug can only be triggered by modifying a
2647 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
2649 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
2650 - Move the "bandwidth-file-headers" line in directory authority
2651 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
2654 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
2655 - On abort, try harder to flush the output buffers of log messages.
2656 On some platforms (macOS), log messages could be discarded when
2657 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
2658 - Report the tor version whenever an assertion fails. Previously, we
2659 only reported the Tor version on some crashes, and some non-fatal
2660 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
2662 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
2663 - When extracting an IPv6 address from a PF-based proxy, verify that
2664 we are actually configured to receive an IPv6 address, and log an
2665 internal error if not. Fixes part of bug 31687; bugfix
2668 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
2669 - When tor is missing descriptors for some primary entry guards,
2670 make the log message less alarming. It's normal for descriptors to
2671 expire, as long as tor fetches new ones soon after. Fixes bug
2672 31657; bugfix on 0.3.3.1-alpha.
2674 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
2675 - Avoid logging that we are relaxing a circuit timeout when that
2676 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
2678 o Minor bugfixes (logging, backport from 0.4.0.3-alpha):
2679 - Correct a misleading error message when IPv4Only or IPv6Only is
2680 used but the resolved address can not be interpreted as an address
2681 of the specified IP version. Fixes bug 13221; bugfix on
2682 0.2.3.9-alpha. Patch from Kris Katterjohn.
2683 - Log the correct port number for listening sockets when "auto" is
2684 used to let Tor pick the port number. Previously, port 0 was
2685 logged instead of the actual port number. Fixes bug 29144; bugfix
2686 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
2687 - Stop logging a BUG() warning when Tor is waiting for exit
2688 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
2690 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
2691 - Do not log a warning when running with an OpenSSL version other
2692 than the one Tor was compiled with, if the two versions should be
2693 compatible. Previously, we would warn whenever the version was
2694 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
2696 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
2697 - Change log level of message "Hash of session info was not as
2698 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
2701 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
2702 - Rate-limit our the logging message about the obsolete .exit
2703 notation. Previously, there was no limit on this warning, which
2704 could potentially be triggered many times by a hostile website.
2705 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
2707 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
2708 - Do not log a nonfatal assertion failure when receiving a VERSIONS
2709 cell on a connection using the obsolete v1 link protocol. Log a
2710 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
2712 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
2713 - Reset the periodic events' "enabled" flag when Tor is shut down
2714 cleanly. Previously, this flag was left on, which caused periodic
2715 events not to be re-enabled when Tor was relaunched in-process
2716 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
2719 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
2720 - Avoid a minor memory leak that could occur on relays when failing
2721 to create a "keys" directory. Fixes bug 30148; bugfix
2724 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
2725 - Fix a trivial memory leak when parsing an invalid value
2726 from a download schedule in the configuration. Fixes bug
2727 30894; bugfix on 0.3.4.1-alpha.
2729 o Minor bugfixes (memory management, backport from 0.4.0.3-alpha):
2730 - Refactor the shared random state's memory management so that it
2731 actually takes ownership of the shared random value pointers.
2732 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
2734 o Minor bugfixes (memory management, testing, backport from 0.4.0.3-alpha):
2735 - Stop leaking parts of the shared random state in the shared-random
2736 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
2738 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
2739 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
2740 implemenation) when failing to load an onion service client
2741 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
2743 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
2744 - When purging the DNS cache because of an out-of-memory condition,
2745 try purging just the older entries at first. Previously, we would
2746 always purge the whole thing. Fixes bug 29617; bugfix
2749 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
2750 - Avoid crashing in our tor_vasprintf() implementation on systems
2751 that define neither vasprintf() nor _vscprintf(). (This bug has
2752 been here long enough that we question whether people are running
2753 Tor on such systems, but we're applying the fix out of caution.)
2754 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
2757 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
2758 - Avoid crashing when starting with a corrupt keys directory where
2759 the old ntor key and the new ntor key are identical. Fixes bug
2760 30916; bugfix on 0.2.4.8-alpha.
2762 o Minor bugfixes (rust, backport from 0.4.0.5):
2763 - Abort on panic in all build profiles, instead of potentially
2764 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
2766 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
2767 - Correctly exclude a redundant rust build job in Travis. Fixes bug
2768 31463; bugfix on 0.3.5.4-alpha.
2770 o Minor bugfixes (single onion services, backport from 0.4.0.3-alpha):
2771 - Allow connections to single onion services to remain idle without
2772 being disconnected. Previously, relays acting as rendezvous points
2773 for single onion services were mistakenly closing idle rendezvous
2774 circuits after 60 seconds, thinking that they were unused
2775 directory-fetching circuits that had served their purpose. Fixes
2776 bug 29665; bugfix on 0.2.1.26.
2778 o Minor bugfixes (stats, backport from 0.4.0.3-alpha):
2779 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
2780 relay and bridge extra-info documents. Fixes bug 29017; bugfix
2783 o Minor bugfixes (testing, backport from 0.4.0.3-alpha):
2784 - Downgrade some LOG_ERR messages in the address/* tests to
2785 warnings. The LOG_ERR messages were occurring when we had no
2786 configured network. We were failing the unit tests, because we
2787 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
2788 29530; bugfix on 0.3.5.8.
2789 - Fix our gcov wrapper script to look for object files at the
2790 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
2792 o Minor bugfixes (testing, backport from 0.4.0.4-rc):
2793 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
2794 recent test-network.sh to use new chutney features in CI. Fixes
2795 bug 29703; bugfix on 0.2.9.1-alpha.
2796 - Fix a test failure on Windows caused by an unexpected "BUG"
2797 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
2800 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
2801 - When testing port rebinding, don't busy-wait for tor to log.
2802 Instead, actually sleep for a short time before polling again.
2803 Also improve the formatting of control commands and log messages.
2804 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
2806 o Minor bugfixes (TLS protocol, backport form 0.4.0.4-rc):
2807 - When classifying a client's selection of TLS ciphers, if the
2808 client ciphers are not yet available, do not cache the result.
2809 Previously, we had cached the unavailability of the cipher list
2810 and never looked again, which in turn led us to assume that the
2811 client only supported the ancient V1 link protocol. This, in turn,
2812 was causing Stem integration tests to stall in some cases. Fixes
2813 bug 30021; bugfix on 0.2.4.8-alpha.
2815 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
2816 - Log bugs about the TLS read buffer's length only once, rather than
2817 filling the logs with similar warnings. Fixes bug 31939; bugfix
2820 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
2821 - Always retry v2 single onion service intro and rend circuits with
2822 a 3-hop path. Previously, v2 single onion services used a 3-hop
2823 path when rendezvous circuits were retried after a remote or
2824 delayed failure, but a 1-hop path for immediate retries. Fixes bug
2825 23818; bugfix on 0.2.9.3-alpha.
2826 - Make v3 single onion services fall back to a 3-hop intro, when all
2827 intro points are unreachable via a 1-hop path. Previously, v3
2828 single onion services failed when all intro nodes were unreachable
2829 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
2831 o Minor bugfixes (Windows, CI, backport from 0.4.0.3-alpha):
2832 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
2833 Windows Server 2012 R2 job. The remaining 2 jobs still provide
2834 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
2835 fast_finish, so failed jobs terminate the build immediately. Fixes
2836 bug 29601; bugfix on 0.3.5.4-alpha.
2838 o Documentation (backport from 0.4.2.1-alpha):
2839 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
2840 notice.html so that operators no longer have to host it
2841 themselves. Closes ticket 31089.
2843 o Testing (backport from 0.4.1.2-alpha):
2844 - Specify torrc paths (with empty files) when launching tor in
2845 integration tests; refrain from reading user and system torrcs.
2846 Resolves issue 29702.
2848 o Testing (continuous integration, backport from 0.4.1.1-alpha):
2849 - In Travis, show stem's tor log after failure. Closes ticket 30234.
2851 o Testing (continuous integration, backport from 0.4.1.5):
2852 - In Travis, make stem log a controller trace to the console, and
2853 tail stem's tor log after failure. Closes ticket 30591.
2854 - In Travis, only run the stem tests that use a tor binary. Closes
2857 o Testing (continuous integration, backport from 0.4.2.3-alpha):
2858 - Disable all but one Travis CI macOS build, to mitigate slow
2859 scheduling of Travis macOS jobs. Closes ticket 32177.
2860 - Run the chutney IPv6 networks as part of Travis CI. Closes
2862 - Simplify the Travis CI build matrix, and optimise for build time.
2863 Closes ticket 31859.
2864 - Use Windows Server 2019 instead of Windows Server 2016 in our
2865 Appveyor builds. Closes ticket 32086.
2867 o Testing (continuous integration, backport from 0.4.2.4-rc):
2868 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
2869 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
2870 until we can fix some Bionic permissions issues (see ticket
2871 32240). Related to ticket 31919.
2872 - Install the mingw OpenSSL package in Appveyor. This makes sure
2873 that the OpenSSL headers and libraries match in Tor's Appveyor
2874 builds. (This bug was triggered by an Appveyor image update.)
2875 Fixes bug 32449; bugfix on 0.3.5.6-rc.
2876 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
2878 o Testing (continuous integration, backport from 0.4.2.5):
2879 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
2880 extensions. Also activates clang's -Wtypedef-redefinition warnings.
2881 Build some jobs with -std=gnu99, and some jobs without.
2882 Closes ticket 32500.
2885 Changes in version 0.4.1.6 - 2019-09-19
2886 This release backports several bugfixes to improve stability and
2887 correctness. Anyone experiencing build problems or crashes with 0.4.1.5,
2888 or experiencing reliability issues with single onion services, should
2891 o Major bugfixes (crash, Linux, Android, backport from 0.4.2.1-alpha):
2892 - Tolerate systems (including some Android installations) where
2893 madvise and MADV_DONTDUMP are available at build-time, but not at
2894 run time. Previously, these systems would notice a failed syscall
2895 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
2896 - Tolerate systems (including some Linux installations) where
2897 madvise and/or MADV_DONTFORK are available at build-time, but not
2898 at run time. Previously, these systems would notice a failed
2899 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
2901 o Minor features (stem tests, backport from 0.4.2.1-alpha):
2902 - Change "make test-stem" so it only runs the stem tests that use
2903 tor. This change makes test-stem faster and more reliable. Closes
2906 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
2907 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
2908 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
2910 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
2911 - Add more stub functions to fix compilation on Android with link-
2912 time optimization when --disable-module-dirauth is used.
2913 Previously, these compilation settings would make the compiler
2914 look for functions that didn't exist. Fixes bug 31552; bugfix
2916 - Suppress spurious float-conversion warnings from GCC when calling
2917 floating-point classifier functions on FreeBSD. Fixes part of bug
2918 31687; bugfix on 0.3.1.5-alpha.
2920 o Minor bugfixes (controller protocol):
2921 - Fix the MAPADDRESS controller command to accept one or more
2922 arguments. Previously, it required two or more arguments, and ignored
2923 the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
2925 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
2926 - When extracting an IPv6 address from a PF-based proxy, verify that
2927 we are actually configured to receive an IPv6 address, and log an
2928 internal error if not. Fixes part of bug 31687; bugfix
2931 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
2932 - When tor is missing descriptors for some primary entry guards,
2933 make the log message less alarming. It's normal for descriptors to
2934 expire, as long as tor fetches new ones soon after. Fixes bug
2935 31657; bugfix on 0.3.3.1-alpha.
2937 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
2938 - Change log level of message "Hash of session info was not as
2939 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
2942 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
2943 - Correctly exclude a redundant rust build job in Travis. Fixes bug
2944 31463; bugfix on 0.3.5.4-alpha.
2946 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
2947 - Always retry v2 single onion service intro and rend circuits with
2948 a 3-hop path. Previously, v2 single onion services used a 3-hop
2949 path when rendezvous circuits were retried after a remote or
2950 delayed failure, but a 1-hop path for immediate retries. Fixes bug
2951 23818; bugfix on 0.2.9.3-alpha.
2953 o Minor bugfixes (v3 single onion services, backport from 0.4.2.1-alpha):
2954 - Always retry v3 single onion service intro and rend circuits with
2955 a 3-hop path. Previously, v3 single onion services used a 3-hop
2956 path when rend circuits were retried after a remote or delayed
2957 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
2958 bugfix on 0.3.2.1-alpha.
2959 - Make v3 single onion services fall back to a 3-hop intro, when all
2960 intro points are unreachable via a 1-hop path. Previously, v3
2961 single onion services failed when all intro nodes were unreachable
2962 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
2964 o Documentation (backport from 0.4.2.1-alpha):
2965 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
2966 notice.html so that operators no longer have to host it
2967 themselves. Closes ticket 31089.
2970 Changes in version 0.4.1.5 - 2019-08-20
2971 This is the first stable release in the 0.4.1.x series. This series
2972 adds experimental circuit-level padding, authenticated SENDME cells to
2973 defend against certain attacks, and several performance improvements
2974 to save on CPU consumption. It fixes bugs in bootstrapping and v3
2975 onion services. It also includes numerous smaller features and
2976 bugfixes on earlier versions.
2978 Per our support policy, we will support the 0.4.1.x series for nine
2979 months, or until three months after the release of a stable 0.4.2.x:
2980 whichever is longer. If you need longer-term support, please stick
2981 with 0.3.5.x, which will we plan to support until Feb 2022.
2983 Below are the changes since 0.4.0.5. For a list of only the changes
2984 since 0.4.1.4-rc, see the ChangeLog file.
2986 o Directory authority changes:
2987 - The directory authority "dizum" has a new IP address. Closes
2990 o Major features (circuit padding):
2991 - Onion service clients now add padding cells at the start of their
2992 INTRODUCE and RENDEZVOUS circuits, to make those circuits' traffic
2993 look more like general purpose Exit traffic. The overhead for this
2994 is 2 extra cells in each direction for RENDEZVOUS circuits, and 1
2995 extra upstream cell and 10 downstream cells for INTRODUCE
2996 circuits. This feature is only enabled when also supported by the
2997 circuit's middle node. (Clients may specify fixed middle nodes
2998 with the MiddleNodes option, and may force-disable this feature
2999 with the CircuitPadding option.) Closes ticket 28634.
3001 o Major features (code organization):
3002 - Tor now includes a generic publish-subscribe message-passing
3003 subsystem that we can use to organize intermodule dependencies. We
3004 hope to use this to reduce dependencies between modules that don't
3005 need to be related, and to generally simplify our codebase. Closes
3008 o Major features (controller protocol):
3009 - Controller commands are now parsed using a generalized parsing
3010 subsystem. Previously, each controller command was responsible for
3011 parsing its own input, which led to strange inconsistencies.
3012 Closes ticket 30091.
3014 o Major features (flow control):
3015 - Implement authenticated SENDMEs as detailed in proposal 289. A
3016 SENDME cell now includes the digest of the traffic that it
3017 acknowledges, so that once an end point receives the SENDME, it
3018 can confirm the other side's knowledge of the previous cells that
3019 were sent, and prevent certain types of denial-of-service attacks.
3020 This behavior is controlled by two new consensus parameters: see
3021 the proposal for more details. Fixes ticket 26288.
3023 o Major features (performance):
3024 - Our node selection algorithm now excludes nodes in linear time.
3025 Previously, the algorithm was quadratic, which could slow down
3026 heavily used onion services. Closes ticket 30307.
3028 o Major features (performance, RNG):
3029 - Tor now constructs a fast secure pseudorandom number generator for
3030 each thread, to use when performance is critical. This PRNG is
3031 based on AES-CTR, using a buffering construction similar to
3032 libottery and the (newer) OpenBSD arc4random() code. It
3033 outperforms OpenSSL 1.1.1a's CSPRNG by roughly a factor of 100 for
3034 small outputs. Although we believe it to be cryptographically
3035 strong, we are only using it when necessary for performance.
3036 Implements tickets 29023 and 29536.
3038 o Major bugfixes (bridges):
3039 - Consider our directory information to have changed when our list
3040 of bridges changes. Previously, Tor would not re-compute the
3041 status of its directory information when bridges changed, and
3042 therefore would not realize that it was no longer able to build
3043 circuits. Fixes part of bug 29875.
3044 - Do not count previously configured working bridges towards our
3045 total of working bridges. Previously, when Tor's list of bridges
3046 changed, it would think that the old bridges were still usable,
3047 and delay fetching router descriptors for the new ones. Fixes part
3048 of bug 29875; bugfix on 0.3.0.1-alpha.
3050 o Major bugfixes (circuit build, guard):
3051 - On relays, properly check that a padding machine is absent before
3052 logging a warning about it being absent. Fixes bug 30649; bugfix
3054 - When considering upgrading circuits from "waiting for guard" to
3055 "open", always ignore circuits that are marked for close. Otherwise,
3056 we can end up in the situation where a subsystem is notified that
3057 a closing circuit has just opened, leading to undesirable
3058 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
3060 o Major bugfixes (onion service reachability):
3061 - Properly clean up the introduction point map when circuits change
3062 purpose from onion service circuits to pathbias, measurement, or
3063 other circuit types. This should fix some service-side instances
3064 of introduction point failure. Fixes bug 29034; bugfix
3067 o Major bugfixes (onion service v3):
3068 - Fix an unreachable bug in which an introduction point could try to
3069 send an INTRODUCE_ACK with a status code that Trunnel would refuse
3070 to encode, leading the relay to assert(). We've consolidated the
3071 ABI values into Trunnel now. Fixes bug 30454; bugfix
3073 - Clients can now handle unknown status codes from INTRODUCE_ACK
3074 cells. (The NACK behavior will stay the same.) This will allow us
3075 to extend status codes in the future without breaking the normal
3076 client behavior. Fixes another part of bug 30454; bugfix
3079 o Minor features (authenticated SENDME):
3080 - Ensure that there is enough randomness on every circuit to prevent
3081 an attacker from successfully predicting the hashes they will need
3082 to include in authenticated SENDME cells. At a random interval, if
3083 we have not sent randomness already, we now leave some extra space
3084 at the end of a cell that we can fill with random bytes. Closes
3087 o Minor features (circuit padding logging):
3088 - Demote noisy client-side warn logs about circuit padding to protocol
3089 warnings. Add additional log messages and circuit ID fields to help
3090 with bug 30992 and any other future issues.
3092 o Minor features (circuit padding):
3093 - We now use a fast PRNG when scheduling circuit padding. Part of
3095 - Allow the padding machine designer to pick the edges of their
3096 histogram instead of trying to compute them automatically using an
3097 exponential formula. Resolves some undefined behavior in the case
3098 of small histograms and allows greater flexibility on machine
3099 design. Closes ticket 29298; bugfix on 0.4.0.1-alpha.
3100 - Allow circuit padding machines to hold a circuit open until they
3101 are done padding it. Closes ticket 28780.
3103 o Minor features (compile-time modules):
3104 - Add a "--list-modules" command to print a list of which compile-
3105 time modules are enabled. Closes ticket 30452.
3107 o Minor features (continuous integration):
3108 - Our Travis configuration now uses Chutney to run some network
3109 integration tests automatically. Closes ticket 29280.
3110 - When running coverage builds on Travis, we now set
3111 TOR_TEST_RNG_SEED, to avoid RNG-based coverage differences. Part
3113 - Remove sudo configuration lines from .travis.yml as they are no
3114 longer needed with current Travis build environment. Resolves
3116 - In Travis, show stem's tor log after failure. Closes ticket 30234.
3118 o Minor features (controller):
3119 - Add onion service version 3 support to the HSFETCH command.
3120 Previously, only version 2 onion services were supported. Closes
3121 ticket 25417. Patch by Neel Chauhan.
3123 o Minor features (debugging):
3124 - Introduce tor_assertf() and tor_assertf_nonfatal() to enable
3125 logging of additional information during assert failure. Now we
3126 can use format strings to include information for trouble
3127 shooting. Resolves ticket 29662.
3129 o Minor features (defense in depth):
3130 - In smartlist_remove_keeporder(), set unused pointers to NULL, in
3131 case a bug causes them to be used later. Closes ticket 30176.
3132 Patch from Tobias Stoeckmann.
3133 - Tor now uses a cryptographically strong PRNG even for decisions
3134 that we do not believe are security-sensitive. Previously, for
3135 performance reasons, we had used a trivially predictable linear
3136 congruential generator algorithm for certain load-balancing and
3137 statistical sampling decisions. Now we use our fast RNG in those
3138 cases. Closes ticket 29542.
3140 o Minor features (developer tools):
3141 - Tor's "practracker" test script now checks for files and functions
3142 that seem too long and complicated. Existing overlong functions
3143 and files are accepted for now, but should eventually be
3144 refactored. Closes ticket 29221.
3145 - Add some scripts used for git maintenance to scripts/git. Closes
3147 - Call practracker from pre-push and pre-commit git hooks to let
3148 developers know if they made any code style violations. Closes
3150 - Add a script to check that each header has a well-formed and
3151 unique guard macro. Closes ticket 29756.
3153 o Minor features (fallback directory list):
3154 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
3155 in December 2018 (of which ~122 were still functional), with a
3156 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
3157 in June 2019. Closes ticket 28795.
3159 o Minor features (geoip):
3160 - Update geoip and geoip6 to the June 10 2019 Maxmind GeoLite2
3161 Country database. Closes ticket 30852.
3162 - Update geoip and geoip6 to the May 13 2019 Maxmind GeoLite2
3163 Country database. Closes ticket 30522.
3165 o Minor features (HTTP tunnel):
3166 - Return an informative web page when the HTTPTunnelPort is used as
3167 an HTTP proxy. Closes ticket 27821, patch by "eighthave".
3169 o Minor features (IPv6, v3 onion services):
3170 - Make v3 onion services put IPv6 addresses in service descriptors.
3171 Before this change, service descriptors only contained IPv4
3172 addresses. Implements 26992.
3174 o Minor features (logging):
3175 - Give a more useful assertion failure message if we think we have
3176 minherit() but we fail to make a region non-inheritable. Give a
3177 compile-time warning if our support for minherit() is incomplete.
3178 Closes ticket 30686.
3180 o Minor features (maintenance):
3181 - Add a new "make autostyle" target that developers can use to apply
3182 all automatic Tor style and consistency conversions to the
3183 codebase. Closes ticket 30539.
3185 o Minor features (modularity):
3186 - The "--disable-module-dirauth" compile-time option now disables
3187 even more dirauth-only code. Closes ticket 30345.
3189 o Minor features (performance):
3190 - Use OpenSSL's implementations of SHA3 when available (in OpenSSL
3191 1.1.1 and later), since they tend to be faster than tiny-keccak.
3192 Closes ticket 28837.
3194 o Minor features (testing):
3195 - The circuitpadding tests now use a reproducible RNG implementation,
3196 so that if a test fails, we can learn why. Part of ticket 28878.
3197 - Tor's tests now support an environment variable, TOR_TEST_RNG_SEED,
3198 to set the RNG seed for tests that use a reproducible RNG. Part of
3200 - When running tests in coverage mode, take additional care to make
3201 our coverage deterministic, so that we can accurately track
3202 changes in code coverage. Closes ticket 30519.
3203 - Tor's unit test code now contains helper functions to replace the
3204 PRNG with a deterministic or reproducible version for testing.
3205 Previously, various tests implemented this in various ways.
3206 Implements ticket 29732.
3207 - We now have a script, cov-test-determinism.sh, to identify places
3208 where our unit test coverage has become nondeterministic. Closes
3210 - Check that representative subsets of values of `int` and `unsigned
3211 int` can be represented by `void *`. Resolves issue 29537.
3213 o Minor bugfixes (bridge authority):
3214 - Bridge authorities now set bridges as running or non-running when
3215 about to dump their status to a file. Previously, they set bridges
3216 as running in response to a GETINFO command, but those shouldn't
3217 modify data structures. Fixes bug 24490; bugfix on 0.2.0.13-alpha.
3218 Patch by Neel Chauhan.
3220 o Minor bugfixes (channel padding statistics):
3221 - Channel padding write totals and padding-enabled totals are now
3222 counted properly in relay extrainfo descriptors. Fixes bug 29231;
3223 bugfix on 0.3.1.1-alpha.
3225 o Minor bugfixes (circuit isolation):
3226 - Fix a logic error that prevented the SessionGroup sub-option from
3227 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
3229 o Minor bugfixes (circuit padding):
3230 - Add a "CircuitPadding" torrc option to disable circuit padding.
3231 Fixes bug 28693; bugfix on 0.4.0.1-alpha.
3232 - Allow circuit padding machines to specify that they do not
3233 contribute much overhead, and provide consensus flags and torrc
3234 options to force clients to only use these low overhead machines.
3235 Fixes bug 29203; bugfix on 0.4.0.1-alpha.
3236 - Provide a consensus parameter to fully disable circuit padding, to
3237 be used in emergency network overload situations. Fixes bug 30173;
3238 bugfix on 0.4.0.1-alpha.
3239 - The circuit padding subsystem will no longer schedule padding if
3240 dormant mode is enabled. Fixes bug 28636; bugfix on 0.4.0.1-alpha.
3241 - Inspect a circuit-level cell queue before sending padding, to
3242 avoid sending padding while too much data is already queued. Fixes
3243 bug 29204; bugfix on 0.4.0.1-alpha.
3244 - Avoid calling monotime_absolute_usec() in circuit padding machines
3245 that do not use token removal or circuit RTT estimation. Fixes bug
3246 29085; bugfix on 0.4.0.1-alpha.
3248 o Minor bugfixes (clock skew detection):
3249 - Don't believe clock skew results from NETINFO cells that appear to
3250 arrive before we sent the VERSIONS cells they are responding to.
3251 Previously, we would accept them up to 3 minutes "in the past".
3252 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
3254 o Minor bugfixes (compatibility, standards compliance):
3255 - Fix a bug that would invoke undefined behavior on certain
3256 operating systems when trying to asprintf() a string exactly
3257 INT_MAX bytes long. We don't believe this is exploitable, but it's
3258 better to fix it anyway. Fixes bug 31001; bugfix on 0.2.2.11-alpha.
3259 Found and fixed by Tobias Stoeckmann.
3261 o Minor bugfixes (compilation warning):
3262 - Fix a compilation warning on Windows about casting a function
3263 pointer for GetTickCount64(). Fixes bug 31374; bugfix on
3266 o Minor bugfixes (compilation):
3267 - Avoid using labs() on time_t, which can cause compilation warnings
3268 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
3270 o Minor bugfixes (compilation, unusual configurations):
3271 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
3272 due to missing declarations of abort(), and prevent other such
3273 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
3275 o Minor bugfixes (configuration, proxies):
3276 - Fix a bug that prevented us from supporting SOCKS5 proxies that
3277 want authentication along with configured (but unused!)
3278 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
3280 o Minor bugfixes (continuous integration):
3281 - Allow the test-stem job to fail in Travis, because it sometimes
3282 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
3283 - Skip test_rebind on macOS in Travis, because it is unreliable on
3284 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3285 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
3286 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3288 o Minor bugfixes (controller protocol):
3289 - Teach the controller parser to distinguish an object preceded by
3290 an argument list from one without. Previously, it couldn't
3291 distinguish an argument list from the first line of a multiline
3292 object. Fixes bug 29984; bugfix on 0.2.3.8-alpha.
3294 o Minor bugfixes (crash on exit):
3295 - Avoid a set of possible code paths that could try to use freed
3296 memory in routerlist_free() while Tor was exiting. Fixes bug
3297 31003; bugfix on 0.1.2.2-alpha.
3299 o Minor bugfixes (developer tooling):
3300 - Fix pre-push hook to allow fixup and squash commits when pushing
3301 to non-upstream git remote. Fixes bug 30286; bugfix
3304 o Minor bugfixes (directory authorities):
3305 - Stop crashing after parsing an unknown descriptor purpose
3306 annotation. We think this bug can only be triggered by modifying a
3307 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
3308 - Move the "bandwidth-file-headers" line in directory authority
3309 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
3311 - Directory authorities with IPv6 support now always mark themselves
3312 as reachable via IPv6. Fixes bug 24338; bugfix on 0.2.4.1-alpha.
3313 Patch by Neel Chauhan.
3315 o Minor bugfixes (documentation):
3316 - Improve the documentation for using MapAddress with ".exit". Fixes
3317 bug 30109; bugfix on 0.1.0.1-rc.
3318 - Improve the monotonic time module and function documentation to
3319 explain what "monotonic" actually means, and document some results
3320 that have surprised people. Fixes bug 29640; bugfix
3322 - Use proper formatting when providing an example on quoting options
3323 that contain whitespace. Fixes bug 29635; bugfix on 0.2.3.18-rc.
3325 o Minor bugfixes (logging):
3326 - Do not log a warning when running with an OpenSSL version other
3327 than the one Tor was compiled with, if the two versions should be
3328 compatible. Previously, we would warn whenever the version was
3329 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
3330 - Warn operators when the MyFamily option is set but ContactInfo is
3331 missing, as the latter should be set too. Fixes bug 25110; bugfix
3334 o Minor bugfixes (memory leaks):
3335 - Avoid a minor memory leak that could occur on relays when failing
3336 to create a "keys" directory. Fixes bug 30148; bugfix
3338 - Fix a trivial memory leak when parsing an invalid value from a
3339 download schedule in the configuration. Fixes bug 30894; bugfix
3342 o Minor bugfixes (NetBSD):
3343 - Fix usage of minherit() on NetBSD and other platforms that define
3344 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
3345 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
3347 o Minor bugfixes (onion services):
3348 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
3349 implemenation) when failing to load an onion service client
3350 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
3351 - When refusing to launch a controller's HSFETCH request because of
3352 rate-limiting, respond to the controller with a new response,
3353 "QUERY_RATE_LIMITED". Previously, we would log QUERY_NO_HSDIR for
3354 this case. Fixes bug 28269; bugfix on 0.3.1.1-alpha. Patch by
3356 - When relaunching a circuit to a rendezvous service, mark the
3357 circuit as needing high-uptime routers as appropriate. Fixes bug
3358 17357; bugfix on 0.1.0.1-rc. Patch by Neel Chauhan.
3359 - Stop ignoring IPv6 link specifiers sent to v3 onion services.
3360 (IPv6 support for v3 onion services is still incomplete: see
3361 ticket 23493 for details.) Fixes bug 23588; bugfix on
3362 0.3.2.1-alpha. Patch by Neel Chauhan.
3364 o Minor bugfixes (onion services, performance):
3365 - When building circuits to onion services, call tor_addr_parse()
3366 less often. Previously, we called tor_addr_parse() in
3367 circuit_is_acceptable() even if its output wasn't used. This
3368 change should improve performance when building circuits. Fixes
3369 bug 22210; bugfix on 0.2.8.12. Patch by Neel Chauhan.
3371 o Minor bugfixes (out-of-memory handler):
3372 - When purging the DNS cache because of an out-of-memory condition,
3373 try purging just the older entries at first. Previously, we would
3374 always purge the whole thing. Fixes bug 29617; bugfix
3377 o Minor bugfixes (performance):
3378 - When checking whether a node is a bridge, use a fast check to make
3379 sure that its identity is set. Previously, we used a constant-time
3380 check, which is not necessary in this case. Fixes bug 30308;
3381 bugfix on 0.3.5.1-alpha.
3383 o Minor bugfixes (pluggable transports):
3384 - Tor now sets TOR_PT_EXIT_ON_STDIN_CLOSE=1 for client transports as
3385 well as servers. Fixes bug 25614; bugfix on 0.2.7.1-alpha.
3387 o Minor bugfixes (portability):
3388 - Avoid crashing in our tor_vasprintf() implementation on systems
3389 that define neither vasprintf() nor _vscprintf(). (This bug has
3390 been here long enough that we question whether people are running
3391 Tor on such systems, but we're applying the fix out of caution.)
3392 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
3395 o Minor bugfixes (probability distributions):
3396 - Refactor and improve parts of the probability distribution code
3397 that made Coverity complain. Fixes bug 29805; bugfix
3400 o Minor bugfixes (python):
3401 - Stop assuming that /usr/bin/python3 exists. For scripts that work
3402 with python2, use /usr/bin/python. Otherwise, use /usr/bin/env
3403 python3. Fixes bug 29913; bugfix on 0.2.5.3-alpha.
3405 o Minor bugfixes (relay):
3406 - When running as a relay, if IPv6Exit is set to 1 while ExitRelay
3407 is auto, act as if ExitRelay is 1. Previously, we would ignore
3408 IPv6Exit if ExitRelay was 0 or auto. Fixes bug 29613; bugfix on
3409 0.3.5.1-alpha. Patch by Neel Chauhan.
3411 o Minor bugfixes (static analysis):
3412 - Fix several spurious Coverity warnings about the unit tests, to
3413 lower our chances of missing real warnings in the future. Fixes
3414 bug 30150; bugfix on 0.3.5.1-alpha and various other Tor versions.
3416 o Minor bugfixes (stats):
3417 - When ExtraInfoStatistics is 0, stop including bandwidth usage
3418 statistics, GeoIPFile hashes, ServerTransportPlugin lines, and
3419 bridge statistics by country in extra-info documents. Fixes bug
3420 29018; bugfix on 0.2.4.1-alpha.
3422 o Minor bugfixes (testing):
3423 - Call setrlimit() to disable core dumps in test_bt_cl.c. Previously
3424 we used `ulimit -c` in test_bt.sh, which violates POSIX shell
3425 compatibility. Fixes bug 29061; bugfix on 0.3.5.1-alpha.
3426 - Fix some incorrect code in the v3 onion service unit tests. Fixes
3427 bug 29243; bugfix on 0.3.2.1-alpha.
3428 - In the "routerkeys/*" tests, check the return values of mkdir()
3429 for possible failures. Fixes bug 29939; bugfix on 0.2.7.2-alpha.
3430 Found by Coverity as CID 1444254.
3431 - Split test_utils_general() into several smaller test functions.
3432 This makes it easier to perform resource deallocation on assert
3433 failure, and fixes Coverity warnings CID 1444117 and CID 1444118.
3434 Fixes bug 29823; bugfix on 0.2.9.1-alpha.
3436 o Minor bugfixes (tor-resolve):
3437 - Fix a memory leak in tor-resolve that could happen if Tor gave it
3438 a malformed SOCKS response. (Memory leaks in tor-resolve don't
3439 actually matter, but it's good to fix them anyway.) Fixes bug
3440 30151; bugfix on 0.4.0.1-alpha.
3442 o Code simplification and refactoring:
3443 - Abstract out the low-level formatting of replies on the control
3444 port. Implements ticket 30007.
3445 - Add several assertions in an attempt to fix some Coverity
3446 warnings. Closes ticket 30149.
3447 - Introduce a connection_dir_buf_add() helper function that checks
3448 for compress_state of dir_connection_t and automatically writes a
3449 string to directory connection with or without compression.
3450 Resolves issue 28816.
3451 - Make the base32_decode() API return the number of bytes written,
3452 for consistency with base64_decode(). Closes ticket 28913.
3453 - Move most relay-only periodic events out of mainloop.c into the
3454 relay subsystem. Closes ticket 30414.
3455 - Refactor and encapsulate parts of the codebase that manipulate
3456 crypt_path_t objects. Resolves issue 30236.
3457 - Refactor several places in our code that Coverity incorrectly
3458 believed might have memory leaks. Closes ticket 30147.
3459 - Remove redundant return values in crypto_format, and the
3460 associated return value checks elsewhere in the code. Make the
3461 implementations in crypto_format consistent, and remove redundant
3462 code. Resolves ticket 29660.
3463 - Rename tor_mem_is_zero() to fast_mem_is_zero(), to emphasize that
3464 it is not a constant-time function. Closes ticket 30309.
3465 - Replace hs_desc_link_specifier_t with link_specifier_t, and remove
3466 all hs_desc_link_specifier_t-specific code. Fixes bug 22781;
3467 bugfix on 0.3.2.1-alpha.
3468 - Simplify v3 onion service link specifier handling code. Fixes bug
3469 23576; bugfix on 0.3.2.1-alpha.
3470 - Split crypto_digest.c into NSS code, OpenSSL code, and shared
3471 code. Resolves ticket 29108.
3472 - Split control.c into several submodules, in preparation for
3473 distributing its current responsibilities throughout the codebase.
3474 Closes ticket 29894.
3475 - Start to move responsibility for knowing about periodic events to
3476 the appropriate subsystems, so that the mainloop doesn't need to
3477 know all the periodic events in the rest of the codebase.
3478 Implements tickets 30293 and 30294.
3481 - Mention URLs for Travis/Appveyor/Jenkins in ReleasingTor.md.
3482 Closes ticket 30630.
3483 - Document how to find git commits and tags for bug fixes in
3484 CodingStandards.md. Update some file documentation. Closes
3488 - Remove the linux-tor-prio.sh script from contrib/operator-tools
3489 directory. Resolves issue 29434.
3490 - Remove the obsolete OpenSUSE initscript. Resolves issue 30076.
3491 - Remove the obsolete script at contrib/dist/tor.sh.in. Resolves
3495 - Specify torrc paths (with empty files) when launching tor in
3496 integration tests; refrain from reading user and system torrcs.
3497 Resolves issue 29702.
3499 o Code simplification and refactoring (shell scripts):
3500 - Clean up many of our shell scripts to fix shellcheck warnings.
3501 These include autogen.sh (ticket 26069), test_keygen.sh (ticket
3502 29062), test_switch_id.sh (ticket 29065), test_rebind.sh (ticket
3503 29063), src/test/fuzz/minimize.sh (ticket 30079), test_rust.sh
3504 (ticket 29064), torify (ticket 29070), asciidoc-helper.sh (29926),
3505 fuzz_multi.sh (30077), fuzz_static_testcases.sh (ticket 29059),
3506 nagios-check-tor-authority-cert (ticket 29071),
3507 src/test/fuzz/fixup_filenames.sh (ticket 30078), test-network.sh
3508 (ticket 29060), test_key_expiration.sh (ticket 30002),
3509 zero_length_keys.sh (ticket 29068), and test_workqueue_*.sh
3512 o Testing (chutney):
3513 - In "make test-network-all", test IPv6-only v3 single onion
3514 services, using the chutney network single-onion-v23-ipv6-md.
3515 Closes ticket 27251.
3517 o Testing (continuous integration):
3518 - In Travis, make stem log a controller trace to the console, and tail
3519 stem's tor log after failure. Closes ticket 30591.
3520 - In Travis, only run the stem tests that use a tor binary.
3521 Closes ticket 30694.
3524 Changes in version 0.4.0.5 - 2019-05-02
3525 This is the first stable release in the 0.4.0.x series. It contains
3526 improvements for power management and bootstrap reporting, as well as
3527 preliminary backend support for circuit padding to prevent some kinds
3528 of traffic analysis. It also continues our work in refactoring Tor for
3529 long-term maintainability.
3531 Per our support policy, we will support the 0.4.0.x series for nine
3532 months, or until three months after the release of a stable 0.4.1.x:
3533 whichever is longer. If you need longer-term support, please stick
3534 with 0.3.5.x, which will we plan to support until Feb 2022.
3536 Below are the changes since 0.3.5.7. For a complete list of changes
3537 since 0.4.0.4-rc, see the ChangeLog file.
3539 o Major features (battery management, client, dormant mode):
3540 - When Tor is running as a client, and it is unused for a long time,
3541 it can now enter a "dormant" state. When Tor is dormant, it avoids
3542 network and CPU activity until it is reawoken either by a user
3543 request or by a controller command. For more information, see the
3544 configuration options starting with "Dormant". Implements tickets
3546 - The client's memory of whether it is "dormant", and how long it
3547 has spent idle, persists across invocations. Implements
3549 - There is a DormantOnFirstStartup option that integrators can use
3550 if they expect that in many cases, Tor will be installed but
3553 o Major features (bootstrap reporting):
3554 - When reporting bootstrap progress, report the first connection
3555 uniformly, regardless of whether it's a connection for building
3556 application circuits. This allows finer-grained reporting of early
3557 progress than previously possible, with the improvements of ticket
3558 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.
3559 - When reporting bootstrap progress, treat connecting to a proxy or
3560 pluggable transport as separate from having successfully used that
3561 proxy or pluggable transport to connect to a relay. Closes tickets
3564 o Major features (circuit padding):
3565 - Implement preliminary support for the circuit padding portion of
3566 Proposal 254. The implementation supports Adaptive Padding (aka
3567 WTF-PAD) state machines for use between experimental clients and
3568 relays. Support is also provided for APE-style state machines that
3569 use probability distributions instead of histograms to specify
3570 inter-packet delay. At the moment, Tor does not provide any
3571 padding state machines that are used in normal operation: for now,
3572 this feature exists solely for experimentation. Closes
3575 o Major features (refactoring):
3576 - Tor now uses an explicit list of its own subsystems when
3577 initializing and shutting down. Previously, these systems were
3578 managed implicitly in various places throughout the codebase.
3579 (There may still be some subsystems using the old system.) Closes
3582 o Major bugfixes (cell scheduler, KIST, security):
3583 - Make KIST consider the outbuf length when computing what it can
3584 put in the outbuf. Previously, KIST acted as though the outbuf
3585 were empty, which could lead to the outbuf becoming too full. It
3586 is possible that an attacker could exploit this bug to cause a Tor
3587 client or relay to run out of memory and crash. Fixes bug 29168;
3588 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
3589 TROVE-2019-001 and CVE-2019-8955.
3591 o Major bugfixes (networking):
3592 - Gracefully handle empty username/password fields in SOCKS5
3593 username/password auth message and allow SOCKS5 handshake to
3594 continue. Previously, we had rejected these handshakes, breaking
3595 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
3597 o Major bugfixes (NSS, relay):
3598 - When running with NSS, disable TLS 1.2 ciphersuites that use
3599 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
3600 these ciphersuites don't work -- which caused relays to fail to
3601 handshake with one another when these ciphersuites were enabled.
3602 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
3604 o Major bugfixes (windows, startup):
3605 - When reading a consensus file from disk, detect whether it was
3606 written in text mode, and re-read it in text mode if so. Always
3607 write consensus files in binary mode so that we can map them into
3608 memory later. Previously, we had written in text mode, which
3609 confused us when we tried to map the file on windows. Fixes bug
3610 28614; bugfix on 0.4.0.1-alpha.
3612 o Minor features (address selection):
3613 - Treat the subnet 100.64.0.0/10 as public for some purposes;
3614 private for others. This subnet is the RFC 6598 (Carrier Grade
3615 NAT) IP range, and is deployed by many ISPs as an alternative to
3616 RFC 1918 that does not break existing internal networks. Tor now
3617 blocks SOCKS and control ports on these addresses and warns users
3618 if client ports or ExtORPorts are listening on a RFC 6598 address.
3619 Closes ticket 28525. Patch by Neel Chauhan.
3621 o Minor features (bandwidth authority):
3622 - Make bandwidth authorities ignore relays that are reported in the
3623 bandwidth file with the flag "vote=0". This change allows us to
3624 report unmeasured relays for diagnostic reasons without including
3625 their bandwidth in the bandwidth authorities' vote. Closes
3627 - When a directory authority is using a bandwidth file to obtain the
3628 bandwidth values that will be included in the next vote, serve
3629 this bandwidth file at /tor/status-vote/next/bandwidth. Closes
3632 o Minor features (bootstrap reporting):
3633 - When reporting bootstrap progress, stop distinguishing between
3634 situations where only internal paths are available and situations
3635 where external paths are available. Previously, Tor would often
3636 erroneously report that it had only internal paths. Closes
3639 o Minor features (compilation):
3640 - Compile correctly when OpenSSL is built with engine support
3641 disabled, or with deprecated APIs disabled. Closes ticket 29026.
3642 Patches from "Mangix".
3644 o Minor features (continuous integration):
3645 - On Travis Rust builds, cleanup Rust registry and refrain from
3646 caching the "target/" directory to speed up builds. Resolves
3648 - Log Python version during each Travis CI job. Resolves
3650 - In Travis, tell timelimit to use stem's backtrace signals, and
3651 launch python directly from timelimit, so python receives the
3652 signals from timelimit, rather than make. Closes ticket 30117.
3654 o Minor features (controller):
3655 - Add a DROPOWNERSHIP command to undo the effects of TAKEOWNERSHIP.
3656 Implements ticket 28843.
3658 o Minor features (developer tooling):
3659 - Check that bugfix versions in changes files look like Tor versions
3660 from the versions spec. Warn when bugfixes claim to be on a future
3661 release. Closes ticket 27761.
3662 - Provide a git pre-commit hook that disallows committing if we have
3663 any failures in our code and changelog formatting checks. It is
3664 now available in scripts/maint/pre-commit.git-hook. Implements
3666 - Provide a git hook script to prevent "fixup!" and "squash!"
3667 commits from ending up in the master branch, as scripts/main/pre-
3668 push.git-hook. Closes ticket 27993.
3670 o Minor features (diagnostic):
3671 - Add more diagnostic log messages in an attempt to solve the issue
3672 of NUL bytes appearing in a microdescriptor cache. Related to
3675 o Minor features (directory authority):
3676 - When a directory authority is using a bandwidth file to obtain
3677 bandwidth values, include the digest of that file in the vote.
3678 Closes ticket 26698.
3679 - Directory authorities support a new consensus algorithm, under
3680 which the family lines in microdescriptors are encoded in a
3681 canonical form. This change makes family lines more compressible
3682 in transit, and on the client. Closes ticket 28266; implements
3685 o Minor features (directory authority, relay):
3686 - Authorities now vote on a "StaleDesc" flag to indicate that a
3687 relay's descriptor is so old that the relay should upload again
3688 soon. Relays treat this flag as a signal to upload a new
3689 descriptor. This flag will eventually let us remove the
3690 'published' date from routerstatus entries, and make our consensus
3691 diffs much smaller. Closes ticket 26770; implements proposal 293.
3693 o Minor features (dormant mode):
3694 - Add a DormantCanceledByStartup option to tell Tor that it should
3695 treat a startup event as cancelling any previous dormant state.
3696 Integrators should use this option with caution: it should only be
3697 used if Tor is being started because of something that the user
3698 did, and not if Tor is being automatically started in the
3699 background. Closes ticket 29357.
3701 o Minor features (fallback directory mirrors):
3702 - Update the fallback whitelist based on operator opt-ins and opt-
3703 outs. Closes ticket 24805, patch by Phoul.
3705 o Minor features (FreeBSD):
3706 - On FreeBSD-based systems, warn relay operators if the
3707 "net.inet.ip.random_id" sysctl (IP ID randomization) is disabled.
3708 Closes ticket 28518.
3710 o Minor features (geoip):
3711 - Update geoip and geoip6 to the April 2 2019 Maxmind GeoLite2
3712 Country database. Closes ticket 29992.
3714 o Minor features (HTTP standards compliance):
3715 - Stop sending the header "Content-type: application/octet-stream"
3716 along with transparently compressed documents: this confused
3717 browsers. Closes ticket 28100.
3719 o Minor features (IPv6):
3720 - We add an option ClientAutoIPv6ORPort, to make clients randomly
3721 prefer a node's IPv4 or IPv6 ORPort. The random preference is set
3722 every time a node is loaded from a new consensus or bridge config.
3723 We expect that this option will enable clients to bootstrap more
3724 quickly without having to determine whether they support IPv4,
3725 IPv6, or both. Closes ticket 27490. Patch by Neel Chauhan.
3726 - When using addrs_in_same_network_family(), avoid choosing circuit
3727 paths that pass through the same IPv6 subnet more than once.
3728 Previously, we only checked IPv4 subnets. Closes ticket 24393.
3729 Patch by Neel Chauhan.
3731 o Minor features (log messages):
3732 - Improve log message in v3 onion services that could print out
3733 negative revision counters. Closes ticket 27707. Patch
3736 o Minor features (memory usage):
3737 - Save memory by storing microdescriptor family lists with a more
3738 compact representation. Closes ticket 27359.
3739 - Tor clients now use mmap() to read consensus files from disk, so
3740 that they no longer need keep the full text of a consensus in
3741 memory when parsing it or applying a diff. Closes ticket 27244.
3743 o Minor features (NSS, diagnostic):
3744 - Try to log an error from NSS (if there is any) and a more useful
3745 description of our situation if we are using NSS and a call to
3746 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
3748 o Minor features (parsing):
3749 - Directory authorities now validate that router descriptors and
3750 ExtraInfo documents are in a valid subset of UTF-8, and reject
3751 them if they are not. Closes ticket 27367.
3753 o Minor features (performance):
3754 - Cache the results of summarize_protocol_flags(), so that we don't
3755 have to parse the same protocol-versions string over and over.
3756 This should save us a huge number of malloc calls on startup, and
3757 may reduce memory fragmentation with some allocators. Closes
3759 - Remove a needless memset() call from get_token_arguments, thereby
3760 speeding up the tokenization of directory objects by about 20%.
3761 Closes ticket 28852.
3762 - Replace parse_short_policy() with a faster implementation, to
3763 improve microdescriptor parsing time. Closes ticket 28853.
3764 - Speed up directory parsing a little by avoiding use of the non-
3765 inlined strcmp_len() function. Closes ticket 28856.
3766 - Speed up microdescriptor parsing by about 30%, to help improve
3767 startup time. Closes ticket 28839.
3769 o Minor features (pluggable transports):
3770 - Add support for emitting STATUS updates to Tor's control port from
3771 a pluggable transport process. Closes ticket 28846.
3772 - Add support for logging to Tor's logging subsystem from a
3773 pluggable transport process. Closes ticket 28180.
3775 o Minor features (process management):
3776 - Add a new process API for handling child processes. This new API
3777 allows Tor to have bi-directional communication with child
3778 processes on both Unix and Windows. Closes ticket 28179.
3779 - Use the subsystem manager to initialize and shut down the process
3780 module. Closes ticket 28847.
3782 o Minor features (relay):
3783 - When listing relay families, list them in canonical form including
3784 the relay's own identity, and try to give a more useful set of
3785 warnings. Part of ticket 28266 and proposal 298.
3787 o Minor features (required protocols):
3788 - Before exiting because of a missing required protocol, Tor will
3789 now check the publication time of the consensus, and not exit
3790 unless the consensus is newer than the Tor program's own release
3791 date. Previously, Tor would not check the consensus publication
3792 time, and so might exit because of a missing protocol that might
3793 no longer be required in a current consensus. Implements proposal
3794 297; closes ticket 27735.
3796 o Minor features (testing):
3797 - Treat all unexpected ERR and BUG messages as test failures. Closes
3799 - Allow a HeartbeatPeriod of less than 30 minutes in testing Tor
3800 networks. Closes ticket 28840. Patch by Rob Jansen.
3801 - Use the approx_time() function when setting the "Expires" header
3802 in directory replies, to make them more testable. Needed for
3805 o Minor bugfixes (security):
3806 - Fix a potential double free bug when reading huge bandwidth files.
3807 The issue is not exploitable in the current Tor network because
3808 the vulnerable code is only reached when directory authorities
3809 read bandwidth files, but bandwidth files come from a trusted
3810 source (usually the authorities themselves). Furthermore, the
3811 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
3812 which are not used by any of the current authorities. Fixes bug
3813 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
3815 - Verify in more places that we are not about to create a buffer
3816 with more than INT_MAX bytes, to avoid possible OOB access in the
3817 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
3818 fixed by Tobias Stoeckmann.
3820 o Minor bugfix (continuous integration):
3821 - Reset coverage state on disk after Travis CI has finished. This
3822 should prevent future coverage merge errors from causing the test
3823 suite for the "process" subsystem to fail. The process subsystem
3824 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
3826 - Terminate test-stem if it takes more than 9.5 minutes to run.
3827 (Travis terminates the job after 10 minutes of no output.)
3828 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
3830 o Minor bugfixes (build, compatibility, rust):
3831 - Update Cargo.lock file to match the version made by the latest
3832 version of Rust, so that "make distcheck" will pass again. Fixes
3833 bug 29244; bugfix on 0.3.3.4-alpha.
3835 o Minor bugfixes (C correctness):
3836 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
3837 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
3840 o Minor bugfixes (client, clock skew):
3841 - Bootstrap successfully even when Tor's clock is behind the clocks
3842 on the authorities. Fixes bug 28591; bugfix on 0.2.0.9-alpha.
3843 - Select guards even if the consensus has expired, as long as the
3844 consensus is still reasonably live. Fixes bug 24661; bugfix
3847 o Minor bugfixes (compilation):
3848 - Fix compilation warnings in test_circuitpadding.c. Fixes bug
3849 29169; bugfix on 0.4.0.1-alpha.
3850 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
3851 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
3852 - Compile correctly on OpenBSD; previously, we were missing some
3853 headers required in order to detect it properly. Fixes bug 28938;
3854 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
3856 o Minor bugfixes (directory clients):
3857 - Mark outdated dirservers when Tor only has a reasonably live
3858 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
3860 o Minor bugfixes (directory mirrors):
3861 - Even when a directory mirror's clock is behind the clocks on the
3862 authorities, we now allow the mirror to serve "future"
3863 consensuses. Fixes bug 28654; bugfix on 0.3.0.1-alpha.
3865 o Minor bugfixes (DNS):
3866 - Gracefully handle an empty or absent resolve.conf file by falling
3867 back to using "localhost" as a DNS server (and hoping it works).
3868 Previously, we would just stop running as an exit. Fixes bug
3869 21900; bugfix on 0.2.1.10-alpha.
3871 o Minor bugfixes (documentation):
3872 - Describe the contents of the v3 onion service client authorization
3873 files correctly: They hold public keys, not private keys. Fixes
3874 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
3876 o Minor bugfixes (guards):
3877 - In count_acceptable_nodes(), the minimum number is now one bridge
3878 or guard node, and two non-guard nodes for a circuit. Previously,
3879 we had added up the sum of all nodes with a descriptor, but that
3880 could cause us to build failing circuits when we had either too
3881 many bridges or not enough guard nodes. Fixes bug 25885; bugfix on
3882 0.2.3.1-alpha. Patch by Neel Chauhan.
3884 o Minor bugfixes (IPv6):
3885 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
3886 IPv6 socket was bound using an address family of AF_INET instead
3887 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
3890 o Minor bugfixes (linux seccomp sandbox):
3891 - Fix startup crash when experimental sandbox support is enabled.
3892 Fixes bug 29150; bugfix on 0.4.0.1-alpha. Patch by Peter Gerber.
3894 o Minor bugfixes (logging):
3895 - Correct a misleading error message when IPv4Only or IPv6Only is
3896 used but the resolved address can not be interpreted as an address
3897 of the specified IP version. Fixes bug 13221; bugfix on
3898 0.2.3.9-alpha. Patch from Kris Katterjohn.
3899 - Log the correct port number for listening sockets when "auto" is
3900 used to let Tor pick the port number. Previously, port 0 was
3901 logged instead of the actual port number. Fixes bug 29144; bugfix
3902 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
3903 - Stop logging a BUG() warning when Tor is waiting for exit
3904 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
3905 - Avoid logging that we are relaxing a circuit timeout when that
3906 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
3907 - Log more information at "warning" level when unable to read a
3908 private key; log more information at "info" level when unable to
3909 read a public key. We had warnings here before, but they were lost
3910 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
3911 - Rework rep_hist_log_link_protocol_counts() to iterate through all
3912 link protocol versions when logging incoming/outgoing connection
3913 counts. Tor no longer skips version 5, and we won't have to
3914 remember to update this function when new link protocol version is
3915 developed. Fixes bug 28920; bugfix on 0.2.6.10.
3917 o Minor bugfixes (memory management):
3918 - Refactor the shared random state's memory management so that it
3919 actually takes ownership of the shared random value pointers.
3920 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
3921 - Stop leaking parts of the shared random state in the shared-random
3922 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
3924 o Minor bugfixes (misc):
3925 - The amount of total available physical memory is now determined
3926 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
3927 when it is defined and a 64-bit variant is not available. Fixes
3928 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
3930 o Minor bugfixes (networking):
3931 - Introduce additional checks into tor_addr_parse() to reject
3932 certain incorrect inputs that previously were not detected. Fixes
3933 bug 23082; bugfix on 0.2.0.10-alpha.
3935 o Minor bugfixes (onion service v3, client):
3936 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
3937 connection waiting for a descriptor that we actually have in the
3938 cache. It turns out that this can actually happen, though it is
3939 rare. Now, tor will recover and retry the descriptor. Fixes bug
3940 28669; bugfix on 0.3.2.4-alpha.
3942 o Minor bugfixes (onion services):
3943 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
3944 than one private key for a hidden service. Fixes bug 29040; bugfix
3946 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
3947 "debug" level. Tor used to log it as a warning, which caused very
3948 long log lines to appear for some users. Fixes bug 29135; bugfix
3950 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
3951 as a warning. Instead, log it as a protocol warning, because there
3952 is nothing that relay operators can do to fix it. Fixes bug 29029;
3953 bugfix on 0.2.5.7-rc.
3955 o Minor bugfixes (periodic events):
3956 - Refrain from calling routerlist_remove_old_routers() from
3957 check_descriptor_callback(). Instead, create a new hourly periodic
3958 event. Fixes bug 27929; bugfix on 0.2.8.1-alpha.
3960 o Minor bugfixes (pluggable transports):
3961 - Make sure that data is continously read from standard output and
3962 standard error pipes of a pluggable transport child-process, to
3963 avoid deadlocking when a pipe's buffer is full. Fixes bug 26360;
3964 bugfix on 0.2.3.6-alpha.
3966 o Minor bugfixes (rust):
3967 - Abort on panic in all build profiles, instead of potentially
3968 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
3970 o Minor bugfixes (scheduler):
3971 - When re-adding channels to the pending list, check the correct
3972 channel's sched_heap_idx. This issue has had no effect in mainline
3973 Tor, but could have led to bugs down the road in improved versions
3974 of our circuit scheduling code. Fixes bug 29508; bugfix
3977 o Minor bugfixes (shellcheck):
3978 - Look for scripts in their correct locations during "make
3979 shellcheck". Previously we had looked in the wrong place during
3980 out-of-tree builds. Fixes bug 30263; bugfix on 0.4.0.1-alpha.
3982 o Minor bugfixes (single onion services):
3983 - Allow connections to single onion services to remain idle without
3984 being disconnected. Previously, relays acting as rendezvous points
3985 for single onion services were mistakenly closing idle rendezvous
3986 circuits after 60 seconds, thinking that they were unused
3987 directory-fetching circuits that had served their purpose. Fixes
3988 bug 29665; bugfix on 0.2.1.26.
3990 o Minor bugfixes (stats):
3991 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
3992 relay and bridge extra-info documents. Fixes bug 29017; bugfix
3995 o Minor bugfixes (testing):
3996 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
3997 recent test-network.sh to use new chutney features in CI. Fixes
3998 bug 29703; bugfix on 0.2.9.1-alpha.
3999 - Fix a test failure on Windows caused by an unexpected "BUG"
4000 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
4002 - Downgrade some LOG_ERR messages in the address/* tests to
4003 warnings. The LOG_ERR messages were occurring when we had no
4004 configured network. We were failing the unit tests, because we
4005 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
4006 29530; bugfix on 0.3.5.8.
4007 - Fix our gcov wrapper script to look for object files at the
4008 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
4009 - Decrease the false positive rate of stochastic probability
4010 distribution tests. Fixes bug 29693; bugfix on 0.4.0.1-alpha.
4011 - Fix intermittent failures on an adaptive padding test. Fixes one
4012 case of bug 29122; bugfix on 0.4.0.1-alpha.
4013 - Disable an unstable circuit-padding test that was failing
4014 intermittently because of an ill-defined small histogram. Such
4015 histograms will be allowed again after 29298 is implemented. Fixes
4016 a second case of bug 29122; bugfix on 0.4.0.1-alpha.
4017 - Detect and suppress "bug" warnings from the util/time test on
4018 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
4019 - Do not log an error-level message if we fail to find an IPv6
4020 network interface from the unit tests. Fixes bug 29160; bugfix
4022 - Instead of relying on hs_free_all() to clean up all onion service
4023 objects in test_build_descriptors(), we now deallocate them one by
4024 one. This lets Coverity know that we are not leaking memory there
4025 and fixes CID 1442277. Fixes bug 28989; bugfix on 0.3.5.1-alpha.
4026 - Check the time in the "Expires" header using approx_time(). Fixes
4027 bug 30001; bugfix on 0.4.0.4-rc.
4029 o Minor bugfixes (TLS protocol):
4030 - When classifying a client's selection of TLS ciphers, if the
4031 client ciphers are not yet available, do not cache the result.
4032 Previously, we had cached the unavailability of the cipher list
4033 and never looked again, which in turn led us to assume that the
4034 client only supported the ancient V1 link protocol. This, in turn,
4035 was causing Stem integration tests to stall in some cases. Fixes
4036 bug 30021; bugfix on 0.2.4.8-alpha.
4038 o Minor bugfixes (UI):
4039 - Lower log level of unlink() errors during bootstrap. Fixes bug
4040 29930; bugfix on 0.4.0.1-alpha.
4042 o Minor bugfixes (usability):
4043 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
4044 Some users took this phrasing to mean that the mentioned guard was
4045 under their control or responsibility, which it is not. Fixes bug
4046 28895; bugfix on Tor 0.3.0.1-alpha.
4048 o Minor bugfixes (Windows, CI):
4049 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
4050 Windows Server 2012 R2 job. The remaining 2 jobs still provide
4051 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
4052 fast_finish, so failed jobs terminate the build immediately. Fixes
4053 bug 29601; bugfix on 0.3.5.4-alpha.
4055 o Code simplification and refactoring:
4056 - Introduce a connection_dir_buf_add() helper function that detects
4057 whether compression is in use, and adds a string accordingly.
4058 Resolves issue 28816.
4059 - Refactor handle_get_next_bandwidth() to use
4060 connection_dir_buf_add(). Implements ticket 29897.
4061 - Reimplement NETINFO cell parsing and generation to rely on
4062 trunnel-generated wire format handling code. Closes ticket 27325.
4063 - Remove unnecessary unsafe code from the Rust macro "cstr!". Closes
4065 - Rework SOCKS wire format handling to rely on trunnel-generated
4066 parsing/generation code. Resolves ticket 27620.
4067 - Split out bootstrap progress reporting from control.c into a
4068 separate file. Part of ticket 27402.
4069 - The .may_include files that we use to describe our directory-by-
4070 directory dependency structure now describe a noncircular
4071 dependency graph over the directories that they cover. Our
4072 checkIncludes.py tool now enforces this noncircularity. Closes
4076 - Clarify that Tor performs stream isolation among *Port listeners
4077 by default. Resolves issue 29121.
4078 - In the manpage entry describing MapAddress torrc setting, use
4079 example IP addresses from ranges specified for use in documentation
4080 by RFC 5737. Resolves issue 28623.
4081 - Mention that you cannot add a new onion service if Tor is already
4082 running with Sandbox enabled. Closes ticket 28560.
4083 - Improve ControlPort documentation. Mention that it accepts
4084 address:port pairs, and can be used multiple times. Closes
4086 - Document the exact output of "tor --version". Closes ticket 28889.
4089 - Remove the old check-tor script. Resolves issue 29072.
4090 - Stop responding to the 'GETINFO status/version/num-concurring' and
4091 'GETINFO status/version/num-versioning' control port commands, as
4092 those were deprecated back in 0.2.0.30. Also stop listing them in
4093 output of 'GETINFO info/names'. Resolves ticket 28757.
4094 - The scripts used to generate and maintain the list of fallback
4095 directories have been extracted into a new "fallback-scripts"
4096 repository. Closes ticket 27914.
4099 - Run shellcheck for scripts in the in scripts/ directory. Closes
4101 - Add unit tests for tokenize_string() and get_next_token()
4102 functions. Resolves ticket 27625.
4104 o Code simplification and refactoring (onion service v3):
4105 - Consolidate the authorized client descriptor cookie computation
4106 code from client and service into one function. Closes
4109 o Code simplification and refactoring (shell scripts):
4110 - Cleanup scan-build.sh to silence shellcheck warnings. Closes
4112 - Fix issues that shellcheck found in chutney-git-bisect.sh.
4113 Resolves ticket 28006.
4114 - Fix issues that shellcheck found in updateRustDependencies.sh.
4115 Resolves ticket 28012.
4116 - Fix shellcheck warnings in cov-diff script. Resolves issue 28009.
4117 - Fix shellcheck warnings in run_calltool.sh. Resolves ticket 28011.
4118 - Fix shellcheck warnings in run_trunnel.sh. Resolves issue 28010.
4119 - Fix shellcheck warnings in scripts/test/coverage. Resolves
4123 Changes in version 0.3.5.8 - 2019-02-21
4124 Tor 0.3.5.8 backports several fixes from later releases, including fixes
4125 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
4128 It also includes a fix for a medium-severity security bug affecting Tor
4129 0.3.2.1-alpha and later. All Tor instances running an affected release
4130 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
4132 o Major bugfixes (cell scheduler, KIST, security):
4133 - Make KIST consider the outbuf length when computing what it can
4134 put in the outbuf. Previously, KIST acted as though the outbuf
4135 were empty, which could lead to the outbuf becoming too full. It
4136 is possible that an attacker could exploit this bug to cause a Tor
4137 client or relay to run out of memory and crash. Fixes bug 29168;
4138 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
4139 TROVE-2019-001 and CVE-2019-8955.
4141 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
4142 - Gracefully handle empty username/password fields in SOCKS5
4143 username/password auth messsage and allow SOCKS5 handshake to
4144 continue. Previously, we had rejected these handshakes, breaking
4145 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
4147 o Minor features (compilation, backport from 0.4.0.2-alpha):
4148 - Compile correctly when OpenSSL is built with engine support
4149 disabled, or with deprecated APIs disabled. Closes ticket 29026.
4150 Patches from "Mangix".
4152 o Minor features (geoip):
4153 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
4154 Country database. Closes ticket 29478.
4156 o Minor features (testing, backport from 0.4.0.2-alpha):
4157 - Treat all unexpected ERR and BUG messages as test failures. Closes
4160 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
4161 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
4162 connection waiting for a descriptor that we actually have in the
4163 cache. It turns out that this can actually happen, though it is
4164 rare. Now, tor will recover and retry the descriptor. Fixes bug
4165 28669; bugfix on 0.3.2.4-alpha.
4167 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
4168 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
4169 IPv6 socket was bound using an address family of AF_INET instead
4170 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
4173 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
4174 - Update Cargo.lock file to match the version made by the latest
4175 version of Rust, so that "make distcheck" will pass again. Fixes
4176 bug 29244; bugfix on 0.3.3.4-alpha.
4178 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
4179 - Select guards even if the consensus has expired, as long as the
4180 consensus is still reasonably live. Fixes bug 24661; bugfix
4183 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
4184 - Compile correctly on OpenBSD; previously, we were missing some
4185 headers required in order to detect it properly. Fixes bug 28938;
4186 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
4188 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
4189 - Describe the contents of the v3 onion service client authorization
4190 files correctly: They hold public keys, not private keys. Fixes
4191 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
4193 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
4194 - Rework rep_hist_log_link_protocol_counts() to iterate through all
4195 link protocol versions when logging incoming/outgoing connection
4196 counts. Tor no longer skips version 5, and we won't have to
4197 remember to update this function when new link protocol version is
4198 developed. Fixes bug 28920; bugfix on 0.2.6.10.
4200 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
4201 - Log more information at "warning" level when unable to read a
4202 private key; log more information at "info" level when unable to
4203 read a public key. We had warnings here before, but they were lost
4204 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
4206 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
4207 - The amount of total available physical memory is now determined
4208 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
4209 when it is defined and a 64-bit variant is not available. Fixes
4210 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
4212 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
4213 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
4214 than one private key for a hidden service. Fixes bug 29040; bugfix
4216 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
4217 "debug" level. Tor used to log it as a warning, which caused very
4218 long log lines to appear for some users. Fixes bug 29135; bugfix
4220 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
4221 as a warning. Instead, log it as a protocol warning, because there
4222 is nothing that relay operators can do to fix it. Fixes bug 29029;
4223 bugfix on 0.2.5.7-rc.
4225 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
4226 - Mark outdated dirservers when Tor only has a reasonably live
4227 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
4229 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
4230 - Detect and suppress "bug" warnings from the util/time test on
4231 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
4232 - Do not log an error-level message if we fail to find an IPv6
4233 network interface from the unit tests. Fixes bug 29160; bugfix
4236 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
4237 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
4238 Some users took this phrasing to mean that the mentioned guard was
4239 under their control or responsibility, which it is not. Fixes bug
4240 28895; bugfix on Tor 0.3.0.1-alpha.
4243 Changes in version 0.3.4.11 - 2019-02-21
4244 Tor 0.3.4.11 is the third stable release in its series. It includes
4245 a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
4246 later. All Tor instances running an affected release should upgrade to
4247 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
4249 o Major bugfixes (cell scheduler, KIST, security):
4250 - Make KIST consider the outbuf length when computing what it can
4251 put in the outbuf. Previously, KIST acted as though the outbuf
4252 were empty, which could lead to the outbuf becoming too full. It
4253 is possible that an attacker could exploit this bug to cause a Tor
4254 client or relay to run out of memory and crash. Fixes bug 29168;
4255 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
4256 TROVE-2019-001 and CVE-2019-8955.
4258 o Minor features (geoip):
4259 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
4260 Country database. Closes ticket 29478.
4262 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
4263 - Update Cargo.lock file to match the version made by the latest
4264 version of Rust, so that "make distcheck" will pass again. Fixes
4265 bug 29244; bugfix on 0.3.3.4-alpha.
4267 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
4268 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
4269 as a warning. Instead, log it as a protocol warning, because there
4270 is nothing that relay operators can do to fix it. Fixes bug 29029;
4271 bugfix on 0.2.5.7-rc.
4274 Changes in version 0.3.3.12 - 2019-02-21
4275 Tor 0.3.3.12 fixes a medium-severity security bug affecting Tor
4276 0.3.2.1-alpha and later. All Tor instances running an affected release
4277 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
4279 This release marks the end of support for the Tor 0.3.3.x series. We
4280 recommend that users switch to either the Tor 0.3.4 series (supported
4281 until at least 10 June 2019), or the Tor 0.3.5 series, which will
4282 receive long-term support until at least 1 Feb 2022.
4284 o Major bugfixes (cell scheduler, KIST, security):
4285 - Make KIST consider the outbuf length when computing what it can
4286 put in the outbuf. Previously, KIST acted as though the outbuf
4287 were empty, which could lead to the outbuf becoming too full. It
4288 is possible that an attacker could exploit this bug to cause a Tor
4289 client or relay to run out of memory and crash. Fixes bug 29168;
4290 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
4291 TROVE-2019-001 and CVE-2019-8955.
4293 o Minor features (geoip):
4294 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
4295 Country database. Closes ticket 29478.
4297 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
4298 - Update Cargo.lock file to match the version made by the latest
4299 version of Rust, so that "make distcheck" will pass again. Fixes
4300 bug 29244; bugfix on 0.3.3.4-alpha.
4302 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
4303 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
4304 as a warning. Instead, log it as a protocol warning, because there
4305 is nothing that relay operators can do to fix it. Fixes bug 29029;
4306 bugfix on 0.2.5.7-rc.
4309 Changes in version 0.3.3.11 - 2019-01-07
4310 Tor 0.3.3.11 backports numerous fixes from later versions of Tor.
4311 numerous fixes, including an important fix for anyone using OpenSSL
4312 1.1.1. Anyone running an earlier version of Tor 0.3.3 should upgrade
4313 to this version, or to a later series.
4315 As a reminder, support the Tor 0.3.3 series will end on 22 Feb 2019.
4316 We anticipate that this will be the last release of Tor 0.3.3, unless
4317 some major bug is before then. Some time between now and then, users
4318 should switch to either the Tor 0.3.4 series (supported until at least
4319 10 June 2019), or the Tor 0.3.5 series, which will receive long-term
4320 support until at least 1 Feb 2022.
4322 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
4323 - Fix our usage of named groups when running as a TLS 1.3 client in
4324 OpenSSL 1.1.1. Previously, we only initialized EC groups when
4325 running as a relay, which caused clients to fail to negotiate TLS
4326 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
4329 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
4330 - Fix a use-after-free error that could be caused by passing Tor an
4331 impossible set of options that would fail during options_act().
4332 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
4334 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
4335 - Only run one online rust build in Travis, to reduce network
4336 errors. Skip offline rust builds on Travis for Linux gcc, because
4337 they're redundant. Implements ticket 27252.
4338 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
4339 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
4340 Linux with default settings, because all the non-default builds
4341 use gcc on Linux. Implements ticket 27252.
4343 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
4344 - Use the Travis Homebrew addon to install packages on macOS during
4345 Travis CI. The package list is the same, but the Homebrew addon
4346 does not do a `brew update` by default. Implements ticket 27738.
4348 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
4349 - Replace the 150 fallbacks originally introduced in Tor
4350 0.3.3.1-alpha in January 2018 (of which ~115 were still
4351 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
4352 removed) generated in December 2018. Closes ticket 24803.
4354 o Minor features (geoip):
4355 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
4356 Country database. Closes ticket 29012.
4358 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
4359 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
4360 key export function from handling long labels. When this bug is
4361 detected, Tor will disable TLS 1.3. We recommend upgrading to a
4362 version of OpenSSL without this bug when it becomes available.
4363 Closes ticket 28973.
4365 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
4366 - Update relay descriptor on bandwidth changes only when the uptime
4367 is smaller than 24h, in order to reduce the efficiency of guard
4368 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
4370 o Minor bugfixes (C correctness, backport from 0.3.5.4-alpha):
4371 - Avoid undefined behavior in an end-of-string check when parsing
4372 the BEGIN line in a directory object. Fixes bug 28202; bugfix
4375 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
4376 - Rewrite our assertion macros so that they no longer suppress the
4377 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
4379 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
4380 - Initialize a variable unconditionally in aes_new_cipher(), since
4381 some compilers cannot tell that we always initialize it before
4382 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
4384 o Minor bugfixes (directory authority, backport from 0.3.5.4-alpha):
4385 - Log additional info when we get a relay that shares an ed25519 ID
4386 with a different relay, instead making a BUG() warning. Fixes bug
4387 27800; bugfix on 0.3.2.1-alpha.
4389 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
4390 - When a user requests a group-readable DataDirectory, give it to
4391 them. Previously, when the DataDirectory and the CacheDirectory
4392 were the same, the default setting (0) for
4393 CacheDirectoryGroupReadable would override the setting for
4394 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
4397 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
4398 - When the onion service directory can't be created or has the wrong
4399 permissions, do not log a stack trace. Fixes bug 27335; bugfix
4402 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
4403 - Close all SOCKS request (for the same .onion) if the newly fetched
4404 descriptor is unusable. Before that, we would close only the first
4405 one leaving the other hanging and let to time out by themselves.
4406 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
4408 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
4409 - Don't warn so loudly when Tor is unable to decode an onion
4410 descriptor. This can now happen as a normal use case if a client
4411 gets a descriptor with client authorization but the client is not
4412 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
4414 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
4415 - When deleting an ephemeral onion service (DEL_ONION), do not close
4416 any rendezvous circuits in order to let the existing client
4417 connections finish by themselves or closed by the application. The
4418 HS v2 is doing that already so now we have the same behavior for
4419 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
4421 o Minor bugfixes (HTTP tunnel):
4422 - Fix a bug warning when closing an HTTP tunnel connection due to
4423 an HTTP request we couldn't handle. Fixes bug 26470; bugfix on
4426 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
4427 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
4428 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
4430 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
4431 - Ensure circuitmux queues are empty before scheduling or sending
4432 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
4434 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
4435 - Reject protocol names containing bytes other than alphanumeric
4436 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
4439 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
4440 - Compute protover votes correctly in the rust version of the
4441 protover code. Previously, the protover rewrite in 24031 allowed
4442 repeated votes from the same voter for the same protocol version
4443 to be counted multiple times in protover_compute_vote(). Fixes bug
4444 27649; bugfix on 0.3.3.5-rc.
4445 - Reject protover names that contain invalid characters. Fixes bug
4446 27687; bugfix on 0.3.3.1-alpha.
4448 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
4449 - protover_all_supported() would attempt to allocate up to 16GB on
4450 some inputs, leading to a potential memory DoS. Fixes bug 27206;
4451 bugfix on 0.3.3.5-rc.
4453 o Minor bugfixes (rust, backport from 0.3.5.4-alpha):
4454 - Fix a potential null dereference in protover_all_supported(). Add
4455 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
4456 - Return a string that can be safely freed by C code, not one
4457 created by the rust allocator, in protover_all_supported(). Fixes
4458 bug 27740; bugfix on 0.3.3.1-alpha.
4459 - Fix an API mismatch in the rust implementation of
4460 protover_compute_vote(). This bug could have caused crashes on any
4461 directory authorities running Tor with Rust (which we do not yet
4462 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
4464 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
4465 - If a unit test running in a subprocess exits abnormally or with a
4466 nonzero status code, treat the test as having failed, even if the
4467 test reported success. Without this fix, memory leaks don't cause
4468 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
4469 bugfix on 0.2.2.4-alpha.
4471 o Minor bugfixes (testing, backport from 0.3.5.4-alpha):
4472 - Treat backtrace test failures as expected on BSD-derived systems
4473 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
4474 (FreeBSD failures have been treated as expected since 18204 in
4475 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
4477 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
4478 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
4479 bugfix on 0.3.0.1-alpha.
4482 Changes in version 0.3.4.10 - 2019-01-07
4483 Tor 0.3.4.9 is the second stable release in its series; it backports
4484 numerous fixes, including an important fix for relays, and for anyone
4485 using OpenSSL 1.1.1. Anyone running an earlier version of Tor 0.3.4
4488 As a reminder, the Tor 0.3.4 series will be supported until 10 June
4489 2019. Some time between now and then, users should switch to the Tor
4490 0.3.5 series, which will receive long-term support until at least 1
4493 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
4494 - Fix our usage of named groups when running as a TLS 1.3 client in
4495 OpenSSL 1.1.1. Previously, we only initialized EC groups when
4496 running as a relay, which caused clients to fail to negotiate TLS
4497 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
4500 o Major bugfixes (relay, directory, backport from 0.3.5.7):
4501 - Always reactivate linked connections in the main loop so long as
4502 any linked connection has been active. Previously, connections
4503 serving directory information wouldn't get reactivated after the
4504 first chunk of data was sent (usually 32KB), which would prevent
4505 clients from bootstrapping. Fixes bug 28912; bugfix on
4506 0.3.4.1-alpha. Patch by "cypherpunks3".
4508 o Minor features (continuous integration, Windows, backport from 0.3.5.6-rc):
4509 - Always show the configure and test logs, and upload them as build
4510 artifacts, when building for Windows using Appveyor CI.
4513 o Minor features (controller, backport from 0.3.5.1-alpha):
4514 - For purposes of CIRC_BW-based dropped cell detection, track half-
4515 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
4516 bias check cells to arrive without counting it as dropped until
4517 either the END arrives, or the windows are empty. Closes
4520 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
4521 - Replace the 150 fallbacks originally introduced in Tor
4522 0.3.3.1-alpha in January 2018 (of which ~115 were still
4523 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
4524 removed) generated in December 2018. Closes ticket 24803.
4526 o Minor features (geoip):
4527 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
4528 Country database. Closes ticket 28395.
4530 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
4531 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
4532 key export function from handling long labels. When this bug is
4533 detected, Tor will disable TLS 1.3. We recommend upgrading to a
4534 version of OpenSSL without this bug when it becomes available.
4535 Closes ticket 28973.
4537 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
4538 - Initialize a variable unconditionally in aes_new_cipher(), since
4539 some compilers cannot tell that we always initialize it before
4540 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
4542 o Minor bugfixes (connection, relay, backport from 0.3.5.5-alpha):
4543 - Avoid a logging a BUG() stacktrace when closing connection held
4544 open because the write side is rate limited but not the read side.
4545 Now, the connection read side is simply shut down until Tor is
4546 able to flush the connection and close it. Fixes bug 27750; bugfix
4549 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.5-alpha):
4550 - Manually configure the zstd compiler options, when building using
4551 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
4552 not come with a pkg-config file. Fixes bug 28454; bugfix
4554 - Stop using an external OpenSSL install, and stop installing MSYS2
4555 packages, when building using mingw on Appveyor Windows CI. Fixes
4556 bug 28399; bugfix on 0.3.4.1-alpha.
4558 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.6-rc):
4559 - Explicitly specify the path to the OpenSSL library and do not
4560 download OpenSSL from Pacman, but instead use the library that is
4561 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
4563 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
4564 - When a user requests a group-readable DataDirectory, give it to
4565 them. Previously, when the DataDirectory and the CacheDirectory
4566 were the same, the default setting (0) for
4567 CacheDirectoryGroupReadable would override the setting for
4568 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
4571 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
4572 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
4573 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
4575 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
4576 - Don't warn so loudly when Tor is unable to decode an onion
4577 descriptor. This can now happen as a normal use case if a client
4578 gets a descriptor with client authorization but the client is not
4579 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
4581 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
4582 - When deleting an ephemeral onion service (DEL_ONION), do not close
4583 any rendezvous circuits in order to let the existing client
4584 connections finish by themselves or closed by the application. The
4585 HS v2 is doing that already so now we have the same behavior for
4586 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
4588 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
4589 - Update relay descriptor on bandwidth changes only when the uptime
4590 is smaller than 24h, in order to reduce the efficiency of guard
4591 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
4593 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
4594 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
4595 bugfix on 0.3.0.1-alpha.
4598 Changes in version 0.3.5.7 - 2019-01-07
4599 Tor 0.3.5.7 is the first stable release in its series; it includes
4600 compilation and portability fixes, and a fix for a severe problem
4601 affecting directory caches.
4603 The Tor 0.3.5 series includes several new features and performance
4604 improvements, including client authorization for v3 onion services,
4605 cleanups to bootstrap reporting, support for improved bandwidth-
4606 measurement tools, experimental support for NSS in place of OpenSSL,
4607 and much more. It also begins a full reorganization of Tor's code
4608 layout, for improved modularity and maintainability in the future.
4609 Finally, there is the usual set of performance improvements and
4610 bugfixes that we try to do in every release series.
4612 There are a couple of changes in the 0.3.5 that may affect
4613 compatibility. First, the default version for newly created onion
4614 services is now v3. Use the HiddenServiceVersion option if you want to
4615 override this. Second, some log messages related to bootstrapping have
4616 changed; if you use stem, you may need to update to the latest version
4617 so it will recognize them.
4619 We have designated 0.3.5 as a "long-term support" (LTS) series: we
4620 will continue to patch major bugs in typical configurations of 0.3.5
4621 until at least 1 Feb 2022. (We do not plan to provide long-term
4622 support for embedding, Rust support, NSS support, running a directory
4623 authority, or unsupported platforms. For these, you will need to stick
4624 with the latest stable release.)
4626 Below are the changes since 0.3.4.9. For a complete list of changes
4627 since 0.3.5.6-rc, see the ChangeLog file.
4629 o Major features (bootstrap):
4630 - Don't report directory progress until after a connection to a
4631 relay or bridge has succeeded. Previously, we'd report 80%
4632 progress based on cached directory information when we couldn't
4633 even connect to the network. Closes ticket 27169.
4635 o Major features (new code layout):
4636 - Nearly all of Tor's source code has been moved around into more
4637 logical places. The "common" directory is now divided into a set
4638 of libraries in "lib", and files in the "or" directory have been
4639 split into "core" (logic absolutely needed for onion routing),
4640 "feature" (independent modules in Tor), and "app" (to configure
4641 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
4642 more information. Closes ticket 26481.
4644 This refactoring is not complete: although the libraries have been
4645 refactored to be acyclic, the main body of Tor is still too
4646 interconnected. We will attempt to improve this in the future.
4648 o Major features (onion services v3):
4649 - Implement onion service client authorization at the descriptor
4650 level: only authorized clients can decrypt a service's descriptor
4651 to find out how to contact it. A new torrc option was added to
4652 control this client side: ClientOnionAuthDir <path>. On the
4653 service side, if the "authorized_clients/" directory exists in the
4654 onion service directory path, client configurations are read from
4655 the files within. See the manpage for more details. Closes ticket
4656 27547. Patch done by Suphanat Chunhapanya (haxxpop).
4657 - Improve revision counter generation in next-gen onion services.
4658 Onion services can now scale by hosting multiple instances on
4659 different hosts without synchronization between them, which was
4660 previously impossible because descriptors would get rejected by
4661 HSDirs. Addresses ticket 25552.
4662 - Version 3 onion services can now use the per-service
4663 HiddenServiceExportCircuitID option to differentiate client
4664 circuits. It communicates with the service by using the HAProxy
4665 protocol to assign virtual IP addresses to inbound client
4666 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
4668 o Major features (onion services, UI change):
4669 - For a newly created onion service, the default version is now 3.
4670 Tor still supports existing version 2 services, but the operator
4671 now needs to set "HiddenServiceVersion 2" in order to create a new
4672 version 2 service. For existing services, Tor now learns the
4673 version by reading the key file. Closes ticket 27215.
4675 o Major features (portability, cryptography, experimental, TLS):
4676 - Tor now has the option to compile with the NSS library instead of
4677 OpenSSL. This feature is experimental, and we expect that bugs may
4678 remain. It is mainly intended for environments where Tor's
4679 performance is not CPU-bound, and where NSS is already known to be
4680 installed. To try it out, configure Tor with the --enable-nss
4681 flag. Closes tickets 26631, 26815, and 26816.
4683 If you are experimenting with this option and using an old cached
4684 consensus, Tor may fail to start. To solve this, delete your
4685 "cached-consensus" and "cached-microdesc-consensus" files,
4686 (if present), and restart Tor.
4688 o Major features (relay, UI change):
4689 - Relays no longer run as exits by default. If the "ExitRelay"
4690 option is auto (or unset), and no exit policy is specified with
4691 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
4692 Previously in this case, we allowed exit traffic and logged a
4693 warning message. Closes ticket 21530. Patch by Neel Chauhan.
4694 - Tor now validates that the ContactInfo config option is valid UTF-
4695 8 when parsing torrc. Closes ticket 27428.
4697 o Major bugfixes (compilation):
4698 - Fix compilation on ARM (and other less-used CPUs) when compiling
4699 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
4701 o Major bugfixes (compilation, rust):
4702 - Rust tests can now build and run successfully with the
4703 --enable-fragile-hardening option enabled. Doing this currently
4704 requires the rust beta channel; it will be possible with stable
4705 rust once Rust version 1.31 is released. Patch from Alex Crichton.
4706 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
4708 o Major bugfixes (directory authority):
4709 - Actually check that the address we get from DirAuthority
4710 configuration line is valid IPv4. Explicitly disallow DirAuthority
4711 address to be a DNS hostname. Fixes bug 26488; bugfix
4714 o Major bugfixes (embedding, main loop):
4715 - When DisableNetwork becomes set, actually disable periodic events
4716 that are already enabled. (Previously, we would refrain from
4717 enabling new ones, but we would leave the old ones turned on.)
4718 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
4720 o Major bugfixes (main loop, bootstrap):
4721 - Make sure Tor bootstraps and works properly if only the
4722 ControlPort is set. Prior to this fix, Tor would only bootstrap
4723 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
4724 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
4726 o Major bugfixes (onion service v3):
4727 - On an intro point for a version 3 onion service, stop closing
4728 introduction circuits on a NACK. This lets the client decide
4729 whether to reuse the circuit or discard it. Previously, we closed
4730 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
4731 0.3.2.1-alpha. Patch by Neel Chaunan.
4733 o Major bugfixes (OpenSSL, portability):
4734 - Fix our usage of named groups when running as a TLS 1.3 client in
4735 OpenSSL 1.1.1. Previously, we only initialized EC groups when
4736 running as a relay, which caused clients to fail to negotiate TLS
4737 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
4740 o Major bugfixes (relay bandwidth statistics):
4741 - When we close relayed circuits, report the data in the circuit
4742 queues as being written in our relay bandwidth stats. This
4743 mitigates guard discovery and other attacks that close circuits
4744 for the explicit purpose of noticing this discrepancy in
4745 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
4747 o Major bugfixes (relay):
4748 - When our write bandwidth limit is exhausted, stop writing on the
4749 connection. Previously, we had a typo in the code that would make
4750 us stop reading instead, leading to relay connections being stuck
4751 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
4753 - Always reactivate linked connections in the main loop so long as
4754 any linked connection has been active. Previously, connections
4755 serving directory information wouldn't get reactivated after the
4756 first chunk of data was sent (usually 32KB), which would prevent
4757 clients from bootstrapping. Fixes bug 28912; bugfix on
4758 0.3.4.1-alpha. Patch by "cypherpunks3".
4760 o Major bugfixes (restart-in-process):
4761 - Fix a use-after-free error that could be caused by passing Tor an
4762 impossible set of options that would fail during options_act().
4763 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
4765 o Minor features (admin tools):
4766 - Add a new --key-expiration option to print the expiration date of
4767 the signing cert in an ed25519_signing_cert file. Resolves
4770 o Minor features (build):
4771 - If you pass the "--enable-pic" option to configure, Tor will try
4772 to tell the compiler to build position-independent code suitable
4773 to link into a dynamic library. (The default remains -fPIE, for
4774 code suitable for a relocatable executable.) Closes ticket 23846.
4776 o Minor features (code correctness, testing):
4777 - Tor's build process now includes a "check-includes" make target to
4778 verify that no module of Tor relies on any headers from a higher-
4779 level module. We hope to use this feature over time to help
4780 refactor our codebase. Closes ticket 26447.
4782 o Minor features (code layout):
4783 - We have a new "lowest-level" error-handling API for use by code
4784 invoked from within the logging module. With this interface, the
4785 logging code is no longer at risk of calling into itself if a
4786 failure occurs while it is trying to log something. Closes
4789 o Minor features (compilation):
4790 - When possible, place our warning flags in a separate file, to
4791 avoid flooding verbose build logs. Closes ticket 28924.
4792 - Tor's configure script now supports a --with-malloc= option to
4793 select your malloc implementation. Supported options are
4794 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
4795 default). Addresses part of ticket 20424. Based on a patch from
4798 o Minor features (config):
4799 - The "auto" keyword in torrc is now case-insensitive. Closes
4802 o Minor features (continuous integration):
4803 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
4805 - Add new CI job to Travis configuration to run stem-based
4806 integration tests. Closes ticket 27913.
4807 - Use the Travis Homebrew addon to install packages on macOS during
4808 Travis CI. The package list is the same, but the Homebrew addon
4809 does not do a `brew update` by default. Implements ticket 27738.
4810 - Report what program produced the mysterious core file that we
4811 occasionally see on Travis CI during make distcheck. Closes
4813 - Don't do a distcheck with --disable-module-dirauth in Travis.
4814 Implements ticket 27252.
4815 - Install libcap-dev and libseccomp2-dev so these optional
4816 dependencies get tested on Travis CI. Closes ticket 26560.
4817 - Only run one online rust build in Travis, to reduce network
4818 errors. Skip offline rust builds on Travis for Linux gcc, because
4819 they're redundant. Implements ticket 27252.
4820 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
4821 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
4822 Linux with default settings, because all the non-default builds
4823 use gcc on Linux. Implements ticket 27252.
4825 o Minor features (continuous integration, Windows):
4826 - Always show the configure and test logs, and upload them as build
4827 artifacts, when building for Windows using Appveyor CI.
4829 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
4830 Appveyor's CI. Closes ticket 28318.
4832 o Minor features (controller):
4833 - Emit CIRC_BW events as soon as we detect that we processed an
4834 invalid or otherwise dropped cell on a circuit. This allows
4835 vanguards and other controllers to react more quickly to dropped
4836 cells. Closes ticket 27678.
4837 - For purposes of CIRC_BW-based dropped cell detection, track half-
4838 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
4839 bias check cells to arrive without counting it as dropped until
4840 either the END arrives, or the windows are empty. Closes
4842 - Implement a 'GETINFO md/all' controller command to enable getting
4843 all known microdescriptors. Closes ticket 8323.
4844 - The GETINFO command now support an "uptime" argument, to return
4845 Tor's uptime in seconds. Closes ticket 25132.
4847 o Minor features (denial-of-service avoidance):
4848 - Make our OOM handler aware of the DNS cache so that it doesn't
4849 fill up the memory. This check is important for our DoS mitigation
4850 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
4852 o Minor features (development):
4853 - Tor's makefile now supports running the "clippy" Rust style tool
4854 on our Rust code. Closes ticket 22156.
4856 o Minor features (directory authority):
4857 - There is no longer an artificial upper limit on the length of
4858 bandwidth lines. Closes ticket 26223.
4859 - When a bandwidth file is used to obtain the bandwidth measurements,
4860 include this bandwidth file headers in the votes. Closes
4862 - Improved support for networks with only a single authority or a
4863 single fallback directory. Patch from Gabriel Somlo. Closes
4866 o Minor features (embedding API):
4867 - The Tor controller API now supports a function to launch Tor with
4868 a preconstructed owning controller FD, so that embedding
4869 applications don't need to manage controller ports and
4870 authentication. Closes ticket 24204.
4871 - The Tor controller API now has a function that returns the name
4872 and version of the backend implementing the API. Closes
4875 o Minor features (fallback directory list):
4876 - Replace the 150 fallbacks originally introduced in Tor
4877 0.3.3.1-alpha in January 2018 (of which ~115 were still
4878 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
4879 removed) generated in December 2018. Closes ticket 24803.
4881 o Minor features (geoip):
4882 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
4883 Country database. Closes ticket 29012.
4885 o Minor features (memory management):
4886 - Get Libevent to use the same memory allocator as Tor, by calling
4887 event_set_mem_functions() during initialization. Resolves
4890 o Minor features (memory usage):
4891 - When not using them, store legacy TAP public onion keys in DER-
4892 encoded format, rather than as expanded public keys. This should
4893 save several megabytes on typical clients. Closes ticket 27246.
4895 o Minor features (OpenSSL bug workaround):
4896 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
4897 key export function from handling long labels. When this bug is
4898 detected, Tor will disable TLS 1.3. We recommend upgrading to a
4899 version of OpenSSL without this bug when it becomes available.
4900 Closes ticket 28973.
4902 o Minor features (OpenSSL):
4903 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
4904 than our own. Resolves ticket 19979.
4906 o Minor features (performance):
4907 - Remove about 96% of the work from the function that we run at
4908 startup to test our curve25519_basepoint implementation. Since
4909 this function has yet to find an actual failure, we now only run
4910 it for 8 iterations instead of 200. Based on our profile
4911 information, this change should save around 8% of our startup time
4912 on typical desktops, and may have a similar effect on other
4913 platforms. Closes ticket 28838.
4914 - Stop re-validating our hardcoded Diffie-Hellman parameters on
4915 every startup. Doing this wasted time and cycles, especially on
4916 low-powered devices. Closes ticket 28851.
4918 o Minor features (Rust, code quality):
4919 - Improve rust code quality in the rust protover implementation by
4920 making it more idiomatic. Includes changing an internal API to
4921 take &str instead of &String. Closes ticket 26492.
4923 o Minor features (testing):
4924 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
4925 chutney. Implements ticket 27211.
4927 o Minor features (tor-resolve):
4928 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
4929 Side-effect of the refactoring for ticket 26526.
4931 o Minor features (UI):
4932 - Log each included configuration file or directory as we read it,
4933 to provide more visibility about where Tor is reading from. Patch
4934 from Unto Sten; closes ticket 27186.
4935 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
4936 Closes ticket 26703.
4938 o Minor bugfixes (32-bit OSX and iOS, timing):
4939 - Fix an integer overflow bug in our optimized 32-bit millisecond-
4940 difference algorithm for 32-bit Apple platforms. Previously, it
4941 would overflow when calculating the difference between two times
4942 more than 47 days apart. Fixes part of bug 27139; bugfix
4944 - Improve the precision of our 32-bit millisecond difference
4945 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
4946 bugfix on 0.3.4.1-alpha.
4947 - Relax the tolerance on the mainloop/update_time_jumps test when
4948 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
4951 o Minor bugfixes (bootstrap):
4952 - Try harder to get descriptors in non-exit test networks, by using
4953 the mid weight for the third hop when there are no exits. Fixes
4954 bug 27237; bugfix on 0.2.6.2-alpha.
4956 o Minor bugfixes (C correctness):
4957 - Avoid casting smartlist index to int implicitly, as it may trigger
4958 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
4959 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
4960 - Use time_t for all values in
4961 predicted_ports_prediction_time_remaining(). Rework the code that
4962 computes difference between durations/timestamps. Fixes bug 27165;
4963 bugfix on 0.3.1.1-alpha.
4965 o Minor bugfixes (client, memory usage):
4966 - When not running as a directory cache, there is no need to store
4967 the text of the current consensus networkstatus in RAM.
4968 Previously, however, clients would store it anyway, at a cost of
4969 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
4972 o Minor bugfixes (client, ReachableAddresses):
4973 - Instead of adding a "reject *:*" line to ReachableAddresses when
4974 loading the configuration, add one to the policy after parsing it
4975 in parse_reachable_addresses(). This prevents extra "reject *.*"
4976 lines from accumulating on reloads. Fixes bug 20874; bugfix on
4977 0.1.1.5-alpha. Patch by Neel Chauhan.
4979 o Minor bugfixes (code quality):
4980 - Rename sandbox_getaddrinfo() and other functions to no longer
4981 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
4982 bugfix on 0.2.7.1-alpha.
4984 o Minor bugfixes (code safety):
4985 - Rewrite our assertion macros so that they no longer suppress the
4986 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
4989 o Minor bugfixes (compilation):
4990 - Initialize a variable unconditionally in aes_new_cipher(), since
4991 some compilers cannot tell that we always initialize it before
4992 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
4994 o Minor bugfixes (configuration):
4995 - Refuse to start with relative file paths and RunAsDaemon set
4996 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
4999 o Minor bugfixes (configuration, Onion Services):
5000 - In rend_service_parse_port_config(), disallow any input to remain
5001 after address-port pair was parsed. This will catch address and
5002 port being whitespace-separated by mistake of the user. Fixes bug
5003 27044; bugfix on 0.2.9.10.
5005 o Minor bugfixes (connection, relay):
5006 - Avoid a logging a BUG() stacktrace when closing connection held
5007 open because the write side is rate limited but not the read side.
5008 Now, the connection read side is simply shut down until Tor is
5009 able to flush the connection and close it. Fixes bug 27750; bugfix
5012 o Minor bugfixes (continuous integration, Windows):
5013 - Stop reinstalling identical packages in our Windows CI. Fixes bug
5014 27464; bugfix on 0.3.4.1-alpha.
5015 - Install only the necessary mingw packages during our appveyor
5016 builds. This change makes the build a little faster, and prevents
5017 a conflict with a preinstalled mingw openssl that appveyor now
5018 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
5019 - Explicitly specify the path to the OpenSSL library and do not
5020 download OpenSSL from Pacman, but instead use the library that is
5021 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
5022 - Manually configure the zstd compiler options, when building using
5023 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
5024 not come with a pkg-config file. Fixes bug 28454; bugfix
5026 - Stop using an external OpenSSL install, and stop installing MSYS2
5027 packages, when building using mingw on Appveyor Windows CI. Fixes
5028 bug 28399; bugfix on 0.3.4.1-alpha.
5030 o Minor bugfixes (controller):
5031 - Consider all routerinfo errors other than "not a server" to be
5032 transient for the purpose of "GETINFO exit-policy/*" controller
5033 request. Print stacktrace in the unlikely case of failing to
5034 recompute routerinfo digest. Fixes bug 27034; bugfix
5037 o Minor bugfixes (correctness):
5038 - Fix an unreached code path where we checked the value of
5039 "hostname" inside send_resolved_hostname_cell(). Previously, we
5040 used it before checking it; now we check it first. Fixes bug
5041 28879; bugfix on 0.1.2.7-alpha.
5043 o Minor bugfixes (directory connection shutdown):
5044 - Avoid a double-close when shutting down a stalled directory
5045 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
5047 o Minor bugfixes (directory permissions):
5048 - When a user requests a group-readable DataDirectory, give it to
5049 them. Previously, when the DataDirectory and the CacheDirectory
5050 were the same, the default setting (0) for
5051 CacheDirectoryGroupReadable would override the setting for
5052 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
5055 o Minor bugfixes (HTTP tunnel):
5056 - Fix a bug warning when closing an HTTP tunnel connection due to an
5057 HTTP request we couldn't handle. Fixes bug 26470; bugfix
5060 o Minor bugfixes (ipv6):
5061 - In addrs_in_same_network_family(), we choose the subnet size based
5062 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
5063 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
5064 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
5066 o Minor bugfixes (Linux seccomp2 sandbox):
5067 - Permit the "shutdown()" system call, which is apparently used by
5068 OpenSSL under some circumstances. Fixes bug 28183; bugfix
5071 o Minor bugfixes (logging):
5072 - Stop talking about the Named flag in log messages. Clients have
5073 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
5075 - As a precaution, do an early return from log_addr_has_changed() if
5076 Tor is running as client. Also, log a stack trace for debugging as
5077 this function should only be called when Tor runs as server. Fixes
5078 bug 26892; bugfix on 0.1.1.9-alpha.
5079 - Refrain from mentioning bug 21018 in the logs, as it is already
5080 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
5082 o Minor bugfixes (logging, documentation):
5083 - When SafeLogging is enabled, scrub IP address in
5084 channel_tls_process_netinfo_cell(). Also, add a note to manpage
5085 that scrubbing is not guaranteed on loglevels below Notice. Fixes
5086 bug 26882; bugfix on 0.2.4.10-alpha.
5088 o Minor bugfixes (memory leaks):
5089 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
5090 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
5091 - Fix a small memory leak when calling Tor with --dump-config. Fixes
5092 bug 27893; bugfix on 0.3.2.1-alpha.
5094 o Minor bugfixes (netflow padding):
5095 - Ensure circuitmux queues are empty before scheduling or sending
5096 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
5098 o Minor bugfixes (onion service v2):
5099 - Log at level "info", not "warning", in the case that we do not
5100 have a consensus when a .onion request comes in. This can happen
5101 normally while bootstrapping. Fixes bug 27040; bugfix
5104 o Minor bugfixes (onion service v3):
5105 - When deleting an ephemeral onion service (DEL_ONION), do not close
5106 any rendezvous circuits in order to let the existing client
5107 connections finish by themselves or closed by the application. The
5108 HS v2 is doing that already so now we have the same behavior for
5109 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
5110 - Build the service descriptor's signing key certificate before
5111 uploading, so we always have a fresh one: leaving no chances for
5112 it to expire service side. Fixes bug 27838; bugfix
5114 - Stop dumping a stack trace when trying to connect to an intro
5115 point without having a descriptor for it. Fixes bug 27774; bugfix
5117 - When selecting a v3 rendezvous point, don't only look at the
5118 protover, but also check whether the curve25519 onion key is
5119 present. This way we avoid picking a relay that supports the v3
5120 rendezvous but for which we don't have the microdescriptor. Fixes
5121 bug 27797; bugfix on 0.3.2.1-alpha.
5122 - Close all SOCKS request (for the same .onion) if the newly fetched
5123 descriptor is unusable. Before that, we would close only the first
5124 one leaving the other hanging and let to time out by themselves.
5125 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
5126 - When the onion service directory can't be created or has the wrong
5127 permissions, do not log a stack trace. Fixes bug 27335; bugfix
5129 - When replacing a descriptor in the client cache, make sure to
5130 close all client introduction circuits for the old descriptor, so
5131 we don't end up with unusable leftover circuits. Fixes bug 27471;
5132 bugfix on 0.3.2.1-alpha.
5134 o Minor bugfixes (OS compatibility):
5135 - Properly handle configuration changes that move a listener to/from
5136 wildcard IP address. If the first attempt to bind a socket fails,
5137 close the old listener and try binding the socket again. Fixes bug
5138 17873; bugfix on 0.0.8pre-1.
5140 o Minor bugfixes (performance)::
5141 - Rework node_is_a_configured_bridge() to no longer call
5142 node_get_all_orports(), which was performing too many memory
5143 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
5145 o Minor bugfixes (protover):
5146 - Reject protocol names containing bytes other than alphanumeric
5147 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
5150 o Minor bugfixes (protover, rust):
5151 - Reject extra commas in version strings. Fixes bug 27197; bugfix
5153 - protover_all_supported() would attempt to allocate up to 16GB on
5154 some inputs, leading to a potential memory DoS. Fixes bug 27206;
5155 bugfix on 0.3.3.5-rc.
5156 - Compute protover votes correctly in the rust version of the
5157 protover code. Previously, the protover rewrite in 24031 allowed
5158 repeated votes from the same voter for the same protocol version
5159 to be counted multiple times in protover_compute_vote(). Fixes bug
5160 27649; bugfix on 0.3.3.5-rc.
5161 - Reject protover names that contain invalid characters. Fixes bug
5162 27687; bugfix on 0.3.3.1-alpha.
5164 o Minor bugfixes (relay shutdown, systemd):
5165 - Notify systemd of ShutdownWaitLength so it can be set to longer
5166 than systemd's TimeoutStopSec. In Tor's systemd service file, set
5167 TimeoutSec to 60 seconds to allow Tor some time to shut down.
5168 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
5170 o Minor bugfixes (relay statistics):
5171 - Update relay descriptor on bandwidth changes only when the uptime
5172 is smaller than 24h, in order to reduce the efficiency of guard
5173 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
5175 o Minor bugfixes (relay):
5176 - Consider the fact that we'll be making direct connections to our
5177 entry and guard nodes when computing the fraction of nodes that
5178 have their descriptors. Also, if we are using bridges and there is
5179 at least one bridge with a full descriptor, treat the fraction of
5180 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
5181 Patch by Neel Chauhan.
5182 - Update the message logged on relays when DirCache is disabled.
5183 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
5184 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
5186 o Minor bugfixes (testing):
5187 - Stop running stem's unit tests as part of "make test-stem", but
5188 continue to run stem's unit and online tests during "make test-
5189 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
5190 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
5191 bugfix on 0.3.0.1-alpha.
5192 - Make the hs_service tests use the same time source when creating
5193 the introduction point and when testing it. Now tests work better
5194 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
5196 - Revise the "conditionvar_timeout" test so that it succeeds even on
5197 heavily loaded systems where the test threads are not scheduled
5198 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
5199 - Fix two unit tests to work when HOME environment variable is not
5200 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
5201 - If a unit test running in a subprocess exits abnormally or with a
5202 nonzero status code, treat the test as having failed, even if the
5203 test reported success. Without this fix, memory leaks don't cause
5204 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
5205 bugfix on 0.2.2.4-alpha.
5206 - When logging a version mismatch in our openssl_version tests,
5207 report the actual offending version strings. Fixes bug 26152;
5208 bugfix on 0.2.9.1-alpha.
5209 - Fix forking tests on Windows when there is a space somewhere in
5210 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
5212 o Minor bugfixes (Windows):
5213 - Correctly identify Windows 8.1, Windows 10, and Windows Server
5214 2008 and later from their NT versions. Fixes bug 28096; bugfix on
5215 0.2.2.34; reported by Keifer Bly.
5216 - On recent Windows versions, the GetVersionEx() function may report
5217 an earlier Windows version than the running OS. To avoid user
5218 confusion, add "[or later]" to Tor's version string on affected
5219 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
5221 - Remove Windows versions that were never supported by the
5222 GetVersionEx() function. Stop duplicating the latest Windows
5223 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
5224 reported by Keifer Bly.
5226 o Code simplification and refactoring:
5227 - When parsing a port configuration, make it more obvious to static
5228 analyzer tools that we always initialize the address. Closes
5230 - Divide more large Tor source files -- especially ones that span
5231 multiple areas of functionality -- into smaller parts, including
5232 onion.c and main.c. Closes ticket 26747.
5233 - Divide the "routerparse.c" module into separate modules for each
5234 group of parsed objects. Closes ticket 27924.
5235 - Move protover_rust.c to the same place protover.c was moved to.
5236 Closes ticket 27814.
5237 - Split directory.c into separate pieces for client, server, and
5238 common functionality. Closes ticket 26744.
5239 - Split the non-statistics-related parts from the rephist.c and
5240 geoip.c modules. Closes ticket 27892.
5241 - Split the router.c file into relay-only and shared components, to
5242 help with future modularization. Closes ticket 27864.
5243 - Divide the routerlist.c and dirserv.c modules into smaller parts.
5244 Closes ticket 27799.
5245 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
5246 longer needed. Closes ticket 26502.
5247 - Include paths to header files within Tor are now qualified by
5248 directory within the top-level src directory.
5249 - Many structures have been removed from the centralized "or.h"
5250 header, and moved into their own headers. This will allow us to
5251 reduce the number of places in the code that rely on each
5252 structure's contents and layout. Closes ticket 26383.
5253 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
5254 - Remove GetAdaptersAddresses_fn_t. The code that used it was
5255 removed as part of the 26481 refactor. Closes ticket 27467.
5256 - Rework Tor SOCKS server code to use Trunnel and benefit from
5257 autogenerated functions for parsing and generating SOCKS wire
5258 format. New implementation is cleaner, more maintainable and
5259 should be less prone to heartbleed-style vulnerabilities.
5260 Implements a significant fraction of ticket 3569.
5261 - Split sampled_guards_update_from_consensus() and
5262 select_entry_guard_for_circuit() into subfunctions. In
5263 entry_guards_update_primary() unite three smartlist enumerations
5264 into one and move smartlist comparison code out of the function.
5265 Closes ticket 21349.
5266 - Tor now assumes that you have standards-conformant stdint.h and
5267 inttypes.h headers when compiling. Closes ticket 26626.
5268 - Unify our bloom filter logic. Previously we had two copies of this
5269 code: one for routerlist filtering, and one for address set
5270 calculations. Closes ticket 26510.
5271 - Use the simpler strcmpstart() helper in
5272 rend_parse_v2_service_descriptor instead of strncmp(). Closes
5274 - Utility functions that can perform a DNS lookup are now wholly
5275 separated from those that can't, in separate headers and C
5276 modules. Closes ticket 26526.
5279 - In the tor-resolve(1) manpage, fix the reference to socks-
5280 extensions.txt by adding a web URL. Resolves ticket 27853.
5281 - Mention that we require Python to be 2.7 or newer for some
5282 integration tests that we ship with Tor. Resolves ticket 27677.
5283 - Copy paragraph and URL to Tor's code of conduct document from
5284 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
5285 - Remove old instructions from INSTALL document. Closes ticket 26588.
5286 - Warn users that they should not include MyFamily line(s) in their
5287 torrc when running Tor bridge. Closes ticket 26908.
5290 - Tor no longer supports building with the dmalloc library. For
5291 debugging memory issues, we suggest using gperftools or msan
5292 instead. Closes ticket 26426.
5293 - Tor no longer attempts to run on Windows environments without the
5294 GetAdaptersAddresses() function. This function has existed since
5295 Windows XP, which is itself already older than we support.
5296 - Remove Tor2web functionality for version 2 onion services. The
5297 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
5298 (This feature was never shipped in vanilla Tor and it was only
5299 possible to use this feature by building the support at compile
5300 time. Tor2webMode is not implemented for version 3 onion services.)
5301 Closes ticket 26367.
5304 - Increase logging and tag all log entries with timestamps in
5305 test_rebind.py. Provides diagnostics for issue 28229.
5307 o Code simplification and refactoring (shared random, dirauth):
5308 - Change many tor_assert() to use BUG() instead. The idea is to not
5309 crash a dirauth but rather scream loudly with a stacktrace and let
5310 it continue run. The shared random subsystem is very resilient and
5311 if anything wrong happens with it, at worst a non coherent value
5312 will be put in the vote and discarded by the other authorities.
5313 Closes ticket 19566.
5315 o Documentation (onion services):
5316 - Improve HSv3 client authorization by making some options more
5317 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
5318 - Document in the man page that changing ClientOnionAuthDir value or
5319 adding a new file in the directory will not work at runtime upon
5320 sending a HUP if Sandbox 1. Closes ticket 28128.
5321 - Note in the man page that the only real way to fully revoke an
5322 onion service v3 client authorization is by restarting the tor
5323 process. Closes ticket 28275.
5326 Changes in version 0.3.4.9 - 2018-11-02
5327 Tor 0.3.4.9 is the second stable release in its series; it backports
5328 numerous fixes, including a fix for a bandwidth management bug that
5329 was causing memory exhaustion on relays. Anyone running an earlier
5330 version of Tor 0.3.4.9 should upgrade.
5332 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
5333 - Fix compilation on ARM (and other less-used CPUs) when compiling
5334 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
5336 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
5337 - Make sure Tor bootstraps and works properly if only the
5338 ControlPort is set. Prior to this fix, Tor would only bootstrap
5339 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
5340 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
5342 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
5343 - When our write bandwidth limit is exhausted, stop writing on the
5344 connection. Previously, we had a typo in the code that would make
5345 us stop reading instead, leading to relay connections being stuck
5346 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
5349 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
5350 - Fix a use-after-free error that could be caused by passing Tor an
5351 impossible set of options that would fail during options_act().
5352 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
5354 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
5355 - Don't do a distcheck with --disable-module-dirauth in Travis.
5356 Implements ticket 27252.
5357 - Only run one online rust build in Travis, to reduce network
5358 errors. Skip offline rust builds on Travis for Linux gcc, because
5359 they're redundant. Implements ticket 27252.
5360 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
5361 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
5362 Linux with default settings, because all the non-default builds
5363 use gcc on Linux. Implements ticket 27252.
5365 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
5366 - Use the Travis Homebrew addon to install packages on macOS during
5367 Travis CI. The package list is the same, but the Homebrew addon
5368 does not do a `brew update` by default. Implements ticket 27738.
5370 o Minor features (geoip):
5371 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
5372 Country database. Closes ticket 27991.
5374 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
5375 - Fix an integer overflow bug in our optimized 32-bit millisecond-
5376 difference algorithm for 32-bit Apple platforms. Previously, it
5377 would overflow when calculating the difference between two times
5378 more than 47 days apart. Fixes part of bug 27139; bugfix
5380 - Improve the precision of our 32-bit millisecond difference
5381 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
5382 bugfix on 0.3.4.1-alpha.
5383 - Relax the tolerance on the mainloop/update_time_jumps test when
5384 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
5387 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
5388 - Avoid undefined behavior in an end-of-string check when parsing
5389 the BEGIN line in a directory object. Fixes bug 28202; bugfix
5392 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
5393 - Only install the necessary mingw packages during our appveyor
5394 builds. This change makes the build a little faster, and prevents
5395 a conflict with a preinstalled mingw openssl that appveyor now
5396 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
5398 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
5399 - Rewrite our assertion macros so that they no longer suppress the
5400 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
5402 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
5403 - Stop reinstalling identical packages in our Windows CI. Fixes bug
5404 27464; bugfix on 0.3.4.1-alpha.
5406 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
5407 - Log additional info when we get a relay that shares an ed25519 ID
5408 with a different relay, instead making a BUG() warning. Fixes bug
5409 27800; bugfix on 0.3.2.1-alpha.
5411 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
5412 - Avoid a double-close when shutting down a stalled directory
5413 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
5415 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
5416 - Fix a bug warning when closing an HTTP tunnel connection due to an
5417 HTTP request we couldn't handle. Fixes bug 26470; bugfix
5420 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
5421 - Ensure circuitmux queues are empty before scheduling or sending
5422 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
5424 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
5425 - When the onion service directory can't be created or has the wrong
5426 permissions, do not log a stack trace. Fixes bug 27335; bugfix
5429 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
5430 - Close all SOCKS request (for the same .onion) if the newly fetched
5431 descriptor is unusable. Before that, we would close only the first
5432 one leaving the other hanging and let to time out by themselves.
5433 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
5435 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
5436 - When selecting a v3 rendezvous point, don't only look at the
5437 protover, but also check whether the curve25519 onion key is
5438 present. This way we avoid picking a relay that supports the v3
5439 rendezvous but for which we don't have the microdescriptor. Fixes
5440 bug 27797; bugfix on 0.3.2.1-alpha.
5442 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
5443 - Reject protocol names containing bytes other than alphanumeric
5444 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
5447 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
5448 - Compute protover votes correctly in the rust version of the
5449 protover code. Previously, the protover rewrite in 24031 allowed
5450 repeated votes from the same voter for the same protocol version
5451 to be counted multiple times in protover_compute_vote(). Fixes bug
5452 27649; bugfix on 0.3.3.5-rc.
5453 - Reject protover names that contain invalid characters. Fixes bug
5454 27687; bugfix on 0.3.3.1-alpha.
5456 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
5457 - protover_all_supported() would attempt to allocate up to 16GB on
5458 some inputs, leading to a potential memory DoS. Fixes bug 27206;
5459 bugfix on 0.3.3.5-rc.
5461 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
5462 - Fix an API mismatch in the rust implementation of
5463 protover_compute_vote(). This bug could have caused crashes on any
5464 directory authorities running Tor with Rust (which we do not yet
5465 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
5467 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
5468 - Fix a potential null dereference in protover_all_supported(). Add
5469 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
5470 - Return a string that can be safely freed by C code, not one
5471 created by the rust allocator, in protover_all_supported(). Fixes
5472 bug 27740; bugfix on 0.3.3.1-alpha.
5474 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
5475 - If a unit test running in a subprocess exits abnormally or with a
5476 nonzero status code, treat the test as having failed, even if the
5477 test reported success. Without this fix, memory leaks don't cause
5478 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
5479 bugfix on 0.2.2.4-alpha.
5481 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
5482 - Make the hs_service tests use the same time source when creating
5483 the introduction point and when testing it. Now tests work better
5484 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
5487 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
5488 - Treat backtrace test failures as expected on BSD-derived systems
5489 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
5490 (FreeBSD failures have been treated as expected since 18204 in
5491 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
5494 Changes in version 0.2.9.17 - 2018-09-10
5495 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
5497 o Minor features (compatibility, backport from 0.3.4.8):
5498 - Tell OpenSSL to maintain backward compatibility with previous
5499 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
5500 ciphers are disabled by default. Closes ticket 27344.
5502 o Minor features (continuous integration, backport from 0.3.4.7-rc):
5503 - Enable macOS builds in our Travis CI configuration. Closes
5505 - Install libcap-dev and libseccomp2-dev so these optional
5506 dependencies get tested on Travis CI. Closes ticket 26560.
5507 - Run asciidoc during Travis CI. Implements ticket 27087.
5508 - Use ccache in our Travis CI configuration. Closes ticket 26952.
5510 o Minor features (geoip):
5511 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
5512 Country database. Closes ticket 27089.
5514 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
5515 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
5516 tell the compiler not to include the system malloc implementation.
5517 Fixes bug 20424; bugfix on 0.2.0.20-rc.
5519 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
5520 - Silence a spurious compiler warning on the GetAdaptersAddresses
5521 function pointer cast. This issue is already fixed by 26481 in
5522 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
5523 bugfix on 0.2.3.11-alpha.
5524 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
5525 supported, and always fails. Some compilers warn about the
5526 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
5529 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
5530 - Don't link or search for pthreads when building for Windows, even
5531 if we are using build environment (like mingw) that provides a
5532 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
5534 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
5535 - Skip a pair of unreliable key generation tests on Windows, until
5536 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
5537 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
5539 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
5540 - Pass the module flags to distcheck configure, and log the flags
5541 before running configure. (Backported to 0.2.9 and later as a
5542 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
5544 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
5545 - When a Travis build fails, and showing a log fails, keep trying to
5546 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
5547 - When we use echo in Travis, don't pass a --flag as the first
5548 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
5550 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
5551 - When voting for recommended versions, make sure that all of the
5552 versions are well-formed and parsable. Fixes bug 26485; bugfix
5555 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
5556 - Fix a bug in out sandboxing rules for the openat() syscall.
5557 Previously, no openat() call would be permitted, which would break
5558 filesystem operations on recent glibc versions. Fixes bug 25440;
5559 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
5561 o Minor bugfixes (onion services, backport from 0.3.4.8):
5562 - Silence a spurious compiler warning in
5563 rend_client_send_introduction(). Fixes bug 27463; bugfix
5566 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
5567 - Log a protocol warning when single onion services or Tor2web clients
5568 fail to authenticate direct connections to relays.
5569 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
5571 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
5572 - Disable core dumps in test_bt.sh, to avoid failures in "make
5573 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
5575 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
5576 - Before running make test-network-all, delete old logs and test
5577 result files, to avoid spurious failures. Fixes bug 27295; bugfix
5580 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
5581 - Our "tortls/cert_matches_key" unit test no longer relies on
5582 OpenSSL internals. Previously, it relied on unsupported OpenSSL
5583 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
5584 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
5586 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
5587 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
5588 27185; bugfix on 0.2.2.2-alpha.
5591 Changes in version 0.3.2.12 - 2018-09-10
5592 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
5594 o Minor features (compatibility, backport from 0.3.4.8):
5595 - Tell OpenSSL to maintain backward compatibility with previous
5596 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
5597 ciphers are disabled by default. Closes ticket 27344.
5599 o Minor features (continuous integration, backport from 0.3.4.7-rc):
5600 - Enable macOS builds in our Travis CI configuration. Closes
5602 - Install libcap-dev and libseccomp2-dev so these optional
5603 dependencies get tested on Travis CI. Closes ticket 26560.
5604 - Run asciidoc during Travis CI. Implements ticket 27087.
5605 - Use ccache in our Travis CI configuration. Closes ticket 26952.
5607 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
5608 - Use cargo cache in our Travis CI configuration. Closes
5611 o Minor features (controller, backport from 0.3.4.6-rc):
5612 - The control port now exposes the list of HTTPTunnelPorts and
5613 ExtOrPorts via GETINFO net/listeners/httptunnel and
5614 net/listeners/extor respectively. Closes ticket 26647.
5616 o Minor features (directory authorities, backport from 0.3.4.7-rc):
5617 - Authorities no longer vote to make the subprotocol version
5618 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
5619 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
5621 o Minor features (geoip):
5622 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
5623 Country database. Closes ticket 27089.
5625 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
5626 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
5627 tell the compiler not to include the system malloc implementation.
5628 Fixes bug 20424; bugfix on 0.2.0.20-rc.
5629 - Don't try to use a pragma to temporarily disable the
5630 -Wunused-const-variable warning if the compiler doesn't support
5631 it. Fixes bug 26785; bugfix on 0.3.2.11.
5633 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
5634 - Silence a spurious compiler warning on the GetAdaptersAddresses
5635 function pointer cast. This issue is already fixed by 26481 in
5636 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
5637 bugfix on 0.2.3.11-alpha.
5638 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
5639 supported, and always fails. Some compilers warn about the
5640 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
5643 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
5644 - Don't link or search for pthreads when building for Windows, even
5645 if we are using build environment (like mingw) that provides a
5646 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
5648 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
5649 - Skip a pair of unreliable key generation tests on Windows, until
5650 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
5651 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
5653 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
5654 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
5655 - Pass the module flags to distcheck configure, and log the flags
5656 before running configure. (Backported to 0.2.9 and later as a
5657 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
5659 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
5660 - When a Travis build fails, and showing a log fails, keep trying to
5661 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
5662 - When we use echo in Travis, don't pass a --flag as the first
5663 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
5665 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
5666 - When voting for recommended versions, make sure that all of the
5667 versions are well-formed and parsable. Fixes bug 26485; bugfix
5670 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
5671 - Fix a bug in out sandboxing rules for the openat() syscall.
5672 Previously, no openat() call would be permitted, which would break
5673 filesystem operations on recent glibc versions. Fixes bug 25440;
5674 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
5676 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
5677 - Improve the log message when connection initiators fail to
5678 authenticate direct connections to relays. Fixes bug 26927; bugfix
5681 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
5682 - Fix bug that causes services to not ever rotate their descriptors
5683 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
5686 o Minor bugfixes (onion services, backport from 0.3.4.8):
5687 - Silence a spurious compiler warning in
5688 rend_client_send_introduction(). Fixes bug 27463; bugfix
5691 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
5692 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
5694 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
5695 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
5696 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
5697 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
5699 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
5700 - Log a protocol warning when single onion services or Tor2web clients
5701 fail to authenticate direct connections to relays.
5702 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
5704 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
5705 - Disable core dumps in test_bt.sh, to avoid failures in "make
5706 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
5708 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
5709 - When running make test-network-all, use the mixed+hs-v2 network.
5710 (A previous fix to chutney removed v3 onion services from the
5711 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
5712 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
5713 - Before running make test-network-all, delete old logs and test
5714 result files, to avoid spurious failures. Fixes bug 27295; bugfix
5717 o Minor bugfixes (testing, openssl compatibility):
5718 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
5719 internals. Previously, it relied on unsupported OpenSSL behavior in
5720 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
5721 bugfix on 0.2.5.1-alpha.
5723 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
5724 - Our "tortls/cert_matches_key" unit test no longer relies on
5725 OpenSSL internals. Previously, it relied on unsupported OpenSSL
5726 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
5727 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
5729 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
5730 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
5731 27185; bugfix on 0.2.2.2-alpha.
5734 Changes in version 0.3.3.10 - 2018-09-10
5735 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
5737 o Minor features (bug workaround, backport from 0.3.4.7-rc):
5738 - Compile correctly on systems that provide the C11 stdatomic.h
5739 header, but where C11 atomic functions don't actually compile.
5740 Closes ticket 26779; workaround for Debian issue 903709.
5742 o Minor features (compatibility, backport from 0.3.4.8):
5743 - Tell OpenSSL to maintain backward compatibility with previous
5744 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
5745 ciphers are disabled by default. Closes ticket 27344.
5747 o Minor features (continuous integration, backport from 0.3.4.7-rc):
5748 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
5749 - Enable macOS builds in our Travis CI configuration. Closes
5751 - Install libcap-dev and libseccomp2-dev so these optional
5752 dependencies get tested on Travis CI. Closes ticket 26560.
5753 - Run asciidoc during Travis CI. Implements ticket 27087.
5754 - Use ccache in our Travis CI configuration. Closes ticket 26952.
5756 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
5757 - Use cargo cache in our Travis CI configuration. Closes
5760 o Minor features (controller, backport from 0.3.4.6-rc):
5761 - The control port now exposes the list of HTTPTunnelPorts and
5762 ExtOrPorts via GETINFO net/listeners/httptunnel and
5763 net/listeners/extor respectively. Closes ticket 26647.
5765 o Minor features (directory authorities, backport from 0.3.4.7-rc):
5766 - Authorities no longer vote to make the subprotocol version
5767 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
5768 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
5770 o Minor features (geoip):
5771 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
5772 Country database. Closes ticket 27089.
5774 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
5775 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
5776 tell the compiler not to include the system malloc implementation.
5777 Fixes bug 20424; bugfix on 0.2.0.20-rc.
5778 - Don't try to use a pragma to temporarily disable the
5779 -Wunused-const-variable warning if the compiler doesn't support
5780 it. Fixes bug 26785; bugfix on 0.3.2.11.
5782 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
5783 - Silence a spurious compiler warning on the GetAdaptersAddresses
5784 function pointer cast. This issue is already fixed by 26481 in
5785 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
5786 bugfix on 0.2.3.11-alpha.
5787 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
5788 supported, and always fails. Some compilers warn about the
5789 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
5792 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
5793 - Don't link or search for pthreads when building for Windows, even
5794 if we are using build environment (like mingw) that provides a
5795 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
5797 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
5798 - Skip a pair of unreliable key generation tests on Windows, until
5799 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
5800 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
5802 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
5803 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
5804 - Pass the module flags to distcheck configure, and log the flags
5805 before running configure. (Backported to 0.2.9 and later as a
5806 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
5808 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
5809 - When a Travis build fails, and showing a log fails, keep trying to
5810 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
5811 - When we use echo in Travis, don't pass a --flag as the first
5812 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
5814 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
5815 - When voting for recommended versions, make sure that all of the
5816 versions are well-formed and parsable. Fixes bug 26485; bugfix
5819 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
5820 - Always call tor_free_all() when leaving tor_run_main(). When we
5821 did not, restarting tor in-process would cause an assertion
5822 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
5824 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
5825 - Fix a bug in our sandboxing rules for the openat() syscall.
5826 Previously, no openat() call would be permitted, which would break
5827 filesystem operations on recent glibc versions. Fixes bug 25440;
5828 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
5830 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
5831 - Improve the log message when connection initiators fail to
5832 authenticate direct connections to relays. Fixes bug 26927; bugfix
5835 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
5836 - Fix bug that causes services to not ever rotate their descriptors
5837 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
5840 o Minor bugfixes (onion services, backport from 0.3.4.8):
5841 - Silence a spurious compiler warning in
5842 rend_client_send_introduction(). Fixes bug 27463; bugfix
5845 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
5846 - Work around two different bugs in the OS X 10.10 and later SDKs
5847 that would prevent us from successfully targeting earlier versions
5848 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
5850 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
5851 - Fix compilation of the unit tests on GNU/Hurd, which does not
5852 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
5855 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
5856 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
5858 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
5859 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
5860 - Protover parsing was accepting the presence of whitespace in
5861 version strings, which the C implementation would choke on, e.g.
5862 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
5863 - Protover parsing was ignoring a 2nd hyphen and everything after
5864 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
5866 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
5867 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
5868 - cd to ${abs_top_builddir}/src/rust before running cargo in
5869 src/test/test_rust.sh. This makes the working directory consistent
5870 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
5872 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
5873 - Log a protocol warning when single onion services or Tor2web clients
5874 fail to authenticate direct connections to relays.
5875 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
5877 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
5878 - Disable core dumps in test_bt.sh, to avoid failures in "make
5879 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
5881 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
5882 - When running make test-network-all, use the mixed+hs-v2 network.
5883 (A previous fix to chutney removed v3 onion services from the
5884 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
5885 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
5886 - Before running make test-network-all, delete old logs and test
5887 result files, to avoid spurious failures. Fixes bug 27295; bugfix
5890 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
5891 - Our "tortls/cert_matches_key" unit test no longer relies on
5892 OpenSSL internals. Previously, it relied on unsupported OpenSSL
5893 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
5894 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
5896 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
5897 - Stop sending ed25519 link specifiers in v3 onion service introduce
5898 cells and descriptors, when the rendezvous or introduction point
5899 doesn't support ed25519 link authentication. Fixes bug 26627;
5900 bugfix on 0.3.2.4-alpha.
5902 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
5903 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
5904 27185; bugfix on 0.2.2.2-alpha.
5907 Changes in version 0.3.4.8 - 2018-09-10
5908 Tor 0.3.4.8 is the first stable release in its series; it includes
5909 compilation and portability fixes.
5911 The Tor 0.3.4 series includes improvements for running Tor in
5912 low-power and embedded environments, which should help performance in
5913 general. We've begun work on better modularity, and included preliminary
5914 changes on the directory authority side to accommodate a new bandwidth
5915 measurement system. We've also integrated more continuous-integration
5916 systems into our development process, and made corresponding changes to
5917 Tor's testing infrastructure. Finally, we've continued to refine
5918 our anti-denial-of-service code.
5920 Below are the changes since 0.3.3.9. For a list of only the changes
5921 since 0.3.4.7-rc, see the ChangeLog file.
5923 o New system requirements:
5924 - Tor no longer tries to support old operating systems without
5925 mmap() or some local equivalent. Apparently, compilation on such
5926 systems has been broken for some time, without anybody noticing or
5927 complaining. Closes ticket 25398.
5929 o Major features (directory authority, modularization):
5930 - The directory authority subsystem has been modularized. The code
5931 is now located in src/or/dirauth/, and is compiled in by default.
5932 To disable the module, the configure option
5933 --disable-module-dirauth has been added. This module may be
5934 disabled by default in some future release. Closes ticket 25610.
5936 o Major features (main loop, CPU usage):
5937 - When Tor is disabled (via DisableNetwork or via hibernation), it
5938 no longer needs to run any per-second events. This change should
5939 make it easier for mobile applications to disable Tor while the
5940 device is sleeping, or Tor is not running. Closes ticket 26063.
5941 - Tor no longer enables all of its periodic events by default.
5942 Previously, Tor would enable all possible main loop events,
5943 regardless of whether it needed them. Furthermore, many of these
5944 events are now disabled when Tor is hibernating or DisableNetwork
5945 is set. This is a big step towards reducing client CPU usage by
5946 reducing the amount of wake-ups the daemon does. Closes tickets
5948 - The bandwidth-limitation logic has been refactored so that
5949 bandwidth calculations are performed on-demand, rather than every
5950 TokenBucketRefillInterval milliseconds. This change should improve
5951 the granularity of our bandwidth calculations, and limit the
5952 number of times that the Tor process needs to wake up when it is
5953 idle. Closes ticket 25373.
5954 - Move responsibility for many operations from a once-per-second
5955 callback to a callback that is only scheduled as needed. Moving
5956 this functionality has allowed us to disable the callback when
5957 Tor's network is disabled. Once enough items are removed from our
5958 once-per-second callback, we can eliminate it entirely to conserve
5959 CPU when idle. The functionality removed includes: closing
5960 connections, circuits, and channels (ticket 25932); consensus
5961 voting (25937); flushing log callbacks (25951); honoring delayed
5962 SIGNEWNYM requests (25949); rescanning the consensus cache
5963 (25931); saving the state file to disk (25948); warning relay
5964 operators about unreachable ports (25952); and keeping track of
5965 Tor's uptime (26009).
5967 o Minor features (accounting):
5968 - When Tor becomes dormant, it now uses a scheduled event to wake up
5969 at the right time. Previously, we would use the per-second timer
5970 to check whether to wake up, but we no longer have any per-second
5971 timers enabled when the network is disabled. Closes ticket 26064.
5973 o Minor features (bug workaround):
5974 - Compile correctly on systems that provide the C11 stdatomic.h
5975 header, but where C11 atomic functions don't actually compile.
5976 Closes ticket 26779; workaround for Debian issue 903709.
5978 o Minor features (code quality):
5979 - Add optional spell-checking for the Tor codebase, using the
5980 "misspell" program. To use this feature, run "make check-typos".
5981 Closes ticket 25024.
5983 o Minor features (compatibility):
5984 - Tell OpenSSL to maintain backward compatibility with previous
5985 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
5986 ciphers are disabled by default. Closes ticket 27344.
5987 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
5988 the no-deprecated option, and builds correctly with them. Closes
5989 tickets 19429, 19981, and 25353.
5991 o Minor features (compilation):
5992 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
5993 tell the compiler not to include the system malloc implementation.
5994 Fixes bug 20424; bugfix on 0.2.0.20-rc.
5995 - Don't try to use a pragma to temporarily disable the
5996 -Wunused-const-variable warning if the compiler doesn't support
5997 it. Fixes bug 26785; bugfix on 0.3.2.11.
5998 - When building Tor, prefer to use Python 3 over Python 2, and more
5999 recent (contemplated) versions over older ones. Closes
6002 o Minor features (compression, zstd):
6003 - When running with zstd, Tor now considers using advanced functions
6004 that the zstd maintainers have labeled as potentially unstable. To
6005 prevent breakage, Tor will only use this functionality when the
6006 runtime version of the zstd library matches the version with which
6007 Tor was compiled. Closes ticket 25162.
6009 o Minor features (configuration):
6010 - The "DownloadSchedule" options have been renamed to end with
6011 "DownloadInitialDelay". The old names are still allowed, but will
6012 produce a warning. Comma-separated lists are still permitted for
6013 these options, but all values after the first are ignored (as they
6014 have been since 0.2.9). Closes ticket 23354.
6016 o Minor features (continuous integration):
6017 - Log the compiler path and version during Appveyor builds.
6018 Implements ticket 27449.
6019 - Show config.log and test-suite.log after failed Appveyor builds.
6020 Also upload the zipped full logs as a build artifact. Implements
6022 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
6023 - Enable macOS builds in our Travis CI configuration. Closes
6025 - Install libcap-dev and libseccomp2-dev so these optional
6026 dependencies get tested on Travis CI. Closes ticket 26560.
6027 - Only post Appveyor IRC notifications when the build fails.
6028 Implements ticket 27275.
6029 - Run asciidoc during Travis CI. Implements ticket 27087.
6030 - Use ccache in our Travis CI configuration. Closes ticket 26952.
6031 - Add the necessary configuration files for continuous integration
6032 testing on Windows, via the Appveyor platform. Closes ticket
6033 25549. Patches from Marcin Cieślak and Isis Lovecruft.
6035 o Minor features (continuous integration, rust):
6036 - Use cargo cache in our Travis CI configuration. Closes
6039 o Minor features (control port):
6040 - Introduce GETINFO "current-time/{local,utc}" to return the local
6041 and UTC times respectively in ISO format. This helps a controller
6042 like Tor Browser detect a time-related error. Closes ticket 25511.
6043 Patch by Neel Chauhan.
6044 - Introduce new fields to the CIRC_BW event. There are two new
6045 fields in each of the read and written directions. The DELIVERED
6046 fields report the total valid data on the circuit, as measured by
6047 the payload sizes of verified and error-checked relay command
6048 cells. The OVERHEAD fields report the total unused bytes in each
6049 of these cells. Closes ticket 25903.
6051 o Minor features (controller):
6052 - The control port now exposes the list of HTTPTunnelPorts and
6053 ExtOrPorts via GETINFO net/listeners/httptunnel and
6054 net/listeners/extor respectively. Closes ticket 26647.
6056 o Minor features (directory authorities):
6057 - Stop warning about incomplete bw lines before the first complete
6058 bw line has been found, so that additional header lines can be
6059 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
6060 - Authorities no longer vote to make the subprotocol version
6061 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
6062 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
6064 o Minor features (directory authority):
6065 - Directory authorities now open their key-pinning files as O_SYNC,
6066 to limit their chances of accidentally writing partial lines.
6067 Closes ticket 23909.
6069 o Minor features (directory authority, forward compatibility):
6070 - Make the lines of the measured bandwidth file able to contain
6071 their entries in any order. Previously, the node_id entry needed
6072 to come first. Closes ticket 26004.
6074 o Minor features (entry guards):
6075 - Introduce a new torrc option NumPrimaryGuards for controlling the
6076 number of primary guards. Closes ticket 25843.
6078 o Minor features (geoip):
6079 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
6080 Country database. Closes ticket 27089.
6082 o Minor features (performance):
6083 - Avoid a needless call to malloc() when processing an incoming
6084 relay cell. Closes ticket 24914.
6085 - Make our timing-wheel code run a tiny bit faster on 32-bit
6086 platforms, by preferring 32-bit math to 64-bit. Closes
6088 - Avoid a needless malloc()/free() pair every time we handle an ntor
6089 handshake. Closes ticket 25150.
6091 o Minor features (Rust, portability):
6092 - Rust cross-compilation is now supported. Closes ticket 25895.
6094 o Minor features (testing):
6095 - Add a unit test for voting_schedule_get_start_of_next_interval().
6096 Closes ticket 26014, and helps make unit test coverage
6098 - A new unittests module specifically for testing the functions in
6099 the (new-ish) bridges.c module has been created with new
6100 unittests, raising the code coverage percentages. Closes 25425.
6101 - We now have improved testing for addressmap_get_virtual_address()
6102 function. This should improve our test coverage, and make our test
6103 coverage more deterministic. Closes ticket 25993.
6105 o Minor features (timekeeping, circuit scheduling):
6106 - When keeping track of how busy each circuit have been recently on
6107 a given connection, use coarse-grained monotonic timers rather
6108 than gettimeofday(). This change should marginally increase
6109 accuracy and performance. Implements part of ticket 25927.
6111 o Minor features (unit tests):
6112 - Test complete bandwidth measurements files, and test that
6113 incomplete bandwidth lines only give warnings when the end of the
6114 header has not been detected. Fixes bug 25947; bugfix
6117 o Minor bugfixes (bandwidth management):
6118 - Consider ourselves "low on write bandwidth" if we have exhausted
6119 our write bandwidth some time in the last second. This was the
6120 documented behavior before, but the actual behavior was to change
6121 this value every TokenBucketRefillInterval. Fixes bug 25828;
6122 bugfix on 0.2.3.5-alpha.
6124 o Minor bugfixes (C correctness):
6125 - Add a missing lock acquisition in the shutdown code of the control
6126 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
6127 Coverity; this is CID 1433643.
6129 o Minor bugfixes (code style):
6130 - Fixed multiple includes of transports.h in src/or/connection.c
6131 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
6132 - Remove the unused variable n_possible from the function
6133 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
6135 o Minor bugfixes (compilation):
6136 - Silence a spurious compiler warning on the GetAdaptersAddresses
6137 function pointer cast. This issue is already fixed by 26481 in
6138 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
6139 bugfix on 0.2.3.11-alpha.
6140 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
6141 supported, and always fails. Some compilers warn about the
6142 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
6144 - Fix a compilation warning on some versions of GCC when building
6145 code that calls routerinfo_get_my_routerinfo() twice, assuming
6146 that the second call will succeed if the first one did. Fixes bug
6147 26269; bugfix on 0.2.8.2-alpha.
6148 - Refrain from compiling unit testing related object files when
6149 --disable-unittests is set to configure script. Fixes bug 24891;
6150 bugfix on 0.2.5.1-alpha.
6151 - The --enable-fatal-warnings flag now affects Rust code as well.
6152 Closes ticket 26245.
6153 - Avoid a compiler warning when casting the return value of
6154 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
6155 26283; bugfix on 0.2.4.10-alpha.
6157 o Minor bugfixes (compilation, windows):
6158 - Don't link or search for pthreads when building for Windows, even
6159 if we are using build environment (like mingw) that provides a
6160 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
6162 o Minor bugfixes (continuous integration):
6163 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
6164 - Skip a pair of unreliable key generation tests on Windows, until
6165 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
6166 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
6168 o Minor bugfixes (control port):
6169 - Respond with more human-readable error messages to GETINFO exit-
6170 policy/* requests. Also, let controller know if an error is
6171 transient (response code 551) or not (response code 552). Fixes
6172 bug 25852; bugfix on 0.2.8.1-alpha.
6173 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
6174 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
6175 on 0.3.3.1-alpha. Patch by "akwizgran".
6176 - Make CIRC_BW event reflect the total of all data sent on a
6177 circuit, including padding and dropped cells. Also fix a mis-
6178 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
6179 bugfix on 0.2.5.2-alpha.
6181 o Minor bugfixes (correctness, flow control):
6182 - Upon receiving a stream-level SENDME cell, verify that our window
6183 has not grown too large. Fixes bug 26214; bugfix on svn
6186 o Minor bugfixes (directory authority):
6187 - When voting for recommended versions, make sure that all of the
6188 versions are well-formed and parsable. Fixes bug 26485; bugfix
6191 o Minor bugfixes (directory client):
6192 - When unverified-consensus is verified, rename it to cached-
6193 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
6194 - Fixed launching a certificate fetch always during the scheduled
6195 periodic consensus fetch by fetching only in those cases when
6196 consensus are waiting for certs. Fixes bug 24740; bugfix
6199 o Minor bugfixes (error reporting):
6200 - Improve tolerance for directory authorities with skewed clocks.
6201 Previously, an authority with a clock more than 60 seconds ahead
6202 could cause a client with a correct clock to warn that the
6203 client's clock was behind. Now the clocks of a majority of
6204 directory authorities have to be ahead of the client before this
6205 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
6207 o Minor bugfixes (in-process restart):
6208 - Always call tor_free_all() when leaving tor_run_main(). When we
6209 did not, restarting tor in-process would cause an assertion
6210 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
6212 o Minor bugfixes (Linux seccomp2 sandbox):
6213 - Fix a bug in our sandboxing rules for the openat() syscall.
6214 Previously, no openat() call would be permitted, which would break
6215 filesystem operations on recent glibc versions. Fixes bug 25440;
6216 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
6218 o Minor bugfixes (logging):
6219 - Improve the log message when connection initiators fail to
6220 authenticate direct connections to relays. Fixes bug 26927; bugfix
6223 o Minor bugfixes (onion services):
6224 - Silence a spurious compiler warning in
6225 rend_client_send_introduction(). Fixes bug 27463; bugfix
6227 - Fix bug that causes services to not ever rotate their descriptors
6228 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
6230 - Recompute some consensus information after detecting a clock jump,
6231 or after transitioning from a non-live consensus to a live
6232 consensus. We do this to avoid having an outdated state, and
6233 miscalculating the index for next-generation onion services. Fixes
6234 bug 24977; bugfix on 0.3.2.1-alpha.
6236 o Minor bugfixes (portability):
6237 - Fix compilation of the unit tests on GNU/Hurd, which does not
6238 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
6240 - Work around two different bugs in the OS X 10.10 and later SDKs
6241 that would prevent us from successfully targeting earlier versions
6242 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
6243 - Do not align mmap length, as it is not required by POSIX, and the
6244 getpagesize function is deprecated. Fixes bug 25399; bugfix
6247 o Minor bugfixes (portability, FreeBSD):
6248 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
6249 does not stringify on FreeBSD, so we switch to tor_asprintf().
6250 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
6252 o Minor bugfixes (relay statistics):
6253 - When a relay is collecting internal statistics about how many
6254 create cell requests it has seen of each type, accurately count
6255 the requests from relays that temporarily fall out of the
6256 consensus. (To be extra conservative, we were already ignoring
6257 requests from clients in our counts, and we continue ignoring them
6258 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
6260 o Minor bugfixes (rust):
6261 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
6263 - Protover parsing was accepting the presence of whitespace in
6264 version strings, which the C implementation would choke on, e.g.
6265 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
6266 - Protover parsing was ignoring a 2nd hyphen and everything after
6267 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
6269 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
6270 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
6271 - cd to ${abs_top_builddir}/src/rust before running cargo in
6272 src/test/test_rust.sh. This makes the working directory consistent
6273 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
6275 o Minor bugfixes (single onion services, Tor2web):
6276 - Log a protocol warning when single onion services or Tor2web
6277 clients fail to authenticate direct connections to relays. Fixes
6278 bug 26924; bugfix on 0.2.9.1-alpha.
6280 o Minor bugfixes (test coverage tools):
6281 - Update our "cov-diff" script to handle output from the latest
6282 version of gcov, and to remove extraneous timestamp information
6283 from its output. Fixes bugs 26101 and 26102; bugfix
6286 o Minor bugfixes (testing):
6287 - Disable core dumps in test_bt.sh, to avoid failures in "make
6288 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
6289 - When testing workqueue event-cancellation, make sure that we
6290 actually cancel an event, and that cancel each event with equal
6291 probability. (It was previously possible, though extremely
6292 unlikely, for our event-canceling test not to cancel any events.)
6293 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
6294 - Repeat part of the test in test_client_pick_intro() a number of
6295 times, to give it consistent coverage. Fixes bug 25996; bugfix
6297 - Remove randomness from the hs_common/responsible_hsdirs test, so
6298 that it always takes the same path through the function it tests.
6299 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
6300 - Change the behavior of the "channel/outbound" test so that it
6301 never causes a 10-second rollover for the EWMA circuitmux code.
6302 Previously, this behavior would happen randomly, and result in
6303 fluctuating test coverage. Fixes bug 25994; bugfix
6305 - Use X509_new() to allocate certificates that will be freed later
6306 with X509_free(). Previously, some parts of the unit tests had
6307 used tor_malloc_zero(), which is incorrect, and which caused test
6308 failures on Windows when they were built with extra hardening.
6309 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
6311 - While running the circuit_timeout test, fix the PRNG to a
6312 deterministic AES stream, so that the test coverage from this test
6313 will itself be deterministic. Fixes bug 25995; bugfix
6316 o Minor bugfixes (testing, bootstrap):
6317 - When calculating bootstrap progress, check exit policies and the
6318 exit flag. Previously, Tor would only check the exit flag, which
6319 caused race conditions in small and fast networks like chutney.
6320 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
6322 o Minor bugfixes (testing, chutney):
6323 - When running make test-network-all, use the mixed+hs-v2 network.
6324 (A previous fix to chutney removed v3 onion services from the
6325 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
6326 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
6327 - Before running make test-network-all, delete old logs and test
6328 result files, to avoid spurious failures. Fixes bug 27295; bugfix
6331 o Minor bugfixes (testing, openssl compatibility):
6332 - Our "tortls/cert_matches_key" unit test no longer relies on
6333 OpenSSL internals. Previously, it relied on unsupported OpenSSL
6334 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
6335 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
6337 o Minor bugfixes (v3 onion services):
6338 - Stop sending ed25519 link specifiers in v3 onion service introduce
6339 cells and descriptors, when the rendezvous or introduction point
6340 doesn't support ed25519 link authentication. Fixes bug 26627;
6341 bugfix on 0.3.2.4-alpha.
6343 o Minor bugfixes (vanguards):
6344 - Allow the last hop in a vanguard circuit to be the same as our
6345 first, to prevent the adversary from influencing guard node choice
6346 by choice of last hop. Also prevent the creation of A - B - A
6347 paths, or A - A paths, which are forbidden by relays. Fixes bug
6348 25870; bugfix on 0.3.3.1-alpha.
6350 o Minor bugfixes (Windows, compilation):
6351 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
6352 27185; bugfix on 0.2.2.2-alpha.
6354 o Code simplification and refactoring:
6355 - Remove duplicate code in parse_{c,s}method_line and bootstrap
6356 their functionalities into a single function. Fixes bug 6236;
6357 bugfix on 0.2.3.6-alpha.
6358 - We remove the PortForwarding and PortForwardingHelper options,
6359 related functions, and the port_forwarding tests. These options
6360 were used by the now-deprecated Vidalia to help ordinary users
6361 become Tor relays or bridges. Closes ticket 25409. Patch by
6363 - In order to make the OR and dir checking function in router.c less
6364 confusing we renamed some functions and
6365 consider_testing_reachability() has been split into
6366 router_should_check_reachability() and
6367 router_do_reachability_checks(). Also we improved the documentation
6368 in some functions. Closes ticket 18918.
6369 - Initial work to isolate Libevent usage to a handful of modules in
6370 our codebase, to simplify our call structure, and so that we can
6371 more easily change event loops in the future if needed. Closes
6373 - Introduce a function to call getsockname() and return tor_addr_t,
6374 to save a little complexity throughout the codebase. Closes
6376 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
6377 as hsdir_index is always present. Also, we move hsdir_index_t into
6378 or.h. Closes ticket 23094. Patch by Neel Chauhan.
6379 - Merge functions used for describing nodes and suppress the
6380 functions that do not allocate memory for the output buffer
6381 string. NODE_DESC_BUF_LEN constant and format_node_description()
6382 function cannot be used externally from router.c module anymore.
6383 Closes ticket 25432. Patch by valentecaio.
6384 - Our main loop has been simplified so that all important operations
6385 happen inside events. Previously, some operations had to happen
6386 outside the event loop, to prevent infinite sequences of event
6387 activations. Closes ticket 25374.
6388 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
6389 it in register_intro_circ() and service_intro_point_new(). This
6390 prevents the digest from being re-calculated each time. Closes
6391 ticket 23107. Patch by Neel Chauhan.
6392 - Refactor token-bucket implementations to use a common backend.
6393 Closes ticket 25766.
6394 - Remove extern declaration of stats_n_seconds_working variable from
6395 main, protecting its accesses with get_uptime() and reset_uptime()
6396 functions. Closes ticket 25081, patch by “valentecaio”.
6397 - Remove our previous logic for "cached gettimeofday()" -- our
6398 coarse monotonic timers are fast enough for this purpose, and far
6399 less error-prone. Implements part of ticket 25927.
6400 - Remove the return value for fascist_firewall_choose_address_base(),
6401 and sister functions such as fascist_firewall_choose_address_node()
6402 and fascist_firewall_choose_address_rs(). Also, while we're here,
6403 initialize the ap argument as leaving it uninitialized can pose a
6404 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
6405 - Rename two fields of connection_t struct. timestamp_lastwritten is
6406 renamed to timestamp_last_write_allowed and timestamp_lastread is
6407 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
6409 - Since Tor requires C99, remove our old workaround code for libc
6410 implementations where free(NULL) doesn't work. Closes ticket 24484.
6411 - Use our standard rate-limiting code to deal with excessive
6412 libevent failures, rather than the hand-rolled logic we had
6413 before. Closes ticket 26016.
6414 - We remove the return value of node_get_prim_orport() and
6415 node_get_prim_dirport(), and introduce node_get_prim_orport() in
6416 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
6417 check for a null address. Closes ticket 23873. Patch by
6419 - We switch to should_record_bridge_info() in
6420 geoip_note_client_seen() and options_need_geoip_info() instead of
6421 accessing the configuration values directly. Fixes bug 25290;
6422 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
6424 o Deprecated features:
6425 - As we are not recommending 0.2.5 anymore, we require relays that
6426 once had an ed25519 key associated with their RSA key to always
6427 have that key, instead of allowing them to drop back to a version
6428 that didn't support ed25519. This means they need to use a new RSA
6429 key if they want to downgrade to an older version of tor without
6430 ed25519. Closes ticket 20522.
6433 - Directory authorities will no longer support voting according to
6434 any consensus method before consensus method 25. This keeps
6435 authorities compatible with all authorities running 0.2.9.8 and
6436 later, and does not break any clients or relays. Implements ticket
6437 24378 and proposal 290.
6438 - The PortForwarding and PortForwardingHelper features have been
6439 removed. The reasoning is, given that implementations of NAT
6440 traversal protocols within common consumer grade routers are
6441 frequently buggy, and that the target audience for a NAT punching
6442 feature is a perhaps less-technically-inclined relay operator,
6443 when the helper fails to setup traversal the problems are usually
6444 deep, ugly, and very router specific, making them horrendously
6445 impossible for technical support to reliable assist with, and thus
6446 resulting in frustration all around. Unfortunately, relay
6447 operators who would like to run relays behind NATs will need to
6448 become more familiar with the port forwarding configurations on
6449 their local router. Closes 25409.
6450 - The TestingEnableTbEmptyEvent option has been removed. It was used
6451 in testing simulations to measure how often connection buckets
6452 were emptied, in order to improve our scheduling, but it has not
6453 been actively used in years. Closes ticket 25760.
6454 - The old "round-robin" circuit multiplexer (circuitmux)
6455 implementation has been removed, along with a fairly large set of
6456 code that existed to support it. It has not been the default
6457 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
6458 but it still required an unreasonable amount of memory and CPU.
6459 Closes ticket 25268.
6462 Changes in version 0.3.3.9 - 2018-07-13
6463 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
6464 bridge relays should upgrade.
6466 o Directory authority changes:
6467 - The "Bifroest" bridge authority has been retired; the new bridge
6468 authority is "Serge", and it is operated by George from the
6469 TorBSD project. Closes ticket 26771.
6472 Changes in version 0.3.2.11 - 2018-07-13
6473 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
6474 bridge relays should upgrade. We also take this opportunity to backport
6477 o Directory authority changes:
6478 - The "Bifroest" bridge authority has been retired; the new bridge
6479 authority is "Serge", and it is operated by George from the
6480 TorBSD project. Closes ticket 26771.
6482 o Directory authority changes (backport from 0.3.3.7):
6483 - Add an IPv6 address for the "dannenberg" directory authority.
6484 Closes ticket 26343.
6486 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
6487 - When directory authorities read a zero-byte bandwidth file, they
6488 would previously log a warning with the contents of an
6489 uninitialised buffer. They now log a warning about the empty file
6490 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
6492 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
6493 - Correctly detect when onion services get disabled after HUP. Fixes
6494 bug 25761; bugfix on 0.3.2.1.
6496 o Minor features (sandbox, backport from 0.3.3.4-alpha):
6497 - Explicitly permit the poll() system call when the Linux
6498 seccomp2-based sandbox is enabled: apparently, some versions of
6499 libc use poll() when calling getpwnam(). Closes ticket 25313.
6501 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
6502 - Update the Travis CI configuration to use the stable Rust channel,
6503 now that we have decided to require that. Closes ticket 25714.
6505 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
6506 - Our .travis.yml configuration now includes support for testing the
6507 results of "make distcheck". (It's not uncommon for "make check"
6508 to pass but "make distcheck" to fail.) Closes ticket 25814.
6509 - Our Travis CI configuration now integrates with the Coveralls
6510 coverage analysis tool. Closes ticket 25818.
6512 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
6513 - Add several checks to detect whether Tor relays are uploading
6514 their descriptors without specifying why they regenerated them.
6515 Diagnostic for ticket 25686.
6517 o Minor features (compilation, backport from 0.3.4.4-rc):
6518 - When building Tor, prefer to use Python 3 over Python 2, and more
6519 recent (contemplated) versions over older ones. Closes
6522 o Minor features (geoip):
6523 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
6524 Country database. Closes ticket 26674.
6526 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
6527 - Upon receiving a malformed connected cell, stop processing the
6528 cell immediately. Previously we would mark the connection for
6529 close, but continue processing the cell as if the connection were
6530 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
6532 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
6533 - Allow the nanosleep() system call, which glibc uses to implement
6534 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
6536 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
6537 - When running the hs_ntor_ref.py test, make sure only to pass
6538 strings (rather than "bytes" objects) to the Python subprocess
6539 module. Python 3 on Windows seems to require this. Fixes bug
6540 26535; bugfix on 0.3.1.1-alpha.
6541 - When running the ntor_ref.py test, make sure only to pass strings
6542 (rather than "bytes" objects) to the Python subprocess module.
6543 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
6546 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
6547 - Work around a change in OpenSSL 1.1.1 where return values that
6548 would previously indicate "no password" now indicate an empty
6549 password. Without this workaround, Tor instances running with
6550 OpenSSL 1.1.1 would accept descriptors that other Tor instances
6551 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
6553 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
6554 - Document that the PerConnBW{Rate,Burst} options will fall back to
6555 their corresponding consensus parameters only if those parameters
6556 are set. Previously we had claimed that these values would always
6557 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
6559 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
6560 - Fix a compilation warning on some versions of GCC when building
6561 code that calls routerinfo_get_my_routerinfo() twice, assuming
6562 that the second call will succeed if the first one did. Fixes bug
6563 26269; bugfix on 0.2.8.2-alpha.
6565 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
6566 - Don't consider Tor running as a client if the ControlPort is open,
6567 but no actual client ports are open. Fixes bug 26062; bugfix
6570 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
6571 - Prevent a possible out-of-bounds smartlist read in
6572 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
6574 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
6575 - Fix a very unlikely (impossible, we believe) null pointer
6576 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
6577 Coverity; this is CID 1430932.
6579 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
6580 - Fix a memory leak when a v3 onion service is configured and gets a
6581 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
6582 - When parsing the descriptor signature, look for the token plus an
6583 extra white-space at the end. This is more correct but also will
6584 allow us to support new fields that might start with "signature".
6585 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
6587 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
6588 - Relays now correctly block attempts to re-extend to the previous
6589 relay by Ed25519 identity. Previously they would warn in this
6590 case, but not actually reject the attempt. Fixes bug 26158; bugfix
6593 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
6594 - Avoid a crash when running with DirPort set but ORPort turned off.
6595 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
6597 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
6598 - Silence unused-const-variable warnings in zstd.h with some GCC
6599 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
6601 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
6602 - Avoid intermittent test failures due to a test that had relied on
6603 onion service introduction point creation finishing within 5
6604 seconds of real clock time. Fixes bug 25450; bugfix
6607 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
6608 - Fix a C99 compliance issue in our configuration script that caused
6609 compilation issues when compiling Tor with certain versions of
6610 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
6612 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
6613 - Fix a number of small memory leaks identified by coverity. Fixes
6614 bug 26467; bugfix on numerous Tor versions.
6616 o Code simplification and refactoring (backport from 0.3.3.5-rc):
6617 - Move the list of default directory authorities to its own file.
6618 Closes ticket 24854. Patch by "beastr0".
6621 Changes in version 0.2.9.16 - 2018-07-13
6622 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
6623 bridge relays should upgrade. We also take this opportunity to backport
6626 o Directory authority changes:
6627 - The "Bifroest" bridge authority has been retired; the new bridge
6628 authority is "Serge", and it is operated by George from the
6629 TorBSD project. Closes ticket 26771.
6631 o Directory authority changes (backport from 0.3.3.7):
6632 - Add an IPv6 address for the "dannenberg" directory authority.
6633 Closes ticket 26343.
6635 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
6636 - When directory authorities read a zero-byte bandwidth file, they
6637 would previously log a warning with the contents of an
6638 uninitialised buffer. They now log a warning about the empty file
6639 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
6641 o Minor features (sandbox, backport from 0.3.3.4-alpha):
6642 - Explicitly permit the poll() system call when the Linux
6643 seccomp2-based sandbox is enabled: apparently, some versions of
6644 libc use poll() when calling getpwnam(). Closes ticket 25313.
6646 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
6647 - Our .travis.yml configuration now includes support for testing the
6648 results of "make distcheck". (It's not uncommon for "make check"
6649 to pass but "make distcheck" to fail.) Closes ticket 25814.
6650 - Our Travis CI configuration now integrates with the Coveralls
6651 coverage analysis tool. Closes ticket 25818.
6653 o Minor features (compilation, backport from 0.3.4.4-rc):
6654 - When building Tor, prefer to use Python 3 over Python 2, and more
6655 recent (contemplated) versions over older ones. Closes
6658 o Minor features (geoip):
6659 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
6660 Country database. Closes ticket 26674.
6662 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
6663 - Upon receiving a malformed connected cell, stop processing the
6664 cell immediately. Previously we would mark the connection for
6665 close, but continue processing the cell as if the connection were
6666 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
6668 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
6669 - Allow the nanosleep() system call, which glibc uses to implement
6670 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
6672 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
6673 - When running the ntor_ref.py test, make sure only to pass strings
6674 (rather than "bytes" objects) to the Python subprocess module.
6675 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
6678 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
6679 - Work around a change in OpenSSL 1.1.1 where return values that
6680 would previously indicate "no password" now indicate an empty
6681 password. Without this workaround, Tor instances running with
6682 OpenSSL 1.1.1 would accept descriptors that other Tor instances
6683 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
6685 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
6686 - Fix a compilation warning on some versions of GCC when building
6687 code that calls routerinfo_get_my_routerinfo() twice, assuming
6688 that the second call will succeed if the first one did. Fixes bug
6689 26269; bugfix on 0.2.8.2-alpha.
6691 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
6692 - Don't consider Tor running as a client if the ControlPort is open,
6693 but no actual client ports are open. Fixes bug 26062; bugfix
6696 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
6697 - Prevent a possible out-of-bounds smartlist read in
6698 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
6700 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
6701 - Fix a very unlikely (impossible, we believe) null pointer
6702 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
6703 Coverity; this is CID 1430932.
6705 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
6706 - Fix a number of small memory leaks identified by coverity. Fixes
6707 bug 26467; bugfix on numerous Tor versions.
6709 o Code simplification and refactoring (backport from 0.3.3.5-rc):
6710 - Move the list of default directory authorities to its own file.
6711 Closes ticket 24854. Patch by "beastr0".
6714 Changes in version 0.3.3.8 - 2018-07-09
6715 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
6716 fixes for a memory leak affecting directory authorities.
6718 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
6719 - Stop leaking memory on directory authorities when planning to
6720 vote. This bug was crashing authorities by exhausting their
6721 memory. Fixes bug 26435; bugfix on 0.3.3.6.
6723 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
6724 - Make sure that failing tests in Rust will actually cause the build
6725 to fail: previously, they were ignored. Fixes bug 26258; bugfix
6728 o Minor features (compilation, backport from 0.3.4.4-rc):
6729 - When building Tor, prefer to use Python 3 over Python 2, and more
6730 recent (contemplated) versions over older ones. Closes
6733 o Minor features (geoip):
6734 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
6735 Country database. Closes ticket 26674.
6737 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
6738 - Add several checks to detect whether Tor relays are uploading
6739 their descriptors without specifying why they regenerated them.
6740 Diagnostic for ticket 25686.
6742 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
6743 - Don't count path selection failures as circuit build failures.
6744 This change should eliminate cases where Tor blames its guard or
6745 the network for situations like insufficient microdescriptors
6746 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
6749 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
6750 - Fix a compilation warning on some versions of GCC when building
6751 code that calls routerinfo_get_my_routerinfo() twice, assuming
6752 that the second call will succeed if the first one did. Fixes bug
6753 26269; bugfix on 0.2.8.2-alpha.
6755 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
6756 - Handle the HSADDRESS= argument to the HSPOST command properly.
6757 (Previously, this argument was misparsed and thus ignored.) Fixes
6758 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
6760 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
6761 - Fix a number of small memory leaks identified by coverity. Fixes
6762 bug 26467; bugfix on numerous Tor versions.
6764 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
6765 - Relays now correctly block attempts to re-extend to the previous
6766 relay by Ed25519 identity. Previously they would warn in this
6767 case, but not actually reject the attempt. Fixes bug 26158; bugfix
6770 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
6771 - When shutting down, Tor now clears all the flags in the control.c
6772 module. This should prevent a bug where authentication cookies are
6773 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
6775 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
6776 - When running the hs_ntor_ref.py test, make sure only to pass
6777 strings (rather than "bytes" objects) to the Python subprocess
6778 module. Python 3 on Windows seems to require this. Fixes bug
6779 26535; bugfix on 0.3.1.1-alpha.
6780 - When running the ntor_ref.py test, make sure only to pass strings
6781 (rather than "bytes" objects) to the Python subprocess module.
6782 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
6786 Changes in version 0.3.3.7 - 2018-06-12
6787 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
6788 fixes for bugs affecting compatibility and stability.
6790 o Directory authority changes:
6791 - Add an IPv6 address for the "dannenberg" directory authority.
6792 Closes ticket 26343.
6794 o Minor features (geoip):
6795 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
6796 Country database. Closes ticket 26351.
6798 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
6799 - Work around a change in OpenSSL 1.1.1 where return values that
6800 would previously indicate "no password" now indicate an empty
6801 password. Without this workaround, Tor instances running with
6802 OpenSSL 1.1.1 would accept descriptors that other Tor instances
6803 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
6805 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
6806 - Silence unused-const-variable warnings in zstd.h with some GCC
6807 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
6809 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
6810 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
6811 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
6812 miscounting the total number of circuits for these field values.)
6813 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
6815 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
6816 - Prevent a possible out-of-bounds smartlist read in
6817 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
6819 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
6820 - Only select relays when they have the descriptors we prefer to use
6821 for them. This change fixes a bug where we could select a relay
6822 because it had _some_ descriptor, but reject it later with a
6823 nonfatal assertion error because it didn't have the exact one we
6824 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
6827 Changes in version 0.3.3.6 - 2018-05-22
6828 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
6829 backports several important fixes from the 0.3.4.1-alpha.
6831 The Tor 0.3.3 series includes controller support and other
6832 improvements for v3 onion services, official support for embedding Tor
6833 within other applications, and our first non-trivial module written in
6834 the Rust programming language. (Rust is still not enabled by default
6835 when building Tor.) And as usual, there are numerous other smaller
6836 bugfixes, features, and improvements.
6838 Below are the changes since 0.3.2.10. For a list of only the changes
6839 since 0.3.3.5-rc, see the ChangeLog file.
6841 o New system requirements:
6842 - When built with Rust, Tor now depends on version 0.2.39 of the
6843 libc crate. Closes tickets 25310 and 25664.
6845 o Major features (embedding):
6846 - There is now a documented stable API for programs that need to
6847 embed Tor. See tor_api.h for full documentation and known bugs.
6848 Closes ticket 23684.
6849 - Tor now has support for restarting in the same process.
6850 Controllers that run Tor using the "tor_api.h" interface can now
6851 restart Tor after Tor has exited. This support is incomplete,
6852 however: we fixed crash bugs that prevented it from working at
6853 all, but many bugs probably remain, including a possibility of
6854 security issues. Implements ticket 24581.
6856 o Major features (IPv6, directory documents):
6857 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
6858 consensus. This information makes it easier for IPv6 clients to
6859 bootstrap and choose reachable entry guards. Implements
6861 - Add consensus method 28, which removes IPv6 ORPorts from
6862 microdescriptors. Now that the consensus contains IPv6 ORPorts,
6863 they are redundant in microdescs. This change will be used by Tor
6864 clients on 0.2.8.x and later. (That is to say, with all Tor
6865 clients that have IPv6 bootstrap and guard support.) Implements
6867 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
6868 set by different numbers of authorities. Fixes 23870
6871 o Major features (onion service v3, control port):
6872 - The control port now supports commands and events for v3 onion
6873 services. It is now possible to create ephemeral v3 services using
6874 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
6875 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
6876 DEL_ONION) have been extended to support v3 onion services. Closes
6877 ticket 20699; implements proposal 284.
6879 o Major features (onion services):
6880 - Provide torrc options to pin the second and third hops of onion
6881 service circuits to a list of nodes. The option HSLayer2Guards
6882 pins the second hop, and the option HSLayer3Guards pins the third
6883 hop. These options are for use in conjunction with experiments
6884 with "vanguards" for preventing guard enumeration attacks. Closes
6886 - When v3 onion service clients send introduce cells, they now
6887 include the IPv6 address of the rendezvous point, if it has one.
6888 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
6889 in future Tor versions, IPv6-only v3 single onion services will be
6890 able to use IPv6 addresses to connect directly to the rendezvous
6891 point. Closes ticket 23577. Patch by Neel Chauhan.
6893 o Major features (relay):
6894 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
6895 operator to use a more reasonable ("reduced") exit policy, rather
6896 than the default one. If you want to run an exit node without
6897 thinking too hard about which ports to allow, this one is for you.
6898 Closes ticket 13605. Patch from Neel Chauhan.
6900 o Major features (rust, portability, experimental):
6901 - Tor now ships with an optional implementation of one of its
6902 smaller modules (protover.c) in the Rust programming language. To
6903 try it out, install a Rust build environment, and configure Tor
6904 with "--enable-rust --enable-cargo-online-mode". This should not
6905 cause any user-visible changes, but should help us gain more
6906 experience with Rust, and plan future Rust integration work.
6907 Implementation by Chelsea Komlo. Closes ticket 22840.
6909 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
6910 - When directory authorities read a zero-byte bandwidth file, they
6911 would previously log a warning with the contents of an
6912 uninitialised buffer. They now log a warning about the empty file
6913 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
6915 o Major bugfixes (security, directory authority, denial-of-service):
6916 - Fix a bug that could have allowed an attacker to force a directory
6917 authority to use up all its RAM by passing it a maliciously
6918 crafted protocol versions string. Fixes bug 25517; bugfix on
6919 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
6921 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
6922 - Avoid a rare assertion failure in the circuit build timeout code
6923 if we fail to allow any circuits to actually complete. Fixes bug
6924 25733; bugfix on 0.2.2.2-alpha.
6926 o Major bugfixes (netflow padding):
6927 - Stop adding unneeded channel padding right after we finish
6928 flushing to a connection that has been trying to flush for many
6929 seconds. Instead, treat all partial or complete flushes as
6930 activity on the channel, which will defer the time until we need
6931 to add padding. This fix should resolve confusing and scary log
6932 messages like "Channel padding timeout scheduled 221453ms in the
6933 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
6935 o Major bugfixes (networking):
6936 - Tor will no longer reject IPv6 address strings from Tor Browser
6937 when they are passed as hostnames in SOCKS5 requests. Fixes bug
6938 25036, bugfix on Tor 0.3.1.2.
6940 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
6941 - Correctly detect when onion services get disabled after HUP. Fixes
6942 bug 25761; bugfix on 0.3.2.1.
6944 o Major bugfixes (performance, load balancing):
6945 - Directory authorities no longer vote in favor of the Guard flag
6946 for relays without directory support. Starting in Tor
6947 0.3.0.1-alpha, clients have been avoiding using such relays in the
6948 Guard position, leading to increasingly broken load balancing for
6949 the 5%-or-so of Guards that don't advertise directory support.
6950 Fixes bug 22310; bugfix on 0.3.0.6.
6952 o Major bugfixes (relay):
6953 - If we have failed to connect to a relay and received a connection
6954 refused, timeout, or similar error (at the TCP level), do not try
6955 that same address/port again for 60 seconds after the failure has
6956 occurred. Fixes bug 24767; bugfix on 0.0.6.
6958 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
6959 - Impose a limit on circuit cell queue size. The limit can be
6960 controlled by a consensus parameter. Fixes bug 25226; bugfix
6963 o Minor features (cleanup):
6964 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
6965 when it stops. Closes ticket 23271.
6967 o Minor features (compatibility, backport from 0.3.4.1-alpha):
6968 - Avoid some compilation warnings with recent versions of LibreSSL.
6969 Closes ticket 26006.
6971 o Minor features (config options):
6972 - Change the way the default value for MaxMemInQueues is calculated.
6973 We now use 40% of the hardware RAM if the system has 8 GB RAM or
6974 more. Otherwise we use the former value of 75%. Closes
6977 o Minor features (continuous integration):
6978 - Update the Travis CI configuration to use the stable Rust channel,
6979 now that we have decided to require that. Closes ticket 25714.
6981 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
6982 - Our .travis.yml configuration now includes support for testing the
6983 results of "make distcheck". (It's not uncommon for "make check"
6984 to pass but "make distcheck" to fail.) Closes ticket 25814.
6985 - Our Travis CI configuration now integrates with the Coveralls
6986 coverage analysis tool. Closes ticket 25818.
6988 o Minor features (defensive programming):
6989 - Most of the functions in Tor that free objects have been replaced
6990 with macros that free the objects and set the corresponding
6991 pointers to NULL. This change should help prevent a large class of
6992 dangling pointer bugs. Closes ticket 24337.
6993 - Where possible, the tor_free() macro now only evaluates its input
6994 once. Part of ticket 24337.
6995 - Check that microdesc ed25519 ids are non-zero in
6996 node_get_ed25519_id() before returning them. Implements ticket
6997 24001, patch by "aruna1234".
6999 o Minor features (directory authority):
7000 - When directory authorities are unable to add signatures to a
7001 pending consensus, log the reason why. Closes ticket 24849.
7003 o Minor features (embedding):
7004 - Tor can now start with a preauthenticated control connection
7005 created by the process that launched it. This feature is meant for
7006 use by programs that want to launch and manage a Tor process
7007 without allowing other programs to manage it as well. For more
7008 information, see the __OwningControllerFD option documented in
7009 control-spec.txt. Closes ticket 23900.
7010 - On most errors that would cause Tor to exit, it now tries to
7011 return from the tor_main() function, rather than calling the
7012 system exit() function. Most users won't notice a difference here,
7013 but it should be significant for programs that run Tor inside a
7014 separate thread: they should now be able to survive Tor's exit
7015 conditions rather than having Tor shut down the entire process.
7016 Closes ticket 23848.
7017 - Applications that want to embed Tor can now tell Tor not to
7018 register any of its own POSIX signal handlers, using the
7019 __DisableSignalHandlers option. Closes ticket 24588.
7021 o Minor features (fallback directory list):
7022 - Avoid selecting fallbacks that change their IP addresses too
7023 often. Select more fallbacks by ignoring the Guard flag, and
7024 allowing lower cutoffs for the Running and V2Dir flags. Also allow
7025 a lower bandwidth, and a higher number of fallbacks per operator
7026 (5% of the list). Implements ticket 24785.
7027 - Update the fallback whitelist and blacklist based on opt-ins and
7028 relay changes. Closes tickets 22321, 24678, 22527, 24135,
7031 o Minor features (fallback directory mirror configuration):
7032 - Add a nickname to each fallback in a C comment. This makes it
7033 easier for operators to find their relays, and allows stem to use
7034 nicknames to identify fallbacks. Implements ticket 24600.
7035 - Add a type and version header to the fallback directory mirror
7036 file. Also add a delimiter to the end of each fallback entry. This
7037 helps external parsers like stem and Relay Search. Implements
7039 - Add an extrainfo cache flag for each fallback in a C comment. This
7040 allows stem to use fallbacks to fetch extra-info documents, rather
7041 than using authorities. Implements ticket 22759.
7042 - Add the generateFallbackDirLine.py script for automatically
7043 generating fallback directory mirror lines from relay fingerprints.
7044 No more typos! Add the lookupFallbackDirContact.py script for
7045 automatically looking up operator contact info from relay
7046 fingerprints. Implements ticket 24706, patch by teor and atagar.
7047 - Reject any fallback directory mirror that serves an expired
7048 consensus. Implements ticket 20942, patch by "minik".
7049 - Remove commas and equals signs from external string inputs to the
7050 fallback list. This avoids format confusion attacks. Implements
7052 - Remove the "weight=10" line from fallback directory mirror
7053 entries. Ticket 24681 will maintain the current fallback weights
7054 by changing Tor's default fallback weight to 10. Implements
7056 - Stop logging excessive information about fallback netblocks.
7057 Implements ticket 24791.
7059 o Minor features (forward-compatibility):
7060 - If a relay supports some link authentication protocol that we do
7061 not recognize, then include that relay's ed25519 key when telling
7062 other relays to extend to it. Previously, we treated future
7063 versions as if they were too old to support ed25519 link
7064 authentication. Closes ticket 20895.
7066 o Minor features (geoip):
7067 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
7068 database. Closes ticket 26104.
7070 o Minor features (heartbeat):
7071 - Add onion service information to our heartbeat logs, displaying
7072 stats about the activity of configured onion services. Closes
7075 o Minor features (instrumentation, development):
7076 - Add the MainloopStats option to allow developers to get
7077 instrumentation information from the main event loop via the
7078 heartbeat messages. We hope to use this to improve Tor's behavior
7079 when it's trying to sleep. Closes ticket 24605.
7081 o Minor features (IPv6):
7082 - Make IPv6-only clients wait for microdescs for relays, even if we
7083 were previously using descriptors (or were using them as a bridge)
7084 and have a cached descriptor for them. Implements ticket 23827.
7085 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
7086 them, rather than waiting to download microdescriptors. Implements
7089 o Minor features (log messages):
7090 - Improve log message in the out-of-memory handler to include
7091 information about memory usage from the different compression
7092 backends. Closes ticket 25372.
7093 - Improve a warning message that happens when we fail to re-parse an
7094 old router because of an expired certificate. Closes ticket 20020.
7095 - Make the log more quantitative when we hit MaxMemInQueues
7096 threshold exposing some values. Closes ticket 24501.
7098 o Minor features (logging):
7099 - Clarify the log messages produced when getrandom() or a related
7100 entropy-generation mechanism gives an error. Closes ticket 25120.
7101 - Added support for the Android logging subsystem. Closes
7104 o Minor features (performance):
7105 - Support predictive circuit building for onion service circuits
7106 with multiple layers of guards. Closes ticket 23101.
7107 - Use stdatomic.h where available, rather than mutexes, to implement
7108 atomic_counter_t. Closes ticket 23953.
7110 o Minor features (performance, 32-bit):
7111 - Improve performance on 32-bit systems by avoiding 64-bit division
7112 when calculating the timestamp in milliseconds for channel padding
7113 computations. Implements ticket 24613.
7114 - Improve performance on 32-bit systems by avoiding 64-bit division
7115 when timestamping cells and buffer chunks for OOM calculations.
7116 Implements ticket 24374.
7118 o Minor features (performance, OSX, iOS):
7119 - Use the mach_approximate_time() function (when available) to
7120 implement coarse monotonic time. Having a coarse time function
7121 should avoid a large number of system calls, and improve
7122 performance slightly, especially under load. Closes ticket 24427.
7124 o Minor features (performance, windows):
7125 - Improve performance on Windows Vista and Windows 7 by adjusting
7126 TCP send window size according to the recommendation from
7127 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
7130 o Minor features (sandbox):
7131 - Explicitly permit the poll() system call when the Linux
7132 seccomp2-based sandbox is enabled: apparently, some versions of
7133 libc use poll() when calling getpwnam(). Closes ticket 25313.
7135 o Minor features (storage, configuration):
7136 - Users can store cached directory documents somewhere other than
7137 the DataDirectory by using the CacheDirectory option. Similarly,
7138 the storage location for relay's keys can be overridden with the
7139 KeyDirectory option. Closes ticket 22703.
7141 o Minor features (testing):
7142 - Add a "make test-rust" target to run the rust tests only. Closes
7145 o Minor features (testing, debugging, embedding):
7146 - For development purposes, Tor now has a mode in which it runs for
7147 a few seconds, then stops, and starts again without exiting the
7148 process. This mode is meant to help us debug various issues with
7149 ticket 23847. To use this feature, compile with
7150 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
7151 environment variable. This is expected to crash a lot, and is
7152 really meant for developers only. It will likely be removed in a
7153 future release. Implements ticket 24583.
7155 o Minor bugfixes (build, rust):
7156 - Fix output of autoconf checks to display success messages for Rust
7157 dependencies and a suitable rustc compiler version. Fixes bug
7158 24612; bugfix on 0.3.1.3-alpha.
7159 - Don't pass the --quiet option to cargo: it seems to suppress some
7160 errors, which is not what we want to do when building. Fixes bug
7161 24518; bugfix on 0.3.1.7.
7162 - Build correctly when building from outside Tor's source tree with
7163 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
7166 o Minor bugfixes (C correctness):
7167 - Fix a very unlikely (impossible, we believe) null pointer
7168 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
7169 Coverity; this is CID 1430932.
7171 o Minor bugfixes (channel, client):
7172 - Better identify client connection when reporting to the geoip
7173 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
7175 o Minor bugfixes (circuit, cannibalization):
7176 - Don't cannibalize preemptively-built circuits if we no longer
7177 recognize their first hop. This situation can happen if our Guard
7178 relay went off the consensus after the circuit was created. Fixes
7179 bug 24469; bugfix on 0.0.6.
7181 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
7182 - Don't consider Tor running as a client if the ControlPort is open,
7183 but no actual client ports are open. Fixes bug 26062; bugfix
7186 o Minor bugfixes (compilation):
7187 - Fix a C99 compliance issue in our configuration script that caused
7188 compilation issues when compiling Tor with certain versions of
7189 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
7191 o Minor bugfixes (controller):
7192 - Restore the correct operation of the RESOLVE command, which had
7193 been broken since we added the ability to enable/disable DNS on
7194 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
7195 - Avoid a (nonfatal) assertion failure when extending a one-hop
7196 circuit from the controller to become a multihop circuit. Fixes
7197 bug 24903; bugfix on 0.2.5.2-alpha.
7199 o Minor bugfixes (correctness):
7200 - Remove a nonworking, unnecessary check to see whether a circuit
7201 hop's identity digest was set when the circuit failed. Fixes bug
7202 24927; bugfix on 0.2.4.4-alpha.
7204 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
7205 - Upon receiving a malformed connected cell, stop processing the
7206 cell immediately. Previously we would mark the connection for
7207 close, but continue processing the cell as if the connection were
7208 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
7210 o Minor bugfixes (directory authorities, IPv6):
7211 - When creating a routerstatus (vote) from a routerinfo (descriptor),
7212 set the IPv6 address to the unspecified IPv6 address, and
7213 explicitly initialize the port to zero. Fixes bug 24488; bugfix
7216 o Minor bugfixes (documentation):
7217 - Document that the PerConnBW{Rate,Burst} options will fall back to
7218 their corresponding consensus parameters only if those parameters
7219 are set. Previously we had claimed that these values would always
7220 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
7222 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
7223 - Stop saying in the manual that clients cache ipv4 dns answers from
7224 exit relays. We haven't used them since 0.2.6.3-alpha, and in
7225 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
7226 we forgot to say so in the man page. Fixes bug 26052; bugfix
7229 o Minor bugfixes (exit relay DNS retries):
7230 - Re-attempt timed-out DNS queries 3 times before failure, since our
7231 timeout is 5 seconds for them, but clients wait 10-15. Also allow
7232 slightly more timeouts per resolver when an exit has multiple
7233 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
7235 o Minor bugfixes (fallback directory mirrors):
7236 - Make updateFallbackDirs.py search harder for python. (Some OSs
7237 don't put it in /usr/bin.) Fixes bug 24708; bugfix
7240 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
7241 - When hibernating, close connections normally and allow them to
7242 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
7244 - Do not attempt to launch self-reachability tests when entering
7245 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
7246 - Resolve several bugs related to descriptor fetching on bridge
7247 clients with bandwidth accounting enabled. (This combination is
7248 not recommended!) Fixes a case of bug 12062; bugfix
7250 - When hibernating, do not attempt to launch DNS checks. Fixes a
7251 case of bug 12062; bugfix on 0.1.2.2-alpha.
7252 - When hibernating, do not try to upload or download descriptors.
7253 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
7255 o Minor bugfixes (IPv6, bridges):
7256 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
7257 bugfix on 0.2.8.2-alpha.
7258 - Tor now sets IPv6 address in the routerstatus as well as in the
7259 router descriptors when updating addresses for a bridge. Closes
7260 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
7262 o Minor bugfixes (Linux seccomp2 sandbox):
7263 - When running with the sandbox enabled, reload configuration files
7264 correctly even when %include was used. Previously we would crash.
7265 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
7267 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
7268 - Allow the nanosleep() system call, which glibc uses to implement
7269 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
7271 o Minor bugfixes (logging):
7272 - Fix a (mostly harmless) race condition when invoking
7273 LOG_PROTOCOL_WARN message from a subthread while the torrc options
7274 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
7276 o Minor bugfixes (man page, SocksPort):
7277 - Remove dead code from the old "SocksSocket" option, and rename
7278 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old
7279 option still works, but is deprecated. Fixes bug 24343; bugfix
7282 o Minor bugfixes (memory leaks):
7283 - Avoid possible at-exit memory leaks related to use of Libevent's
7284 event_base_once() function. (This function tends to leak memory if
7285 the event_base is closed before the event fires.) Fixes bug 24584;
7286 bugfix on 0.2.8.1-alpha.
7287 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
7290 o Minor bugfixes (network IPv6 test):
7291 - Tor's test scripts now check if "ping -6 ::1" works when the user
7292 runs "make test-network-all". Fixes bug 24677; bugfix on
7293 0.2.9.3-alpha. Patch by "ffmancera".
7295 o Minor bugfixes (networking):
7296 - string_is_valid_hostname() will not consider IP strings to be
7297 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
7299 o Minor bugfixes (onion service v3):
7300 - Avoid an assertion failure when the next onion service descriptor
7301 rotation type is out of sync with the consensus's valid-after
7302 time. Instead, log a warning message with extra information, so we
7303 can better hunt down the cause of this assertion. Fixes bug 25306;
7304 bugfix on 0.3.2.1-alpha.
7306 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
7307 - Fix a memory leak when a v3 onion service is configured and gets a
7308 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
7309 - When parsing the descriptor signature, look for the token plus an
7310 extra white-space at the end. This is more correct but also will
7311 allow us to support new fields that might start with "signature".
7312 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
7314 o Minor bugfixes (onion services):
7315 - If we are configured to offer a single onion service, don't log
7316 long-term established one hop rendezvous points in the heartbeat.
7317 Fixes bug 25116; bugfix on 0.2.9.6-rc.
7319 o Minor bugfixes (performance):
7320 - Reduce the number of circuits that will be opened at once during
7321 the circuit build timeout phase. This is done by increasing the
7322 idle timeout to 3 minutes, and lowering the maximum number of
7323 concurrent learning circuits to 10. Fixes bug 24769; bugfix
7325 - Avoid calling protocol_list_supports_protocol() from inside tight
7326 loops when running with cached routerinfo_t objects. Instead,
7327 summarize the relevant protocols as flags in the routerinfo_t, as
7328 we do for routerstatus_t objects. This change simplifies our code
7329 a little, and saves a large amount of short-term memory allocation
7330 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
7332 o Minor bugfixes (performance, timeouts):
7333 - Consider circuits for timeout as soon as they complete a hop. This
7334 is more accurate than applying the timeout in
7335 circuit_expire_building() because that function is only called
7336 once per second, which is now too slow for typical timeouts on the
7337 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
7338 - Use onion service circuits (and other circuits longer than 3 hops)
7339 to calculate a circuit build timeout. Previously, Tor only
7340 calculated its build timeout based on circuits that planned to be
7341 exactly 3 hops long. With this change, we include measurements
7342 from all circuits at the point where they complete their third
7343 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
7345 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
7346 - Avoid a crash when running with DirPort set but ORPort turned off.
7347 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
7349 o Minor bugfixes (Rust FFI):
7350 - Fix a minor memory leak which would happen whenever the C code
7351 would call the Rust implementation of
7352 protover_get_supported_protocols(). This was due to the C version
7353 returning a static string, whereas the Rust version newly allocated
7354 a CString to pass across the FFI boundary. Consequently, the C
7355 code was not expecting to need to free() what it was given. Fixes
7356 bug 25127; bugfix on 0.3.2.1-alpha.
7358 o Minor bugfixes (spelling):
7359 - Use the "misspell" tool to detect and fix typos throughout the
7360 source code. Fixes bug 23650; bugfix on various versions of Tor.
7361 Patch from Deepesh Pathak.
7363 o Minor bugfixes (testing):
7364 - Avoid intermittent test failures due to a test that had relied on
7365 onion service introduction point creation finishing within 5
7366 seconds of real clock time. Fixes bug 25450; bugfix
7368 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
7369 bugfix on 0.2.3.1-alpha.
7371 o Minor bugfixes (unit test, monotonic time):
7372 - Increase a constant (1msec to 10msec) in the monotonic time test
7373 that makes sure the nsec/usec/msec times read are synchronized.
7374 This change was needed to accommodate slow systems like armel or
7375 when the clock_gettime() is not a VDSO on the running kernel.
7376 Fixes bug 25113; bugfix on 0.2.9.1.
7378 o Code simplification and refactoring:
7379 - Move the list of default directory authorities to its own file.
7380 Closes ticket 24854. Patch by "beastr0".
7381 - Remove the old (deterministic) directory retry logic entirely:
7382 We've used exponential backoff exclusively for some time. Closes
7384 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
7386 - Remove a series of counters used to track circuit extend attempts
7387 and connection status but that in reality we aren't using for
7388 anything other than stats logged by a SIGUSR1 signal. Closes
7390 - Remove /usr/athena from search path in configure.ac. Closes
7392 - Remove duplicate code in node_has_curve25519_onion_key() and
7393 node_get_curve25519_onion_key(), and add a check for a zero
7394 microdesc curve25519 onion key. Closes ticket 23966, patch by
7395 "aruna1234" and teor.
7396 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
7397 memory allocations with large numbers of OR connections (e.g.
7398 relays). Closes ticket 24119.
7399 - Separate the function that deletes ephemeral files when Tor
7401 - Small changes to Tor's buf_t API to make it suitable for use as a
7402 general-purpose safe string constructor. Closes ticket 22342.
7403 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
7404 avoid source code identifier confusion. Closes ticket 24467.
7405 - The tor_git_revision[] constant no longer needs to be redeclared
7406 by everything that links against the rest of Tor. Done as part of
7407 ticket 23845, to simplify our external API.
7408 - We make extend_info_from_node() use node_get_curve25519_onion_key()
7409 introduced in ticket 23577 to access the curve25519 public keys
7410 rather than accessing it directly. Closes ticket 23760. Patch by
7412 - Add a function to log channels' scheduler state changes to aid
7413 debugging efforts. Closes ticket 24531.
7416 - Improved the documentation of AccountingStart parameter. Closes
7418 - Update the documentation for "Log" to include the current list of
7419 logging domains. Closes ticket 25378.
7420 - Add documentation on how to build tor with Rust dependencies
7421 without having to be online. Closes ticket 22907; bugfix
7423 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
7424 traffic. Closes ticket 24318.
7425 - Document that OutboundBindAddress doesn't apply to DNS requests.
7426 Closes ticket 22145. Patch from Aruna Maurya.
7428 o Code simplification and refactoring (channels):
7429 - Remove the incoming and outgoing channel queues. These were never
7430 used, but still took up a step in our fast path.
7431 - The majority of the channel unit tests have been rewritten and the
7432 code coverage has now been raised to 83.6% for channel.c. Closes
7434 - Remove other dead code from the channel subsystem: All together,
7435 this cleanup has removed more than 1500 lines of code overall and
7436 adding very little except for unit test.
7438 o Code simplification and refactoring (circuit rendezvous):
7439 - Split the client-side rendezvous circuit lookup into two
7440 functions: one that returns only established circuits and another
7441 that returns all kinds of circuits. Closes ticket 23459.
7443 o Code simplification and refactoring (controller):
7444 - Make most of the variables in networkstatus_getinfo_by_purpose()
7445 const. Implements ticket 24489.
7447 o Documentation (backport from 0.3.4.1-alpha):
7448 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
7449 ticket 25857. Patch from "CTassisF".
7451 o Documentation (man page):
7452 - The HiddenServiceVersion torrc option accepts only one number:
7453 either version 2 or 3. Closes ticket 25026; bugfix
7456 o Documentation (manpage, denial of service):
7457 - Provide more detail about the denial-of-service options, by
7458 listing each mitigation and explaining how they relate. Closes
7462 Changes in version 0.3.1.10 - 2018-03-03
7463 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
7466 It includes an important security fix for a remote crash attack
7467 against directory authorities, tracked as TROVE-2018-001.
7469 This release also backports our new system for improved resistance to
7470 denial-of-service attacks against relays.
7472 This release also fixes several minor bugs and annoyances from
7475 All directory authorities should upgrade to one of the versions
7476 released today. Relays running 0.3.1.x may wish to update to one of
7477 the versions released today, for the DoS mitigations.
7479 Please note: according to our release calendar, Tor 0.3.1 will no
7480 longer be supported after 1 July 2018. If you will be running Tor
7481 after that date, you should make sure to plan to upgrade to the latest
7482 stable version, or downgrade to 0.2.9 (which will receive long-term
7485 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
7486 - Fix a protocol-list handling bug that could be used to remotely crash
7487 directory authorities with a null-pointer exception. Fixes bug 25074;
7488 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
7491 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
7492 - Give relays some defenses against the recent network overload. We
7493 start with three defenses (default parameters in parentheses).
7494 First: if a single client address makes too many concurrent
7495 connections (>100), hang up on further connections. Second: if a
7496 single client address makes circuits too quickly (more than 3 per
7497 second, with an allowed burst of 90) while also having too many
7498 connections open (3), refuse new create cells for the next while
7499 (1-2 hours). Third: if a client asks to establish a rendezvous
7500 point to you directly, ignore the request. These defenses can be
7501 manually controlled by new torrc options, but relays will also
7502 take guidance from consensus parameters, so there's no need to
7503 configure anything manually. Implements ticket 24902.
7505 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
7506 - Update the sandbox rules so that they should now work correctly
7507 with Glibc 2.26. Closes ticket 24315.
7509 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
7510 - Fix an "off by 2" error in counting rendezvous failures on the
7511 onion service side. While we thought we would stop the rendezvous
7512 attempt after one failed circuit, we were actually making three
7513 circuit attempts before giving up. Now switch to a default of 2,
7514 and allow the consensus parameter "hs_service_max_rdv_failures" to
7515 override. Fixes bug 24895; bugfix on 0.0.6.
7517 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
7518 - Add Link protocol version 5 to the supported protocols list. Fixes
7519 bug 25070; bugfix on 0.3.1.1-alpha.
7521 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
7522 - Fix a set of false positives where relays would consider
7523 connections to other relays as being client-only connections (and
7524 thus e.g. deserving different link padding schemes) if those
7525 relays fell out of the consensus briefly. Now we look only at the
7526 initial handshake and whether the connection authenticated as a
7527 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
7529 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
7530 - Make our OOM handler aware of the geoip client history cache so it
7531 doesn't fill up the memory. This check is important for IPv6 and
7532 our DoS mitigation subsystem. Closes ticket 25122.
7534 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
7535 - Change relay bandwidth reporting stats interval from 4 hours to 24
7536 hours in order to reduce the efficiency of guard discovery
7537 attacks. Fixes ticket 23856.
7539 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
7540 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
7541 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
7542 since they neither disabled TLS 1.3 nor enabled any of the
7543 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
7544 Closes ticket 24978.
7546 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
7547 - The fallback directory list has been re-generated based on the
7548 current status of the network. Tor uses fallback directories to
7549 bootstrap when it doesn't yet have up-to-date directory
7550 information. Closes ticket 24801.
7551 - Make the default DirAuthorityFallbackRate 0.1, so that clients
7552 prefer to bootstrap from fallback directory mirrors. This is a
7553 follow-up to 24679, which removed weights from the default
7554 fallbacks. Implements ticket 24681.
7556 o Minor features (geoip):
7557 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
7560 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
7561 - Use the actual observed address of an incoming relay connection,
7562 not the canonical address of the relay from its descriptor, when
7563 making decisions about how to handle the incoming connection.
7564 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
7566 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
7567 - Directory authorities, when refusing a descriptor from a rejected
7568 relay, now explicitly tell the relay (in its logs) to set a valid
7569 ContactInfo address and contact the bad-relays@ mailing list.
7570 Fixes bug 25170; bugfix on 0.2.9.1.
7572 o Minor bugfixes (address selection, backport from 0.3.2.9):
7573 - When the fascist_firewall_choose_address_ functions don't find a
7574 reachable address, set the returned address to the null address
7575 and port. This is a precautionary measure, because some callers do
7576 not check the return value. Fixes bug 24736; bugfix
7579 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
7580 - Fetch descriptors aggressively whenever we lack enough to build
7581 circuits, regardless of how many descriptors we are missing.
7582 Previously, we would delay launching the fetch when we had fewer
7583 than 15 missing descriptors, even if some of those descriptors
7584 were blocking circuits from building. Fixes bug 23985; bugfix on
7585 0.1.1.11-alpha. The effects of this bug became worse in
7586 0.3.0.3-alpha, when we began treating missing descriptors from our
7587 primary guards as a reason to delay circuits.
7588 - Don't try fetching microdescriptors from relays that have failed
7589 to deliver them in the past. Fixes bug 23817; bugfix
7592 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
7593 - Fix a signed/unsigned comparison warning introduced by our fix to
7594 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
7596 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
7597 - Avoid a crash when attempting to use the seccomp2 sandbox together
7598 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
7601 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
7602 - Fix a possible crash on malformed consensus. If a consensus had
7603 contained an unparseable protocol line, it could have made clients
7604 and relays crash with a null-pointer exception. To exploit this
7605 issue, however, an attacker would need to be able to subvert the
7606 directory authority system. Fixes bug 25251; bugfix on
7607 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
7609 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
7610 - Recover better from empty or corrupt files in the consensus cache
7611 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
7612 - When a consensus diff calculation is only partially successful,
7613 only record the successful parts as having succeeded. Partial
7614 success can happen if (for example) one compression method fails
7615 but the others succeed. Previously we misrecorded all the
7616 calculations as having succeeded, which would later cause a
7617 nonfatal assertion failure. Fixes bug 24086; bugfix
7620 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
7621 - Tor now updates its guard state when it reads a consensus
7622 regardless of whether it's missing descriptors. That makes tor use
7623 its primary guards to fetch descriptors in some edge cases where
7624 it would previously have used fallback directories. Fixes bug
7625 23862; bugfix on 0.3.0.1-alpha.
7627 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
7628 - Don't treat inability to store a cached consensus object as a bug:
7629 it can happen normally when we are out of disk space. Fixes bug
7630 24859; bugfix on 0.3.1.1-alpha.
7632 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
7633 - When queuing DESTROY cells on a channel, only queue the circuit-id
7634 and reason fields: not the entire 514-byte cell. This fix should
7635 help mitigate any bugs or attacks that fill up these queues, and
7636 free more RAM for other uses. Fixes bug 24666; bugfix
7639 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
7640 - When closing a connection via close_connection_immediately(), we
7641 mark it as "not blocked on bandwidth", to prevent later calls from
7642 trying to unblock it, and give it permission to read. This fixes a
7643 backtrace warning that can happen on relays under various
7644 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
7646 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
7647 - When selecting relays by bandwidth, avoid a rounding error that
7648 could sometimes cause load to be imbalanced incorrectly.
7649 Previously, we would always round upwards; now, we round towards
7650 the nearest integer. This had the biggest effect when a relay's
7651 weight adjustments should have given it weight 0, but it got
7652 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
7653 - When calculating the fraction of nodes that have descriptors, and
7654 all nodes in the network have zero bandwidths, count the number of
7655 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
7656 - Actually log the total bandwidth in compute_weighted_bandwidths().
7657 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
7659 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
7660 - Improve the performance of our consensus-diff application code
7661 when Tor is built with the --enable-fragile-hardening option set.
7662 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
7664 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
7665 - Don't exit the Tor process if setrlimit() fails to change the file
7666 limit (which can happen sometimes on some versions of OSX). Fixes
7667 bug 21074; bugfix on 0.0.9pre5.
7669 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
7670 - Fix a bug in the bit-counting parts of our timing-wheel code on
7671 MSVC. (Note that MSVC is still not a supported build platform, due
7672 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
7675 o Minor bugfixes (relay, partial backport):
7676 - Make the internal channel_is_client() function look at what sort
7677 of connection handshake the other side used, rather than whether
7678 the other side ever sent a create_fast cell to us. Backports part
7679 of the fixes from bugs 22805 and 24898.
7681 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
7682 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
7684 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
7685 bugfix on 0.2.9.4-alpha.
7687 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
7688 - Update the "rust dependencies" submodule to be a project-level
7689 repository, rather than a user repository. Closes ticket 25323.
7692 Changes in version 0.2.9.15 - 2018-03-03
7693 Tor 0.2.9.15 backports important security and stability bugfixes from
7696 It includes an important security fix for a remote crash attack
7697 against directory authorities, tracked as TROVE-2018-001.
7699 This release also backports our new system for improved resistance to
7700 denial-of-service attacks against relays.
7702 This release also fixes several minor bugs and annoyances from
7705 All directory authorities should upgrade to one of the versions
7706 released today. Relays running 0.2.9.x may wish to update to one of
7707 the versions released today, for the DoS mitigations.
7709 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
7710 - Fix a protocol-list handling bug that could be used to remotely crash
7711 directory authorities with a null-pointer exception. Fixes bug 25074;
7712 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
7715 o Major features (denial-of-service mitigation):
7716 - Give relays some defenses against the recent network overload. We
7717 start with three defenses (default parameters in parentheses).
7718 First: if a single client address makes too many concurrent
7719 connections (>100), hang up on further connections. Second: if a
7720 single client address makes circuits too quickly (more than 3 per
7721 second, with an allowed burst of 90) while also having too many
7722 connections open (3), refuse new create cells for the next while
7723 (1-2 hours). Third: if a client asks to establish a rendezvous
7724 point to you directly, ignore the request. These defenses can be
7725 manually controlled by new torrc options, but relays will also
7726 take guidance from consensus parameters, so there's no need to
7727 configure anything manually. Implements ticket 24902.
7729 o Major bugfixes (bootstrapping):
7730 - Fetch descriptors aggressively whenever we lack enough to build
7731 circuits, regardless of how many descriptors we are missing.
7732 Previously, we would delay launching the fetch when we had fewer
7733 than 15 missing descriptors, even if some of those descriptors
7734 were blocking circuits from building. Fixes bug 23985; bugfix on
7735 0.1.1.11-alpha. The effects of this bug became worse in
7736 0.3.0.3-alpha, when we began treating missing descriptors from our
7737 primary guards as a reason to delay circuits.
7739 o Major bugfixes (onion services, retry behavior):
7740 - Fix an "off by 2" error in counting rendezvous failures on the
7741 onion service side. While we thought we would stop the rendezvous
7742 attempt after one failed circuit, we were actually making three
7743 circuit attempts before giving up. Now switch to a default of 2,
7744 and allow the consensus parameter "hs_service_max_rdv_failures" to
7745 override. Fixes bug 24895; bugfix on 0.0.6.
7747 o Minor feature (relay statistics):
7748 - Change relay bandwidth reporting stats interval from 4 hours to 24
7749 hours in order to reduce the efficiency of guard discovery
7750 attacks. Fixes ticket 23856.
7752 o Minor features (compatibility, OpenSSL):
7753 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
7754 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
7755 since they neither disabled TLS 1.3 nor enabled any of the
7756 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
7757 Closes ticket 24978.
7759 o Minor features (denial-of-service avoidance):
7760 - Make our OOM handler aware of the geoip client history cache so it
7761 doesn't fill up the memory. This check is important for IPv6 and
7762 our DoS mitigation subsystem. Closes ticket 25122.
7764 o Minor features (fallback directory mirrors):
7765 - The fallback directory list has been re-generated based on the
7766 current status of the network. Tor uses fallback directories to
7767 bootstrap when it doesn't yet have up-to-date directory
7768 information. Closes ticket 24801.
7769 - Make the default DirAuthorityFallbackRate 0.1, so that clients
7770 prefer to bootstrap from fallback directory mirrors. This is a
7771 follow-up to 24679, which removed weights from the default
7772 fallbacks. Implements ticket 24681.
7774 o Minor features (geoip):
7775 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
7778 o Minor features (linux seccomp2 sandbox):
7779 - Update the sandbox rules so that they should now work correctly
7780 with Glibc 2.26. Closes ticket 24315.
7782 o Minor bugfix (channel connection):
7783 - Use the actual observed address of an incoming relay connection,
7784 not the canonical address of the relay from its descriptor, when
7785 making decisions about how to handle the incoming connection.
7786 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
7788 o Minor bugfix (directory authority):
7789 - Directory authorities, when refusing a descriptor from a rejected
7790 relay, now explicitly tell the relay (in its logs) to set a valid
7791 ContactInfo address and contact the bad-relays@ mailing list.
7792 Fixes bug 25170; bugfix on 0.2.9.1.
7794 o Minor bugfixes (address selection):
7795 - When the fascist_firewall_choose_address_ functions don't find a
7796 reachable address, set the returned address to the null address
7797 and port. This is a precautionary measure, because some callers do
7798 not check the return value. Fixes bug 24736; bugfix
7801 o Minor bugfixes (compilation):
7802 - Fix a signed/unsigned comparison warning introduced by our fix to
7803 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
7805 o Minor bugfixes (control port, linux seccomp2 sandbox):
7806 - Avoid a crash when attempting to use the seccomp2 sandbox together
7807 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
7810 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
7811 - Fix a possible crash on malformed consensus. If a consensus had
7812 contained an unparseable protocol line, it could have made clients
7813 and relays crash with a null-pointer exception. To exploit this
7814 issue, however, an attacker would need to be able to subvert the
7815 directory authority system. Fixes bug 25251; bugfix on
7816 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
7818 o Minor bugfixes (memory usage):
7819 - When queuing DESTROY cells on a channel, only queue the circuit-id
7820 and reason fields: not the entire 514-byte cell. This fix should
7821 help mitigate any bugs or attacks that fill up these queues, and
7822 free more RAM for other uses. Fixes bug 24666; bugfix
7825 o Minor bugfixes (network layer):
7826 - When closing a connection via close_connection_immediately(), we
7827 mark it as "not blocked on bandwidth", to prevent later calls from
7828 trying to unblock it, and give it permission to read. This fixes a
7829 backtrace warning that can happen on relays under various
7830 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
7832 o Minor bugfixes (OSX):
7833 - Don't exit the Tor process if setrlimit() fails to change the file
7834 limit (which can happen sometimes on some versions of OSX). Fixes
7835 bug 21074; bugfix on 0.0.9pre5.
7837 o Minor bugfixes (path selection):
7838 - When selecting relays by bandwidth, avoid a rounding error that
7839 could sometimes cause load to be imbalanced incorrectly.
7840 Previously, we would always round upwards; now, we round towards
7841 the nearest integer. This had the biggest effect when a relay's
7842 weight adjustments should have given it weight 0, but it got
7843 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
7844 - When calculating the fraction of nodes that have descriptors, and
7845 all nodes in the network have zero bandwidths, count the number of
7846 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
7847 - Actually log the total bandwidth in compute_weighted_bandwidths().
7848 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
7850 o Minor bugfixes (portability, msvc):
7851 - Fix a bug in the bit-counting parts of our timing-wheel code on
7852 MSVC. (Note that MSVC is still not a supported build platform, due
7853 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
7856 o Minor bugfixes (relay):
7857 - Make the internal channel_is_client() function look at what sort
7858 of connection handshake the other side used, rather than whether
7859 the other side ever sent a create_fast cell to us. Backports part
7860 of the fixes from bugs 22805 and 24898.
7862 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
7863 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
7865 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
7866 bugfix on 0.2.9.4-alpha.
7869 Changes in version 0.3.2.10 - 2018-03-03
7870 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
7871 backports a number of bugfixes, including important fixes for security
7874 It includes an important security fix for a remote crash attack
7875 against directory authorities, tracked as TROVE-2018-001.
7877 Additionally, it backports a fix for a bug whose severity we have
7878 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
7879 triggered in order to crash relays with a use-after-free pattern. As
7880 such, we are now tracking that bug as TROVE-2018-002 and
7881 CVE-2018-0491, and backporting it to earlier releases. This bug
7882 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
7885 This release also backports our new system for improved resistance to
7886 denial-of-service attacks against relays.
7888 This release also fixes several minor bugs and annoyances from
7891 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
7892 today, for the fix to TROVE-2018-002. Directory authorities should
7893 also upgrade. (Relays on earlier versions might want to update too for
7894 the DoS mitigations.)
7896 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
7897 - Fix a protocol-list handling bug that could be used to remotely crash
7898 directory authorities with a null-pointer exception. Fixes bug 25074;
7899 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
7902 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
7903 - Avoid adding the same channel twice in the KIST scheduler pending
7904 list, which could lead to remote denial-of-service use-after-free
7905 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
7907 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
7908 - Give relays some defenses against the recent network overload. We
7909 start with three defenses (default parameters in parentheses).
7910 First: if a single client address makes too many concurrent
7911 connections (>100), hang up on further connections. Second: if a
7912 single client address makes circuits too quickly (more than 3 per
7913 second, with an allowed burst of 90) while also having too many
7914 connections open (3), refuse new create cells for the next while
7915 (1-2 hours). Third: if a client asks to establish a rendezvous
7916 point to you directly, ignore the request. These defenses can be
7917 manually controlled by new torrc options, but relays will also
7918 take guidance from consensus parameters, so there's no need to
7919 configure anything manually. Implements ticket 24902.
7921 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
7922 - Fix an "off by 2" error in counting rendezvous failures on the
7923 onion service side. While we thought we would stop the rendezvous
7924 attempt after one failed circuit, we were actually making three
7925 circuit attempts before giving up. Now switch to a default of 2,
7926 and allow the consensus parameter "hs_service_max_rdv_failures" to
7927 override. Fixes bug 24895; bugfix on 0.0.6.
7928 - New-style (v3) onion services now obey the "max rendezvous circuit
7929 attempts" logic. Previously they would make as many rendezvous
7930 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
7931 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
7933 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
7934 - Add Link protocol version 5 to the supported protocols list. Fixes
7935 bug 25070; bugfix on 0.3.1.1-alpha.
7937 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
7938 - Fix a set of false positives where relays would consider
7939 connections to other relays as being client-only connections (and
7940 thus e.g. deserving different link padding schemes) if those
7941 relays fell out of the consensus briefly. Now we look only at the
7942 initial handshake and whether the connection authenticated as a
7943 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
7945 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
7946 - The scheduler subsystem was failing to promptly notice changes in
7947 consensus parameters, making it harder to switch schedulers
7948 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
7950 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
7951 - Make our OOM handler aware of the geoip client history cache so it
7952 doesn't fill up the memory. This check is important for IPv6 and
7953 our DoS mitigation subsystem. Closes ticket 25122.
7955 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
7956 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
7957 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
7958 since they neither disabled TLS 1.3 nor enabled any of the
7959 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
7960 Closes ticket 24978.
7962 o Minor features (geoip):
7963 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
7966 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
7967 - When logging a failure to create an onion service's descriptor,
7968 also log what the problem with the descriptor was. Diagnostic
7971 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
7972 - Use the actual observed address of an incoming relay connection,
7973 not the canonical address of the relay from its descriptor, when
7974 making decisions about how to handle the incoming connection.
7975 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
7977 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
7978 - Fix a possible crash on malformed consensus. If a consensus had
7979 contained an unparseable protocol line, it could have made clients
7980 and relays crash with a null-pointer exception. To exploit this
7981 issue, however, an attacker would need to be able to subvert the
7982 directory authority system. Fixes bug 25251; bugfix on
7983 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
7985 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
7986 - Directory authorities, when refusing a descriptor from a rejected
7987 relay, now explicitly tell the relay (in its logs) to set a valid
7988 ContactInfo address and contact the bad-relays@ mailing list.
7989 Fixes bug 25170; bugfix on 0.2.9.1.
7991 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
7992 - When building with Rust on OSX, link against libresolv, to work
7993 around the issue at https://github.com/rust-lang/rust/issues/46797.
7994 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
7996 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
7997 - Remove a BUG() statement when a client fetches an onion descriptor
7998 that has a lower revision counter than the one in its cache. This
7999 can happen in normal circumstances due to HSDir desync. Fixes bug
8000 24976; bugfix on 0.3.2.1-alpha.
8002 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
8003 - Don't treat inability to store a cached consensus object as a bug:
8004 it can happen normally when we are out of disk space. Fixes bug
8005 24859; bugfix on 0.3.1.1-alpha.
8007 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
8008 - Improve the performance of our consensus-diff application code
8009 when Tor is built with the --enable-fragile-hardening option set.
8010 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
8012 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
8013 - Don't exit the Tor process if setrlimit() fails to change the file
8014 limit (which can happen sometimes on some versions of OSX). Fixes
8015 bug 21074; bugfix on 0.0.9pre5.
8017 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
8018 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
8020 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
8021 bugfix on 0.2.9.4-alpha.
8023 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
8024 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
8025 25005; bugfix on 0.3.2.7-rc.
8027 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
8028 - Look at the "HSRend" protocol version, not the "HSDir" protocol
8029 version, when deciding whether a consensus entry can support the
8030 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
8031 bugfix on 0.3.2.1-alpha.
8033 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
8034 - Update the "rust dependencies" submodule to be a project-level
8035 repository, rather than a user repository. Closes ticket 25323.
8037 o Documentation (backport from 0.3.3.1-alpha)
8038 - Document that operators who run more than one relay or bridge are
8039 expected to set MyFamily and ContactInfo correctly. Closes
8043 Changes in version 0.3.2.9 - 2018-01-09
8044 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
8046 The 0.3.2 series includes our long-anticipated new onion service
8047 design, with numerous security features. (For more information, see
8048 our blog post at https://blog.torproject.org/fall-harvest.) We also
8049 have a new circuit scheduler algorithm for improved performance on
8050 relays everywhere (see https://blog.torproject.org/kist-and-tell),
8051 along with many smaller features and bugfixes.
8053 Per our stable release policy, we plan to support each stable release
8054 series for at least the next nine months, or for three months after
8055 the first stable release of the next series: whichever is longer. If
8056 you need a release with long-term support, we recommend that you stay
8057 with the 0.2.9 series.
8059 Below is a list of the changes since 0.3.1.7. For a list of all
8060 changes since 0.3.2.8-rc, see the ChangeLog file.
8062 o Directory authority changes:
8063 - Add "Bastet" as a ninth directory authority to the default list.
8064 Closes ticket 23910.
8065 - The directory authority "Longclaw" has changed its IP address.
8066 Closes ticket 23592.
8067 - Remove longclaw's IPv6 address, as it will soon change. Authority
8068 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
8069 3/8 directory authorities with IPv6 addresses, but there are also
8070 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
8071 - Add an IPv6 address for the "bastet" directory authority. Closes
8074 o Major features (next-generation onion services):
8075 - Tor now supports the next-generation onion services protocol for
8076 clients and services! As part of this release, the core of
8077 proposal 224 has been implemented and is available for
8078 experimentation and testing by our users. This newer version of
8079 onion services ("v3") features many improvements over the legacy
8082 a) Better crypto (replaced SHA1/DH/RSA1024
8083 with SHA3/ed25519/curve25519)
8085 b) Improved directory protocol, leaking much less information to
8088 c) Improved directory protocol, with smaller surface for
8091 d) Better onion address security against impersonation.
8093 e) More extensible introduction/rendezvous protocol.
8095 f) A cleaner and more modular codebase.
8097 You can identify a next-generation onion address by its length:
8098 they are 56 characters long, as in
8099 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
8101 In the future, we will release more options and features for v3
8102 onion services, but we first need a testing period, so that the
8103 current codebase matures and becomes more robust. Planned features
8104 include: offline keys, advanced client authorization, improved
8105 guard algorithms, and statistics. For full details, see
8108 Legacy ("v2") onion services will still work for the foreseeable
8109 future, and will remain the default until this new codebase gets
8110 tested and hardened. Service operators who want to experiment with
8111 the new system can use the 'HiddenServiceVersion 3' torrc
8112 directive along with the regular onion service configuration
8113 options. For more information, see our blog post at
8114 "https://blog.torproject.org/fall-harvest". Enjoy!
8116 o Major feature (scheduler, channel):
8117 - Tor now uses new schedulers to decide which circuits should
8118 deliver cells first, in order to improve congestion at relays. The
8119 first type is called "KIST" ("Kernel Informed Socket Transport"),
8120 and is only available on Linux-like systems: it uses feedback from
8121 the kernel to prevent the kernel's TCP buffers from growing too
8122 full. The second new scheduler type is called "KISTLite": it
8123 behaves the same as KIST, but runs on systems without kernel
8124 support for inspecting TCP implementation details. The old
8125 scheduler is still available, under the name "Vanilla". To change
8126 the default scheduler preference order, use the new "Schedulers"
8127 option. (The default preference order is "KIST,KISTLite,Vanilla".)
8129 Matt Traudt implemented KIST, based on research by Rob Jansen,
8130 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
8131 more information, see the design paper at
8132 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
8133 followup implementation paper at https://arxiv.org/abs/1709.01044.
8134 Closes ticket 12541. For more information, see our blog post at
8135 "https://blog.torproject.org/kist-and-tell".
8137 o Major bugfixes (security, general):
8138 - Fix a denial of service bug where an attacker could use a
8139 malformed directory object to cause a Tor instance to pause while
8140 OpenSSL would try to read a passphrase from the terminal. (Tor
8141 instances run without a terminal, which is the case for most Tor
8142 packages, are not impacted.) Fixes bug 24246; bugfix on every
8143 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
8144 Found by OSS-Fuzz as testcase 6360145429790720.
8146 o Major bugfixes (security, directory authority):
8147 - Fix a denial of service issue where an attacker could crash a
8148 directory authority using a malformed router descriptor. Fixes bug
8149 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
8152 o Major bugfixes (security, onion service v2):
8153 - Fix a use-after-free error that could crash v2 Tor onion services
8154 when they failed to open circuits while expiring introduction
8155 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
8156 also tracked as TROVE-2017-013 and CVE-2017-8823.
8157 - When checking for replays in the INTRODUCE1 cell data for a
8158 (legacy) onion service, correctly detect replays in the RSA-
8159 encrypted part of the cell. We were previously checking for
8160 replays on the entire cell, but those can be circumvented due to
8161 the malleability of Tor's legacy hybrid encryption. This fix helps
8162 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
8163 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
8166 o Major bugfixes (security, relay):
8167 - When running as a relay, make sure that we never build a path
8168 through ourselves, even in the case where we have somehow lost the
8169 version of our descriptor appearing in the consensus. Fixes part
8170 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
8171 as TROVE-2017-012 and CVE-2017-8822.
8172 - When running as a relay, make sure that we never choose ourselves
8173 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
8174 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
8176 o Major bugfixes (bootstrapping):
8177 - Fetch descriptors aggressively whenever we lack enough to build
8178 circuits, regardless of how many descriptors we are missing.
8179 Previously, we would delay launching the fetch when we had fewer
8180 than 15 missing descriptors, even if some of those descriptors
8181 were blocking circuits from building. Fixes bug 23985; bugfix on
8182 0.1.1.11-alpha. The effects of this bug became worse in
8183 0.3.0.3-alpha, when we began treating missing descriptors from our
8184 primary guards as a reason to delay circuits.
8185 - Don't try fetching microdescriptors from relays that have failed
8186 to deliver them in the past. Fixes bug 23817; bugfix
8189 o Major bugfixes (circuit prediction):
8190 - Fix circuit prediction logic so that a client doesn't treat a port
8191 as being "handled" by a circuit if that circuit already has
8192 isolation settings on it. This change should make Tor clients more
8193 responsive by improving their chances of having a pre-created
8194 circuit ready for use when a request arrives. Fixes bug 18859;
8195 bugfix on 0.2.3.3-alpha.
8197 o Major bugfixes (exit relays, DNS):
8198 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
8199 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
8200 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
8201 identifying and finding a workaround to this bug and to Moritz,
8202 Arthur Edelstein, and Roger for helping to track it down and
8205 o Major bugfixes (relay, crash, assertion failure):
8206 - Fix a timing-based assertion failure that could occur when the
8207 circuit out-of-memory handler freed a connection's output buffer.
8208 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
8210 o Major bugfixes (usability, control port):
8211 - Report trusted clock skew indications as bootstrap errors, so
8212 controllers can more easily alert users when their clocks are
8213 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
8215 o Minor features (bridge):
8216 - Bridge relays can now set the BridgeDistribution config option to
8217 add a "bridge-distribution-request" line to their bridge
8218 descriptor, which tells BridgeDB how they'd like their bridge
8219 address to be given out. (Note that as of Oct 2017, BridgeDB does
8220 not yet implement this feature.) As a side benefit, this feature
8221 provides a way to distinguish bridge descriptors from non-bridge
8222 descriptors. Implements tickets 18329.
8223 - When handling the USERADDR command on an ExtOrPort, warn when the
8224 transports provides a USERADDR with no port. In a future version,
8225 USERADDR commands of this format may be rejected. Detects problems
8226 related to ticket 23080.
8228 o Minor features (bug detection):
8229 - Log a warning message with a stack trace for any attempt to call
8230 get_options() during option validation. This pattern has caused
8231 subtle bugs in the past. Closes ticket 22281.
8233 o Minor features (build, compilation):
8234 - The "check-changes" feature is now part of the "make check" tests;
8235 we'll use it to try to prevent misformed changes files from
8236 accumulating. Closes ticket 23564.
8237 - Tor builds should now fail if there are any mismatches between the
8238 C type representing a configuration variable and the C type the
8239 data-driven parser uses to store a value there. Previously, we
8240 needed to check these by hand, which sometimes led to mistakes.
8241 Closes ticket 23643.
8243 o Minor features (client):
8244 - You can now use Tor as a tunneled HTTP proxy: use the new
8245 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
8246 requests. Closes ticket 22407.
8247 - Add an extra check to make sure that we always use the newer guard
8248 selection code for picking our guards. Closes ticket 22779.
8249 - When downloading (micro)descriptors, don't split the list into
8250 multiple requests unless we want at least 32 descriptors.
8251 Previously, we split at 4, not 32, which led to significant
8252 overhead in HTTP request size and degradation in compression
8253 performance. Closes ticket 23220.
8254 - Improve log messages when missing descriptors for primary guards.
8255 Resolves ticket 23670.
8257 o Minor features (command line):
8258 - Add a new commandline option, --key-expiration, which prints when
8259 the current signing key is going to expire. Implements ticket
8260 17639; patch by Isis Lovecruft.
8262 o Minor features (control port):
8263 - If an application tries to use the control port as an HTTP proxy,
8264 respond with a meaningful "This is the Tor control port" message,
8265 and log the event. Closes ticket 1667. Patch from Ravi
8267 - Provide better error message for GETINFO desc/(id|name) when not
8268 fetching router descriptors. Closes ticket 5847. Patch by
8270 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
8271 whether Tor will try to download router descriptors and
8272 microdescriptors respectively. Closes ticket 22684.
8273 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
8274 so controllers can tell whether the geoip databases are loaded.
8275 Closes ticket 23237.
8276 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
8277 events. Closes ticket 19254. Patch by "DonnchaC".
8279 o Minor features (development support):
8280 - Developers can now generate a call-graph for Tor using the
8281 "calltool" python program, which post-processes object dumps. It
8282 should work okay on many Linux and OSX platforms, and might work
8283 elsewhere too. To run it, install calltool from
8284 https://gitweb.torproject.org/user/nickm/calltool.git and run
8285 "make callgraph". Closes ticket 19307.
8287 o Minor features (directory authority):
8288 - Make the "Exit" flag assignment only depend on whether the exit
8289 policy allows connections to ports 80 and 443. Previously relays
8290 would get the Exit flag if they allowed connections to one of
8291 these ports and also port 6667. Resolves ticket 23637.
8293 o Minor features (ed25519):
8294 - Add validation function to checks for torsion components in
8295 ed25519 public keys, used by prop224 client-side code. Closes
8296 ticket 22006. Math help by Ian Goldberg.
8298 o Minor features (exit relay, DNS):
8299 - Improve the clarity and safety of the log message from evdns when
8300 receiving an apparently spoofed DNS reply. Closes ticket 3056.
8302 o Minor features (fallback directory mirrors):
8303 - The fallback directory list has been re-generated based on the
8304 current status of the network. Tor uses fallback directories to
8305 bootstrap when it doesn't yet have up-to-date directory
8306 information. Closes ticket 24801.
8307 - Make the default DirAuthorityFallbackRate 0.1, so that clients
8308 prefer to bootstrap from fallback directory mirrors. This is a
8309 follow-up to 24679, which removed weights from the default
8310 fallbacks. Implements ticket 24681.
8312 o Minor features (geoip):
8313 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
8316 o Minor features (integration, hardening):
8317 - Add a new NoExec option to prevent Tor from running other
8318 programs. When this option is set to 1, Tor will never try to run
8319 another program, regardless of the settings of
8320 PortForwardingHelper, ClientTransportPlugin, or
8321 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
8322 without restarting Tor. Closes ticket 22976.
8324 o Minor features (linux seccomp2 sandbox):
8325 - Update the sandbox rules so that they should now work correctly
8326 with Glibc 2.26. Closes ticket 24315.
8328 o Minor features (logging):
8329 - Provide better warnings when the getrandom() syscall fails. Closes
8331 - Downgrade a pair of log messages that could occur when an exit's
8332 resolver gave us an unusual (but not forbidden) response. Closes
8334 - Improve the message we log when re-enabling circuit build timeouts
8335 after having received a consensus. Closes ticket 20963.
8336 - Log more circuit information whenever we are about to try to
8337 package a relay cell on a circuit with a nonexistent n_chan.
8338 Attempt to diagnose ticket 8185.
8339 - Improve info-level log identification of particular circuits, to
8340 help with debugging. Closes ticket 23645.
8341 - Improve the warning message for specifying a relay by nickname.
8342 The previous message implied that nickname registration was still
8343 part of the Tor network design, which it isn't. Closes
8345 - If the sandbox filter fails to load, suggest to the user that
8346 their kernel might not support seccomp2. Closes ticket 23090.
8348 o Minor features (onion service, circuit, logging):
8349 - Improve logging of many callsite in the circuit subsystem to print
8350 the circuit identifier(s).
8351 - Log when we cleanup an intro point from a service so we know when
8352 and for what reason it happened. Closes ticket 23604.
8354 o Minor features (portability):
8355 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
8356 (It doesn't yet work with the sandbox enabled.) Closes
8358 - Check at configure time whether uint8_t is the same type as
8359 unsigned char. Lots of existing code already makes this
8360 assumption, and there could be strict aliasing issues if the
8361 assumption is violated. Closes ticket 22410.
8363 o Minor features (relay):
8364 - When choosing which circuits can be expired as unused, consider
8365 circuits from clients even if those clients used regular CREATE
8366 cells to make them; and do not consider circuits from relays even
8367 if they were made with CREATE_FAST. Part of ticket 22805.
8368 - Reject attempts to use relative file paths when RunAsDaemon is
8369 set. Previously, Tor would accept these, but the directory-
8370 changing step of RunAsDaemon would give strange and/or confusing
8371 results. Closes ticket 22731.
8373 o Minor features (relay statistics):
8374 - Change relay bandwidth reporting stats interval from 4 hours to 24
8375 hours in order to reduce the efficiency of guard discovery
8376 attacks. Fixes ticket 23856.
8378 o Minor features (reverted deprecations):
8379 - The ClientDNSRejectInternalAddresses flag can once again be set in
8380 non-testing Tor networks, so long as they do not use the default
8381 directory authorities. This change also removes the deprecation of
8382 this flag from 0.2.9.2-alpha. Closes ticket 21031.
8384 o Minor features (robustness):
8385 - Change several fatal assertions when flushing buffers into non-
8386 fatal assertions, to prevent any recurrence of 23690.
8388 o Minor features (startup, safety):
8389 - When configured to write a PID file, Tor now exits if it is unable
8390 to do so. Previously, it would warn and continue. Closes
8393 o Minor features (static analysis):
8394 - The BUG() macro has been changed slightly so that Coverity no
8395 longer complains about dead code if the bug is impossible. Closes
8398 o Minor features (testing):
8399 - Our fuzzing tests now test the encrypted portions of v3 onion
8400 service descriptors. Implements more of 21509.
8401 - Add a unit test to make sure that our own generated platform
8402 string will be accepted by directory authorities. Closes
8404 - The default chutney network tests now include tests for the v3
8405 onion service design. Make sure you have the latest version of
8406 chutney if you want to run these. Closes ticket 22437.
8407 - Add a unit test to verify that we can parse a hardcoded v2 onion
8408 service descriptor. Closes ticket 15554.
8410 o Minor bugfixes (address selection):
8411 - When the fascist_firewall_choose_address_ functions don't find a
8412 reachable address, set the returned address to the null address
8413 and port. This is a precautionary measure, because some callers do
8414 not check the return value. Fixes bug 24736; bugfix
8417 o Minor bugfixes (bootstrapping):
8418 - When warning about state file clock skew, report the correct
8419 direction for the detected skew. Fixes bug 23606; bugfix
8422 o Minor bugfixes (bridge clients, bootstrap):
8423 - Retry directory downloads when we get our first bridge descriptor
8424 during bootstrap or while reconnecting to the network. Keep
8425 retrying every time we get a bridge descriptor, until we have a
8426 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
8427 - Stop delaying bridge descriptor fetches when we have cached bridge
8428 descriptors. Instead, only delay bridge descriptor fetches when we
8429 have at least one reachable bridge. Fixes part of bug 24367;
8430 bugfix on 0.2.0.3-alpha.
8431 - Stop delaying directory fetches when we have cached bridge
8432 descriptors. Instead, only delay bridge descriptor fetches when
8433 all our bridges are definitely unreachable. Fixes part of bug
8434 24367; bugfix on 0.2.0.3-alpha.
8436 o Minor bugfixes (bridge):
8437 - Overwrite the bridge address earlier in the process of retrieving
8438 its descriptor, to make sure we reach it on the configured
8439 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
8441 o Minor bugfixes (build, compilation):
8442 - Fix a compilation warning when building with zstd support on
8443 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
8444 and fixed by Andreas Stieger.
8445 - When searching for OpenSSL, don't accept any OpenSSL library that
8446 lacks TLSv1_1_method(): Tor doesn't build with those versions.
8447 Additionally, look in /usr/local/opt/openssl, if it's present.
8448 These changes together repair the default build on OSX systems
8449 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
8450 - Fix a signed/unsigned comparison warning introduced by our fix to
8451 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
8452 - Fix a memory leak warning in one of the libevent-related
8453 configuration tests that could occur when manually specifying
8454 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
8455 Found and patched by Alex Xu.
8456 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
8457 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
8459 o Minor bugfixes (certificate handling):
8460 - Fix a time handling bug in Tor certificates set to expire after
8461 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
8462 Coverity as CID 1415728.
8464 o Minor bugfixes (client):
8465 - By default, do not enable storage of client-side DNS values. These
8466 values were unused by default previously, but they should not have
8467 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
8469 o Minor bugfixes (client, usability):
8470 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
8471 SOCKS4a requests that contain IP address strings, even when
8472 SafeSocks in enabled, as this prevents user from connecting to
8473 known IP addresses without relying on DNS for resolving. SafeSocks
8474 still rejects SOCKS connections that connect to IP addresses when
8475 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
8476 bugfix on Tor 0.2.6.2-alpha.
8478 o Minor bugfixes (code correctness):
8479 - Call htons() in extend_cell_format() for encoding a 16-bit value.
8480 Previously we used ntohs(), which happens to behave the same on
8481 all the platforms we support, but which isn't really correct.
8482 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
8483 - For defense-in-depth, make the controller's write_escaped_data()
8484 function robust to extremely long inputs. Fixes bug 19281; bugfix
8485 on 0.1.1.1-alpha. Reported by Guido Vranken.
8486 - Fix several places in our codebase where a C compiler would be
8487 likely to eliminate a check, based on assuming that undefined
8488 behavior had not happened elsewhere in the code. These cases are
8489 usually a sign of redundant checking or dubious arithmetic. Found
8490 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
8491 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
8494 o Minor bugfixes (compression):
8495 - Handle a pathological case when decompressing Zstandard data when
8496 the output buffer size is zero. Fixes bug 23551; bugfix
8499 o Minor bugfixes (consensus expiry):
8500 - Check for adequate directory information correctly. Previously, Tor
8501 would reconsider whether it had sufficient directory information
8502 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
8504 o Minor bugfixes (control port, linux seccomp2 sandbox):
8505 - Avoid a crash when attempting to use the seccomp2 sandbox together
8506 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
8509 o Minor bugfixes (control port, onion services):
8510 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
8511 HS_DESC event when a service is not able to upload a descriptor.
8512 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
8514 o Minor bugfixes (directory cache):
8515 - Recover better from empty or corrupt files in the consensus cache
8516 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
8517 - When a consensus diff calculation is only partially successful,
8518 only record the successful parts as having succeeded. Partial
8519 success can happen if (for example) one compression method fails
8520 but the others succeed. Previously we misrecorded all the
8521 calculations as having succeeded, which would later cause a
8522 nonfatal assertion failure. Fixes bug 24086; bugfix
8525 o Minor bugfixes (directory client):
8526 - On failure to download directory information, delay retry attempts
8527 by a random amount based on the "decorrelated jitter" algorithm.
8528 Our previous delay algorithm tended to produce extra-long delays
8529 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
8531 o Minor bugfixes (directory protocol):
8532 - Directory servers now include a "Date:" http header for response
8533 codes other than 200. Clients starting with a skewed clock and a
8534 recent consensus were getting "304 Not modified" responses from
8535 directory authorities, so without the Date header, the client
8536 would never hear about a wrong clock. Fixes bug 23499; bugfix
8538 - Make clients wait for 6 seconds before trying to download a
8539 consensus from an authority. Fixes bug 17750; bugfix
8542 o Minor bugfixes (documentation):
8543 - Document better how to read gcov, and what our gcov postprocessing
8544 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
8545 - Fix manpage to not refer to the obsolete (and misspelled)
8546 UseEntryGuardsAsDirectoryGuards parameter in the description of
8547 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
8549 o Minor bugfixes (DoS-resistance):
8550 - If future code asks if there are any running bridges, without
8551 checking if bridges are enabled, log a BUG warning rather than
8552 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
8554 o Minor bugfixes (entry guards):
8555 - Tor now updates its guard state when it reads a consensus
8556 regardless of whether it's missing descriptors. That makes tor use
8557 its primary guards to fetch descriptors in some edge cases where
8558 it would previously have used fallback directories. Fixes bug
8559 23862; bugfix on 0.3.0.1-alpha.
8561 o Minor bugfixes (format strictness):
8562 - Restrict several data formats to decimal. Previously, the
8563 BuildTimeHistogram entries in the state file, the "bw=" entries in
8564 the bandwidth authority file, and the process IDs passed to the
8565 __OwningControllerProcess option could all be specified in hex or
8566 octal as well as in decimal. This was not an intentional feature.
8567 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
8570 o Minor bugfixes (heartbeat):
8571 - If we fail to write a heartbeat message, schedule a retry for the
8572 minimum heartbeat interval number of seconds in the future. Fixes
8573 bug 19476; bugfix on 0.2.3.1-alpha.
8575 o Minor bugfixes (logging):
8576 - Suppress a log notice when relay descriptors arrive. We already
8577 have a bootstrap progress for this so no need to log notice
8578 everytime tor receives relay descriptors. Microdescriptors behave
8579 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
8580 - Remove duplicate log messages regarding opening non-local
8581 SocksPorts upon parsing config and opening listeners at startup.
8582 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
8583 - Use a more comprehensible log message when telling the user
8584 they've excluded every running exit node. Fixes bug 7890; bugfix
8586 - When logging the number of descriptors we intend to download per
8587 directory request, do not log a number higher than then the number
8588 of descriptors we're fetching in total. Fixes bug 19648; bugfix
8590 - When warning about a directory owned by the wrong user, log the
8591 actual name of the user owning the directory. Previously, we'd log
8592 the name of the process owner twice. Fixes bug 23487; bugfix
8594 - Fix some messages on unexpected errors from the seccomp2 library.
8595 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
8596 - The tor specification says hop counts are 1-based, so fix two log
8597 messages that mistakenly logged 0-based hop counts. Fixes bug
8598 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
8599 Credit to Xiaofan Li for reporting this issue.
8601 o Minor bugfixes (logging, relay shutdown, annoyance):
8602 - When a circuit is marked for close, do not attempt to package any
8603 cells for channels on that circuit. Previously, we would detect
8604 this condition lower in the call stack, when we noticed that the
8605 circuit had no attached channel, and log an annoying message.
8606 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
8608 o Minor bugfixes (memory safety, defensive programming):
8609 - Clear the target address when node_get_prim_orport() returns
8610 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
8612 o Minor bugfixes (memory usage):
8613 - When queuing DESTROY cells on a channel, only queue the circuit-id
8614 and reason fields: not the entire 514-byte cell. This fix should
8615 help mitigate any bugs or attacks that fill up these queues, and
8616 free more RAM for other uses. Fixes bug 24666; bugfix
8619 o Minor bugfixes (network layer):
8620 - When closing a connection via close_connection_immediately(), we
8621 mark it as "not blocked on bandwidth", to prevent later calls from
8622 trying to unblock it, and give it permission to read. This fixes a
8623 backtrace warning that can happen on relays under various
8624 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
8626 o Minor bugfixes (onion services):
8627 - The introduction circuit was being timed out too quickly while
8628 waiting for the rendezvous circuit to complete. Keep the intro
8629 circuit around longer instead of timing out and reopening new ones
8630 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
8631 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
8632 so it matches dir-spec.txt. Fixes bug 24262; bugfix
8634 - When handling multiple SOCKS request for the same .onion address,
8635 only fetch the service descriptor once.
8636 - Avoid a possible double close of a circuit by the intro point on
8637 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
8638 bugfix on 0.3.0.1-alpha.
8639 - When reloading configured onion services, copy all information
8640 from the old service object. Previously, some data was omitted,
8641 causing delays in descriptor upload, and other bugs. Fixes bug
8642 23790; bugfix on 0.2.1.9-alpha.
8644 o Minor bugfixes (path selection):
8645 - When selecting relays by bandwidth, avoid a rounding error that
8646 could sometimes cause load to be imbalanced incorrectly.
8647 Previously, we would always round upwards; now, we round towards
8648 the nearest integer. This had the biggest effect when a relay's
8649 weight adjustments should have given it weight 0, but it got
8650 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
8651 - When calculating the fraction of nodes that have descriptors, and
8652 all nodes in the network have zero bandwidths, count the number of
8653 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
8654 - Actually log the total bandwidth in compute_weighted_bandwidths().
8655 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
8657 o Minor bugfixes (portability):
8658 - Stop using the PATH_MAX variable, which is not defined on GNU
8659 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
8660 - Fix a bug in the bit-counting parts of our timing-wheel code on
8661 MSVC. (Note that MSVC is still not a supported build platform, due
8662 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
8665 o Minor bugfixes (relay):
8666 - When uploading our descriptor for the first time after startup,
8667 report the reason for uploading as "Tor just started" rather than
8668 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
8669 - Avoid unnecessary calls to directory_fetches_from_authorities() on
8670 relays, to prevent spurious address resolutions and descriptor
8671 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
8672 bugfix on in 0.2.8.1-alpha.
8673 - Avoid a crash when transitioning from client mode to bridge mode.
8674 Previously, we would launch the worker threads whenever our
8675 "public server" mode changed, but not when our "server" mode
8676 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
8678 o Minor bugfixes (testing):
8679 - Fix a spurious fuzzing-only use of an uninitialized value. Found
8680 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
8681 - Test that IPv6-only clients can use microdescriptors when running
8682 "make test-network-all". Requires chutney master 61c28b9 or later.
8683 Closes ticket 24109.
8684 - Prevent scripts/test/coverage from attempting to move gcov output
8685 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
8686 - Capture and detect several "Result does not fit" warnings in unit
8687 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
8689 - Fix additional channelpadding unit test failures by using mocked
8690 time instead of actual time for all tests. Fixes bug 23608; bugfix
8692 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
8693 to correctly handle cases where a caller gives it an RSA key of
8694 under 160 bits. (This is not actually a bug in Tor itself, but
8695 rather in our fuzzing code.) Fixes bug 24247; bugfix on
8696 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
8697 - Fix a broken unit test for the OutboundAddress option: the parsing
8698 function was never returning an error on failure. Fixes bug 23366;
8699 bugfix on 0.3.0.3-alpha.
8700 - Fix a signed-integer overflow in the unit tests for
8701 dir/download_status_random_backoff, which was untriggered until we
8702 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
8704 o Minor bugfixes (usability, control port):
8705 - Stop making an unnecessary routerlist check in NETINFO clock skew
8706 detection; this was preventing clients from reporting NETINFO clock
8707 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
8709 o Code simplification and refactoring:
8710 - Remove various ways of testing circuits and connections for
8711 "clientness"; instead, favor channel_is_client(). Part of
8713 - Extract the code for handling newly-open channels into a separate
8714 function from the general code to handle channel state
8715 transitions. This change simplifies our callgraph, reducing the
8716 size of the largest strongly connected component by roughly a
8717 factor of two. Closes ticket 22608.
8718 - Remove dead code for largely unused statistics on the number of
8719 times we've attempted various public key operations. Fixes bug
8720 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
8721 - Remove several now-obsolete functions for asking about old
8722 variants directory authority status. Closes ticket 22311; patch
8724 - Remove some of the code that once supported "Named" and "Unnamed"
8725 routers. Authorities no longer vote for these flags. Closes
8727 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
8728 and old hidden services, to indicate that they aren't suitable for
8729 new protocols or formats. Closes ticket 23026.
8730 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
8731 22521. Patch from Neel Chauhan.
8732 - Split the enormous circuit_send_next_onion_skin() function into
8733 multiple subfunctions. Closes ticket 22804.
8734 - Split the portions of the buffer.c module that handle particular
8735 protocols into separate modules. Part of ticket 23149.
8736 - Use our test macros more consistently, to produce more useful
8737 error messages when our unit tests fail. Add coccinelle patches to
8738 allow us to re-check for test macro uses. Closes ticket 22497.
8740 o Deprecated features:
8741 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
8742 now deprecated; they do not apply to relays, and they have had no
8743 effect on clients since 0.2.8.x. Closes ticket 19704.
8744 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
8745 only applies to direct unencrypted HTTP connections to your
8746 directory server, which your Tor probably isn't using. Closes
8750 - Add notes in man page regarding OS support for the various
8751 scheduler types. Attempt to use less jargon in the scheduler
8752 section. Closes ticket 24254.
8753 - Clarify that the Address option is entirely about setting an
8754 advertised IPv4 address. Closes ticket 18891.
8755 - Clarify the manpage's use of the term "address" to clarify what
8756 kind of address is intended. Closes ticket 21405.
8757 - Document that onion service subdomains are allowed, and ignored.
8758 Closes ticket 18736.
8759 - Clarify in the manual that "Sandbox 1" is only supported on Linux
8760 kernels. Closes ticket 22677.
8761 - Document all values of PublishServerDescriptor in the manpage.
8762 Closes ticket 15645.
8763 - Improve the documentation for the directory port part of the
8764 DirAuthority line. Closes ticket 20152.
8765 - Restore documentation for the authorities' "approved-routers"
8766 file. Closes ticket 21148.
8769 - The AllowDotExit option has been removed as unsafe. It has been
8770 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
8771 - The ClientDNSRejectInternalAddresses flag can no longer be set on
8772 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
8773 Closes ticket 21031.
8774 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
8775 nobody was using it any longer. Closes ticket 22377.
8778 Changes in version 0.3.1.9 - 2017-12-01:
8779 Tor 0.3.1.9 backports important security and stability fixes from the
8780 0.3.2 development series. All Tor users should upgrade to this
8781 release, or to another of the releases coming out today.
8783 o Major bugfixes (security, backport from 0.3.2.6-alpha):
8784 - Fix a denial of service bug where an attacker could use a
8785 malformed directory object to cause a Tor instance to pause while
8786 OpenSSL would try to read a passphrase from the terminal. (Tor
8787 instances run without a terminal, which is the case for most Tor
8788 packages, are not impacted.) Fixes bug 24246; bugfix on every
8789 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
8790 Found by OSS-Fuzz as testcase 6360145429790720.
8791 - Fix a denial of service issue where an attacker could crash a
8792 directory authority using a malformed router descriptor. Fixes bug
8793 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
8795 - When checking for replays in the INTRODUCE1 cell data for a
8796 (legacy) onion service, correctly detect replays in the RSA-
8797 encrypted part of the cell. We were previously checking for
8798 replays on the entire cell, but those can be circumvented due to
8799 the malleability of Tor's legacy hybrid encryption. This fix helps
8800 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
8801 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
8804 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
8805 - Fix a use-after-free error that could crash v2 Tor onion services
8806 when they failed to open circuits while expiring introduction
8807 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
8808 also tracked as TROVE-2017-013 and CVE-2017-8823.
8810 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
8811 - When running as a relay, make sure that we never build a path
8812 through ourselves, even in the case where we have somehow lost the
8813 version of our descriptor appearing in the consensus. Fixes part
8814 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
8815 as TROVE-2017-012 and CVE-2017-8822.
8816 - When running as a relay, make sure that we never choose ourselves
8817 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
8818 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
8820 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
8821 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
8822 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
8823 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
8824 identifying and finding a workaround to this bug and to Moritz,
8825 Arthur Edelstein, and Roger for helping to track it down and
8828 o Minor features (bridge):
8829 - Bridges now include notice in their descriptors that they are
8830 bridges, and notice of their distribution status, based on their
8831 publication settings. Implements ticket 18329. For more fine-
8832 grained control of how a bridge is distributed, upgrade to 0.3.2.x
8835 o Minor features (directory authority, backport from 0.3.2.6-alpha):
8836 - Add an IPv6 address for the "bastet" directory authority. Closes
8839 o Minor features (geoip):
8840 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
8843 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
8844 - Avoid unnecessary calls to directory_fetches_from_authorities() on
8845 relays, to prevent spurious address resolutions and descriptor
8846 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
8847 bugfix on in 0.2.8.1-alpha.
8849 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
8850 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
8851 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
8853 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
8854 - When a circuit is marked for close, do not attempt to package any
8855 cells for channels on that circuit. Previously, we would detect
8856 this condition lower in the call stack, when we noticed that the
8857 circuit had no attached channel, and log an annoying message.
8858 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
8860 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
8861 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
8862 so it matches dir-spec.txt. Fixes bug 24262; bugfix
8865 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
8866 - Avoid a crash when transitioning from client mode to bridge mode.
8867 Previously, we would launch the worker threads whenever our
8868 "public server" mode changed, but not when our "server" mode
8869 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
8872 Changes in version 0.3.0.13 - 2017-12-01
8873 Tor 0.3.0.13 backports important security and stability bugfixes from
8874 later Tor releases. All Tor users should upgrade to this release, or
8875 to another of the releases coming out today.
8877 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
8878 2018. If you need a release with long-term support, please stick with
8879 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
8881 o Major bugfixes (security, backport from 0.3.2.6-alpha):
8882 - Fix a denial of service bug where an attacker could use a
8883 malformed directory object to cause a Tor instance to pause while
8884 OpenSSL would try to read a passphrase from the terminal. (Tor
8885 instances run without a terminal, which is the case for most Tor
8886 packages, are not impacted.) Fixes bug 24246; bugfix on every
8887 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
8888 Found by OSS-Fuzz as testcase 6360145429790720.
8889 - Fix a denial of service issue where an attacker could crash a
8890 directory authority using a malformed router descriptor. Fixes bug
8891 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
8893 - When checking for replays in the INTRODUCE1 cell data for a
8894 (legacy) onion service, correctly detect replays in the RSA-
8895 encrypted part of the cell. We were previously checking for
8896 replays on the entire cell, but those can be circumvented due to
8897 the malleability of Tor's legacy hybrid encryption. This fix helps
8898 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
8899 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
8902 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
8903 - Fix a use-after-free error that could crash v2 Tor onion services
8904 when they failed to open circuits while expiring introduction
8905 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
8906 also tracked as TROVE-2017-013 and CVE-2017-8823.
8908 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
8909 - When running as a relay, make sure that we never build a path
8910 through ourselves, even in the case where we have somehow lost the
8911 version of our descriptor appearing in the consensus. Fixes part
8912 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
8913 as TROVE-2017-012 and CVE-2017-8822.
8914 - When running as a relay, make sure that we never choose ourselves
8915 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
8916 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
8918 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
8919 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
8920 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
8921 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
8922 identifying and finding a workaround to this bug and to Moritz,
8923 Arthur Edelstein, and Roger for helping to track it down and
8926 o Minor features (security, windows, backport from 0.3.1.1-alpha):
8927 - Enable a couple of pieces of Windows hardening: one
8928 (HeapEnableTerminationOnCorruption) that has been on-by-default
8929 since Windows 8, and unavailable before Windows 7; and one
8930 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
8931 affect us, but shouldn't do any harm. Closes ticket 21953.
8933 o Minor features (bridge, backport from 0.3.1.9):
8934 - Bridges now include notice in their descriptors that they are
8935 bridges, and notice of their distribution status, based on their
8936 publication settings. Implements ticket 18329. For more fine-
8937 grained control of how a bridge is distributed, upgrade to 0.3.2.x
8940 o Minor features (directory authority, backport from 0.3.2.6-alpha):
8941 - Add an IPv6 address for the "bastet" directory authority. Closes
8944 o Minor features (geoip):
8945 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
8948 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
8949 - Avoid unnecessary calls to directory_fetches_from_authorities() on
8950 relays, to prevent spurious address resolutions and descriptor
8951 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
8952 bugfix on in 0.2.8.1-alpha.
8954 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
8955 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
8956 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
8958 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
8959 - When a circuit is marked for close, do not attempt to package any
8960 cells for channels on that circuit. Previously, we would detect
8961 this condition lower in the call stack, when we noticed that the
8962 circuit had no attached channel, and log an annoying message.
8963 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
8965 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
8966 - Avoid a crash when transitioning from client mode to bridge mode.
8967 Previously, we would launch the worker threads whenever our
8968 "public server" mode changed, but not when our "server" mode
8969 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
8971 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
8972 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
8973 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
8976 Changes in version 0.2.9.14 - 2017-12-01
8977 Tor 0.3.0.13 backports important security and stability bugfixes from
8978 later Tor releases. All Tor users should upgrade to this release, or
8979 to another of the releases coming out today.
8981 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
8982 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
8983 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
8984 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
8985 identifying and finding a workaround to this bug and to Moritz,
8986 Arthur Edelstein, and Roger for helping to track it down and
8989 o Major bugfixes (security, backport from 0.3.2.6-alpha):
8990 - Fix a denial of service bug where an attacker could use a
8991 malformed directory object to cause a Tor instance to pause while
8992 OpenSSL would try to read a passphrase from the terminal. (Tor
8993 instances run without a terminal, which is the case for most Tor
8994 packages, are not impacted.) Fixes bug 24246; bugfix on every
8995 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
8996 Found by OSS-Fuzz as testcase 6360145429790720.
8997 - Fix a denial of service issue where an attacker could crash a
8998 directory authority using a malformed router descriptor. Fixes bug
8999 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
9001 - When checking for replays in the INTRODUCE1 cell data for a
9002 (legacy) onion service, correctly detect replays in the RSA-
9003 encrypted part of the cell. We were previously checking for
9004 replays on the entire cell, but those can be circumvented due to
9005 the malleability of Tor's legacy hybrid encryption. This fix helps
9006 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9007 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9010 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
9011 - Fix a use-after-free error that could crash v2 Tor onion services
9012 when they failed to open circuits while expiring introduction
9013 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9014 also tracked as TROVE-2017-013 and CVE-2017-8823.
9016 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9017 - When running as a relay, make sure that we never build a path
9018 through ourselves, even in the case where we have somehow lost the
9019 version of our descriptor appearing in the consensus. Fixes part
9020 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9021 as TROVE-2017-012 and CVE-2017-8822.
9023 o Minor features (bridge, backport from 0.3.1.9):
9024 - Bridges now include notice in their descriptors that they are
9025 bridges, and notice of their distribution status, based on their
9026 publication settings. Implements ticket 18329. For more fine-
9027 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9030 o Minor features (directory authority, backport from 0.3.2.6-alpha):
9031 - Add an IPv6 address for the "bastet" directory authority. Closes
9034 o Minor features (geoip):
9035 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9038 o Minor features (security, windows, backport from 0.3.1.1-alpha):
9039 - Enable a couple of pieces of Windows hardening: one
9040 (HeapEnableTerminationOnCorruption) that has been on-by-default
9041 since Windows 8, and unavailable before Windows 7; and one
9042 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
9043 affect us, but shouldn't do any harm. Closes ticket 21953.
9045 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
9046 - Avoid unnecessary calls to directory_fetches_from_authorities() on
9047 relays, to prevent spurious address resolutions and descriptor
9048 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
9049 bugfix on in 0.2.8.1-alpha.
9051 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
9052 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
9053 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
9055 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
9056 - When a circuit is marked for close, do not attempt to package any
9057 cells for channels on that circuit. Previously, we would detect
9058 this condition lower in the call stack, when we noticed that the
9059 circuit had no attached channel, and log an annoying message.
9060 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
9062 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
9063 - Avoid a crash when transitioning from client mode to bridge mode.
9064 Previously, we would launch the worker threads whenever our
9065 "public server" mode changed, but not when our "server" mode
9066 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
9068 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
9069 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
9070 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
9073 Changes in version 0.2.8.17 - 2017-12-01
9074 Tor 0.2.8.17 backports important security and stability bugfixes from
9075 later Tor releases. All Tor users should upgrade to this release, or
9076 to another of the releases coming out today.
9078 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
9079 2018. If you need a release with long-term support, please upgrade with
9080 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9082 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9083 - Fix a denial of service bug where an attacker could use a
9084 malformed directory object to cause a Tor instance to pause while
9085 OpenSSL would try to read a passphrase from the terminal. (Tor
9086 instances run without a terminal, which is the case for most Tor
9087 packages, are not impacted.) Fixes bug 24246; bugfix on every
9088 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9089 Found by OSS-Fuzz as testcase 6360145429790720.
9090 - When checking for replays in the INTRODUCE1 cell data for a
9091 (legacy) onion service, correctly detect replays in the RSA-
9092 encrypted part of the cell. We were previously checking for
9093 replays on the entire cell, but those can be circumvented due to
9094 the malleability of Tor's legacy hybrid encryption. This fix helps
9095 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9096 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9099 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
9100 - Fix a use-after-free error that could crash v2 Tor onion services
9101 when they failed to open circuits while expiring introduction
9102 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9103 also tracked as TROVE-2017-013 and CVE-2017-8823.
9105 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9106 - When running as a relay, make sure that we never build a path through
9107 ourselves, even in the case where we have somehow lost the version of
9108 our descriptor appearing in the consensus. Fixes part of bug 21534;
9109 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
9112 o Minor features (bridge, backport from 0.3.1.9):
9113 - Bridges now include notice in their descriptors that they are
9114 bridges, and notice of their distribution status, based on their
9115 publication settings. Implements ticket 18329. For more fine-
9116 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9119 o Minor features (directory authority, backport from 0.3.2.6-alpha):
9120 - Add an IPv6 address for the "bastet" directory authority. Closes
9123 o Minor features (geoip):
9124 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9127 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
9128 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
9129 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
9132 Changes in version 0.2.5.16 - 2017-12-01
9133 Tor 0.2.5.13 backports important security and stability bugfixes from
9134 later Tor releases. All Tor users should upgrade to this release, or
9135 to another of the releases coming out today.
9137 Note: the Tor 0.2.5 series will no longer be supported after 1 May
9138 2018. If you need a release with long-term support, please upgrade to
9139 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9141 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9142 - Fix a denial of service bug where an attacker could use a
9143 malformed directory object to cause a Tor instance to pause while
9144 OpenSSL would try to read a passphrase from the terminal. (Tor
9145 instances run without a terminal, which is the case for most Tor
9146 packages, are not impacted.) Fixes bug 24246; bugfix on every
9147 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9148 Found by OSS-Fuzz as testcase 6360145429790720.
9149 - When checking for replays in the INTRODUCE1 cell data for a
9150 (legacy) onion service, correctly detect replays in the RSA-
9151 encrypted part of the cell. We were previously checking for
9152 replays on the entire cell, but those can be circumvented due to
9153 the malleability of Tor's legacy hybrid encryption. This fix helps
9154 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9155 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9158 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9159 - When running as a relay, make sure that we never build a path
9160 through ourselves, even in the case where we have somehow lost the
9161 version of our descriptor appearing in the consensus. Fixes part
9162 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9163 as TROVE-2017-012 and CVE-2017-8822.
9165 o Minor features (bridge, backport from 0.3.1.9):
9166 - Bridges now include notice in their descriptors that they are
9167 bridges, and notice of their distribution status, based on their
9168 publication settings. Implements ticket 18329. For more fine-
9169 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9172 o Minor features (geoip):
9173 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9177 Changes in version 0.2.5.15 - 2017-10-25
9178 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
9179 series. It also adds a new directory authority, Bastet.
9181 Note: the Tor 0.2.5 series will no longer be supported after 1 May
9182 2018. If you need a release with long-term support, please upgrade to
9183 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9185 o Directory authority changes:
9186 - Add "Bastet" as a ninth directory authority to the default list.
9187 Closes ticket 23910.
9188 - The directory authority "Longclaw" has changed its IP address.
9189 Closes ticket 23592.
9191 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
9192 - Avoid an assertion failure bug affecting our implementation of
9193 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
9194 handling of "0xx" differs from what we had expected. Fixes bug
9195 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
9197 o Minor features (geoip):
9198 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9201 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
9202 - Fix a memset() off the end of an array when packing cells. This
9203 bug should be harmless in practice, since the corrupted bytes are
9204 still in the same structure, and are always padding bytes,
9205 ignored, or immediately overwritten, depending on compiler
9206 behavior. Nevertheless, because the memset()'s purpose is to make
9207 sure that any other cell-handling bugs can't expose bytes to the
9208 network, we need to fix it. Fixes bug 22737; bugfix on
9209 0.2.4.11-alpha. Fixes CID 1401591.
9211 o Build features (backport from 0.3.1.5-alpha):
9212 - Tor's repository now includes a Travis Continuous Integration (CI)
9213 configuration file (.travis.yml). This is meant to help new
9214 developers and contributors who fork Tor to a Github repository be
9215 better able to test their changes, and understand what we expect
9216 to pass. To use this new build feature, you must fork Tor to your
9217 Github account, then go into the "Integrations" menu in the
9218 repository settings for your fork and enable Travis, then push
9219 your changes. Closes ticket 22636.
9222 Changes in version 0.2.8.16 - 2017-10-25
9223 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
9224 series, including a bugfix for a crash issue that had affected relays
9225 under memory pressure. It also adds a new directory authority, Bastet.
9227 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
9228 2018. If you need a release with long-term support, please stick with
9229 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9231 o Directory authority changes:
9232 - Add "Bastet" as a ninth directory authority to the default list.
9233 Closes ticket 23910.
9234 - The directory authority "Longclaw" has changed its IP address.
9235 Closes ticket 23592.
9237 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
9238 - Fix a timing-based assertion failure that could occur when the
9239 circuit out-of-memory handler freed a connection's output buffer.
9240 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
9242 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
9243 - Remove longclaw's IPv6 address, as it will soon change. Authority
9244 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
9245 3/8 directory authorities with IPv6 addresses, but there are also
9246 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
9248 o Minor features (geoip):
9249 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9253 Changes in version 0.2.9.13 - 2017-10-25
9254 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
9255 series, including a bugfix for a crash issue that had affected relays
9256 under memory pressure. It also adds a new directory authority, Bastet.
9258 o Directory authority changes:
9259 - Add "Bastet" as a ninth directory authority to the default list.
9260 Closes ticket 23910.
9261 - The directory authority "Longclaw" has changed its IP address.
9262 Closes ticket 23592.
9264 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
9265 - Fix a timing-based assertion failure that could occur when the
9266 circuit out-of-memory handler freed a connection's output buffer.
9267 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
9269 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
9270 - Remove longclaw's IPv6 address, as it will soon change. Authority
9271 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
9272 3/8 directory authorities with IPv6 addresses, but there are also
9273 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
9275 o Minor features (geoip):
9276 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9279 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
9280 - When a directory authority rejects a descriptor or extrainfo with
9281 a given digest, mark that digest as undownloadable, so that we do
9282 not attempt to download it again over and over. We previously
9283 tried to avoid downloading such descriptors by other means, but we
9284 didn't notice if we accidentally downloaded one anyway. This
9285 behavior became problematic in 0.2.7.2-alpha, when authorities
9286 began pinning Ed25519 keys. Fixes bug 22349; bugfix
9289 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
9290 - Clear the address when node_get_prim_orport() returns early.
9291 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
9293 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
9294 - When running as a Windows service, set the ID of the main thread
9295 correctly. Failure to do so made us fail to send log messages to
9296 the controller in 0.2.1.16-rc, slowed down controller event
9297 delivery in 0.2.7.3-rc and later, and crash with an assertion
9298 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
9299 Patch and diagnosis from "Vort".
9302 Changes in version 0.3.0.12 - 2017-10-25
9303 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
9304 series, including a bugfix for a crash issue that had affected relays
9305 under memory pressure. It also adds a new directory authority, Bastet.
9307 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
9308 2018. If you need a release with long-term support, please stick with
9309 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9311 o Directory authority changes:
9312 - Add "Bastet" as a ninth directory authority to the default list.
9313 Closes ticket 23910.
9314 - The directory authority "Longclaw" has changed its IP address.
9315 Closes ticket 23592.
9317 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
9318 - Fix a timing-based assertion failure that could occur when the
9319 circuit out-of-memory handler freed a connection's output buffer.
9320 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
9322 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
9323 - Remove longclaw's IPv6 address, as it will soon change. Authority
9324 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
9325 3/8 directory authorities with IPv6 addresses, but there are also
9326 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
9328 o Minor features (geoip):
9329 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9332 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
9333 - When a directory authority rejects a descriptor or extrainfo with
9334 a given digest, mark that digest as undownloadable, so that we do
9335 not attempt to download it again over and over. We previously
9336 tried to avoid downloading such descriptors by other means, but we
9337 didn't notice if we accidentally downloaded one anyway. This
9338 behavior became problematic in 0.2.7.2-alpha, when authorities
9339 began pinning Ed25519 keys. Fixes bug 22349; bugfix
9342 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
9343 - Avoid a possible double close of a circuit by the intro point on
9344 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
9345 bugfix on 0.3.0.1-alpha.
9347 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
9348 - Clear the address when node_get_prim_orport() returns early.
9349 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
9351 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
9352 - When running as a Windows service, set the ID of the main thread
9353 correctly. Failure to do so made us fail to send log messages to
9354 the controller in 0.2.1.16-rc, slowed down controller event
9355 delivery in 0.2.7.3-rc and later, and crash with an assertion
9356 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
9357 Patch and diagnosis from "Vort".
9360 Changes in version 0.3.1.8 - 2017-10-25
9361 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
9362 It includes several bugfixes, including a bugfix for a crash issue
9363 that had affected relays under memory pressure. It also adds
9364 a new directory authority, Bastet.
9366 o Directory authority changes:
9367 - Add "Bastet" as a ninth directory authority to the default list.
9368 Closes ticket 23910.
9369 - The directory authority "Longclaw" has changed its IP address.
9370 Closes ticket 23592.
9372 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
9373 - Fix a timing-based assertion failure that could occur when the
9374 circuit out-of-memory handler freed a connection's output buffer.
9375 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
9377 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
9378 - Remove longclaw's IPv6 address, as it will soon change. Authority
9379 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
9380 3/8 directory authorities with IPv6 addresses, but there are also
9381 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
9383 o Minor features (geoip):
9384 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9387 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
9388 - Fix a compilation warning when building with zstd support on
9389 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
9390 and fixed by Andreas Stieger.
9392 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
9393 - Handle a pathological case when decompressing Zstandard data when
9394 the output buffer size is zero. Fixes bug 23551; bugfix
9397 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
9398 - Remove the length limit on HTTP status lines that authorities can
9399 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
9401 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
9402 - Avoid a possible double close of a circuit by the intro point on
9403 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
9404 bugfix on 0.3.0.1-alpha.
9406 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
9407 - Clear the address when node_get_prim_orport() returns early.
9408 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
9410 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
9411 - Fix additional channelpadding unit test failures by using mocked
9412 time instead of actual time for all tests. Fixes bug 23608; bugfix
9416 Changes in version 0.2.8.15 - 2017-09-18
9417 Tor 0.2.8.15 backports a collection of bugfixes from later
9420 Most significantly, it includes a fix for TROVE-2017-008, a
9421 security bug that affects hidden services running with the
9422 SafeLogging option disabled. For more information, see
9423 https://trac.torproject.org/projects/tor/ticket/23490
9425 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
9426 2018. We suggest that you upgrade to the latest stable release if
9427 possible. If you can't, we recommend that you upgrade at least to
9428 0.2.9, which will be supported until 2020.
9430 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
9431 - Avoid an assertion failure bug affecting our implementation of
9432 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
9433 handling of "0xx" differs from what we had expected. Fixes bug
9434 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
9437 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
9440 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
9441 - Backport a fix for an "unused variable" warning that appeared
9442 in some versions of mingw. Fixes bug 22838; bugfix on
9445 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
9446 - Fix a memset() off the end of an array when packing cells. This
9447 bug should be harmless in practice, since the corrupted bytes are
9448 still in the same structure, and are always padding bytes,
9449 ignored, or immediately overwritten, depending on compiler
9450 behavior. Nevertheless, because the memset()'s purpose is to make
9451 sure that any other cell-handling bugs can't expose bytes to the
9452 network, we need to fix it. Fixes bug 22737; bugfix on
9453 0.2.4.11-alpha. Fixes CID 1401591.
9455 o Build features (backport from 0.3.1.5-alpha):
9456 - Tor's repository now includes a Travis Continuous Integration (CI)
9457 configuration file (.travis.yml). This is meant to help new
9458 developers and contributors who fork Tor to a Github repository be
9459 better able to test their changes, and understand what we expect
9460 to pass. To use this new build feature, you must fork Tor to your
9461 Github account, then go into the "Integrations" menu in the
9462 repository settings for your fork and enable Travis, then push
9463 your changes. Closes ticket 22636.
9466 Changes in version 0.2.9.12 - 2017-09-18
9467 Tor 0.2.9.12 backports a collection of bugfixes from later
9470 Most significantly, it includes a fix for TROVE-2017-008, a
9471 security bug that affects hidden services running with the
9472 SafeLogging option disabled. For more information, see
9473 https://trac.torproject.org/projects/tor/ticket/23490
9475 o Major features (security, backport from 0.3.0.2-alpha):
9476 - Change the algorithm used to decide DNS TTLs on client and server
9477 side, to better resist DNS-based correlation attacks like the
9478 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
9479 Feamster. Now relays only return one of two possible DNS TTL
9480 values, and clients are willing to believe DNS TTL values up to 3
9481 hours long. Closes ticket 19769.
9483 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
9484 - Fix a rare crash when sending a begin cell on a circuit whose
9485 linked directory connection had already been closed. Fixes bug
9486 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
9488 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
9489 - Fix a bug that prevented exit nodes from caching DNS records for
9490 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
9492 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
9493 - Fix a typo that had prevented TPROXY-based transparent proxying
9494 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
9495 Patch from "d4fq0fQAgoJ".
9497 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
9498 - Avoid an assertion failure bug affecting our implementation of
9499 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
9500 handling of "0xx" differs from what we had expected. Fixes bug
9501 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
9503 o Minor features (code style, backport from 0.3.1.3-alpha):
9504 - Add "Falls through" comments to our codebase, in order to silence
9505 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
9506 Stieger. Closes ticket 22446.
9508 o Minor features (geoip):
9509 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
9512 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
9513 - Roll over monthly accounting at the configured hour and minute,
9514 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
9515 Found by Andrey Karpov with PVS-Studio.
9517 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
9518 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
9519 bugfix on 0.2.8.1-alpha.
9520 - Fix warnings when building with libscrypt and openssl scrypt support
9521 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
9522 - When building with certain versions the mingw C header files, avoid
9523 float-conversion warnings when calling the C functions isfinite(),
9524 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
9526 o Minor bugfixes (compilation, backport from 0.3.1.7):
9527 - Avoid compiler warnings in the unit tests for running tor_sscanf()
9528 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
9530 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
9531 - Backport a fix for an "unused variable" warning that appeared
9532 in some versions of mingw. Fixes bug 22838; bugfix on
9535 o Minor bugfixes (controller, backport from 0.3.1.7):
9536 - Do not crash when receiving a HSPOST command with an empty body.
9537 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
9538 - Do not crash when receiving a POSTDESCRIPTOR command with an
9539 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
9541 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
9542 - Avoid Coverity build warnings related to our BUG() macro. By
9543 default, Coverity treats BUG() as the Linux kernel does: an
9544 instant abort(). We need to override that so our BUG() macro
9545 doesn't prevent Coverity from analyzing functions that use it.
9546 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
9548 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
9549 - Fix a memset() off the end of an array when packing cells. This
9550 bug should be harmless in practice, since the corrupted bytes are
9551 still in the same structure, and are always padding bytes,
9552 ignored, or immediately overwritten, depending on compiler
9553 behavior. Nevertheless, because the memset()'s purpose is to make
9554 sure that any other cell-handling bugs can't expose bytes to the
9555 network, we need to fix it. Fixes bug 22737; bugfix on
9556 0.2.4.11-alpha. Fixes CID 1401591.
9558 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
9559 - When setting the maximum number of connections allowed by the OS,
9560 always allow some extra file descriptors for other files. Fixes
9561 bug 22797; bugfix on 0.2.0.10-alpha.
9563 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
9564 - Avoid a sandbox failure when trying to re-bind to a socket and
9565 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
9567 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
9568 - Permit the fchmod system call, to avoid crashing on startup when
9569 starting with the seccomp2 sandbox and an unexpected set of
9570 permissions on the data directory or its contents. Fixes bug
9571 22516; bugfix on 0.2.5.4-alpha.
9573 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
9574 - Avoid a double-marked-circuit warning that could happen when we
9575 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
9578 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
9579 - Reject version numbers with non-numeric prefixes (such as +, -, or
9580 whitespace). Disallowing whitespace prevents differential version
9581 parsing between POSIX-based and Windows platforms. Fixes bug 21507
9582 and part of 21508; bugfix on 0.0.8pre1.
9584 o Build features (backport from 0.3.1.5-alpha):
9585 - Tor's repository now includes a Travis Continuous Integration (CI)
9586 configuration file (.travis.yml). This is meant to help new
9587 developers and contributors who fork Tor to a Github repository be
9588 better able to test their changes, and understand what we expect
9589 to pass. To use this new build feature, you must fork Tor to your
9590 Github account, then go into the "Integrations" menu in the
9591 repository settings for your fork and enable Travis, then push
9592 your changes. Closes ticket 22636.
9595 Changes in version 0.3.0.11 - 2017-09-18
9596 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
9599 Most significantly, it includes a fix for TROVE-2017-008, a
9600 security bug that affects hidden services running with the
9601 SafeLogging option disabled. For more information, see
9602 https://trac.torproject.org/projects/tor/ticket/23490
9604 o Minor features (code style, backport from 0.3.1.7):
9605 - Add "Falls through" comments to our codebase, in order to silence
9606 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
9607 Stieger. Closes ticket 22446.
9610 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
9613 o Minor bugfixes (compilation, backport from 0.3.1.7):
9614 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
9615 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
9617 o Minor bugfixes (controller, backport from 0.3.1.7):
9618 - Do not crash when receiving a HSPOST command with an empty body.
9619 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
9620 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
9621 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
9623 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
9624 - When setting the maximum number of connections allowed by the OS,
9625 always allow some extra file descriptors for other files. Fixes
9626 bug 22797; bugfix on 0.2.0.10-alpha.
9628 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
9629 - Remove a forgotten debugging message when an introduction point
9630 successfully establishes a hidden service prop224 circuit with
9632 - Change three other log_warn() for an introduction point to
9633 protocol warnings, because they can be failure from the network
9634 and are not relevant to the operator. Fixes bug 23078; bugfix on
9635 0.3.0.1-alpha and 0.3.0.2-alpha.
9638 Changes in version 0.3.1.7 - 2017-09-18
9639 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
9641 With the 0.3.1 series, Tor now serves and downloads directory
9642 information in more compact formats, to save on bandwidth overhead. It
9643 also contains a new padding system to resist netflow-based traffic
9644 analysis, and experimental support for building parts of Tor in Rust
9645 (though no parts of Tor are in Rust yet). There are also numerous
9646 small features, bugfixes on earlier release series, and groundwork for
9647 the hidden services revamp of 0.3.2.
9649 This release also includes a fix for TROVE-2017-008, a security bug
9650 that affects hidden services running with the SafeLogging option
9651 disabled. For more information, see
9652 https://trac.torproject.org/projects/tor/ticket/23490
9654 Per our stable release policy, we plan to support each stable release
9655 series for at least the next nine months, or for three months after
9656 the first stable release of the next series: whichever is longer. If
9657 you need a release with long-term support, we recommend that you stay
9658 with the 0.2.9 series.
9660 Below is a list of the changes since 0.3.0. For a list of all
9661 changes since 0.3.1.6-rc, see the ChangeLog file.
9664 - To build with zstd and lzma support, Tor now requires the
9665 pkg-config tool at build time.
9667 o Major bugfixes (security, hidden services, loggging):
9668 - Fix a bug where we could log uninitialized stack when a certain
9669 hidden service error occurred while SafeLogging was disabled.
9670 Fixes bug #23490; bugfix on 0.2.7.2-alpha.
9671 This is also tracked as TROVE-2017-008 and CVE-2017-0380.
9673 o Major features (build system, continuous integration):
9674 - Tor's repository now includes a Travis Continuous Integration (CI)
9675 configuration file (.travis.yml). This is meant to help new
9676 developers and contributors who fork Tor to a Github repository be
9677 better able to test their changes, and understand what we expect
9678 to pass. To use this new build feature, you must fork Tor to your
9679 Github account, then go into the "Integrations" menu in the
9680 repository settings for your fork and enable Travis, then push
9681 your changes. Closes ticket 22636.
9683 o Major features (directory protocol):
9684 - Tor relays and authorities can now serve clients an abbreviated
9685 version of the consensus document, containing only the changes
9686 since an older consensus document that the client holds. Clients
9687 now request these documents when available. When both client and
9688 server use this new protocol, they will use far less bandwidth (up
9689 to 94% less) to keep the client's consensus up-to-date. Implements
9690 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
9691 - Tor can now compress directory traffic with lzma or with zstd
9692 compression algorithms, which can deliver better bandwidth
9693 performance. Because lzma is computationally expensive, it's only
9694 used for documents that can be compressed once and served many
9695 times. Support for these algorithms requires that tor is built
9696 with the libzstd and/or liblzma libraries available. Implements
9697 proposal 278; closes ticket 21662.
9698 - Relays now perform the more expensive compression operations, and
9699 consensus diff generation, in worker threads. This separation
9700 avoids delaying the main thread when a new consensus arrives.
9702 o Major features (experimental):
9703 - Tor can now build modules written in Rust. To turn this on, pass
9704 the "--enable-rust" flag to the configure script. It's not time to
9705 get excited yet: currently, there is no actual Rust functionality
9706 beyond some simple glue code, and a notice at startup to tell you
9707 that Rust is running. Still, we hope that programmers and
9708 packagers will try building Tor with Rust support, so that we can
9709 find issues and solve portability problems. Closes ticket 22106.
9711 o Major features (traffic analysis resistance):
9712 - Connections between clients and relays now send a padding cell in
9713 each direction every 1.5 to 9.5 seconds (tunable via consensus
9714 parameters). This padding will not resist specialized
9715 eavesdroppers, but it should be enough to make many ISPs' routine
9716 network flow logging less useful in traffic analysis against
9719 Padding is negotiated using Tor's link protocol, so both relays
9720 and clients must upgrade for this to take effect. Clients may
9721 still send padding despite the relay's version by setting
9722 ConnectionPadding 1 in torrc, and may disable padding by setting
9723 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
9724 users with the torrc option ReducedConnectionPadding. Implements
9725 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
9726 - Relays will publish 24 hour totals of padding and non-padding cell
9727 counts to their extra-info descriptors, unless PaddingStatistics 0
9728 is set in torrc. These 24 hour totals are also rounded to
9731 o Major bugfixes (hidden service, relay, security):
9732 - Fix a remotely triggerable assertion failure when a hidden service
9733 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
9734 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
9735 - Fix a remotely triggerable assertion failure caused by receiving a
9736 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
9737 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
9740 o Major bugfixes (path selection, security):
9741 - When choosing which guard to use for a circuit, avoid the exit's
9742 family along with the exit itself. Previously, the new guard
9743 selection logic avoided the exit, but did not consider its family.
9744 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
9745 006 and CVE-2017-0377.
9747 o Major bugfixes (connection usage):
9748 - We use NETINFO cells to try to determine if both relays involved
9749 in a connection will agree on the canonical status of that
9750 connection. We prefer the connections where this is the case for
9751 extend cells, and try to close connections where relays disagree
9752 on their canonical status early. Also, we now prefer the oldest
9753 valid connection for extend cells. These two changes should reduce
9754 the number of long-term connections that are kept open between
9755 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
9756 - Relays now log hourly statistics (look for
9757 "channel_check_for_duplicates" lines) on the total number of
9758 connections to other relays. If the number of connections per
9759 relay is unexpectedly large, this log message is at notice level.
9760 Otherwise it is at info.
9762 o Major bugfixes (entry guards):
9763 - When starting with an old consensus, do not add new entry guards
9764 unless the consensus is "reasonably live" (under 1 day old). Fixes
9765 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
9766 - Don't block bootstrapping when a primary bridge is offline and we
9767 can't get its descriptor. Fixes bug 22325; fixes one case of bug
9768 21969; bugfix on 0.3.0.3-alpha.
9770 o Major bugfixes (linux TPROXY support):
9771 - Fix a typo that had prevented TPROXY-based transparent proxying
9772 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
9773 Patch from "d4fq0fQAgoJ".
9775 o Major bugfixes (openbsd, denial-of-service):
9776 - Avoid an assertion failure bug affecting our implementation of
9777 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
9778 handling of "0xx" differs from what we had expected. Fixes bug
9779 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
9781 o Major bugfixes (relay, link handshake):
9782 - When performing the v3 link handshake on a TLS connection, report
9783 that we have the x509 certificate that we actually used on that
9784 connection, even if we have changed certificates since that
9785 connection was first opened. Previously, we would claim to have
9786 used our most recent x509 link certificate, which would sometimes
9787 make the link handshake fail. Fixes one case of bug 22460; bugfix
9790 o Major bugfixes (relays, key management):
9791 - Regenerate link and authentication certificates whenever the key
9792 that signs them changes; also, regenerate link certificates
9793 whenever the signed key changes. Previously, these processes were
9794 only weakly coupled, and we relays could (for minutes to hours)
9795 wind up with an inconsistent set of keys and certificates, which
9796 other relays would not accept. Fixes two cases of bug 22460;
9797 bugfix on 0.3.0.1-alpha.
9798 - When sending an Ed25519 signing->link certificate in a CERTS cell,
9799 send the certificate that matches the x509 certificate that we
9800 used on the TLS connection. Previously, there was a race condition
9801 if the TLS context rotated after we began the TLS handshake but
9802 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
9805 o Minor features (security, windows):
9806 - Enable a couple of pieces of Windows hardening: one
9807 (HeapEnableTerminationOnCorruption) that has been on-by-default
9808 since Windows 8, and unavailable before Windows 7; and one
9809 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
9810 affect us, but shouldn't do any harm. Closes ticket 21953.
9812 o Minor features (bridge authority):
9813 - Add "fingerprint" lines to the networkstatus-bridges file produced
9814 by bridge authorities. Closes ticket 22207.
9816 o Minor features (code style):
9817 - Add "Falls through" comments to our codebase, in order to silence
9818 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
9819 Stieger. Closes ticket 22446.
9821 o Minor features (config options):
9822 - Allow "%include" directives in torrc configuration files. These
9823 directives import the settings from other files, or from all the
9824 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
9825 - Make SAVECONF return an error when overwriting a torrc that has
9826 includes. Using SAVECONF with the FORCE option will allow it to
9827 overwrite torrc even if includes are used. Related to ticket 1922.
9828 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
9829 will work without the FORCE option. Related to ticket 1922.
9831 o Minor features (controller):
9832 - Warn the first time that a controller requests data in the long-
9833 deprecated 'GETINFO network-status' format. Closes ticket 21703.
9835 o Minor features (defaults):
9836 - The default value for UseCreateFast is now 0: clients which
9837 haven't yet received a consensus document will now use a proper
9838 ntor handshake to talk to their directory servers whenever they
9839 can. Closes ticket 21407.
9840 - Onion key rotation and expiry intervals are now defined as a
9841 network consensus parameter, per proposal 274. The default
9842 lifetime of an onion key is increased from 7 to 28 days. Old onion
9843 keys will expire after 7 days by default. This change will make
9844 consensus diffs much smaller, and save significant bandwidth.
9845 Closes ticket 21641.
9847 o Minor features (defensive programming):
9848 - Create a pair of consensus parameters, nf_pad_tor2web and
9849 nf_pad_single_onion, to disable netflow padding in the consensus
9850 for non-anonymous connections in case the overhead is high. Closes
9853 o Minor features (diagnostic):
9854 - Add a stack trace to the bug warnings that can be logged when
9855 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
9856 attempt for bug 23105.
9857 - Add logging messages to try to diagnose a rare bug that seems to
9858 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
9859 think this is happening because of incorrect system clocks, but
9860 we'd like to know for certain. Diagnostic for bug 22466.
9861 - Avoid an assertion failure, and log a better error message, when
9862 unable to remove a file from the consensus cache on Windows.
9863 Attempts to mitigate and diagnose bug 22752.
9865 o Minor features (directory authority):
9866 - Improve the message that authorities report to relays that present
9867 RSA/Ed25519 keypairs that conflict with previously pinned keys.
9868 Closes ticket 22348.
9870 o Minor features (directory cache, consensus diff):
9871 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
9872 operators with low-resource environments to adjust the number of
9873 consensuses they'll store and generate diffs from. Most cache
9874 operators should leave it unchanged. Helps to work around
9877 o Minor features (fallback directory list):
9878 - Update the fallback directory mirror whitelist and blacklist based
9879 on operator emails. Closes task 21121.
9880 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
9881 December 2016 (of which ~126 were still functional) with a list of
9882 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
9883 2017. Resolves ticket 21564.
9885 o Minor features (geoip):
9886 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
9889 o Minor features (hidden services, logging):
9890 - Log a message when a hidden service descriptor has fewer
9891 introduction points than specified in
9892 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
9893 - Log a message when a hidden service reaches its introduction point
9894 circuit limit, and when that limit is reset. Follow up to ticket
9895 21594; closes ticket 21622.
9896 - Warn user if multiple entries in EntryNodes and at least one
9897 HiddenService are used together. Pinning EntryNodes along with a
9898 hidden service can be possibly harmful; for instance see ticket
9899 14917 or 21155. Closes ticket 21155.
9901 o Minor features (linux seccomp2 sandbox):
9902 - We now have a document storage backend compatible with the Linux
9903 seccomp2 sandbox. This backend is used for consensus documents and
9904 diffs between them; in the long term, we'd like to use it for
9905 unparseable directory material too. Closes ticket 21645
9906 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
9907 from 1MB to 16MB. This was necessary with the glibc allocator in
9908 order to allow worker threads to allocate more memory -- which in
9909 turn is necessary because of our new use of worker threads for
9910 compression. Closes ticket 22096.
9912 o Minor features (logging):
9913 - Log files are no longer created world-readable by default.
9914 (Previously, most distributors would store the logs in a non-
9915 world-readable location to prevent inappropriate access. This
9916 change is an extra precaution.) Closes ticket 21729; patch
9919 o Minor features (performance):
9920 - Our Keccak (SHA-3) implementation now accesses memory more
9921 efficiently, especially on little-endian systems. Closes
9923 - Add an O(1) implementation of channel_find_by_global_id(), to
9924 speed some controller functions.
9926 o Minor features (relay, configuration):
9927 - The MyFamily option may now be repeated as many times as desired,
9928 for relays that want to configure large families. Closes ticket
9929 4998; patch by Daniel Pinto.
9931 o Minor features (relay, performance):
9932 - Always start relays with at least two worker threads, to prevent
9933 priority inversion on slow tasks. Part of the fix for bug 22883.
9934 - Allow background work to be queued with different priorities, so
9935 that a big pile of slow low-priority jobs will not starve out
9936 higher priority jobs. This lays the groundwork for a fix for
9939 o Minor features (safety):
9940 - Add an explicit check to extrainfo_parse_entry_from_string() for
9941 NULL inputs. We don't believe this can actually happen, but it may
9942 help silence a warning from the Clang analyzer. Closes
9945 o Minor features (testing):
9946 - Add more tests for compression backend initialization. Closes
9948 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
9949 When Tor is compiled with this option, we disable a number of
9950 redundant memory-safety failsafes that are intended to stop bugs
9951 from becoming security issues. This makes it easier to hunt for
9952 bugs that would be security issues without the failsafes turned
9953 on. Closes ticket 21439.
9954 - Add a general event-tracing instrumentation support to Tor. This
9955 subsystem will enable developers and researchers to add fine-
9956 grained instrumentation to their Tor instances, for use when
9957 examining Tor network performance issues. There are no trace
9958 events yet, and event-tracing is off by default unless enabled at
9959 compile time. Implements ticket 13802.
9960 - Improve our version parsing tests: add tests for typical version
9961 components, add tests for invalid versions, including numeric
9962 range and non-numeric prefixes. Unit tests 21278, 21450, and
9963 21507. Partially implements 21470.
9965 o Minor bugfixes (bandwidth accounting):
9966 - Roll over monthly accounting at the configured hour and minute,
9967 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
9968 Found by Andrey Karpov with PVS-Studio.
9970 o Minor bugfixes (code correctness):
9971 - Accurately identify client connections by their lack of peer
9972 authentication. This means that we bail out earlier if asked to
9973 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
9976 o Minor bugfixes (compilation warnings):
9977 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
9978 22915; bugfix on 0.2.8.1-alpha.
9979 - Fix warnings when building with libscrypt and openssl scrypt
9980 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
9981 - When building with certain versions of the mingw C header files,
9982 avoid float-conversion warnings when calling the C functions
9983 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
9986 o Minor bugfixes (compilation):
9987 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
9988 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
9990 o Minor bugfixes (compression):
9991 - When spooling compressed data to an output buffer, don't try to
9992 spool more data when there is no more data to spool and we are not
9993 trying to flush the input. Previously, we would sometimes launch
9994 compression requests with nothing to do, which interferes with our
9995 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
9997 o Minor bugfixes (configuration):
9998 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
9999 bug 22252; bugfix on 0.2.9.3-alpha.
10001 o Minor bugfixes (connection lifespan):
10002 - Allow more control over how long TLS connections are kept open:
10003 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
10004 single option called CircuitsAvailableTimeout. Also, allow the
10005 consensus to control the default values for both this preference
10006 and the lifespan of relay-to-relay connections. Fixes bug 17592;
10007 bugfix on 0.2.5.5-alpha.
10008 - Increase the initial circuit build timeout testing frequency, to
10009 help ensure that ReducedConnectionPadding clients finish learning
10010 a timeout before their orconn would expire. The initial testing
10011 rate was set back in the days of TAP and before the Tor Browser
10012 updater, when we had to be much more careful about new clients
10013 making lots of circuits. With this change, a circuit build timeout
10014 is learned in about 15-20 minutes, instead of 100-120 minutes.
10016 o Minor bugfixes (controller):
10017 - Do not crash when receiving a HSPOST command with an empty body.
10018 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
10019 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
10020 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
10021 - GETINFO onions/current and onions/detached no longer respond with
10022 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
10023 - Trigger HS descriptor events on the control port when the client
10024 fails to pick a hidden service directory for a hidden service.
10025 This can happen if all the hidden service directories are in
10026 ExcludeNodes, or they have all been queried within the last 15
10027 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
10029 o Minor bugfixes (correctness):
10030 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
10031 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
10033 o Minor bugfixes (coverity build support):
10034 - Avoid Coverity build warnings related to our BUG() macro. By
10035 default, Coverity treats BUG() as the Linux kernel does: an
10036 instant abort(). We need to override that so our BUG() macro
10037 doesn't prevent Coverity from analyzing functions that use it.
10038 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
10040 o Minor bugfixes (defensive programming):
10041 - Detect and break out of infinite loops in our compression code. We
10042 don't think that any such loops exist now, but it's best to be
10043 safe. Closes ticket 22672.
10044 - Fix a memset() off the end of an array when packing cells. This
10045 bug should be harmless in practice, since the corrupted bytes are
10046 still in the same structure, and are always padding bytes,
10047 ignored, or immediately overwritten, depending on compiler
10048 behavior. Nevertheless, because the memset()'s purpose is to make
10049 sure that any other cell-handling bugs can't expose bytes to the
10050 network, we need to fix it. Fixes bug 22737; bugfix on
10051 0.2.4.11-alpha. Fixes CID 1401591.
10053 o Minor bugfixes (directory authority):
10054 - When a directory authority rejects a descriptor or extrainfo with
10055 a given digest, mark that digest as undownloadable, so that we do
10056 not attempt to download it again over and over. We previously
10057 tried to avoid downloading such descriptors by other means, but we
10058 didn't notice if we accidentally downloaded one anyway. This
10059 behavior became problematic in 0.2.7.2-alpha, when authorities
10060 began pinning Ed25519 keys. Fixes bug 22349; bugfix
10062 - When rejecting a router descriptor for running an obsolete version
10063 of Tor without ntor support, warn about the obsolete tor version,
10064 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
10065 - Prevent the shared randomness subsystem from asserting when
10066 initialized by a bridge authority with an incomplete configuration
10067 file. Fixes bug 21586; bugfix on 0.2.9.8.
10069 o Minor bugfixes (error reporting, windows):
10070 - When formatting Windows error messages, use the English format to
10071 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
10074 o Minor bugfixes (exit-side DNS):
10075 - Fix an untriggerable assertion that checked the output of a
10076 libevent DNS error, so that the assertion actually behaves as
10077 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
10078 Karpov using PVS-Studio.
10080 o Minor bugfixes (fallback directories):
10081 - Make the usage example in updateFallbackDirs.py actually work, and
10082 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
10083 - Decrease the guard flag average required to be a fallback. This
10084 allows us to keep relays that have their guard flag removed when
10085 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
10086 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
10087 bugfix on 0.2.8.1-alpha.
10088 - Make sure fallback directory mirrors have the same address, port,
10089 and relay identity key for at least 30 days before they are
10090 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
10092 o Minor bugfixes (file limits, osx):
10093 - When setting the maximum number of connections allowed by the OS,
10094 always allow some extra file descriptors for other files. Fixes
10095 bug 22797; bugfix on 0.2.0.10-alpha.
10097 o Minor bugfixes (hidden services):
10098 - Increase the number of circuits that a service is allowed to
10099 open over a specific period of time. The value was lower than it
10100 should be (8 vs 12) in the normal case of 3 introduction points.
10101 Fixes bug 22159; bugfix on 0.3.0.5-rc.
10102 - Fix a BUG warning during HSv3 descriptor decoding that could be
10103 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
10104 on 0.3.0.1-alpha. Bug found by "haxxpop".
10105 - Stop printing a cryptic warning when a hidden service gets a
10106 request to connect to a virtual port that it hasn't configured.
10107 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
10108 - Simplify hidden service descriptor creation by using an existing
10109 flag to check if an introduction point is established. Fixes bug
10110 21599; bugfix on 0.2.7.2-alpha.
10112 o Minor bugfixes (link handshake):
10113 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
10114 months, and regenerate it when it is within one month of expiring.
10115 Previously, we had generated this certificate at startup with a
10116 ten-year lifetime, but that could lead to weird behavior when Tor
10117 was started with a grossly inaccurate clock. Mitigates bug 22466;
10118 mitigation on 0.3.0.1-alpha.
10120 o Minor bugfixes (linux seccomp2 sandbox):
10121 - Avoid a sandbox failure when trying to re-bind to a socket and
10122 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
10123 - Permit the fchmod system call, to avoid crashing on startup when
10124 starting with the seccomp2 sandbox and an unexpected set of
10125 permissions on the data directory or its contents. Fixes bug
10126 22516; bugfix on 0.2.5.4-alpha.
10128 o Minor bugfixes (logging):
10129 - When decompressing, do not warn if we fail to decompress using a
10130 compression method that we merely guessed. Fixes part of bug
10131 22670; bugfix on 0.1.1.14-alpha.
10132 - When decompressing, treat mismatch between content-encoding and
10133 actual compression type as a protocol warning. Fixes part of bug
10134 22670; bugfix on 0.1.1.9-alpha.
10135 - Downgrade "assigned_to_cpuworker failed" message to info-level
10136 severity. In every case that can reach it, either a better warning
10137 has already been logged, or no warning is warranted. Fixes bug
10138 22356; bugfix on 0.2.6.3-alpha.
10139 - Log a better message when a directory authority replies to an
10140 upload with an unexpected status code. Fixes bug 11121; bugfix
10142 - Downgrade a log statement about unexpected relay cells from "bug"
10143 to "protocol warning", because there is at least one use case
10144 where it can be triggered by a buggy tor implementation. Fixes bug
10145 21293; bugfix on 0.1.1.14-alpha.
10147 o Minor bugfixes (logging, relay):
10148 - Remove a forgotten debugging message when an introduction point
10149 successfully establishes a hidden service prop224 circuit with
10151 - Change three other log_warn() for an introduction point to
10152 protocol warnings, because they can be failure from the network
10153 and are not relevant to the operator. Fixes bug 23078; bugfix on
10154 0.3.0.1-alpha and 0.3.0.2-alpha.
10156 o Minor bugfixes (relay):
10157 - Inform the geoip and rephist modules about all requests, even on
10158 relays that are only fetching microdescriptors. Fixes a bug
10159 related to 21585; bugfix on 0.3.0.1-alpha.
10161 o Minor bugfixes (memory leaks):
10162 - Fix a small memory leak at exit from the backtrace handler code.
10163 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
10164 - When directory authorities reject a router descriptor due to
10165 keypinning, free the router descriptor rather than leaking the
10166 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
10167 - Fix a small memory leak when validating a configuration that uses
10168 two or more AF_UNIX sockets for the same port type. Fixes bug
10169 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
10171 o Minor bugfixes (process behavior):
10172 - When exiting because of an error, always exit with a nonzero exit
10173 status. Previously, we would fail to report an error in our exit
10174 status in cases related to __OwningControllerProcess failure,
10175 lockfile contention, and Ed25519 key initialization. Fixes bug
10176 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
10177 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
10180 o Minor bugfixes (robustness, error handling):
10181 - Improve our handling of the cases where OpenSSL encounters a
10182 memory error while encoding keys and certificates. We haven't
10183 observed these errors in the wild, but if they do happen, we now
10184 detect and respond better. Fixes bug 19418; bugfix on all versions
10185 of Tor. Reported by Guido Vranken.
10187 o Minor bugfixes (testing):
10188 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
10189 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
10190 - Use unbuffered I/O for utility functions around the
10191 process_handle_t type. This fixes unit test failures reported on
10192 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
10193 - Make display of captured unit test log messages consistent. Fixes
10194 bug 21510; bugfix on 0.2.9.3-alpha.
10195 - Make test-network.sh always call chutney's test-network.sh.
10196 Previously, this only worked on systems which had bash installed,
10197 due to some bash-specific code in the script. Fixes bug 19699;
10198 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
10199 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
10200 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
10201 - The unit tests now pass on systems where localhost is misconfigured
10202 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
10205 o Minor bugfixes (voting consistency):
10206 - Reject version numbers with non-numeric prefixes (such as +, -, or
10207 whitespace). Disallowing whitespace prevents differential version
10208 parsing between POSIX-based and Windows platforms. Fixes bug 21507
10209 and part of 21508; bugfix on 0.0.8pre1.
10211 o Minor bugfixes (Windows service):
10212 - When running as a Windows service, set the ID of the main thread
10213 correctly. Failure to do so made us fail to send log messages to
10214 the controller in 0.2.1.16-rc, slowed down controller event
10215 delivery in 0.2.7.3-rc and later, and crash with an assertion
10216 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
10217 Patch and diagnosis from "Vort".
10219 o Minor bugfixes (windows, relay):
10220 - Resolve "Failure from drain_fd: No error" warnings on Windows
10221 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
10223 o Code simplification and refactoring:
10224 - Break up the 630-line function connection_dir_client_reached_eof()
10225 into a dozen smaller functions. This change should help
10226 maintainability and readability of the client directory code.
10227 - Isolate our use of the openssl headers so that they are only
10228 included from our crypto wrapper modules, and from tests that
10229 examine those modules' internals. Closes ticket 21841.
10230 - Simplify our API to launch directory requests, making it more
10231 extensible and less error-prone. Now it's easier to add extra
10232 headers to directory requests. Closes ticket 21646.
10233 - Our base64 decoding functions no longer overestimate the output
10234 space that they need when parsing unpadded inputs. Closes
10236 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
10237 Resolves ticket 22213.
10238 - The logic that directory caches use to spool request to clients,
10239 serving them one part at a time so as not to allocate too much
10240 memory, has been refactored for consistency. Previously there was
10241 a separate spooling implementation per type of spoolable data. Now
10242 there is one common spooling implementation, with extensible data
10243 types. Closes ticket 21651.
10244 - Tor's compression module now supports multiple backends. Part of
10245 the implementation for proposal 278; closes ticket 21663.
10248 - Add a manpage description for the key-pinning-journal file. Closes
10250 - Correctly note that bandwidth accounting values are stored in the
10251 state file, and the bw_accounting file is now obsolete. Closes
10253 - Document more of the files in the Tor data directory, including
10254 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
10255 approved-routers, sr-random, and diff-cache. Found while fixing
10257 - Clarify the manpage for the (deprecated) torify script. Closes
10259 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
10260 Closes ticket 21873.
10261 - Correct documentation about the default DataDirectory value.
10262 Closes ticket 21151.
10263 - Document the default behavior of NumEntryGuards and
10264 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
10266 - Document key=value pluggable transport arguments for Bridge lines
10267 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
10268 - Note that bandwidth-limiting options don't affect TCP headers or
10269 DNS. Closes ticket 17170.
10271 o Removed features (configuration options, all in ticket 22060):
10272 - These configuration options are now marked Obsolete, and no longer
10273 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
10274 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
10275 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
10276 in 0.2.9.2-alpha and have now been removed. The previous default
10277 behavior is now always chosen; the previous (less secure) non-
10278 default behavior is now unavailable.
10279 - CloseHSClientCircuitsImmediatelyOnTimeout and
10280 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
10281 0.2.9.2-alpha and now have been removed. HS circuits never close
10282 on circuit build timeout; they have a longer timeout period.
10283 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
10284 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
10285 (and others) to configure listen-only and advertise-only addresses.
10287 o Removed features (tools):
10288 - We've removed the tor-checkkey tool from src/tools. Long ago, we
10289 used it to help people detect RSA keys that were generated by
10290 versions of Debian affected by CVE-2008-0166. But those keys have
10291 been out of circulation for ages, and this tool is no longer
10292 required. Closes ticket 21842.
10295 Changes in version 0.3.0.10 - 2017-08-02
10296 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
10297 from the current Tor alpha series. OpenBSD users and TPROXY users
10298 should upgrade; others are probably okay sticking with 0.3.0.9.
10300 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
10301 - Tor's repository now includes a Travis Continuous Integration (CI)
10302 configuration file (.travis.yml). This is meant to help new
10303 developers and contributors who fork Tor to a Github repository be
10304 better able to test their changes, and understand what we expect
10305 to pass. To use this new build feature, you must fork Tor to your
10306 Github account, then go into the "Integrations" menu in the
10307 repository settings for your fork and enable Travis, then push
10308 your changes. Closes ticket 22636.
10310 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
10311 - Fix a typo that had prevented TPROXY-based transparent proxying
10312 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
10313 Patch from "d4fq0fQAgoJ".
10315 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
10316 - Avoid an assertion failure bug affecting our implementation of
10317 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
10318 handling of "0xbar" differs from what we had expected. Fixes bug
10319 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
10321 o Minor features (backport from 0.3.1.5-alpha):
10322 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
10325 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
10326 - Roll over monthly accounting at the configured hour and minute,
10327 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
10328 Found by Andrey Karpov with PVS-Studio.
10330 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
10331 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
10332 bugfix on 0.2.8.1-alpha.
10333 - Fix warnings when building with libscrypt and openssl scrypt
10334 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
10335 - When building with certain versions of the mingw C header files,
10336 avoid float-conversion warnings when calling the C functions
10337 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
10340 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
10341 - Backport a fix for an "unused variable" warning that appeared
10342 in some versions of mingw. Fixes bug 22838; bugfix on
10345 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
10346 - Avoid Coverity build warnings related to our BUG() macro. By
10347 default, Coverity treats BUG() as the Linux kernel does: an
10348 instant abort(). We need to override that so our BUG() macro
10349 doesn't prevent Coverity from analyzing functions that use it.
10350 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
10352 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
10353 - When rejecting a router descriptor for running an obsolete version
10354 of Tor without ntor support, warn about the obsolete tor version,
10355 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
10357 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
10358 - Avoid a sandbox failure when trying to re-bind to a socket and
10359 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
10361 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
10362 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
10363 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
10366 Changes in version 0.3.0.9 - 2017-06-29
10367 Tor 0.3.0.9 fixes a path selection bug that would allow a client
10368 to use a guard that was in the same network family as a chosen exit
10369 relay. This is a security regression; all clients running earlier
10370 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
10373 This release also backports several other bugfixes from the 0.3.1.x
10376 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
10377 - When choosing which guard to use for a circuit, avoid the exit's
10378 family along with the exit itself. Previously, the new guard
10379 selection logic avoided the exit, but did not consider its family.
10380 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
10381 006 and CVE-2017-0377.
10383 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
10384 - Don't block bootstrapping when a primary bridge is offline and we
10385 can't get its descriptor. Fixes bug 22325; fixes one case of bug
10386 21969; bugfix on 0.3.0.3-alpha.
10388 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
10389 - When starting with an old consensus, do not add new entry guards
10390 unless the consensus is "reasonably live" (under 1 day old). Fixes
10391 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
10393 o Minor features (geoip):
10394 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
10397 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
10398 - Reject version numbers with non-numeric prefixes (such as +, -, or
10399 whitespace). Disallowing whitespace prevents differential version
10400 parsing between POSIX-based and Windows platforms. Fixes bug 21507
10401 and part of 21508; bugfix on 0.0.8pre1.
10403 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
10404 - Permit the fchmod system call, to avoid crashing on startup when
10405 starting with the seccomp2 sandbox and an unexpected set of
10406 permissions on the data directory or its contents. Fixes bug
10407 22516; bugfix on 0.2.5.4-alpha.
10409 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
10410 - Fix a memset() off the end of an array when packing cells. This
10411 bug should be harmless in practice, since the corrupted bytes are
10412 still in the same structure, and are always padding bytes,
10413 ignored, or immediately overwritten, depending on compiler
10414 behavior. Nevertheless, because the memset()'s purpose is to make
10415 sure that any other cell-handling bugs can't expose bytes to the
10416 network, we need to fix it. Fixes bug 22737; bugfix on
10417 0.2.4.11-alpha. Fixes CID 1401591.
10420 Changes in version 0.3.0.8 - 2017-06-08
10421 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
10422 remotely crash a hidden service with an assertion failure. Anyone
10423 running a hidden service should upgrade to this version, or to some
10424 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
10426 Tor 0.3.0.8 also includes fixes for several key management bugs
10427 that sometimes made relays unreliable, as well as several other
10428 bugfixes described below.
10430 o Major bugfixes (hidden service, relay, security, backport
10431 from 0.3.1.3-alpha):
10432 - Fix a remotely triggerable assertion failure when a hidden service
10433 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
10434 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
10435 - Fix a remotely triggerable assertion failure caused by receiving a
10436 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
10437 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
10440 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
10441 - When performing the v3 link handshake on a TLS connection, report
10442 that we have the x509 certificate that we actually used on that
10443 connection, even if we have changed certificates since that
10444 connection was first opened. Previously, we would claim to have
10445 used our most recent x509 link certificate, which would sometimes
10446 make the link handshake fail. Fixes one case of bug 22460; bugfix
10449 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
10450 - Regenerate link and authentication certificates whenever the key
10451 that signs them changes; also, regenerate link certificates
10452 whenever the signed key changes. Previously, these processes were
10453 only weakly coupled, and we relays could (for minutes to hours)
10454 wind up with an inconsistent set of keys and certificates, which
10455 other relays would not accept. Fixes two cases of bug 22460;
10456 bugfix on 0.3.0.1-alpha.
10457 - When sending an Ed25519 signing->link certificate in a CERTS cell,
10458 send the certificate that matches the x509 certificate that we
10459 used on the TLS connection. Previously, there was a race condition
10460 if the TLS context rotated after we began the TLS handshake but
10461 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
10464 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
10465 - Stop rejecting v3 hidden service descriptors because their size
10466 did not match an old padding rule. Fixes bug 22447; bugfix on
10469 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
10470 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
10471 December 2016 (of which ~126 were still functional) with a list of
10472 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
10473 2017. Resolves ticket 21564.
10475 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
10476 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
10477 bug 22252; bugfix on 0.2.9.3-alpha.
10479 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
10480 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
10481 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
10483 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
10484 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
10485 months, and regenerate it when it is within one month of expiring.
10486 Previously, we had generated this certificate at startup with a
10487 ten-year lifetime, but that could lead to weird behavior when Tor
10488 was started with a grossly inaccurate clock. Mitigates bug 22466;
10489 mitigation on 0.3.0.1-alpha.
10491 o Minor bugfixes (memory leak, directory authority, backport from
10493 - When directory authorities reject a router descriptor due to
10494 keypinning, free the router descriptor rather than leaking the
10495 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
10498 Changes in version 0.2.9.11 - 2017-06-08
10499 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
10500 remotely crash a hidden service with an assertion failure. Anyone
10501 running a hidden service should upgrade to this version, or to some
10502 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
10503 are not affected by TROVE-2017-004.)
10505 Tor 0.2.9.11 also backports fixes for several key management bugs
10506 that sometimes made relays unreliable, as well as several other
10507 bugfixes described below.
10509 o Major bugfixes (hidden service, relay, security, backport
10510 from 0.3.1.3-alpha):
10511 - Fix a remotely triggerable assertion failure caused by receiving a
10512 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
10513 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
10516 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
10517 - When performing the v3 link handshake on a TLS connection, report
10518 that we have the x509 certificate that we actually used on that
10519 connection, even if we have changed certificates since that
10520 connection was first opened. Previously, we would claim to have
10521 used our most recent x509 link certificate, which would sometimes
10522 make the link handshake fail. Fixes one case of bug 22460; bugfix
10525 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
10526 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
10527 December 2016 (of which ~126 were still functional) with a list of
10528 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
10529 2017. Resolves ticket 21564.
10531 o Minor features (future-proofing, backport from 0.3.0.7):
10532 - Tor no longer refuses to download microdescriptors or descriptors if
10533 they are listed as "published in the future". This change will
10534 eventually allow us to stop listing meaningful "published" dates
10535 in microdescriptor consensuses, and thereby allow us to reduce the
10536 resources required to download consensus diffs by over 50%.
10537 Implements part of ticket 21642; implements part of proposal 275.
10539 o Minor features (directory authorities, backport from 0.3.0.4-rc)
10540 - Directory authorities now reject relays running versions
10541 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
10542 suffer from bug 20499 and don't keep their consensus cache
10543 up-to-date. Resolves ticket 20509.
10545 o Minor features (geoip):
10546 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
10549 o Minor bugfixes (control port, backport from 0.3.0.6):
10550 - The GETINFO extra-info/digest/<digest> command was broken because
10551 of a wrong base16 decode return value check, introduced when
10552 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
10554 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
10555 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
10556 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
10558 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
10559 - The getpid() system call is now permitted under the Linux seccomp2
10560 sandbox, to avoid crashing with versions of OpenSSL (and other
10561 libraries) that attempt to learn the process's PID by using the
10562 syscall rather than the VDSO code. Fixes bug 21943; bugfix
10565 o Minor bugfixes (memory leak, directory authority, backport
10566 from 0.3.1.2-alpha):
10567 - When directory authorities reject a router descriptor due to
10568 keypinning, free the router descriptor rather than leaking the
10569 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
10571 Changes in version 0.2.8.14 - 2017-06-08
10572 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
10573 remotely crash a hidden service with an assertion failure. Anyone
10574 running a hidden service should upgrade to this version, or to some
10575 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
10576 are not affected by TROVE-2017-004.)
10578 o Major bugfixes (hidden service, relay, security):
10579 - Fix a remotely triggerable assertion failure caused by receiving a
10580 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
10581 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
10584 o Minor features (geoip):
10585 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
10588 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
10589 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
10590 December 2016 (of which ~126 were still functional) with a list of
10591 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
10592 2017. Resolves ticket 21564.
10594 o Minor bugfixes (correctness):
10595 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
10596 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
10598 Changes in version 0.2.7.8 - 2017-06-08
10599 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
10600 remotely crash a hidden service with an assertion failure. Anyone
10601 running a hidden service should upgrade to this version, or to some
10602 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
10603 are not affected by TROVE-2017-004.)
10605 o Major bugfixes (hidden service, relay, security):
10606 - Fix a remotely triggerable assertion failure caused by receiving a
10607 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
10608 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
10611 o Minor features (geoip):
10612 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
10615 o Minor bugfixes (correctness):
10616 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
10617 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
10620 Changes in version 0.2.6.12 - 2017-06-08
10621 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
10622 remotely crash a hidden service with an assertion failure. Anyone
10623 running a hidden service should upgrade to this version, or to some
10624 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
10625 are not affected by TROVE-2017-004.)
10627 o Major bugfixes (hidden service, relay, security):
10628 - Fix a remotely triggerable assertion failure caused by receiving a
10629 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
10630 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
10633 o Minor features (geoip):
10634 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
10637 o Minor bugfixes (correctness):
10638 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
10639 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
10641 Changes in version 0.2.5.14 - 2017-06-08
10642 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
10643 remotely crash a hidden service with an assertion failure. Anyone
10644 running a hidden service should upgrade to this version, or to some
10645 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
10646 are not affected by TROVE-2017-004.)
10648 o Major bugfixes (hidden service, relay, security):
10649 - Fix a remotely triggerable assertion failure caused by receiving a
10650 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
10651 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
10654 o Minor features (geoip):
10655 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
10658 o Minor bugfixes (correctness):
10659 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
10660 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
10662 Changes in version 0.2.4.29 - 2017-06-08
10663 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
10664 remotely crash a hidden service with an assertion failure. Anyone
10665 running a hidden service should upgrade to this version, or to some
10666 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
10667 are not affected by TROVE-2017-004.)
10669 o Major bugfixes (hidden service, relay, security):
10670 - Fix a remotely triggerable assertion failure caused by receiving a
10671 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
10672 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
10675 o Minor features (geoip):
10676 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
10679 o Minor bugfixes (correctness):
10680 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
10681 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
10684 Changes in version 0.3.0.7 - 2017-05-15
10685 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
10686 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
10687 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
10688 clients are not affected.
10690 o Major bugfixes (hidden service directory, security):
10691 - Fix an assertion failure in the hidden service directory code, which
10692 could be used by an attacker to remotely cause a Tor relay process to
10693 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
10694 should upgrade. This security issue is tracked as TROVE-2017-002.
10695 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
10698 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
10701 o Minor features (future-proofing):
10702 - Tor no longer refuses to download microdescriptors or descriptors
10703 if they are listed as "published in the future". This change will
10704 eventually allow us to stop listing meaningful "published" dates
10705 in microdescriptor consensuses, and thereby allow us to reduce the
10706 resources required to download consensus diffs by over 50%.
10707 Implements part of ticket 21642; implements part of proposal 275.
10709 o Minor bugfixes (Linux seccomp2 sandbox):
10710 - The getpid() system call is now permitted under the Linux seccomp2
10711 sandbox, to avoid crashing with versions of OpenSSL (and other
10712 libraries) that attempt to learn the process's PID by using the
10713 syscall rather than the VDSO code. Fixes bug 21943; bugfix
10717 Changes in version 0.3.0.6 - 2017-04-26
10718 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
10720 With the 0.3.0 series, clients and relays now use Ed25519 keys to
10721 authenticate their link connections to relays, rather than the old
10722 RSA1024 keys that they used before. (Circuit crypto has been
10723 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
10724 the guard selection and replacement algorithm to behave more robustly
10725 in the presence of unreliable networks, and to resist guard-
10728 This series also includes numerous other small features and bugfixes,
10729 along with more groundwork for the upcoming hidden-services revamp.
10731 Per our stable release policy, we plan to support the Tor 0.3.0
10732 release series for at least the next nine months, or for three months
10733 after the first stable release of the 0.3.1 series: whichever is
10734 longer. If you need a release with long-term support, we recommend
10735 that you stay with the 0.2.9 series.
10737 Below are the changes since 0.2.9.10. For a list of only the changes
10738 since 0.3.0.5-rc, see the ChangeLog file.
10740 o Major features (directory authority, security):
10741 - The default for AuthDirPinKeys is now 1: directory authorities
10742 will reject relays where the RSA identity key matches a previously
10743 seen value, but the Ed25519 key has changed. Closes ticket 18319.
10745 o Major features (guard selection algorithm):
10746 - Tor's guard selection algorithm has been redesigned from the
10747 ground up, to better support unreliable networks and restrictive
10748 sets of entry nodes, and to better resist guard-capture attacks by
10749 hostile local networks. Implements proposal 271; closes
10752 o Major features (next-generation hidden services):
10753 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
10754 prop224 aka "Next Generation Hidden Services". Service and clients
10755 don't use this functionality yet. Closes ticket 19043. Based on
10756 initial code by Alec Heifetz.
10757 - Relays now support the HSDir version 3 protocol, so that they can
10758 can store and serve v3 descriptors. This is part of the next-
10759 generation onion service work detailed in proposal 224. Closes
10762 o Major features (protocol, ed25519 identity keys):
10763 - Clients now support including Ed25519 identity keys in the EXTEND2
10764 cells they generate. By default, this is controlled by a consensus
10765 parameter, currently disabled. You can turn this feature on for
10766 testing by setting ExtendByEd25519ID in your configuration. This
10767 might make your traffic appear different than the traffic
10768 generated by other users, however. Implements part of ticket
10769 15056; part of proposal 220.
10770 - Relays now understand requests to extend to other relays by their
10771 Ed25519 identity keys. When an Ed25519 identity key is included in
10772 an EXTEND2 cell, the relay will only extend the circuit if the
10773 other relay can prove ownership of that identity. Implements part
10774 of ticket 15056; part of proposal 220.
10775 - Relays now use Ed25519 to prove their Ed25519 identities and to
10776 one another, and to clients. This algorithm is faster and more
10777 secure than the RSA-based handshake we've been doing until now.
10778 Implements the second big part of proposal 220; Closes
10781 o Major features (security):
10782 - Change the algorithm used to decide DNS TTLs on client and server
10783 side, to better resist DNS-based correlation attacks like the
10784 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
10785 Feamster. Now relays only return one of two possible DNS TTL
10786 values, and clients are willing to believe DNS TTL values up to 3
10787 hours long. Closes ticket 19769.
10789 o Major bugfixes (client, onion service, also in 0.2.9.9):
10790 - Fix a client-side onion service reachability bug, where multiple
10791 socks requests to an onion service (or a single slow request)
10792 could cause us to mistakenly mark some of the service's
10793 introduction points as failed, and we cache that failure so
10794 eventually we run out and can't reach the service. Also resolves a
10795 mysterious "Remote server sent bogus reason code 65021" log
10796 warning. The bug was introduced in ticket 17218, where we tried to
10797 remember the circuit end reason as a uint16_t, which mangled
10798 negative values. Partially fixes bug 21056 and fixes bug 20307;
10799 bugfix on 0.2.8.1-alpha.
10801 o Major bugfixes (crash, directory connections):
10802 - Fix a rare crash when sending a begin cell on a circuit whose
10803 linked directory connection had already been closed. Fixes bug
10804 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
10806 o Major bugfixes (directory authority):
10807 - During voting, when marking a relay as a probable sybil, do not
10808 clear its BadExit flag: sybils can still be bad in other ways
10809 too. (We still clear the other flags.) Fixes bug 21108; bugfix
10812 o Major bugfixes (DNS):
10813 - Fix a bug that prevented exit nodes from caching DNS records for
10814 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
10816 o Major bugfixes (IPv6 Exits):
10817 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
10818 any IPv6 addresses. Instead, only reject a port over IPv6 if the
10819 exit policy rejects that port on more than an IPv6 /16 of
10820 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
10821 which rejected a relay's own IPv6 address by default. Fixes bug
10822 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
10824 o Major bugfixes (parsing):
10825 - Fix an integer underflow bug when comparing malformed Tor
10826 versions. This bug could crash Tor when built with
10827 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
10828 0.2.9.8, which were built with -ftrapv by default. In other cases
10829 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
10830 on 0.0.8pre1. Found by OSS-Fuzz.
10831 - When parsing a malformed content-length field from an HTTP
10832 message, do not read off the end of the buffer. This bug was a
10833 potential remote denial-of-service attack against Tor clients and
10834 relays. A workaround was released in October 2016, to prevent this
10835 bug from crashing Tor. This is a fix for the underlying issue,
10836 which should no longer matter (if you applied the earlier patch).
10837 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
10838 using AFL (http://lcamtuf.coredump.cx/afl/).
10840 o Major bugfixes (scheduler):
10841 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
10842 caused the channel scheduler to behave more or less randomly,
10843 rather than preferring channels with higher-priority circuits.
10844 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
10846 o Major bugfixes (security, also in 0.2.9.9):
10847 - Downgrade the "-ftrapv" option from "always on" to "only on when
10848 --enable-expensive-hardening is provided." This hardening option,
10849 like others, can turn survivable bugs into crashes--and having it
10850 on by default made a (relatively harmless) integer overflow bug
10851 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
10852 bugfix on 0.2.9.1-alpha.
10854 o Minor feature (client):
10855 - Enable IPv6 traffic on the SocksPort by default. To disable this,
10856 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
10858 o Minor feature (fallback scripts):
10859 - Add a check_existing mode to updateFallbackDirs.py, which checks
10860 if fallbacks in the hard-coded list are working. Closes ticket
10861 20174. Patch by haxxpop.
10863 o Minor feature (protocol versioning):
10864 - Add new protocol version for proposal 224. HSIntro now advertises
10865 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
10867 o Minor features (ciphersuite selection):
10868 - Allow relays to accept a wider range of ciphersuites, including
10869 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
10870 - Clients now advertise a list of ciphersuites closer to the ones
10871 preferred by Firefox. Closes part of ticket 15426.
10873 o Minor features (controller):
10874 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
10875 shared-random values to the controller. Closes ticket 19925.
10876 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
10877 rather than "unrecognized." Closes ticket 20389; patch from
10880 o Minor features (controller, configuration):
10881 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
10882 and so on, now comes with a __*Port variant that will not be saved
10883 to the torrc file by the controller's SAVECONF command. This
10884 change allows TorBrowser to set up a single-use domain socket for
10885 each time it launches Tor. Closes ticket 20956.
10886 - The GETCONF command can now query options that may only be
10887 meaningful in context-sensitive lists. This allows the controller
10888 to query the mixed SocksPort/__SocksPort style options introduced
10889 in feature 20956. Implements ticket 21300.
10891 o Minor features (diagnostic, directory client):
10892 - Warn when we find an unexpected inconsistency in directory
10893 download status objects. Prevents some negative consequences of
10896 o Minor features (directory authorities):
10897 - Directory authorities now reject descriptors that claim to be
10898 malformed versions of Tor. Helps prevent exploitation of
10900 - Reject version numbers with components that exceed INT32_MAX.
10901 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
10902 Fixes bug 21450; bugfix on 0.0.8pre1.
10904 o Minor features (directory authority):
10905 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
10906 default) to control whether authorities should try to probe relays
10907 by their Ed25519 link keys. This option will go away in a few
10908 releases--unless we encounter major trouble in our ed25519 link
10909 protocol rollout, in which case it will serve as a safety option.
10911 o Minor features (directory cache):
10912 - Relays and bridges will now refuse to serve the consensus they
10913 have if they know it is too old for a client to use. Closes
10916 o Minor features (ed25519 link handshake):
10917 - Advertise support for the ed25519 link handshake using the
10918 subprotocol-versions mechanism, so that clients can tell which
10919 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
10921 o Minor features (entry guards):
10922 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
10923 break regression tests.
10924 - Require UseEntryGuards when UseBridges is set, in order to make
10925 sure bridges aren't bypassed. Resolves ticket 20502.
10927 o Minor features (fallback directories):
10928 - Allow 3 fallback relays per operator, which is safe now that we
10929 are choosing 200 fallback relays. Closes ticket 20912.
10930 - Annotate updateFallbackDirs.py with the bandwidth and consensus
10931 weight for each candidate fallback. Closes ticket 20878.
10932 - Display the relay fingerprint when downloading consensuses from
10933 fallbacks. Closes ticket 20908.
10934 - Exclude relays affected by bug 20499 from the fallback list.
10935 Exclude relays from the fallback list if they are running versions
10936 known to be affected by bug 20499, or if in our tests they deliver
10937 a stale consensus (i.e. one that expired more than 24 hours ago).
10938 Closes ticket 20539.
10939 - Make it easier to change the output sort order of fallbacks.
10940 Closes ticket 20822.
10941 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
10943 - Require fallback directories to have the same address and port for
10944 7 days (now that we have enough relays with this stability).
10945 Relays whose OnionOO stability timer is reset on restart by bug
10946 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
10947 this issue. Closes ticket 20880; maintains short-term fix
10949 - Require fallbacks to have flags for 90% of the time (weighted
10950 decaying average), rather than 95%. This allows at least 73% of
10951 clients to bootstrap in the first 5 seconds without contacting an
10952 authority. Part of ticket 18828.
10953 - Select 200 fallback directories for each release. Closes
10956 o Minor features (fingerprinting resistance, authentication):
10957 - Extend the length of RSA keys used for TLS link authentication to
10958 2048 bits. (These weren't used for forward secrecy; for forward
10959 secrecy, we used P256.) Closes ticket 13752.
10961 o Minor features (geoip):
10962 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
10965 o Minor features (geoip, also in 0.2.9.9):
10966 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
10969 o Minor features (infrastructure):
10970 - Implement smartlist_add_strdup() function. Replaces the use of
10971 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
10973 o Minor features (linting):
10974 - Enhance the changes file linter to warn on Tor versions that are
10975 prefixed with "tor-". Closes ticket 21096.
10977 o Minor features (logging):
10978 - In several places, describe unset ed25519 keys as "<unset>",
10979 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
10981 o Minor features (portability, compilation):
10982 - Autoconf now checks to determine if OpenSSL structures are opaque,
10983 instead of explicitly checking for OpenSSL version numbers. Part
10985 - Support building with recent LibreSSL code that uses opaque
10986 structures. Closes ticket 21359.
10988 o Minor features (relay):
10989 - We now allow separation of exit and relay traffic to different
10990 source IP addresses, using the OutboundBindAddressExit and
10991 OutboundBindAddressOR options respectively. Closes ticket 17975.
10992 Written by Michael Sonntag.
10994 o Minor features (reliability, crash):
10995 - Try better to detect problems in buffers where they might grow (or
10996 think they have grown) over 2 GB in size. Diagnostic for
10999 o Minor features (testing):
11000 - During 'make test-network-all', if tor logs any warnings, ask
11001 chutney to output them. Requires a recent version of chutney with
11002 the 21572 patch. Implements 21570.
11004 o Minor bugfix (control protocol):
11005 - The reply to a "GETINFO config/names" request via the control
11006 protocol now spells the type "Dependent" correctly. This is a
11007 breaking change in the control protocol. (The field seems to be
11008 ignored by the most common known controllers.) Fixes bug 18146;
11009 bugfix on 0.1.1.4-alpha.
11010 - The GETINFO extra-info/digest/<digest> command was broken because
11011 of a wrong base16 decode return value check, introduced when
11012 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
11014 o Minor bugfix (logging):
11015 - Don't recommend the use of Tor2web in non-anonymous mode.
11016 Recommending Tor2web is a bad idea because the client loses all
11017 anonymity. Tor2web should only be used in specific cases by users
11018 who *know* and understand the issues. Fixes bug 21294; bugfix
11021 o Minor bugfixes (bug resilience):
11022 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
11023 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
11024 Hans Jerry Illikainen.
11026 o Minor bugfixes (build):
11027 - Replace obsolete Autoconf macros with their modern equivalent and
11028 prevent similar issues in the future. Fixes bug 20990; bugfix
11031 o Minor bugfixes (certificate expiration time):
11032 - Avoid using link certificates that don't become valid till some
11033 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
11035 o Minor bugfixes (client):
11036 - Always recover from failures in extend_info_from_node(), in an
11037 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
11038 bugfix on 0.2.3.1-alpha.
11039 - When clients that use bridges start up with a cached consensus on
11040 disk, they were ignoring it and downloading a new one. Now they
11041 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
11043 o Minor bugfixes (code correctness):
11044 - Repair a couple of (unreachable or harmless) cases of the risky
11045 comparison-by-subtraction pattern that caused bug 21278.
11047 o Minor bugfixes (config):
11048 - Don't assert on startup when trying to get the options list and
11049 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
11050 options so of course they aren't ready yet. Fixes bug 21062;
11051 bugfix on 0.2.9.3-alpha.
11053 o Minor bugfixes (configuration):
11054 - Accept non-space whitespace characters after the severity level in
11055 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
11056 - Support "TByte" and "TBytes" units in options given in bytes.
11057 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
11058 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
11060 o Minor bugfixes (configure, autoconf):
11061 - Rename the configure option --enable-expensive-hardening to
11062 --enable-fragile-hardening. Expensive hardening makes the tor
11063 daemon abort when some kinds of issues are detected. Thus, it
11064 makes tor more at risk of remote crashes but safer against RCE or
11065 heartbleed bug category. We now try to explain this issue in a
11066 message from the configure script. Fixes bug 21290; bugfix
11069 o Minor bugfixes (consensus weight):
11070 - Add new consensus method that initializes bw weights to 1 instead
11071 of 0. This prevents a zero weight from making it all the way to
11072 the end (happens in small testing networks) and causing an error.
11073 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
11075 o Minor bugfixes (crash prevention):
11076 - Fix an (currently untriggerable, but potentially dangerous) crash
11077 bug when base32-encoding inputs whose sizes are not a multiple of
11078 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
11080 o Minor bugfixes (dead code):
11081 - Remove a redundant check for PidFile changes at runtime in
11082 options_transition_allowed(): this check is already performed
11083 regardless of whether the sandbox is active. Fixes bug 21123;
11084 bugfix on 0.2.5.4-alpha.
11086 o Minor bugfixes (descriptors):
11087 - Correctly recognise downloaded full descriptors as valid, even
11088 when using microdescriptors as circuits. This affects clients with
11089 FetchUselessDescriptors set, and may affect directory authorities.
11090 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
11092 o Minor bugfixes (directory mirrors):
11093 - Allow relays to use directory mirrors without a DirPort: these
11094 relays need to be contacted over their ORPorts using a begindir
11095 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
11096 - Clarify the message logged when a remote relay is unexpectedly
11097 missing an ORPort or DirPort: users were confusing this with a
11098 local port. Fixes another case of bug 20711; bugfix
11101 o Minor bugfixes (directory system):
11102 - Bridges and relays now use microdescriptors (like clients do)
11103 rather than old-style router descriptors. Now bridges will blend
11104 in with clients in terms of the circuits they build. Fixes bug
11105 6769; bugfix on 0.2.3.2-alpha.
11106 - Download all consensus flavors, descriptors, and authority
11107 certificates when FetchUselessDescriptors is set, regardless of
11108 whether tor is a directory cache or not. Fixes bug 20667; bugfix
11109 on all recent tor versions.
11111 o Minor bugfixes (documentation):
11112 - Update the tor manual page to document every option that can not
11113 be changed while tor is running. Fixes bug 21122.
11115 o Minor bugfixes (ed25519 certificates):
11116 - Correctly interpret ed25519 certificates that would expire some
11117 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
11119 o Minor bugfixes (fallback directories):
11120 - Avoid checking fallback candidates' DirPorts if they are down in
11121 OnionOO. When a relay operator has multiple relays, this
11122 prioritizes relays that are up over relays that are down. Fixes
11123 bug 20926; bugfix on 0.2.8.3-alpha.
11124 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
11125 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
11126 - Stop failing when a relay has no uptime data in
11127 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
11129 o Minor bugfixes (hidden service):
11130 - Clean up the code for expiring intro points with no associated
11131 circuits. It was causing, rarely, a service with some expiring
11132 introduction points to not open enough additional introduction
11133 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
11134 - Resolve two possible underflows which could lead to creating and
11135 closing a lot of introduction point circuits in a non-stop loop.
11136 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
11137 - Stop setting the torrc option HiddenServiceStatistics to "0" just
11138 because we're not a bridge or relay. Instead, we preserve whatever
11139 value the user set (or didn't set). Fixes bug 21150; bugfix
11142 o Minor bugfixes (hidden services):
11143 - Make hidden services check for failed intro point connections,
11144 even when they have exceeded their intro point creation limit.
11145 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
11146 - Make hidden services with 8 to 10 introduction points check for
11147 failed circuits immediately after startup. Previously, they would
11148 wait for 5 minutes before performing their first checks. Fixes bug
11149 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
11150 - Stop ignoring misconfigured hidden services. Instead, refuse to
11151 start tor until the misconfigurations have been corrected. Fixes
11152 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
11155 o Minor bugfixes (IPv6):
11156 - Make IPv6-using clients try harder to find an IPv6 directory
11157 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
11158 - When IPv6 addresses have not been downloaded yet (microdesc
11159 consensus documents don't list relay IPv6 addresses), use hard-
11160 coded addresses for authorities, fallbacks, and configured
11161 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
11162 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
11164 o Minor bugfixes (memory leak at exit):
11165 - Fix a small harmless memory leak at exit of the previously unused
11166 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
11169 o Minor bugfixes (onion services):
11170 - Allow the number of introduction points to be as low as 0, rather
11171 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
11173 o Minor bugfixes (portability):
11174 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
11175 It is supported by OpenBSD itself, and also by most OpenBSD
11176 variants (such as Bitrig). Fixes bug 20980; bugfix
11179 o Minor bugfixes (portability, also in 0.2.9.9):
11180 - Avoid crashing when Tor is built using headers that contain
11181 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
11182 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
11184 - Fix Libevent detection on platforms without Libevent 1 headers
11185 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
11187 o Minor bugfixes (relay):
11188 - Avoid a double-marked-circuit warning that could happen when we
11189 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
11191 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
11192 initializing the keys would reset the DataDirectory to 0700
11193 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
11194 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
11196 o Minor bugfixes (testing):
11197 - Fix Raspbian build issues related to missing socket errno in
11198 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch by "hein".
11199 - Remove undefined behavior from the backtrace generator by removing
11200 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
11201 - Use bash in src/test/test-network.sh. This ensures we reliably
11202 call chutney's newer tools/test-network.sh when available. Fixes
11203 bug 21562; bugfix on 0.2.9.1-alpha.
11205 o Minor bugfixes (tor-resolve):
11206 - The tor-resolve command line tool now rejects hostnames over 255
11207 characters in length. Previously, it would silently truncate them,
11208 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
11209 Patch by "junglefowl".
11211 o Minor bugfixes (unit tests):
11212 - Allow the unit tests to pass even when DNS lookups of bogus
11213 addresses do not fail as expected. Fixes bug 20862 and 20863;
11214 bugfix on unit tests introduced in 0.2.8.1-alpha
11215 through 0.2.9.4-alpha.
11217 o Minor bugfixes (util):
11218 - When finishing writing a file to disk, if we were about to replace
11219 the file with the temporary file created before and we fail to
11220 replace it, remove the temporary file so it doesn't stay on disk.
11221 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
11223 o Minor bugfixes (Windows services):
11224 - Be sure to initialize the monotonic time subsystem before using
11225 it, even when running as an NT service. Fixes bug 21356; bugfix
11228 o Minor bugfixes (Windows):
11229 - Check for getpagesize before using it to mmap files. This fixes
11230 compilation in some MinGW environments. Fixes bug 20530; bugfix on
11231 0.1.2.1-alpha. Reported by "ice".
11233 o Code simplification and refactoring:
11234 - Abolish all global guard context in entrynodes.c; replace with new
11235 guard_selection_t structure as preparation for proposal 271.
11236 Closes ticket 19858.
11237 - Extract magic numbers in circuituse.c into defined variables.
11238 - Introduce rend_service_is_ephemeral() that tells if given onion
11239 service is ephemeral. Replace unclear NULL-checkings for service
11240 directory with this function. Closes ticket 20526.
11241 - Refactor circuit_is_available_for_use to remove unnecessary check.
11242 - Refactor circuit_predict_and_launch_new for readability and
11243 testability. Closes ticket 18873.
11244 - Refactor code to manipulate global_origin_circuit_list into
11245 separate functions. Closes ticket 20921.
11246 - Refactor large if statement in purpose_needs_anonymity to use
11247 switch statement instead. Closes part of ticket 20077.
11248 - Refactor the hashing API to return negative values for errors, as
11249 is done as throughout the codebase. Closes ticket 20717.
11250 - Remove data structures that were used to index or_connection
11251 objects by their RSA identity digests. These structures are fully
11252 redundant with the similar structures used in the
11253 channel abstraction.
11254 - Remove duplicate code in the channel_write_*cell() functions.
11255 Closes ticket 13827; patch from Pingl.
11256 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
11257 use only purpose_needs_anonymity. Closes part of ticket 20077.
11258 - The code to generate and parse EXTEND and EXTEND2 cells has been
11259 replaced with code automatically generated by the
11262 o Documentation (formatting):
11263 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
11264 blocks were incorrectly appearing. Closes ticket 20885.
11266 o Documentation (man page):
11267 - Clarify many options in tor.1 and add some min/max values for
11268 HiddenService options. Closes ticket 21058.
11271 - Change '1' to 'weight_scale' in consensus bw weights calculation
11272 comments, as that is reality. Closes ticket 20273. Patch
11274 - Clarify that when ClientRejectInternalAddresses is enabled (which
11275 is the default), multicast DNS hostnames for machines on the local
11276 network (of the form *.local) are also rejected. Closes
11278 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
11279 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix on 0.2.5.6-alpha.
11280 - Include the "TBits" unit in Tor's man page. Fixes part of bug
11281 20622; bugfix on 0.2.5.1-alpha.
11282 - Small fixes to the fuzzing documentation. Closes ticket 21472.
11283 - Stop the man page from incorrectly stating that HiddenServiceDir
11284 must already exist. Fixes 20486.
11285 - Update the description of the directory server options in the
11286 manual page, to clarify that a relay no longer needs to set
11287 DirPort in order to be a directory cache. Closes ticket 21720.
11289 o Removed features:
11290 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
11291 limit for relays running on a single IP applies to authority IP
11292 addresses as well as to non-authority IP addresses. Closes
11294 - The UseDirectoryGuards torrc option no longer exists: all users
11295 that use entry guards will also use directory guards. Related to
11296 proposal 271; implements part of ticket 20831.
11299 - Add tests for networkstatus_compute_bw_weights_v10.
11300 - Add unit tests circuit_predict_and_launch_new.
11301 - Extract dummy_origin_circuit_new so it can be used by other
11303 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
11304 from "overcaffeinated".
11305 - Perform the coding style checks when running the tests and fail
11306 when coding style violations are found. Closes ticket 5500.
11309 Changes in version 0.2.8.13 - 2017-03-03
11310 Tor 0.2.8.13 backports a security fix from later Tor
11311 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
11312 this release, if for some reason they cannot upgrade to a later
11313 release series, and if they build Tor with the --enable-expensive-hardening
11316 Note that support for Tor 0.2.8.x is ending next year: we will not issue
11317 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
11318 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
11320 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
11321 - Fix an integer underflow bug when comparing malformed Tor
11322 versions. This bug could crash Tor when built with
11323 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
11324 0.2.9.8, which were built with -ftrapv by default. In other cases
11325 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
11326 on 0.0.8pre1. Found by OSS-Fuzz.
11328 o Minor features (geoip):
11329 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
11333 Changes in version 0.2.7.7 - 2017-03-03
11334 Tor 0.2.7.7 backports a number of security fixes from later Tor
11335 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
11336 this release, if for some reason they cannot upgrade to a later
11339 Note that support for Tor 0.2.7.x is ending this year: we will not issue
11340 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
11341 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
11343 o Directory authority changes (backport from 0.2.8.5-rc):
11344 - Urras is no longer a directory authority. Closes ticket 19271.
11346 o Directory authority changes (backport from 0.2.9.2-alpha):
11347 - The "Tonga" bridge authority has been retired; the new bridge
11348 authority is "Bifroest". Closes tickets 19728 and 19690.
11350 o Directory authority key updates (backport from 0.2.8.1-alpha):
11351 - Update the V3 identity key for the dannenberg directory authority:
11352 it was changed on 18 November 2015. Closes task 17906. Patch
11355 o Major bugfixes (parsing, security, backport from 0.2.9.8):
11356 - Fix a bug in parsing that could cause clients to read a single
11357 byte past the end of an allocated region. This bug could be used
11358 to cause hardened clients (built with --enable-expensive-hardening)
11359 to crash if they tried to visit a hostile hidden service. Non-
11360 hardened clients are only affected depending on the details of
11361 their platform's memory allocator. Fixes bug 21018; bugfix on
11362 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
11363 2016-12-002 and as CVE-2016-1254.
11365 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
11366 - Stop a crash that could occur when a client running with DNSPort
11367 received a query with multiple address types, and the first
11368 address type was not supported. Found and fixed by Scott Dial.
11369 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
11370 - Prevent a class of security bugs caused by treating the contents
11371 of a buffer chunk as if they were a NUL-terminated string. At
11372 least one such bug seems to be present in all currently used
11373 versions of Tor, and would allow an attacker to remotely crash
11374 most Tor instances, especially those compiled with extra compiler
11375 hardening. With this defense in place, such bugs can't crash Tor,
11376 though we should still fix them as they occur. Closes ticket
11377 20384 (TROVE-2016-10-001).
11379 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
11380 - Avoid a difficult-to-trigger heap corruption attack when extending
11381 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
11382 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
11383 Reported by Guido Vranken.
11385 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
11386 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
11387 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
11389 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
11390 - If OpenSSL fails to generate an RSA key, do not retain a dangling
11391 pointer to the previous (uninitialized) key value. The impact here
11392 should be limited to a difficult-to-trigger crash, if OpenSSL is
11393 running an engine that makes key generation failures possible, or
11394 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
11395 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
11398 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
11399 - Fix an integer underflow bug when comparing malformed Tor
11400 versions. This bug could crash Tor when built with
11401 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
11402 0.2.9.8, which were built with -ftrapv by default. In other cases
11403 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
11404 on 0.0.8pre1. Found by OSS-Fuzz.
11406 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
11407 - Make memwipe() do nothing when passed a NULL pointer or buffer of
11408 zero size. Check size argument to memwipe() for underflow. Fixes
11409 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
11412 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
11413 - Make Tor survive errors involving connections without a
11414 corresponding event object. Previously we'd fail with an
11415 assertion; now we produce a log message. Related to bug 16248.
11417 o Minor features (geoip):
11418 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
11422 Changes in version 0.2.6.11 - 2017-03-03
11423 Tor 0.2.6.11 backports a number of security fixes from later Tor
11424 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
11425 this release, if for some reason they cannot upgrade to a later
11428 Note that support for Tor 0.2.6.x is ending this year: we will not issue
11429 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
11430 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
11432 o Directory authority changes (backport from 0.2.8.5-rc):
11433 - Urras is no longer a directory authority. Closes ticket 19271.
11435 o Directory authority changes (backport from 0.2.9.2-alpha):
11436 - The "Tonga" bridge authority has been retired; the new bridge
11437 authority is "Bifroest". Closes tickets 19728 and 19690.
11439 o Directory authority key updates (backport from 0.2.8.1-alpha):
11440 - Update the V3 identity key for the dannenberg directory authority:
11441 it was changed on 18 November 2015. Closes task 17906. Patch
11444 o Major features (security fixes, backport from 0.2.9.4-alpha):
11445 - Prevent a class of security bugs caused by treating the contents
11446 of a buffer chunk as if they were a NUL-terminated string. At
11447 least one such bug seems to be present in all currently used
11448 versions of Tor, and would allow an attacker to remotely crash
11449 most Tor instances, especially those compiled with extra compiler
11450 hardening. With this defense in place, such bugs can't crash Tor,
11451 though we should still fix them as they occur. Closes ticket
11452 20384 (TROVE-2016-10-001).
11454 o Major bugfixes (parsing, security, backport from 0.2.9.8):
11455 - Fix a bug in parsing that could cause clients to read a single
11456 byte past the end of an allocated region. This bug could be used
11457 to cause hardened clients (built with --enable-expensive-hardening)
11458 to crash if they tried to visit a hostile hidden service. Non-
11459 hardened clients are only affected depending on the details of
11460 their platform's memory allocator. Fixes bug 21018; bugfix on
11461 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
11462 2016-12-002 and as CVE-2016-1254.
11464 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
11465 - Stop a crash that could occur when a client running with DNSPort
11466 received a query with multiple address types, and the first
11467 address type was not supported. Found and fixed by Scott Dial.
11468 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
11470 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
11471 - Fix an error that could cause us to read 4 bytes before the
11472 beginning of an openssl string. This bug could be used to cause
11473 Tor to crash on systems with unusual malloc implementations, or
11474 systems with unusual hardening installed. Fixes bug 17404; bugfix
11477 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
11478 - Avoid a difficult-to-trigger heap corruption attack when extending
11479 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
11480 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
11481 Reported by Guido Vranken.
11483 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
11484 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
11485 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
11487 o Major bugfixes (guard selection, backport from 0.2.7.6):
11488 - Actually look at the Guard flag when selecting a new directory
11489 guard. When we implemented the directory guard design, we
11490 accidentally started treating all relays as if they have the Guard
11491 flag during guard selection, leading to weaker anonymity and worse
11492 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
11495 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
11496 - If OpenSSL fails to generate an RSA key, do not retain a dangling
11497 pointer to the previous (uninitialized) key value. The impact here
11498 should be limited to a difficult-to-trigger crash, if OpenSSL is
11499 running an engine that makes key generation failures possible, or
11500 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
11501 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
11504 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
11505 - Fix an integer underflow bug when comparing malformed Tor
11506 versions. This bug could crash Tor when built with
11507 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
11508 0.2.9.8, which were built with -ftrapv by default. In other cases
11509 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
11510 on 0.0.8pre1. Found by OSS-Fuzz.
11512 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
11513 - Make memwipe() do nothing when passed a NULL pointer or buffer of
11514 zero size. Check size argument to memwipe() for underflow. Fixes
11515 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
11518 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
11519 - Make Tor survive errors involving connections without a
11520 corresponding event object. Previously we'd fail with an
11521 assertion; now we produce a log message. Related to bug 16248.
11523 o Minor features (geoip):
11524 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
11527 o Minor bugfixes (compilation, backport from 0.2.7.6):
11528 - Fix a compilation warning with Clang 3.6: Do not check the
11529 presence of an address which can never be NULL. Fixes bug 17781.
11532 Changes in version 0.2.5.13 - 2017-03-03
11533 Tor 0.2.5.13 backports a number of security fixes from later Tor
11534 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
11535 this release, if for some reason they cannot upgrade to a later
11538 Note that support for Tor 0.2.5.x is ending next year: we will not issue
11539 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
11540 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
11542 o Directory authority changes (backport from 0.2.8.5-rc):
11543 - Urras is no longer a directory authority. Closes ticket 19271.
11545 o Directory authority changes (backport from 0.2.9.2-alpha):
11546 - The "Tonga" bridge authority has been retired; the new bridge
11547 authority is "Bifroest". Closes tickets 19728 and 19690.
11549 o Directory authority key updates (backport from 0.2.8.1-alpha):
11550 - Update the V3 identity key for the dannenberg directory authority:
11551 it was changed on 18 November 2015. Closes task 17906. Patch
11554 o Major features (security fixes, backport from 0.2.9.4-alpha):
11555 - Prevent a class of security bugs caused by treating the contents
11556 of a buffer chunk as if they were a NUL-terminated string. At
11557 least one such bug seems to be present in all currently used
11558 versions of Tor, and would allow an attacker to remotely crash
11559 most Tor instances, especially those compiled with extra compiler
11560 hardening. With this defense in place, such bugs can't crash Tor,
11561 though we should still fix them as they occur. Closes ticket
11562 20384 (TROVE-2016-10-001).
11564 o Major bugfixes (parsing, security, backport from 0.2.9.8):
11565 - Fix a bug in parsing that could cause clients to read a single
11566 byte past the end of an allocated region. This bug could be used
11567 to cause hardened clients (built with --enable-expensive-hardening)
11568 to crash if they tried to visit a hostile hidden service. Non-
11569 hardened clients are only affected depending on the details of
11570 their platform's memory allocator. Fixes bug 21018; bugfix on
11571 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
11572 2016-12-002 and as CVE-2016-1254.
11574 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
11575 - Stop a crash that could occur when a client running with DNSPort
11576 received a query with multiple address types, and the first
11577 address type was not supported. Found and fixed by Scott Dial.
11578 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
11580 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
11581 - Fix an error that could cause us to read 4 bytes before the
11582 beginning of an openssl string. This bug could be used to cause
11583 Tor to crash on systems with unusual malloc implementations, or
11584 systems with unusual hardening installed. Fixes bug 17404; bugfix
11587 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
11588 - Avoid a difficult-to-trigger heap corruption attack when extending
11589 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
11590 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
11591 Reported by Guido Vranken.
11593 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
11594 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
11595 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
11597 o Major bugfixes (guard selection, backport from 0.2.7.6):
11598 - Actually look at the Guard flag when selecting a new directory
11599 guard. When we implemented the directory guard design, we
11600 accidentally started treating all relays as if they have the Guard
11601 flag during guard selection, leading to weaker anonymity and worse
11602 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
11605 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
11606 - If OpenSSL fails to generate an RSA key, do not retain a dangling
11607 pointer to the previous (uninitialized) key value. The impact here
11608 should be limited to a difficult-to-trigger crash, if OpenSSL is
11609 running an engine that makes key generation failures possible, or
11610 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
11611 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
11614 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
11615 - Fix an integer underflow bug when comparing malformed Tor
11616 versions. This bug could crash Tor when built with
11617 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
11618 0.2.9.8, which were built with -ftrapv by default. In other cases
11619 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
11620 on 0.0.8pre1. Found by OSS-Fuzz.
11622 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
11623 - Make memwipe() do nothing when passed a NULL pointer or buffer of
11624 zero size. Check size argument to memwipe() for underflow. Fixes
11625 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
11628 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
11629 - Make Tor survive errors involving connections without a
11630 corresponding event object. Previously we'd fail with an
11631 assertion; now we produce a log message. Related to bug 16248.
11633 o Minor features (geoip):
11634 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
11637 o Minor bugfixes (compilation, backport from 0.2.7.6):
11638 - Fix a compilation warning with Clang 3.6: Do not check the
11639 presence of an address which can never be NULL. Fixes bug 17781.
11641 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
11642 - Check for failures from crypto_early_init, and refuse to continue.
11643 A previous typo meant that we could keep going with an
11644 uninitialized crypto library, and would have OpenSSL initialize
11645 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
11646 when implementing ticket 4900. Patch by "teor".
11648 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
11649 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
11650 a client authorized hidden service. Fixes bug 15823; bugfix
11654 Changes in version 0.2.4.28 - 2017-03-03
11655 Tor 0.2.4.28 backports a number of security fixes from later Tor
11656 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
11657 this release, if for some reason they cannot upgrade to a later
11660 Note that support for Tor 0.2.4.x is ending soon: we will not issue
11661 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
11662 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
11664 o Directory authority changes (backport from 0.2.8.5-rc):
11665 - Urras is no longer a directory authority. Closes ticket 19271.
11667 o Directory authority changes (backport from 0.2.9.2-alpha):
11668 - The "Tonga" bridge authority has been retired; the new bridge
11669 authority is "Bifroest". Closes tickets 19728 and 19690.
11671 o Directory authority key updates (backport from 0.2.8.1-alpha):
11672 - Update the V3 identity key for the dannenberg directory authority:
11673 it was changed on 18 November 2015. Closes task 17906. Patch
11676 o Major features (security fixes, backport from 0.2.9.4-alpha):
11677 - Prevent a class of security bugs caused by treating the contents
11678 of a buffer chunk as if they were a NUL-terminated string. At
11679 least one such bug seems to be present in all currently used
11680 versions of Tor, and would allow an attacker to remotely crash
11681 most Tor instances, especially those compiled with extra compiler
11682 hardening. With this defense in place, such bugs can't crash Tor,
11683 though we should still fix them as they occur. Closes ticket
11684 20384 (TROVE-2016-10-001).
11686 o Major bugfixes (parsing, security, backport from 0.2.9.8):
11687 - Fix a bug in parsing that could cause clients to read a single
11688 byte past the end of an allocated region. This bug could be used
11689 to cause hardened clients (built with --enable-expensive-hardening)
11690 to crash if they tried to visit a hostile hidden service. Non-
11691 hardened clients are only affected depending on the details of
11692 their platform's memory allocator. Fixes bug 21018; bugfix on
11693 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
11694 2016-12-002 and as CVE-2016-1254.
11696 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
11697 - Fix an error that could cause us to read 4 bytes before the
11698 beginning of an openssl string. This bug could be used to cause
11699 Tor to crash on systems with unusual malloc implementations, or
11700 systems with unusual hardening installed. Fixes bug 17404; bugfix
11703 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
11704 - Avoid a difficult-to-trigger heap corruption attack when extending
11705 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
11706 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
11707 Reported by Guido Vranken.
11709 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
11710 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
11711 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
11713 o Major bugfixes (guard selection, backport from 0.2.7.6):
11714 - Actually look at the Guard flag when selecting a new directory
11715 guard. When we implemented the directory guard design, we
11716 accidentally started treating all relays as if they have the Guard
11717 flag during guard selection, leading to weaker anonymity and worse
11718 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
11721 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
11722 - If OpenSSL fails to generate an RSA key, do not retain a dangling
11723 pointer to the previous (uninitialized) key value. The impact here
11724 should be limited to a difficult-to-trigger crash, if OpenSSL is
11725 running an engine that makes key generation failures possible, or
11726 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
11727 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
11730 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
11731 - Fix an integer underflow bug when comparing malformed Tor
11732 versions. This bug could crash Tor when built with
11733 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
11734 0.2.9.8, which were built with -ftrapv by default. In other cases
11735 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
11736 on 0.0.8pre1. Found by OSS-Fuzz.
11738 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
11739 - Make memwipe() do nothing when passed a NULL pointer or buffer of
11740 zero size. Check size argument to memwipe() for underflow. Fixes
11741 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
11744 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
11745 - Make Tor survive errors involving connections without a
11746 corresponding event object. Previously we'd fail with an
11747 assertion; now we produce a log message. Related to bug 16248.
11749 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
11750 - Make it harder for attackers to overload hidden services with
11751 introductions, by blocking multiple introduction requests on the
11752 same circuit. Resolves ticket 15515.
11754 o Minor features (geoip):
11755 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
11758 o Minor bugfixes (compilation, backport from 0.2.7.6):
11759 - Fix a compilation warning with Clang 3.6: Do not check the
11760 presence of an address which can never be NULL. Fixes bug 17781.
11762 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
11763 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
11764 a client authorized hidden service. Fixes bug 15823; bugfix
11768 Changes in version 0.2.9.10 - 2017-03-01
11769 Tor 0.2.9.10 backports a security fix from later Tor release. It also
11770 includes fixes for some major issues affecting directory authorities,
11771 LibreSSL compatibility, and IPv6 correctness.
11773 The Tor 0.2.9.x release series is now marked as a long-term-support
11774 series. We intend to backport security fixes to 0.2.9.x until at
11775 least January of 2020.
11777 o Major bugfixes (directory authority, 0.3.0.3-alpha):
11778 - During voting, when marking a relay as a probable sybil, do not
11779 clear its BadExit flag: sybils can still be bad in other ways
11780 too. (We still clear the other flags.) Fixes bug 21108; bugfix
11783 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
11784 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
11785 any IPv6 addresses. Instead, only reject a port over IPv6 if the
11786 exit policy rejects that port on more than an IPv6 /16 of
11787 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
11788 which rejected a relay's own IPv6 address by default. Fixes bug
11789 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
11791 o Major bugfixes (parsing, also in 0.3.0.4-rc):
11792 - Fix an integer underflow bug when comparing malformed Tor
11793 versions. This bug could crash Tor when built with
11794 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
11795 0.2.9.8, which were built with -ftrapv by default. In other cases
11796 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
11797 on 0.0.8pre1. Found by OSS-Fuzz.
11799 o Minor features (directory authorities, also in 0.3.0.4-rc):
11800 - Directory authorities now reject descriptors that claim to be
11801 malformed versions of Tor. Helps prevent exploitation of
11803 - Reject version numbers with components that exceed INT32_MAX.
11804 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
11805 Fixes bug 21450; bugfix on 0.0.8pre1.
11807 o Minor features (geoip):
11808 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
11811 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
11812 - Autoconf now checks to determine if OpenSSL structures are opaque,
11813 instead of explicitly checking for OpenSSL version numbers. Part
11815 - Support building with recent LibreSSL code that uses opaque
11816 structures. Closes ticket 21359.
11818 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
11819 - Repair a couple of (unreachable or harmless) cases of the risky
11820 comparison-by-subtraction pattern that caused bug 21278.
11822 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
11823 - The tor-resolve command line tool now rejects hostnames over 255
11824 characters in length. Previously, it would silently truncate them,
11825 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
11826 Patch by "junglefowl".
11829 Changes in version 0.2.9.9 - 2017-01-23
11830 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
11831 cause relays and clients to crash, even if they were not built with
11832 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
11833 versions, and also affects 0.3.0.1-alpha: all relays running an affected
11834 version should upgrade.
11836 This release also resolves a client-side onion service reachability
11837 bug, and resolves a pair of small portability issues.
11839 o Major bugfixes (security):
11840 - Downgrade the "-ftrapv" option from "always on" to "only on when
11841 --enable-expensive-hardening is provided." This hardening option,
11842 like others, can turn survivable bugs into crashes -- and having
11843 it on by default made a (relatively harmless) integer overflow bug
11844 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
11845 bugfix on 0.2.9.1-alpha.
11847 o Major bugfixes (client, onion service):
11848 - Fix a client-side onion service reachability bug, where multiple
11849 socks requests to an onion service (or a single slow request)
11850 could cause us to mistakenly mark some of the service's
11851 introduction points as failed, and we cache that failure so
11852 eventually we run out and can't reach the service. Also resolves a
11853 mysterious "Remote server sent bogus reason code 65021" log
11854 warning. The bug was introduced in ticket 17218, where we tried to
11855 remember the circuit end reason as a uint16_t, which mangled
11856 negative values. Partially fixes bug 21056 and fixes bug 20307;
11857 bugfix on 0.2.8.1-alpha.
11859 o Minor features (geoip):
11860 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
11863 o Minor bugfixes (portability):
11864 - Avoid crashing when Tor is built using headers that contain
11865 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
11866 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
11868 - Fix Libevent detection on platforms without Libevent 1 headers
11869 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
11872 Changes in version 0.2.8.12 - 2016-12-19
11873 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
11874 below) where Tor clients could crash when attempting to visit a
11875 hostile hidden service. Clients are recommended to upgrade as packages
11876 become available for their systems.
11878 It also includes an updated list of fallback directories, backported
11881 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
11882 backported to 0.2.8 in the future.
11884 o Major bugfixes (parsing, security, backported from 0.2.9.8):
11885 - Fix a bug in parsing that could cause clients to read a single
11886 byte past the end of an allocated region. This bug could be used
11887 to cause hardened clients (built with --enable-expensive-hardening)
11888 to crash if they tried to visit a hostile hidden service. Non-
11889 hardened clients are only affected depending on the details of
11890 their platform's memory allocator. Fixes bug 21018; bugfix on
11891 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
11892 2016-12-002 and as CVE-2016-1254.
11894 o Minor features (fallback directory list, backported from 0.2.9.8):
11895 - Replace the 81 remaining fallbacks of the 100 originally
11896 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
11897 fallbacks (123 new, 54 existing, 27 removed) generated in December
11898 2016. Resolves ticket 20170.
11900 o Minor features (geoip, backported from 0.2.9.7-rc):
11901 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
11905 Changes in version 0.2.9.8 - 2016-12-19
11906 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
11908 The Tor 0.2.9 series makes mandatory a number of security features
11909 that were formerly optional. It includes support for a new shared-
11910 randomness protocol that will form the basis for next generation
11911 hidden services, includes a single-hop hidden service mode for
11912 optimizing .onion services that don't actually want to be hidden,
11913 tries harder not to overload the directory authorities with excessive
11914 downloads, and supports a better protocol versioning scheme for
11915 improved compatibility with other implementations of the Tor protocol.
11917 And of course, there are numerous other bugfixes and improvements.
11919 This release also includes a fix for a medium-severity issue (bug
11920 21018 below) where Tor clients could crash when attempting to visit a
11921 hostile hidden service. Clients are recommended to upgrade as packages
11922 become available for their systems.
11924 Below are listed the changes since Tor 0.2.8.11. For a list of
11925 changes since 0.2.9.7-rc, see the ChangeLog file.
11927 o New system requirements:
11928 - When building with OpenSSL, Tor now requires version 1.0.1 or
11929 later. OpenSSL 1.0.0 and earlier are no longer supported by the
11930 OpenSSL team, and should not be used. Closes ticket 20303.
11931 - Tor now requires Libevent version 2.0.10-stable or later. Older
11932 versions of Libevent have less efficient backends for several
11933 platforms, and lack the DNS code that we use for our server-side
11934 DNS support. This implements ticket 19554.
11935 - Tor now requires zlib version 1.2 or later, for security,
11936 efficiency, and (eventually) gzip support. (Back when we started,
11937 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
11938 released in 2003. We recommend the latest version.)
11940 o Deprecated features:
11941 - A number of DNS-cache-related sub-options for client ports are now
11942 deprecated for security reasons, and may be removed in a future
11943 version of Tor. (We believe that client-side DNS caching is a bad
11944 idea for anonymity, and you should not turn it on.) The options
11945 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
11946 UseIPv4Cache, and UseIPv6Cache.
11947 - A number of options are deprecated for security reasons, and may
11948 be removed in a future version of Tor. The options are:
11949 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
11950 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
11951 CloseHSClientCircuitsImmediatelyOnTimeout,
11952 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
11953 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
11954 UseNTorHandshake, and WarnUnsafeSocks.
11955 - The *ListenAddress options are now deprecated as unnecessary: the
11956 corresponding *Port options should be used instead. These options
11957 may someday be removed. The affected options are:
11958 ControlListenAddress, DNSListenAddress, DirListenAddress,
11959 NATDListenAddress, ORListenAddress, SocksListenAddress,
11960 and TransListenAddress.
11962 o Major bugfixes (parsing, security, new since 0.2.9.7-rc):
11963 - Fix a bug in parsing that could cause clients to read a single
11964 byte past the end of an allocated region. This bug could be used
11965 to cause hardened clients (built with --enable-expensive-hardening)
11966 to crash if they tried to visit a hostile hidden service. Non-
11967 hardened clients are only affected depending on the details of
11968 their platform's memory allocator. Fixes bug 21018; bugfix on
11969 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
11970 2016-12-002 and as CVE-2016-1254.
11972 o Major features (build, hardening):
11973 - Tor now builds with -ftrapv by default on compilers that support
11974 it. This option detects signed integer overflow (which C forbids),
11975 and turns it into a hard-failure. We do not apply this option to
11976 code that needs to run in constant time to avoid side-channels;
11977 instead, we use -fwrapv in that code. Closes ticket 17983.
11978 - When --enable-expensive-hardening is selected, stop applying the
11979 clang/gcc sanitizers to code that needs to run in constant time.
11980 Although we are aware of no introduced side-channels, we are not
11981 able to prove that there are none. Related to ticket 17983.
11983 o Major features (circuit building, security):
11984 - Authorities, relays, and clients now require ntor keys in all
11985 descriptors, for all hops (except for rare hidden service protocol
11986 cases), for all circuits, and for all other roles. Part of
11988 - Authorities, relays, and clients only use ntor, except for
11989 rare cases in the hidden service protocol. Part of ticket 19163.
11991 o Major features (compilation):
11992 - Our big list of extra GCC warnings is now enabled by default when
11993 building with GCC (or with anything like Clang that claims to be
11994 GCC-compatible). To make all warnings into fatal compilation
11995 errors, pass --enable-fatal-warnings to configure. Closes
11997 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
11998 turn on C and POSIX extensions. (Previously, we attempted to do
11999 this on an ad hoc basis.) Closes ticket 19139.
12001 o Major features (directory authorities, hidden services):
12002 - Directory authorities can now perform the shared randomness
12003 protocol specified by proposal 250. Using this protocol, directory
12004 authorities generate a global fresh random value every day. In the
12005 future, this value will be used by hidden services to select
12006 HSDirs. This release implements the directory authority feature;
12007 the hidden service side will be implemented in the future as part
12008 of proposal 224. Resolves ticket 16943; implements proposal 250.
12010 o Major features (downloading, random exponential backoff):
12011 - When we fail to download an object from a directory service, wait
12012 for an (exponentially increasing) randomized amount of time before
12013 retrying, rather than a fixed interval as we did before. This
12014 prevents a group of Tor instances from becoming too synchronized,
12015 or a single Tor instance from becoming too predictable, in its
12016 download schedule. Closes ticket 15942.
12018 o Major features (resource management):
12019 - Tor can now notice it is about to run out of sockets, and
12020 preemptively close connections of lower priority. (This feature is
12021 off by default for now, since the current prioritizing method is
12022 yet not mature enough. You can enable it by setting
12023 "DisableOOSCheck 0", but watch out: it might close some sockets
12024 you would rather have it keep.) Closes ticket 18640.
12026 o Major features (single-hop "hidden" services):
12027 - Add experimental HiddenServiceSingleHopMode and
12028 HiddenServiceNonAnonymousMode options. When both are set to 1,
12029 every hidden service on that Tor instance becomes a non-anonymous
12030 Single Onion Service. Single Onions make one-hop (direct)
12031 connections to their introduction and rendezvous points. One-hop
12032 circuits make Single Onion servers easily locatable, but clients
12033 remain location-anonymous. This is compatible with the existing
12034 hidden service implementation, and works on the current Tor
12035 network without any changes to older relays or clients. Implements
12036 proposal 260, completes ticket 17178. Patch by teor and asn.
12038 o Major features (subprotocol versions):
12039 - Tor directory authorities now vote on a set of recommended
12040 "subprotocol versions", and on a set of required subprotocol
12041 versions. Clients and relays that lack support for a _required_
12042 subprotocol version will not start; those that lack support for a
12043 _recommended_ subprotocol version will warn the user to upgrade.
12044 This change allows compatible implementations of the Tor protocol(s)
12045 to exist without pretending to be 100% bug-compatible with
12046 particular releases of Tor itself. Closes ticket 19958; implements
12047 part of proposal 264.
12049 o Major bugfixes (circuit building):
12050 - Hidden service client-to-intro-point and service-to-rendezvous-
12051 point circuits use the TAP key supplied by the protocol, to avoid
12052 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
12054 o Major bugfixes (download scheduling):
12055 - Avoid resetting download status for consensuses hourly, since we
12056 already have another, smarter retry mechanism. Fixes bug 8625;
12057 bugfix on 0.2.0.9-alpha.
12058 - If a consensus expires while we are waiting for certificates to
12059 download, stop waiting for certificates.
12060 - If we stop waiting for certificates less than a minute after we
12061 started downloading them, do not consider the certificate download
12062 failure a separate failure. Fixes bug 20533; bugfix
12064 - When using exponential backoff in test networks, use a lower
12065 exponent, so the delays do not vary as much. This helps test
12066 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
12068 o Major bugfixes (exit policies):
12069 - Avoid disclosing exit outbound bind addresses, configured port
12070 bind addresses, and local interface addresses in relay descriptors
12071 by default under ExitPolicyRejectPrivate. Instead, only reject
12072 these (otherwise unlisted) addresses if
12073 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
12074 0.2.7.2-alpha. Patch by teor.
12076 o Major bugfixes (hidden services):
12077 - Allow Tor clients with appropriate controllers to work with
12078 FetchHidServDescriptors set to 0. Previously, this option also
12079 disabled descriptor cache lookup, thus breaking hidden services
12080 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
12081 - Clients now require hidden services to include the TAP keys for
12082 their intro points in the hidden service descriptor. This prevents
12083 an inadvertent upgrade to ntor, which a malicious hidden service
12084 could use to distinguish clients by consensus version. Fixes bug
12085 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
12087 o Major bugfixes (relay, resolver, logging):
12088 - For relays that don't know their own address, avoid attempting a
12089 local hostname resolve for each descriptor we download. This
12090 will cut down on the number of "Success: chose address 'x.x.x.x'"
12091 log lines, and also avoid confusing clock jumps if the resolver
12092 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
12094 o Minor features (port flags):
12095 - Add new flags to the *Port options to give finer control over which
12096 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
12097 and the synthetic flag OnionTrafficOnly, which is equivalent to
12098 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
12099 18693; patch by "teor".
12101 o Minor features (build, hardening):
12102 - Detect and work around a libclang_rt problem that would prevent
12103 clang from finding __mulodi4() on some 32-bit platforms, and thus
12104 keep -ftrapv from linking on those systems. Closes ticket 19079.
12105 - When building on a system without runtime support for the runtime
12106 hardening options, try to log a useful warning at configuration
12107 time, rather than an incomprehensible warning at link time. If
12108 expensive hardening was requested, this warning becomes an error.
12109 Closes ticket 18895.
12111 o Minor features (client, directory):
12112 - Since authorities now omit all routers that lack the Running and
12113 Valid flags, we assume that any relay listed in the consensus must
12114 have those flags. Closes ticket 20001; implements part of
12117 o Minor features (code safety):
12118 - In our integer-parsing functions, ensure that the maximum value we
12119 allow is no smaller than the minimum value. Closes ticket 19063;
12120 patch from "U+039b".
12122 o Minor features (compilation, portability):
12123 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
12126 o Minor features (config):
12127 - Warn users when descriptor and port addresses are inconsistent.
12128 Mitigates bug 13953; patch by teor.
12130 o Minor features (controller):
12131 - Allow controllers to configure basic client authorization on
12132 hidden services when they create them with the ADD_ONION controller
12133 command. Implements ticket 15588. Patch by "special".
12134 - Fire a STATUS_SERVER controller event whenever the hibernation
12135 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
12136 - Implement new GETINFO queries for all downloads that use
12137 download_status_t to schedule retries. This allows controllers to
12138 examine the schedule for pending downloads. Closes ticket 19323.
12140 o Minor features (development tools, etags):
12141 - Teach the "make tags" Makefile target how to correctly find
12142 "MOCK_IMPL" function definitions. Patch from nherring; closes
12145 o Minor features (directory authority):
12146 - After voting, if the authorities decide that a relay is not
12147 "Valid", they no longer include it in the consensus at all. Closes
12148 ticket 20002; implements part of proposal 272.
12149 - Directory authorities now only give the Guard flag to a relay if
12150 they are also giving it the Stable flag. This change allows us to
12151 simplify path selection for clients. It should have minimal effect
12152 in practice, since >99% of Guards already have the Stable flag.
12153 Implements ticket 18624.
12154 - Directory authorities now write their v3-status-votes file out to
12155 disk earlier in the consensus process, so we have a record of the
12156 votes even if we abort the consensus process. Resolves
12159 o Minor features (fallback directory list, new since 0.2.9.7-rc):
12160 - Replace the 81 remaining fallbacks of the 100 originally
12161 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
12162 fallbacks (123 new, 54 existing, 27 removed) generated in December
12163 2016. Resolves ticket 20170.
12165 o Minor features (hidden service):
12166 - Stop being so strict about the payload length of "rendezvous1"
12167 cells. We used to be locked in to the "TAP" handshake length, and
12168 now we can handle better handshakes like "ntor". Resolves
12171 o Minor features (infrastructure, time):
12172 - Tor now includes an improved timer backend, so that we can
12173 efficiently support tens or hundreds of thousands of concurrent
12174 timers, as will be needed for some of our planned anti-traffic-
12175 analysis work. This code is based on William Ahern's "timeout.c"
12176 project, which implements a "tickless hierarchical timing wheel".
12177 Closes ticket 18365.
12178 - Tor now uses the operating system's monotonic timers (where
12179 available) for internal fine-grained timing. Previously we would
12180 look at the system clock, and then attempt to compensate for the
12181 clock running backwards. Closes ticket 18908.
12183 o Minor features (logging):
12184 - Add a set of macros to check nonfatal assertions, for internal
12185 use. Migrating more of our checks to these should help us avoid
12186 needless crash bugs. Closes ticket 18613.
12187 - Provide a more useful warning message when configured with an
12188 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
12189 - When dumping unparseable router descriptors, optionally store them
12190 in separate files, named by digest, up to a configurable size
12191 limit. You can change the size limit by setting the
12192 MaxUnparseableDescSizeToLog option, and disable this feature by
12193 setting that option to 0. Closes ticket 18322.
12195 o Minor features (performance):
12196 - Change the "optimistic data" extension from "off by default" to
12197 "on by default". The default was ordinarily overridden by a
12198 consensus option, but when clients were bootstrapping for the
12199 first time, they would not have a consensus to get the option
12200 from. Changing this default saves a round-trip during startup.
12201 Closes ticket 18815.
12203 o Minor features (relay, usability):
12204 - When the directory authorities refuse a bad relay's descriptor,
12205 encourage the relay operator to contact us. Many relay operators
12206 won't notice this line in their logs, but it's a win if even a few
12207 learn why we don't like what their relay was doing. Resolves
12210 o Minor features (security, TLS):
12211 - Servers no longer support clients that lack AES ciphersuites.
12212 (3DES is no longer considered an acceptable cipher.) We believe
12213 that no such Tor clients currently exist, since Tor has required
12214 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
12216 o Minor features (testing):
12217 - Disable memory protections on OpenBSD when performing our unit
12218 tests for memwipe(). The test deliberately invokes undefined
12219 behavior, and the OpenBSD protections interfere with this. Patch
12220 from "rubiate". Closes ticket 20066.
12221 - Move the test-network.sh script to chutney, and modify tor's test-
12222 network.sh to call the (newer) chutney version when available.
12223 Resolves ticket 19116. Patch by teor.
12224 - Use the lcov convention for marking lines as unreachable, so that
12225 we don't count them when we're generating test coverage data.
12226 Update our coverage tools to understand this convention. Closes
12228 - Our link-handshake unit tests now check that when invalid
12229 handshakes fail, they fail with the error messages we expected.
12230 - Our unit testing code that captures log messages no longer
12231 prevents them from being written out if the user asked for them
12232 (by passing --debug or --info or --notice or --warn to the "test"
12233 binary). This change prevents us from missing unexpected log
12234 messages simply because we were looking for others. Related to
12236 - The unit tests now log all warning messages with the "BUG" flag.
12237 Previously, they only logged errors by default. This change will
12238 help us make our testing code more correct, and make sure that we
12239 only hit this code when we mean to. In the meantime, however,
12240 there will be more warnings in the unit test logs than before.
12241 This is preparatory work for ticket 19999.
12242 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
12243 assertion as a test failure.
12244 - We've done significant work to make the unit tests run faster.
12246 o Minor features (testing, ipv6):
12247 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
12248 tests. Remove bridges+hs, as it's somewhat redundant. This
12249 requires a recent chutney version that supports IPv6 clients,
12250 relays, and authorities. Closes ticket 20069; patch by teor.
12251 - Add the single-onion and single-onion-ipv6 chutney targets to
12252 "make test-network-all". This requires a recent chutney version
12253 with the single onion network flavors (git c72a652 or later).
12254 Closes ticket 20072; patch by teor.
12256 o Minor features (Tor2web):
12257 - Make Tor2web clients respect ReachableAddresses. This feature was
12258 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
12259 0.2.8.7. Implements feature 20034. Patch by teor.
12261 o Minor features (unix domain sockets):
12262 - When configuring a unix domain socket for a SocksPort,
12263 ControlPort, or Hidden service, you can now wrap the address in
12264 quotes, using C-style escapes inside the quotes. This allows unix
12265 domain socket paths to contain spaces. Resolves ticket 18753.
12267 o Minor features (user interface):
12268 - Tor now supports the ability to declare options deprecated, so
12269 that we can recommend that people stop using them. Previously, this
12270 was done in an ad-hoc way. There is a new --list-deprecated-options
12271 command-line option to list all of the deprecated options. Closes
12274 o Minor features (virtual addresses):
12275 - Increase the maximum number of bits for the IPv6 virtual network
12276 prefix from 16 to 104. In this way, the condition for address
12277 allocation is less restrictive. Closes ticket 20151; feature
12280 o Minor bug fixes (circuits):
12281 - Use the CircuitBuildTimeout option whenever
12282 LearnCircuitBuildTimeout is disabled. Previously, we would respect
12283 the option when a user disabled it, but not when it was disabled
12284 because some other option was set. Fixes bug 20073; bugfix on
12285 0.2.4.12-alpha. Patch by teor.
12287 o Minor bugfixes (build):
12288 - The current Git revision when building from a local repository is
12289 now detected correctly when using git worktrees. Fixes bug 20492;
12290 bugfix on 0.2.3.9-alpha.
12292 o Minor bugfixes (relay address discovery):
12293 - Stop reordering IP addresses returned by the OS. This makes it
12294 more likely that Tor will guess the same relay IP address every
12295 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
12296 Reported by René Mayrhofer, patch by "cypherpunks".
12298 o Minor bugfixes (memory allocation):
12299 - Change how we allocate memory for large chunks on buffers, to
12300 avoid a (currently impossible) integer overflow, and to waste less
12301 space when allocating unusually large chunks. Fixes bug 20081;
12302 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
12304 o Minor bugfixes (bootstrap):
12305 - Remember the directory server we fetched the consensus or previous
12306 certificates from, and use it to fetch future authority
12307 certificates. This change improves bootstrapping performance.
12308 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
12310 o Minor bugfixes (circuits):
12311 - Make sure extend_info_from_router() is only called on servers.
12312 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
12314 o Minor bugfixes (client, fascistfirewall):
12315 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
12316 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
12318 o Minor bugfixes (client, unix domain sockets):
12319 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
12320 the client address is meaningless. Fixes bug 20261; bugfix
12323 o Minor bugfixes (code style):
12324 - Fix an integer signedness conversion issue in the case conversion
12325 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
12327 o Minor bugfixes (compilation):
12328 - Build correctly on versions of libevent2 without support for
12329 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
12331 - When building with Clang, use a full set of GCC warnings.
12332 (Previously, we included only a subset, because of the way we
12333 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
12334 - Detect Libevent2 functions correctly on systems that provide
12335 libevent2, but where libevent1 is linked with -levent. Fixes bug
12336 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
12337 - Run correctly when built on Windows build environments that
12338 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
12340 o Minor bugfixes (configuration):
12341 - When parsing quoted configuration values from the torrc file,
12342 handle Windows line endings correctly. Fixes bug 19167; bugfix on
12343 0.2.0.16-alpha. Patch from "Pingl".
12345 o Minor bugfixes (directory authority):
12346 - Authorities now sort the "package" lines in their votes, for ease
12347 of debugging. (They are already sorted in consensus documents.)
12348 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
12349 - Die with a more useful error when the operator forgets to place
12350 the authority_signing_key file into the keys directory. This
12351 avoids an uninformative assert & traceback about having an invalid
12352 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
12353 - When allowing private addresses, mark Exits that only exit to
12354 private locations as such. Fixes bug 20064; bugfix
12356 - When parsing a detached signature, make sure we use the length of
12357 the digest algorithm instead of a hardcoded DIGEST256_LEN in
12358 order to avoid comparing bytes out-of-bounds with a smaller digest
12359 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
12361 o Minor bugfixes (getpass):
12362 - Defensively fix a non-triggerable heap corruption at do_getpass()
12363 to protect ourselves from mistakes in the future. Fixes bug
12364 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
12367 o Minor bugfixes (guard selection):
12368 - Don't mark guards as unreachable if connection_connect() fails.
12369 That function fails for local reasons, so it shouldn't reveal
12370 anything about the status of the guard. Fixes bug 14334; bugfix
12372 - Use a single entry guard even if the NumEntryGuards consensus
12373 parameter is not provided. Fixes bug 17688; bugfix
12376 o Minor bugfixes (hidden services):
12377 - Increase the minimum number of internal circuits we preemptively
12378 build from 2 to 3, so a circuit is available when a client
12379 connects to another onion service. Fixes bug 13239; bugfix
12381 - Allow hidden services to run on IPv6 addresses even when the
12382 IPv6Exit option is not set. Fixes bug 18357; bugfix
12384 - Stop logging intro point details to the client log on certain
12385 error conditions. Fixed as part of bug 20012; bugfix on
12386 0.2.4.8-alpha. Patch by teor.
12387 - When deleting an ephemeral hidden service, close its intro points
12388 even if they are not completely open. Fixes bug 18604; bugfix
12390 - When configuring hidden services, check every hidden service
12391 directory's permissions. Previously, we only checked the last
12392 hidden service. Fixes bug 20529; bugfix on 0.2.6.2-alpha.
12394 o Minor bugfixes (IPv6, testing):
12395 - Check for IPv6 correctly on Linux when running test networks.
12396 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
12398 o Minor bugfixes (Linux seccomp2 sandbox):
12399 - Add permission to run the sched_yield() and sigaltstack() system
12400 calls, in order to support versions of Tor compiled with asan or
12401 ubsan code that use these calls. Now "sandbox 1" and
12402 "--enable-expensive-hardening" should be compatible on more
12403 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
12405 o Minor bugfixes (logging):
12406 - Downgrade a harmless log message about the
12407 pending_entry_connections list from "warn" to "info". Mitigates
12409 - Log a more accurate message when we fail to dump a microdescriptor.
12410 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
12411 - When logging a directory ownership mismatch, log the owning
12412 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
12413 - When we are unable to remove the bw_accounting file, do not warn
12414 if the reason we couldn't remove it was that it didn't exist.
12415 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from pastly.
12417 o Minor bugfixes (memory leak):
12418 - Fix a series of slow memory leaks related to parsing torrc files
12419 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
12420 - Avoid a small memory leak when informing worker threads about
12421 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
12422 - Fix a small memory leak when receiving AF_UNIX connections on a
12423 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
12424 - When moving a signed descriptor object from a source to an
12425 existing destination, free the allocated memory inside that
12426 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
12427 - Fix a memory leak and use-after-free error when removing entries
12428 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
12429 0.2.5.5-alpha. Patch from "cypherpunks".
12430 - Fix a small, uncommon memory leak that could occur when reading a
12431 truncated ed25519 key file. Fixes bug 18956; bugfix
12434 o Minor bugfixes (option parsing):
12435 - Count unix sockets when counting client listeners (SOCKS, Trans,
12436 NATD, and DNS). This has no user-visible behavior changes: these
12437 options are set once, and never read. Required for correct
12438 behavior in ticket 17178. Fixes bug 19677; bugfix on
12439 0.2.6.3-alpha. Patch by teor.
12441 o Minor bugfixes (options):
12442 - Check the consistency of UseEntryGuards and EntryNodes more
12443 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
12445 - Stop changing the configured value of UseEntryGuards on
12446 authorities and Tor2web clients. Fixes bug 20074; bugfix on
12447 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
12450 o Minor bugfixes (relay):
12451 - Ensure relays don't make multiple connections during bootstrap.
12452 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
12453 - Do not try to parallelize workers more than 16x without the user
12454 explicitly configuring us to do so, even if we do detect more than
12455 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
12457 o Minor bugfixes (testing):
12458 - The test-stem and test-network makefile targets now depend only on
12459 the tor binary that they are testing. Previously, they depended on
12460 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
12461 patch from "cypherpunks".
12462 - Allow clients to retry HSDirs much faster in test networks. Fixes
12463 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
12464 - Avoid a unit test failure on systems with over 16 detectable CPU
12465 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
12466 - Let backtrace tests work correctly under AddressSanitizer:
12467 disable ASAN's detection of segmentation faults while running
12468 test_bt.sh, so that we can make sure that our own backtrace
12469 generation code works. Fixes bug 18934; bugfix
12470 on 0.2.5.2-alpha. Patch from "cypherpunks".
12471 - Fix the test-network-all target on out-of-tree builds by using the
12472 correct path to the test driver script. Fixes bug 19421; bugfix
12474 - Stop spurious failures in the local interface address discovery
12475 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
12477 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
12478 removed the ECDH ciphers which caused the tests to fail on
12479 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
12480 - The tor_tls_server_info_callback unit test no longer crashes when
12481 debug-level logging is turned on. Fixes bug 20041; bugfix
12484 o Minor bugfixes (time):
12485 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
12486 bugfix on all released tor versions.
12487 - When computing the difference between two times in milliseconds,
12488 we now round to the nearest millisecond correctly. Previously, we
12489 could sometimes round in the wrong direction. Fixes bug 19428;
12490 bugfix on 0.2.2.2-alpha.
12492 o Minor bugfixes (Tor2web):
12493 - Prevent Tor2web clients from running hidden services: these services
12494 are not anonymous due to the one-hop client paths. Fixes bug
12495 19678. Patch by teor.
12497 o Minor bugfixes (user interface):
12498 - Display a more accurate number of suppressed messages in the log
12499 rate-limiter. Previously, there was a potential integer overflow
12500 in the counter. Now, if the number of messages hits a maximum, the
12501 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
12503 - Fix a typo in the passphrase prompt for the ed25519 identity key.
12504 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
12506 o Code simplification and refactoring:
12507 - Remove redundant declarations of the MIN macro. Closes
12509 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
12510 Closes ticket 18462; patch from "icanhasaccount".
12511 - Split the 600-line directory_handle_command_get function into
12512 separate functions for different URL types. Closes ticket 16698.
12515 - Add module-level internal documentation for 36 C files that
12516 previously didn't have a high-level overview. Closes ticket 20385.
12517 - Correct the IPv6 syntax in our documentation for the
12518 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
12519 - Correct the minimum bandwidth value in torrc.sample, and queue a
12520 corresponding change for torrc.minimal. Closes ticket 20085.
12521 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
12522 ticket 19153. Patch from "U+039b".
12523 - Module-level documentation for several more modules. Closes
12524 tickets 19287 and 19290.
12525 - Document the --passphrase-fd option in the tor manpage. Fixes bug
12526 19504; bugfix on 0.2.7.3-rc.
12527 - Document the default PathsNeededToBuildCircuits value that's used
12528 by clients when the directory authorities don't set
12529 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 0.2.4.10-alpha.
12530 Patch by teor, reported by Jesse V.
12531 - Fix manual for the User option: it takes a username, not a UID.
12532 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
12534 - Fix the description of the --passphrase-fd option in the
12535 tor-gencert manpage. The option is used to pass the number of a
12536 file descriptor to read the passphrase from, not to read the file
12537 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
12540 - We no longer include the (dead, deprecated) bufferevent code in
12541 Tor. Closes ticket 19450. Based on a patch from "U+039b".
12543 o Removed features:
12544 - Remove support for "GET /tor/bytes.txt" DirPort request, and
12545 "GETINFO dir-usage" controller request, which were only available
12546 via a compile-time option in Tor anyway. Feature was added in
12547 0.2.2.1-alpha. Resolves ticket 19035.
12548 - There is no longer a compile-time option to disable support for
12549 TransPort. (If you don't want TransPort, just don't use it.) Patch
12550 from "U+039b". Closes ticket 19449.
12553 - Run more workqueue tests as part of "make check". These had
12554 previously been implemented, but you needed to know special
12555 command-line options to enable them.
12556 - We now have unit tests for our code to reject zlib "compression
12557 bombs". (Fortunately, the code works fine.)
12560 Changes in version 0.2.8.11 - 2016-12-08
12561 Tor 0.2.8.11 backports fixes for additional portability issues that
12562 could prevent Tor from building correctly on OSX Sierra, or with
12563 OpenSSL 1.1. Affected users should upgrade; others can safely stay
12566 o Minor bugfixes (portability):
12567 - Avoid compilation errors when building on OSX Sierra. Sierra began
12568 to support the getentropy() and clock_gettime() APIs, but created
12569 a few problems in doing so. Tor 0.2.9 has a more thorough set of
12570 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
12571 monotonic time interfaces. Fixes bug 20865. Bugfix
12574 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
12575 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
12576 architectures. Closes ticket 20588.
12579 Changes in version 0.2.8.10 - 2016-12-02
12580 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
12581 unusable after they left standby mode. It also backports fixes for
12582 a few portability issues and a small but problematic memory leak.
12584 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
12585 - When Tor leaves standby because of a new application request, open
12586 circuits as needed to serve that request. Previously, we would
12587 potentially wait a very long time. Fixes part of bug 19969; bugfix
12590 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
12591 - Clients now respond to new application stream requests immediately
12592 when they arrive, rather than waiting up to one second before
12593 starting to handle them. Fixes part of bug 19969; bugfix
12596 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
12597 - Work around a bug in the OSX 10.12 SDK that would prevent us from
12598 successfully targeting earlier versions of OSX. Resolves
12601 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
12602 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
12603 20551; bugfix on 0.2.1.1-alpha.
12605 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
12606 - Work around a memory leak in OpenSSL 1.1 when encoding public
12607 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
12609 o Minor features (geoip):
12610 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
12614 Changes in version 0.2.8.9 - 2016-10-17
12615 Tor 0.2.8.9 backports a fix for a security hole in previous versions
12616 of Tor that would allow a remote attacker to crash a Tor client,
12617 hidden service, relay, or authority. All Tor users should upgrade to
12618 this version, or to 0.2.9.4-alpha. Patches will be released for older
12621 o Major features (security fixes, also in 0.2.9.4-alpha):
12622 - Prevent a class of security bugs caused by treating the contents
12623 of a buffer chunk as if they were a NUL-terminated string. At
12624 least one such bug seems to be present in all currently used
12625 versions of Tor, and would allow an attacker to remotely crash
12626 most Tor instances, especially those compiled with extra compiler
12627 hardening. With this defense in place, such bugs can't crash Tor,
12628 though we should still fix them as they occur. Closes ticket
12629 20384 (TROVE-2016-10-001).
12631 o Minor features (geoip):
12632 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
12636 Changes in version 0.2.8.8 - 2016-09-23
12637 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
12638 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
12639 who select public relays as their bridges.
12641 o Major bugfixes (crash):
12642 - Fix a complicated crash bug that could affect Tor clients
12643 configured to use bridges when replacing a networkstatus consensus
12644 in which one of their bridges was mentioned. OpenBSD users saw
12645 more crashes here, but all platforms were potentially affected.
12646 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
12648 o Major bugfixes (relay, OOM handler):
12649 - Fix a timing-dependent assertion failure that could occur when we
12650 tried to flush from a circuit after having freed its cells because
12651 of an out-of-memory condition. Fixes bug 20203; bugfix on
12652 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
12655 o Minor feature (fallback directories):
12656 - Remove broken fallbacks from the hard-coded fallback directory
12657 list. Closes ticket 20190; patch by teor.
12659 o Minor features (geoip):
12660 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
12664 Changes in version 0.2.8.7 - 2016-08-24
12665 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
12666 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
12667 who sets the ReachableAddresses option, and all bridges, are strongly
12668 encouraged to upgrade.
12670 o Directory authority changes:
12671 - The "Tonga" bridge authority has been retired; the new bridge
12672 authority is "Bifroest". Closes tickets 19728 and 19690.
12674 o Major bugfixes (client, security):
12675 - Only use the ReachableAddresses option to restrict the first hop
12676 in a path. In earlier versions of 0.2.8.x, it would apply to
12677 every hop in the path, with a possible degradation in anonymity
12678 for anyone using an uncommon ReachableAddress setting. Fixes bug
12679 19973; bugfix on 0.2.8.2-alpha.
12681 o Minor features (geoip):
12682 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
12685 o Minor bugfixes (compilation):
12686 - Remove an inappropriate "inline" in tortls.c that was causing
12687 warnings on older versions of GCC. Fixes bug 19903; bugfix
12690 o Minor bugfixes (fallback directories):
12691 - Avoid logging a NULL string pointer when loading fallback
12692 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
12693 and 0.2.8.1-alpha. Report and patch by "rubiate".
12696 Changes in version 0.2.8.6 - 2016-08-02
12698 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
12700 The Tor 0.2.8 series improves client bootstrapping performance,
12701 completes the authority-side implementation of improved identity
12702 keys for relays, and includes numerous bugfixes and performance
12703 improvements throughout the program. This release continues to
12704 improve the coverage of Tor's test suite. For a full list of
12705 changes since Tor 0.2.7, see the ReleaseNotes file.
12707 Below is a list of the changes since Tor 0.2.7.
12709 o New system requirements:
12710 - Tor no longer attempts to support platforms where the "time_t"
12711 type is unsigned. (To the best of our knowledge, only OpenVMS does
12712 this, and Tor has never actually built on OpenVMS.) Closes
12714 - Tor no longer supports versions of OpenSSL with a broken
12715 implementation of counter mode. (This bug was present in OpenSSL
12716 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
12717 longer runs with, these versions.
12718 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
12719 later (released in 2008 and 2009 respectively). If you are
12720 building Tor from the git repository instead of from the source
12721 distribution, and your tools are older than this, you will need to
12722 upgrade. Closes ticket 17732.
12724 o Directory authority changes:
12725 - Update the V3 identity key for the dannenberg directory authority:
12726 it was changed on 18 November 2015. Closes task 17906. Patch
12728 - Urras is no longer a directory authority. Closes ticket 19271.
12730 o Major features (directory system):
12731 - Include a trial list of default fallback directories, based on an
12732 opt-in survey of suitable relays. Doing this should make clients
12733 bootstrap more quickly and reliably, and reduce the load on the
12734 directory authorities. Closes ticket 15775. Patch by teor.
12735 Candidates identified using an OnionOO script by weasel, teor,
12736 gsathya, and karsten.
12737 - Previously only relays that explicitly opened a directory port
12738 (DirPort) accepted directory requests from clients. Now all
12739 relays, with and without a DirPort, accept and serve tunneled
12740 directory requests that they receive through their ORPort. You can
12741 disable this behavior using the new DirCache option. Closes
12743 - When bootstrapping multiple consensus downloads at a time, use the
12744 first one that starts downloading, and close the rest. This
12745 reduces failures when authorities or fallback directories are slow
12746 or down. Together with the code for feature 15775, this feature
12747 should reduces failures due to fallback churn. Implements ticket
12748 4483. Patch by teor. Implements IPv4 portions of proposal 210 by
12749 mikeperry and teor.
12751 o Major features (security, Linux):
12752 - When Tor starts as root on Linux and is told to switch user ID, it
12753 can now retain the capability to bind to low ports. By default,
12754 Tor will do this only when it's switching user ID and some low
12755 ports have been configured. You can change this behavior with the
12756 new option KeepBindCapabilities. Closes ticket 8195.
12758 o Major bugfixes (client, bootstrapping):
12759 - Check if bootstrap consensus downloads are still needed when the
12760 linked connection attaches. This prevents tor making unnecessary
12761 begindir-style connections, which are the only directory
12762 connections tor clients make since the fix for 18483 was merged.
12763 - Fix some edge cases where consensus download connections may not
12764 have been closed, even though they were not needed. Related to fix
12766 - Make relays retry consensus downloads the correct number of times,
12767 rather than the more aggressive client retry count. Fixes part of
12770 o Major bugfixes (dns proxy mode, crash):
12771 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12772 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12774 o Major bugfixes (ed25519, voting):
12775 - Actually enable support for authorities to match routers by their
12776 Ed25519 identities. Previously, the code had been written, but
12777 some debugging code that had accidentally been left in the
12778 codebase made it stay turned off. Fixes bug 17702; bugfix
12780 - When collating votes by Ed25519 identities, authorities now
12781 include a "NoEdConsensus" flag if the ed25519 value (or lack
12782 thereof) for a server does not reflect the majority consensus.
12783 Related to bug 17668; bugfix on 0.2.7.2-alpha.
12784 - When generating a vote with keypinning disabled, never include two
12785 entries for the same ed25519 identity. This bug was causing
12786 authorities to generate votes that they could not parse when a
12787 router violated key pinning by changing its RSA identity but
12788 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
12789 18318. Bugfix on 0.2.7.2-alpha.
12791 o Major bugfixes (key management):
12792 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12793 pointer to the previous (uninitialized) key value. The impact here
12794 should be limited to a difficult-to-trigger crash, if OpenSSL is
12795 running an engine that makes key generation failures possible, or
12796 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12797 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12800 o Major bugfixes (security, client, DNS proxy):
12801 - Stop a crash that could occur when a client running with DNSPort
12802 received a query with multiple address types, and the first
12803 address type was not supported. Found and fixed by Scott Dial.
12804 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
12806 o Major bugfixes (security, compilation):
12807 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
12808 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
12809 cause a compiler warning, thereby making other checks fail, and
12810 needlessly disabling compiler-hardening support. Fixes one case of
12811 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
12812 - Repair hardened builds under the clang compiler. Previously, our
12813 use of _FORTIFY_SOURCE would conflict with clang's address
12814 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
12816 o Major bugfixes (security, pointers):
12817 - Avoid a difficult-to-trigger heap corruption attack when extending
12818 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12819 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12820 Reported by Guido Vranken.
12822 o Major bugfixes (testing):
12823 - Fix a bug that would block 'make test-network-all' on systems where
12824 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
12826 o Major bugfixes (user interface):
12827 - Correctly give a warning in the cases where a relay is specified
12828 by nickname, and one such relay is found, but it is not officially
12829 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
12831 o Minor features (accounting):
12832 - Added two modes to the AccountingRule option: One for limiting
12833 only the number of bytes sent ("AccountingRule out"), and one for
12834 limiting only the number of bytes received ("AccountingRule in").
12835 Closes ticket 15989; patch from "unixninja92".
12837 o Minor features (bug-resistance):
12838 - Make Tor survive errors involving connections without a
12839 corresponding event object. Previously we'd fail with an
12840 assertion; now we produce a log message. Related to bug 16248.
12841 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
12842 level code, to harden against accidental failures to NUL-
12843 terminate. Part of ticket 17852. Patch from jsturgix. Found
12846 o Minor features (build):
12847 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
12848 as having possible IPFW support. Closes ticket 18448. Patch from
12849 Steven Chamberlain.
12850 - Since our build process now uses "make distcheck", we no longer
12851 force "make dist" to depend on "make check". Closes ticket 17893;
12852 patch from "cypherpunks".
12853 - Tor now builds once again with the recent OpenSSL 1.1 development
12854 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev). We have been
12855 tracking OpenSSL 1.1 development as it has progressed, and fixing
12856 numerous compatibility issues as they arose. See tickets
12857 17549, 17921, 17984, 19499, and 18286.
12858 - When building manual pages, set the timezone to "UTC", so that the
12859 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
12860 Patch from intrigeri.
12862 o Minor features (clients):
12863 - Make clients, onion services, and bridge relays always use an
12864 encrypted begindir connection for directory requests. Resolves
12865 ticket 18483. Patch by teor.
12867 o Minor features (controller):
12868 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
12869 controllers can examine the the reject rules added by
12870 ExitPolicyRejectPrivate. This makes it easier for stem to display
12872 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
12873 tickets 16774 and 17817. Patch by George Tankersley.
12874 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
12875 service descriptor from a service's local hidden service
12876 descriptor cache. Closes ticket 14846.
12878 o Minor features (crypto):
12879 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
12880 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
12882 - Improve performance when hashing non-multiple of 8 sized buffers,
12883 based on Andrew Moon's public domain SipHash-2-4 implementation.
12884 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
12885 - Validate the hard-coded Diffie-Hellman parameters and ensure that
12886 p is a safe prime, and g is a suitable generator. Closes
12888 - When allocating a digest state object, allocate no more space than
12889 we actually need. Previously, we would allocate as much space as
12890 the state for the largest algorithm would need. This change saves
12891 up to 672 bytes per circuit. Closes ticket 17796.
12893 o Minor features (directory downloads):
12894 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
12895 directory mirrors. The default is 1; set it to 0 to disable
12896 fallbacks. Implements ticket 17576. Patch by teor.
12897 - Wait for busy authorities and fallback directories to become non-
12898 busy when bootstrapping. (A similar change was made in 6c443e987d
12899 for directory caches chosen from the consensus.) Closes ticket
12900 17864; patch by teor.
12902 o Minor features (geoip):
12903 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
12906 o Minor features (hidden service directory):
12907 - Streamline relay-side hsdir handling: when relays consider whether
12908 to accept an uploaded hidden service descriptor, they no longer
12909 check whether they are one of the relays in the network that is
12910 "supposed" to handle that descriptor. Implements ticket 18332.
12912 o Minor features (IPv6):
12913 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
12914 to 1, tor prefers IPv6 directory addresses.
12915 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
12916 avoids using IPv4 for client OR and directory connections.
12917 - Add address policy assume_action support for IPv6 addresses.
12918 - Add an argument 'ipv6=address:orport' to the DirAuthority and
12919 FallbackDir torrc options, to specify an IPv6 address for an
12920 authority or fallback directory. Add hard-coded ipv6 addresses for
12921 directory authorities that have them. Closes ticket 17327; patch
12922 from Nick Mathewson and teor.
12923 - Allow users to configure directory authorities and fallback
12924 directory servers with IPv6 addresses and ORPorts. Resolves
12926 - Limit IPv6 mask bits to 128.
12927 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
12928 17638; bugfix on 0.0.2pre8. Patch by teor.
12929 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
12930 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
12931 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
12932 - Warn when comparing against an AF_UNSPEC address in a policy, it's
12933 almost always a bug. Closes ticket 17863; patch by teor.
12934 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
12935 17060; bugfix on 0.2.1.3-alpha. Patch by teor.
12937 o Minor features (Linux seccomp2 sandbox):
12938 - Reject attempts to change our Address with "Sandbox 1" enabled.
12939 Changing Address with Sandbox turned on would never actually work,
12940 but previously it would fail in strange and confusing ways. Found
12941 while fixing 18548.
12943 o Minor features (logging):
12944 - When logging to syslog, allow a tag to be added to the syslog
12945 identity (the string prepended to every log message). The tag can
12946 be configured with SyslogIdentityTag and defaults to none. Setting
12947 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
12950 o Minor features (portability):
12951 - Use timingsafe_memcmp() where available. Closes ticket 17944;
12952 patch from <logan@hackers.mu>.
12954 o Minor features (relay, address discovery):
12955 - Add a family argument to get_interface_addresses_raw() and
12956 subfunctions to make network interface address interogation more
12957 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
12958 types of interfaces from the operating system. Resolves
12960 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
12961 fails to enumerate interface addresses using the platform-specific
12962 API, have it rely on the UDP socket fallback technique to try and
12963 find out what IP addresses (both IPv4 and IPv6) our machine has.
12964 Resolves ticket 17951.
12966 o Minor features (replay cache):
12967 - The replay cache now uses SHA256 instead of SHA1. Implements
12968 feature 8961. Patch by teor, issue reported by rransom.
12970 o Minor features (robustness):
12971 - Exit immediately with an error message if the code attempts to use
12972 Libevent without having initialized it. This should resolve some
12973 frequently-made mistakes in our unit tests. Closes ticket 18241.
12975 o Minor features (security, clock):
12976 - Warn when the system clock appears to move back in time (when the
12977 state file was last written in the future). Tor doesn't know that
12978 consensuses have expired if the clock is in the past. Patch by
12979 teor. Implements ticket 17188.
12981 o Minor features (security, exit policies):
12982 - ExitPolicyRejectPrivate now rejects more private addresses by
12983 default. Specifically, it now rejects the relay's outbound bind
12984 addresses (if configured), and the relay's configured port
12985 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
12986 0.2.0.11-alpha. Patch by teor.
12988 o Minor features (security, memory erasure):
12989 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12990 zero size. Check size argument to memwipe() for underflow. Fixes
12991 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12993 - Set the unused entries in a smartlist to NULL. This helped catch
12994 a (harmless) bug, and shouldn't affect performance too much.
12995 Implements ticket 17026.
12996 - Use SecureMemoryWipe() function to securely clean memory on
12997 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
12998 Implements feature 17986.
12999 - Use explicit_bzero or memset_s when present. Previously, we'd use
13000 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
13001 from <logan@hackers.mu> and <selven@hackers.mu>.
13003 o Minor features (security, RNG):
13004 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
13005 positively are not allowed to fail. Previously we depended on
13006 internal details of OpenSSL's behavior. Closes ticket 17686.
13007 - Never use the system entropy output directly for anything besides
13008 seeding the PRNG. When we want to generate important keys, instead
13009 of using system entropy directly, we now hash it with the PRNG
13010 stream. This may help resist certain attacks based on broken OS
13011 entropy implementations. Closes part of ticket 17694.
13012 - Use modern system calls (like getentropy() or getrandom()) to
13013 generate strong entropy on platforms that have them. Closes
13016 o Minor features (security, win32):
13017 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
13018 attack. Fixes bug 18123; bugfix on all tor versions. Patch
13021 o Minor features (unix domain sockets):
13022 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
13023 Unix domain sockets without checking the permissions on the parent
13024 directory. (Tor checks permissions by default because some
13025 operating systems only check permissions on the parent directory.
13026 However, some operating systems do look at permissions on the
13027 socket, and tor's default check is unneeded.) Closes ticket 18458.
13030 o Minor features (unix file permissions):
13031 - Defer creation of Unix sockets until after setuid. This avoids
13032 needing CAP_CHOWN and CAP_FOWNER when using systemd's
13033 CapabilityBoundingSet, or chown and fowner when using SELinux.
13034 Implements part of ticket 17562. Patch from Jamie Nguyen.
13035 - If any directory created by Tor is marked as group readable, the
13036 filesystem group is allowed to be either the default GID or the
13037 root user. Allowing root to read the DataDirectory prevents the
13038 need for CAP_READ_SEARCH when using systemd's
13039 CapabilityBoundingSet, or dac_read_search when using SELinux.
13040 Implements part of ticket 17562. Patch from Jamie Nguyen.
13041 - Introduce a new DataDirectoryGroupReadable option. If it is set to
13042 1, the DataDirectory will be made readable by the default GID.
13043 Implements part of ticket 17562. Patch from Jamie Nguyen.
13045 o Minor bugfixes (accounting):
13046 - The max bandwidth when using 'AccountRule sum' is now correctly
13047 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
13048 from "unixninja92".
13050 o Minor bugfixes (assert, portability):
13051 - Fix an assertion failure in memarea.c on systems where "long" is
13052 shorter than the size of a pointer. Fixes bug 18716; bugfix
13055 o Minor bugfixes (bootstrap):
13056 - Consistently use the consensus download schedule for authority
13057 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
13059 o Minor bugfixes (build):
13060 - Avoid spurious failures from configure files related to calling
13061 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
13062 0.2.0.1-alpha. Patch from "cypherpunks".
13063 - Do not link the unit tests against both the testing and non-
13064 testing versions of the static libraries. Fixes bug 18490; bugfix
13066 - Resolve warnings when building on systems that are concerned with
13067 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
13069 - Silence spurious clang-scan warnings in the ed25519_donna code by
13070 explicitly initializing some objects. Fixes bug 18384; bugfix on
13071 0.2.7.2-alpha. Patch by teor.
13072 - When libscrypt.h is found, but no libscrypt library can be linked,
13073 treat libscrypt as absent. Fixes bug 19161; bugfix
13075 - Cause the unit tests to compile correctly on mingw64 versions that
13076 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
13077 - Don't try to use the pthread_condattr_setclock() function unless
13078 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
13079 17819; bugfix on 0.2.6.3-alpha.
13080 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
13082 - Fix search for libevent libraries on OpenBSD (and other systems
13083 that install libevent 1 and libevent 2 in parallel). Fixes bug
13084 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
13085 - Isolate environment variables meant for tests from the rest of the
13086 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
13087 - Mark all object files that include micro-revision.i as depending
13088 on it, so as to make parallel builds more reliable. Fixes bug
13089 17826; bugfix on 0.2.5.1-alpha.
13090 - Remove config.log only from make distclean, not from make clean.
13091 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
13092 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
13094 - Remove an #endif from configure.ac so that we correctly detect the
13095 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
13098 o Minor bugfixes (client, bootstrap):
13099 - Count receipt of new microdescriptors as progress towards
13100 bootstrapping. Previously, with EntryNodes set, Tor might not
13101 successfully repopulate the guard set on bootstrapping. Fixes bug
13102 16825; bugfix on 0.2.3.1-alpha.
13104 o Minor bugfixes (code correctness):
13105 - Fix a bad memory handling bug that would occur if we had queued a
13106 cell on a channel's incoming queue. Fortunately, we can't actually
13107 queue a cell like that as our code is constructed today, but it's
13108 best to avoid this kind of error, even if there isn't any code
13109 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
13110 - Assert that allocated memory held by the reputation code is freed
13111 according to its internal counters. Fixes bug 17753; bugfix
13113 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
13115 - Update to the latest version of Trunnel, which tries harder to
13116 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
13117 by clang address sanitizer. Fixes bug 18373; bugfix
13119 - When closing an entry connection, generate a warning if we should
13120 have sent an end cell for it but we haven't. Fixes bug 17876;
13121 bugfix on 0.2.3.2-alpha.
13123 o Minor bugfixes (configuration):
13124 - Fix a tiny memory leak when parsing a port configuration ending in
13125 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
13127 o Minor bugfixes (containers):
13128 - If we somehow attempt to construct a heap with more than
13129 1073741822 elements, avoid an integer overflow when maintaining
13130 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
13132 o Minor bugfixes (controller, microdescriptors):
13133 - Make GETINFO dir/status-vote/current/consensus conform to the
13134 control specification by returning "551 Could not open cached
13135 consensus..." when not caching consensuses. Fixes bug 18920;
13136 bugfix on 0.2.2.6-alpha.
13138 o Minor bugfixes (crypto):
13139 - Check the return value of HMAC() and assert on failure. Fixes bug
13140 17658; bugfix on 0.2.3.6-alpha. Patch by teor.
13142 o Minor bugfixes (directories):
13143 - When fetching extrainfo documents, compare their SHA256 digests
13144 and Ed25519 signing key certificates with the routerinfo that led
13145 us to fetch them, rather than with the most recent routerinfo.
13146 Otherwise we generate many spurious warnings about mismatches.
13147 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
13148 - When generating a URL for a directory server on an IPv6 address,
13149 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
13150 on 0.2.3.9-alpha. Patch from Malek.
13152 o Minor bugfixes (downloading):
13153 - Predict more correctly whether we'll be downloading over HTTP when
13154 we determine the maximum length of a URL. This should avoid a
13155 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
13158 o Minor bugfixes (exit policies, security):
13159 - Refresh an exit relay's exit policy when interface addresses
13160 change. Previously, tor only refreshed the exit policy when the
13161 configured external address changed. Fixes bug 18208; bugfix on
13162 0.2.7.3-rc. Patch by teor.
13164 o Minor bugfixes (fallback directories):
13165 - Mark fallbacks as "too busy" when they return a 503 response,
13166 rather than just marking authorities. Fixes bug 17572; bugfix on
13167 0.2.4.7-alpha. Patch by teor.
13168 - When requesting extrainfo descriptors from a trusted directory
13169 server, check whether it is an authority or a fallback directory
13170 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
13171 0.2.4.7-alpha. Reported by atagar, patch by teor.
13173 o Minor bugfixes (hidden service, client):
13174 - Handle the case where the user makes several fast consecutive
13175 requests to the same .onion address. Previously, the first six
13176 requests would each trigger a descriptor fetch, each picking a
13177 directory (there are 6 overall) and the seventh one would fail
13178 because no directories were left, thereby triggering a close on
13179 all current directory connections asking for the hidden service.
13180 The solution here is to not close the connections if we have
13181 pending directory fetches. Fixes bug 15937; bugfix
13184 o Minor bugfixes (hidden service, control port):
13185 - Add the onion address to the HS_DESC event for the UPLOADED action
13186 both on success or failure. It was previously hardcoded with
13187 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
13189 o Minor bugfixes (hidden service, directory):
13190 - Bridges now refuse "rendezvous2" (hidden service descriptor)
13191 publish attempts. Suggested by ticket 18332.
13193 o Minor bugfixes (IPv6):
13194 - Update the limits in max_dl_per_request for IPv6 address length.
13195 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
13197 o Minor bugfixes (Linux seccomp2 sandbox):
13198 - Allow more syscalls when running with "Sandbox 1" enabled:
13199 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
13200 some systems, these are required for Tor to start. Fixes bug
13201 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
13202 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
13203 so that get_interface_address6_via_udp_socket_hack() can work.
13204 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
13205 - Allow the setrlimit syscall, and the prlimit and prlimit64
13206 syscalls, which some libc implementations use under the hood.
13207 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
13208 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
13209 enabled and no DNS resolvers configured. This should help TAILS
13210 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
13211 - Fix a crash when using offline master ed25519 keys with the Linux
13212 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
13213 - Allow statistics to be written to disk when "Sandbox 1" is
13214 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
13215 0.2.6.1-alpha respectively.
13217 o Minor bugfixes (logging):
13218 - In log messages that include a function name, use __FUNCTION__
13219 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
13220 with clang __PRETTY_FUNCTION__ has extra information we don't
13221 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
13223 - Remove needless quotes from a log message about unparseable
13224 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
13225 - Scrub service name in "unrecognized service ID" log messages.
13226 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
13227 - When logging information about an unparsable networkstatus vote or
13228 consensus, do not say "vote" when we mean consensus. Fixes bug
13229 18368; bugfix on 0.2.0.8-alpha.
13230 - When we can't generate a signing key because OfflineMasterKey is
13231 set, do not imply that we should have been able to load it. Fixes
13232 bug 18133; bugfix on 0.2.7.2-alpha.
13233 - When logging a malformed hostname received through socks4, scrub
13234 it if SafeLogging says we should. Fixes bug 17419; bugfix
13237 o Minor bugfixes (memory safety):
13238 - Avoid freeing an uninitialized pointer when opening a socket fails
13239 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
13240 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
13242 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
13243 18672; bugfix on 0.2.5.1-alpha.
13244 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
13247 o Minor bugfixes (pluggable transports):
13248 - Avoid reporting a spurious error when we decide that we don't need
13249 to terminate a pluggable transport because it has already exited.
13250 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
13252 o Minor bugfixes (pointer arithmetic):
13253 - Fix a bug in memarea_alloc() that could have resulted in remote
13254 heap write access, if Tor had ever passed an unchecked size to
13255 memarea_alloc(). Fortunately, all the sizes we pass to
13256 memarea_alloc() are pre-checked to be less than 128 kilobytes.
13257 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
13260 o Minor bugfixes (private directory):
13261 - Prevent a race condition when creating private directories. Fixes
13262 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
13263 Patch from jsturgix. Found with Flawfinder.
13265 o Minor bugfixes (relays):
13266 - Check that both the ORPort and DirPort (if present) are reachable
13267 before publishing a relay descriptor. Otherwise, relays publish a
13268 descriptor with DirPort 0 when the DirPort reachability test takes
13269 longer than the ORPort reachability test. Fixes bug 18050; bugfix
13270 on 0.1.0.1-rc. Reported by "starlight", patch by teor.
13271 - Resolve some edge cases where we might launch an ORPort
13272 reachability check even when DisableNetwork is set. Noticed while
13273 fixing bug 18616; bugfix on 0.2.3.9-alpha.
13275 o Minor bugfixes (relays, hidden services):
13276 - Refuse connection requests to private OR addresses unless
13277 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
13278 then refuse to send any cells to a private address. Fixes bugs
13279 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by teor.
13281 o Minor bugfixes (security, hidden services):
13282 - Prevent hidden services connecting to client-supplied rendezvous
13283 addresses that are reserved as internal or multicast. Fixes bug
13284 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
13286 o Minor bugfixes (statistics):
13287 - Consistently check for overflow in round_*_to_next_multiple_of
13288 functions, and add unit tests with additional and maximal values.
13289 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
13290 - Handle edge cases in the laplace functions: avoid division by
13291 zero, avoid taking the log of zero, and silence clang type
13292 conversion warnings using round and trunc. Add unit tests for edge
13293 cases with maximal values. Fixes part of bug 13192; bugfix
13295 - We now include consensus downloads via IPv6 in our directory-
13296 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
13298 o Minor bugfixes (test networks, IPv6):
13299 - Allow internal IPv6 addresses in descriptors in test networks.
13300 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
13303 o Minor bugfixes (testing):
13304 - Check the full results of SHA256 and SHA512 digests in the unit
13305 tests. Bugfix on 0.2.2.4-alpha. Patch by teor.
13306 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
13308 - Fix a small memory leak that would occur when the
13309 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
13310 bugfix on 0.2.5.2-alpha.
13311 - Make unit tests pass on IPv6-only systems, and systems without
13312 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
13313 bugfix on 0.2.7.3-rc. Patch by teor.
13314 - The test for log_heartbeat was incorrectly failing in timezones
13315 with non-integer offsets. Instead of comparing the end of the time
13316 string against a constant, compare it to the output of
13317 format_local_iso_time when given the correct input. Fixes bug
13318 18039; bugfix on 0.2.5.4-alpha.
13319 - We no longer disable assertions in the unit tests when coverage is
13320 enabled. Instead, we require you to say --disable-asserts-in-tests
13321 to the configure script if you need assertions disabled in the
13322 unit tests (for example, if you want to perform branch coverage).
13323 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
13325 o Minor bugfixes (time handling):
13326 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
13327 field. Otherwise, our unit tests crash on Windows. Fixes bug
13328 18977; bugfix on 0.2.2.25-alpha.
13329 - Avoid overflow in tor_timegm when parsing dates in and after 2038
13330 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
13331 0.0.2pre14. Patch by teor.
13333 o Minor bugfixes (tor-gencert):
13334 - Correctly handle the case where an authority operator enters a
13335 passphrase but sends an EOF before sending a newline. Fixes bug
13336 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
13338 o Code simplification and refactoring:
13339 - Clean up a little duplicated code in
13340 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
13342 - Decouple the list of streams waiting to be attached to circuits
13343 from the overall connection list. This change makes it possible to
13344 attach streams quickly while simplifying Tor's callgraph and
13345 avoiding O(N) scans of the entire connection list. Closes
13347 - Extract the more complicated parts of circuit_mark_for_close()
13348 into a new function that we run periodically before circuits are
13349 freed. This change removes more than half of the functions
13350 currently in the "blob". Closes ticket 17218.
13351 - Move logging of redundant policy entries in
13352 policies_parse_exit_policy_internal into its own function. Closes
13353 ticket 17608; patch from "juce".
13354 - Quote all the string interpolations in configure.ac -- even those
13355 which we are pretty sure can't contain spaces. Closes ticket
13356 17744. Patch from zerosion.
13357 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
13358 use them. Closes ticket 17926.
13359 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
13360 inplace, so there's no need to have a separate implementation for
13361 the non-inplace code. Closes ticket 18258. Patch from Malek.
13362 - Simplify return types for some crypto functions that can't
13363 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
13364 - When a direct directory request fails immediately on launch,
13365 instead of relaunching that request from inside the code that
13366 launches it, instead mark the connection for teardown. This change
13367 simplifies Tor's callback and prevents the directory-request
13368 launching code from invoking itself recursively. Closes
13372 - Add a description of the correct use of the '--keygen' command-
13373 line option. Closes ticket 17583; based on text by 's7r'.
13374 - Change build messages to refer to "Fedora" instead of "Fedora
13375 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
13376 Patches from "icanhasaccount" and "cypherpunks".
13377 - Document the contents of the 'datadir/keys' subdirectory in the
13378 manual page. Closes ticket 17621.
13379 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
13380 - Explain actual minima for BandwidthRate. Closes ticket 16382.
13381 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
13382 - Mention torspec URL in the manpage and point the reader to it
13383 whenever we mention a document that belongs in torspce. Fixes
13385 - Stop recommending use of nicknames to identify relays in our
13386 MapAddress documentation. Closes ticket 18312.
13388 o Removed features:
13389 - Remove client-side support for connecting to Tor relays running
13390 versions of Tor before 0.2.3.6-alpha. These relays didn't support
13391 the v3 TLS handshake protocol, and are no longer allowed on the
13392 Tor network. Implements the client side of ticket 11150. Based on
13393 patches by Tom van der Woerdt.
13394 - We no longer maintain an internal freelist in memarea.c.
13395 Allocators should be good enough to make this code unnecessary,
13396 and it's doubtful that it ever had any performance benefit.
13399 - Add unit tests to check for common RNG failure modes, such as
13400 returning all zeroes, identical values, or incrementing values
13401 (OpenSSL's rand_predictable feature). Patch by teor.
13402 - Always test both ed25519 backends, so that we can be sure that our
13403 batch-open replacement code works. Part of ticket 16794.
13404 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
13405 portion of ticket 16831.
13406 - Fix several warnings from clang's address sanitizer produced in
13408 - Log more information when the backtrace tests fail. Closes ticket
13409 17892. Patch from "cypherpunks."
13410 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
13411 util_format.c, directory.c, and options_validate.c. Closes tickets
13412 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
13414 - Treat backtrace test failures as expected on FreeBSD until we
13415 solve bug 17808. Closes ticket 18204.
13416 - Unit tests for directory_handle_command_get. Closes ticket 17004.
13417 Patch from Reinaldo de Souza Jr.
13420 Changes in version 0.2.7.6 - 2015-12-10
13421 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
13422 well as a minor bug in hidden service reliability.
13424 o Major bugfixes (guard selection):
13425 - Actually look at the Guard flag when selecting a new directory
13426 guard. When we implemented the directory guard design, we
13427 accidentally started treating all relays as if they have the Guard
13428 flag during guard selection, leading to weaker anonymity and worse
13429 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
13432 o Minor features (geoip):
13433 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
13436 o Minor bugfixes (compilation):
13437 - When checking for net/pfvar.h, include netinet/in.h if possible.
13438 This fixes transparent proxy detection on OpenBSD. Fixes bug
13439 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
13440 - Fix a compilation warning with Clang 3.6: Do not check the
13441 presence of an address which can never be NULL. Fixes bug 17781.
13443 o Minor bugfixes (correctness):
13444 - When displaying an IPv6 exit policy, include the mask bits
13445 correctly even when the number is greater than 31. Fixes bug
13446 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
13447 - The wrong list was used when looking up expired intro points in a
13448 rend service object, causing what we think could be reachability
13449 issues for hidden services, and triggering a BUG log. Fixes bug
13450 16702; bugfix on 0.2.7.2-alpha.
13451 - Fix undefined behavior in the tor_cert_checksig function. Fixes
13452 bug 17722; bugfix on 0.2.7.2-alpha.
13455 Changes in version 0.2.7.5 - 2015-11-20
13456 The Tor 0.2.7 release series is dedicated to the memory of Tor user
13457 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
13458 tirelessly to advocate human rights regardless of national borders,
13459 and oppose the encroachments of mass surveillance. He opposed national
13460 exceptionalism, he brought clarity to legal and policy debates, he
13461 understood and predicted the impact of mass surveillance on the world,
13462 and he laid the groundwork for resisting it. While serving on the Tor
13463 Project's board of directors, he brought us his uncompromising focus
13464 on technical excellence in the service of humankind. Caspar was an
13465 inimitable force for good and a wonderful friend. He was kind,
13466 humorous, generous, gallant, and believed we should protect one
13467 another without exception. We honor him here for his ideals, his
13468 efforts, and his accomplishments. Please honor his memory with works
13469 that would make him proud.
13471 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
13473 The 0.2.7 series adds a more secure identity key type for relays,
13474 improves cryptography performance, resolves several longstanding
13475 hidden-service performance issues, improves controller support for
13476 hidden services, and includes small bugfixes and performance
13477 improvements throughout the program. This release series also includes
13478 more tests than before, and significant simplifications to which parts
13479 of Tor invoke which others. For a full list of changes, see below.
13481 o New system requirements:
13482 - Tor no longer includes workarounds to support Libevent versions
13483 before 1.3e. Libevent 2.0 or later is recommended. Closes
13485 - Tor no longer supports copies of OpenSSL that are missing support
13486 for Elliptic Curve Cryptography. (We began using ECC when
13487 available in 0.2.4.8-alpha, for more safe and efficient key
13488 negotiation.) In particular, support for at least one of P256 or
13489 P224 is now required, with manual configuration needed if only
13490 P224 is available. Resolves ticket 16140.
13491 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
13492 on an operating system that has not upgraded to OpenSSL 1.0 or
13493 later, and you compile Tor from source, you will need to install a
13494 more recent OpenSSL to link Tor against.) These versions of
13495 OpenSSL are still supported by the OpenSSL, but the numerous
13496 cryptographic improvements in later OpenSSL releases makes them a
13497 clear choice. Resolves ticket 16034.
13499 o Major features (controller):
13500 - Add the ADD_ONION and DEL_ONION commands that allow the creation
13501 and management of hidden services via the controller. Closes
13503 - New "GETINFO onions/current" and "GETINFO onions/detached"
13504 commands to get information about hidden services created via the
13505 controller. Part of ticket 6411.
13506 - New HSFETCH command to launch a request for a hidden service
13507 descriptor. Closes ticket 14847.
13508 - New HSPOST command to upload a hidden service descriptor. Closes
13509 ticket 3523. Patch by "DonnchaC".
13511 o Major features (Ed25519 identity keys, Proposal 220):
13512 - Add support for offline encrypted Ed25519 master keys. To use this
13513 feature on your tor relay, run "tor --keygen" to make a new master
13514 key (or to make a new signing key if you already have a master
13515 key). Closes ticket 13642.
13516 - All relays now maintain a stronger identity key, using the Ed25519
13517 elliptic curve signature format. This master key is designed so
13518 that it can be kept offline. Relays also generate an online
13519 signing key, and a set of other Ed25519 keys and certificates.
13520 These are all automatically regenerated and rotated as needed.
13521 Implements part of ticket 12498.
13522 - Directory authorities now vote on Ed25519 identity keys along with
13523 RSA1024 keys. Implements part of ticket 12498.
13524 - Directory authorities track which Ed25519 identity keys have been
13525 used with which RSA1024 identity keys, and do not allow them to
13526 vary freely. Implements part of ticket 12498.
13527 - Microdescriptors now include Ed25519 identity keys. Implements
13528 part of ticket 12498.
13529 - Add a --newpass option to allow changing or removing the
13530 passphrase of an encrypted key with tor --keygen. Implements part
13532 - Add a new OfflineMasterKey option to tell Tor never to try loading
13533 or generating a secret Ed25519 identity key. You can use this in
13534 combination with tor --keygen to manage offline and/or encrypted
13535 Ed25519 keys. Implements ticket 16944.
13536 - On receiving a HUP signal, check to see whether the Ed25519
13537 signing key has changed, and reload it if so. Closes ticket 16790.
13538 - Significant usability improvements for Ed25519 key management. Log
13539 messages are better, and the code can recover from far more
13540 failure conditions. Thanks to "s7r" for reporting and diagnosing
13543 o Major features (ECC performance):
13544 - Improve the runtime speed of Ed25519 signature verification by
13545 using Ed25519-donna's batch verification support. Implements
13547 - Improve the speed of Ed25519 operations and Curve25519 keypair
13548 generation when built targeting 32 bit x86 platforms with SSE2
13549 available. Implements ticket 16535.
13550 - Improve the runtime speed of Ed25519 operations by using the
13551 public-domain Ed25519-donna by Andrew M. ("floodyberry").
13552 Implements ticket 16467.
13553 - Improve the runtime speed of the ntor handshake by using an
13554 optimized curve25519 basepoint scalarmult implementation from the
13555 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
13556 ideas by Adam Langley. Implements ticket 9663.
13558 o Major features (Hidden services):
13559 - Hidden services, if using the EntryNodes option, are required to
13560 use more than one EntryNode, in order to avoid a guard discovery
13561 attack. (This would only affect people who had configured hidden
13562 services and manually specified the EntryNodes option with a
13563 single entry-node. The impact was that it would be easy to
13564 remotely identify the guard node used by such a hidden service.
13565 See ticket for more information.) Fixes ticket 14917.
13566 - Add the torrc option HiddenServiceNumIntroductionPoints, to
13567 specify a fixed number of introduction points. Its maximum value
13568 is 10 and default is 3. Using this option can increase a hidden
13569 service's reliability under load, at the cost of making it more
13570 visible that the hidden service is facing extra load. Closes
13572 - Remove the adaptive algorithm for choosing the number of
13573 introduction points, which used to change the number of
13574 introduction points (poorly) depending on the number of
13575 connections the HS sees. Closes ticket 4862.
13577 o Major features (onion key cross-certification):
13578 - Relay descriptors now include signatures of their own identity
13579 keys, made using the TAP and ntor onion keys. These signatures
13580 allow relays to prove ownership of their own onion keys. Because
13581 of this change, microdescriptors will no longer need to include
13582 RSA identity keys. Implements proposal 228; closes ticket 12499.
13584 o Major bugfixes (client-side privacy, also in 0.2.6.9):
13585 - Properly separate out each SOCKSPort when applying stream
13586 isolation. The error occurred because each port's session group
13587 was being overwritten by a default value when the listener
13588 connection was initialized. Fixes bug 16247; bugfix on
13589 0.2.6.3-alpha. Patch by "jojelino".
13591 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
13592 - Stop refusing to store updated hidden service descriptors on a
13593 client. This reverts commit 9407040c59218 (which indeed fixed bug
13594 14219, but introduced a major hidden service reachability
13595 regression detailed in bug 16381). This is a temporary fix since
13596 we can live with the minor issue in bug 14219 (it just results in
13597 some load on the network) but the regression of 16381 is too much
13598 of a setback. First-round fix for bug 16381; bugfix
13601 o Major bugfixes (hidden services):
13602 - Revert commit that made directory authorities assign the HSDir
13603 flag to relays without a DirPort; this was bad because such relays
13604 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
13606 - When cannibalizing a circuit for an introduction point, always
13607 extend to the chosen exit node (creating a 4 hop circuit).
13608 Previously Tor would use the current circuit exit node, which
13609 changed the original choice of introduction point, and could cause
13610 the hidden service to skip excluded introduction points or
13611 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
13614 o Major bugfixes (memory leaks):
13615 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
13616 17398; bugfix on 0.2.6.1-alpha.
13618 o Major bugfixes (open file limit):
13619 - The open file limit wasn't checked before calling
13620 tor_accept_socket_nonblocking(), which would make Tor exceed the
13621 limit. Now, before opening a new socket, Tor validates the open
13622 file limit just before, and if the max has been reached, return an
13623 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
13625 o Major bugfixes (security, correctness):
13626 - Fix an error that could cause us to read 4 bytes before the
13627 beginning of an openssl string. This bug could be used to cause
13628 Tor to crash on systems with unusual malloc implementations, or
13629 systems with unusual hardening installed. Fixes bug 17404; bugfix
13632 o Major bugfixes (stability, also in 0.2.6.10):
13633 - Stop crashing with an assertion failure when parsing certain kinds
13634 of malformed or truncated microdescriptors. Fixes bug 16400;
13635 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
13636 by "cypherpunks_backup".
13637 - Stop random client-side assertion failures that could occur when
13638 connecting to a busy hidden service, or connecting to a hidden
13639 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
13642 o Minor features (client, SOCKS):
13643 - Add GroupWritable and WorldWritable options to unix-socket based
13644 SocksPort and ControlPort options. These options apply to a single
13645 socket, and override {Control,Socks}SocketsGroupWritable. Closes
13647 - Relax the validation done to hostnames in SOCKS5 requests, and
13648 allow a single trailing '.' to cope with clients that pass FQDNs
13649 using that syntax to explicitly indicate that the domain name is
13650 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
13651 - Relax the validation of hostnames in SOCKS5 requests, allowing the
13652 character '_' to appear, in order to cope with domains observed in
13653 the wild that are serving non-RFC compliant records. Resolves
13656 o Minor features (client-side privacy):
13657 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
13658 lifespan when IsolateSOCKSAuth and streams with SOCKS
13659 authentication are attached to the circuit. This allows
13660 applications like TorBrowser to manage circuit lifetime on their
13661 own. Implements feature 15482.
13662 - When logging malformed hostnames from SOCKS5 requests, respect
13663 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
13665 o Minor features (clock-jump tolerance):
13666 - Recover better when our clock jumps back many hours, like might
13667 happen for Tails or Whonix users who start with a very wrong
13668 hardware clock, use Tor to discover a more accurate time, and then
13669 fix their clock. Resolves part of ticket 8766.
13671 o Minor features (command-line interface):
13672 - Make --hash-password imply --hush to prevent unnecessary noise.
13673 Closes ticket 15542. Patch from "cypherpunks".
13674 - Print a warning whenever we find a relative file path being used
13675 as torrc option. Resolves issue 14018.
13677 o Minor features (compilation):
13678 - Give a warning as early as possible when trying to build with an
13679 unsupported OpenSSL version. Closes ticket 16901.
13680 - Use C99 variadic macros when the compiler is not GCC. This avoids
13681 failing compilations on MSVC, and fixes a log-file-based race
13682 condition in our old workarounds. Original patch from Gisle Vanem.
13684 o Minor features (control protocol):
13685 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
13686 the control protocol. Resolves ticket 15358.
13688 o Minor features (controller):
13689 - Add DirAuthority lines for default directory authorities to the
13690 output of the "GETINFO config/defaults" command if not already
13691 present. Implements ticket 14840.
13692 - Controllers can now use "GETINFO hs/client/desc/id/..." to
13693 retrieve items from the client's hidden service descriptor cache.
13694 Closes ticket 14845.
13695 - Implement a new controller command "GETINFO status/fresh-relay-
13696 descs" to fetch a descriptor/extrainfo pair that was generated on
13697 demand just for the controller's use. Implements ticket 14784.
13699 o Minor features (directory authorities):
13700 - Directory authorities no longer vote against the "Fast", "Stable",
13701 and "HSDir" flags just because they were going to vote against
13702 "Running": if the consensus turns out to be that the router was
13703 running, then the authority's vote should count. Patch from Peter
13704 Retzlaff; closes issue 8712.
13706 o Minor features (directory authorities, security, also in 0.2.6.9):
13707 - The HSDir flag given by authorities now requires the Stable flag.
13708 For the current network, this results in going from 2887 to 2806
13709 HSDirs. Also, it makes it harder for an attacker to launch a sybil
13710 attack by raising the effort for a relay to become Stable to
13711 require at the very least 7 days, while maintaining the 96 hours
13712 uptime requirement for HSDir. Implements ticket 8243.
13714 o Minor features (DoS-resistance):
13715 - Make it harder for attackers to overload hidden services with
13716 introductions, by blocking multiple introduction requests on the
13717 same circuit. Resolves ticket 15515.
13719 o Minor features (geoip):
13720 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
13723 o Minor features (hidden services):
13724 - Add the new options "HiddenServiceMaxStreams" and
13725 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
13726 limit the maximum number of simultaneous streams per circuit, and
13727 optionally tear down the circuit when the limit is exceeded. Part
13729 - Client now uses an introduction point failure cache to know when
13730 to fetch or keep a descriptor in their cache. Previously, failures
13731 were recorded implicitly, but not explicitly remembered. Closes
13733 - Relays need to have the Fast flag to get the HSDir flag. As this
13734 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
13735 drop. This change should make some attacks against the hidden
13736 service directory system harder. Fixes ticket 15963.
13737 - Turn on hidden service statistics collection by setting the torrc
13738 option HiddenServiceStatistics to "1" by default. (This keeps
13739 track only of the fraction of traffic used by hidden services, and
13740 the total number of hidden services in existence.) Closes
13742 - To avoid leaking HS popularity, don't cycle the introduction point
13743 when we've handled a fixed number of INTRODUCE2 cells but instead
13744 cycle it when a random number of introductions is reached, thus
13745 making it more difficult for an attacker to find out the amount of
13746 clients that have used the introduction point for a specific HS.
13747 Closes ticket 15745.
13749 o Minor features (logging):
13750 - Include the Tor version in all LD_BUG log messages, since people
13751 tend to cut and paste those into the bugtracker. Implements
13754 o Minor features (pluggable transports):
13755 - When launching managed pluggable transports on Linux systems,
13756 attempt to have the kernel deliver a SIGTERM on tor exit if the
13757 pluggable transport process is still running. Resolves
13759 - When launching managed pluggable transports, setup a valid open
13760 stdin in the child process that can be used to detect if tor has
13761 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
13762 can be used by implementations to detect this new behavior.
13763 Resolves ticket 15435.
13765 o Minor bugfixes (torrc exit policies):
13766 - In each instance above, usage advice is provided to avoid the
13767 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
13768 16069; bugfix on 0.2.4.7-alpha.
13769 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
13770 produce IPv6 wildcard addresses. Previously they would produce
13771 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
13772 of bug 16069; bugfix on 0.2.4.7-alpha.
13773 - When parsing torrc ExitPolicies, we now issue an info-level
13774 message when expanding an "accept/reject *" line to include both
13775 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
13776 - When parsing torrc ExitPolicies, we now warn for a number of cases
13777 where the user's intent is likely to differ from Tor's actual
13778 behavior. These include: using an IPv4 address with an accept6 or
13779 reject6 line; using "private" on an accept6 or reject6 line; and
13780 including any ExitPolicy lines after accept *:* or reject *:*.
13781 Related to ticket 16069.
13783 o Minor bugfixes (command-line interface):
13784 - When "--quiet" is provided along with "--validate-config", do not
13785 write anything to stdout on success. Fixes bug 14994; bugfix
13787 - When complaining about bad arguments to "--dump-config", use
13788 stderr, not stdout.
13789 - Print usage information for --dump-config when it is used without
13790 an argument. Also, fix the error message to use different wording
13791 and add newline at the end. Fixes bug 15541; bugfix
13794 o Minor bugfixes (compilation):
13795 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
13796 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
13797 - Repair compilation with the most recent (unreleased, alpha)
13798 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
13800 o Minor bugfixes (compilation, also in 0.2.6.9):
13801 - Build with --enable-systemd correctly when libsystemd is
13802 installed, but systemd is not. Fixes bug 16164; bugfix on
13803 0.2.6.3-alpha. Patch from Peter Palfrader.
13805 o Minor bugfixes (configuration, unit tests):
13806 - Only add the default fallback directories when the DirAuthorities,
13807 AlternateDirAuthority, and FallbackDir directory config options
13808 are set to their defaults. The default fallback directory list is
13809 currently empty, this fix will only change tor's behavior when it
13810 has default fallback directories. Includes unit tests for
13811 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
13812 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
13814 o Minor bugfixes (controller):
13815 - Add the descriptor ID in each HS_DESC control event. It was
13816 missing, but specified in control-spec.txt. Fixes bug 15881;
13817 bugfix on 0.2.5.2-alpha.
13819 o Minor bugfixes (correctness):
13820 - For correctness, avoid modifying a constant string in
13821 handle_control_postdescriptor. Fixes bug 15546; bugfix
13823 - Remove side-effects from tor_assert() calls. This was harmless,
13824 because we never disable assertions, but it is bad style and
13825 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
13827 - When calling channel_free_list(), avoid calling smartlist_remove()
13828 while inside a FOREACH loop. This partially reverts commit
13829 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
13830 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
13832 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
13833 - Check for failures from crypto_early_init, and refuse to continue.
13834 A previous typo meant that we could keep going with an
13835 uninitialized crypto library, and would have OpenSSL initialize
13836 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
13837 when implementing ticket 4900. Patch by "teor".
13839 o Minor bugfixes (hidden service):
13840 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
13841 a client authorized hidden service. Fixes bug 15823; bugfix
13843 - Remove an extraneous newline character from the end of hidden
13844 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
13846 o Minor bugfixes (Linux seccomp2 sandbox):
13847 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
13848 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
13849 - Allow bridge authorities to run correctly under the seccomp2
13850 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
13851 - Add the "hidserv-stats" filename to our sandbox filter for the
13852 HiddenServiceStatistics option to work properly. Fixes bug 17354;
13853 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
13855 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
13856 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
13857 these when eventfd2() support is missing. Fixes bug 16363; bugfix
13858 on 0.2.6.3-alpha. Patch from "teor".
13860 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
13861 - Allow systemd connections to work with the Linux seccomp2 sandbox
13862 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
13864 - Fix sandboxing to work when running as a relay, by allowing the
13865 renaming of secret_id_key, and allowing the eventfd2 and futex
13866 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
13869 o Minor bugfixes (logging):
13870 - When building Tor under Clang, do not include an extra set of
13871 parentheses in log messages that include function names. Fixes bug
13872 15269; bugfix on every released version of Tor when compiled with
13873 recent enough Clang.
13875 o Minor bugfixes (network):
13876 - When attempting to use fallback technique for network interface
13877 lookup, disregard loopback and multicast addresses since they are
13878 unsuitable for public communications.
13880 o Minor bugfixes (open file limit):
13881 - Fix set_max_file_descriptors() to set by default the max open file
13882 limit to the current limit when setrlimit() fails. Fixes bug
13883 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
13885 o Minor bugfixes (portability):
13886 - Check correctly for Windows socket errors in the workqueue
13887 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
13888 - Try harder to normalize the exit status of the Tor process to the
13889 standard-provided range. Fixes bug 16975; bugfix on every version
13891 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes part
13892 of bug 17151; bugfix on 0.2.5.2-alpha. Patch from Marcin Cieślak.
13894 o Minor bugfixes (relay):
13895 - Ensure that worker threads actually exit when a fatal error or
13896 shutdown is indicated. This fix doesn't currently affect the
13897 behavior of Tor, because Tor workers never indicates fatal error
13898 or shutdown except in the unit tests. Fixes bug 16868; bugfix
13900 - Fix a rarely-encountered memory leak when failing to initialize
13901 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
13902 from "cypherpunks".
13903 - Unblock threads before releasing the work queue mutex to ensure
13904 predictable scheduling behavior. Fixes bug 16644; bugfix
13907 o Minor bugfixes (security, exit policies):
13908 - ExitPolicyRejectPrivate now also rejects the relay's published
13909 IPv6 address (if any), and any publicly routable IPv4 or IPv6
13910 addresses on any local interfaces. ticket 17027. Patch by "teor".
13911 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
13913 o Minor bugfixes (statistics):
13914 - Disregard the ConnDirectionStatistics torrc options when Tor is
13915 not a relay since in that mode of operation no sensible data is
13916 being collected and because Tor might run into measurement hiccups
13917 when running as a client for some time, then becoming a relay.
13918 Fixes bug 15604; bugfix on 0.2.2.35.
13920 o Minor bugfixes (systemd):
13921 - Tor's systemd unit file no longer contains extraneous spaces.
13922 These spaces would sometimes confuse tools like deb-systemd-
13923 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
13925 o Minor bugfixes (test networks):
13926 - When self-testing reachability, use ExtendAllowPrivateAddresses to
13927 determine if local/private addresses imply reachability. The
13928 previous fix used TestingTorNetwork, which implies
13929 ExtendAllowPrivateAddresses, but this excluded rare configurations
13930 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
13931 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
13932 issue discovered by CJ Ess.
13934 o Minor bugfixes (tests, also in 0.2.6.9):
13935 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
13936 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
13938 o Code simplification and refactoring:
13939 - Change the function that's called when we need to retry all
13940 downloads so that it only reschedules the downloads to happen
13941 immediately, rather than launching them all at once itself. This
13942 further simplifies Tor's callgraph.
13943 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
13944 to ensure they remain consistent and visible everywhere.
13945 - Move some format-parsing functions out of crypto.c and
13946 crypto_curve25519.c into crypto_format.c and/or util_format.c.
13947 - Move the client-only parts of init_keys() into a separate
13948 function. Closes ticket 16763.
13949 - Move the hacky fallback code out of get_interface_address6() into
13950 separate function and get it covered with unit-tests. Resolves
13952 - Refactor hidden service client-side cache lookup to intelligently
13953 report its various failure cases, and disentangle failure cases
13954 involving a lack of introduction points. Closes ticket 14391.
13955 - Remove some vestigial workarounds for the MSVC6 compiler. We
13956 haven't supported that in ages.
13957 - Remove the unused "nulterminate" argument from buf_pullup().
13958 - Simplify the microdesc_free() implementation so that it no longer
13959 appears (to code analysis tools) to potentially invoke a huge
13960 suite of other microdesc functions.
13961 - Simply the control graph further by deferring the inner body of
13962 directory_all_unreachable() into a callback. Closes ticket 16762.
13963 - The link authentication code has been refactored for better
13964 testability and reliability. It now uses code generated with the
13965 "trunnel" binary encoding generator, to reduce the risk of bugs
13966 due to programmer error. Done as part of ticket 12498.
13967 - Treat the loss of an owning controller as equivalent to a SIGTERM
13968 signal. This removes a tiny amount of duplicated code, and
13969 simplifies our callgraph. Closes ticket 16788.
13970 - Use our own Base64 encoder instead of OpenSSL's, to allow more
13971 control over the output. Part of ticket 15652.
13972 - When generating an event to send to the controller, we no longer
13973 put the event over the network immediately. Instead, we queue
13974 these events, and use a Libevent callback to deliver them. This
13975 change simplifies Tor's callgraph by reducing the number of
13976 functions from which all other Tor functions are reachable. Closes
13978 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
13979 that try to scan or compile every file on Unix won't decide that
13983 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
13984 - Improve the descriptions of statistics-related torrc options in
13985 the manpage to describe rationale and possible uses cases. Fixes
13987 - Improve the layout and formatting of ./configure --help messages.
13988 Closes ticket 15024. Patch from "cypherpunks".
13989 - Include a specific and (hopefully) accurate documentation of the
13990 torrc file's meta-format in doc/torrc_format.txt. This is mainly
13991 of interest to people writing programs to parse or generate torrc
13992 files. This document is not a commitment to long-term
13993 compatibility; some aspects of the current format are a bit
13994 ridiculous. Closes ticket 2325.
13995 - Include the TUNING document in our source tarball. It is referred
13996 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
13998 - Note that HiddenServicePorts can take a unix domain socket. Closes
14000 - Recommend a 40 GB example AccountingMax in torrc.sample rather
14001 than a 4 GB max. Closes ticket 16742.
14002 - Standardize on the term "server descriptor" in the manual page.
14003 Previously, we had used "router descriptor", "server descriptor",
14004 and "relay descriptor" interchangeably. Part of ticket 14987.
14005 - Advise users on how to configure separate IPv4 and IPv6 exit
14006 policies in the manpage and sample torrcs. Related to ticket 16069.
14007 - Fix an error in the manual page and comments for
14008 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
14009 required "ORPort connectivity". While this is true, it is in no
14010 way unique to the HSDir flag. Of all the flags, only HSDirs need a
14011 DirPort configured in order for the authorities to assign that
14012 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
14014 - Fix the usage message of tor-resolve(1) so that it no longer lists
14015 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
14018 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
14019 and always use the internal Base64 decoder. The internal decoder
14020 has been part of tor since 0.2.0.10-alpha, and no one should
14021 be using the OpenSSL one. Part of ticket 15652.
14022 - Remove the 'tor_strclear()' function; use memwipe() instead.
14023 Closes ticket 14922.
14024 - Remove the code that would try to aggressively flush controller
14025 connections while writing to them. This code was introduced in
14026 0.1.2.7-alpha, in order to keep output buffers from exceeding
14027 their limits. But there is no longer a maximum output buffer size,
14028 and flushing data in this way caused some undesirable recursions
14029 in our call graph. Closes ticket 16480.
14030 - The internal pure-C tor-fw-helper tool is now removed from the Tor
14031 distribution, in favor of the pure-Go clone available from
14032 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
14033 used by the C tor-fw-helper are not, in our opinion, very
14034 confidence- inspiring in their secure-programming techniques.
14035 Closes ticket 13338.
14037 o Removed features:
14038 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
14039 fingerprinting we now recommend pluggable transports; for forward-
14040 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
14041 - Remove the HidServDirectoryV2 option. Now all relays offer to
14042 store hidden service descriptors. Related to 16543.
14043 - Remove the VoteOnHidServDirectoriesV2 option, since all
14044 authorities have long set it to 1. Closes ticket 16543.
14045 - Remove the undocumented "--digests" command-line option. It
14046 complicated our build process, caused subtle build issues on
14047 multiple platforms, and is now redundant since we started
14048 including git version identifiers. Closes ticket 14742.
14049 - Tor no longer contains checks for ancient directory cache versions
14050 that didn't know about microdescriptors.
14051 - Tor no longer contains workarounds for stat files generated by
14052 super-old versions of Tor that didn't choose guards sensibly.
14055 - The test-network.sh script now supports performance testing.
14056 Requires corresponding chutney performance testing changes. Patch
14057 by "teor". Closes ticket 14175.
14058 - Add a new set of callgraph analysis scripts that use clang to
14059 produce a list of which Tor functions are reachable from which
14060 other Tor functions. We're planning to use these to help simplify
14061 our code structure by identifying illogical dependencies.
14062 - Add new 'test-full' and 'test-full-online' targets to run all
14063 tests, including integration tests with stem and chutney.
14064 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
14065 by-side in the same parent directory. Closes ticket 16903. Patch
14067 - Document use of coverity, clang static analyzer, and clang dynamic
14068 undefined behavior and address sanitizers in doc/HACKING. Include
14069 detailed usage instructions in the blacklist. Patch by "teor".
14070 Closes ticket 15817.
14071 - Make "bridges+hs" the default test network. This tests almost all
14072 tor functionality during make test-network, while allowing tests
14073 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
14074 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
14075 (chutney). Patches by "teor".
14076 - Make the test-workqueue test work on Windows by initializing the
14077 network before we begin.
14078 - New make target (make test-network-all) to run multiple applicable
14079 chutney test cases. Patch from Teor; closes 16953.
14080 - Now that OpenSSL has its own scrypt implementation, add an unit
14081 test that checks for interoperability between libscrypt_scrypt()
14082 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
14083 and rely on EVP_PBE_scrypt() whenever possible. Resolves
14085 - The link authentication protocol code now has extensive tests.
14086 - The relay descriptor signature testing code now has
14088 - The test_workqueue program now runs faster, and is enabled by
14089 default as a part of "make check".
14090 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
14091 functions in dns.c. Implements a portion of ticket 16831.
14092 - Use environment variables rather than autoconf substitutions to
14093 send variables from the build system to the test scripts. This
14094 change should be easier to maintain, and cause 'make distcheck' to
14095 work better than before. Fixes bug 17148.
14096 - When building Tor with testing coverage enabled, run Chutney tests
14097 (if any) using the 'tor-cov' coverage binary.
14098 - When running test-network or test-stem, check for the absence of
14099 stem/chutney before doing any build operations.
14100 - Add a test to verify that the compiler does not eliminate our
14101 memwipe() implementation. Closes ticket 15377.
14102 - Add make rule `check-changes` to verify the format of changes
14103 files. Closes ticket 15180.
14104 - Add unit tests for control_event_is_interesting(). Add a compile-
14105 time check that the number of events doesn't exceed the capacity
14106 of control_event_t.event_mask. Closes ticket 15431, checks for
14107 bugs similar to 13085. Patch by "teor".
14108 - Command-line argument tests moved to Stem. Resolves ticket 14806.
14109 - Integrate the ntor, backtrace, and zero-length keys tests into the
14110 automake test suite. Closes ticket 15344.
14111 - Remove assertions during builds to determine Tor's test coverage.
14112 We don't want to trigger these even in assertions, so including
14113 them artificially makes our branch coverage look worse than it is.
14114 This patch provides the new test-stem-full and coverage-html-full
14115 configure options. Implements ticket 15400.
14116 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
14117 explicitly manage consensus flags in testing networks. Patch by
14118 "robgjansen", modified by "teor". Implements part of ticket 14882.
14119 - Check for matching value in server response in ntor_ref.py. Fixes
14120 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
14122 - Set the severity correctly when testing
14123 get_interface_addresses_ifaddrs() and
14124 get_interface_addresses_win32(), so that the tests fail gracefully
14125 instead of triggering an assertion. Fixes bug 15759; bugfix on
14126 0.2.6.3-alpha. Reported by Nicolas Derive.
14128 Changes in version 0.2.6.10 - 2015-07-12
14129 Tor version 0.2.6.10 fixes some significant stability and hidden
14130 service client bugs, bulletproofs the cryptography init process, and
14131 fixes a bug when using the sandbox code with some older versions of
14132 Linux. Everyone running an older version, especially an older version
14133 of 0.2.6, should upgrade.
14135 o Major bugfixes (hidden service clients, stability):
14136 - Stop refusing to store updated hidden service descriptors on a
14137 client. This reverts commit 9407040c59218 (which indeed fixed bug
14138 14219, but introduced a major hidden service reachability
14139 regression detailed in bug 16381). This is a temporary fix since
14140 we can live with the minor issue in bug 14219 (it just results in
14141 some load on the network) but the regression of 16381 is too much
14142 of a setback. First-round fix for bug 16381; bugfix
14145 o Major bugfixes (stability):
14146 - Stop crashing with an assertion failure when parsing certain kinds
14147 of malformed or truncated microdescriptors. Fixes bug 16400;
14148 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
14149 by "cypherpunks_backup".
14150 - Stop random client-side assertion failures that could occur when
14151 connecting to a busy hidden service, or connecting to a hidden
14152 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
14155 o Minor features (geoip):
14156 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
14157 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
14159 o Minor bugfixes (crypto error-handling):
14160 - Check for failures from crypto_early_init, and refuse to continue.
14161 A previous typo meant that we could keep going with an
14162 uninitialized crypto library, and would have OpenSSL initialize
14163 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
14164 when implementing ticket 4900. Patch by "teor".
14166 o Minor bugfixes (Linux seccomp2 sandbox):
14167 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
14168 these when eventfd2() support is missing. Fixes bug 16363; bugfix
14169 on 0.2.6.3-alpha. Patch from "teor".
14172 Changes in version 0.2.6.9 - 2015-06-11
14173 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
14174 requirements for receiving an HSDir flag, and addresses some other small
14175 bugs in the systemd and sandbox code. Clients using circuit isolation
14176 should upgrade; all directory authorities should upgrade.
14178 o Major bugfixes (client-side privacy):
14179 - Properly separate out each SOCKSPort when applying stream
14180 isolation. The error occurred because each port's session group was
14181 being overwritten by a default value when the listener connection
14182 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
14185 o Minor feature (directory authorities, security):
14186 - The HSDir flag given by authorities now requires the Stable flag.
14187 For the current network, this results in going from 2887 to 2806
14188 HSDirs. Also, it makes it harder for an attacker to launch a sybil
14189 attack by raising the effort for a relay to become Stable which
14190 takes at the very least 7 days to do so and by keeping the 96
14191 hours uptime requirement for HSDir. Implements ticket 8243.
14193 o Minor bugfixes (compilation):
14194 - Build with --enable-systemd correctly when libsystemd is
14195 installed, but systemd is not. Fixes bug 16164; bugfix on
14196 0.2.6.3-alpha. Patch from Peter Palfrader.
14198 o Minor bugfixes (Linux seccomp2 sandbox):
14199 - Fix sandboxing to work when running as a relaymby renaming of
14200 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
14201 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
14202 - Allow systemd connections to work with the Linux seccomp2 sandbox
14203 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
14206 o Minor bugfixes (tests):
14207 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
14208 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
14211 Changes in version 0.2.6.8 - 2015-05-21
14212 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
14213 fixes an authority-side bug in assigning the HSDir flag. All directory
14214 authorities should upgrade.
14216 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
14217 - Revert commit that made directory authorities assign the HSDir
14218 flag to relays without a DirPort; this was bad because such relays
14219 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
14222 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
14223 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
14224 a client authorized hidden service. Fixes bug 15823; bugfix
14227 o Minor features (geoip):
14228 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
14229 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
14233 Changes in version 0.2.6.7 - 2015-04-06
14234 Tor 0.2.6.7 fixes two security issues that could be used by an
14235 attacker to crash hidden services, or crash clients visiting hidden
14236 services. Hidden services should upgrade as soon as possible; clients
14237 should upgrade whenever packages become available.
14239 This release also contains two simple improvements to make hidden
14240 services a bit less vulnerable to denial-of-service attacks.
14242 o Major bugfixes (security, hidden service):
14243 - Fix an issue that would allow a malicious client to trigger an
14244 assertion failure and halt a hidden service. Fixes bug 15600;
14245 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
14246 - Fix a bug that could cause a client to crash with an assertion
14247 failure when parsing a malformed hidden service descriptor. Fixes
14248 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
14250 o Minor features (DoS-resistance, hidden service):
14251 - Introduction points no longer allow multiple INTRODUCE1 cells to
14252 arrive on the same circuit. This should make it more expensive for
14253 attackers to overwhelm hidden services with introductions.
14254 Resolves ticket 15515.
14255 - Decrease the amount of reattempts that a hidden service performs
14256 when its rendezvous circuits fail. This reduces the computational
14257 cost for running a hidden service under heavy load. Resolves
14261 Changes in version 0.2.5.12 - 2015-04-06
14262 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
14263 could be used by an attacker to crash hidden services, or crash clients
14264 visiting hidden services. Hidden services should upgrade as soon as
14265 possible; clients should upgrade whenever packages become available.
14267 This release also backports a simple improvement to make hidden
14268 services a bit less vulnerable to denial-of-service attacks.
14270 o Major bugfixes (security, hidden service):
14271 - Fix an issue that would allow a malicious client to trigger an
14272 assertion failure and halt a hidden service. Fixes bug 15600;
14273 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
14274 - Fix a bug that could cause a client to crash with an assertion
14275 failure when parsing a malformed hidden service descriptor. Fixes
14276 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
14278 o Minor features (DoS-resistance, hidden service):
14279 - Introduction points no longer allow multiple INTRODUCE1 cells to
14280 arrive on the same circuit. This should make it more expensive for
14281 attackers to overwhelm hidden services with introductions.
14282 Resolves ticket 15515.
14285 Changes in version 0.2.4.27 - 2015-04-06
14286 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
14287 could be used by an attacker to crash hidden services, or crash clients
14288 visiting hidden services. Hidden services should upgrade as soon as
14289 possible; clients should upgrade whenever packages become available.
14291 This release also backports a simple improvement to make hidden
14292 services a bit less vulnerable to denial-of-service attacks.
14294 o Major bugfixes (security, hidden service):
14295 - Fix an issue that would allow a malicious client to trigger an
14296 assertion failure and halt a hidden service. Fixes bug 15600;
14297 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
14298 - Fix a bug that could cause a client to crash with an assertion
14299 failure when parsing a malformed hidden service descriptor. Fixes
14300 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
14302 o Minor features (DoS-resistance, hidden service):
14303 - Introduction points no longer allow multiple INTRODUCE1 cells to
14304 arrive on the same circuit. This should make it more expensive for
14305 attackers to overwhelm hidden services with introductions.
14306 Resolves ticket 15515.
14309 Changes in version 0.2.6.6 - 2015-03-24
14310 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
14312 It adds numerous safety, security, correctness, and performance
14313 improvements. Client programs can be configured to use more kinds of
14314 sockets, AutomapHosts works better, the multithreading backend is
14315 improved, cell transmission is refactored, test coverage is much
14316 higher, more denial-of-service attacks are handled, guard selection is
14317 improved to handle long-term guards better, pluggable transports
14318 should work a bit better, and some annoying hidden service performance
14319 bugs should be addressed.
14321 o New compiler and system requirements:
14322 - Tor 0.2.6.x requires that your compiler support more of the C99
14323 language standard than before. The 'configure' script now detects
14324 whether your compiler supports C99 mid-block declarations and
14325 designated initializers. If it does not, Tor will not compile.
14327 We may revisit this requirement if it turns out that a significant
14328 number of people need to build Tor with compilers that don't
14329 bother implementing a 15-year-old standard. Closes ticket 13233.
14330 - Tor no longer supports systems without threading support. When we
14331 began working on Tor, there were several systems that didn't have
14332 threads, or where the thread support wasn't able to run the
14333 threads of a single process on multiple CPUs. That no longer
14334 holds: every system where Tor needs to run well now has threading
14335 support. Resolves ticket 12439.
14337 o Deprecated versions and removed support:
14338 - Tor relays older than 0.2.4.18-rc are no longer allowed to
14339 advertise themselves on the network. Closes ticket 13555.
14340 - Tor clients no longer support connecting to hidden services
14341 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
14342 option has been removed. (There shouldn't be any hidden services
14343 running these versions on the network.) Closes ticket 7803.
14345 o Directory authority changes:
14346 - The directory authority Faravahar has a new IP address. This
14347 closes ticket 14487.
14348 - Remove turtles as a directory authority.
14349 - Add longclaw as a new (v3) directory authority. This implements
14350 ticket 13296. This keeps the directory authority count at 9.
14352 o Major features (bridges):
14353 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
14354 transports if they are configured via the "TOR_PT_PROXY"
14355 environment variable. Implements proposal 232. Resolves
14358 o Major features (changed defaults):
14359 - Prevent relay operators from unintentionally running exits: When a
14360 relay is configured as an exit node, we now warn the user unless
14361 the "ExitRelay" option is set to 1. We warn even more loudly if
14362 the relay is configured with the default exit policy, since this
14363 can indicate accidental misconfiguration. Setting "ExitRelay 0"
14364 stops Tor from running as an exit relay. Closes ticket 10067.
14366 o Major features (client performance, hidden services):
14367 - Allow clients to use optimistic data when connecting to a hidden
14368 service, which should remove a round-trip from hidden service
14369 initialization. See proposal 181 for details. Implements
14372 o Major features (directory system):
14373 - Upon receiving an unparseable directory object, if its digest
14374 matches what we expected, then don't try to download it again.
14375 Previously, when we got a descriptor we didn't like, we would keep
14376 trying to download it over and over. Closes ticket 11243.
14377 - When downloading server- or microdescriptors from a directory
14378 server, we no longer launch multiple simultaneous requests to the
14379 same server. This reduces load on the directory servers,
14380 especially when directory guards are in use. Closes ticket 9969.
14381 - When downloading server- or microdescriptors over a tunneled
14382 connection, do not limit the length of our requests to what the
14383 Squid proxy is willing to handle. Part of ticket 9969.
14384 - Authorities can now vote on the correct digests and latest
14385 versions for different software packages. This allows packages
14386 that include Tor to use the Tor authority system as a way to get
14387 notified of updates and their correct digests. Implements proposal
14388 227. Closes ticket 10395.
14390 o Major features (guards):
14391 - Introduce the Guardfraction feature to improves load balancing on
14392 guard nodes. Specifically, it aims to reduce the traffic gap that
14393 guard nodes experience when they first get the Guard flag. This is
14394 a required step if we want to increase the guard lifetime to 9
14395 months or greater. Closes ticket 9321.
14397 o Major features (hidden services):
14398 - Make HS port scanning more difficult by immediately closing the
14399 circuit when a user attempts to connect to a nonexistent port.
14400 Closes ticket 13667.
14401 - Add a HiddenServiceStatistics option that allows Tor relays to
14402 gather and publish statistics about the overall size and volume of
14403 hidden service usage. Specifically, when this option is turned on,
14404 an HSDir will publish an approximate number of hidden services
14405 that have published descriptors to it the past 24 hours. Also, if
14406 a relay has acted as a hidden service rendezvous point, it will
14407 publish the approximate amount of rendezvous cells it has relayed
14408 the past 24 hours. The statistics themselves are obfuscated so
14409 that the exact values cannot be derived. For more details see
14410 proposal 238, "Better hidden service stats from Tor relays". This
14411 feature is currently disabled by default. Implements feature 13192.
14413 o Major features (performance):
14414 - Make the CPU worker implementation more efficient by avoiding the
14415 kernel and lengthening pipelines. The original implementation used
14416 sockets to transfer data from the main thread to the workers, and
14417 didn't allow any thread to be assigned more than a single piece of
14418 work at once. The new implementation avoids communications
14419 overhead by making requests in shared memory, avoiding kernel IO
14420 where possible, and keeping more requests in flight at once.
14421 Implements ticket 9682.
14423 o Major features (relay):
14424 - Raise the minimum acceptable configured bandwidth rate for bridges
14425 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
14426 20 KiB/sec.) Closes ticket 13822.
14427 - Complete revision of the code that relays use to decide which cell
14428 to send next. Formerly, we selected the best circuit to write on
14429 each channel, but we didn't select among channels in any
14430 sophisticated way. Now, we choose the best circuits globally from
14431 among those whose channels are ready to deliver traffic.
14433 This patch implements a new inter-cmux comparison API, a global
14434 high/low watermark mechanism and a global scheduler loop for
14435 transmission prioritization across all channels as well as among
14436 circuits on one channel. This schedule is currently tuned to
14437 (tolerantly) avoid making changes in network performance, but it
14438 should form the basis for major circuit performance increases in
14439 the future. Code by Andrea; tuning by Rob Jansen; implements
14442 o Major features (sample torrc):
14443 - Add a new, infrequently-changed "torrc.minimal". This file is
14444 similar to torrc.sample, but it will change as infrequently as
14445 possible, for the benefit of users whose systems prompt them for
14446 intervention whenever a default configuration file is changed.
14447 Making this change allows us to update torrc.sample to be a more
14448 generally useful "sample torrc".
14450 o Major features (security, unix domain sockets):
14451 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
14452 applications can reach Tor without having to create AF_INET or
14453 AF_INET6 sockets, meaning they can completely disable their
14454 ability to make non-Tor network connections. To create a socket of
14455 this type, use "SocksPort unix:/path/to/socket". Implements
14457 - Support mapping hidden service virtual ports to AF_UNIX sockets.
14458 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
14459 Implements ticket 11485.
14461 o Major bugfixes (client, automap):
14462 - Repair automapping with IPv6 addresses. This automapping should
14463 have worked previously, but one piece of debugging code that we
14464 inserted to detect a regression actually caused the regression to
14465 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
14466 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
14469 o Major bugfixes (crash, OSX, security):
14470 - Fix a remote denial-of-service opportunity caused by a bug in
14471 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
14474 o Major bugfixes (directory authorities):
14475 - Do not assign the HSDir flag to relays if they are not Valid, or
14476 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
14478 o Major bugfixes (directory bandwidth performance):
14479 - Don't flush the zlib buffer aggressively when compressing
14480 directory information for clients. This should save about 7% of
14481 the bandwidth currently used for compressed descriptors and
14482 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
14484 o Major bugfixes (exit node stability):
14485 - Fix an assertion failure that could occur under high DNS load.
14486 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
14487 diagnosed and fixed by "cypherpunks".
14489 o Major bugfixes (FreeBSD IPFW transparent proxy):
14490 - Fix address detection with FreeBSD transparent proxies, when
14491 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
14494 o Major bugfixes (hidden services):
14495 - When closing an introduction circuit that was opened in parallel
14496 with others, don't mark the introduction point as unreachable.
14497 Previously, the first successful connection to an introduction
14498 point would make the other introduction points get marked as
14499 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
14501 o Major bugfixes (Linux seccomp2 sandbox):
14502 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
14503 crash during attempts to call wait4. Fixes bug 15088; bugfix on
14504 0.2.5.1-alpha. Patch from "sanic".
14506 o Major bugfixes (mixed relay-client operation):
14507 - When running as a relay and client at the same time (not
14508 recommended), if we decide not to use a new guard because we want
14509 to retry older guards, only close the locally-originating circuits
14510 passing through that guard. Previously we would close all the
14511 circuits through that guard. Fixes bug 9819; bugfix on
14512 0.2.1.1-alpha. Reported by "skruffy".
14514 o Major bugfixes (pluggable transports):
14515 - Initialize the extended OR Port authentication cookie before
14516 launching pluggable transports. This prevents a race condition
14517 that occurred when server-side pluggable transports would cache the
14518 authentication cookie before it has been (re)generated. Fixes bug
14519 15240; bugfix on 0.2.5.1-alpha.
14521 o Major bugfixes (relay, stability, possible security):
14522 - Fix a bug that could lead to a relay crashing with an assertion
14523 failure if a buffer of exactly the wrong layout is passed to
14524 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
14525 0.2.0.10-alpha. Patch from "cypherpunks".
14526 - Do not assert if the 'data' pointer on a buffer is advanced to the
14527 very end of the buffer; log a BUG message instead. Only assert if
14528 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
14530 o Minor features (build):
14531 - New --disable-system-torrc compile-time option to prevent Tor from
14532 looking for the system-wide torrc or torrc-defaults files.
14533 Resolves ticket 13037.
14535 o Minor features (client):
14536 - Clients are now willing to send optimistic data (before they
14537 receive a 'connected' cell) to relays of any version. (Relays
14538 without support for optimistic data are no longer supported on the
14539 Tor network.) Resolves ticket 13153.
14541 o Minor features (client):
14542 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
14543 is enabled, reject requests with IP addresses as hostnames.
14544 Resolves ticket 13315.
14546 o Minor features (controller):
14547 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
14548 write an unscheduled heartbeat message to the log. Implements
14550 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
14551 events so controllers can observe circuit isolation inputs. Closes
14553 - ControlPort now supports the unix:/path/to/socket syntax as an
14554 alternative to the ControlSocket option, for consistency with
14555 SocksPort and HiddenServicePort. Closes ticket 14451.
14556 - New "GETINFO bw-event-cache" to get information about recent
14557 bandwidth events. Closes ticket 14128. Useful for controllers to
14558 get recent bandwidth history after the fix for ticket 13988.
14559 - Messages about problems in the bootstrap process now include
14560 information about the server we were trying to connect to when we
14561 noticed the problem. Closes ticket 15006.
14563 o Minor features (Denial of service resistance):
14564 - Count the total number of bytes used storing hidden service
14565 descriptors against the value of MaxMemInQueues. If we're low on
14566 memory, and more than 20% of our memory is used holding hidden
14567 service descriptors, free them until no more than 10% of our
14568 memory holds hidden service descriptors. Free the least recently
14569 fetched descriptors first. Resolves ticket 13806.
14570 - When we have recently been under memory pressure (over 3/4 of
14571 MaxMemInQueues is allocated), then allocate smaller zlib objects
14572 for small requests. Closes ticket 11791.
14574 o Minor features (directory authorities):
14575 - Don't list relays with a bandwidth estimate of 0 in the consensus.
14576 Implements a feature proposed during discussion of bug 13000.
14577 - In tor-gencert, report an error if the user provides the same
14578 argument more than once.
14579 - If a directory authority can't find a best consensus method in the
14580 votes that it holds, it now falls back to its favorite consensus
14581 method. Previously, it fell back to method 1. Neither of these is
14582 likely to get enough signatures, but "fall back to favorite"
14583 doesn't require us to maintain support an obsolete consensus
14584 method. Implements part of proposal 215.
14586 o Minor features (geoip):
14587 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
14588 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
14591 o Minor features (guard nodes):
14592 - Reduce the time delay before saving guard status to disk from 10
14593 minutes to 30 seconds (or from one hour to 10 minutes if
14594 AvoidDiskWrites is set). Closes ticket 12485.
14596 o Minor features (heartbeat):
14597 - On relays, report how many connections we negotiated using each
14598 version of the Tor link protocols. This information will let us
14599 know if removing support for very old versions of the Tor
14600 protocols is harming the network. Closes ticket 15212.
14602 o Minor features (hidden service):
14603 - Make Sybil attacks against hidden services harder by changing the
14604 minimum time required to get the HSDir flag from 25 hours up to 96
14605 hours. Addresses ticket 14149.
14606 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
14607 services to disable the anti-scanning feature introduced in
14608 0.2.6.2-alpha. With this option not set, a connection to an
14609 unlisted port closes the circuit. With this option set, only a
14610 RELAY_DONE cell is sent. Closes ticket 14084.
14611 - When re-enabling the network, don't try to build introduction
14612 circuits until we have successfully built a circuit. This makes
14613 hidden services come up faster when the network is re-enabled.
14614 Patch from "akwizgran". Closes ticket 13447.
14615 - When we fail to retrieve a hidden service descriptor, send the
14616 controller an "HS_DESC FAILED" controller event. Implements
14618 - New HiddenServiceDirGroupReadable option to cause hidden service
14619 directories and hostname files to be created group-readable. Patch
14620 from "anon", David Stainton, and "meejah". Closes ticket 11291.
14622 o Minor features (interface):
14623 - Implement "-f -" command-line option to read torrc configuration
14624 from standard input, if you don't want to store the torrc file in
14625 the file system. Implements feature 13865.
14627 o Minor features (logging):
14628 - Add a count of unique clients to the bridge heartbeat message.
14629 Resolves ticket 6852.
14630 - Suppress "router info incompatible with extra info" message when
14631 reading extrainfo documents from cache. (This message got loud
14632 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
14634 - Elevate hidden service authorized-client message from DEBUG to
14635 INFO. Closes ticket 14015.
14636 - On Unix-like systems, you can now use named pipes as the target of
14637 the Log option, and other options that try to append to files.
14638 Closes ticket 12061. Patch from "carlo von lynX".
14639 - When opening a log file at startup, send it every log message that
14640 we generated between startup and opening it. Previously, log
14641 messages that were generated before opening the log file were only
14642 logged to stdout. Closes ticket 6938.
14643 - Add a TruncateLogFile option to overwrite logs instead of
14644 appending to them. Closes ticket 5583.
14645 - Quiet some log messages in the heartbeat and at startup. Closes
14648 o Minor features (portability, Solaris):
14649 - Threads are no longer disabled by default on Solaris; we believe
14650 that the versions of Solaris with broken threading support are all
14651 obsolete by now. Resolves ticket 9495.
14653 o Minor features (relay):
14654 - Re-check our address after we detect a changed IP address from
14655 getsockname(). This ensures that the controller command "GETINFO
14656 address" will report the correct value. Resolves ticket 11582.
14658 - A new AccountingRule option lets Relays set whether they'd like
14659 AccountingMax to be applied separately to inbound and outbound
14660 traffic, or applied to the sum of inbound and outbound traffic.
14661 Resolves ticket 961. Patch by "chobe".
14662 - When identity keypair is generated for first time, log a
14663 congratulatory message that links to the new relay lifecycle
14664 document. Implements feature 10427.
14666 o Minor features (security, memory wiping):
14667 - Ensure we securely wipe keys from memory after
14668 crypto_digest_get_digest and init_curve25519_keypair_from_file
14669 have finished using them. Resolves ticket 13477.
14671 o Minor features (security, out-of-memory handling):
14672 - When handling an out-of-memory condition, allocate less memory for
14673 temporary data structures. Fixes issue 10115.
14674 - When handling an out-of-memory condition, consider more types of
14675 buffers, including those on directory connections, and zlib
14676 buffers. Resolves ticket 11792.
14678 o Minor features (stability):
14679 - Add assertions in our hash-table iteration code to check for
14680 corrupted values that could cause infinite loops. Closes
14683 o Minor features (systemd):
14684 - Various improvements and modernizations in systemd hardening
14685 support. Closes ticket 13805. Patch from Craig Andrews.
14686 - Where supported, when running with systemd, report successful
14687 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
14688 - When running with systemd, support systemd watchdog messages. Part
14689 of ticket 11016. Patch by Michael Scherer.
14691 o Minor features (testing networks):
14692 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
14693 the "Exit" flag regardless of their uptime, bandwidth, or exit
14694 policy. TestingTorNetwork must be set for this option to have any
14695 effect. Previously, authorities would take up to 35 minutes to
14696 give nodes the Exit flag in a test network. Partially implements
14698 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
14699 and the default on a testing network to 2 minutes. Drop the
14700 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
14701 keep the default on a testing network at 30 seconds. This reduces
14702 HS bootstrap time to around 25 seconds. Also, change the default
14703 time in test-network.sh to match. Closes ticket 13401. Patch
14705 - Create TestingDirAuthVoteHSDir to correspond to
14706 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
14707 HSDir flag for the listed relays regardless of uptime or ORPort
14708 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
14709 Partial implementation for ticket 14067. Patch by "teor".
14711 o Minor features (tor2web mode):
14712 - Introduce the config option Tor2webRendezvousPoints, which allows
14713 clients in Tor2webMode to select a specific Rendezvous Point to be
14714 used in HS circuits. This might allow better performance for
14715 Tor2Web nodes. Implements ticket 12844.
14717 o Minor features (transparent proxy):
14718 - Update the transparent proxy option checks to allow for both ipfw
14719 and pf on OS X. Closes ticket 14002.
14720 - Use the correct option when using IPv6 with transparent proxy
14721 support on Linux. Resolves 13808. Patch by Francisco Blas
14724 o Minor features (validation):
14725 - Check all date/time values passed to tor_timegm and
14726 parse_rfc1123_time for validity, taking leap years into account.
14727 Improves HTTP header validation. Implemented with bug 13476.
14728 - In correct_tm(), limit the range of values returned by system
14729 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
14730 This means we don't have to deal with negative or too large dates,
14731 even if a clock is wrong. Otherwise we might fail to read a file
14732 written by us which includes such a date. Fixes bug 13476.
14733 - Stop allowing invalid address patterns like "*/24" that contain
14734 both a wildcard address and a bit prefix length. This affects all
14735 our address-range parsing code. Fixes bug 7484; bugfix
14738 o Minor bugfixes (bridge clients):
14739 - When configured to use a bridge without an identity digest (not
14740 recommended), avoid launching an extra channel to it when
14741 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
14743 o Minor bugfixes (bridges):
14744 - When DisableNetwork is set, do not launch pluggable transport
14745 plugins, and if any are running, terminate them. Fixes bug 13213;
14746 bugfix on 0.2.3.6-alpha.
14748 o Minor bugfixes (C correctness):
14749 - Fix several instances of possible integer overflow/underflow/NaN.
14750 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
14752 - In circuit_build_times_calculate_timeout() in circuitstats.c,
14753 avoid dividing by zero in the pareto calculations. This traps
14754 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
14756 - Fix an integer overflow in format_time_interval(). Fixes bug
14757 13393; bugfix on 0.2.0.10-alpha.
14758 - Set the correct day of year value when the system's localtime(_r)
14759 or gmtime(_r) functions fail to set struct tm. Not externally
14760 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
14761 - Avoid unlikely signed integer overflow in tor_timegm on systems
14762 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
14764 o Minor bugfixes (certificate handling):
14765 - If an authority operator accidentally makes a signing certificate
14766 with a future publication time, do not discard its real signing
14767 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
14768 - Remove any old authority certificates that have been superseded
14769 for at least two days. Previously, we would keep superseded
14770 certificates until they expired, if they were published close in
14771 time to the certificate that superseded them. Fixes bug 11454;
14772 bugfix on 0.2.1.8-alpha.
14774 o Minor bugfixes (client):
14775 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
14776 BadExit flag are not considered worthy candidates. Fixes bug
14777 13066; bugfix on 0.1.2.3-alpha.
14778 - Use the consensus schedule for downloading consensuses, and not
14779 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
14780 - Handle unsupported or malformed SOCKS5 requests properly by
14781 responding with the appropriate error message before closing the
14782 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
14784 o Minor bugfixes (client, automapping):
14785 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
14786 no value follows the option. Fixes bug 14142; bugfix on
14787 0.2.4.7-alpha. Patch by "teor".
14788 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
14789 14195; bugfix on 0.1.0.1-rc.
14790 - Prevent changes to other options from removing the wildcard value
14791 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
14793 - Allow MapAddress and AutomapHostsOnResolve to work together when
14794 an address is mapped into another address type (like .onion) that
14795 must be automapped at resolve time. Fixes bug 7555; bugfix
14798 o Minor bugfixes (client, bridges):
14799 - When we are using bridges and we had a network connectivity
14800 problem, only retry connecting to our currently configured
14801 bridges, not all bridges we know about and remember using. Fixes
14802 bug 14216; bugfix on 0.2.2.17-alpha.
14804 o Minor bugfixes (client, DNS):
14805 - Report the correct cached DNS expiration times on SOCKS port or in
14806 DNS replies. Previously, we would report everything as "never
14807 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
14808 - Avoid a small memory leak when we find a cached answer for a
14809 reverse DNS lookup in a client-side DNS cache. (Remember, client-
14810 side DNS caching is off by default, and is not recommended.) Fixes
14811 bug 14259; bugfix on 0.2.0.1-alpha.
14813 o Minor bugfixes (client, IPv6):
14814 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
14815 flag is not set; and not because the NoIPv4Traffic flag was set.
14816 Previously we'd looked at the NoIPv4Traffic flag for both types of
14817 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
14819 o Minor bugfixes (client, microdescriptors):
14820 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
14821 computing which microdescriptors to download. This keeps us from
14822 erroneous download behavior if two microdescriptor digests ever
14823 have the same first 160 bits. Fixes part of bug 13399; bugfix
14825 - Reset a router's status if its microdescriptor digest changes,
14826 even if the first 160 bits remain the same. Fixes part of bug
14827 13399; bugfix on 0.2.3.1-alpha.
14829 o Minor bugfixes (client, torrc):
14830 - Stop modifying the value of our DirReqStatistics torrc option just
14831 because we're not a bridge or relay. This bug was causing Tor
14832 Browser users to write "DirReqStatistics 0" in their torrc files
14833 as if they had chosen to change the config. Fixes bug 4244; bugfix
14835 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
14836 that our options have changed every time we SIGHUP. Fixes bug
14837 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
14839 o Minor bugfixes (compilation):
14840 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
14842 - Silence clang warnings under --enable-expensive-hardening,
14843 including implicit truncation of 64 bit values to 32 bit, const
14844 char assignment to self, tautological compare, and additional
14845 parentheses around equality tests. Fixes bug 13577; bugfix
14847 - Fix a clang warning about checking whether an address in the
14848 middle of a structure is NULL. Fixes bug 14001; bugfix
14850 - The address of an array in the middle of a structure will always
14851 be non-NULL. clang recognises this and complains. Disable the
14852 tautologous and redundant check to silence this warning. Fixes bug
14853 14001; bugfix on 0.2.1.2-alpha.
14854 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
14855 Addresses ticket 14188.
14856 - Build without warnings with the stock OpenSSL srtp.h header, which
14857 has a duplicate declaration of SSL_get_selected_srtp_profile().
14858 Fixes bug 14220; this is OpenSSL's bug, not ours.
14859 - Do not compile any code related to Tor2Web mode when Tor2Web mode
14860 is not enabled at compile time. Previously, this code was included
14861 in a disabled state. See discussion on ticket 12844.
14862 - Allow our configure script to build correctly with autoconf 2.62
14863 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
14864 - Improve the error message from ./configure to make it clear that
14865 when asciidoc has not been found, the user will have to either add
14866 --disable-asciidoc argument or install asciidoc. Resolves
14869 o Minor bugfixes (controller):
14870 - Report "down" in response to the "GETINFO entry-guards" command
14871 when relays are down with an unreachable_since value. Previously,
14872 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
14873 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
14874 14116; bugfix on 0.2.2.9-alpha.
14876 o Minor bugfixes (controller):
14877 - Return an error when the second or later arguments of the
14878 "setevents" controller command are invalid events. Previously we
14879 would return success while silently skipping invalid events. Fixes
14880 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
14882 o Minor bugfixes (directory authority):
14883 - Allow directory authorities to fetch more data from one another if
14884 they find themselves missing lots of votes. Previously, they had
14885 been bumping against the 10 MB queued data limit. Fixes bug 14261;
14886 bugfix on 0.1.2.5-alpha.
14887 - Do not attempt to download extrainfo documents which we will be
14888 unable to validate with a matching server descriptor. Fixes bug
14889 13762; bugfix on 0.2.0.1-alpha.
14890 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
14891 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
14892 - Enlarge the buffer to read bwauth generated files to avoid an
14893 issue when parsing the file in dirserv_read_measured_bandwidths().
14894 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
14895 - When running as a v3 directory authority, advertise that you serve
14896 extra-info documents so that clients who want them can find them
14897 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
14899 o Minor bugfixes (directory system):
14900 - Always believe that v3 directory authorities serve extra-info
14901 documents, whether they advertise "caches-extra-info" or not.
14902 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
14903 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
14904 Previously, directories offering BRIDGE_DIRINFO and some other
14905 flag (i.e. microdescriptors or extrainfo) would be ignored when
14906 looking for bridges. Partially fixes bug 13163; bugfix
14909 o Minor bugfixes (file handling):
14910 - Stop failing when key files are zero-length. Instead, generate new
14911 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
14912 on all versions of Tor. Patch by "teor".
14913 - Stop generating a fresh .old RSA onion key file when the .old file
14914 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
14915 - Avoid overwriting .old key files with empty key files.
14916 - Skip loading zero-length extrainfo store, router store, stats,
14917 state, and key files.
14918 - Avoid crashing when trying to reload a torrc specified as a
14919 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
14922 o Minor bugfixes (hidden services):
14923 - Close the introduction circuit when we have no more usable intro
14924 points, instead of waiting for it to time out. This also ensures
14925 that no follow-up HS descriptor fetch is triggered when the
14926 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
14927 - When fetching a hidden service descriptor for a down service that
14928 was recently up, do not keep refetching until we try the same
14929 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
14930 - Correctly send a controller event when we find that a rendezvous
14931 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
14932 - Pre-check directory permissions for new hidden-services to avoid
14933 at least one case of "Bug: Acting on config options left us in a
14934 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
14935 - When fetching hidden service descriptors, we now check not only
14936 for whether we got the hidden service we had in mind, but also
14937 whether we got the particular descriptors we wanted. This prevents
14938 a class of inefficient but annoying DoS attacks by hidden service
14939 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
14942 o Minor bugfixes (Linux seccomp2 sandbox):
14943 - Make transparent proxy support work along with the seccomp2
14944 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
14945 by Francisco Blas Izquierdo Riera.
14946 - Fix a memory leak in tor-resolve when running with the sandbox
14947 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
14948 - Allow glibc fatal errors to be sent to stderr before Tor exits.
14949 Previously, glibc would try to write them to /dev/tty, and the
14950 sandbox would trap the call and make Tor exit prematurely. Fixes
14951 bug 14759; bugfix on 0.2.5.1-alpha.
14953 o Minor bugfixes (logging):
14954 - Avoid crashing when there are more log domains than entries in
14955 domain_list. Bugfix on 0.2.3.1-alpha.
14956 - Downgrade warnings about RSA signature failures to info log level.
14957 Emit a warning when an extra info document is found incompatible
14958 with a corresponding router descriptor. Fixes bug 9812; bugfix
14960 - Make connection_ap_handshake_attach_circuit() log the circuit ID
14961 correctly. Fixes bug 13701; bugfix on 0.0.6.
14963 o Minor bugfixes (networking):
14964 - Check for orconns and use connection_or_close_for_error() rather
14965 than connection_mark_for_close() directly in the getsockopt()
14966 failure case of connection_handle_write_impl(). Fixes bug 11302;
14967 bugfix on 0.2.4.4-alpha.
14969 o Minor bugfixes (parsing):
14970 - Stop accepting milliseconds (or other junk) at the end of
14971 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
14972 - Support two-number and three-number version numbers correctly, in
14973 case we change the Tor versioning system in the future. Fixes bug
14974 13661; bugfix on 0.0.8pre1.
14976 o Minor bugfixes (portability):
14977 - Fix the ioctl()-based network interface lookup code so that it
14978 will work on systems that have variable-length struct ifreq, for
14980 - Use the correct datatype in the SipHash-2-4 function to prevent
14981 compilers from assuming any sort of alignment. Fixes bug 15436;
14982 bugfix on 0.2.5.3-alpha.
14984 o Minor bugfixes (preventative security, C safety):
14985 - When reading a hexadecimal, base-32, or base-64 encoded value from
14986 a string, always overwrite the whole output buffer. This prevents
14987 some bugs where we would look at (but fortunately, not reveal)
14988 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
14990 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
14991 just the part that's used. This makes it harder for data leak bugs
14992 to occur in the event of other programming failures. Resolves
14995 o Minor bugfixes (relay):
14996 - When generating our family list, remove spaces from around the
14997 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
14998 - If our previous bandwidth estimate was 0 bytes, allow publishing a
14999 new relay descriptor immediately. Fixes bug 13000; bugfix
15002 o Minor bugfixes (shutdown):
15003 - When shutting down, always call event_del() on lingering read or
15004 write events before freeing them. Otherwise, we risk double-frees
15005 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
15008 o Minor bugfixes (small memory leaks):
15009 - Avoid leaking memory when using IPv6 virtual address mappings.
15010 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
15013 o Minor bugfixes (statistics):
15014 - Increase period over which bandwidth observations are aggregated
15015 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
15017 o Minor bugfixes (systemd support):
15018 - Run correctly under systemd with the RunAsDaemon option set. Fixes
15019 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
15020 - Inform the systemd supervisor about more changes in the Tor
15021 process status. Implements part of ticket 14141. Patch from
15024 o Minor bugfixes (testing networks):
15025 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
15026 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
15027 - Stop using the default authorities in networks which provide both
15028 AlternateDirAuthority and AlternateBridgeAuthority. Partially
15029 fixes bug 13163; bugfix on 0.2.0.13-alpha.
15031 o Minor bugfixes (testing networks, fast startup):
15032 - Allow Tor to build circuits using a consensus with no exits. If
15033 the consensus has no exits (typical of a bootstrapping test
15034 network), allow Tor to build circuits once enough descriptors have
15035 been downloaded. This assists in bootstrapping a testing Tor
15036 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
15038 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
15039 header to directory servers. This allows us to obtain consensuses
15040 promptly when the consensus interval is very short. This assists
15041 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
15042 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
15043 - Stop assuming that private addresses are local when checking
15044 reachability in a TestingTorNetwork. Instead, when testing, assume
15045 all OR connections are remote. (This is necessary due to many test
15046 scenarios running all relays on localhost.) This assists in
15047 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
15048 0.1.0.1-rc. Patch by "teor".
15049 - Avoid building exit circuits from a consensus with no exits. Now
15050 thanks to our fix for 13718, we accept a no-exit network as not
15051 wholly lost, but we need to remember not to try to build exit
15052 circuits on it. Closes ticket 13814; patch by "teor".
15053 - Stop requiring exits to have non-zero bandwithcapacity in a
15054 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
15055 ignore exit bandwidthcapacity. This assists in bootstrapping a
15056 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
15057 on 0.2.0.3-alpha. Patch by "teor".
15058 - Add "internal" to some bootstrap statuses when no exits are
15059 available. If the consensus does not contain Exits, Tor will only
15060 build internal circuits. In this case, relevant statuses will
15061 contain the word "internal" as indicated in the Tor control-
15062 spec.txt. When bootstrap completes, Tor will be ready to build
15063 internal circuits. If a future consensus contains Exits, exit
15064 circuits may become available. Fixes part of bug 13718; bugfix on
15065 0.2.4.10-alpha. Patch by "teor".
15066 - Decrease minimum consensus interval to 10 seconds when
15067 TestingTorNetwork is set, or 5 seconds for the first consensus.
15068 Fix assumptions throughout the code that assume larger intervals.
15069 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
15071 - Avoid excluding guards from path building in minimal test
15072 networks, when we're in a test network and excluding guards would
15073 exclude all relays. This typically occurs in incredibly small tor
15074 networks, and those using "TestingAuthVoteGuard *". Fixes part of
15075 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
15077 o Minor bugfixes (testing):
15078 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
15079 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
15080 - Stop spawn test failures due to a race condition between the
15081 SIGCHLD handler updating the process status, and the test reading
15082 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
15083 - Avoid passing an extra backslash when creating a temporary
15084 directory for running the unit tests on Windows. Fixes bug 12392;
15085 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
15087 o Minor bugfixes (TLS):
15088 - Check more thoroughly throughout the TLS code for possible
15089 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
15091 o Minor bugfixes (transparent proxy):
15092 - Use getsockname, not getsockopt, to retrieve the address for a
15093 TPROXY-redirected connection. Fixes bug 13796; bugfix
15096 o Minor bugfixes (windows):
15097 - Remove code to special-case handling of NTE_BAD_KEYSET when
15098 acquiring windows CryptoAPI context. This error can't actually
15099 occur for the parameters we're providing. Fixes bug 10816; bugfix
15102 o Minor bugfixes (zlib):
15103 - Avoid truncating a zlib stream when trying to finalize it with an
15104 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
15106 o Code simplification and refactoring:
15107 - Change the entry_is_live() function to take named bitfield
15108 elements instead of an unnamed list of booleans. Closes
15110 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
15111 Resolves ticket 12205.
15112 - Use calloc and reallocarray functions instead of multiply-
15113 then-malloc. This makes it less likely for us to fall victim to an
15114 integer overflow attack when allocating. Resolves ticket 12855.
15115 - Use the standard macro name SIZE_MAX, instead of our
15117 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
15118 functions which take them as arguments. Replace 0 with NO_DIRINFO
15119 in a function call for clarity. Seeks to prevent future issues
15121 - Avoid 4 null pointer errors under clang static analysis by using
15122 tor_assert() to prove that the pointers aren't null. Fixes
15124 - Rework the API of policies_parse_exit_policy() to use a bitmask to
15125 represent parsing options, instead of a confusing mess of
15126 booleans. Resolves ticket 8197.
15127 - Introduce a helper function to parse ExitPolicy in
15128 or_options_t structure.
15129 - Move fields related to isolating and configuring client ports into
15130 a shared structure. Previously, they were duplicated across
15131 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
15132 to copy them correctly had been the cause of at least one bug in
15133 the past. Closes ticket 8546.
15134 - Refactor the get_interface_addresses_raw() doom-function into
15135 multiple smaller and simpler subfunctions. Cover the resulting
15136 subfunctions with unit-tests. Fixes a significant portion of
15138 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
15139 only for version <= 0.2.2.24 which is now deprecated. Closes
15141 - Remove a test for a long-defunct broken version-one
15143 - Refactor main loop to extract the 'loop' part. This makes it
15144 easier to run Tor under Shadow. Closes ticket 15176.
15145 - Stop using can_complete_circuits as a global variable; access it
15146 with a function instead.
15147 - Avoid using operators directly as macro arguments: this lets us
15148 apply coccinelle transformations to our codebase more directly.
15149 Closes ticket 13172.
15150 - Combine the functions used to parse ClientTransportPlugin and
15151 ServerTransportPlugin into a single function. Closes ticket 6456.
15152 - Add inline functions and convenience macros for inspecting channel
15153 state. Refactor the code to use convenience macros instead of
15154 checking channel state directly. Fixes issue 7356.
15155 - Document all members of was_router_added_t and rename
15156 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
15157 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
15158 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
15159 constant instead of hardcoded value. Fixes issue 13840.
15160 - Refactor our generic strmap and digestmap types into a single
15161 implementation, so that we can add a new digest256map
15165 - Add a doc/TUNING document with tips for handling large numbers of
15166 TCP connections when running busy Tor relay. Update the warning
15167 message to point to this file when running out of sockets
15168 operating system is allowing to use simultaneously. Resolves
15170 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
15171 for writing the OpenBSD-specific tips. Resolves ticket 13702.
15172 - Make the tor-resolve documentation match its help string and its
15173 options. Resolves part of ticket 14325.
15174 - Log a more useful error message from tor-resolve when failing to
15175 look up a hidden service address. Resolves part of ticket 14325.
15176 - Document the bridge-authority-only 'networkstatus-bridges' file.
15177 Closes ticket 13713; patch from "tom".
15178 - Fix typo in PredictedPortsRelevanceTime option description in
15179 manpage. Resolves issue 13707.
15180 - Stop suggesting that users specify relays by nickname: it isn't a
15181 good idea. Also, properly cross-reference how to specify relays in
15182 all parts of manual documenting options that take a list of
15183 relays. Closes ticket 13381.
15184 - Clarify the HiddenServiceDir option description in manpage to make
15185 it clear that relative paths are taken with respect to the current
15186 working directory. Also clarify that this behavior is not
15187 guaranteed to remain indefinitely. Fixes issue 13913.
15189 o Distribution (systemd):
15190 - systemd unit file: only allow tor to write to /var/lib/tor and
15191 /var/log/tor. The rest of the filesystem is accessible for reading
15192 only. Patch by intrigeri; resolves ticket 12751.
15193 - systemd unit file: ensure that the process and all its children
15194 can never gain new privileges. Patch by intrigeri; resolves
15196 - systemd unit file: set up /var/run/tor as writable for the Tor
15197 service. Patch by intrigeri; resolves ticket 13196.
15199 o Downgraded warnings:
15200 - Don't warn when we've attempted to contact a relay using the wrong
15201 ntor onion key. Closes ticket 9635.
15204 - Remove some lingering dead code that once supported mempools.
15205 Mempools were disabled by default in 0.2.5, and removed entirely
15206 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
15209 o Removed features (directory authorities):
15210 - Remove code that prevented authorities from listing Tor relays
15211 affected by CVE-2011-2769 as guards. These relays are already
15212 rejected altogether due to the minimum version requirement of
15213 0.2.3.16-alpha. Closes ticket 13152.
15214 - The "AuthDirRejectUnlisted" option no longer has any effect, as
15215 the fingerprints file (approved-routers) has been deprecated.
15216 - Directory authorities do not support being Naming dirauths anymore.
15217 The "NamingAuthoritativeDir" config option is now obsolete.
15218 - Directory authorities do not support giving out the BadDirectory
15220 - Directory authorities no longer advertise or support consensus
15221 methods 1 through 12 inclusive. These consensus methods were
15222 obsolete and/or insecure: maintaining the ability to support them
15223 served no good purpose. Implements part of proposal 215; closes
15226 o Removed features:
15227 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
15228 longer silently accepted as an alias for "ExitNodes".
15229 - The --enable-mempool and --enable-buf-freelists options, which
15230 were originally created to work around bad malloc implementations,
15231 no longer exist. They were off-by-default in 0.2.5. Closes
15233 - We no longer remind the user about configuration options that have
15234 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
15235 - Remove our old, non-weighted bandwidth-based node selection code.
15236 Previously, we used it as a fallback when we couldn't perform
15237 weighted bandwidth-based node selection. But that would only
15238 happen in the cases where we had no consensus, or when we had a
15239 consensus generated by buggy or ancient directory authorities. In
15240 either case, it's better to use the more modern, better maintained
15241 algorithm, with reasonable defaults for the weights. Closes
15243 - Remove the --disable-curve25519 configure option. Relays and
15244 clients now are required to support curve25519 and the
15246 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
15247 used to be deprecated synonyms for "StrictNodes", are now marked
15248 obsolete. Resolves ticket 12226.
15249 - Clients don't understand the BadDirectory flag in the consensus
15250 anymore, and ignore it.
15252 o Removed platform support:
15253 - We no longer include special code to build on Windows CE; as far
15254 as we know, nobody has used Tor on Windows CE in a very long time.
15255 Closes ticket 11446.
15257 o Testing (test-network.sh):
15258 - Stop using "echo -n", as some shells' built-in echo doesn't
15259 support "-n". Instead, use "/bin/echo -n". Partially fixes
15261 - Stop an apparent test-network hang when used with make -j2. Fixes
15263 - Add a --delay option to test-network.sh, which configures the
15264 delay before the chutney network tests for data transmission.
15265 Partially implements ticket 13161.
15268 - Test that tor does not fail when key files are zero-length. Check
15269 that tor generates new keys, and overwrites the empty key files.
15270 - Test that tor generates new keys when keys are missing
15271 (existing behavior).
15272 - Test that tor does not overwrite key files that already contain
15273 data (existing behavior). Tests bug 13111. Patch by "teor".
15274 - New "make test-stem" target to run stem integration tests.
15275 Requires that the "STEM_SOURCE_DIR" environment variable be set.
15276 Closes ticket 14107.
15277 - Make the test_cmdline_args.py script work correctly on Windows.
15278 Patch from Gisle Vanem.
15279 - Move the slower unit tests into a new "./src/test/test-slow"
15280 binary that can be run independently of the other tests. Closes
15282 - New tests for many parts of channel, relay, and circuitmux
15283 functionality. Code by Andrea; part of 9262.
15284 - New tests for parse_transport_line(). Part of ticket 6456.
15285 - In the unit tests, use chgrp() to change the group of the unit
15286 test temporary directory to the current user, so that the sticky
15287 bit doesn't interfere with tests that check directory groups.
15289 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
15291 - Refactor the function that chooses guard nodes so that it can more
15292 easily be tested; write some tests for it.
15293 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
15294 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
15295 - Create unit tests for format_time_interval(). With bug 13393.
15296 - Add unit tests for tor_timegm signed overflow, tor_timegm and
15297 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
15298 tests (visible) fixes in bug 13476.
15299 - Add a "coverage-html" make target to generate HTML-visualized
15300 coverage results when building with --enable-coverage. (Requires
15301 lcov.) Patch from Kevin Murray.
15302 - Enable the backtrace handler (where supported) when running the
15304 - Revise all unit tests that used the legacy test_* macros to
15305 instead use the recommended tt_* macros. This patch was generated
15306 with coccinelle, to avoid manual errors. Closes ticket 13119.
15308 Changes in version 0.2.5.11 - 2015-03-17
15309 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
15311 It backports several bugfixes from the 0.2.6 branch, including a
15312 couple of medium-level security fixes for relays and exit nodes.
15313 It also updates the list of directory authorities.
15315 o Directory authority changes:
15316 - Remove turtles as a directory authority.
15317 - Add longclaw as a new (v3) directory authority. This implements
15318 ticket 13296. This keeps the directory authority count at 9.
15319 - The directory authority Faravahar has a new IP address. This
15320 closes ticket 14487.
15322 o Major bugfixes (crash, OSX, security):
15323 - Fix a remote denial-of-service opportunity caused by a bug in
15324 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
15327 o Major bugfixes (relay, stability, possible security):
15328 - Fix a bug that could lead to a relay crashing with an assertion
15329 failure if a buffer of exactly the wrong layout was passed to
15330 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
15331 0.2.0.10-alpha. Patch from 'cypherpunks'.
15332 - Do not assert if the 'data' pointer on a buffer is advanced to the
15333 very end of the buffer; log a BUG message instead. Only assert if
15334 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
15336 o Major bugfixes (exit node stability):
15337 - Fix an assertion failure that could occur under high DNS load.
15338 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
15339 diagnosed and fixed by "cypherpunks".
15341 o Major bugfixes (Linux seccomp2 sandbox):
15342 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
15343 crash during attempts to call wait4. Fixes bug 15088; bugfix on
15344 0.2.5.1-alpha. Patch from "sanic".
15346 o Minor features (controller):
15347 - New "GETINFO bw-event-cache" to get information about recent
15348 bandwidth events. Closes ticket 14128. Useful for controllers to
15349 get recent bandwidth history after the fix for ticket 13988.
15351 o Minor features (geoip):
15352 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
15353 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
15356 o Minor bugfixes (client, automapping):
15357 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
15358 no value follows the option. Fixes bug 14142; bugfix on
15359 0.2.4.7-alpha. Patch by "teor".
15360 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
15361 14195; bugfix on 0.1.0.1-rc.
15363 o Minor bugfixes (compilation):
15364 - Build without warnings with the stock OpenSSL srtp.h header, which
15365 has a duplicate declaration of SSL_get_selected_srtp_profile().
15366 Fixes bug 14220; this is OpenSSL's bug, not ours.
15368 o Minor bugfixes (directory authority):
15369 - Allow directory authorities to fetch more data from one another if
15370 they find themselves missing lots of votes. Previously, they had
15371 been bumping against the 10 MB queued data limit. Fixes bug 14261;
15372 bugfix on 0.1.2.5-alpha.
15373 - Enlarge the buffer to read bwauth generated files to avoid an
15374 issue when parsing the file in dirserv_read_measured_bandwidths().
15375 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
15377 o Minor bugfixes (statistics):
15378 - Increase period over which bandwidth observations are aggregated
15379 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
15381 o Minor bugfixes (preventative security, C safety):
15382 - When reading a hexadecimal, base-32, or base-64 encoded value from
15383 a string, always overwrite the whole output buffer. This prevents
15384 some bugs where we would look at (but fortunately, not reveal)
15385 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
15389 Changes in version 0.2.4.26 - 2015-03-17
15390 Tor 0.2.4.26 includes an updated list of directory authorities. It
15391 also backports a couple of stability and security bugfixes from 0.2.5
15394 o Directory authority changes:
15395 - Remove turtles as a directory authority.
15396 - Add longclaw as a new (v3) directory authority. This implements
15397 ticket 13296. This keeps the directory authority count at 9.
15398 - The directory authority Faravahar has a new IP address. This
15399 closes ticket 14487.
15401 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
15402 - Fix an assertion failure that could occur under high DNS load.
15403 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
15404 diagnosed and fixed by "cypherpunks".
15406 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
15407 - Fix a bug that could lead to a relay crashing with an assertion
15408 failure if a buffer of exactly the wrong layout was passed to
15409 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
15410 0.2.0.10-alpha. Patch from 'cypherpunks'.
15411 - Do not assert if the 'data' pointer on a buffer is advanced to the
15412 very end of the buffer; log a BUG message instead. Only assert if
15413 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
15415 o Minor features (geoip):
15416 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
15417 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
15420 Changes in version 0.2.5.10 - 2014-10-24
15421 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
15423 It adds several new security features, including improved
15424 denial-of-service resistance for relays, new compiler hardening
15425 options, and a system-call sandbox for hardened installations on Linux
15426 (requires seccomp2). The controller protocol has several new features,
15427 resolving IPv6 addresses should work better than before, and relays
15428 should be a little more CPU-efficient. We've added support for more
15429 OpenBSD and FreeBSD transparent proxy types. We've improved the build
15430 system and testing infrastructure to allow unit testing of more parts
15431 of the Tor codebase. Finally, we've addressed several nagging pluggable
15432 transport usability issues, and included numerous other small bugfixes
15433 and features mentioned below.
15435 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
15436 have accumulated many known flaws; everyone should upgrade.
15438 o Major features (security):
15439 - The ntor handshake is now on-by-default, no matter what the
15440 directory authorities recommend. Implements ticket 8561.
15441 - Make the "tor-gencert" tool used by directory authority operators
15442 create 2048-bit signing keys by default (rather than 1024-bit, since
15443 1024-bit is uncomfortably small these days). Addresses ticket 10324.
15444 - Warn about attempts to run hidden services and relays in the same
15445 process: that's probably not a good idea. Closes ticket 12908.
15446 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
15447 today support TLS 1.0 or later, so we can safely turn off support
15448 for this old (and insecure) protocol. Fixes bug 13426.
15450 o Major features (relay security, DoS-resistance):
15451 - When deciding whether we have run out of memory and we need to
15452 close circuits, also consider memory allocated in buffers for
15453 streams attached to each circuit.
15455 This change, which extends an anti-DoS feature introduced in
15456 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
15457 better resist more memory-based DoS attacks than before. Since the
15458 MaxMemInCellQueues option now applies to all queues, it is renamed
15459 to MaxMemInQueues. This feature fixes bug 10169.
15460 - Avoid hash-flooding denial-of-service attacks by using the secure
15461 SipHash-2-4 hash function for our hashtables. Without this
15462 feature, an attacker could degrade performance of a targeted
15463 client or server by flooding their data structures with a large
15464 number of entries to be stored at the same hash table position,
15465 thereby slowing down the Tor instance. With this feature, hash
15466 table positions are derived from a randomized cryptographic key,
15467 and an attacker cannot predict which entries will collide. Closes
15469 - If you don't specify MaxMemInQueues yourself, Tor now tries to
15470 pick a good value based on your total system memory. Previously,
15471 the default was always 8 GB. You can still override the default by
15472 setting MaxMemInQueues yourself. Resolves ticket 11396.
15474 o Major features (bridges and pluggable transports):
15475 - Add support for passing arguments to managed pluggable transport
15476 proxies. Implements ticket 3594.
15477 - Bridges now track GeoIP information and the number of their users
15478 even when pluggable transports are in use, and report usage
15479 statistics in their extra-info descriptors. Resolves tickets 4773
15481 - Don't launch pluggable transport proxies if we don't have any
15482 bridges configured that would use them. Now we can list many
15483 pluggable transports, and Tor will dynamically start one when it
15484 hears a bridge address that needs it. Resolves ticket 5018.
15485 - The bridge directory authority now assigns status flags (Stable,
15486 Guard, etc) to bridges based on thresholds calculated over all
15487 Running bridges. Now bridgedb can finally make use of its features
15488 to e.g. include at least one Stable bridge in its answers. Fixes
15491 o Major features (controller):
15492 - Extend ORCONN controller event to include an "ID" parameter,
15493 and add four new controller event types CONN_BW, CIRC_BW,
15494 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
15495 The new events are emitted in private Tor networks only, with the
15496 goal of being able to better track performance and load during
15497 full-network simulations. Implements proposal 218 and ticket 7359.
15499 o Major features (relay performance):
15500 - Speed up server-side lookups of rendezvous and introduction point
15501 circuits by using hashtables instead of linear searches. These
15502 functions previously accounted between 3 and 7% of CPU usage on
15503 some busy relays. Resolves ticket 9841.
15504 - Avoid wasting CPU when extending a circuit over a channel that is
15505 nearly out of circuit IDs. Previously, we would do a linear scan
15506 over possible circuit IDs before finding one or deciding that we
15507 had exhausted our possibilities. Now, we try at most 64 random
15508 circuit IDs before deciding that we probably won't succeed. Fixes
15509 a possible root cause of ticket 11553.
15511 o Major features (seccomp2 sandbox, Linux only):
15512 - Use the seccomp2 syscall filtering facility on Linux to limit
15513 which system calls Tor can invoke. This is an experimental,
15514 Linux-only feature to provide defense-in-depth against unknown
15515 attacks. To try turning it on, set "Sandbox 1" in your torrc
15516 file. Please be ready to report bugs. We hope to add support
15517 for better sandboxing in the future, including more fine-grained
15518 filters, better division of responsibility, and support for more
15519 platforms. This work has been done by Cristian-Matei Toader for
15520 Google Summer of Code. Resolves tickets 11351 and 11465.
15522 o Major features (testing networks):
15523 - Make testing Tor networks bootstrap better: lower directory fetch
15524 retry schedules and maximum interval without directory requests,
15525 and raise maximum download tries. Implements ticket 6752.
15526 - Add make target 'test-network' to run tests on a Chutney network.
15527 Implements ticket 8530.
15529 o Major features (other):
15530 - On some platforms (currently: recent OSX versions, glibc-based
15531 platforms that support the ELF format, and a few other
15532 Unix-like operating systems), Tor can now dump stack traces
15533 when a crash occurs or an assertion fails. By default, traces
15534 are dumped to stderr (if possible) and to any logs that are
15535 reporting errors. Implements ticket 9299.
15537 o Deprecated versions:
15538 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
15539 attention for some while.
15541 o Major bugfixes (security, directory authorities):
15542 - Directory authorities now include a digest of each relay's
15543 identity key as a part of its microdescriptor.
15545 This is a workaround for bug 11743 (reported by "cypherpunks"),
15546 where Tor clients do not support receiving multiple
15547 microdescriptors with the same SHA256 digest in the same
15548 consensus. When clients receive a consensus like this, they only
15549 use one of the relays. Without this fix, a hostile relay could
15550 selectively disable some client use of target relays by
15551 constructing a router descriptor with a different identity and the
15552 same microdescriptor parameters and getting the authorities to
15553 list it in a microdescriptor consensus. This fix prevents an
15554 attacker from causing a microdescriptor collision, because the
15555 router's identity is not forgeable.
15557 o Major bugfixes (openssl bug workaround):
15558 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
15559 1.0.1j, built with the 'no-ssl3' configuration option. Fixes
15560 bug 13471. This is a workaround for an OpenSSL bug.
15562 o Major bugfixes (client):
15563 - Perform circuit cleanup operations even when circuit
15564 construction operations are disabled (because the network is
15565 disabled, or because there isn't enough directory information).
15566 Previously, when we were not building predictive circuits, we
15567 were not closing expired circuits either. Fixes bug 8387; bugfix on
15568 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
15569 became more strict about when we have "enough directory information
15570 to build circuits".
15572 o Major bugfixes (client, pluggable transports):
15573 - When managing pluggable transports, use OS notification facilities
15574 to learn if they have crashed, and don't attempt to kill any
15575 process that has already exited. Fixes bug 8746; bugfix
15578 o Major bugfixes (relay denial of service):
15579 - Instead of writing destroy cells directly to outgoing connection
15580 buffers, queue them and intersperse them with other outgoing cells.
15581 This can prevent a set of resource starvation conditions where too
15582 many pending destroy cells prevent data cells from actually getting
15583 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
15584 bugfix on 0.2.0.1-alpha.
15586 o Major bugfixes (relay):
15587 - Avoid queuing or sending destroy cells for circuit ID zero when we
15588 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
15589 Found and fixed by "cypherpunks".
15590 - Fix ORPort reachability detection on relays running behind a
15591 proxy, by correctly updating the "local" mark on the controlling
15592 channel when changing the address of an or_connection_t after the
15593 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
15594 - Use a direct dirport connection when uploading non-anonymous
15595 descriptors to the directory authorities. Previously, relays would
15596 incorrectly use tunnel connections under a fairly wide variety of
15597 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
15598 - When a circuit accidentally has the same circuit ID for its
15599 forward and reverse direction, correctly detect the direction of
15600 cells using that circuit. Previously, this bug made roughly one
15601 circuit in a million non-functional. Fixes bug 12195; this is a
15602 bugfix on every version of Tor.
15604 o Minor features (security):
15605 - New --enable-expensive-hardening option to enable security
15606 hardening options that consume nontrivial amounts of CPU and
15607 memory. Right now, this includes AddressSanitizer and UbSan, which
15608 are supported in newer versions of GCC and Clang. Closes ticket
15610 - Authorities now assign the Guard flag to the fastest 25% of the
15611 network (it used to be the fastest 50%). Also raise the consensus
15612 weight that guarantees the Guard flag from 250 to 2000. For the
15613 current network, this results in about 1100 guards, down from 2500.
15614 This step paves the way for moving the number of entry guards
15615 down to 1 (proposal 236) while still providing reasonable expected
15616 performance for most users. Implements ticket 12690.
15618 o Minor features (security, memory management):
15619 - Memory allocation tricks (mempools and buffer freelists) are now
15620 disabled by default. You can turn them back on with
15621 --enable-mempools and --enable-buf-freelists respectively. We're
15622 disabling these features because malloc performance is good enough
15623 on most platforms, and a similar feature in OpenSSL exacerbated
15624 exploitation of the Heartbleed attack. Resolves ticket 11476.
15626 o Minor features (bridge client):
15627 - Report a more useful failure message when we can't connect to a
15628 bridge because we don't have the right pluggable transport
15629 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
15631 o Minor features (bridge):
15632 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
15633 cookie file for the ExtORPort g+r by default.
15635 o Minor features (bridges, pluggable transports):
15636 - Bridges now write the SHA1 digest of their identity key
15637 fingerprint (that is, a hash of a hash of their public key) to
15638 notice-level logs, and to a new hashed-fingerprint file. This
15639 information will help bridge operators look up their bridge in
15640 Globe and similar tools. Resolves ticket 10884.
15641 - Improve the message that Tor displays when running as a bridge
15642 using pluggable transports without an Extended ORPort listener.
15643 Also, log the message in the log file too. Resolves ticket 11043.
15644 - Add threshold cutoffs to the networkstatus document created by
15645 the Bridge Authority. Fixes bug 1117.
15646 - On Windows, spawn background processes using the CREATE_NO_WINDOW
15647 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
15648 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
15649 Vidalia set this option for us.) Implements ticket 10297.
15651 o Minor features (build):
15652 - The configure script has a --disable-seccomp option to turn off
15653 support for libseccomp on systems that have it, in case it (or
15654 Tor's use of it) is broken. Resolves ticket 11628.
15655 - Assume that a user using ./configure --host wants to cross-compile,
15656 and give an error if we cannot find a properly named
15657 tool-chain. Add a --disable-tool-name-check option to proceed
15658 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
15659 - If we run ./configure and the compiler recognizes -fstack-protector
15660 but the linker rejects it, warn the user about a potentially missing
15661 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
15662 - Add support for `--library-versions` flag. Implements ticket 6384.
15663 - Return the "unexpected sendme" warnings to a warn severity, but make
15664 them rate limited, to help diagnose ticket 8093.
15665 - Detect a missing asciidoc, and warn the user about it, during
15666 configure rather than at build time. Fixes issue 6506. Patch from
15669 o Minor features (client):
15670 - Add a new option, PredictedPortsRelevanceTime, to control how long
15671 after having received a request to connect to a given port Tor
15672 will try to keep circuits ready in anticipation of future requests
15673 for that port. Patch from "unixninja92"; implements ticket 9176.
15675 o Minor features (config options and command line):
15676 - Add an --allow-missing-torrc commandline option that tells Tor to
15677 run even if the configuration file specified by -f is not available.
15678 Implements ticket 10060.
15679 - Add support for the TPROXY transparent proxying facility on Linux.
15680 See documentation for the new TransProxyType option for more
15681 details. Implementation by "thomo". Closes ticket 10582.
15683 o Minor features (config options):
15684 - Config (torrc) lines now handle fingerprints which are missing
15685 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
15686 - Support a --dump-config option to print some or all of the
15687 configured options. Mainly useful for debugging the command-line
15688 option parsing code. Helps resolve ticket 4647.
15689 - Raise awareness of safer logging: notify user of potentially
15690 unsafe config options, like logging more verbosely than severity
15691 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
15692 - Add a new configuration option TestingV3AuthVotingStartOffset
15693 that bootstraps a network faster by changing the timing for
15694 consensus votes. Addresses ticket 8532.
15695 - Add a new torrc option "ServerTransportOptions" that allows
15696 bridge operators to pass configuration parameters to their
15697 pluggable transports. Resolves ticket 8929.
15698 - The config (torrc) file now accepts bandwidth and space limits in
15699 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
15700 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
15703 o Minor features (controller):
15704 - Make the entire exit policy available from the control port via
15705 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
15707 - Because of the fix for ticket 11396, the real limit for memory
15708 usage may no longer match the configured MaxMemInQueues value. The
15709 real limit is now exposed via GETINFO limits/max-mem-in-queues.
15710 - Add a new "HS_DESC" controller event that reports activities
15711 related to hidden service descriptors. Resolves ticket 8510.
15712 - New "DROPGUARDS" controller command to forget all current entry
15713 guards. Not recommended for ordinary use, since replacing guards
15714 too frequently makes several attacks easier. Resolves ticket 9934;
15716 - Implement the TRANSPORT_LAUNCHED control port event that
15717 notifies controllers about new launched pluggable
15718 transports. Resolves ticket 5609.
15720 o Minor features (diagnostic):
15721 - When logging a warning because of bug 7164, additionally check the
15722 hash table for consistency (as proposed on ticket 11737). This may
15723 help diagnose bug 7164.
15724 - When we log a heartbeat, log how many one-hop circuits we have
15725 that are at least 30 minutes old, and log status information about
15726 a few of them. This is an attempt to track down bug 8387.
15727 - When encountering an unexpected CR while writing text to a file on
15728 Windows, log the name of the file. Should help diagnosing
15730 - Give more specific warnings when a client notices that an onion
15731 handshake has failed. Fixes ticket 9635.
15732 - Add significant new logging code to attempt to diagnose bug 12184,
15733 where relays seem to run out of available circuit IDs.
15734 - Improve the diagnostic log message for bug 8387 even further to
15735 try to improve our odds of figuring out why one-hop directory
15736 circuits sometimes do not get closed.
15737 - Add more log messages to diagnose bug 7164, which causes
15738 intermittent "microdesc_free() called but md was still referenced"
15739 warnings. We now include more information, to figure out why we
15740 might be cleaning a microdescriptor for being too old if it's
15741 still referenced by a live node_t object.
15742 - Log current accounting state (bytes sent and received + remaining
15743 time for the current accounting period) in the relay's heartbeat
15744 message. Implements ticket 5526; patch from Peter Retzlaff.
15746 o Minor features (geoip):
15747 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
15750 o Minor features (interface):
15751 - Generate a warning if any ports are listed in the SocksPolicy,
15752 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
15753 AuthDirBadExit options. (These options only support address
15754 ranges.) Fixes part of ticket 11108.
15756 o Minor features (kernel API usage):
15757 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
15758 sockets in a single system call. Implements ticket 5129.
15760 o Minor features (log messages):
15761 - When ServerTransportPlugin is set on a bridge, Tor can write more
15762 useful statistics about bridge use in its extrainfo descriptors,
15763 but only if the Extended ORPort ("ExtORPort") is set too. Add a
15764 log message to inform the user in this case. Resolves ticket 9651.
15765 - When receiving a new controller connection, log the origin address.
15766 Resolves ticket 9698; patch from "sigpipe".
15767 - When logging OpenSSL engine status at startup, log the status of
15768 more engines. Fixes ticket 10043; patch from Joshua Datko.
15770 o Minor features (log verbosity):
15771 - Demote the message that we give when a flushing connection times
15772 out for too long from NOTICE to INFO. It was usually meaningless.
15773 Resolves ticket 5286.
15774 - Don't log so many notice-level bootstrapping messages at startup
15775 about downloading descriptors. Previously, we'd log a notice
15776 whenever we learned about more routers. Now, we only log a notice
15777 at every 5% of progress. Fixes bug 9963.
15778 - Warn less verbosely when receiving a malformed
15779 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
15781 o Minor features (performance):
15782 - If we're using the pure-C 32-bit curve25519_donna implementation
15783 of curve25519, build it with the -fomit-frame-pointer option to
15784 make it go faster on register-starved hosts. This improves our
15785 handshake performance by about 6% on i386 hosts without nacl.
15786 Closes ticket 8109.
15788 o Minor features (relay):
15789 - If a circuit timed out for at least 3 minutes, check if we have a
15790 new external IP address, and publish a new descriptor with the new
15791 IP address if it changed. Resolves ticket 2454.
15793 o Minor features (testing):
15794 - If Python is installed, "make check" now runs extra tests beyond
15795 the unit test scripts.
15796 - When bootstrapping a test network, sometimes very few relays get
15797 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
15798 specify a set of relays which should be voted Guard regardless of
15799 their uptime or bandwidth. Addresses ticket 9206.
15801 o Minor features (transparent proxy, *BSD):
15802 - Support FreeBSD's ipfw firewall interface for TransPort ports on
15803 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
15804 10267; patch from "yurivict".
15805 - Support OpenBSD's divert-to rules with the pf firewall for
15806 transparent proxy ports. To enable it, set "TransProxyType
15807 pf-divert". This allows Tor to run a TransPort transparent proxy
15808 port on OpenBSD 4.4 or later without root privileges. See the
15809 pf.conf(5) manual page for information on configuring pf to use
15810 divert-to rules. Closes ticket 10896; patch from Dana Koch.
15812 o Minor bugfixes (bridge client):
15813 - Stop accepting bridge lines containing hostnames. Doing so would
15814 cause clients to perform DNS requests on the hostnames, which was
15815 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
15817 o Minor bugfixes (bridges):
15818 - Avoid potential crashes or bad behavior when launching a
15819 server-side managed proxy with ORPort or ExtORPort temporarily
15820 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
15821 - Fix a bug where the first connection works to a bridge that uses a
15822 pluggable transport with client-side parameters, but we don't send
15823 the client-side parameters on subsequent connections. (We don't
15824 use any pluggable transports with client-side parameters yet,
15825 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
15826 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
15828 o Minor bugfixes (build, auxiliary programs):
15829 - Stop preprocessing the "torify" script with autoconf, since
15830 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
15832 - The tor-fw-helper program now follows the standard convention and
15833 exits with status code "0" on success. Fixes bug 9030; bugfix on
15834 0.2.3.1-alpha. Patch by Arlo Breault.
15835 - Corrected ./configure advice for what openssl dev package you should
15836 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
15838 o Minor bugfixes (client):
15839 - Avoid "Tried to open a socket with DisableNetwork set" warnings
15840 when starting a client with bridges configured and DisableNetwork
15841 set. (Tor launcher starts Tor with DisableNetwork set the first
15842 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
15843 - Improve the log message when we can't connect to a hidden service
15844 because all of the hidden service directory nodes hosting its
15845 descriptor are excluded. Improves on our fix for bug 10722, which
15846 was a bugfix on 0.2.0.10-alpha.
15847 - Raise a control port warning when we fail to connect to all of
15848 our bridges. Previously, we didn't inform the controller, and
15849 the bootstrap process would stall. Fixes bug 11069; bugfix on
15851 - Exit immediately when a process-owning controller exits.
15852 Previously, tor relays would wait for a little while after their
15853 controller exited, as if they had gotten an INT signal -- but this
15854 was problematic, since there was no feedback for the user. To do a
15855 clean shutdown, controllers should send an INT signal and give Tor
15856 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
15857 - Stop attempting to connect to bridges before our pluggable
15858 transports are configured (harmless but resulted in some erroneous
15859 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
15860 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
15861 generating incorrect SOCKS5 responses, and confusing client
15862 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
15864 o Minor bugfixes (client, DNSPort):
15865 - When using DNSPort, try to respond to AAAA requests with AAAA
15866 answers. Previously, we hadn't looked at the request type when
15867 deciding which answer type to prefer. Fixes bug 10468; bugfix on
15869 - When receiving a DNS query for an unsupported record type, reply
15870 with no answer rather than with a NOTIMPL error. This behavior
15871 isn't correct either, but it will break fewer client programs, we
15872 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
15875 o Minor bugfixes (client, logging during bootstrap):
15876 - Only report the first fatal bootstrap error on a given OR
15877 connection. This stops us from telling the controller bogus error
15878 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
15879 - Avoid generating spurious warnings when starting with
15880 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
15883 o Minor bugfixes (closing OR connections):
15884 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
15885 check if it's an or_connection_t and correctly call
15886 connection_or_close_for_error() rather than
15887 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
15889 - When closing all connections on setting DisableNetwork to 1, use
15890 connection_or_close_normally() rather than closing OR connections
15891 out from under the channel layer. Fixes bug 11306; bugfix on
15894 o Minor bugfixes (code correctness):
15895 - Previously we used two temporary files when writing descriptors to
15896 disk; now we only use one. Fixes bug 1376.
15897 - Remove an erroneous (but impossible and thus harmless) pointer
15898 comparison that would have allowed compilers to skip a bounds
15899 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
15900 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
15901 - Fix an always-true assertion in pluggable transports code so it
15902 actually checks what it was trying to check. Fixes bug 10046;
15903 bugfix on 0.2.3.9-alpha. Found by "dcb".
15905 o Minor bugfixes (command line):
15906 - Use a single command-line parser for parsing torrc options on the
15907 command line and for finding special command-line options to avoid
15908 inconsistent behavior for torrc option arguments that have the same
15909 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
15911 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
15912 9573; bugfix on 0.0.9pre5.
15914 o Minor bugfixes (compilation):
15915 - Compile correctly with builds and forks of OpenSSL (such as
15916 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
15917 0.2.1.1-alpha. Patch from "dhill".
15918 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
15919 turned off (that is, without support for v2 link handshakes). Fixes
15920 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
15921 - In routerlist_assert_ok(), don't take the address of a
15922 routerinfo's cache_info member unless that routerinfo is non-NULL.
15923 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
15924 - Fix a large number of false positive warnings from the clang
15925 analyzer static analysis tool. This should make real warnings
15926 easier for clang analyzer to find. Patch from "teor". Closes
15928 - Resolve GCC complaints on OpenBSD about discarding constness in
15929 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
15930 on 0.1.1.23. Patch from Dana Koch.
15931 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
15932 treatment of long and time_t as comparable types. Fixes part of
15933 bug 11633. Patch from Dana Koch.
15934 - When deciding whether to build the 64-bit curve25519
15935 implementation, detect platforms where we can compile 128-bit
15936 arithmetic but cannot link it. Fixes bug 11729; bugfix on
15937 0.2.4.8-alpha. Patch from "conradev".
15938 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
15939 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
15940 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
15942 - Build and run correctly on systems like OpenBSD-current that have
15943 patched OpenSSL to remove get_cipher_by_char and/or its
15944 implementations. Fixes issue 13325.
15946 o Minor bugfixes (controller and command-line):
15947 - If changing a config option via "setconf" fails in a recoverable
15948 way, we used to nonetheless write our new control ports to the
15949 file described by the "ControlPortWriteToFile" option. Now we only
15950 write out that file if we successfully switch to the new config
15951 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
15953 o Minor bugfixes (directory server):
15954 - No longer accept malformed http headers when parsing urls from
15955 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
15956 bugfix on 0.0.6pre1.
15957 - When sending a compressed set of descriptors or microdescriptors,
15958 make sure to finalize the zlib stream. Previously, we would write
15959 all the compressed data, but if the last descriptor we wanted to
15960 send was missing or too old, we would not mark the stream as
15961 finished. This caused problems for decompression tools. Fixes bug
15962 11648; bugfix on 0.1.1.23.
15964 o Minor bugfixes (hidden service):
15965 - Only retry attempts to connect to a chosen rendezvous point 8
15966 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
15968 o Minor bugfixes (interface):
15969 - Reject relative control socket paths and emit a warning. Previously,
15970 single-component control socket paths would be rejected, but Tor
15971 would not log why it could not validate the config. Fixes bug 9258;
15972 bugfix on 0.2.3.16-alpha.
15974 o Minor bugfixes (log messages):
15975 - Fix a bug where clients using bridges would report themselves
15976 as 50% bootstrapped even without a live consensus document.
15977 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
15978 - Suppress a warning where, if there's only one directory authority
15979 in the network, we would complain that votes and signatures cannot
15980 be uploaded to other directory authorities. Fixes bug 10842;
15981 bugfix on 0.2.2.26-beta.
15982 - Report bootstrapping progress correctly when we're downloading
15983 microdescriptors. We had updated our "do we have enough microdescs
15984 to begin building circuits?" logic most recently in 0.2.4.10-alpha
15985 (see bug 5956), but we left the bootstrap status event logic at
15986 "how far through getting 1/4 of them are we?" Fixes bug 9958;
15987 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
15989 o Minor bugfixes (logging):
15990 - Downgrade "Unexpected onionskin length after decryption" warning
15991 to a protocol-warn, since there's nothing relay operators can do
15992 about a client that sends them a malformed create cell. Resolves
15993 bug 12996; bugfix on 0.0.6rc1.
15994 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
15995 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
15996 - When logging information about an EXTEND2 or EXTENDED2 cell, log
15997 their names correctly. Fixes part of bug 12700; bugfix
15999 - When logging information about a relay cell whose command we don't
16000 recognize, log its command as an integer. Fixes part of bug 12700;
16001 bugfix on 0.2.1.10-alpha.
16002 - Escape all strings from the directory connection before logging
16003 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
16004 - Squelch a spurious LD_BUG message "No origin circuit for
16005 successful SOCKS stream" in certain hidden service failure cases;
16007 - Downgrade the severity of the 'unexpected sendme cell from client'
16008 from 'warn' to 'protocol warning'. Closes ticket 8093.
16010 o Minor bugfixes (misc code correctness):
16011 - In munge_extrainfo_into_routerinfo(), check the return value of
16012 memchr(). This would have been a serious issue if we ever passed
16013 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
16015 - On the chance that somebody manages to build Tor on a
16016 platform where time_t is unsigned, correct the way that
16017 microdesc_add_to_cache() handles negative time arguments.
16018 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
16019 - Fix various instances of undefined behavior in channeltls.c,
16020 tor_memmem(), and eventdns.c that would cause us to construct
16021 pointers to memory outside an allocated object. (These invalid
16022 pointers were not accessed, but C does not even allow them to
16023 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
16024 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
16025 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
16026 fix some miscellaneous errors in our tests and codebase. Fixes bug
16027 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
16028 - Always check return values for unlink, munmap, UnmapViewOfFile;
16029 check strftime return values more often. In some cases all we can
16030 do is report a warning, but this may help prevent deeper bugs from
16031 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
16033 - Fix numerous warnings from the clang "scan-build" static analyzer.
16034 Some of these are programming style issues; some of them are false
16035 positives that indicated awkward code; some are undefined behavior
16036 cases related to constructing (but not using) invalid pointers;
16037 some are assumptions about API behavior; some are (harmlessly)
16038 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
16039 correct; and one or two are genuine bugs that weren't reachable
16040 from the rest of the program. Fixes bug 8793; bugfixes on many,
16043 o Minor bugfixes (node selection):
16044 - If ExcludeNodes is set, consider non-excluded hidden service
16045 directory servers before excluded ones. Do not consider excluded
16046 hidden service directory servers at all if StrictNodes is
16047 set. (Previously, we would sometimes decide to connect to those
16048 servers, and then realize before we initiated a connection that
16049 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
16050 Reported by "mr-4".
16051 - If we set the ExitNodes option but it doesn't include any nodes
16052 that have the Exit flag, we would choose not to bootstrap. Now we
16053 bootstrap so long as ExitNodes includes nodes which can exit to
16054 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
16056 o Minor bugfixes (performance):
16057 - Avoid a bug where every successful connection made us recompute
16058 the flag telling us whether we have sufficient information to
16059 build circuits. Previously, we would forget our cached value
16060 whenever we successfully opened a channel (or marked a router as
16061 running or not running for any other reason), regardless of
16062 whether we had previously believed the router to be running. This
16063 forced us to run an expensive update operation far too often.
16064 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
16065 - Avoid using tor_memeq() for checking relay cell integrity. This
16066 removes a possible performance bottleneck. Fixes part of bug
16067 12169; bugfix on 0.2.1.31.
16069 o Minor bugfixes (platform-specific):
16070 - When dumping a malformed directory object to disk, save it in
16071 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
16073 - Don't report failures from make_socket_reuseable() on incoming
16074 sockets on OSX: this can happen when incoming connections close
16075 early. Fixes bug 10081.
16077 o Minor bugfixes (pluggable transports):
16078 - Avoid another 60-second delay when starting Tor in a pluggable-
16079 transport-using configuration when we already have cached
16080 descriptors for our bridges. Fixes bug 11965; bugfix
16083 o Minor bugfixes (protocol correctness):
16084 - When receiving a VERSIONS cell with an odd number of bytes, close
16085 the connection immediately since the cell is malformed. Fixes bug
16086 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
16089 o Minor bugfixes (relay, other):
16090 - We now drop CREATE cells for already-existent circuit IDs and for
16091 zero-valued circuit IDs, regardless of other factors that might
16092 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
16094 - When rejecting DATA cells for stream_id zero, still count them
16095 against the circuit's deliver window so that we don't fail to send
16096 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
16098 o Minor bugfixes (relay, threading):
16099 - Check return code on spawn_func() in cpuworker code, so that we
16100 don't think we've spawned a nonworking cpuworker and write junk to
16101 it forever. Fix related to bug 4345; bugfix on all released Tor
16102 versions. Found by "skruffy".
16103 - Use a pthread_attr to make sure that spawn_func() cannot return an
16104 error while at the same time launching a thread. Fix related to
16105 bug 4345; bugfix on all released Tor versions. Reported
16108 o Minor bugfixes (relays and bridges):
16109 - Avoid crashing on a malformed resolv.conf file when running a
16110 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
16111 - Non-exit relays no longer launch mock DNS requests to check for
16112 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
16113 non-exit relays stopped servicing DNS requests. Fixes bug 965;
16114 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
16115 - Bridges now report complete directory request statistics. Related
16116 to bug 5824; bugfix on 0.2.2.1-alpha.
16117 - Bridges now never collect statistics that were designed for
16118 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
16120 o Minor bugfixes (testing):
16121 - Fix all valgrind warnings produced by the unit tests. There were
16122 over a thousand memory leak warnings previously, mostly produced
16123 by forgetting to free things in the unit test code. Fixes bug
16124 11618, bugfixes on many versions of Tor.
16126 o Minor bugfixes (tor-fw-helper):
16127 - Give a correct log message when tor-fw-helper fails to launch.
16128 (Previously, we would say something like "tor-fw-helper sent us a
16129 string we could not parse".) Fixes bug 9781; bugfix
16132 o Minor bugfixes (trivial memory leaks):
16133 - Fix a small memory leak when signing a directory object. Fixes bug
16134 11275; bugfix on 0.2.4.13-alpha.
16135 - Resolve some memory leaks found by coverity in the unit tests, on
16136 exit in tor-gencert, and on a failure to compute digests for our
16137 own keys when generating a v3 networkstatus vote. These leaks
16138 should never have affected anyone in practice.
16140 o Code simplification and refactoring:
16141 - Remove some old fallback code designed to keep Tor clients working
16142 in a network with only two working relays. Elsewhere in the code we
16143 have long since stopped supporting such networks, so there wasn't
16144 much point in keeping it around. Addresses ticket 9926.
16145 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
16146 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
16147 - Extract the common duplicated code for creating a subdirectory
16148 of the data directory and writing to a file in it. Fixes ticket
16149 4282; patch from Peter Retzlaff.
16150 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
16151 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
16152 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
16153 - Add a set of accessor functions for the circuit timeout data
16154 structure. Fixes ticket 6153; patch from "piet".
16155 - Clean up exit paths from connection_listener_new(). Closes ticket
16156 8789. Patch from Arlo Breault.
16157 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
16158 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
16159 - Use a doubly-linked list to implement the global circuit list.
16160 Resolves ticket 9108. Patch from Marek Majkowski.
16161 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
16162 - Remove constants and tests for PKCS1 padding; it's insecure and
16163 shouldn't be used for anything new. Fixes bug 8792; patch
16165 - Remove instances of strcpy() from the unit tests. They weren't
16166 hurting anything, since they were only in the unit tests, but it's
16167 embarrassing to have strcpy() in the code at all, and some analysis
16168 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
16169 0.2.3.8-alpha. Patch from Arlo Breault.
16170 - Remove is_internal_IP() function. Resolves ticket 4645.
16171 - Remove unused function circuit_dump_by_chan from circuitlist.c.
16172 Closes issue 9107; patch from "marek".
16173 - Change our use of the ENUM_BF macro to avoid declarations that
16175 - Get rid of router->address, since in all cases it was just the
16176 string representation of router->addr. Resolves ticket 5528.
16179 - Adjust the URLs in the README to refer to the new locations of
16180 several documents on the website. Fixes bug 12830. Patch from
16182 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
16184 - Update manpage to describe some of the files you can expect to
16185 find in Tor's DataDirectory. Addresses ticket 9839.
16186 - Clean up several option names in the manpage to match their real
16187 names, add the missing documentation for a couple of testing and
16188 directory authority options, remove the documentation for a
16189 V2-directory fetching option that no longer exists. Resolves
16191 - Correct the documentation so that it lists the correct directory
16192 for the stats files. (They are in a subdirectory called "stats",
16194 - In the manpage, move more authority-only options into the
16195 directory authority section so that operators of regular directory
16196 caches don't get confused.
16197 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
16198 11061; bugfix on 0.2.4.7-alpha.
16199 - Resolve warnings from Doxygen.
16200 - Document in the manpage that "KBytes" may also be written as
16201 "kilobytes" or "KB", that "Kbits" may also be written as
16202 "kilobits", and so forth. Closes ticket 9222.
16203 - Document that the ClientOnly config option overrides ORPort.
16204 Our old explanation made ClientOnly sound as though it did
16205 nothing at all. Resolves bug 9059.
16206 - Explain that SocksPolicy, DirPolicy, and similar options don't
16207 take port arguments. Fixes the other part of ticket 11108.
16208 - Fix a comment about the rend_server_descriptor_t.protocols field
16209 to more accurately describe its range. Also, make that field
16210 unsigned, to more accurately reflect its usage. Fixes bug 9099;
16211 bugfix on 0.2.1.5-alpha.
16212 - Fix the manpage's description of HiddenServiceAuthorizeClient:
16213 the maximum client name length is 16, not 19. Fixes bug 11118;
16214 bugfix on 0.2.1.6-alpha.
16217 - The contrib directory has been sorted and tidied. Before, it was
16218 an unsorted dumping ground for useful and not-so-useful things.
16219 Now, it is divided based on functionality, and the items which
16220 seemed to be nonfunctional or useless have been removed. Resolves
16221 ticket 8966; based on patches from "rl1987".
16223 o Removed code and features:
16224 - Clients now reject any directory authority certificates lacking
16225 a dir-key-crosscert element. These have been included since
16226 0.2.1.9-alpha, so there's no real reason for them to be optional
16227 any longer. Completes proposal 157. Resolves ticket 10162.
16228 - Remove all code that existed to support the v2 directory system,
16229 since there are no longer any v2 directory authorities. Resolves
16231 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
16232 options, which were used for designating authorities as "Hidden
16233 service authorities". There has been no use of hidden service
16234 authorities since 0.2.2.1-alpha, when we stopped uploading or
16235 downloading v0 hidden service descriptors. Fixes bug 10881; also
16236 part of a fix for bug 10841.
16237 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
16238 and MTBF calculations, but that nobody was using. Fixes bug 11742.
16239 - The TunnelDirConns and PreferTunnelledDirConns options no longer
16240 exist; tunneled directory connections have been available since
16241 0.1.2.5-alpha, and turning them off is not a good idea. This is a
16242 brute-force fix for 10849, where "TunnelDirConns 0" would break
16244 - Remove all code for the long unused v1 directory protocol.
16245 Resolves ticket 11070.
16246 - Remove all remaining code related to version-0 hidden service
16247 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
16248 the rest of bug 10841.
16249 - Remove migration code from when we renamed the "cached-routers"
16250 file to "cached-descriptors" back in 0.2.0.8-alpha. This
16251 incidentally resolves ticket 6502 by cleaning up the related code
16252 a bit. Patch from Akshay Hebbar.
16254 o Test infrastructure:
16255 - Tor now builds each source file in two modes: a mode that avoids
16256 exposing identifiers needlessly, and another mode that exposes
16257 more identifiers for testing. This lets the compiler do better at
16258 optimizing the production code, while enabling us to take more
16259 radical measures to let the unit tests test things.
16260 - The production builds no longer include functions used only in
16261 the unit tests; all functions exposed from a module only for
16262 unit-testing are now static in production builds.
16263 - Add an --enable-coverage configuration option to make the unit
16264 tests (and a new src/or/tor-cov target) to build with gcov test
16266 - Update to the latest version of tinytest.
16267 - Improve the tinytest implementation of string operation tests so
16268 that comparisons with NULL strings no longer crash the tests; they
16269 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
16270 - New macros in test.h to simplify writing mock-functions for unit
16271 tests. Part of ticket 11507. Patch from Dana Koch.
16272 - We now have rudimentary function mocking support that our unit
16273 tests can use to test functions in isolation. Function mocking
16274 lets the tests temporarily replace a function's dependencies with
16275 stub functions, so that the tests can check the function without
16276 invoking the other functions it calls.
16279 - Complete tests for the status.c module. Resolves ticket 11507.
16280 Patch from Dana Koch.
16281 - Add more unit tests for the <circid,channel>->circuit map, and
16282 the destroy-cell-tracking code to fix bug 7912.
16283 - Unit tests for failing cases of the TAP onion handshake.
16284 - More unit tests for address-manipulation functions.
16286 o Distribution (systemd):
16287 - Include a tor.service file in contrib/dist for use with systemd.
16288 Some distributions will be able to use this file unmodified;
16289 others will need to tweak it, or write their own. Patch from Jamie
16290 Nguyen; resolves ticket 8368.
16291 - Verify configuration file via ExecStartPre in the systemd unit
16292 file. Patch from intrigeri; resolves ticket 12730.
16293 - Explicitly disable RunAsDaemon in the systemd unit file. Our
16294 current systemd unit uses "Type = simple", so systemd does not
16295 expect tor to fork. If the user has "RunAsDaemon 1" in their
16296 torrc, then things won't work as expected. This is e.g. the case
16297 on Debian (and derivatives), since there we pass "--defaults-torrc
16298 /usr/share/tor/tor-service-defaults-torrc" (that contains
16299 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
16303 Changes in version 0.2.4.25 - 2014-10-20
16304 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
16305 (even though POODLE does not affect Tor). It also works around a crash
16306 bug caused by some operating systems' response to the "POODLE" attack
16307 (which does affect Tor).
16309 o Major security fixes (also in 0.2.5.9-rc):
16310 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
16311 today support TLS 1.0 or later, so we can safely turn off support
16312 for this old (and insecure) protocol. Fixes bug 13426.
16314 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
16315 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
16316 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
16317 13471. This is a workaround for an OpenSSL bug.
16320 Changes in version 0.2.4.24 - 2014-09-22
16321 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
16322 connecting to hidden services, and it updates the location of one of
16323 the directory authorities.
16326 - Clients now send the correct address for their chosen rendezvous
16327 point when trying to access a hidden service. They used to send
16328 the wrong address, which would still work some of the time because
16329 they also sent the identity digest of the rendezvous point, and if
16330 the hidden service happened to try connecting to the rendezvous
16331 point from a relay that already had a connection open to it,
16332 the relay would reuse that connection. Now connections to hidden
16333 services should be more robust and faster. Also, this bug meant
16334 that clients were leaking to the hidden service whether they were
16335 on a little-endian (common) or big-endian (rare) system, which for
16336 some users might have reduced their anonymity. Fixes bug 13151;
16337 bugfix on 0.2.1.5-alpha.
16339 o Directory authority changes:
16340 - Change IP address for gabelmoo (v3 directory authority).
16342 o Minor features (geoip):
16343 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
16347 Changes in version 0.2.4.23 - 2014-07-28
16348 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
16349 guard rotation, and also backports several important fixes from the
16350 Tor 0.2.5 alpha release series.
16353 - Clients now look at the "usecreatefast" consensus parameter to
16354 decide whether to use CREATE_FAST or CREATE cells for the first hop
16355 of their circuit. This approach can improve security on connections
16356 where Tor's circuit handshake is stronger than the available TLS
16357 connection security levels, but the tradeoff is more computational
16358 load on guard relays. Implements proposal 221. Resolves ticket 9386.
16359 - Make the number of entry guards configurable via a new
16360 NumEntryGuards consensus parameter, and the number of directory
16361 guards configurable via a new NumDirectoryGuards consensus
16362 parameter. Implements ticket 12688.
16365 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
16366 implementation that caused incorrect results on 32-bit
16367 implementations when certain malformed inputs were used along with
16368 a small class of private ntor keys. This bug does not currently
16369 appear to allow an attacker to learn private keys or impersonate a
16370 Tor server, but it could provide a means to distinguish 32-bit Tor
16371 implementations from 64-bit Tor implementations. Fixes bug 12694;
16372 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
16376 - Warn and drop the circuit if we receive an inbound 'relay early'
16377 cell. Those used to be normal to receive on hidden service circuits
16378 due to bug 1038, but the buggy Tor versions are long gone from
16379 the network so we can afford to resume watching for them. Resolves
16380 the rest of bug 1038; bugfix on 0.2.1.19.
16381 - Correct a confusing error message when trying to extend a circuit
16382 via the control protocol but we don't know a descriptor or
16383 microdescriptor for one of the specified relays. Fixes bug 12718;
16384 bugfix on 0.2.3.1-alpha.
16385 - Avoid an illegal read from stack when initializing the TLS
16386 module using a version of OpenSSL without all of the ciphers
16387 used by the v2 link handshake. Fixes bug 12227; bugfix on
16388 0.2.4.8-alpha. Found by "starlight".
16391 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
16395 Changes in version 0.2.4.22 - 2014-05-16
16396 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
16397 alpha release series. These include blocking all authority signing
16398 keys that may have been affected by the OpenSSL "heartbleed" bug,
16399 choosing a far more secure set of TLS ciphersuites by default, closing
16400 a couple of memory leaks that could be used to run a target relay out
16401 of RAM, and several others.
16403 o Major features (security, backport from 0.2.5.4-alpha):
16404 - Block authority signing keys that were used on authorities
16405 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
16406 don't have any evidence that these keys _were_ compromised; we're
16407 doing this to be prudent.) Resolves ticket 11464.
16409 o Major bugfixes (security, OOM):
16410 - Fix a memory leak that could occur if a microdescriptor parse
16411 fails during the tokenizing step. This bug could enable a memory
16412 exhaustion attack by directory servers. Fixes bug 11649; bugfix
16415 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
16416 - The relay ciphersuite list is now generated automatically based on
16417 uniform criteria, and includes all OpenSSL ciphersuites with
16418 acceptable strength and forward secrecy. Previously, we had left
16419 some perfectly fine ciphersuites unsupported due to omission or
16420 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
16421 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
16422 - Relays now trust themselves to have a better view than clients of
16423 which TLS ciphersuites are better than others. (Thanks to bug
16424 11513, the relay list is now well-considered, whereas the client
16425 list has been chosen mainly for anti-fingerprinting purposes.)
16426 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
16427 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
16428 AES128. Resolves ticket 11528.
16429 - Clients now try to advertise the same list of ciphersuites as
16430 Firefox 28. This change enables selection of (fast) GCM
16431 ciphersuites, disables some strange old ciphers, and stops
16432 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
16433 Resolves ticket 11438.
16435 o Minor bugfixes (configuration, security):
16436 - When running a hidden service, do not allow TunneledDirConns 0:
16437 trying to set that option together with a hidden service would
16438 otherwise prevent the hidden service from running, and also make
16439 it publish its descriptors directly over HTTP. Fixes bug 10849;
16440 bugfix on 0.2.1.1-alpha.
16442 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
16443 - Avoid sending a garbage value to the controller when a circuit is
16444 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
16446 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
16447 - Stop leaking memory when we successfully resolve a PTR record.
16448 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
16450 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
16451 - Avoid 60-second delays in the bootstrapping process when Tor is
16452 launching for a second time while using bridges. Fixes bug 9229;
16453 bugfix on 0.2.0.3-alpha.
16455 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
16456 - Give the correct URL in the warning message when trying to run a
16457 relay on an ancient version of Windows. Fixes bug 9393.
16459 o Minor bugfixes (compilation):
16460 - Fix a compilation error when compiling with --disable-curve25519.
16461 Fixes bug 9700; bugfix on 0.2.4.17-rc.
16464 - Downgrade the warning severity for the the "md was still
16465 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
16466 for trying to diagnose this bug, and the current warning in
16467 earlier versions of tor achieves nothing useful. Addresses warning
16470 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
16471 - When we run out of usable circuit IDs on a channel, log only one
16472 warning for the whole channel, and describe how many circuits
16473 there were on the channel. Fixes part of ticket 11553.
16475 o Minor features (security, backport from 0.2.5.4-alpha):
16476 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
16477 leave the default at 8GBytes), to better support Raspberry Pi
16478 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
16480 o Documentation (backport from 0.2.5.4-alpha):
16481 - Correctly document that we search for a system torrc file before
16482 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
16486 Changes in version 0.2.4.21 - 2014-02-28
16487 Tor 0.2.4.21 further improves security against potential adversaries who
16488 find breaking 1024-bit crypto doable, and backports several stability
16489 and robustness patches from the 0.2.5 branch.
16491 o Major features (client security):
16492 - When we choose a path for a 3-hop circuit, make sure it contains
16493 at least one relay that supports the NTor circuit extension
16494 handshake. Otherwise, there is a chance that we're building
16495 a circuit that's worth attacking by an adversary who finds
16496 breaking 1024-bit crypto doable, and that chance changes the game
16497 theory. Implements ticket 9777.
16500 - Do not treat streams that fail with reason
16501 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
16502 since it could also indicate an ENETUNREACH connection error. Fixes
16503 part of bug 10777; bugfix on 0.2.4.8-alpha.
16505 o Code simplification and refactoring:
16506 - Remove data structures which were introduced to implement the
16507 CellStatistics option: they are now redundant with the new timestamp
16508 field in the regular packed_cell_t data structure, which we did
16509 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
16512 - Always clear OpenSSL bignums before freeing them -- even bignums
16513 that don't contain secrets. Resolves ticket 10793. Patch by
16515 - Build without warnings under clang 3.4. (We have some macros that
16516 define static functions only some of which will get used later in
16517 the module. Starting with clang 3.4, these give a warning unless the
16518 unused attribute is set on them.) Resolves ticket 10904.
16519 - Update geoip and geoip6 files to the February 7 2014 Maxmind
16520 GeoLite2 Country database.
16523 - Set the listen() backlog limit to the largest actually supported
16524 on the system, not to the value in a header file. Fixes bug 9716;
16525 bugfix on every released Tor.
16526 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
16527 exit node as a NOROUTE error, not an INTERNAL error, since they
16528 can apparently happen when trying to connect to the wrong sort
16529 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
16530 - Fix build warnings about missing "a2x" comment when building the
16531 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
16532 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
16533 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
16534 not entirely remove it from the connection lists. Fixes bug 9602;
16535 bugfix on 0.2.4.4-alpha.
16536 - Fix a segmentation fault in our benchmark code when running with
16537 Fedora's OpenSSL package, or any other OpenSSL that provides
16538 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
16539 - Turn "circuit handshake stats since last time" log messages into a
16540 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
16542 o Documentation fixes:
16543 - Document that all but one DirPort entry must have the NoAdvertise
16544 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
16547 Changes in version 0.2.4.20 - 2013-12-22
16548 Tor 0.2.4.20 fixes potentially poor random number generation for users
16549 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
16550 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
16551 and 4) have no state file in their DataDirectory (as would happen on
16552 first start). Users who generated relay or hidden service identity
16553 keys in such a situation should discard them and generate new ones.
16555 This release also fixes a logic error that caused Tor clients to build
16556 many more preemptive circuits than they actually need.
16559 - Do not allow OpenSSL engines to replace the PRNG, even when
16560 HardwareAccel is set. The only default builtin PRNG engine uses
16561 the Intel RDRAND instruction to replace the entire PRNG, and
16562 ignores all attempts to seed it with more entropy. That's
16563 cryptographically stupid: the right response to a new alleged
16564 entropy source is never to discard all previously used entropy
16565 sources. Fixes bug 10402; works around behavior introduced in
16566 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
16568 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
16569 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
16570 - Avoid launching spurious extra circuits when a stream is pending.
16571 This fixes a bug where any circuit that _wasn't_ unusable for new
16572 streams would be treated as if it were, causing extra circuits to
16573 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
16576 - Avoid a crash bug when starting with a corrupted microdescriptor
16577 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
16578 - If we fail to dump a previously cached microdescriptor to disk, avoid
16579 freeing duplicate data later on. Fixes bug 10423; bugfix on
16580 0.2.4.13-alpha. Spotted by "bobnomnom".
16583 Changes in version 0.2.4.19 - 2013-12-11
16584 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
16585 (1986-2013). Aaron worked on diverse projects including helping to guide
16586 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
16587 transparency to the U.S government's PACER documents, and contributing
16588 design and development for Tor and Tor2Web. Aaron was one of the latest
16589 martyrs in our collective fight for civil liberties and human rights,
16590 and his death is all the more painful because he was one of us.
16592 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
16593 a new circuit handshake and link encryption that use ECC to provide
16594 better security and efficiency; makes relays better manage circuit
16595 creation requests; uses "directory guards" to reduce client enumeration
16596 risks; makes bridges collect and report statistics about the pluggable
16597 transports they support; cleans up and improves our geoip database;
16598 gets much closer to IPv6 support for clients, bridges, and relays; makes
16599 directory authorities use measured bandwidths rather than advertised
16600 ones when computing flags and thresholds; disables client-side DNS
16601 caching to reduce tracking risks; and fixes a big bug in bridge
16602 reachability testing. This release introduces two new design
16603 abstractions in the code: a new "channel" abstraction between circuits
16604 and or_connections to allow for implementing alternate relay-to-relay
16605 transports, and a new "circuitmux" abstraction storing the queue of
16606 circuits for a channel. The release also includes many stability,
16607 security, and privacy fixes.
16609 o Major features (new circuit handshake):
16610 - Tor now supports a new circuit extension handshake designed by Ian
16611 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
16612 circuit extension handshake, later called "TAP", was a bit slow
16613 (especially on the relay side), had a fragile security proof, and
16614 used weaker keys than we'd now prefer. The new circuit handshake
16615 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
16616 function, making it significantly more secure than the older
16617 handshake, and significantly faster. Tor can use one of two built-in
16618 pure-C curve25519-donna implementations by Adam Langley, or it
16619 can link against the "nacl" library for a tuned version if present.
16621 The built-in version is very fast for 64-bit systems when building
16622 with GCC. The built-in 32-bit version is still faster than the
16623 old TAP protocol, but using libnacl is better on most such hosts.
16625 Implements proposal 216; closes ticket 7202.
16627 o Major features (better link encryption):
16628 - Relays can now enable the ECDHE TLS ciphersuites when available
16629 and appropriate. These ciphersuites let us negotiate forward-secure
16630 TLS secret keys more safely and more efficiently than with our
16631 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
16632 public relays prefer the (faster) P224 group, and bridges prefer
16633 the (more common) P256 group; you can override this with the
16636 This feature requires clients running 0.2.3.17-beta or later,
16637 and requires both sides to be running OpenSSL 1.0.0 or later
16638 with ECC support. OpenSSL 1.0.1, with the compile-time option
16639 "enable-ec_nistp_64_gcc_128", is highly recommended.
16641 Implements the relay side of proposal 198; closes ticket 7200.
16643 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
16644 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
16645 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
16646 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
16647 them to solve bug 6033.)
16649 o Major features (relay performance):
16650 - Instead of limiting the number of queued onionskins (aka circuit
16651 create requests) to a fixed, hard-to-configure number, we limit
16652 the size of the queue based on how many we expect to be able to
16653 process in a given amount of time. We estimate the time it will
16654 take to process an onionskin based on average processing time
16655 of previous onionskins. Closes ticket 7291. You'll never have to
16656 configure MaxOnionsPending again.
16657 - Relays process the new "NTor" circuit-level handshake requests
16658 with higher priority than the old "TAP" circuit-level handshake
16659 requests. We still process some TAP requests to not totally starve
16660 0.2.3 clients when NTor becomes popular. A new consensus parameter
16661 "NumNTorsPerTAP" lets us tune the balance later if we need to.
16662 Implements ticket 9574.
16664 o Major features (client bootstrapping resilience):
16665 - Add a new "FallbackDir" torrc option to use when we can't use
16666 a directory mirror from the consensus (either because we lack a
16667 consensus, or because they're all down). Currently, all authorities
16668 are fallbacks by default, and there are no other default fallbacks,
16669 but that will change. This option will allow us to give clients a
16670 longer list of servers to try to get a consensus from when first
16671 connecting to the Tor network, and thereby reduce load on the
16672 directory authorities. Implements proposal 206, "Preconfigured
16673 directory sources for bootstrapping". We also removed the old
16674 "FallbackNetworkstatus" option, since we never got it working well
16675 enough to use it. Closes bug 572.
16676 - If we have no circuits open, use a relaxed timeout (the
16677 95th-percentile cutoff) until a circuit succeeds. This heuristic
16678 should allow Tor to succeed at building circuits even when the
16679 network connection drastically changes. Should help with bug 3443.
16681 o Major features (use of guards):
16682 - Support directory guards (proposal 207): when possible, clients now
16683 use their entry guards for non-anonymous directory requests. This
16684 can help prevent client enumeration. Note that this behavior only
16685 works when we have a usable consensus directory, and when options
16686 about what to download are more or less standard. In the future we
16687 should re-bootstrap from our guards, rather than re-bootstrapping
16688 from the preconfigured list of directory sources that ships with
16689 Tor. Resolves ticket 6526.
16690 - Raise the default time that a client keeps an entry guard from
16691 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
16692 2012 paper. (We would make it even longer, but we need better client
16693 load balancing first.) Also, make the guard lifetime controllable
16694 via a new GuardLifetime torrc option and a GuardLifetime consensus
16695 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
16697 o Major features (bridges with pluggable transports):
16698 - Bridges now report the pluggable transports they support to the
16699 bridge authority, so it can pass the supported transports on to
16700 bridgedb and/or eventually do reachability testing. Implements
16702 - Automatically forward the TCP ports of pluggable transport
16703 proxies using tor-fw-helper if PortForwarding is enabled. Implements
16706 o Major features (geoip database):
16707 - Maxmind began labelling Tor relays as being in country "A1",
16708 which breaks by-country node selection inside Tor. Now we use a
16709 script to replace "A1" ("Anonymous Proxy") entries in our geoip
16710 file with real country codes. This script fixes about 90% of "A1"
16711 entries automatically and uses manual country code assignments to
16712 fix the remaining 10%. See src/config/README.geoip for details.
16714 - Add GeoIP database for IPv6 addresses. The new config option
16716 - Update to the October 2 2013 Maxmind GeoLite Country database.
16718 o Major features (IPv6):
16719 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
16720 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
16721 to happen. Implements ticket 5535.
16722 - All kind of relays, not just bridges, can now advertise an IPv6
16723 OR port. Implements ticket 6362.
16724 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
16725 connectivity, then set the IPv6Exit flag to 1. Also make sure your
16726 exit policy reads as you would like: the address * applies to all
16727 address families, whereas *4 is IPv4 address only, and *6 is IPv6
16728 addresses only. On the client side, you'll need to wait for enough
16729 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
16730 and use Socks5. Closes ticket 5547, implements proposal 117 as
16731 revised in proposal 208.
16732 - Bridge authorities now accept IPv6 bridge addresses and include
16733 them in network status documents. Implements ticket 5534.
16734 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
16736 o Major features (directory authorities):
16737 - Directory authorities now prefer using measured bandwidths to
16738 advertised ones when computing flags and thresholds. Resolves
16740 - Directory authorities that vote measured bandwidths about more
16741 than a threshold number of relays now treat relays with
16742 unmeasured bandwidths as having bandwidth 0 when computing their
16743 flags. Resolves ticket 8435.
16744 - Directory authorities now support a new consensus method (17)
16745 where they cap the published bandwidth of relays for which
16746 insufficient bandwidth measurements exist. Fixes part of bug 2286.
16747 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
16748 serve any v2 directory information. Now we can test disabling the
16749 old deprecated v2 directory format, and see whether doing so has
16750 any effect on network load. Begins to fix bug 6783.
16752 o Major features (build and portability):
16753 - Switch to a nonrecursive Makefile structure. Now instead of each
16754 Makefile.am invoking other Makefile.am's, there is a master
16755 Makefile.am that includes the others. This change makes our build
16756 process slightly more maintainable, and improves parallelism for
16757 building with make -j. Original patch by Stewart Smith; various
16758 fixes by Jim Meyering.
16759 - Where available, we now use automake's "silent" make rules by
16760 default, so that warnings are easier to spot. You can get the old
16761 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
16762 - Resume building correctly with MSVC and Makefile.nmake. This patch
16763 resolves numerous bugs and fixes reported by ultramage, including
16764 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
16766 o Security features:
16767 - Switch to a completely time-invariant approach for picking nodes
16768 weighted by bandwidth. Our old approach would run through the
16769 part of the loop after it had made its choice slightly slower
16770 than it ran through the part of the loop before it had made its
16771 choice. Addresses ticket 6538.
16772 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
16773 by tor2web clients allows hidden services to identify tor2web
16774 clients through their repeated selection of the same rendezvous
16775 and introduction point circuit endpoints (their guards). Resolves
16778 o Major bugfixes (relay denial of service):
16779 - When we have too much memory queued in circuits (according to a new
16780 MaxMemInCellQueues option), close the circuits that have the oldest
16781 queued cells, on the theory that those are most responsible for
16782 us running low on memory. This prevents us from running out of
16783 memory as a relay if circuits fill up faster than they can be
16784 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
16785 Tor. This bug is a further fix beyond bug 6252, whose fix was
16786 merged into 0.2.3.21-rc.
16787 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
16788 ID: these could be used to create unexpected streams and circuits
16789 which would count as "present" to some parts of Tor but "absent"
16790 to others, leading to zombie circuits and streams or to a bandwidth
16791 denial-of-service. Fixes bug 7889; bugfix on every released version
16792 of Tor. Reported by "oftc_must_be_destroyed".
16793 - Avoid a bug where our response to TLS renegotiation under certain
16794 network conditions could lead to a busy-loop, with 100% CPU
16795 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
16797 o Major bugfixes (asserts, crashes, leaks):
16798 - Prevent the get_freelists() function from running off the end of
16799 the list of freelists if it somehow gets an unrecognized
16800 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
16802 - Avoid a memory leak where we would leak a consensus body when we
16803 find that a consensus which we couldn't previously verify due to
16804 missing certificates is now verifiable. Fixes bug 8719; bugfix
16806 - If we are unable to save a microdescriptor to the journal, do not
16807 drop it from memory and then reattempt downloading it. Fixes bug
16808 9645; bugfix on 0.2.2.6-alpha.
16809 - Fix an assertion failure that would occur when disabling the
16810 ORPort setting on a running Tor process while accounting was
16811 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
16812 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
16813 when an exit connection with optimistic data succeeds immediately
16814 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
16816 - Fix a memory leak that would occur whenever a configuration
16817 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
16819 o Major bugfixes (relay rate limiting):
16820 - When a TLS write is partially successful but incomplete, remember
16821 that the flushed part has been flushed, and notice that bytes were
16822 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
16823 bugfix on Tor 0.1.0.5-rc.
16824 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
16825 to 1GB/1GB. The previous defaults were intended to be "basically
16826 infinite", but it turns out they're now limiting our 100mbit+
16827 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
16828 last time we raised it).
16829 - No longer stop reading or writing on cpuworker connections when
16830 our rate limiting buckets go empty. Now we should handle circuit
16831 handshake requests more promptly. Resolves bug 9731.
16833 o Major bugfixes (client-side privacy):
16834 - When we mark a circuit as unusable for new circuits, have it
16835 continue to be unusable for new circuits even if MaxCircuitDirtiness
16836 is increased too much at the wrong time, or the system clock jumps
16837 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
16838 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
16839 which have resolved to internal addresses") is set, apply that
16840 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
16841 - When an exit relay rejects a stream with reason "exit policy", but
16842 we only know an exit policy summary (e.g. from the microdesc
16843 consensus) for it, do not mark the relay as useless for all exiting.
16844 Instead, mark just the circuit as unsuitable for that particular
16845 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
16847 o Major bugfixes (stream isolation):
16848 - Allow applications to get proper stream isolation with
16849 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
16850 username/password authentication also offer "no authentication". Tor
16851 had previously preferred "no authentication", so the applications
16852 never actually sent Tor their auth details. Now Tor selects
16853 username/password authentication if it's offered. You can disable
16854 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
16855 bug 8117; bugfix on 0.2.3.3-alpha.
16856 - Follow the socks5 protocol when offering username/password
16857 authentication. The fix for bug 8117 exposed this bug, and it
16858 turns out real-world applications like Pidgin do care. Bugfix on
16859 0.2.3.2-alpha; fixes bug 8879.
16861 o Major bugfixes (client circuit building):
16862 - Alter circuit build timeout measurement to start at the point
16863 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
16864 initialization). This should make our timeout measurements more
16865 uniform. Previously, we were sometimes including ORconn setup time
16866 in our circuit build time measurements. Should resolve bug 3443.
16867 - If the circuit build timeout logic is disabled (via the consensus,
16868 or because we are an authority), then don't build testing circuits.
16869 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
16871 o Major bugfixes (client-side DNS):
16872 - Turn off the client-side DNS cache by default. Updating and using
16873 the DNS cache is now configurable on a per-client-port
16874 level. SOCKSPort, DNSPort, etc lines may now contain
16875 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
16876 cache these types of DNS answers when we receive them from an
16877 exit node in response to an application request on this port, and
16878 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
16879 cached DNS answers of these types, we shouldn't use them. It's
16880 potentially risky to use cached DNS answers at the client, since
16881 doing so can indicate to one exit what answers we've gotten
16882 for DNS lookups in the past. With IPv6, this becomes especially
16883 problematic. Using cached DNS answers for requests on the same
16884 circuit would present less linkability risk, since all traffic
16885 on a circuit is already linkable, but it would also provide
16886 little performance benefit: the exit node caches DNS replies
16887 too. Implements a simplified version of Proposal 205. Implements
16890 o Major bugfixes (hidden service privacy):
16891 - Limit hidden service descriptors to at most ten introduction
16892 points, to slow one kind of guard enumeration. Fixes bug 9002;
16893 bugfix on 0.1.1.11-alpha.
16895 o Major bugfixes (directory fetching):
16896 - If the time to download the next old-style networkstatus is in
16897 the future, do not decline to consider whether to download the
16898 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
16900 - We used to always request authority certificates by identity digest,
16901 meaning we'd get the newest one even when we wanted one with a
16902 different signing key. Then we would complain about being given
16903 a certificate we already had, and never get the one we really
16904 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
16905 resource to request the one we want. Fixes bug 5595; bugfix on
16908 o Major bugfixes (bridge reachability):
16909 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
16910 previously they did not, which prevented them from receiving
16911 successful connections from relays for self-test or bandwidth
16912 testing. Also, when a relay is extending a circuit to a bridge,
16913 it needs to send a NETINFO cell, even when the bridge hasn't sent
16914 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
16916 o Major bugfixes (control interface):
16917 - When receiving a new configuration file via the control port's
16918 LOADCONF command, do not treat the defaults file as absent.
16919 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
16921 o Major bugfixes (directory authorities):
16922 - Stop marking every relay as having been down for one hour every
16923 time we restart a directory authority. These artificial downtimes
16924 were messing with our Stable and Guard flag calculations. Fixes
16925 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
16926 - When computing directory thresholds, ignore any rejected-as-sybil
16927 nodes during the computation so that they can't influence Fast,
16928 Guard, etc. (We should have done this for proposal 109.) Fixes
16930 - When marking a node as a likely sybil, reset its uptime metrics
16931 to zero, so that it cannot time towards getting marked as Guard,
16932 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
16934 - Fix a bug in the voting algorithm that could yield incorrect results
16935 when a non-naming authority declared too many flags. Fixes bug 9200;
16936 bugfix on 0.2.0.3-alpha.
16938 o Internal abstraction features:
16939 - Introduce new channel_t abstraction between circuits and
16940 or_connection_t to allow for implementing alternate OR-to-OR
16941 transports. A channel_t is an abstract object which can either be a
16942 cell-bearing channel, which is responsible for authenticating and
16943 handshaking with the remote OR and transmitting cells to and from
16944 it, or a listening channel, which spawns new cell-bearing channels
16945 at the request of remote ORs. Implements part of ticket 6465.
16946 - Make a channel_tls_t subclass of channel_t, adapting it to the
16947 existing or_connection_t code. The V2/V3 protocol handshaking
16948 code which formerly resided in command.c has been moved below the
16949 channel_t abstraction layer and may be found in channeltls.c now.
16950 Implements the rest of ticket 6465.
16951 - Introduce new circuitmux_t storing the queue of circuits for
16952 a channel; this encapsulates and abstracts the queue logic and
16953 circuit selection policy, and allows the latter to be overridden
16954 easily by switching out a policy object. The existing EWMA behavior
16955 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
16957 o New build requirements:
16958 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
16959 strongly recommended.
16960 - Tor maintainers now require Automake version 1.9 or later to build
16961 Tor from the Git repository. (Automake is not required when building
16962 from a source distribution.)
16964 o Minor features (protocol):
16965 - No longer include the "opt" prefix when generating routerinfos
16966 or v2 directories: it has been needless since Tor 0.1.2. Closes
16968 - Reject EXTEND cells sent to nonexistent streams. According to the
16969 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
16970 we were only checking for stream IDs that were currently in use.
16971 Found while hunting for more instances of bug 6271. Bugfix on
16972 0.0.2pre8, which introduced incremental circuit construction.
16973 - Tor relays and clients now support a better CREATE/EXTEND cell
16974 format, allowing the sender to specify multiple address, identity,
16975 and handshake types. Implements Robert Ransom's proposal 200;
16976 closes ticket 7199.
16977 - Reject as invalid most directory objects containing a NUL.
16978 Belt-and-suspender fix for bug 8037.
16980 o Minor features (security):
16981 - Clear keys and key-derived material left on the stack in
16982 rendservice.c and rendclient.c. Check return value of
16983 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
16984 These fixes should make us more forward-secure against cold-boot
16985 attacks and the like. Fixes bug 2385.
16986 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
16987 Irix's random() only return 15 bits; Solaris's random() returns more
16988 bits but its RAND_MAX says it only returns 15, and so on. Motivated
16989 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
16991 o Minor features (control protocol):
16992 - Add a "GETINFO signal/names" control port command. Implements
16994 - Provide default values for all options via "GETINFO config/defaults".
16995 Implements ticket 4971.
16996 - Allow an optional $ before the node identity digest in the
16997 controller command GETINFO ns/id/<identity>, for consistency with
16998 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
16999 - Add CACHED keyword to ADDRMAP events in the control protocol
17000 to indicate whether a DNS result will be cached or not. Resolves
17002 - Generate bootstrapping status update events correctly when fetching
17003 microdescriptors. Fixes bug 9927.
17005 o Minor features (path selection):
17006 - When deciding whether we have enough descriptors to build circuits,
17007 instead of looking at raw relay counts, look at which fraction
17008 of (bandwidth-weighted) paths we're able to build. This approach
17009 keeps clients from building circuits if their paths are likely to
17010 stand out statistically. The default fraction of paths needed is
17011 taken from the consensus directory; you can override it with the
17012 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
17013 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
17014 and we have GeoIP information, also exclude all nodes with unknown
17015 countries "??" and "A1". This behavior is controlled by the
17016 new GeoIPExcludeUnknown option: you can make such nodes always
17017 excluded with "GeoIPExcludeUnknown 1", and disable the feature
17018 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
17019 gets you the default behavior. Implements feature 7706.
17021 o Minor features (hidden services):
17022 - Improve circuit build timeout handling for hidden services.
17023 In particular: adjust build timeouts more accurately depending
17024 upon the number of hop-RTTs that a particular circuit type
17025 undergoes. Additionally, launch intro circuits in parallel
17026 if they timeout, and take the first one to reply as valid.
17027 - The Tor client now ignores sub-domain components of a .onion
17028 address. This change makes HTTP "virtual" hosting
17029 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
17030 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
17031 hosted on the same hidden service. Implements proposal 204.
17032 - Enable Tor to read configuration, state, and key information from
17033 a FIFO. Previously Tor would only read from files with a positive
17034 stat.st_size. Code from meejah; fixes bug 6044.
17036 o Minor features (clients):
17037 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
17038 microdescriptor-related dir requests, and only fall back to normal
17039 descriptors if none of their bridges can handle microdescriptors
17040 (as opposed to the fix in ticket 4013, which caused them to fall
17041 back to normal descriptors if *any* of their bridges preferred
17042 them). Resolves ticket 4994.
17043 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
17044 TCP ports to forward. In the past it only accepted two ports:
17045 the ORPort and the DirPort.
17047 o Minor features (protecting client timestamps):
17048 - Clients no longer send timestamps in their NETINFO cells. These were
17049 not used for anything, and they provided one small way for clients
17050 to be distinguished from each other as they moved from network to
17051 network or behind NAT. Implements part of proposal 222.
17052 - Clients now round timestamps in INTRODUCE cells down to the nearest
17053 10 minutes. If a new Support022HiddenServices option is set to 0, or
17054 if it's set to "auto" and the feature is disabled in the consensus,
17055 the timestamp is sent as 0 instead. Implements part of proposal 222.
17056 - Stop sending timestamps in AUTHENTICATE cells. This is not such
17057 a big deal from a security point of view, but it achieves no actual
17058 good purpose, and isn't needed. Implements part of proposal 222.
17059 - Reduce down accuracy of timestamps in hidden service descriptors.
17060 Implements part of proposal 222.
17062 o Minor features (bridges):
17063 - Make bridge relays check once a minute for whether their IP
17064 address has changed, rather than only every 15 minutes. Resolves
17065 bugs 1913 and 1992.
17066 - Bridge statistics now count bridge clients connecting over IPv6:
17067 bridge statistics files now list "bridge-ip-versions" and
17068 extra-info documents list "geoip6-db-digest". The control protocol
17069 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
17070 implementation by "shkoo", addressing ticket 5055.
17071 - Add a new torrc option "ServerTransportListenAddr" to let bridge
17072 operators select the address where their pluggable transports will
17073 listen for connections. Resolves ticket 7013.
17074 - Randomize the lifetime of our SSL link certificate, so censors can't
17075 use the static value for filtering Tor flows. Resolves ticket 8443;
17076 related to ticket 4014 which was included in 0.2.2.33.
17078 o Minor features (relays):
17079 - Option OutboundBindAddress can be specified multiple times and
17080 accepts IPv6 addresses. Resolves ticket 6876.
17082 o Minor features (IPv6, client side):
17083 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
17084 prefer to hand out virtual IPv6 addresses, since there are more of
17085 them and we can't run out. To override this behavior and make IPv4
17086 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
17087 or DNSPort you're using for resolving. Implements ticket 7571.
17088 - AutomapHostsOnResolve responses are now randomized, to avoid
17089 annoying situations where Tor is restarted and applications
17090 connect to the wrong addresses.
17091 - Never try more than 1000 times to pick a new virtual address when
17092 AutomapHostsOnResolve is set. That's good enough so long as we
17093 aren't close to handing out our entire virtual address space;
17094 if you're getting there, it's best to switch to IPv6 virtual
17097 o Minor features (IPv6, relay/authority side):
17098 - New config option "AuthDirHasIPv6Connectivity 1" that directory
17099 authorities should set if they have IPv6 connectivity and want to
17100 do reachability tests for IPv6 relays. Implements feature 5974.
17101 - A relay with an IPv6 OR port now sends that address in NETINFO
17102 cells (in addition to its other address). Implements ticket 6364.
17104 o Minor features (directory authorities):
17105 - Directory authorities no long accept descriptors for any version of
17106 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
17107 These versions are insecure, unsupported, or both. Implements
17109 - When directory authorities are computing thresholds for flags,
17110 never let the threshold for the Fast flag fall below 4096
17111 bytes. Also, do not consider nodes with extremely low bandwidths
17112 when deciding thresholds for various directory flags. This change
17113 should raise our threshold for Fast relays, possibly in turn
17114 improving overall network performance; see ticket 1854. Resolves
17116 - Directory authorities now include inside each vote a statement of
17117 the performance thresholds they used when assigning flags.
17118 Implements ticket 8151.
17119 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
17120 in directory authority votes to describe whether they have enough
17121 measured bandwidths to ignore advertised (relay descriptor)
17122 bandwidth claims. Resolves ticket 8711.
17124 o Minor features (path bias detection):
17125 - Path Use Bias: Perform separate accounting for successful circuit
17126 use. Keep separate statistics on stream attempt rates versus stream
17127 success rates for each guard. Provide configurable thresholds to
17128 determine when to emit log messages or disable use of guards that
17129 fail too many stream attempts. Resolves ticket 7802.
17130 - Create three levels of Path Bias log messages, as opposed to just
17131 two. These are configurable via consensus as well as via the torrc
17132 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
17133 The default values are 0.70, 0.50, and 0.30 respectively.
17134 - Separate the log message levels from the decision to drop guards,
17135 which also is available via torrc option PathBiasDropGuards.
17136 PathBiasDropGuards still defaults to 0 (off).
17137 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
17138 in combination with PathBiasExtremeRate.
17139 - Increase the default values for PathBiasScaleThreshold and
17140 PathBiasCircThreshold from (200, 20) to (300, 150).
17141 - Add in circuit usage accounting to path bias. If we try to use a
17142 built circuit but fail for any reason, it counts as path bias.
17143 Certain classes of circuits where the adversary gets to pick your
17144 destination node are exempt from this accounting. Usage accounting
17145 can be specifically disabled via consensus parameter or torrc.
17146 - Convert all internal path bias state to double-precision floating
17147 point, to avoid roundoff error and other issues.
17148 - Only record path bias information for circuits that have completed
17149 *two* hops. Assuming end-to-end tagging is the attack vector, this
17150 makes us more resilient to ambient circuit failure without any
17151 detection capability loss.
17153 o Minor features (build):
17154 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
17155 dhill. Resolves ticket 6982.
17156 - Compile on win64 using mingw64. Fixes bug 7260; patches from
17158 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
17159 separate error codes; or at least, don't break for that reason.
17160 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
17162 o Build improvements (autotools):
17163 - Warn if building on a platform with an unsigned time_t: there
17164 are too many places where Tor currently assumes that time_t can
17165 hold negative values. We'd like to fix them all, but probably
17167 - Do not report status verbosely from autogen.sh unless the -v flag
17168 is specified. Fixes issue 4664. Patch from Onizuka.
17169 - Detect and reject attempts to build Tor with threading support
17170 when OpenSSL has been compiled without threading support.
17172 - Try to detect if we are ever building on a platform where
17173 memset(...,0,...) does not set the value of a double to 0.0. Such
17174 platforms are permitted by the C standard, though in practice
17175 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
17176 currently support them, but it's better to detect them and fail
17177 than to perform erroneously.
17178 - We no longer warn so much when generating manpages from their
17180 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
17181 the signs of types during autoconf. This is better than our old
17182 approach, which didn't work when cross-compiling.
17184 o Minor features (log messages, warnings):
17185 - Detect when we're running with a version of OpenSSL other than the
17186 one we compiled with. This conflict has occasionally given people
17187 hard-to-track-down errors.
17188 - Warn users who run hidden services on a Tor client with
17189 UseEntryGuards disabled that their hidden services will be
17190 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
17191 attack which motivated Tor to support entry guards in the first
17192 place). Resolves ticket 6889.
17193 - Warn when we are binding low ports when hibernation is enabled;
17194 previously we had warned when we were _advertising_ low ports with
17195 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
17196 - Issue a warning when running with the bufferevents backend enabled.
17197 It's still not stable, and people should know that they're likely
17198 to hit unexpected problems. Closes ticket 9147.
17200 o Minor features (log messages, notices):
17201 - Refactor resolve_my_address() so it returns the method by which we
17202 decided our public IP address (explicitly configured, resolved from
17203 explicit hostname, guessed from interfaces, learned by gethostname).
17204 Now we can provide more helpful log messages when a relay guesses
17205 its IP address incorrectly (e.g. due to unexpected lines in
17206 /etc/hosts). Resolves ticket 2267.
17207 - Track how many "TAP" and "NTor" circuit handshake requests we get,
17208 and how many we complete, and log it every hour to help relay
17209 operators follow trends in network load. Addresses ticket 9658.
17211 o Minor features (log messages, diagnostics):
17212 - If we fail to free a microdescriptor because of bug 7164, log
17213 the filename and line number from which we tried to free it.
17214 - We compute the overhead from passing onionskins back and forth to
17215 cpuworkers, and report it when dumping statistics in response to
17216 SIGUSR1. Supports ticket 7291.
17217 - Add another diagnostic to the heartbeat message: track and log
17218 overhead that TLS is adding to the data we write. If this is
17219 high, we are sending too little data to SSL_write at a time.
17220 Diagnostic for bug 7707.
17221 - Log packaged cell fullness as part of the heartbeat message.
17222 Diagnosis to try to determine the extent of bug 7743.
17223 - Add more detail to a log message about relaxed timeouts, to help
17225 - When learning a fingerprint for a bridge, log its corresponding
17226 transport type. Implements ticket 7896.
17227 - Warn more aggressively when flushing microdescriptors to a
17228 microdescriptor cache fails, in an attempt to mitigate bug 8031,
17229 or at least make it more diagnosable.
17230 - Improve the log message when "Bug/attack: unexpected sendme cell
17231 from client" occurs, to help us track bug 8093.
17232 - Improve debugging output to help track down bug 8185 ("Bug:
17233 outgoing relay cell has n_chan==NULL. Dropping.")
17235 o Minor features (log messages, quieter bootstrapping):
17236 - Log fewer lines at level "notice" about our OpenSSL and Libevent
17237 versions and capabilities when everything is going right. Resolves
17238 part of ticket 6736.
17239 - Omit the first heartbeat log message, because it never has anything
17240 useful to say, and it clutters up the bootstrapping messages.
17241 Resolves ticket 6758.
17242 - Don't log about reloading the microdescriptor cache at startup. Our
17243 bootstrap warnings are supposed to tell the user when there's a
17244 problem, and our bootstrap notices say when there isn't. Resolves
17245 ticket 6759; bugfix on 0.2.2.6-alpha.
17246 - Don't log "I learned some more directory information" when we're
17247 reading cached directory information. Reserve it for when new
17248 directory information arrives in response to a fetch. Resolves
17250 - Don't complain about bootstrapping problems while hibernating.
17251 These complaints reflect a general code problem, but not one
17252 with any problematic effects (no connections are actually
17253 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
17255 o Minor features (testing):
17256 - In our testsuite, create temporary directories with a bit more
17257 entropy in their name to make name collisions less likely. Fixes
17259 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
17260 (P-256) Diffie-Hellman handshakes to src/or/bench.
17261 - Add benchmark functions to test onion handshake performance.
17264 - The DirServer option is now DirAuthority, for consistency with
17265 current naming patterns. You can still use the old DirServer form.
17267 o Minor bugfixes (protocol):
17268 - Fix the handling of a TRUNCATE cell when it arrives while the
17269 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
17270 - When a Tor client gets a "truncated" relay cell, the first byte of
17271 its payload specifies why the circuit was truncated. We were
17272 ignoring this 'reason' byte when tearing down the circuit, resulting
17273 in the controller not being told why the circuit closed. Now we
17274 pass the reason from the truncated cell to the controller. Bugfix
17275 on 0.1.2.3-alpha; fixes bug 7039.
17276 - Fix a misframing issue when reading the version numbers in a
17277 VERSIONS cell. Previously we would recognize [00 01 00 02] as
17278 'version 1, version 2, and version 0x100', when it should have
17279 only included versions 1 and 2. Fixes bug 8059; bugfix on
17280 0.2.0.10-alpha. Reported pseudonymously.
17281 - Make the format and order of STREAM events for DNS lookups
17282 consistent among the various ways to launch DNS lookups. Fixes
17283 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
17285 o Minor bugfixes (syscalls and disk interaction):
17286 - Always check the return values of functions fcntl() and
17287 setsockopt(). We don't believe these are ever actually failing in
17288 practice, but better safe than sorry. Also, checking these return
17289 values should please analysis tools like Coverity. Patch from
17290 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
17291 - Avoid double-closing the listener socket in our socketpair()
17292 replacement (used on Windows) in the case where the addresses on
17293 our opened sockets don't match what we expected. Fixes bug 9400;
17294 bugfix on 0.0.2pre7. Found by Coverity.
17295 - Correctly store microdescriptors and extrainfo descriptors that
17296 include an internal NUL byte. Fixes bug 8037; bugfix on
17297 0.2.0.1-alpha. Bug reported by "cypherpunks".
17298 - If for some reason we fail to write a microdescriptor while
17299 rebuilding the cache, do not let the annotations from that
17300 microdescriptor linger in the cache file, and do not let the
17301 microdescriptor stay recorded as present in its old location.
17302 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
17303 - Use direct writes rather than stdio when building microdescriptor
17304 caches, in an attempt to mitigate bug 8031, or at least make it
17307 o Minor fixes (config options):
17308 - Warn and fail if a server is configured not to advertise any
17309 ORPorts at all. (We need *something* to put in our descriptor,
17310 or we just won't work.)
17311 - Behave correctly when the user disables LearnCircuitBuildTimeout
17312 but doesn't tell us what they would like the timeout to be. Fixes
17313 bug 6304; bugfix on 0.2.2.14-alpha.
17314 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
17315 to start with a triple-underscore so the controller won't touch it.
17316 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
17317 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
17318 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
17319 - When autodetecting the number of CPUs, use the number of available
17320 CPUs in preference to the number of configured CPUs. Inform the
17321 user if this reduces the number of available CPUs. Fixes bug 8002;
17322 bugfix on 0.2.3.1-alpha.
17323 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
17324 - Make it an error when you set EntryNodes but disable UseGuardNodes,
17325 since it will (surprisingly to some users) ignore EntryNodes. Fixes
17326 bug 8180; bugfix on 0.2.3.11-alpha.
17327 - Avoid overflows when the user sets MaxCircuitDirtiness to a
17328 ridiculously high value, by imposing a (ridiculously high) 30-day
17329 maximum on MaxCircuitDirtiness.
17331 o Minor bugfixes (control protocol):
17332 - Stop sending a stray "(null)" in some cases for the server status
17333 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
17335 - The ADDRMAP command can no longer generate an ill-formed error
17336 code on a failed MAPADDRESS. It now says "internal" rather than
17337 an English sentence fragment with spaces in the middle. Bugfix on
17338 Tor 0.2.0.19-alpha.
17340 o Minor bugfixes (clients / edges):
17341 - When we receive a RELAY_END cell with the reason DONE, or with no
17342 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
17343 status as "connection refused". Previously we reported these cases
17344 as success but then immediately closed the connection. Fixes bug
17345 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
17346 - If the guard we choose first doesn't answer, we would try the
17347 second guard, but once we connected to the second guard we would
17348 abandon it and retry the first one, slowing down bootstrapping.
17349 The fix is to treat all our initially chosen guards as acceptable
17350 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
17351 - When choosing which stream on a formerly stalled circuit to wake
17352 first, make better use of the platform's weak RNG. Previously,
17353 we had been using the % ("modulo") operator to try to generate a
17354 1/N chance of picking each stream, but this behaves badly with
17355 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
17358 o Minor bugfixes (path bias detection):
17359 - If the state file's path bias counts are invalid (presumably from a
17360 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
17361 additional checks and log messages to the scaling of Path Bias
17362 counts, in case there still are remaining issues with scaling.
17363 Should help resolve bug 8235.
17364 - Prevent rounding error in path bias counts when scaling
17365 them down, and use the correct scale factor default. Also demote
17366 some path bias related log messages down a level and make others
17367 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
17368 - Remove a source of rounding error during path bias count scaling;
17369 don't count cannibalized circuits as used for path bias until we
17370 actually try to use them; and fix a circuit_package_relay_cell()
17371 warning message about n_chan==NULL. Fixes bug 7802.
17372 - Paste the description for PathBias parameters from the man
17373 page into or.h, so the code documents them too. Fixes bug 7982;
17374 bugfix on 0.2.3.17-beta.
17376 o Minor bugfixes (relays):
17377 - Stop trying to resolve our hostname so often (e.g. every time we
17378 think about doing a directory fetch). Now we reuse the cached
17379 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
17380 and 2410 (bugfix on 0.1.2.2-alpha).
17381 - When examining the list of network interfaces to find our address,
17382 do not consider non-running or disabled network interfaces. Fixes
17383 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
17385 o Minor bugfixes (blocking resistance):
17386 - Only disable TLS session ticket support when running as a TLS
17387 server. Now clients will blend better with regular Firefox
17388 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
17390 o Minor bugfixes (IPv6):
17391 - Use square brackets around IPv6 addresses in numerous places
17392 that needed them, including log messages, HTTPS CONNECT proxy
17393 requests, TransportProxy statefile entries, and pluggable transport
17394 extra-info lines. Fixes bug 7011; patch by David Fifield.
17396 o Minor bugfixes (directory authorities):
17397 - Reject consensus votes with more than 64 known-flags. We aren't even
17398 close to that limit yet, and our code doesn't handle it correctly.
17399 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
17400 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
17401 bugfix on 0.2.0.3-alpha.
17403 o Minor bugfixes (memory leaks):
17404 - Avoid leaking memory if we fail to compute a consensus signature
17405 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
17406 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
17407 on 0.2.1.1-alpha; fixes bug 7816.
17408 - Fix a memory leak during safe-cookie controller authentication.
17409 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
17410 - Free some more still-in-use memory at exit, to make hunting for
17411 memory leaks easier. Resolves bug 7029.
17413 o Minor bugfixes (code correctness):
17414 - Increase the width of the field used to remember a connection's
17415 link protocol version to two bytes. Harmless for now, since the
17416 only currently recognized versions are one byte long. Reported
17417 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
17418 - Fix a crash when debugging unit tests on Windows: deallocate a
17419 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
17420 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
17421 - When detecting the largest possible file descriptor (in order to
17422 close all file descriptors when launching a new program), actually
17423 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
17424 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
17426 - Avoid a crash if we fail to generate an extrainfo descriptor.
17427 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
17428 this is CID 718634.
17429 - Avoid an off-by-one error when checking buffer boundaries when
17430 formatting the exit status of a pluggable transport helper.
17431 This is probably not an exploitable bug, but better safe than
17432 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
17434 - Get rid of a couple of harmless clang warnings, where we compared
17435 enums to ints. These warnings are newly introduced in clang 3.2.
17437 o Minor bugfixes (code cleanliness):
17438 - Avoid use of reserved identifiers in our C code. The C standard
17439 doesn't like us declaring anything that starts with an
17440 underscore, so let's knock it off before we get in trouble. Fix
17441 for bug 1031; bugfix on the first Tor commit.
17442 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
17443 with large values. This situation was untriggered, but nevertheless
17444 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
17445 - Fix an impossible buffer overrun in the AES unit tests. Fixes
17446 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
17447 - Fix handling of rendezvous client authorization types over 8.
17448 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
17449 - Remove a couple of extraneous semicolons that were upsetting the
17450 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
17451 bugfix on 0.2.2.1-alpha.
17452 - When complaining about a client port on a public address, log
17453 which address we're complaining about. Fixes bug 4020; bugfix on
17454 0.2.3.3-alpha. Patch by Tom Fitzhenry.
17456 o Minor bugfixes (log messages, warnings):
17457 - If we encounter a write failure on a SOCKS connection before we
17458 finish our SOCKS handshake, don't warn that we closed the
17459 connection before we could send a SOCKS reply. Fixes bug 8427;
17460 bugfix on 0.1.0.1-rc.
17461 - Fix a directory authority warn caused when we have a large amount
17462 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
17463 - Downgrade "Failed to hand off onionskin" messages to "debug"
17464 severity, since they're typically redundant with the "Your computer
17465 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
17466 - Avoid spurious warnings when configuring multiple client ports of
17467 which only some are nonlocal. Previously, we had claimed that some
17468 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
17471 o Minor bugfixes (log messages, other):
17472 - Fix log messages and comments to avoid saying "GMT" when we mean
17473 "UTC". Fixes bug 6113.
17474 - When rejecting a configuration because we were unable to parse a
17475 quoted string, log an actual error message. Fixes bug 7950; bugfix
17477 - Correctly recognize that [::1] is a loopback address. Fixes
17478 bug 8377; bugfix on 0.2.1.3-alpha.
17479 - Don't log inappropriate heartbeat messages when hibernating: a
17480 hibernating node is _expected_ to drop out of the consensus,
17481 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
17482 bugfix on 0.2.3.1-alpha.
17483 - Eliminate several instances where we use "Nickname=ID" to refer to
17484 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
17485 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
17488 o Minor bugfixes (build):
17489 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
17490 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
17491 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
17493 o Documentation fixes:
17494 - Make the torify manpage no longer refer to tsocks; torify hasn't
17495 supported tsocks since 0.2.3.14-alpha.
17496 - Make the tor manpage no longer reference tsocks.
17497 - Fix the GeoIPExcludeUnknown documentation to refer to
17498 ExcludeExitNodes rather than the currently nonexistent
17499 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
17500 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
17502 - Say "KBytes" rather than "KB" in the man page (for various values
17503 of K), to further reduce confusion about whether Tor counts in
17504 units of memory or fractions of units of memory. Resolves ticket 7054.
17505 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
17506 names match. Fixes bug 7768.
17507 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
17508 message is logged at notice, not at info.
17509 - Clarify the usage and risks of setting the ContactInfo torrc line
17510 for your relay or bridge. Resolves ticket 9854.
17511 - Add anchors to the manpage so we can link to the html version of
17512 the documentation for specific options. Resolves ticket 9866.
17513 - Replace remaining references to DirServer in man page and
17514 log entries. Resolves ticket 10124.
17516 o Removed features:
17517 - Stop exporting estimates of v2 and v3 directory traffic shares
17518 in extrainfo documents. They were unneeded and sometimes inaccurate.
17519 Also stop exporting any v2 directory request statistics. Resolves
17521 - Drop support for detecting and warning about versions of Libevent
17522 before 1.3e. Nothing reasonable ships with them any longer; warning
17523 the user about them shouldn't be needed. Resolves ticket 6826.
17524 - Now that all versions before 0.2.2.x are disallowed, we no longer
17525 need to work around their missing features. Remove a bunch of
17526 compatibility code.
17529 - The tor-tsocks.conf is no longer distributed or installed. We
17530 recommend that tsocks users use torsocks instead. Resolves
17532 - Remove some of the older contents of doc/ as obsolete; move others
17533 to torspec.git. Fixes bug 8965.
17535 o Code simplification:
17536 - Avoid using character buffers when constructing most directory
17537 objects: this approach was unwieldy and error-prone. Instead,
17538 build smartlists of strings, and concatenate them when done.
17539 - Rename "isin" functions to "contains", for grammar. Resolves
17541 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
17542 with the natural logarithm function from the system libm. Resolves
17544 - Start using OpenBSD's implementation of queue.h, so that we don't
17545 need to hand-roll our own pointer and list structures whenever we
17546 need them. (We can't rely on a sys/queue.h, since some operating
17547 systems don't have them, and the ones that do have them don't all
17548 present the same extensions.)
17549 - Start using OpenBSD's implementation of queue.h (originally by
17551 - Enhance our internal sscanf replacement so that we can eliminate
17552 the last remaining uses of the system sscanf. (Though those uses
17553 of sscanf were safe, sscanf itself is generally error prone, so
17554 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
17556 - Replace all calls to snprintf() outside of src/ext with
17557 tor_snprintf(). Also remove the #define to replace snprintf with
17558 _snprintf on Windows; they have different semantics, and all of
17559 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
17562 - Add a wrapper function for the common "log a message with a
17564 - Split the onion.c file into separate modules for the onion queue
17565 and the different handshakes it supports.
17566 - Move the client-side address-map/virtual-address/DNS-cache code
17567 out of connection_edge.c into a new addressmap.c module.
17568 - Move the entry node code from circuitbuild.c to its own file.
17569 - Move the circuit build timeout tracking code from circuitbuild.c
17571 - Source files taken from other packages now reside in src/ext;
17572 previously they were scattered around the rest of Tor.
17573 - Move the generic "config" code into a new file, and have "config.c"
17574 hold only torrc- and state-related code. Resolves ticket 6823.
17575 - Move the core of our "choose a weighted element at random" logic
17576 into its own function, and give it unit tests. Now the logic is
17577 testable, and a little less fragile too.
17578 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
17579 - Move last_reachable and testing_since from routerinfo_t to node_t.
17580 Implements ticket 5529.
17581 - Add replaycache_t structure, functions and unit tests, then refactor
17582 rend_service_introduce() to be more clear to read, improve, debug,
17583 and test. Resolves bug 6177.
17586 - Remove some now-needless code that tried to aggressively flush
17587 OR connections as data was added to them. Since 0.2.0.1-alpha, our
17588 cell queue logic has saved us from the failure mode that this code
17589 was supposed to prevent. Removing this code will limit the number
17590 of baroque control flow paths through Tor's network logic. Reported
17591 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
17592 - Remove unused code for parsing v1 directories and "running routers"
17593 documents. Fixes bug 6887.
17594 - Remove the marshalling/unmarshalling code for sending requests to
17595 cpuworkers over a socket, and instead just send structs. The
17596 recipient will always be the same Tor binary as the sender, so
17597 any encoding is overkill.
17598 - Remove the testing_since field of node_t, which hasn't been used
17599 for anything since 0.2.0.9-alpha.
17600 - Finally remove support for malloc_good_size and malloc_usable_size.
17601 We had hoped that these functions would let us eke a little more
17602 memory out of our malloc implementation. Unfortunately, the only
17603 implementations that provided these functions are also ones that
17604 are already efficient about not overallocation: they never got us
17605 more than 7 or so bytes per allocation. Removing them saves us a
17606 little code complexity and a nontrivial amount of build complexity.
17609 Changes in version 0.2.3.25 - 2012-11-19
17610 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
17611 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
17612 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
17613 programmer, and friend. Unstinting in his dedication to the cause of
17614 freedom, he inspired and helped many of us as we began our work on
17615 anonymity, and inspires us still. Please honor his memory by writing
17616 software to protect people's freedoms, and by helping others to do so.
17618 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
17619 significantly reduced directory overhead (via microdescriptors),
17620 enormous crypto performance improvements for fast relays on new
17621 enough hardware, a new v3 TLS handshake protocol that can better
17622 resist fingerprinting, support for protocol obfuscation plugins (aka
17623 pluggable transports), better scalability for hidden services, IPv6
17624 support for bridges, performance improvements like allowing clients
17625 to skip the first round-trip on the circuit ("optimistic data") and
17626 refilling token buckets more often, a new "stream isolation" design
17627 to isolate different applications on different circuits, and many
17628 stability, security, and privacy fixes.
17630 Major features (v3 directory protocol):
17631 - Clients now use microdescriptors instead of regular descriptors
17632 to build circuits. Microdescriptors are authority-generated
17633 summaries of regular descriptors' contents, designed to change very
17634 rarely (see proposal 158 for details). This feature is designed
17635 to save bandwidth, especially for clients on slow internet
17636 connections. Use "UseMicrodescriptors 0" to disable it.
17637 - Caches now download, cache, and serve microdescriptors, as well
17638 as multiple "flavors" of the consensus, including a flavor that
17639 describes microdescriptors.
17641 o Major features (build hardening):
17642 - Enable gcc and ld hardening by default. Resolves ticket 5210.
17644 o Major features (relay scaling):
17645 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
17646 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
17647 vectorized AES implementations as appropriate. These can be much,
17648 much faster than other AES implementations.
17649 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
17650 implementation. It makes AES_CTR about 7% faster than our old one
17651 (which was about 10% faster than the one OpenSSL used to provide).
17652 Resolves ticket 4526.
17653 - Use OpenSSL's EVP interface for AES encryption, so that all AES
17654 operations can use hardware acceleration (if present). Resolves
17656 - Unconditionally use OpenSSL's AES implementation instead of our
17657 old built-in one. OpenSSL's AES has been better for a while, and
17658 relatively few servers should still be on any version of OpenSSL
17659 that doesn't have good optimized assembly AES.
17661 o Major features (blocking resistance):
17662 - Update TLS cipher list to match Firefox 8 and later. Resolves
17664 - Remove support for clients falsely claiming to support standard
17665 ciphersuites that they can actually provide. As of modern OpenSSL
17666 versions, it's not necessary to fake any standard ciphersuite,
17667 and doing so prevents us from using better ciphersuites in the
17668 future, since servers can't know whether an advertised ciphersuite
17669 is really supported or not. Some hosts -- notably, ones with very
17670 old versions of OpenSSL or where OpenSSL has been built with ECC
17671 disabled -- will stand out because of this change; TBB users should
17672 not be affected. Implements the client side of proposal 198.
17673 - Implement a new handshake protocol (v3) for authenticating Tors to
17674 each other over TLS. It should be more resistant to fingerprinting
17675 than previous protocols, and should require less TLS hacking for
17676 future Tor implementations. Implements proposal 176.
17677 - Allow variable-length padding cells, to disguise the length of
17678 Tor's TLS records. Implements part of proposal 184.
17679 - While we're trying to bootstrap, record how many TLS connections
17680 fail in each state, and report which states saw the most failures
17681 in response to any bootstrap failures. This feature may speed up
17682 diagnosis of censorship events. Implements ticket 3116.
17684 o Major features (pluggable transports):
17685 - Clients and bridges can now be configured to use a separate
17686 "transport" proxy. This approach makes the censorship arms race
17687 easier by allowing bridges to use protocol obfuscation plugins.
17688 Implements proposal 180 (tickets 2841 and 3472).
17690 o Major features (DoS resistance):
17691 - Now that Tor 0.2.0.x is completely deprecated, enable the final
17692 part of "Proposal 110: Avoiding infinite length circuits" by
17693 refusing all circuit-extend requests that do not use a relay_early
17694 cell. This change helps Tor resist a class of denial-of-service
17695 attacks by limiting the maximum circuit length.
17696 - Tear down the circuit if we get an unexpected SENDME cell. Clients
17697 could use this trick to make their circuits receive cells faster
17698 than our flow control would have allowed, or to gum up the network,
17699 or possibly to do targeted memory denial-of-service attacks on
17700 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
17701 from July 2002, before the release of Tor 0.0.0.
17703 o Major features (hidden services):
17704 - Adjust the number of introduction points that a hidden service
17705 will try to maintain based on how long its introduction points
17706 remain in use and how many introductions they handle. Fixes
17708 - Add a "tor2web mode" for clients that want to connect to hidden
17709 services non-anonymously (and possibly more quickly). As a safety
17710 measure to try to keep users from turning this on without knowing
17711 what they are doing, tor2web mode must be explicitly enabled at
17712 compile time, and a copy of Tor compiled to run in tor2web mode
17713 cannot be used as a normal Tor client. Implements feature 2553.
17715 o Major features (IPv6):
17716 - Clients can now connect to private bridges over IPv6. Bridges
17717 still need at least one IPv4 address in order to connect to
17718 other relays. Note that we don't yet handle the case where the
17719 user has two bridge lines for the same bridge (one IPv4, one
17720 IPv6). Implements parts of proposal 186.
17722 o Major features (directory authorities):
17723 - Use a more secure consensus parameter voting algorithm. Now at
17724 least three directory authorities or a majority of them must
17725 vote on a given parameter before it will be included in the
17726 consensus. Implements proposal 178.
17727 - Remove the artificially low cutoff of 20KB to guarantee the Fast
17728 flag. In the past few years the average relay speed has picked
17729 up, and while the "top 7/8 of the network get the Fast flag" and
17730 "all relays with 20KB or more of capacity get the Fast flag" rules
17731 used to have the same result, now the top 7/8 of the network has
17732 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
17734 o Major features (performance):
17735 - Exit nodes now accept and queue data on not-yet-connected streams.
17736 Previously, the client wasn't allowed to send data until the
17737 stream was connected, which slowed down all connections. This
17738 change will enable clients to perform a "fast-start" on streams
17739 and send data without having to wait for a confirmation that the
17740 stream has opened. Patch from Ian Goldberg; implements the server
17741 side of Proposal 174.
17742 - When using an exit relay running 0.2.3.x, clients can now
17743 "optimistically" send data before the exit relay reports that
17744 the stream has opened. This saves a round trip when starting
17745 connections where the client speaks first (such as web browsing).
17746 This behavior is controlled by a consensus parameter (currently
17747 disabled). To turn it on or off manually, use the "OptimisticData"
17748 torrc option. Implements proposal 181; code by Ian Goldberg.
17749 - Add a new TokenBucketRefillInterval option to refill token buckets
17750 more frequently than once per second. This should improve network
17751 performance, alleviate queueing problems, and make traffic less
17752 bursty. Implements proposal 183; closes ticket 3630. Design by
17753 Florian Tschorsch and Björn Scheuermann; implementation by
17755 - Raise the threshold of server descriptors needed (75%) and exit
17756 server descriptors needed (50%) before we will declare ourselves
17757 bootstrapped. This will make clients start building circuits a
17758 little later, but makes the initially constructed circuits less
17759 skewed and less in conflict with further directory fetches. Fixes
17762 o Major features (relays):
17763 - Relays now try regenerating and uploading their descriptor more
17764 frequently if they are not listed in the consensus, or if the
17765 version of their descriptor listed in the consensus is too
17766 old. This fix should prevent situations where a server declines
17767 to re-publish itself because it has done so too recently, even
17768 though the authorities decided not to list its recent-enough
17769 descriptor. Fix for bug 3327.
17771 o Major features (stream isolation):
17772 - You can now configure Tor so that streams from different
17773 applications are isolated on different circuits, to prevent an
17774 attacker who sees your streams as they leave an exit node from
17775 linking your sessions to one another. To do this, choose some way
17776 to distinguish the applications: have them connect to different
17777 SocksPorts, or have one of them use SOCKS4 while the other uses
17778 SOCKS5, or have them pass different authentication strings to the
17779 SOCKS proxy. Then, use the new SocksPort syntax to configure the
17780 degree of isolation you need. This implements Proposal 171.
17781 - There's a new syntax for specifying multiple client ports (such as
17782 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
17783 multiple *Port entries with full addr:port syntax on each.
17784 The old *ListenAddress format is still supported, but you can't
17785 mix it with the new *Port syntax.
17787 o Major features (bufferevents):
17788 - Tor can now optionally build with the "bufferevents" buffered IO
17789 backend provided by Libevent 2. To use this feature, make sure you
17790 have the latest possible version of Libevent, and pass the
17791 --enable-bufferevents flag to configure when building Tor from
17792 source. This feature will make our networking code more flexible,
17793 let us stack layers on each other, and let us use more efficient
17794 zero-copy transports where available.
17795 - Add experimental support for running on Windows with IOCP and no
17796 kernel-space socket buffers. This feature is controlled by a new
17797 "UserspaceIOCPBuffers" config option (off by default), which has
17798 no effect unless Tor has been built with bufferevents enabled,
17799 you're running on Windows, and you've set "DisableIOCP 0". In the
17800 long run, this may help solve or mitigate bug 98.
17802 o Major features (path selection):
17803 - The EntryNodes option can now include country codes like {de} or IP
17804 addresses or network masks. Previously we had disallowed these
17805 options because we didn't have an efficient way to keep the list up
17806 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
17809 o Major features (port forwarding):
17810 - Add support for automatic port mapping on the many home routers
17811 that support NAT-PMP or UPnP. To build the support code, you'll
17812 need to have the libnatpnp library and/or the libminiupnpc library,
17813 and you'll need to enable the feature specifically by passing
17814 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
17815 it on, use the new PortForwarding option.
17817 o Major features (logging):
17818 - Add a new 'Heartbeat' log message type to periodically log a message
17819 describing Tor's status at level Notice. This feature is meant for
17820 operators who log at notice, and want to make sure that their Tor
17821 server is still working. Implementation by George Kadianakis.
17822 - Make logging resolution configurable with a new LogTimeGranularity
17823 option, and change the default from 1 millisecond to 1 second.
17824 Implements enhancement 1668.
17826 o Major features (other):
17827 - New "DisableNetwork" config option to prevent Tor from launching any
17828 connections or accepting any connections except on a control port.
17829 Bundles and controllers can set this option before letting Tor talk
17830 to the rest of the network, for example to prevent any connections
17831 to a non-bridge address. Packages like Orbot can also use this
17832 option to instruct Tor to save power when the network is off.
17833 - Try to use system facilities for enumerating local interface
17834 addresses, before falling back to our old approach (which was
17835 binding a UDP socket, and calling getsockname() on it). That
17836 approach was scaring OS X users whose draconian firewall
17837 software warned about binding to UDP sockets regardless of
17838 whether packets were sent. Now we try to use getifaddrs(),
17839 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
17840 system supports. Resolves ticket 1827.
17841 - Add experimental support for a "defaults" torrc file to be parsed
17842 before the regular torrc. Torrc options override the defaults file's
17843 options in the same way that the command line overrides the torrc.
17844 The SAVECONF controller command saves only those options which
17845 differ between the current configuration and the defaults file. HUP
17846 reloads both files. Implements task 4552.
17848 o New directory authorities:
17849 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
17850 authority. Closes ticket 5749.
17852 o Security/privacy fixes:
17853 - Avoid read-from-freed-memory and double-free bugs that could occur
17854 when a DNS request fails while launching it. Fixes bug 6480;
17855 bugfix on 0.2.0.1-alpha.
17856 - Reject any attempt to extend to an internal address. Without
17857 this fix, a router could be used to probe addresses on an internal
17858 network to see whether they were accepting connections. Fixes bug
17859 6710; bugfix on 0.0.8pre1.
17860 - Close any connection that sends unrecognized junk before the TLS
17861 handshake. Solves an issue noted in bug 4369.
17862 - The advertised platform of a relay now includes only its operating
17863 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
17864 its service pack level (for Windows) or its CPU architecture
17865 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
17866 can insert an extra string in the platform line by setting the
17867 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
17868 - Disable TLS session tickets. OpenSSL's implementation was giving
17869 our TLS session keys the lifetime of our TLS context objects, when
17870 perfect forward secrecy would want us to discard anything that
17871 could decrypt a link connection as soon as the link connection
17872 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
17873 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
17874 - Tor tries to wipe potentially sensitive data after using it, so
17875 that if some subsequent security failure exposes Tor's memory,
17876 the damage will be limited. But we had a bug where the compiler
17877 was eliminating these wipe operations when it decided that the
17878 memory was no longer visible to a (correctly running) program,
17879 hence defeating our attempt at defense in depth. We fix that
17880 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
17881 is unlikely to optimize away. Future versions of Tor may use
17882 a less ridiculously heavy approach for this. Fixes bug 7352.
17883 Reported in an article by Andrey Karpov.
17885 o Major bugfixes (crashes and asserts):
17886 - Avoid a pair of double-free and use-after-mark bugs that can
17887 occur with certain timings in canceled and re-received DNS
17888 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
17889 - Fix a denial of service attack by which any directory authority
17890 could crash all the others, or by which a single v2 directory
17891 authority could crash everybody downloading v2 directory
17892 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
17893 - Fix an assert that directory authorities could trigger on sighup
17894 during some configuration state transitions. We now don't treat
17895 it as a fatal error when the new descriptor we just generated in
17896 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
17897 - Avoid segfault when starting up having run with an extremely old
17898 version of Tor and parsing its state file. Fixes bug 6801; bugfix
17901 o Major bugfixes (clients):
17902 - If we are unable to find any exit that supports our predicted ports,
17903 stop calling them predicted, so that we don't loop and build
17904 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
17905 which introduced predicted ports.
17906 - Check at each new consensus whether our entry guards were picked
17907 long enough ago that we should rotate them. Previously, we only
17908 did this check at startup, which could lead to us holding a guard
17909 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
17910 - When fetching a bridge descriptor from a bridge authority,
17911 always do so anonymously, whether we have been able to open
17912 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
17913 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
17914 but we'll need to wait for bug 6010 before it's actually usable.
17916 o Major bugfixes (directory voting):
17917 - Check more thoroughly to prevent a rogue authority from
17918 double-voting on any consensus directory parameter. Previously,
17919 authorities would crash in this case if the total number of
17920 votes for any parameter exceeded the number of active voters,
17921 but would let it pass otherwise. Partially fixes bug 5786; bugfix
17923 - When computing weight parameters, behave more robustly in the
17924 presence of a bad bwweightscale value. Previously, the authorities
17925 would crash if they agreed on a sufficiently broken weight_scale
17926 value; now, they use a reasonable default and carry on. Fixes the
17927 rest of bug 5786; bugfix on 0.2.2.17-alpha.
17928 - If authorities are unable to get a v2 consensus document from other
17929 directory authorities, they no longer fall back to fetching
17930 them from regular directory caches. Fixes bug 5635; bugfix on
17931 0.2.2.26-beta, where routers stopped downloading v2 consensus
17932 documents entirely.
17934 o Major bugfixes (relays):
17935 - Fix a bug handling SENDME cells on nonexistent streams that could
17936 result in bizarre window values. Report and patch contributed
17937 pseudonymously. Fixes part of bug 6271. This bug was introduced
17938 before the first Tor release, in svn commit r152.
17939 - Don't update the AccountingSoftLimitHitAt state file entry whenever
17940 tor gets started. This prevents a wrong average bandwidth
17941 estimate, which would cause relays to always start a new accounting
17942 interval at the earliest possible moment. Fixes bug 2003; bugfix
17943 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
17944 immensely in tracking this bug down.
17945 - Fix a possible crash bug when checking for deactivated circuits
17946 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
17947 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
17948 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
17949 connections. This change should allow busy exit relays to stop
17950 running out of available sockets as quickly. Fixes bug 4950;
17951 bugfix on 0.2.2.26-beta.
17953 o Major bugfixes (blocking resistance):
17954 - Bridges no longer include their address in NETINFO cells on outgoing
17955 OR connections, to allow them to blend in better with clients.
17956 Removes another avenue for enumerating bridges. Reported by
17957 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
17958 cells were introduced.
17959 - Warn the user when HTTPProxy, but no other proxy type, is
17960 configured. This can cause surprising behavior: it doesn't send
17961 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
17962 directory traffic only. Resolves ticket 4663.
17964 o Major bugfixes (hidden services):
17965 - Improve hidden service robustness: when an attempt to connect to
17966 a hidden service ends, be willing to refetch its hidden service
17967 descriptors from each of the HSDir relays responsible for them
17968 immediately. Previously, we would not consider refetching the
17969 service's descriptors from each HSDir for 15 minutes after the last
17970 fetch, which was inconvenient if the hidden service was not running
17971 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
17972 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
17973 They used to check that the timestamp was within 30 minutes
17974 of their system clock, so they could cap the size of their
17975 replay-detection cache, but that approach unnecessarily refused
17976 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
17977 the v3 intro-point protocol (the first one which sent a timestamp
17978 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
17979 - When one of a hidden service's introduction points appears to be
17980 unreachable, stop trying it. Previously, we would keep trying
17981 to build circuits to the introduction point until we lost the
17982 descriptor, usually because the user gave up and restarted Tor.
17983 Fixes part of bug 3825.
17985 o Changes to default torrc file:
17986 - Stop listing "socksport 9050" in torrc.sample. We open a socks
17987 port on 9050 by default anyway, so this should not change anything
17989 - Stop mentioning the deprecated *ListenAddress options in
17990 torrc.sample. Fixes bug 5438.
17991 - Document unit of bandwidth-related options in sample torrc.
17993 - Fix broken URLs in the sample torrc file, and tell readers about
17994 the OutboundBindAddress, ExitPolicyRejectPrivate, and
17995 PublishServerDescriptor options. Addresses bug 4652.
17997 o Minor features (directory authorities):
17998 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
17999 change when the authority is deciding whether to accept a newly
18000 uploaded descriptor. Implements ticket 6423.
18001 - Directory authorities are now a little more lenient at accepting
18002 older router descriptors, or newer router descriptors that don't
18003 make big changes. This should help ameliorate past and future
18004 issues where routers think they have uploaded valid descriptors,
18005 but the authorities don't think so. Fix for ticket 2479.
18006 - Authority operators can now vote for all relays in a given
18007 set of countries to be BadDir/BadExit/Invalid/Rejected.
18008 - Provide two consensus parameters (FastFlagMinThreshold and
18009 FastFlagMaxThreshold) to control the range of allowable bandwidths
18010 for the Fast directory flag. These allow authorities to run
18011 experiments on appropriate requirements for being a "Fast" node.
18012 The AuthDirFastGuarantee config value still applies. Implements
18015 o Minor features (bridges / bridge authorities):
18016 - Make bridge SSL certificates a bit more stealthy by using random
18017 serial numbers, in the same fashion as OpenSSL when generating
18018 self-signed certificates. Implements ticket 4584.
18019 - Tag a bridge's descriptor as "never to be sent unencrypted".
18020 This shouldn't matter, since bridges don't open non-anonymous
18021 connections to the bridge authority and don't allow unencrypted
18022 directory connections from clients, but we might as well make
18023 sure. Closes bug 5139.
18024 - The Bridge Authority now writes statistics on how many bridge
18025 descriptors it gave out in total, and how many unique descriptors
18026 it gave out. It also lists how often the most and least commonly
18027 fetched descriptors were given out, as well as the median and
18028 25th/75th percentile. Implements tickets 4200 and 4294.
18030 o Minor features (IPv6):
18031 - Make the code that clients use to detect an address change be
18032 IPv6-aware, so that it won't fill clients' logs with error
18033 messages when trying to get the IPv4 address of an IPv6
18034 connection. Implements ticket 5537.
18035 - Relays now understand an IPv6 address when they get one from a
18036 directory server. Resolves ticket 4875.
18038 o Minor features (hidden services):
18039 - Expire old or over-used hidden service introduction points.
18040 Required by fix for bug 3460.
18041 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
18042 public key replay-detection cache from 60 minutes to 5 minutes. This
18043 replay-detection cache is now used only to detect multiple
18044 INTRODUCE2 cells specifying the same rendezvous point, so we can
18045 avoid launching multiple simultaneous attempts to connect to it.
18046 - When a hidden service's introduction point times out, consider
18047 trying it again during the next attempt to connect to the
18048 HS. Previously, we would not try it again unless a newly fetched
18049 descriptor contained it. Required by fixes for bugs 1297 and 3825.
18051 o Minor features (relays):
18052 - Relays now include a reason for regenerating their descriptors
18053 in an HTTP header when uploading to the authorities. This will
18054 make it easier to debug descriptor-upload issues in the future.
18055 - Turn on directory request statistics by default and include them in
18056 extra-info descriptors. Don't break if we have no GeoIP database.
18057 - Replace files in stats/ rather than appending to them. Now that we
18058 include statistics in extra-info descriptors, it makes no sense to
18059 keep old statistics forever. Implements ticket 2930.
18060 - Relays that set "ConnDirectionStatistics 1" write statistics on the
18061 bidirectional use of connections to disk every 24 hours.
18062 - Add a GeoIP file digest to the extra-info descriptor. Implements
18065 o Minor features (new config options):
18066 - New config option "DynamicDHGroups" (disabled by default) provides
18067 each bridge with a unique prime DH modulus to be used during
18068 SSL handshakes. This option attempts to help against censors
18069 who might use the Apache DH modulus as a static identifier for
18070 bridges. Addresses ticket 4548.
18071 - New config option "DisableDebuggerAttachment" (on by default)
18072 to prevent basic debugging attachment attempts by other processes.
18073 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
18074 - Ordinarily, Tor does not count traffic from private addresses (like
18075 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
18076 There is now a new option, CountPrivateBandwidth, to disable this
18077 behavior. Patch from Daniel Cagara.
18079 o Minor features (different behavior for old config options):
18080 - Allow MapAddress directives to specify matches against super-domains,
18081 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
18082 Implements issue 933.
18083 - Don't disable the DirPort when we cannot exceed our AccountingMax
18084 limit during this interval because the effective bandwidthrate is
18085 low enough. This is useful in a situation where AccountMax is only
18086 used as an additional safeguard or to provide statistics.
18087 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
18088 implements ticket 3439.
18089 - When configuring a large set of nodes in EntryNodes, and there are
18090 enough of them listed as Guard so that we don't need to consider
18091 the non-guard entries, prefer the ones listed with the Guard flag.
18092 - If you set the NumCPUs option to 0, Tor will now try to detect how
18093 many CPUs you have. This is the new default behavior.
18094 - The NodeFamily option -- which let you declare that you want to
18095 consider nodes to be part of a family whether they list themselves
18096 that way or not -- now allows IP address ranges and country codes.
18098 o Minor features (new command-line config behavior):
18099 - Slightly change behavior of "list" options (that is, config
18100 options that can appear more than once) when they appear both in
18101 torrc and on the command line. Previously, the command-line options
18102 would be appended to the ones from torrc. Now, the command-line
18103 options override the torrc options entirely. This new behavior
18104 allows the user to override list options (like exit policies and
18105 ports to listen on) from the command line, rather than simply
18106 appending to the list.
18107 - You can get the old (appending) command-line behavior for "list"
18108 options by prefixing the option name with a "+".
18109 - You can remove all the values for a "list" option from the command
18110 line without adding any new ones by prefixing the option name
18113 o Minor features (controller, new events):
18114 - Extend the control protocol to report flags that control a circuit's
18115 path selection in CIRC events and in replies to 'GETINFO
18116 circuit-status'. Implements part of ticket 2411.
18117 - Extend the control protocol to report the hidden service address
18118 and current state of a hidden-service-related circuit in CIRC
18119 events and in replies to 'GETINFO circuit-status'. Implements part
18121 - Include the creation time of a circuit in CIRC and CIRC2
18122 control-port events and the list produced by the 'GETINFO
18123 circuit-status' control-port command.
18124 - Add a new CONF_CHANGED event so that controllers can be notified
18125 of any configuration changes made by other controllers, or by the
18126 user. Implements ticket 1692.
18127 - Add a new SIGNAL event to the controller interface so that
18128 controllers can be notified when Tor handles a signal. Resolves
18129 issue 1955. Patch by John Brooks.
18131 o Minor features (controller, new getinfo options):
18132 - Expose our view of whether we have gone dormant to the controller,
18133 via a new "GETINFO dormant" value. Torbutton and other controllers
18134 can use this to avoid doing periodic requests through Tor while
18135 it's dormant (bug 4718). Resolves ticket 5954.
18136 - Add a new GETINFO option to get total bytes read and written. Patch
18137 from pipe, revised by atagar. Resolves ticket 2345.
18138 - Implement new GETINFO controller fields to provide information about
18139 the Tor process's pid, euid, username, and resource limits.
18141 o Minor features (controller, other):
18142 - Allow controllers to request an event notification whenever a
18143 circuit is cannibalized or its purpose is changed. Implements
18144 part of ticket 3457.
18145 - Use absolute path names when reporting the torrc filename in the
18146 control protocol, so a controller can more easily find the torrc
18147 file. Resolves bug 1101.
18148 - When reporting the path to the cookie file to the controller,
18149 give an absolute path. Resolves ticket 4881.
18151 o Minor features (log messages):
18152 - Add more information to a log statement that might help track down
18153 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
18154 non-IP address" messages (or any Bug messages, for that matter!),
18155 please let us know about it.
18156 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
18157 EntryNodes will have no effect. Resolves issue 2571.
18158 - Try to make the introductory warning message that Tor prints on
18159 startup more useful for actually finding help and information.
18160 Resolves ticket 2474.
18161 - When the system call to create a listener socket fails, log the
18162 error message explaining why. This may help diagnose bug 4027.
18164 o Minor features (other):
18165 - When we fail to initialize Libevent, retry with IOCP disabled so we
18166 don't need to turn on multi-threading support in Libevent, which in
18167 turn requires a working socketpair(). This is a workaround for bug
18168 4457, which affects Libevent versions from 2.0.1-alpha through
18170 - When starting as root and then changing our UID via the User
18171 control option, and we have a ControlSocket configured, make sure
18172 that the ControlSocket is owned by the same account that Tor will
18173 run under. Implements ticket 3421; fix by Jérémy Bobbio.
18174 - Accept attempts to include a password authenticator in the
18175 handshake, as supported by SOCKS5. This handles SOCKS clients that
18176 don't know how to omit a password when authenticating. Resolves
18178 - Check for and recover from inconsistency in the microdescriptor
18179 cache. This will make it harder for us to accidentally free a
18180 microdescriptor without removing it from the appropriate data
18181 structures. Fixes issue 3135; issue noted by "wanoskarnet".
18182 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
18184 o Minor bugfixes (code security):
18185 - Prevent a null-pointer dereference when receiving a data cell
18186 for a nonexistent stream when the circuit in question has an
18187 empty deliver window. We don't believe this is triggerable,
18188 since we don't currently allow deliver windows to become empty,
18189 but the logic is tricky enough that it's better to make the code
18190 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
18191 - Fix a (harmless) integer overflow in cell statistics reported by
18192 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
18193 - Fix our implementation of crypto_random_hostname() so it can't
18194 overflow on ridiculously large inputs. (No Tor version has ever
18195 provided this kind of bad inputs, but let's be correct in depth.)
18196 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
18197 - Add a (probably redundant) memory clear between iterations of
18198 the router status voting loop, to prevent future coding errors
18199 where data might leak between iterations of the loop. Resolves
18202 o Minor bugfixes (wrapper functions):
18203 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
18204 utility function used in the control-port code). This shouldn't
18205 ever happen unless Tor is completely out of memory, but if it did
18206 happen and Tor somehow recovered from it, Tor could have sent a log
18207 message to a control port in the middle of a reply to a controller
18208 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
18209 - Fix some (not actually triggerable) buffer size checks in usage of
18210 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
18212 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
18213 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
18214 - Enforce correct return behavior of tor_vsscanf() when the '%%'
18215 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
18216 - Make our replacement implementation of strtok_r() compatible with
18217 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
18218 bugfix on 0.2.2.1-alpha.
18219 - Find more places in the code that should have been testing for
18220 invalid sockets using the SOCKET_OK macro. Required for a fix
18221 for bug 4533. Bugfix on 0.2.2.28-beta.
18223 o Minor bugfixes (code correctness):
18224 - Check return value of fputs() when writing authority certificate
18225 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
18226 - When building Tor on Windows with -DUNICODE (not default), ensure
18227 that error messages, filenames, and DNS server names are always
18228 NUL-terminated when we convert them to a single-byte encoding.
18229 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
18230 - Fix a memory leak when trying to launch a DNS request when the
18231 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
18233 - Correct file sizes when reading binary files on Cygwin, to avoid
18234 a bug where Tor would fail to read its state file. Fixes bug 6844;
18235 bugfix on 0.1.2.7-alpha.
18236 - Make sure to set *socket_error in all error cases in
18237 connection_connect(), so it can't produce a warning about
18238 errno being zero from errno_to_orconn_end_reason(). Bugfix on
18239 0.2.1.1-alpha; resolves ticket 6028.
18240 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
18241 bug 4532; found by "troll_un".
18243 o Minor bugfixes (clients):
18244 - Allow one-hop directory-fetching circuits the full "circuit build
18245 timeout" period, rather than just half of it, before failing them
18246 and marking the relay down. This fix should help reduce cases where
18247 clients declare relays (or worse, bridges) unreachable because
18248 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
18249 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
18251 - Ensure we don't cannibalize circuits that are longer than three hops
18252 already, so we don't end up making circuits with 5 or more
18253 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
18254 0.1.0.1-rc which introduced cannibalization.
18256 o Minor bugfixes (relays):
18257 - Don't publish a new relay descriptor when we reload our onion key,
18258 unless the onion key has actually changed. Fixes bug 3263 and
18259 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
18260 - When relays refuse a "create" cell because their queue of pending
18261 create cells is too big (typically because their cpu can't keep up
18262 with the arrival rate), send back reason "resource limit" rather
18263 than reason "internal", so network measurement scripts can get a
18264 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
18265 - Exit nodes don't need to fetch certificates for authorities that
18266 they don't recognize; only directory authorities, bridges,
18267 and caches need to do that. Fixes part of bug 2297; bugfix on
18270 o Minor bugfixes (directory authority / mirrors):
18271 - Avoid O(n^2) performance characteristics when parsing a large
18272 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
18273 - Authorities no longer include any router in their microdescriptor
18274 consensuses for which they couldn't generate or agree on a
18275 microdescriptor. Fixes the second piece of bug 6404; fix on
18277 - When checking for requested signatures on the latest consensus
18278 before serving it to a client, make sure to check the right
18279 consensus flavor. Bugfix on 0.2.2.6-alpha.
18280 - Fix an edge case where TestingTorNetwork is set but the authorities
18281 and relays all have an uptime of zero, so the private Tor network
18282 could briefly lack support for hidden services. Fixes bug 3886;
18283 bugfix on 0.2.2.18-alpha.
18284 - Directory caches no longer refuse to clean out descriptors because
18285 of missing v2 networkstatus documents, unless they're configured
18286 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
18287 0.2.2.26-beta. Patch by Daniel Bryg.
18288 - Don't serve or accept v2 hidden service descriptors over a relay's
18289 DirPort. It's never correct to do so, and disabling it might
18290 make it more annoying to exploit any bugs that turn up in the
18291 descriptor-parsing code. Fixes bug 7149.
18293 o Minor bugfixes (hidden services, client-side):
18294 - Assert that hidden-service-related operations are not performed
18295 using single-hop circuits. Previously, Tor would assert that
18296 client-side streams are not attached to single-hop circuits,
18297 but not that other sensitive operations on the client and service
18298 side are not performed using single-hop circuits. Fixes bug 3332;
18300 - Avoid undefined behavior when parsing the list of supported
18301 rendezvous/introduction protocols in a hidden service descriptor.
18302 Previously, Tor would have confused (as-yet-unused) protocol version
18303 numbers greater than 32 with lower ones on many platforms. Fixes
18304 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
18305 - Don't close hidden service client circuits which have almost
18306 finished connecting to their destination when they reach
18307 the normal circuit-build timeout. Previously, we would close
18308 introduction circuits which are waiting for an acknowledgement
18309 from the introduction point, and rendezvous circuits which have
18310 been specified in an INTRODUCE1 cell sent to a hidden service,
18311 after the normal CBT. Now, we mark them as 'timed out', and launch
18312 another rendezvous attempt in parallel. This behavior change can
18313 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
18314 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
18316 o Minor bugfixes (hidden services, service-side):
18317 - Don't close hidden-service-side rendezvous circuits when they
18318 reach the normal circuit-build timeout. This behavior change can
18319 be disabled using the new
18320 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
18321 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
18322 - Don't launch more than 10 service-side introduction-point circuits
18323 for a hidden service in five minutes. Previously, we would consider
18324 launching more introduction-point circuits if at least one second
18325 had passed without any introduction-point circuits failing. Fixes
18326 bug 4607; bugfix on 0.0.7pre1.
18328 o Minor bugfixes (config option behavior):
18329 - If the user tries to set MyFamily on a bridge, refuse to
18330 do so, and warn about the security implications. Fixes bug 4657;
18331 bugfix on 0.2.0.3-alpha.
18332 - The "--quiet" and "--hush" options now apply not only to Tor's
18333 behavior before logs are configured, but also to Tor's behavior in
18334 the absence of configured logs. Fixes bug 3550; bugfix on
18336 - Change the AllowDotExit rules so they should actually work.
18337 We now enforce AllowDotExit only immediately after receiving an
18338 address via SOCKS or DNSPort: other sources are free to provide
18339 .exit addresses after the resolution occurs. Fixes bug 3940;
18340 bugfix on 0.2.2.1-alpha.
18341 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
18342 don't depend on the consensus parameters or compute adaptive
18343 timeouts when it is disabled. Fixes bug 5049; bugfix on
18345 - After we pick a directory mirror, we would refuse to use it if
18346 it's in our ExcludeExitNodes list, resulting in mysterious failures
18347 to bootstrap for people who just wanted to avoid exiting from
18348 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
18349 - When told to add a bridge with the same digest as a preexisting
18350 bridge but a different addr:port, change the addr:port as
18351 requested. Previously we would not notice the change. Fixes half
18352 of bug 5603; fix on 0.2.2.26-beta.
18354 o Minor bugfixes (controller):
18355 - Allow manual 'authenticate' commands to the controller interface
18356 from netcat (nc) as well as telnet. We were rejecting them because
18357 they didn't come with the expected whitespace at the end of the
18358 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
18359 - Report a real bootstrap problem to the controller on router
18360 identity mismatch. Previously we just said "foo", which probably
18361 made a lot of sense at the time. Fixes bug 4169; bugfix on
18363 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
18364 option is set to 0 (which Vidalia version 0.2.16 now does when
18365 a SAVECONF attempt fails), perform other actions that SIGHUP
18366 usually causes (like reopening the logs). Fixes bug 5095; bugfix
18368 - Correctly handle checking the permissions on the parent
18369 directory of a control socket in the root directory. Bug found
18370 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
18372 - End AUTHCHALLENGE error messages (in the control protocol) with
18373 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
18375 o Minor bugfixes (network reading/writing):
18376 - Disable writing on marked-for-close connections when they are
18377 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
18378 bug 5263; bugfix on 0.0.2pre13, where we first added a special
18379 case for flushing marked connections.
18380 - Make sure that there are no unhandled pending TLS errors before
18381 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
18382 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
18383 Bugfix on 0.1.0.5-rc; fixes bug 4528.
18384 - Detect SSL handshake even when the initial attempt to write the
18385 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
18386 - If the client fails to set a reasonable set of ciphersuites
18387 during its v2 handshake renegotiation, allow the renegotiation to
18388 continue nevertheless (i.e. send all the required certificates).
18389 Fixes bug 4591; bugfix on 0.2.0.20-rc.
18391 o Minor bugfixes (other):
18392 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
18393 resource exhaustion, so that clients can adjust their load to
18394 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
18395 started using END_STREAM_REASON_RESOURCELIMIT.
18396 - Don't check for whether the address we're using for outbound
18397 connections has changed until after the outbound connection has
18398 completed. On Windows, getsockname() doesn't succeed until the
18399 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
18400 - Don't hold a Windows file handle open for every file mapping;
18401 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
18403 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
18404 bugfix on 0.2.1.10-alpha.
18405 - If we fail to write a microdescriptor to the disk cache, do not
18406 continue replacing the old microdescriptor file. Fixes bug 2954;
18407 bugfix on 0.2.2.6-alpha.
18409 o Minor bugfixes (log messages, path selection):
18410 - Downgrade "set buildtimeout to low value" messages to "info"
18411 severity; they were never an actual problem, there was never
18412 anything reasonable to do about them, and they tended to spam logs
18413 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
18414 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
18415 more information to it, so that we can track it down in case it
18416 returns again. Mitigates bug 5235.
18417 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
18418 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
18419 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
18420 - Issue a log message if a guard completes less than 40% of your
18421 circuits. Threshold is configurable by torrc option
18422 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
18423 additional, off-by-default code to disable guards which fail too
18424 many circuits. Addresses ticket 5458.
18426 o Minor bugfixes (log messages, client):
18427 - Downgrade "Got a certificate, but we already have it" log messages
18428 from warning to info, except when we're a dirauth. Fixes bug 5238;
18429 bugfix on 0.2.1.7-alpha.
18430 - Fix the log message describing how we work around discovering
18431 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
18432 4837; bugfix on 0.2.2.9-alpha.
18433 - When logging about a disallowed .exit name, do not also call it
18434 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
18435 - Fix a log message suggesting that people contact a non-existent
18436 email address. Fixes bug 3448.
18437 - Rephrase the log message emitted if the TestSocks check is
18438 successful. Patch from Fabian Keil; fixes bug 4094.
18439 - Log (at debug level) whenever a circuit's purpose is changed.
18440 - Log SSL state transitions at log level DEBUG, log domain
18441 HANDSHAKE. This can be useful for debugging censorship events.
18442 Implements ticket 3264.
18443 - We now log which torrc file we're using on startup. Implements
18445 - Rate-limit log messages when asked to connect anonymously to
18446 a private address. When these hit, they tended to hit fast and
18447 often. Also, don't bother trying to connect to addresses that we
18448 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
18449 reply makes us think we have been lied to, even when the address the
18450 client tried to connect to was "localhost." Resolves ticket 2822.
18452 o Minor bugfixes (log messages, non-client):
18453 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
18454 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
18455 - Don't log that we have "decided to publish new relay descriptor"
18456 unless we are actually publishing a descriptor. Fixes bug 3942;
18457 bugfix on 0.2.2.28-beta.
18458 - Log which authority we're missing votes from when we go to fetch
18459 them from the other auths.
18460 - Replace "Sending publish request" log messages with "Launching
18461 upload", so that they no longer confusingly imply that we're
18462 sending something to a directory we might not even be connected
18463 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
18464 - Warn when Tor is configured to use accounting in a way that can
18465 link a hidden service to some other hidden service or public
18466 address. Resolves ticket 6490.
18467 - Fix a minor formatting issue in one of tor-gencert's error messages.
18471 - Update to the latest version of the tinytest unit testing framework.
18472 This includes a couple of bugfixes that can be relevant for
18473 running forked unit tests on Windows, and removes all reserved
18475 - Avoid a false positive in the util/threads unit test by increasing
18476 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
18477 - Make it possible to set the TestingTorNetwork configuration
18478 option using AlternateDirAuthority and AlternateBridgeAuthority
18479 as an alternative to setting DirServer. Addresses ticket 6377.
18480 - Add a unit test for the environment_variable_names_equal() function.
18481 - A wide variety of new unit tests by Esteban Manchado Velázquez.
18482 - Numerous new unit tests for functions in util.c and address.c by
18484 - The long-disabled benchmark tests are now split into their own
18485 ./src/test/bench binary.
18486 - The benchmark tests can now use more accurate timers than
18487 gettimeofday() when such timers are available.
18488 - Use tt_assert(), not tor_assert(), for checking for test failures.
18489 This makes the unit tests more able to go on in the event that
18492 o Build improvements:
18493 - Use the dead_strip option when building Tor on OS X. This reduces
18494 binary size by almost 19% when linking openssl and libevent
18495 statically, which we do for Tor Browser Bundle.
18496 - Provide a better error message about possible OSX Asciidoc failure
18497 reasons. Fixes bug 6436.
18498 - Detect attempts to build Tor on (as yet hypothetical) versions
18499 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
18500 fix for bug 4533. Bugfix on 0.2.2.28-beta.
18501 - On Windows, we now define the _WIN32_WINNT macros only if they
18502 are not already defined. This lets the person building Tor decide,
18503 if they want, to require a later version of Windows.
18504 - Our autogen.sh script now uses autoreconf to launch autoconf,
18505 automake, and so on. This is more robust against some of the failure
18506 modes associated with running the autotools pieces on their own.
18507 - Running "make version" now displays the version of Tor that
18508 we're about to build. Idea from katmagic; resolves issue 4400.
18509 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
18510 on 0.2.2.4-alpha; fixes bug 3427.
18511 - New --enable-static-tor configure option for building Tor as
18512 statically as possible. Idea, general hackery and thoughts from
18513 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
18515 - Limited, experimental support for building with nmake and MSVC.
18517 o Build requirements:
18518 - Building Tor with bufferevent support now requires Libevent
18519 2.0.13-stable or later. Previous versions of Libevent had bugs in
18520 SSL-related bufferevents and related issues that would make Tor
18521 work badly with bufferevents. Requiring 2.0.13-stable also allows
18522 Tor with bufferevents to take advantage of Libevent APIs
18523 introduced after 2.0.8-rc.
18524 - Our build system requires automake 1.6 or later to create the
18525 Makefile.in files. Previously, you could have used 1.4.
18526 This only affects developers and people building Tor from git;
18527 people who build Tor from the source distribution without changing
18528 the Makefile.am files should be fine.
18529 - Detect when we try to build on a platform that doesn't define
18530 AF_UNSPEC to 0. We don't work there, so refuse to compile.
18532 o Build fixes (compile/link):
18533 - Format more doubles with %f, not %lf. Patch from grarpamp to make
18534 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
18536 - When building with --enable-static-tor on OpenBSD, do not
18537 erroneously attempt to link -lrt. Fixes bug 5103.
18538 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
18539 that IPv6 stuff will compile on MSVC, and compilation issues
18540 will be easier to track down. Fixes bug 5861.
18541 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
18542 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
18543 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
18544 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
18546 o Build fixes (other):
18547 - Use the _WIN32 macro throughout our code to detect Windows.
18548 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
18550 - Properly handle the case where the build-tree is not the same
18551 as the source tree when generating src/common/common_sha1.i,
18552 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
18553 bugfix on 0.2.0.1-alpha.
18554 - During configure, search for library containing cos function as
18555 libm lives in libcore on some platforms (BeOS/Haiku). Linking
18556 against libm was hard-coded before. Fixes the first part of bug
18557 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
18559 - Prevent a false positive from the check-spaces script, by disabling
18560 the "whitespace between function name and (" check for functions
18563 o Packaging (RPM) changes:
18564 - Update our default RPM spec files to work with mock and rpmbuild
18565 on RHEL/Fedora. They have an updated set of dependencies and
18566 conflicts, a fix for an ancient typo when creating the "_tor"
18567 user, and better instructions. Thanks to Ondrej Mikle for the
18568 patch series. Fixes bug 6043.
18569 - On OpenSUSE, create the /var/run/tor directory on startup if it
18570 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
18572 o Code refactoring (safety):
18573 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
18574 10 lines. Also, don't nest them. Doing so in the past has
18575 led to hard-to-debug code. The new style is to use the
18576 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
18577 - Use macros to indicate OpenSSL versions, so we don't need to worry
18578 about accidental hexadecimal bit shifts.
18579 - Use tor_sscanf() in place of scanf() in more places through the
18580 code. This makes us a little more locale-independent, and
18581 should help shut up code-analysis tools that can't tell
18582 a safe sscanf string from a dangerous one.
18583 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
18584 - Use the smartlist_add_asprintf() alias more consistently.
18586 o Code refactoring (consolidate):
18587 - A major revision to our internal node-selecting and listing logic.
18588 Tor already had at least two major ways to look at the question of
18589 "which Tor servers do we know about": a list of router descriptors,
18590 and a list of entries in the current consensus. With
18591 microdescriptors, we're adding a third. Having so many systems
18592 without an abstraction layer over them was hurting the codebase.
18593 Now, we have a new "node_t" abstraction that presents a consistent
18594 interface to a client's view of a Tor node, and holds (nearly) all
18595 of the mutable state formerly in routerinfo_t and routerstatus_t.
18596 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
18597 Libevent's notion of cached time when possible.
18598 - Remove duplicate code for invoking getrlimit() from control.c.
18599 - Use OpenSSL's built-in SSL_state_string_long() instead of our
18600 own homebrewed ssl_state_to_string() replacement. Patch from
18601 Emile Snyder. Fixes bug 4653.
18602 - Change the symmetric cipher interface so that creating and
18603 initializing a stream cipher are no longer separate functions.
18605 o Code refactoring (separate):
18606 - Make a new "entry connection" struct as an internal subtype of "edge
18607 connection", to simplify the code and make exit connections smaller.
18608 - Split connection_about_to_close() into separate functions for each
18610 - Rewrite the listener-selection logic so that parsing which ports
18611 we want to listen on is now separate from binding to the ports
18614 o Code refactoring (name changes):
18615 - Rename a handful of old identifiers, mostly related to crypto
18616 structures and crypto functions. By convention, our "create an
18617 object" functions are called "type_new()", our "free an object"
18618 functions are called "type_free()", and our types indicate that
18619 they are types only with a final "_t". But a handful of older
18620 types and functions broke these rules, with function names like
18621 "type_create" or "subsystem_op_type", or with type names like
18623 - Rename Tor functions that turn strings into addresses, so that
18624 "parse" indicates that no hostname resolution occurs, and
18625 "lookup" indicates that hostname resolution may occur. This
18626 should help prevent mistakes in the future. Fixes bug 3512.
18627 - Use the name "CERTS" consistently to refer to the new cell type;
18628 we were calling it CERT in some places and CERTS in others.
18629 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
18630 invalid value, rather than just -1.
18631 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
18632 can pick them up when the tests aren't disabled. Bugfix on
18633 0.2.2.4-alpha which introduced tinytest.
18635 o Code refactoring (other):
18636 - Defensively refactor rend_mid_rendezvous() so that protocol
18637 violations and length checks happen in the beginning. Fixes
18639 - Remove the pure attribute from all functions that used it
18640 previously. In many cases we assigned it incorrectly, because the
18641 functions might assert or call impure functions, and we don't have
18642 evidence that keeping the pure attribute is worthwhile. Implements
18643 changes suggested in ticket 4421.
18644 - Move the replay-detection cache for the RSA-encrypted parts of
18645 INTRODUCE2 cells to the introduction point data structures.
18646 Previously, we would use one replay-detection cache per hidden
18647 service. Required by fix for bug 3460.
18648 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
18649 no longer link against Libevent: they never used it, but
18650 our library structure used to force them to link it.
18652 o Removed features and files:
18653 - Remove all internal support for unpadded RSA. We never used it, and
18654 it would be a bad idea to start.
18655 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
18657 - Remove some redundant #include directives throughout the code.
18658 Patch from Andrea Gelmini.
18659 - Remove some old code to remember statistics about which descriptors
18660 we've served as a directory mirror. The feature wasn't used and
18661 is outdated now that microdescriptors are around.
18662 - Remove some old code to work around even older versions of Tor that
18663 used forked processes to handle DNS requests. Such versions of Tor
18664 are no longer in use as relays.
18665 - The "torify" script no longer supports the "tsocks" socksifier
18666 tool, since tsocks doesn't support DNS and UDP right for Tor.
18667 Everyone should be using torsocks instead. Fixes bugs 3530 and
18668 5180. Based on a patch by "ugh".
18669 - Remove the torrc.bridge file: we don't use it for anything, and
18670 it had become badly desynchronized from torrc.sample. Resolves
18674 - Begin a doc/state-contents.txt file to explain the contents of
18675 the Tor state file. Fixes bug 2987.
18676 - Clarify the documentation for the Alternate*Authority options.
18678 - Document the --defaults-torrc option, and the new semantics for
18679 overriding, extending, and clearing lists of options. Closes
18681 - Add missing man page documentation for consensus and microdesc
18682 files. Resolves ticket 6732.
18683 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
18685 o Documentation fixes:
18686 - Improve the manual's documentation for the NT Service command-line
18687 options. Addresses ticket 3964.
18688 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
18689 - Document the changes to the ORPort and DirPort options, and the
18690 fact that {OR/Dir}ListenAddress is now unnecessary (and
18691 therefore deprecated). Resolves ticket 5597.
18692 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
18693 - Clarify that hidden services are TCP only. Fixes bug 6024.
18696 Changes in version 0.2.2.39 - 2012-09-11
18697 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
18701 - Fix an assertion failure in tor_timegm() that could be triggered
18702 by a badly formatted directory object. Bug found by fuzzing with
18703 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
18704 - Do not crash when comparing an address with port value 0 to an
18705 address policy. This bug could have been used to cause a remote
18706 assertion failure by or against directory authorities, or to
18707 allow some applications to crash clients. Fixes bug 6690; bugfix
18711 Changes in version 0.2.2.38 - 2012-08-12
18712 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
18713 attack that could in theory leak path information.
18716 - Avoid an uninitialized memory read when reading a vote or consensus
18717 document that has an unrecognized flavor name. This read could
18718 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
18719 - Try to leak less information about what relays a client is
18720 choosing to a side-channel attacker. Previously, a Tor client would
18721 stop iterating through the list of available relays as soon as it
18722 had chosen one, thus finishing a little earlier when it picked
18723 a router earlier in the list. If an attacker can recover this
18724 timing information (nontrivial but not proven to be impossible),
18725 they could learn some coarse-grained information about which relays
18726 a client was picking (middle nodes in particular are likelier to
18727 be affected than exits). The timing attack might be mitigated by
18728 other factors (see bug 6537 for some discussion), but it's best
18729 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
18732 Changes in version 0.2.2.37 - 2012-06-06
18733 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
18734 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
18738 - Work around a bug in OpenSSL that broke renegotiation with TLS
18739 1.1 and TLS 1.2. Without this workaround, all attempts to speak
18740 the v2 Tor connection protocol when both sides were using OpenSSL
18741 1.0.1 would fail. Resolves ticket 6033.
18742 - When waiting for a client to renegotiate, don't allow it to add
18743 any bytes to the input buffer. This fixes a potential DoS issue.
18744 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
18745 - Fix an edge case where if we fetch or publish a hidden service
18746 descriptor, we might build a 4-hop circuit and then use that circuit
18747 for exiting afterwards -- even if the new last hop doesn't obey our
18748 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
18751 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
18752 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
18755 - Tell GCC and Clang to check for any errors in format strings passed
18756 to the tor_v*(print|scan)f functions.
18759 Changes in version 0.2.2.36 - 2012-05-24
18760 Tor 0.2.2.36 updates the addresses for two of the eight directory
18761 authorities, fixes some potential anonymity and security issues,
18762 and fixes several crash bugs.
18764 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
18765 known flaws, and nobody should be using them. You should upgrade. If
18766 you're using a Linux or BSD and its packages are obsolete, stop using
18767 those packages and upgrade anyway.
18769 o Directory authority changes:
18770 - Change IP address for maatuska (v3 directory authority).
18771 - Change IP address for ides (v3 directory authority), and rename
18775 - When building or running with any version of OpenSSL earlier
18776 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
18777 versions have a bug (CVE-2011-4576) in which their block cipher
18778 padding includes uninitialized data, potentially leaking sensitive
18779 information to any peer with whom they make a SSLv3 connection. Tor
18780 does not use SSL v3 by default, but a hostile client or server
18781 could force an SSLv3 connection in order to gain information that
18782 they shouldn't have been able to get. The best solution here is to
18783 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
18784 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
18785 to make sure that the bug can't happen.
18786 - Never use a bridge or a controller-supplied node as an exit, even
18787 if its exit policy allows it. Found by wanoskarnet. Fixes bug
18788 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
18789 and 0.2.0.3-alpha (for bridge-purpose descriptors).
18790 - Only build circuits if we have a sufficient threshold of the total
18791 descriptors that are marked in the consensus with the "Exit"
18792 flag. This mitigates an attack proposed by wanoskarnet, in which
18793 all of a client's bridges collude to restrict the exit nodes that
18794 the client knows about. Fixes bug 5343.
18795 - Provide controllers with a safer way to implement the cookie
18796 authentication mechanism. With the old method, if another locally
18797 running program could convince a controller that it was the Tor
18798 process, then that program could trick the controller into telling
18799 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
18800 authentication method uses a challenge-response approach to prevent
18801 this attack. Fixes bug 5185; implements proposal 193.
18804 - Avoid logging uninitialized data when unable to decode a hidden
18805 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
18806 - Avoid a client-side assertion failure when receiving an INTRODUCE2
18807 cell on a general purpose circuit. Fixes bug 5644; bugfix on
18809 - Fix builds when the path to sed, openssl, or sha1sum contains
18810 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
18812 - Correct our replacements for the timeradd() and timersub() functions
18813 on platforms that lack them (for example, Windows). The timersub()
18814 function is used when expiring circuits, while timeradd() is
18815 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
18816 bugfix on 0.2.2.24-alpha.
18817 - Fix the SOCKET_OK test that we use to tell when socket
18818 creation fails so that it works on Win64. Fixes part of bug 4533;
18819 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
18822 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
18823 Fixes bug 5346; bugfix on 0.0.8pre3.
18824 - Make our number-parsing functions always treat too-large values
18825 as an error, even when those values exceed the width of the
18826 underlying type. Previously, if the caller provided these
18827 functions with minima or maxima set to the extreme values of the
18828 underlying integer type, these functions would return those
18829 values on overflow rather than treating overflow as an error.
18830 Fixes part of bug 5786; bugfix on 0.0.9.
18831 - Older Linux kernels erroneously respond to strange nmap behavior
18832 by having accept() return successfully with a zero-length
18833 socket. When this happens, just close the connection. Previously,
18834 we would try harder to learn the remote address: but there was
18835 no such remote address to learn, and our method for trying to
18836 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
18837 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
18838 - Correct parsing of certain date types in parse_http_time().
18839 Without this patch, If-Modified-Since would behave
18840 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
18841 Esteban Manchado Velázques.
18842 - Change the BridgePassword feature (part of the "bridge community"
18843 design, which is not yet implemented) to use a time-independent
18844 comparison. The old behavior might have allowed an adversary
18845 to use timing to guess the BridgePassword value. Fixes bug 5543;
18846 bugfix on 0.2.0.14-alpha.
18847 - Detect and reject certain misformed escape sequences in
18848 configuration values. Previously, these values would cause us
18849 to crash if received in a torrc file or over an authenticated
18850 control port. Bug found by Esteban Manchado Velázquez, and
18851 independently by Robert Connolly from Matta Consulting who further
18852 noted that it allows a post-authentication heap overflow. Patch
18853 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
18854 bugfix on 0.2.0.16-alpha.
18855 - Fix a compile warning when using the --enable-openbsd-malloc
18856 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
18857 - During configure, detect when we're building with clang version
18858 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
18859 CFLAGS. clang doesn't support them yet.
18860 - When sending an HTTP/1.1 proxy request, include a Host header.
18861 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
18862 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
18863 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
18864 - If we hit the error case where routerlist_insert() replaces an
18865 existing (old) server descriptor, make sure to remove that
18866 server descriptor from the old_routers list. Fix related to bug
18867 1776. Bugfix on 0.2.2.18-alpha.
18869 o Minor bugfixes (documentation and log messages):
18870 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
18871 Fixes bug 4856; bugfix on Tor 0.0.6.
18872 - Update "ClientOnly" man page entry to explain that there isn't
18873 really any point to messing with it. Resolves ticket 5005.
18874 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
18875 directory authority option (introduced in Tor 0.2.2.34).
18876 - Downgrade the "We're missing a certificate" message from notice
18877 to info: people kept mistaking it for a real problem, whereas it
18878 is seldom the problem even when we are failing to bootstrap. Fixes
18879 bug 5067; bugfix on 0.2.0.10-alpha.
18880 - Correctly spell "connect" in a log message on failure to create a
18881 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
18882 - Clarify the behavior of MaxCircuitDirtiness with hidden service
18883 circuits. Fixes issue 5259.
18886 - Directory authorities now reject versions of Tor older than
18887 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
18888 inclusive. These versions accounted for only a small fraction of
18889 the Tor network, and have numerous known security issues. Resolves
18891 - Update to the May 1 2012 Maxmind GeoLite Country database.
18894 - When sending or relaying a RELAY_EARLY cell, we used to convert
18895 it to a RELAY cell if the connection was using the v1 link
18896 protocol. This was a workaround for older versions of Tor, which
18897 didn't handle RELAY_EARLY cells properly. Now that all supported
18898 versions can handle RELAY_EARLY cells, and now that we're enforcing
18899 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
18900 remove this workaround. Addresses bug 4786.
18903 Changes in version 0.2.2.35 - 2011-12-16
18904 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
18905 buffers code. Absolutely everybody should upgrade.
18907 The bug relied on an incorrect calculation when making data continuous
18908 in one of our IO buffers, if the first chunk of the buffer was
18909 misaligned by just the wrong amount. The miscalculation would allow an
18910 attacker to overflow a piece of heap-allocated memory. To mount this
18911 attack, the attacker would need to either open a SOCKS connection to
18912 Tor's SocksPort (usually restricted to localhost), or target a Tor
18913 instance configured to make its connections through a SOCKS proxy
18914 (which Tor does not do by default).
18916 Good security practice requires that all heap-overflow bugs should be
18917 presumed to be exploitable until proven otherwise, so we are treating
18918 this as a potential code execution attack. Please upgrade immediately!
18919 This bug does not affect bufferevents-based builds of Tor. Special
18920 thanks to "Vektor" for reporting this issue to us!
18922 Tor 0.2.2.35 also fixes several bugs in previous versions, including
18923 crash bugs for unusual configurations, and a long-term bug that
18924 would prevent Tor from starting on Windows machines with draconian
18927 With this release, we remind everyone that 0.2.0.x has reached its
18928 formal end-of-life. Those Tor versions have many known flaws, and
18929 nobody should be using them. You should upgrade -- ideally to the
18930 0.2.2.x series. If you're using a Linux or BSD and its packages are
18931 obsolete, stop using those packages and upgrade anyway.
18933 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
18934 longer receive support after some time in early 2012.
18937 - Fix a heap overflow bug that could occur when trying to pull
18938 data into the first chunk of a buffer, when that chunk had
18939 already had some data drained from it. Fixes CVE-2011-2778;
18940 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
18941 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
18942 that it doesn't attempt to allocate a socketpair. This could cause
18943 some problems on Windows systems with overzealous firewalls. Fix for
18944 bug 4457; workaround for Libevent versions 2.0.1-alpha through
18946 - If we mark an OR connection for close based on a cell we process,
18947 don't process any further cells on it. We already avoid further
18948 reads on marked-for-close connections, but now we also discard the
18949 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
18950 which was the first version where we might mark a connection for
18951 close based on processing a cell on it.
18952 - Correctly sanity-check that we don't underflow on a memory
18953 allocation (and then assert) for hidden service introduction
18954 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
18955 bugfix on 0.2.1.5-alpha.
18956 - Fix a memory leak when we check whether a hidden service
18957 descriptor has any usable introduction points left. Fixes bug
18958 4424. Bugfix on 0.2.2.25-alpha.
18959 - Don't crash when we're running as a relay and don't have a GeoIP
18960 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
18961 we've had in the 0.2.3.x branch already.
18962 - When running as a client, do not print a misleading (and plain
18963 wrong) log message that we're collecting "directory request"
18964 statistics: clients don't collect statistics. Also don't create a
18965 useless (because empty) stats file in the stats/ directory. Fixes
18966 bug 4353; bugfix on 0.2.2.34.
18969 - Detect failure to initialize Libevent. This fix provides better
18970 detection for future instances of bug 4457.
18971 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
18972 function. This was eating up hideously large amounts of time on some
18973 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
18974 - Resolve an integer overflow bug in smartlist_ensure_capacity().
18975 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
18977 - Don't warn about unused log_mutex in log.c when building with
18978 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
18979 0.1.0.6-rc which introduced --disable-threads.
18980 - When configuring, starting, or stopping an NT service, stop
18981 immediately after the service configuration attempt has succeeded
18982 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
18983 - When sending a NETINFO cell, include the original address
18984 received for the other side, not its canonical address. Found
18985 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
18986 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
18987 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
18988 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
18989 occurred when a client tried to fetch a descriptor for a bridge
18990 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
18991 - Backport fixes for a pair of compilation warnings on Windows.
18992 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
18993 - If we had ever tried to call tor_addr_to_str on an address of
18994 unknown type, we would have done a strdup on an uninitialized
18995 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
18996 Reported by "troll_un".
18997 - Correctly detect and handle transient lookup failures from
18998 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
18999 Reported by "troll_un".
19000 - Fix null-pointer access that could occur if TLS allocation failed.
19001 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
19002 - Use tor_socket_t type for listener argument to accept(). Fixes bug
19003 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
19006 - Add two new config options for directory authorities:
19007 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
19008 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
19009 that is always sufficient to satisfy the bandwidth requirement for
19010 the Guard flag. Now it will be easier for researchers to simulate
19011 Tor networks with different values. Resolves ticket 4484.
19012 - When Tor ignores a hidden service specified in its configuration,
19013 include the hidden service's directory in the warning message.
19014 Previously, we would only tell the user that some hidden service
19015 was ignored. Bugfix on 0.0.6; fixes bug 4426.
19016 - Update to the December 6 2011 Maxmind GeoLite Country database.
19018 o Packaging changes:
19019 - Make it easier to automate expert package builds on Windows,
19020 by removing an absolute path from makensis.exe command.
19023 Changes in version 0.2.1.32 - 2011-12-16
19024 Tor 0.2.1.32 backports important security and privacy fixes for
19025 oldstable. This release is intended only for package maintainers and
19026 others who cannot use the 0.2.2 stable series. All others should be
19027 using Tor 0.2.2.x or newer.
19029 The Tor 0.2.1.x series will reach formal end-of-life some time in
19030 early 2012; we will stop releasing patches for it then.
19032 o Major bugfixes (also included in 0.2.2.x):
19033 - Correctly sanity-check that we don't underflow on a memory
19034 allocation (and then assert) for hidden service introduction
19035 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
19036 bugfix on 0.2.1.5-alpha.
19037 - Fix a heap overflow bug that could occur when trying to pull
19038 data into the first chunk of a buffer, when that chunk had
19039 already had some data drained from it. Fixes CVE-2011-2778;
19040 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
19043 - Update to the December 6 2011 Maxmind GeoLite Country database.
19046 Changes in version 0.2.2.34 - 2011-10-26
19047 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
19048 can deanonymize Tor users. Everybody should upgrade.
19050 The attack relies on four components: 1) Clients reuse their TLS cert
19051 when talking to different relays, so relays can recognize a user by
19052 the identity key in her cert. 2) An attacker who knows the client's
19053 identity key can probe each guard relay to see if that identity key
19054 is connected to that guard relay right now. 3) A variety of active
19055 attacks in the literature (starting from "Low-Cost Traffic Analysis
19056 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
19057 discover the guard relays that a Tor user visiting the website is using.
19058 4) Clients typically pick three guards at random, so the set of guards
19059 for a given user could well be a unique fingerprint for her. This
19060 release fixes components #1 and #2, which is enough to block the attack;
19061 the other two remain as open research problems. Special thanks to
19062 "frosty_un" for reporting the issue to us!
19064 Clients should upgrade so they are no longer recognizable by the TLS
19065 certs they present. Relays should upgrade so they no longer allow a
19066 remote attacker to probe them to test whether unpatched clients are
19067 currently connected to them.
19069 This release also fixes several vulnerabilities that allow an attacker
19070 to enumerate bridge relays. Some bridge enumeration attacks still
19071 remain; see for example proposal 188.
19073 o Privacy/anonymity fixes (clients):
19074 - Clients and bridges no longer send TLS certificate chains on
19075 outgoing OR connections. Previously, each client or bridge would
19076 use the same cert chain for all outgoing OR connections until
19077 its IP address changes, which allowed any relay that the client
19078 or bridge contacted to determine which entry guards it is using.
19079 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
19080 - If a relay receives a CREATE_FAST cell on a TLS connection, it
19081 no longer considers that connection as suitable for satisfying a
19082 circuit EXTEND request. Now relays can protect clients from the
19083 CVE-2011-2768 issue even if the clients haven't upgraded yet.
19084 - Directory authorities no longer assign the Guard flag to relays
19085 that haven't upgraded to the above "refuse EXTEND requests
19086 to client connections" fix. Now directory authorities can
19087 protect clients from the CVE-2011-2768 issue even if neither
19088 the clients nor the relays have upgraded yet. There's a new
19089 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
19090 to let us transition smoothly, else tomorrow there would be no
19093 o Privacy/anonymity fixes (bridge enumeration):
19094 - Bridge relays now do their directory fetches inside Tor TLS
19095 connections, like all the other clients do, rather than connecting
19096 directly to the DirPort like public relays do. Removes another
19097 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
19098 - Bridges relays now build circuits for themselves in a more similar
19099 way to how clients build them. Removes another avenue for
19100 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
19101 when bridges were introduced.
19102 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
19103 that they initiated. Relays could distinguish incoming bridge
19104 connections from client connections, creating another avenue for
19105 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
19106 Found by "frosty_un".
19109 - Fix a crash bug when changing node restrictions while a DNS lookup
19110 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
19112 - Don't launch a useless circuit after failing to use one of a
19113 hidden service's introduction points. Previously, we would
19114 launch a new introduction circuit, but not set the hidden service
19115 which that circuit was intended to connect to, so it would never
19116 actually be used. A different piece of code would then create a
19117 new introduction circuit correctly. Bug reported by katmagic and
19118 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
19121 - Change an integer overflow check in the OpenBSD_Malloc code so
19122 that GCC is less likely to eliminate it as impossible. Patch
19123 from Mansour Moufid. Fixes bug 4059.
19124 - When a hidden service turns an extra service-side introduction
19125 circuit into a general-purpose circuit, free the rend_data and
19126 intro_key fields first, so we won't leak memory if the circuit
19127 is cannibalized for use as another service-side introduction
19128 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
19129 - Bridges now skip DNS self-tests, to act a little more stealthily.
19130 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
19131 bridges. Patch by "warms0x".
19132 - Fix internal bug-checking logic that was supposed to catch
19133 failures in digest generation so that it will fail more robustly
19134 if we ask for a nonexistent algorithm. Found by Coverity Scan.
19135 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
19136 - Report any failure in init_keys() calls launched because our
19137 IP address has changed. Spotted by Coverity Scan. Bugfix on
19138 0.1.1.4-alpha; fixes CID 484.
19140 o Minor bugfixes (log messages and documentation):
19141 - Remove a confusing dollar sign from the example fingerprint in the
19142 man page, and also make the example fingerprint a valid one. Fixes
19143 bug 4309; bugfix on 0.2.1.3-alpha.
19144 - The next version of Windows will be called Windows 8, and it has
19145 a major version of 6, minor version of 2. Correctly identify that
19146 version instead of calling it "Very recent version". Resolves
19147 ticket 4153; reported by funkstar.
19148 - Downgrade log messages about circuit timeout calibration from
19149 "notice" to "info": they don't require or suggest any human
19150 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
19151 bugfix on 0.2.2.14-alpha.
19154 - Turn on directory request statistics by default and include them in
19155 extra-info descriptors. Don't break if we have no GeoIP database.
19156 Backported from 0.2.3.1-alpha; implements ticket 3951.
19157 - Update to the October 4 2011 Maxmind GeoLite Country database.
19160 Changes in version 0.2.1.31 - 2011-10-26
19161 Tor 0.2.1.31 backports important security and privacy fixes for
19162 oldstable. This release is intended only for package maintainers and
19163 others who cannot use the 0.2.2 stable series. All others should be
19164 using Tor 0.2.2.x or newer.
19166 o Security fixes (also included in 0.2.2.x):
19167 - Replace all potentially sensitive memory comparison operations
19168 with versions whose runtime does not depend on the data being
19169 compared. This will help resist a class of attacks where an
19170 adversary can use variations in timing information to learn
19171 sensitive data. Fix for one case of bug 3122. (Safe memcmp
19172 implementation by Robert Ransom based partially on code by DJB.)
19173 - Fix an assert in parsing router descriptors containing IPv6
19174 addresses. This one took down the directory authorities when
19175 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
19177 o Privacy/anonymity fixes (also included in 0.2.2.x):
19178 - Clients and bridges no longer send TLS certificate chains on
19179 outgoing OR connections. Previously, each client or bridge would
19180 use the same cert chain for all outgoing OR connections until
19181 its IP address changes, which allowed any relay that the client
19182 or bridge contacted to determine which entry guards it is using.
19183 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
19184 - If a relay receives a CREATE_FAST cell on a TLS connection, it
19185 no longer considers that connection as suitable for satisfying a
19186 circuit EXTEND request. Now relays can protect clients from the
19187 CVE-2011-2768 issue even if the clients haven't upgraded yet.
19188 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
19189 that they initiated. Relays could distinguish incoming bridge
19190 connections from client connections, creating another avenue for
19191 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
19192 Found by "frosty_un".
19193 - When receiving a hidden service descriptor, check that it is for
19194 the hidden service we wanted. Previously, Tor would store any
19195 hidden service descriptors that a directory gave it, whether it
19196 wanted them or not. This wouldn't have let an attacker impersonate
19197 a hidden service, but it did let directories pre-seed a client
19198 with descriptors that it didn't want. Bugfix on 0.0.6.
19199 - Avoid linkability based on cached hidden service descriptors: forget
19200 all hidden service descriptors cached as a client when processing a
19201 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
19202 - Make the bridge directory authority refuse to answer directory
19203 requests for "all" descriptors. It used to include bridge
19204 descriptors in its answer, which was a major information leak.
19205 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
19206 - Don't attach new streams to old rendezvous circuits after SIGNAL
19207 NEWNYM. Previously, we would keep using an existing rendezvous
19208 circuit if it remained open (i.e. if it were kept open by a
19209 long-lived stream, or if a new stream were attached to it before
19210 Tor could notice that it was old and no longer in use). Bugfix on
19211 0.1.1.15-rc; fixes bug 3375.
19213 o Minor bugfixes (also included in 0.2.2.x):
19214 - When we restart our relay, we might get a successful connection
19215 from the outside before we've started our reachability tests,
19216 triggering a warning: "ORPort found reachable, but I have no
19217 routerinfo yet. Failing to inform controller of success." This
19218 bug was harmless unless Tor is running under a controller
19219 like Vidalia, in which case the controller would never get a
19220 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
19222 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
19223 enabled. Fixes bug 1526.
19224 - Remove undocumented option "-F" from tor-resolve: it hasn't done
19225 anything since 0.2.1.16-rc.
19226 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
19227 None of the cases where we did this before were wrong, but by making
19228 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
19229 - Fix a rare crash bug that could occur when a client was configured
19230 with a large number of bridges. Fixes bug 2629; bugfix on
19231 0.2.1.2-alpha. Bugfix by trac user "shitlei".
19232 - Correct the warning displayed when a rendezvous descriptor exceeds
19233 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
19235 - Fix an uncommon assertion failure when running with DNSPort under
19236 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
19237 - When warning about missing zlib development packages during compile,
19238 give the correct package names. Bugfix on 0.2.0.1-alpha.
19239 - Require that introduction point keys and onion keys have public
19240 exponent 65537. Bugfix on 0.2.0.10-alpha.
19241 - Do not crash when our configuration file becomes unreadable, for
19242 example due to a permissions change, between when we start up
19243 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
19245 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
19247 - Always NUL-terminate the sun_path field of a sockaddr_un before
19248 passing it to the kernel. (Not a security issue: kernels are
19249 smart enough to reject bad sockaddr_uns.) Found by Coverity;
19250 CID #428. Bugfix on Tor 0.2.0.3-alpha.
19251 - Don't stack-allocate the list of supplementary GIDs when we're
19252 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
19253 could take up to 256K, which is way too much stack. Found by
19254 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
19256 o Minor bugfixes (only in 0.2.1.x):
19257 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
19258 rely on them. Bugfix on 0.2.1.30.
19259 - Use git revisions instead of svn revisions when generating our
19260 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
19262 o Minor features (also included in 0.2.2.x):
19263 - Adjust the expiration time on our SSL session certificates to
19264 better match SSL certs seen in the wild. Resolves ticket 4014.
19265 - Allow nameservers with IPv6 address. Resolves bug 2574.
19266 - Update to the October 4 2011 Maxmind GeoLite Country database.
19269 Changes in version 0.2.2.33 - 2011-09-13
19270 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
19271 TLS handshake that makes relays and bridges that run this new version
19272 reachable from Iran again.
19275 - Avoid an assertion failure when reloading a configuration with
19276 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
19277 3923; bugfix on 0.2.2.25-alpha.
19279 o Minor features (security):
19280 - Check for replays of the public-key encrypted portion of an
19281 INTRODUCE1 cell, in addition to the current check for replays of
19282 the g^x value. This prevents a possible class of active attacks
19283 by an attacker who controls both an introduction point and a
19284 rendezvous point, and who uses the malleability of AES-CTR to
19285 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
19286 that these attacks are infeasible (requiring the attacker to send
19287 on the order of zettabytes of altered cells in a short interval),
19288 but we'd rather block them off in case there are any classes of
19289 this attack that we missed. Reported by Willem Pinckaers.
19292 - Adjust the expiration time on our SSL session certificates to
19293 better match SSL certs seen in the wild. Resolves ticket 4014.
19294 - Change the default required uptime for a relay to be accepted as
19295 a HSDir (hidden service directory) from 24 hours to 25 hours.
19296 Improves on 0.2.0.10-alpha; resolves ticket 2649.
19297 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
19298 authorities to abstain from voting on assignment of the HSDir
19299 consensus flag. Related to bug 2649.
19300 - Update to the September 6 2011 Maxmind GeoLite Country database.
19302 o Minor bugfixes (documentation and log messages):
19303 - Correct the man page to explain that HashedControlPassword and
19304 CookieAuthentication can both be set, in which case either method
19305 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
19306 when we decided to allow these config options to both be set. Issue
19307 raised by bug 3898.
19308 - Demote the 'replay detected' log message emitted when a hidden
19309 service receives the same Diffie-Hellman public key in two different
19310 INTRODUCE2 cells to info level. A normal Tor client can cause that
19311 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
19312 fixes part of bug 2442.
19313 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
19314 level. There is nothing that a hidden service's operator can do
19315 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
19317 - Clarify a log message specifying the characters permitted in
19318 HiddenServiceAuthorizeClient client names. Previously, the log
19319 message said that "[A-Za-z0-9+-_]" were permitted; that could have
19320 given the impression that every ASCII character between "+" and "_"
19321 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
19324 - Provide a substitute implementation of lround() for MSVC, which
19325 apparently lacks it. Patch from Gisle Vanem.
19326 - Clean up some code issues that prevented Tor from building on older
19327 BSDs. Fixes bug 3894; reported by "grarpamp".
19328 - Search for a platform-specific version of "ar" when cross-compiling.
19329 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
19332 Changes in version 0.2.2.32 - 2011-08-27
19333 The Tor 0.2.2 release series is dedicated to the memory of Andreas
19334 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
19335 a founder of the PETS community, a leader in our field, a mentor,
19336 and a friend. He left us with these words: "I had the possibility
19337 to contribute to this world that is not as it should be. I hope I
19338 could help in some areas to make the world a better place, and that
19339 I could also encourage other people to be engaged in improving the
19340 world. Please, stay engaged. This world needs you, your love, your
19341 initiative -- now I cannot be part of that anymore."
19343 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
19344 ready. More than two years in the making, this release features improved
19345 client performance and hidden service reliability, better compatibility
19346 for Android, correct behavior for bridges that listen on more than
19347 one address, more extensible and flexible directory object handling,
19348 better reporting of network statistics, improved code security, and
19349 many many other features and bugfixes.
19351 o Major features (client performance):
19352 - When choosing which cells to relay first, relays now favor circuits
19353 that have been quiet recently, to provide lower latency for
19354 low-volume circuits. By default, relays enable or disable this
19355 feature based on a setting in the consensus. They can override
19356 this default by using the new "CircuitPriorityHalflife" config
19357 option. Design and code by Ian Goldberg, Can Tang, and Chris
19359 - Directory authorities now compute consensus weightings that instruct
19360 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
19361 and no flag. Clients use these weightings to distribute network load
19362 more evenly across these different relay types. The weightings are
19363 in the consensus so we can change them globally in the future. Extra
19364 thanks to "outofwords" for finding some nasty security bugs in
19365 the first implementation of this feature.
19367 o Major features (client performance, circuit build timeout):
19368 - Tor now tracks how long it takes to build client-side circuits
19369 over time, and adapts its timeout to local network performance.
19370 Since a circuit that takes a long time to build will also provide
19371 bad performance, we get significant latency improvements by
19372 discarding the slowest 20% of circuits. Specifically, Tor creates
19373 circuits more aggressively than usual until it has enough data
19374 points for a good timeout estimate. Implements proposal 151.
19375 - Circuit build timeout constants can be controlled by consensus
19376 parameters. We set good defaults for these parameters based on
19377 experimentation on broadband and simulated high-latency links.
19378 - Circuit build time learning can be disabled via consensus parameter
19379 or by the client via a LearnCircuitBuildTimeout config option. We
19380 also automatically disable circuit build time calculation if either
19381 AuthoritativeDirectory is set, or if we fail to write our state
19382 file. Implements ticket 1296.
19384 o Major features (relays use their capacity better):
19385 - Set SO_REUSEADDR socket option on all sockets, not just
19386 listeners. This should help busy exit nodes avoid running out of
19387 useable ports just because all the ports have been used in the
19388 near past. Resolves issue 2850.
19389 - Relays now save observed peak bandwidth throughput rates to their
19390 state file (along with total usage, which was already saved),
19391 so that they can determine their correct estimated bandwidth on
19392 restart. Resolves bug 1863, where Tor relays would reset their
19393 estimated bandwidth to 0 after restarting.
19394 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
19395 should give us approximately 40-50% more Guard-flagged nodes,
19396 improving the anonymity the Tor network can provide and also
19397 decreasing the dropoff in throughput that relays experience when
19398 they first get the Guard flag.
19399 - Directory authorities now take changes in router IP address and
19400 ORPort into account when determining router stability. Previously,
19401 if a router changed its IP or ORPort, the authorities would not
19402 treat it as having any downtime for the purposes of stability
19403 calculation, whereas clients would experience downtime since the
19404 change would take a while to propagate to them. Resolves issue 1035.
19405 - New AccelName and AccelDir options add support for dynamic OpenSSL
19406 hardware crypto acceleration engines.
19408 o Major features (relays control their load better):
19409 - Exit relays now try harder to block exit attempts from unknown
19410 relays, to make it harder for people to use them as one-hop proxies
19411 a la tortunnel. Controlled by the refuseunknownexits consensus
19412 parameter (currently enabled), or you can override it on your
19413 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
19414 based on a variant of proposal 163.
19415 - Add separate per-conn write limiting to go with the per-conn read
19416 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
19417 but never per-conn write limits.
19418 - New consensus params "bwconnrate" and "bwconnburst" to let us
19419 rate-limit client connections as they enter the network. It's
19420 controlled in the consensus so we can turn it on and off for
19421 experiments. It's starting out off. Based on proposal 163.
19423 o Major features (controllers):
19424 - Export GeoIP information on bridge usage to controllers even if we
19425 have not yet been running for 24 hours. Now Vidalia bridge operators
19426 can get more accurate and immediate feedback about their
19427 contributions to the network.
19428 - Add an __OwningControllerProcess configuration option and a
19429 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
19430 that when it exits, Tor will shut down. Implements feature 3049.
19432 o Major features (directory authorities):
19433 - Directory authorities now create, vote on, and serve multiple
19434 parallel formats of directory data as part of their voting process.
19435 Partially implements Proposal 162: "Publish the consensus in
19437 - Directory authorities now agree on and publish small summaries
19438 of router information that clients can use in place of regular
19439 server descriptors. This transition will allow Tor 0.2.3 clients
19440 to use far less bandwidth for downloading information about the
19441 network. Begins the implementation of Proposal 158: "Clients
19442 download consensus + microdescriptors".
19443 - The directory voting system is now extensible to use multiple hash
19444 algorithms for signatures and resource selection. Newer formats
19445 are signed with SHA256, with a possibility for moving to a better
19446 hash algorithm in the future.
19447 - Directory authorities can now vote on arbitrary integer values as
19448 part of the consensus process. This is designed to help set
19449 network-wide parameters. Implements proposal 167.
19451 o Major features and bugfixes (node selection):
19452 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
19453 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
19454 options. Previously, we had been ambiguous in describing what
19455 counted as an "exit" node, and what operations exactly "StrictNodes
19456 0" would permit. This created confusion when people saw nodes built
19457 through unexpected circuits, and made it hard to tell real bugs from
19458 surprises. Now the intended behavior is:
19459 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
19460 a node that delivers user traffic outside the Tor network.
19461 . "Entry", in the context of EntryNodes, means a node used as the
19462 first hop of a multihop circuit. It doesn't include direct
19463 connections to directory servers.
19464 . "ExcludeNodes" applies to all nodes.
19465 . "StrictNodes" changes the behavior of ExcludeNodes only. When
19466 StrictNodes is set, Tor should avoid all nodes listed in
19467 ExcludeNodes, even when it will make user requests fail. When
19468 StrictNodes is *not* set, then Tor should follow ExcludeNodes
19469 whenever it can, except when it must use an excluded node to
19470 perform self-tests, connect to a hidden service, provide a
19471 hidden service, fulfill a .exit request, upload directory
19472 information, or fetch directory information.
19473 Collectively, the changes to implement the behavior fix bug 1090.
19474 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
19475 change during a config reload, mark and discard all our origin
19476 circuits. This fix should address edge cases where we change the
19477 config options and but then choose a circuit that we created before
19479 - Make EntryNodes config option much more aggressive even when
19480 StrictNodes is not set. Before it would prepend your requested
19481 entrynodes to your list of guard nodes, but feel free to use others
19482 after that. Now it chooses only from your EntryNodes if any of
19483 those are available, and only falls back to others if a) they're
19484 all down and b) StrictNodes is not set.
19485 - Now we refresh your entry guards from EntryNodes at each consensus
19486 fetch -- rather than just at startup and then they slowly rot as
19487 the network changes.
19488 - Add support for the country code "{??}" in torrc options like
19489 ExcludeNodes, to indicate all routers of unknown country. Closes
19491 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
19492 a node is listed in both, it's treated as excluded.
19493 - ExcludeNodes now applies to directory nodes -- as a preference if
19494 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
19495 Don't exclude all the directory authorities and set StrictNodes to 1
19496 unless you really want your Tor to break.
19497 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
19498 - ExcludeExitNodes now overrides .exit requests.
19499 - We don't use bridges listed in ExcludeNodes.
19500 - When StrictNodes is 1:
19501 . We now apply ExcludeNodes to hidden service introduction points
19502 and to rendezvous points selected by hidden service users. This
19503 can make your hidden service less reliable: use it with caution!
19504 . If we have used ExcludeNodes on ourself, do not try relay
19505 reachability self-tests.
19506 . If we have excluded all the directory authorities, we will not
19507 even try to upload our descriptor if we're a relay.
19508 . Do not honor .exit requests to an excluded node.
19509 - When the set of permitted nodes changes, we now remove any mappings
19510 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
19512 - We never cannibalize a circuit that had excluded nodes on it, even
19513 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
19514 - Improve log messages related to excluded nodes.
19516 o Major features (misc):
19517 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
19518 to help Tor build correctly for Android phones.
19519 - The options SocksPort, ControlPort, and so on now all accept a
19520 value "auto" that opens a socket on an OS-selected port. A
19521 new ControlPortWriteToFile option tells Tor to write its
19522 actual control port or ports to a chosen file. If the option
19523 ControlPortFileGroupReadable is set, the file is created as
19524 group-readable. Now users can run two Tor clients on the same
19525 system without needing to manually mess with parameters. Resolves
19526 part of ticket 3076.
19527 - Tor now supports tunneling all of its outgoing connections over
19528 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
19529 configuration options. Code by Christopher Davis.
19531 o Code security improvements:
19532 - Replace all potentially sensitive memory comparison operations
19533 with versions whose runtime does not depend on the data being
19534 compared. This will help resist a class of attacks where an
19535 adversary can use variations in timing information to learn
19536 sensitive data. Fix for one case of bug 3122. (Safe memcmp
19537 implementation by Robert Ransom based partially on code by DJB.)
19538 - Enable Address Space Layout Randomization (ASLR) and Data Execution
19539 Prevention (DEP) by default on Windows to make it harder for
19540 attackers to exploit vulnerabilities. Patch from John Brooks.
19541 - New "--enable-gcc-hardening" ./configure flag (off by default)
19542 to turn on gcc compile time hardening options. It ensures
19543 that signed ints have defined behavior (-fwrapv), enables
19544 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
19545 with canaries (-fstack-protector-all), turns on ASLR protection if
19546 supported by the kernel (-fPIE, -pie), and adds additional security
19547 related warnings. Verified to work on Mac OS X and Debian Lenny.
19548 - New "--enable-linker-hardening" ./configure flag (off by default)
19549 to turn on ELF specific hardening features (relro, now). This does
19550 not work with Mac OS X or any other non-ELF binary format.
19551 - Always search the Windows system directory for system DLLs, and
19552 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
19553 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
19554 current and future memory pages via mlockall(). On supported
19555 platforms (modern Linux and probably BSD but not Windows or OS X),
19556 this should effectively disable any and all attempts to page out
19557 memory. This option requires that you start your Tor as root --
19558 if you use DisableAllSwap, please consider using the User option
19559 to properly reduce the privileges of your Tor.
19561 o Major bugfixes (crashes):
19562 - Fix crash bug on platforms where gmtime and localtime can return
19563 NULL. Windows 7 users were running into this one. Fixes part of bug
19564 2077. Bugfix on all versions of Tor. Found by boboper.
19565 - Introduce minimum/maximum values that clients will believe
19566 from the consensus. Now we'll have a better chance to avoid crashes
19567 or worse when a consensus param has a weird value.
19568 - Fix a rare crash bug that could occur when a client was configured
19569 with a large number of bridges. Fixes bug 2629; bugfix on
19570 0.2.1.2-alpha. Bugfix by trac user "shitlei".
19571 - Do not crash when our configuration file becomes unreadable, for
19572 example due to a permissions change, between when we start up
19573 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
19575 - If we're in the pathological case where there's no exit bandwidth
19576 but there is non-exit bandwidth, or no guard bandwidth but there
19577 is non-guard bandwidth, don't crash during path selection. Bugfix
19579 - Fix a crash bug when trying to initialize the evdns module in
19580 Libevent 2. Bugfix on 0.2.1.16-rc.
19582 o Major bugfixes (stability):
19583 - Fix an assert in parsing router descriptors containing IPv6
19584 addresses. This one took down the directory authorities when
19585 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
19586 - Fix an uncommon assertion failure when running with DNSPort under
19587 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
19588 - Treat an unset $HOME like an empty $HOME rather than triggering an
19589 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
19590 - More gracefully handle corrupt state files, removing asserts
19591 in favor of saving a backup and resetting state.
19592 - Instead of giving an assertion failure on an internal mismatch
19593 on estimated freelist size, just log a BUG warning and try later.
19594 Mitigates but does not fix bug 1125.
19595 - Fix an assert that got triggered when using the TestingTorNetwork
19596 configuration option and then issuing a GETINFO config-text control
19597 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
19598 - If the cached cert file is unparseable, warn but don't exit.
19600 o Privacy fixes (relays/bridges):
19601 - Don't list Windows capabilities in relay descriptors. We never made
19602 use of them, and maybe it's a bad idea to publish them. Bugfix
19604 - If the Nickname configuration option isn't given, Tor would pick a
19605 nickname based on the local hostname as the nickname for a relay.
19606 Because nicknames are not very important in today's Tor and the
19607 "Unnamed" nickname has been implemented, this is now problematic
19608 behavior: It leaks information about the hostname without being
19609 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
19610 introduced the Unnamed nickname. Reported by tagnaq.
19611 - Maintain separate TLS contexts and certificates for incoming and
19612 outgoing connections in bridge relays. Previously we would use the
19613 same TLS contexts and certs for incoming and outgoing connections.
19614 Bugfix on 0.2.0.3-alpha; addresses bug 988.
19615 - Maintain separate identity keys for incoming and outgoing TLS
19616 contexts in bridge relays. Previously we would use the same
19617 identity keys for incoming and outgoing TLS contexts. Bugfix on
19618 0.2.0.3-alpha; addresses the other half of bug 988.
19619 - Make the bridge directory authority refuse to answer directory
19620 requests for "all descriptors". It used to include bridge
19621 descriptors in its answer, which was a major information leak.
19622 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
19624 o Privacy fixes (clients):
19625 - When receiving a hidden service descriptor, check that it is for
19626 the hidden service we wanted. Previously, Tor would store any
19627 hidden service descriptors that a directory gave it, whether it
19628 wanted them or not. This wouldn't have let an attacker impersonate
19629 a hidden service, but it did let directories pre-seed a client
19630 with descriptors that it didn't want. Bugfix on 0.0.6.
19631 - Start the process of disabling ".exit" address notation, since it
19632 can be used for a variety of esoteric application-level attacks
19633 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
19635 - Reject attempts at the client side to open connections to private
19636 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
19637 a randomly chosen exit node. Attempts to do so are always
19638 ill-defined, generally prevented by exit policies, and usually
19639 in error. This will also help to detect loops in transparent
19640 proxy configurations. You can disable this feature by setting
19641 "ClientRejectInternalAddresses 0" in your torrc.
19642 - Log a notice when we get a new control connection. Now it's easier
19643 for security-conscious users to recognize when a local application
19644 is knocking on their controller door. Suggested by bug 1196.
19646 o Privacy fixes (newnym):
19647 - Avoid linkability based on cached hidden service descriptors: forget
19648 all hidden service descriptors cached as a client when processing a
19649 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
19650 - On SIGHUP, do not clear out all TrackHostExits mappings, client
19651 DNS cache entries, and virtual address mappings: that's what
19652 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
19653 - Don't attach new streams to old rendezvous circuits after SIGNAL
19654 NEWNYM. Previously, we would keep using an existing rendezvous
19655 circuit if it remained open (i.e. if it were kept open by a
19656 long-lived stream, or if a new stream were attached to it before
19657 Tor could notice that it was old and no longer in use). Bugfix on
19658 0.1.1.15-rc; fixes bug 3375.
19660 o Major bugfixes (relay bandwidth accounting):
19661 - Fix a bug that could break accounting on 64-bit systems with large
19662 time_t values, making them hibernate for impossibly long intervals.
19663 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
19664 - Fix a bug in bandwidth accounting that could make us use twice
19665 the intended bandwidth when our interval start changes due to
19666 daylight saving time. Now we tolerate skew in stored vs computed
19667 interval starts: if the start of the period changes by no more than
19668 50% of the period's duration, we remember bytes that we transferred
19669 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
19671 o Major bugfixes (bridges):
19672 - Bridges now use "reject *:*" as their default exit policy. Bugfix
19673 on 0.2.0.3-alpha. Fixes bug 1113.
19674 - If you configure your bridge with a known identity fingerprint,
19675 and the bridge authority is unreachable (as it is in at least
19676 one country now), fall back to directly requesting the descriptor
19677 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
19679 - Fix a bug where bridge users who configure the non-canonical
19680 address of a bridge automatically switch to its canonical
19681 address. If a bridge listens at more than one address, it
19682 should be able to advertise those addresses independently and
19683 any non-blocked addresses should continue to work. Bugfix on Tor
19684 0.2.0.3-alpha. Fixes bug 2510.
19685 - If you configure Tor to use bridge A, and then quit and
19686 configure Tor to use bridge B instead (or if you change Tor
19687 to use bridge B via the controller), it would happily continue
19688 to use bridge A if it's still reachable. While this behavior is
19689 a feature if your goal is connectivity, in some scenarios it's a
19690 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
19691 - When the controller configures a new bridge, don't wait 10 to 60
19692 seconds before trying to fetch its descriptor. Bugfix on
19693 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
19695 o Major bugfixes (directory authorities):
19696 - Many relays have been falling out of the consensus lately because
19697 not enough authorities know about their descriptor for them to get
19698 a majority of votes. When we deprecated the v2 directory protocol,
19699 we got rid of the only way that v3 authorities can hear from each
19700 other about other descriptors. Now authorities examine every v3
19701 vote for new descriptors, and fetch them from that authority. Bugfix
19703 - Authorities could be tricked into giving out the Exit flag to relays
19704 that didn't allow exiting to any ports. This bug could screw
19705 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
19706 1238. Bug discovered by Martin Kowalczyk.
19707 - If all authorities restart at once right before a consensus vote,
19708 nobody will vote about "Running", and clients will get a consensus
19709 with no usable relays. Instead, authorities refuse to build a
19710 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
19712 o Major bugfixes (stream-level fairness):
19713 - When receiving a circuit-level SENDME for a blocked circuit, try
19714 to package cells fairly from all the streams that had previously
19715 been blocked on that circuit. Previously, we had started with the
19716 oldest stream, and allowed each stream to potentially exhaust
19717 the circuit's package window. This gave older streams on any
19718 given circuit priority over newer ones. Fixes bug 1937. Detected
19719 originally by Camilo Viecco. This bug was introduced before the
19720 first Tor release, in svn commit r152: it is the new winner of
19721 the longest-lived bug prize.
19722 - Fix a stream fairness bug that would cause newer streams on a given
19723 circuit to get preference when reading bytes from the origin or
19724 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
19725 introduced before the first Tor release, in svn revision r152.
19726 - When the exit relay got a circuit-level sendme cell, it started
19727 reading on the exit streams, even if had 500 cells queued in the
19728 circuit queue already, so the circuit queue just grew and grew in
19729 some cases. We fix this by not re-enabling reading on receipt of a
19730 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
19731 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
19733 - Newly created streams were allowed to read cells onto circuits,
19734 even if the circuit's cell queue was blocked and waiting to drain.
19735 This created potential unfairness, as older streams would be
19736 blocked, but newer streams would gladly fill the queue completely.
19737 We add code to detect this situation and prevent any stream from
19738 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
19741 o Major bugfixes (hidden services):
19742 - Apply circuit timeouts to opened hidden-service-related circuits
19743 based on the correct start time. Previously, we would apply the
19744 circuit build timeout based on time since the circuit's creation;
19745 it was supposed to be applied based on time since the circuit
19746 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
19747 - Improve hidden service robustness: When we find that we have
19748 extended a hidden service's introduction circuit to a relay not
19749 listed as an introduction point in the HS descriptor we currently
19750 have, retry with an introduction point from the current
19751 descriptor. Previously we would just give up. Fixes bugs 1024 and
19752 1930; bugfix on 0.2.0.10-alpha.
19753 - Directory authorities now use data collected from their own
19754 uptime observations when choosing whether to assign the HSDir flag
19755 to relays, instead of trusting the uptime value the relay reports in
19756 its descriptor. This change helps prevent an attack where a small
19757 set of nodes with frequently-changing identity keys can blackhole
19758 a hidden service. (Only authorities need upgrade; others will be
19759 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
19760 - Stop assigning the HSDir flag to relays that disable their
19761 DirPort (and thus will refuse to answer directory requests). This
19762 fix should dramatically improve the reachability of hidden services:
19763 hidden services and hidden service clients pick six HSDir relays
19764 to store and retrieve the hidden service descriptor, and currently
19765 about half of the HSDir relays will refuse to work. Bugfix on
19766 0.2.0.10-alpha; fixes part of bug 1693.
19768 o Major bugfixes (misc):
19769 - Clients now stop trying to use an exit node associated with a given
19770 destination by TrackHostExits if they fail to reach that exit node.
19771 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
19772 - Fix a regression that caused Tor to rebind its ports if it receives
19773 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
19774 - Remove an extra pair of quotation marks around the error
19775 message in control-port STATUS_GENERAL BUG events. Bugfix on
19776 0.1.2.6-alpha; fixes bug 3732.
19778 o Minor features (relays):
19779 - Ensure that no empty [dirreq-](read|write)-history lines are added
19780 to an extrainfo document. Implements ticket 2497.
19781 - When bandwidth accounting is enabled, be more generous with how
19782 much bandwidth we'll use up before entering "soft hibernation".
19783 Previously, we'd refuse new connections and circuits once we'd
19784 used up 95% of our allotment. Now, we use up 95% of our allotment,
19785 AND make sure that we have no more than 500MB (or 3 hours of
19786 expected traffic, whichever is lower) remaining before we enter
19788 - Relays now log the reason for publishing a new relay descriptor,
19789 so we have a better chance of hunting down instances of bug 1810.
19790 Resolves ticket 3252.
19791 - Log a little more clearly about the times at which we're no longer
19792 accepting new connections (e.g. due to hibernating). Resolves
19794 - When AllowSingleHopExits is set, print a warning to explain to the
19795 relay operator why most clients are avoiding her relay.
19796 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
19797 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
19798 clients are already deprecated because of security bugs.
19800 o Minor features (network statistics):
19801 - Directory mirrors that set "DirReqStatistics 1" write statistics
19802 about directory requests to disk every 24 hours. As compared to the
19803 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
19804 improvements: 1) stats are written to disk exactly every 24 hours;
19805 2) estimated shares of v2 and v3 requests are determined as mean
19806 values, not at the end of a measurement period; 3) unresolved
19807 requests are listed with country code '??'; 4) directories also
19808 measure download times.
19809 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
19810 number of exit streams and transferred bytes per port to disk every
19812 - Relays that set "CellStatistics 1" write statistics on how long
19813 cells spend in their circuit queues to disk every 24 hours.
19814 - Entry nodes that set "EntryStatistics 1" write statistics on the
19815 rough number and origins of connecting clients to disk every 24
19817 - Relays that write any of the above statistics to disk and set
19818 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
19819 their extra-info documents. Implements proposal 166.
19821 o Minor features (GeoIP and statistics):
19822 - Provide a log message stating which geoip file we're parsing
19823 instead of just stating that we're parsing the geoip file.
19824 Implements ticket 2432.
19825 - Make sure every relay writes a state file at least every 12 hours.
19826 Previously, a relay could go for weeks without writing its state
19827 file, and on a crash could lose its bandwidth history, capacity
19828 estimates, client country statistics, and so on. Addresses bug 3012.
19829 - Relays report the number of bytes spent on answering directory
19830 requests in extra-info descriptors similar to {read,write}-history.
19831 Implements enhancement 1790.
19832 - Report only the top 10 ports in exit-port stats in order not to
19833 exceed the maximum extra-info descriptor length of 50 KB. Implements
19835 - If writing the state file to disk fails, wait up to an hour before
19836 retrying again, rather than trying again each second. Fixes bug
19837 2346; bugfix on Tor 0.1.1.3-alpha.
19838 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
19839 when we switch from being a public relay to a bridge. Otherwise
19840 there will still be clients that see the relay in their consensus,
19841 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
19843 - Update to the August 2 2011 Maxmind GeoLite Country database.
19845 o Minor features (clients):
19846 - When expiring circuits, use microsecond timers rather than
19847 one-second timers. This can avoid an unpleasant situation where a
19848 circuit is launched near the end of one second and expired right
19849 near the beginning of the next, and prevent fluctuations in circuit
19851 - If we've configured EntryNodes and our network goes away and/or all
19852 our entrynodes get marked down, optimistically retry them all when
19853 a new socks application request appears. Fixes bug 1882.
19854 - Always perform router selections using weighted relay bandwidth,
19855 even if we don't need a high capacity circuit at the time. Non-fast
19856 circuits now only differ from fast ones in that they can use relays
19857 not marked with the Fast flag. This "feature" could turn out to
19858 be a horrible bug; we should investigate more before it goes into
19860 - When we run out of directory information such that we can't build
19861 circuits, but then get enough that we can build circuits, log when
19862 we actually construct a circuit, so the user has a better chance of
19863 knowing what's going on. Fixes bug 1362.
19864 - Log SSL state transitions at debug level during handshake, and
19865 include SSL states in error messages. This may help debug future
19866 SSL handshake issues.
19868 o Minor features (directory authorities):
19869 - When a router changes IP address or port, authorities now launch
19870 a new reachability test for it. Implements ticket 1899.
19871 - Directory authorities now reject relays running any versions of
19872 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
19873 known bugs that keep RELAY_EARLY cells from working on rendezvous
19874 circuits. Followup to fix for bug 2081.
19875 - Directory authorities now reject relays running any version of Tor
19876 older than 0.2.0.26-rc. That version is the earliest that fetches
19877 current directory information correctly. Fixes bug 2156.
19878 - Directory authorities now do an immediate reachability check as soon
19879 as they hear about a new relay. This change should slightly reduce
19880 the time between setting up a relay and getting listed as running
19881 in the consensus. It should also improve the time between setting
19882 up a bridge and seeing use by bridge users.
19883 - Directory authorities no longer launch a TLS connection to every
19884 relay as they startup. Now that we have 2k+ descriptors cached,
19885 the resulting network hiccup is becoming a burden. Besides,
19886 authorities already avoid voting about Running for the first half
19887 hour of their uptime.
19888 - Directory authorities now log the source of a rejected POSTed v3
19889 networkstatus vote, so we can track failures better.
19890 - Backport code from 0.2.3.x that allows directory authorities to
19891 clean their microdescriptor caches. Needed to resolve bug 2230.
19893 o Minor features (hidden services):
19894 - Use computed circuit-build timeouts to decide when to launch
19895 parallel introduction circuits for hidden services. (Previously,
19896 we would retry after 15 seconds.)
19897 - Don't allow v0 hidden service authorities to act as clients.
19898 Required by fix for bug 3000.
19899 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
19900 by fix for bug 3000.
19901 - Make hidden services work better in private Tor networks by not
19902 requiring any uptime to join the hidden service descriptor
19903 DHT. Implements ticket 2088.
19904 - Log (at info level) when purging pieces of hidden-service-client
19905 state because of SIGNAL NEWNYM.
19907 o Minor features (controller interface):
19908 - New "GETINFO net/listeners/(type)" controller command to return
19909 a list of addresses and ports that are bound for listeners for a
19910 given connection type. This is useful when the user has configured
19911 "SocksPort auto" and the controller needs to know which port got
19912 chosen. Resolves another part of ticket 3076.
19913 - Have the controller interface give a more useful message than
19914 "Internal Error" in response to failed GETINFO requests.
19915 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
19916 event, to give information on the current rate of circuit timeouts
19917 over our stored history.
19918 - The 'EXTENDCIRCUIT' control port command can now be used with
19919 a circ id of 0 and no path. This feature will cause Tor to build
19920 a new 'fast' general purpose circuit using its own path selection
19922 - Added a BUILDTIMEOUT_SET controller event to describe changes
19923 to the circuit build timeout.
19924 - New controller command "getinfo config-text". It returns the
19925 contents that Tor would write if you send it a SAVECONF command,
19926 so the controller can write the file to disk itself.
19928 o Minor features (controller protocol):
19929 - Add a new ControlSocketsGroupWritable configuration option: when
19930 it is turned on, ControlSockets are group-writeable by the default
19931 group of the current user. Patch by Jérémy Bobbio; implements
19933 - Tor now refuses to create a ControlSocket in a directory that is
19934 world-readable (or group-readable if ControlSocketsGroupWritable
19935 is 0). This is necessary because some operating systems do not
19936 enforce permissions on an AF_UNIX sockets. Permissions on the
19937 directory holding the socket, however, seems to work everywhere.
19938 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
19939 not. This would lead to a cookie that is still not group readable.
19940 Closes bug 1843. Suggested by katmagic.
19941 - Future-proof the controller protocol a bit by ignoring keyword
19942 arguments we do not recognize.
19944 o Minor features (more useful logging):
19945 - Revise most log messages that refer to nodes by nickname to
19946 instead use the "$key=nickname at address" format. This should be
19947 more useful, especially since nicknames are less and less likely
19948 to be unique. Resolves ticket 3045.
19949 - When an HTTPS proxy reports "403 Forbidden", we now explain
19950 what it means rather than calling it an unexpected status code.
19951 Closes bug 2503. Patch from Michael Yakubovich.
19952 - Rate-limit a warning about failures to download v2 networkstatus
19953 documents. Resolves part of bug 1352.
19954 - Rate-limit the "your application is giving Tor only an IP address"
19955 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
19956 - Rate-limit "Failed to hand off onionskin" warnings.
19957 - When logging a rate-limited warning, we now mention how many messages
19958 got suppressed since the last warning.
19959 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
19960 2 no signature, 4 required" messages about consensus signatures
19961 easier to read, and make sure they get logged at the same severity
19962 as the messages explaining which keys are which. Fixes bug 1290.
19963 - Don't warn when we have a consensus that we can't verify because
19964 of missing certificates, unless those certificates are ones
19965 that we have been trying and failing to download. Fixes bug 1145.
19967 o Minor features (log domains):
19968 - Add documentation for configuring logging at different severities in
19969 different log domains. We've had this feature since 0.2.1.1-alpha,
19970 but for some reason it never made it into the manpage. Fixes
19972 - Make it simpler to specify "All log domains except for A and B".
19973 Previously you needed to say "[*,~A,~B]". Now you can just say
19975 - Add a "LogMessageDomains 1" option to include the domains of log
19976 messages along with the messages. Without this, there's no way
19977 to use log domains without reading the source or doing a lot
19979 - Add a new "Handshake" log domain for activities that happen
19980 during the TLS handshake.
19982 o Minor features (build process):
19983 - Make compilation with clang possible when using
19984 "--enable-gcc-warnings" by removing two warning options that clang
19985 hasn't implemented yet and by fixing a few warnings. Resolves
19987 - Detect platforms that brokenly use a signed size_t, and refuse to
19988 build there. Found and analyzed by doorss and rransom.
19989 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
19991 - Add support for statically linking zlib by specifying
19992 "--enable-static-zlib", to go with our support for statically
19993 linking openssl and libevent. Resolves bug 1358.
19994 - Instead of adding the svn revision to the Tor version string, report
19995 the git commit (when we're building from a git checkout).
19996 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
19998 - New --digests command-line switch to output the digests of the
19999 source files Tor was built with.
20000 - Generate our manpage and HTML documentation using Asciidoc. This
20001 change should make it easier to maintain the documentation, and
20002 produce nicer HTML. The build process fails if asciidoc cannot
20003 be found and building with asciidoc isn't disabled (via the
20004 "--disable-asciidoc" argument to ./configure. Skipping the manpage
20005 speeds up the build considerably.
20007 o Minor features (options / torrc):
20008 - Warn when the same option is provided more than once in a torrc
20009 file, on the command line, or in a single SETCONF statement, and
20010 the option is one that only accepts a single line. Closes bug 1384.
20011 - Warn when the user configures two HiddenServiceDir lines that point
20012 to the same directory. Bugfix on 0.0.6 (the version introducing
20013 HiddenServiceDir); fixes bug 3289.
20014 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
20015 do individual connection-level rate limiting of clients. The torrc
20016 config options with the same names trump the consensus params, if
20017 both are present. Replaces the old "bwconnrate" and "bwconnburst"
20018 consensus params which were broken from 0.2.2.7-alpha through
20019 0.2.2.14-alpha. Closes bug 1947.
20020 - New config option "WarnUnsafeSocks 0" disables the warning that
20021 occurs whenever Tor receives a socks handshake using a version of
20022 the socks protocol that can only provide an IP address (rather
20023 than a hostname). Setups that do DNS locally over Tor are fine,
20024 and we shouldn't spam the logs in that case.
20025 - New config option "CircuitStreamTimeout" to override our internal
20026 timeout schedule for how many seconds until we detach a stream from
20027 a circuit and try a new circuit. If your network is particularly
20028 slow, you might want to set this to a number like 60.
20029 - New options for SafeLogging to allow scrubbing only log messages
20030 generated while acting as a relay. Specify "SafeLogging relay" if
20031 you want to ensure that only messages known to originate from
20032 client use of the Tor process will be logged unsafely.
20033 - Time and memory units in the configuration file can now be set to
20034 fractional units. For example, "2.5 GB" is now a valid value for
20036 - Support line continuations in the torrc config file. If a line
20037 ends with a single backslash character, the newline is ignored, and
20038 the configuration value is treated as continuing on the next line.
20041 o Minor features (unit tests):
20042 - Revise our unit tests to use the "tinytest" framework, so we
20043 can run tests in their own processes, have smarter setup/teardown
20044 code, and so on. The unit test code has moved to its own
20045 subdirectory, and has been split into multiple modules.
20046 - Add a unit test for cross-platform directory-listing code.
20047 - Add some forgotten return value checks during unit tests. Found
20049 - Use GetTempDir to find the proper temporary directory location on
20050 Windows when generating temporary files for the unit tests. Patch
20053 o Minor features (misc):
20054 - The "torify" script now uses torsocks where available.
20055 - Make Libevent log messages get delivered to controllers later,
20056 and not from inside the Libevent log handler. This prevents unsafe
20057 reentrant Libevent calls while still letting the log messages
20059 - Certain Tor clients (such as those behind check.torproject.org) may
20060 want to fetch the consensus in an extra early manner. To enable this
20061 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
20062 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
20063 as only certain clients who must have this information sooner should
20065 - Expand homedirs passed to tor-checkkey. This should silence a
20066 coverity complaint about passing a user-supplied string into
20067 open() without checking it.
20068 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
20069 used on bridges, and it makes bridge scanning somewhat easier.
20070 - Create the /var/run/tor directory on startup on OpenSUSE if it is
20071 not already created. Patch from Andreas Stieger. Fixes bug 2573.
20073 o Minor bugfixes (relays):
20074 - When a relay decides that its DNS is too broken for it to serve
20075 as an exit server, it advertised itself as a non-exit, but
20076 continued to act as an exit. This could create accidental
20077 partitioning opportunities for users. Instead, if a relay is
20078 going to advertise reject *:* as its exit policy, it should
20079 really act with exit policy "reject *:*". Fixes bug 2366.
20080 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
20081 - Publish a router descriptor even if generating an extra-info
20082 descriptor fails. Previously we would not publish a router
20083 descriptor without an extra-info descriptor; this can cause fast
20084 exit relays collecting exit-port statistics to drop from the
20085 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
20086 - When we're trying to guess whether we know our IP address as
20087 a relay, we would log various ways that we failed to guess
20088 our address, but never log that we ended up guessing it
20089 successfully. Now add a log line to help confused and anxious
20090 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
20091 - For bandwidth accounting, calculate our expected bandwidth rate
20092 based on the time during which we were active and not in
20093 soft-hibernation during the last interval. Previously, we were
20094 also considering the time spent in soft-hibernation. If this
20095 was a long time, we would wind up underestimating our bandwidth
20096 by a lot, and skewing our wakeup time towards the start of the
20097 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
20098 - Demote a confusing TLS warning that relay operators might get when
20099 someone tries to talk to their ORPort. It is not the operator's
20100 fault, nor can they do anything about it. Fixes bug 1364; bugfix
20102 - Change "Application request when we're believed to be offline."
20103 notice to "Application request when we haven't used client
20104 functionality lately.", to clarify that it's not an error. Bugfix
20105 on 0.0.9.3; fixes bug 1222.
20107 o Minor bugfixes (bridges):
20108 - When a client starts or stops using bridges, never use a circuit
20109 that was built before the configuration change. This behavior could
20110 put at risk a user who uses bridges to ensure that her traffic
20111 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
20113 - Do not reset the bridge descriptor download status every time we
20114 re-parse our configuration or get a configuration change. Fixes
20115 bug 3019; bugfix on 0.2.0.3-alpha.
20116 - Users couldn't configure a regular relay to be their bridge. It
20117 didn't work because when Tor fetched the bridge descriptor, it found
20118 that it already had it, and didn't realize that the purpose of the
20119 descriptor had changed. Now we replace routers with a purpose other
20120 than bridge with bridge descriptors when fetching them. Bugfix on
20121 0.1.1.9-alpha. Fixes bug 1776.
20122 - In the special case where you configure a public exit relay as your
20123 bridge, Tor would be willing to use that exit relay as the last
20124 hop in your circuit as well. Now we fail that circuit instead.
20125 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
20127 o Minor bugfixes (clients):
20128 - We now ask the other side of a stream (the client or the exit)
20129 for more data on that stream when the amount of queued data on
20130 that stream dips low enough. Previously, we wouldn't ask the
20131 other side for more data until either it sent us more data (which
20132 it wasn't supposed to do if it had exhausted its window!) or we
20133 had completely flushed all our queued data. This flow control fix
20134 should improve throughput. Fixes bug 2756; bugfix on the earliest
20135 released versions of Tor (svn commit r152).
20136 - When a client finds that an origin circuit has run out of 16-bit
20137 stream IDs, we now mark it as unusable for new streams. Previously,
20138 we would try to close the entire circuit. Bugfix on 0.0.6.
20139 - Make it explicit that we don't cannibalize one-hop circuits. This
20140 happens in the wild, but doesn't turn out to be a problem because
20141 we fortunately don't use those circuits. Many thanks to outofwords
20142 for the initial analysis and to swissknife who confirmed that
20143 two-hop circuits are actually created.
20144 - Resolve an edge case in path weighting that could make us misweight
20145 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
20146 - Make the DNSPort option work with libevent 2.x. Don't alter the
20147 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
20149 o Minor bugfixes (directory authorities):
20150 - Make directory authorities more accurate at recording when
20151 relays that have failed several reachability tests became
20152 unreachable, so we can provide more accuracy at assigning Stable,
20153 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
20154 - Directory authorities are now more robust to hops back in time
20155 when calculating router stability. Previously, if a run of uptime
20156 or downtime appeared to be negative, the calculation could give
20157 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
20159 - Directory authorities will now attempt to download consensuses
20160 if their own efforts to make a live consensus have failed. This
20161 change means authorities that restart will fetch a valid
20162 consensus, and it means authorities that didn't agree with the
20163 current consensus will still fetch and serve it if it has enough
20164 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
20165 - Never vote for a server as "Running" if we have a descriptor for
20166 it claiming to be hibernating, and that descriptor was published
20167 more recently than our last contact with the server. Bugfix on
20168 0.2.0.3-alpha; fixes bug 911.
20169 - Directory authorities no longer change their opinion of, or vote on,
20170 whether a router is Running, unless they have themselves been
20171 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
20174 o Minor bugfixes (hidden services):
20175 - Log malformed requests for rendezvous descriptors as protocol
20176 warnings, not warnings. Also, use a more informative log message
20177 in case someone sees it at log level warning without prior
20178 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
20179 - Accept hidden service descriptors if we think we might be a hidden
20180 service directory, regardless of what our consensus says. This
20181 helps robustness, since clients and hidden services can sometimes
20182 have a more up-to-date view of the network consensus than we do,
20183 and if they think that the directory authorities list us a HSDir,
20184 we might actually be one. Related to bug 2732; bugfix on
20186 - Correct the warning displayed when a rendezvous descriptor exceeds
20187 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
20189 - Clients and hidden services now use HSDir-flagged relays for hidden
20190 service descriptor downloads and uploads even if the relays have no
20191 DirPort set and the client has disabled TunnelDirConns. This will
20192 eventually allow us to give the HSDir flag to relays with no
20193 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
20194 - Only limit the lengths of single HS descriptors, even when multiple
20195 HS descriptors are published to an HSDir relay in a single POST
20196 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
20198 o Minor bugfixes (controllers):
20199 - Allow GETINFO fingerprint to return a fingerprint even when
20200 we have not yet built a router descriptor. Fixes bug 3577;
20201 bugfix on 0.2.0.1-alpha.
20202 - Send a SUCCEEDED stream event to the controller when a reverse
20203 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
20204 discovered by katmagic.
20205 - Remove a trailing asterisk from "exit-policy/default" in the
20206 output of the control port command "GETINFO info/names". Bugfix
20208 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
20209 2917. Bugfix on 0.1.1.1-alpha.
20210 - When we restart our relay, we might get a successful connection
20211 from the outside before we've started our reachability tests,
20212 triggering a warning: "ORPort found reachable, but I have no
20213 routerinfo yet. Failing to inform controller of success." This
20214 bug was harmless unless Tor is running under a controller
20215 like Vidalia, in which case the controller would never get a
20216 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
20218 - When a controller changes TrackHostExits, remove mappings for
20219 hosts that should no longer have their exits tracked. Bugfix on
20221 - When a controller changes VirtualAddrNetwork, remove any mappings
20222 for hosts that were automapped to the old network. Bugfix on
20224 - When a controller changes one of the AutomapHosts* options, remove
20225 any mappings for hosts that should no longer be automapped. Bugfix
20227 - Fix an off-by-one error in calculating some controller command
20228 argument lengths. Fortunately, this mistake is harmless since
20229 the controller code does redundant NUL termination too. Found by
20230 boboper. Bugfix on 0.1.1.1-alpha.
20231 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
20232 would return "551 Internal error" rather than "552 Unrecognized key
20233 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
20234 - Don't spam the controller with events when we have no file
20235 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
20236 for log messages was already solved from bug 748.)
20237 - Emit a GUARD DROPPED controller event for a case we missed.
20238 - Ensure DNS requests launched by "RESOLVE" commands from the
20239 controller respect the __LeaveStreamsUnattached setconf options. The
20240 same goes for requests launched via DNSPort or transparent
20241 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
20243 o Minor bugfixes (config options):
20244 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
20245 Change the limit to 512 characters by removing base64 newlines.
20246 Fixes bug 2752. Fix by Michael Yakubovich.
20247 - Complain if PublishServerDescriptor is given multiple arguments that
20248 include 0 or 1. This configuration will be rejected in the future.
20249 Bugfix on 0.2.0.1-alpha; closes bug 1107.
20250 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
20251 Bugfix on 0.2.0.13-alpha; closes bug 928.
20253 o Minor bugfixes (log subsystem fixes):
20254 - When unable to format an address as a string, report its value
20255 as "???" rather than reusing the last formatted address. Bugfix
20257 - Be more consistent in our treatment of file system paths. "~" should
20258 get expanded to the user's home directory in the Log config option.
20259 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
20260 feature for the -f and --DataDirectory options.
20262 o Minor bugfixes (memory management):
20263 - Don't stack-allocate the list of supplementary GIDs when we're
20264 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
20265 could take up to 256K, which is way too much stack. Found by
20266 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
20267 - Save a couple bytes in memory allocation every time we escape
20268 certain characters in a string. Patch from Florian Zumbiehl.
20270 o Minor bugfixes (protocol correctness):
20271 - When checking for 1024-bit keys, check for 1024 bits, not 128
20272 bytes. This allows Tor to correctly discard keys of length 1017
20273 through 1023. Bugfix on 0.0.9pre5.
20274 - Require that introduction point keys and onion handshake keys
20275 have a public exponent of 65537. Starts to fix bug 3207; bugfix
20277 - Handle SOCKS messages longer than 128 bytes long correctly, rather
20278 than waiting forever for them to finish. Fixes bug 2330; bugfix
20279 on 0.2.0.16-alpha. Found by doorss.
20280 - Never relay a cell for a circuit we have already destroyed.
20281 Between marking a circuit as closeable and finally closing it,
20282 it may have been possible for a few queued cells to get relayed,
20283 even though they would have been immediately dropped by the next
20284 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
20285 - Never queue a cell for a circuit that's already been marked
20287 - Fix a spec conformance issue: the network-status-version token
20288 must be the first token in a v3 consensus or vote. Discovered by
20289 "parakeep". Bugfix on 0.2.0.3-alpha.
20290 - A networkstatus vote must contain exactly one signature. Spec
20291 conformance issue. Bugfix on 0.2.0.3-alpha.
20292 - When asked about a DNS record type we don't support via a
20293 client DNSPort, reply with NOTIMPL rather than an empty
20294 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
20295 - Make more fields in the controller protocol case-insensitive, since
20296 control-spec.txt said they were.
20298 o Minor bugfixes (log messages):
20299 - Fix a log message that said "bits" while displaying a value in
20300 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
20302 - Downgrade "no current certificates known for authority" message from
20303 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
20304 - Correctly describe errors that occur when generating a TLS object.
20305 Previously we would attribute them to a failure while generating a
20306 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
20308 - Fix an instance where a Tor directory mirror might accidentally
20309 log the IP address of a misbehaving Tor client. Bugfix on
20311 - Stop logging at severity 'warn' when some other Tor client tries
20312 to establish a circuit with us using weak DH keys. It's a protocol
20313 violation, but that doesn't mean ordinary users need to hear about
20314 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
20315 - If your relay can't keep up with the number of incoming create
20316 cells, it would log one warning per failure into your logs. Limit
20317 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
20319 o Minor bugfixes (build fixes):
20320 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
20321 - When warning about missing zlib development packages during compile,
20322 give the correct package names. Bugfix on 0.2.0.1-alpha.
20323 - Fix warnings that newer versions of autoconf produce during
20324 ./autogen.sh. These warnings appear to be harmless in our case,
20325 but they were extremely verbose. Fixes bug 2020.
20326 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
20329 o Minor bugfixes (portability):
20330 - Write several files in text mode, on OSes that distinguish text
20331 mode from binary mode (namely, Windows). These files are:
20332 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
20333 that collect those statistics; 'client_keys' and 'hostname' for
20334 hidden services that use authentication; and (in the tor-gencert
20335 utility) newly generated identity and signing keys. Previously,
20336 we wouldn't specify text mode or binary mode, leading to an
20337 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
20338 the DirRecordUsageByCountry option which would have triggered
20339 the assertion failure was added), although this assertion failure
20340 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
20341 - Selectively disable deprecation warnings on OS X because Lion
20342 started deprecating the shipped copy of openssl. Fixes bug 3643.
20343 - Use a wide type to hold sockets when built for 64-bit Windows.
20345 - Fix an issue that prevented static linking of libevent on
20346 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
20347 where we introduced the "--with-static-libevent" configure option.
20348 - Fix a bug with our locking implementation on Windows that couldn't
20349 correctly detect when a file was already locked. Fixes bug 2504,
20350 bugfix on 0.2.1.6-alpha.
20351 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
20353 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
20354 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
20357 o Minor bugfixes (code correctness):
20358 - Always NUL-terminate the sun_path field of a sockaddr_un before
20359 passing it to the kernel. (Not a security issue: kernels are
20360 smart enough to reject bad sockaddr_uns.) Found by Coverity;
20361 CID #428. Bugfix on Tor 0.2.0.3-alpha.
20362 - Make connection_printf_to_buf()'s behavior sane. Its callers
20363 expect it to emit a CRLF iff the format string ends with CRLF;
20364 it actually emitted a CRLF iff (a) the format string ended with
20365 CRLF or (b) the resulting string was over 1023 characters long or
20366 (c) the format string did not end with CRLF *and* the resulting
20367 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
20368 fixes part of bug 3407.
20369 - Make send_control_event_impl()'s behavior sane. Its callers
20370 expect it to always emit a CRLF at the end of the string; it
20371 might have emitted extra control characters as well. Bugfix on
20372 0.1.1.9-alpha; fixes another part of bug 3407.
20373 - Make crypto_rand_int() check the value of its input correctly.
20374 Previously, it accepted values up to UINT_MAX, but could return a
20375 negative number if given a value above INT_MAX+1. Found by George
20376 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
20377 - Fix a potential null-pointer dereference while computing a
20378 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
20380 - If we fail to compute the identity digest of a v3 legacy keypair,
20381 warn, and don't use a buffer-full of junk instead. Bugfix on
20382 0.2.1.1-alpha; fixes bug 3106.
20383 - Resolve an untriggerable issue in smartlist_string_num_isin(),
20384 where if the function had ever in the future been used to check
20385 for the presence of a too-large number, it would have given an
20386 incorrect result. (Fortunately, we only used it for 16-bit
20387 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
20388 - Be more careful about reporting the correct error from a failed
20389 connect() system call. Under some circumstances, it was possible to
20390 look at an incorrect value for errno when sending the end reason.
20391 Bugfix on 0.1.0.1-rc.
20392 - Correctly handle an "impossible" overflow cases in connection byte
20393 counting, where we write or read more than 4GB on an edge connection
20394 in a single second. Bugfix on 0.1.2.8-beta.
20395 - Avoid a double mark-for-free warning when failing to attach a
20396 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
20398 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
20399 found by "cypherpunks". This bug was introduced before the first
20400 Tor release, in svn commit r110.
20401 - Fix a bug in bandwidth history state parsing that could have been
20402 triggered if a future version of Tor ever changed the timing
20403 granularity at which bandwidth history is measured. Bugfix on
20404 Tor 0.1.1.11-alpha.
20405 - Add assertions to check for overflow in arguments to
20406 base32_encode() and base32_decode(); fix a signed-unsigned
20407 comparison there too. These bugs are not actually reachable in Tor,
20408 but it's good to prevent future errors too. Found by doorss.
20409 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
20411 - Set target port in get_interface_address6() correctly. Bugfix
20412 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
20413 - Fix an impossible-to-actually-trigger buffer overflow in relay
20414 descriptor generation. Bugfix on 0.1.0.15.
20415 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
20417 o Minor bugfixes (code improvements):
20418 - After we free an internal connection structure, overwrite it
20419 with a different memory value than we use for overwriting a freed
20420 internal circuit structure. Should help with debugging. Suggested
20422 - If OpenSSL fails to make a duplicate of a private or public key, log
20423 an error message and try to exit cleanly. May help with debugging
20424 if bug 1209 ever remanifests.
20425 - Some options used different conventions for uppercasing of acronyms
20426 when comparing manpage and source. Fix those in favor of the
20427 manpage, as it makes sense to capitalize acronyms.
20428 - Take a first step towards making or.h smaller by splitting out
20429 function definitions for all source files in src/or/. Leave
20430 structures and defines in or.h for now.
20431 - Remove a few dead assignments during router parsing. Found by
20433 - Don't use 1-bit wide signed bit fields. Found by coverity.
20434 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
20435 None of the cases where we did this before were wrong, but by making
20436 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
20437 - The memarea code now uses a sentinel value at the end of each area
20438 to make sure nothing writes beyond the end of an area. This might
20439 help debug some conceivable causes of bug 930.
20440 - Always treat failure to allocate an RSA key as an unrecoverable
20442 - Add some more defensive programming for architectures that can't
20443 handle unaligned integer accesses. We don't know of any actual bugs
20444 right now, but that's the best time to fix them. Fixes bug 1943.
20446 o Minor bugfixes (misc):
20447 - Fix a rare bug in rend_fn unit tests: we would fail a test when
20448 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
20449 on 0.2.0.10-alpha; fixes bug 1808.
20450 - Where available, use Libevent 2.0's periodic timers so that our
20451 once-per-second cleanup code gets called even more closely to
20452 once per second than it would otherwise. Fixes bug 943.
20453 - Ignore OutboundBindAddress when connecting to localhost.
20454 Connections to localhost need to come _from_ localhost, or else
20455 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
20457 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
20459 - If any of the v3 certs we download are unparseable, we should
20460 actually notice the failure so we don't retry indefinitely. Bugfix
20461 on 0.2.0.x; reported by "rotator".
20462 - When Tor fails to parse a descriptor of any kind, dump it to disk.
20463 Might help diagnosing bug 1051.
20464 - Make our 'torify' script more portable; if we have only one of
20465 'torsocks' or 'tsocks' installed, don't complain to the user;
20466 and explain our warning about tsocks better.
20467 - Fix some urls in the exit notice file and make it XHTML1.1 strict
20468 compliant. Based on a patch from Christian Kujau.
20470 o Documentation changes:
20471 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
20472 - Resolve all doxygen warnings except those for missing documentation.
20474 - Add doxygen documentation for more functions, fields, and types.
20475 - Convert the HACKING file to asciidoc, and add a few new sections
20476 to it, explaining how we use Git, how we make changelogs, and
20477 what should go in a patch.
20478 - Document the default socks host and port (127.0.0.1:9050) for
20480 - Removed some unnecessary files from the source distribution. The
20481 AUTHORS file has now been merged into the people page on the
20482 website. The roadmaps and design doc can now be found in the
20483 projects directory in svn.
20485 o Deprecated and removed features (config):
20486 - Remove the torrc.complete file. It hasn't been kept up to date
20487 and users will have better luck checking out the manpage.
20488 - Remove the HSAuthorityRecordStats option that version 0 hidden
20489 service authorities could use to track statistics of overall v0
20490 hidden service usage.
20491 - Remove the obsolete "NoPublish" option; it has been flagged
20492 as obsolete and has produced a warning since 0.1.1.18-rc.
20493 - Caches no longer download and serve v2 networkstatus documents
20494 unless FetchV2Networkstatus flag is set: these documents haven't
20495 haven't been used by clients or relays since 0.2.0.x. Resolves
20498 o Deprecated and removed features (controller):
20499 - The controller no longer accepts the old obsolete "addr-mappings/"
20500 or "unregistered-servers-" GETINFO values.
20501 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
20502 always on; using them is necessary for correct forward-compatible
20505 o Deprecated and removed features (misc):
20506 - Hidden services no longer publish version 0 descriptors, and clients
20507 do not request or use version 0 descriptors. However, the old hidden
20508 service authorities still accept and serve version 0 descriptors
20509 when contacted by older hidden services/clients.
20510 - Remove undocumented option "-F" from tor-resolve: it hasn't done
20511 anything since 0.2.1.16-rc.
20512 - Remove everything related to building the expert bundle for OS X.
20513 It has confused many users, doesn't work right on OS X 10.6,
20514 and is hard to get rid of once installed. Resolves bug 1274.
20515 - Remove support for .noconnect style addresses. Nobody was using
20516 them, and they provided another avenue for detecting Tor users
20517 via application-level web tricks.
20518 - When we fixed bug 1038 we had to put in a restriction not to send
20519 RELAY_EARLY cells on rend circuits. This was necessary as long
20520 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
20521 active. Now remove this obsolete check. Resolves bug 2081.
20522 - Remove workaround code to handle directory responses from servers
20523 that had bug 539 (they would send HTTP status 503 responses _and_
20524 send a body too). Since only server versions before
20525 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
20526 keep the workaround in place.
20527 - Remove the old 'fuzzy time' logic. It was supposed to be used for
20528 handling calculations where we have a known amount of clock skew and
20529 an allowed amount of unknown skew. But we only used it in three
20530 places, and we never adjusted the known/unknown skew values. This is
20531 still something we might want to do someday, but if we do, we'll
20532 want to do it differently.
20533 - Remove the "--enable-iphone" option to ./configure. According to
20534 reports from Marco Bonetti, Tor builds fine without any special
20535 tweaking on recent iPhone SDK versions.
20538 Changes in version 0.2.1.30 - 2011-02-23
20539 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
20540 change is a slight tweak to Tor's TLS handshake that makes relays
20541 and bridges that run this new version reachable from Iran again.
20542 We don't expect this tweak will win the arms race long-term, but it
20543 buys us time until we roll out a better solution.
20546 - Stop sending a CLOCK_SKEW controller status event whenever
20547 we fetch directory information from a relay that has a wrong clock.
20548 Instead, only inform the controller when it's a trusted authority
20549 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
20550 the rest of bug 1074.
20551 - Fix a bounds-checking error that could allow an attacker to
20552 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
20553 Found by "piebeer".
20554 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
20555 Tor would ignore their RelayBandwidthBurst setting,
20556 potentially using more bandwidth than expected. Bugfix on
20557 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
20558 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
20559 hidserv" in her torrc. The 'hidserv' argument never controlled
20560 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
20563 - Adjust our TLS Diffie-Hellman parameters to match those used by
20565 - Update to the February 1 2011 Maxmind GeoLite Country database.
20568 - Check for and reject overly long directory certificates and
20569 directory tokens before they have a chance to hit any assertions.
20570 Bugfix on 0.2.1.28. Found by "doorss".
20571 - Bring the logic that gathers routerinfos and assesses the
20572 acceptability of circuits into line. This prevents a Tor OP from
20573 getting locked in a cycle of choosing its local OR as an exit for a
20574 path (due to a .exit request) and then rejecting the circuit because
20575 its OR is not listed yet. It also prevents Tor clients from using an
20576 OR running in the same instance as an exit (due to a .exit request)
20577 if the OR does not meet the same requirements expected of an OR
20578 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
20580 o Packaging changes:
20581 - Stop shipping the Tor specs files and development proposal documents
20582 in the tarball. They are now in a separate git repository at
20583 git://git.torproject.org/torspec.git
20584 - Do not include Git version tags as though they are SVN tags when
20585 generating a tarball from inside a repository that has switched
20586 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
20589 Changes in version 0.2.1.29 - 2011-01-15
20590 Tor 0.2.1.29 continues our recent code security audit work. The main
20591 fix resolves a remote heap overflow vulnerability that can allow remote
20592 code execution. Other fixes address a variety of assert and crash bugs,
20593 most of which we think are hard to exploit remotely.
20595 o Major bugfixes (security):
20596 - Fix a heap overflow bug where an adversary could cause heap
20597 corruption. This bug probably allows remote code execution
20598 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
20600 - Prevent a denial-of-service attack by disallowing any
20601 zlib-compressed data whose compression factor is implausibly
20602 high. Fixes part of bug 2324; reported by "doorss".
20603 - Zero out a few more keys in memory before freeing them. Fixes
20604 bug 2384 and part of bug 2385. These key instances found by
20605 "cypherpunks", based on Andrew Case's report about being able
20606 to find sensitive data in Tor's memory space if you have enough
20607 permissions. Bugfix on 0.0.2pre9.
20609 o Major bugfixes (crashes):
20610 - Prevent calls to Libevent from inside Libevent log handlers.
20611 This had potential to cause a nasty set of crashes, especially
20612 if running Libevent with debug logging enabled, and running
20613 Tor with a controller watching for low-severity log messages.
20614 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
20615 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
20616 underflow errors there too. Fixes the other part of bug 2324.
20617 - Fix a bug where we would assert if we ever had a
20618 cached-descriptors.new file (or another file read directly into
20619 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
20620 on 0.2.1.25. Found by doorss.
20621 - Fix some potential asserts and parsing issues with grossly
20622 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
20625 o Minor bugfixes (other):
20626 - Fix a bug with handling misformed replies to reverse DNS lookup
20627 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
20628 bug reported by doorss.
20629 - Fix compilation on mingw when a pthreads compatibility library
20630 has been installed. (We don't want to use it, so we shouldn't
20631 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
20632 - Fix a bug where we would declare that we had run out of virtual
20633 addresses when the address space was only half-exhausted. Bugfix
20635 - Correctly handle the case where AutomapHostsOnResolve is set but
20636 no virtual addresses are available. Fixes bug 2328; bugfix on
20637 0.1.2.1-alpha. Bug found by doorss.
20638 - Correctly handle wrapping around when we run out of virtual
20639 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
20642 - Update to the January 1 2011 Maxmind GeoLite Country database.
20643 - Introduce output size checks on all of our decryption functions.
20646 - Tor does not build packages correctly with Automake 1.6 and earlier;
20647 added a check to Makefile.am to make sure that we're building with
20648 Automake 1.7 or later.
20649 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
20650 because we built it with a too-old version of automake. Thus that
20651 release broke ./configure --enable-openbsd-malloc, which is popular
20652 among really fast exit relays on Linux.
20655 Changes in version 0.2.1.28 - 2010-12-17
20656 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
20657 exploitable bugs. We also took this opportunity to change the IP address
20658 for one of our directory authorities, and to update the geoip database
20662 - Fix a remotely exploitable bug that could be used to crash instances
20663 of Tor remotely by overflowing on the heap. Remote-code execution
20664 hasn't been confirmed, but can't be ruled out. Everyone should
20665 upgrade. Bugfix on the 0.1.1 series and later.
20667 o Directory authority changes:
20668 - Change IP address and ports for gabelmoo (v3 directory authority).
20671 - Update to the December 1 2010 Maxmind GeoLite Country database.
20674 Changes in version 0.2.1.27 - 2010-11-23
20675 Yet another OpenSSL security patch broke its compatibility with Tor:
20676 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
20677 also took this opportunity to fix several crash bugs, integrate a new
20678 directory authority, and update the bundled GeoIP database.
20681 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
20682 No longer set the tlsext_host_name extension on server SSL objects;
20683 but continue to set it on client SSL objects. Our goal in setting
20684 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
20685 bugfix on 0.2.1.1-alpha.
20686 - Do not log messages to the controller while shrinking buffer
20687 freelists. Doing so would sometimes make the controller connection
20688 try to allocate a buffer chunk, which would mess up the internals
20689 of the freelist and cause an assertion failure. Fixes bug 1125;
20690 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
20691 - Learn our external IP address when we're a relay or bridge, even if
20692 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
20693 where we introduced bridge relays that don't need to publish to
20694 be useful. Fixes bug 2050.
20695 - Do even more to reject (and not just ignore) annotations on
20696 router descriptors received anywhere but from the cache. Previously
20697 we would ignore such annotations at first, but cache them to disk
20698 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
20699 - When you're using bridges and your network goes away and your
20700 bridges get marked as down, recover when you attempt a new socks
20701 connection (if the network is back), rather than waiting up to an
20702 hour to try fetching new descriptors for your bridges. Bugfix on
20703 0.2.0.3-alpha; fixes bug 1981.
20706 - Move to the November 2010 Maxmind GeoLite country db (rather
20707 than the June 2009 ip-to-country GeoIP db) for our statistics that
20708 count how many users relays are seeing from each country. Now we'll
20709 have more accurate data, especially for many African countries.
20711 o New directory authorities:
20712 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
20716 - Fix an assertion failure that could occur in directory caches or
20717 bridge users when using a very short voting interval on a testing
20718 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
20720 - Enforce multiplicity rules when parsing annotations. Bugfix on
20721 0.2.0.8-alpha. Found by piebeer.
20722 - Allow handshaking OR connections to take a full KeepalivePeriod
20723 seconds to handshake. Previously, we would close them after
20724 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
20725 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
20727 - When building with --enable-gcc-warnings on OpenBSD, disable
20728 warnings in system headers. This makes --enable-gcc-warnings
20729 pass on OpenBSD 4.8.
20732 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
20733 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
20734 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
20735 Servers can start sending this code when enough clients recognize
20736 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
20737 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
20738 Patch from mingw-san.
20741 - Remove the old debian/ directory from the main Tor distribution.
20742 The official Tor-for-debian git repository lives at the URL
20743 https://git.torproject.org/debian/tor.git
20744 - Stop shipping the old doc/website/ directory in the tarball. We
20745 changed the website format in late 2010, and what we shipped in
20746 0.2.1.26 really wasn't that useful anyway.
20749 Changes in version 0.2.1.26 - 2010-05-02
20750 Tor 0.2.1.26 addresses the recent connection and memory overload
20751 problems we've been seeing on relays, especially relays with their
20752 DirPort open. If your relay has been crashing, or you turned it off
20753 because it used too many resources, give this release a try.
20755 This release also fixes yet another instance of broken OpenSSL libraries
20756 that was causing some relays to drop out of the consensus.
20759 - Teach relays to defend themselves from connection overload. Relays
20760 now close idle circuits early if it looks like they were intended
20761 for directory fetches. Relays are also more aggressive about closing
20762 TLS connections that have no circuits on them. Such circuits are
20763 unlikely to be re-used, and tens of thousands of them were piling
20764 up at the fast relays, causing the relays to run out of sockets
20765 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
20766 their directory fetches over TLS).
20767 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
20768 that claim to be earlier than 0.9.8m, but which have in reality
20769 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
20770 behavior. Possible fix for some cases of bug 1346.
20771 - Directory mirrors were fetching relay descriptors only from v2
20772 directory authorities, rather than v3 authorities like they should.
20773 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
20774 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
20777 - Finally get rid of the deprecated and now harmful notion of "clique
20778 mode", where directory authorities maintain TLS connections to
20782 - In the util/threads test, no longer free the test_mutex before all
20783 worker threads have finished. Bugfix on 0.2.1.6-alpha.
20784 - The master thread could starve the worker threads quite badly on
20785 certain systems, causing them to run only partially in the allowed
20786 window. This resulted in test failures. Now the master thread sleeps
20787 occasionally for a few microseconds while the two worker-threads
20788 compete for the mutex. Bugfix on 0.2.0.1-alpha.
20791 Changes in version 0.2.1.25 - 2010-03-16
20792 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
20793 prevent relays from guessing their IP address correctly. It also fixes
20794 several minor potential security bugs.
20797 - Fix a regression from our patch for bug 1244 that caused relays
20798 to guess their IP address incorrectly if they didn't set Address
20799 in their torrc and/or their address fails to resolve. Bugfix on
20800 0.2.1.23; fixes bug 1269.
20801 - When freeing a session key, zero it out completely. We only zeroed
20802 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
20803 patched by ekir. Fixes bug 1254.
20806 - Fix a dereference-then-NULL-check sequence when publishing
20807 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
20809 - Fix another dereference-then-NULL-check sequence. Bugfix on
20810 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
20811 - Make sure we treat potentially not NUL-terminated strings correctly.
20812 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
20815 Changes in version 0.2.1.24 - 2010-02-21
20816 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
20820 - Work correctly out-of-the-box with even more vendor-patched versions
20821 of OpenSSL. In particular, make it so Debian and OS X don't need
20822 customized patches to run/build.
20825 Changes in version 0.2.1.23 - 2010-02-13
20826 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
20827 again on the latest OS X, and updates the location of a directory
20830 o Major bugfixes (performance):
20831 - We were selecting our guards uniformly at random, and then weighting
20832 which of our guards we'd use uniformly at random. This imbalance
20833 meant that Tor clients were severely limited on throughput (and
20834 probably latency too) by the first hop in their circuit. Now we
20835 select guards weighted by currently advertised bandwidth. We also
20836 automatically discard guards picked using the old algorithm. Fixes
20837 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
20840 - Make Tor work again on the latest OS X: when deciding whether to
20841 use strange flags to turn TLS renegotiation on, detect the OpenSSL
20842 version at run-time, not compile time. We need to do this because
20843 Apple doesn't update its dev-tools headers when it updates its
20844 libraries in a security patch.
20845 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
20846 that could happen on 32-bit platforms with 64-bit time_t. Also fix
20847 a memory leak when requesting a hidden service descriptor we've
20848 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
20852 - Refactor resolve_my_address() to not use gethostbyname() anymore.
20853 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
20856 - Avoid a mad rush at the beginning of each month when each client
20857 rotates half of its guards. Instead we spread the rotation out
20858 throughout the month, but we still avoid leaving a precise timestamp
20859 in the state file about when we first picked the guard. Improves
20860 over the behavior introduced in 0.1.2.17.
20863 Changes in version 0.2.1.22 - 2010-01-19
20864 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
20865 authorities -- it would tell you its whole history of bridge descriptors
20866 if you make the right directory request. This stable update also
20867 rotates two of the seven v3 directory authority keys and locations.
20869 o Directory authority changes:
20870 - Rotate keys (both v3 identity and relay identity) for moria1
20874 - Stop bridge directory authorities from answering dbg-stability.txt
20875 directory queries, which would let people fetch a list of all
20876 bridge identities they track. Bugfix on 0.2.1.6-alpha.
20879 Changes in version 0.2.1.21 - 2009-12-21
20880 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
20881 library. If you use Tor on Linux / Unix and you're getting SSL
20882 renegotiation errors, upgrading should help. We also recommend an
20883 upgrade if you're an exit relay.
20886 - Work around a security feature in OpenSSL 0.9.8l that prevents our
20887 handshake from working unless we explicitly tell OpenSSL that we
20888 are using SSL renegotiation safely. We are, of course, but OpenSSL
20889 0.9.8l won't work unless we say we are.
20890 - Avoid crashing if the client is trying to upload many bytes and the
20891 circuit gets torn down at the same time, or if the flip side
20892 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
20895 - Do not refuse to learn about authority certs and v2 networkstatus
20896 documents that are older than the latest consensus. This bug might
20897 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
20898 Spotted and fixed by xmux.
20899 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
20900 trigger platform-specific option misparsing case found by Coverity
20902 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
20903 trigger assert. Fixes bug 1173.
20906 Changes in version 0.2.1.20 - 2009-10-15
20907 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
20908 services at once, prepares for more performance improvements, and
20909 fixes a bunch of smaller bugs.
20911 The Windows and OS X bundles also include a more recent Vidalia,
20912 and switch from Privoxy to Polipo.
20914 The OS X installers are now drag and drop. It's best to un-install
20915 Tor/Vidalia and then install this new bundle, rather than upgrade. If
20916 you want to upgrade, you'll need to update the paths for Tor and Polipo
20917 in the Vidalia Settings window.
20920 - Send circuit or stream sendme cells when our window has decreased
20921 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
20922 by Karsten when testing the "reduce circuit window" performance
20923 patch. Bugfix on the 54th commit on Tor -- from July 2002,
20924 before the release of Tor 0.0.0. This is the new winner of the
20926 - Fix a remotely triggerable memory leak when a consensus document
20927 contains more than one signature from the same voter. Bugfix on
20929 - Avoid segfault in rare cases when finishing an introduction circuit
20930 as a client and finding out that we don't have an introduction key
20931 for it. Fixes bug 1073. Reported by Aaron Swartz.
20934 - Tor now reads the "circwindow" parameter out of the consensus,
20935 and uses that value for its circuit package window rather than the
20936 default of 1000 cells. Begins the implementation of proposal 168.
20938 o New directory authorities:
20939 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
20941 - Move moria1 and tonga to alternate IP addresses.
20944 - Fix a signed/unsigned compile warning in 0.2.1.19.
20945 - Fix possible segmentation fault on directory authorities. Bugfix on
20947 - Fix an extremely rare infinite recursion bug that could occur if
20948 we tried to log a message after shutting down the log subsystem.
20949 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
20950 - Fix an obscure bug where hidden services on 64-bit big-endian
20951 systems might mis-read the timestamp in v3 introduce cells, and
20952 refuse to connect back to the client. Discovered by "rotor".
20953 Bugfix on 0.2.1.6-alpha.
20954 - We were triggering a CLOCK_SKEW controller status event whenever
20955 we connect via the v2 connection protocol to any relay that has
20956 a wrong clock. Instead, we should only inform the controller when
20957 it's a trusted authority that claims our clock is wrong. Bugfix
20958 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
20959 - We were telling the controller about CHECKING_REACHABILITY and
20960 REACHABILITY_FAILED status events whenever we launch a testing
20961 circuit or notice that one has failed. Instead, only tell the
20962 controller when we want to inform the user of overall success or
20963 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
20965 - Don't warn when we're using a circuit that ends with a node
20966 excluded in ExcludeExitNodes, but the circuit is not used to access
20967 the outside world. This should help fix bug 1090. Bugfix on
20969 - Work around a small memory leak in some versions of OpenSSL that
20970 stopped the memory used by the hostname TLS extension from being
20974 - Add a "getinfo status/accepted-server-descriptor" controller
20975 command, which is the recommended way for controllers to learn
20976 whether our server descriptor has been successfully received by at
20977 least on directory authority. Un-recommend good-server-descriptor
20978 getinfo and status events until we have a better design for them.
20981 Changes in version 0.2.1.19 - 2009-07-28
20982 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
20986 - Make accessing hidden services on 0.2.1.x work right again.
20987 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
20988 part of patch provided by "optimist".
20991 - When a relay/bridge is writing out its identity key fingerprint to
20992 the "fingerprint" file and to its logs, write it without spaces. Now
20993 it will look like the fingerprints in our bridges documentation,
20994 and confuse fewer users.
20997 - Relays no longer publish a new server descriptor if they change
20998 their MaxAdvertisedBandwidth config option but it doesn't end up
20999 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
21000 fixes bug 1026. Patch from Sebastian.
21001 - Avoid leaking memory every time we get a create cell but we have
21002 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
21003 fixes bug 1034. Reported by BarkerJr.
21006 Changes in version 0.2.1.18 - 2009-07-24
21007 Tor 0.2.1.18 lays the foundations for performance improvements,
21008 adds status events to help users diagnose bootstrap problems, adds
21009 optional authentication/authorization for hidden services, fixes a
21010 variety of potential anonymity problems, and includes a huge pile of
21011 other features and bug fixes.
21013 o Major features (clients):
21014 - Start sending "bootstrap phase" status events to the controller,
21015 so it can keep the user informed of progress fetching directory
21016 information and establishing circuits. Also inform the controller
21017 if we think we're stuck at a particular bootstrap phase. Implements
21019 - Clients replace entry guards that were chosen more than a few months
21020 ago. This change should significantly improve client performance,
21021 especially once more people upgrade, since relays that have been
21022 a guard for a long time are currently overloaded.
21023 - Network status consensus documents and votes now contain bandwidth
21024 information for each relay. Clients use the bandwidth values
21025 in the consensus, rather than the bandwidth values in each
21026 relay descriptor. This approach opens the door to more accurate
21027 bandwidth estimates once the directory authorities start doing
21028 active measurements. Implements part of proposal 141.
21030 o Major features (relays):
21031 - Disable and refactor some debugging checks that forced a linear scan
21032 over the whole server-side DNS cache. These accounted for over 50%
21033 of CPU time on a relatively busy exit node's gprof profile. Also,
21034 disable some debugging checks that appeared in exit node profile
21035 data. Found by Jacob.
21036 - New DirPortFrontPage option that takes an html file and publishes
21037 it as "/" on the DirPort. Now relay operators can provide a
21038 disclaimer without needing to set up a separate webserver. There's
21039 a sample disclaimer in contrib/tor-exit-notice.html.
21041 o Major features (hidden services):
21042 - Make it possible to build hidden services that only certain clients
21043 are allowed to connect to. This is enforced at several points,
21044 so that unauthorized clients are unable to send INTRODUCE cells
21045 to the service, or even (depending on the type of authentication)
21046 to learn introduction points. This feature raises the bar for
21047 certain kinds of active attacks against hidden services. Design
21048 and code by Karsten Loesing. Implements proposal 121.
21049 - Relays now store and serve v2 hidden service descriptors by default,
21050 i.e., the new default value for HidServDirectoryV2 is 1. This is
21051 the last step in proposal 114, which aims to make hidden service
21052 lookups more reliable.
21054 o Major features (path selection):
21055 - ExitNodes and Exclude*Nodes config options now allow you to restrict
21056 by country code ("{US}") or IP address or address pattern
21057 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
21058 refinement to decide what config options should take priority if
21059 you ask to both use a particular node and exclude it.
21061 o Major features (misc):
21062 - When building a consensus, do not include routers that are down.
21063 This cuts down 30% to 40% on consensus size. Implements proposal
21065 - New TestingTorNetwork config option to allow adjustment of
21066 previously constant values that could slow bootstrapping. Implements
21067 proposal 135. Patch from Karsten.
21068 - Convert many internal address representations to optionally hold
21069 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
21070 elements. Make resolver code handle nameservers located at IPv6
21072 - More work on making our TLS handshake blend in: modify the list
21073 of ciphers advertised by OpenSSL in client mode to even more
21074 closely resemble a common web browser. We cheat a little so that
21075 we can advertise ciphers that the locally installed OpenSSL doesn't
21077 - Use the TLS1 hostname extension to more closely resemble browser
21080 o Security fixes (anonymity/entropy):
21081 - Never use a connection with a mismatched address to extend a
21082 circuit, unless that connection is canonical. A canonical
21083 connection is one whose address is authenticated by the router's
21084 identity key, either in a NETINFO cell or in a router descriptor.
21085 - Implement most of proposal 110: The first K cells to be sent
21086 along a circuit are marked as special "early" cells; only K "early"
21087 cells will be allowed. Once this code is universal, we can block
21088 certain kinds of denial-of-service attack by requiring that EXTEND
21089 commands must be sent using an "early" cell.
21090 - Resume using OpenSSL's RAND_poll() for better (and more portable)
21091 cross-platform entropy collection again. We used to use it, then
21092 stopped using it because of a bug that could crash systems that
21093 called RAND_poll when they had a lot of fds open. It looks like the
21094 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
21095 at startup, and to call RAND_poll() when we reseed later only if
21096 we have a non-buggy OpenSSL version.
21097 - When the client is choosing entry guards, now it selects at most
21098 one guard from a given relay family. Otherwise we could end up with
21099 all of our entry points into the network run by the same operator.
21100 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
21101 - Do not use or believe expired v3 authority certificates. Patch
21102 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
21103 - Drop begin cells to a hidden service if they come from the middle
21104 of a circuit. Patch from lark.
21105 - When we erroneously receive two EXTEND cells for the same circuit
21106 ID on the same connection, drop the second. Patch from lark.
21107 - Authorities now vote for the Stable flag for any router whose
21108 weighted MTBF is at least 5 days, regardless of the mean MTBF.
21109 - Clients now never report any stream end reason except 'MISC'.
21110 Implements proposal 148.
21112 o Major bugfixes (crashes):
21113 - Parse dates and IPv4 addresses in a locale- and libc-independent
21114 manner, to avoid platform-dependent behavior on malformed input.
21115 - Fix a crash that occurs on exit nodes when a nameserver request
21116 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
21117 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
21119 - Do not assume that a stack-allocated character array will be
21120 64-bit aligned on platforms that demand that uint64_t access is
21121 aligned. Possible fix for bug 604.
21122 - Resolve a very rare crash bug that could occur when the user forced
21123 a nameserver reconfiguration during the middle of a nameserver
21124 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
21125 - Avoid a "0 divided by 0" calculation when calculating router uptime
21126 at directory authorities. Bugfix on 0.2.0.8-alpha.
21127 - Fix an assertion bug in parsing policy-related options; possible fix
21129 - Rate-limit too-many-sockets messages: when they happen, they happen
21130 a lot and end up filling up the disk. Resolves bug 748.
21131 - Fix a race condition that could cause crashes or memory corruption
21132 when running as a server with a controller listening for log
21134 - Avoid crashing when we have a policy specified in a DirPolicy or
21135 SocksPolicy or ReachableAddresses option with ports set on it,
21136 and we re-load the policy. May fix bug 996.
21137 - Fix an assertion failure on 64-bit platforms when we allocated
21138 memory right up to the end of a memarea, then realigned the memory
21139 one step beyond the end. Fixes a possible cause of bug 930.
21140 - Protect the count of open sockets with a mutex, so we can't
21141 corrupt it when two threads are closing or opening sockets at once.
21142 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
21144 o Major bugfixes (clients):
21145 - Discard router descriptors as we load them if they are more than
21146 five days old. Otherwise if Tor is off for a long time and then
21147 starts with cached descriptors, it will try to use the onion keys
21148 in those obsolete descriptors when building circuits. Fixes bug 887.
21149 - When we choose to abandon a new entry guard because we think our
21150 older ones might be better, close any circuits pending on that
21151 new entry guard connection. This fix should make us recover much
21152 faster when our network is down and then comes back. Bugfix on
21153 0.1.2.8-beta; found by lodger.
21154 - When Tor clients restart after 1-5 days, they discard all their
21155 cached descriptors as too old, but they still use the cached
21156 consensus document. This approach is good for robustness, but
21157 bad for performance: since they don't know any bandwidths, they
21158 end up choosing at random rather than weighting their choice by
21159 speed. Fixed by the above feature of putting bandwidths in the
21162 o Major bugfixes (relays):
21163 - Relays were falling out of the networkstatus consensus for
21164 part of a day if they changed their local config but the
21165 authorities discarded their new descriptor as "not sufficiently
21166 different". Now directory authorities accept a descriptor as changed
21167 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
21168 patch by Sebastian.
21169 - Ensure that two circuits can never exist on the same connection
21170 with the same circuit ID, even if one is marked for close. This
21171 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
21172 - Directory authorities were neglecting to mark relays down in their
21173 internal histories if the relays fall off the routerlist without
21174 ever being found unreachable. So there were relays in the histories
21175 that haven't been seen for eight months, and are listed as being
21176 up for eight months. This wreaked havoc on the "median wfu" and
21177 "median mtbf" calculations, in turn making Guard and Stable flags
21178 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
21181 o Major bugfixes (hidden services):
21182 - When establishing a hidden service, introduction points that
21183 originate from cannibalized circuits were completely ignored
21184 and not included in rendezvous service descriptors. This might
21185 have been another reason for delay in making a hidden service
21186 available. Bugfix from long ago (0.0.9.x?)
21188 o Major bugfixes (memory and resource management):
21189 - Fixed some memory leaks -- some quite frequent, some almost
21190 impossible to trigger -- based on results from Coverity.
21191 - Speed up parsing and cut down on memory fragmentation by using
21192 stack-style allocations for parsing directory objects. Previously,
21193 this accounted for over 40% of allocations from within Tor's code
21194 on a typical directory cache.
21195 - Use a Bloom filter rather than a digest-based set to track which
21196 descriptors we need to keep around when we're cleaning out old
21197 router descriptors. This speeds up the computation significantly,
21198 and may reduce fragmentation.
21200 o New/changed config options:
21201 - Now NodeFamily and MyFamily config options allow spaces in
21202 identity fingerprints, so it's easier to paste them in.
21203 Suggested by Lucky Green.
21204 - Allow ports 465 and 587 in the default exit policy again. We had
21205 rejected them in 0.1.0.15, because back in 2005 they were commonly
21206 misconfigured and ended up as spam targets. We hear they are better
21207 locked down these days.
21208 - Make TrackHostExit mappings expire a while after their last use, not
21209 after their creation. Patch from Robert Hogan.
21210 - Add an ExcludeExitNodes option so users can list a set of nodes
21211 that should be be excluded from the exit node position, but
21212 allowed elsewhere. Implements proposal 151.
21213 - New --hush command-line option similar to --quiet. While --quiet
21214 disables all logging to the console on startup, --hush limits the
21215 output to messages of warning and error severity.
21216 - New configure/torrc options (--enable-geoip-stats,
21217 DirRecordUsageByCountry) to record how many IPs we've served
21218 directory info to in each country code, how many status documents
21219 total we've sent to each country code, and what share of the total
21220 directory requests we should expect to see.
21221 - Make outbound DNS packets respect the OutboundBindAddress setting.
21222 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
21223 - Allow separate log levels to be configured for different logging
21224 domains. For example, this allows one to log all notices, warnings,
21225 or errors, plus all memory management messages of level debug or
21226 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
21227 - Update to the "June 3 2009" ip-to-country file.
21229 o Minor features (relays):
21230 - Raise the minimum rate limiting to be a relay from 20000 bytes
21231 to 20480 bytes (aka 20KB/s), to match our documentation. Also
21232 update directory authorities so they always assign the Fast flag
21233 to relays with 20KB/s of capacity. Now people running relays won't
21234 suddenly find themselves not seeing any use, if the network gets
21236 - If we're a relay and we change our IP address, be more verbose
21237 about the reason that made us change. Should help track down
21238 further bugs for relays on dynamic IP addresses.
21239 - Exit servers can now answer resolve requests for ip6.arpa addresses.
21240 - Implement most of Proposal 152: allow specialized servers to permit
21241 single-hop circuits, and clients to use those servers to build
21242 single-hop circuits when using a specialized controller. Patch
21243 from Josh Albrecht. Resolves feature request 768.
21244 - When relays do their initial bandwidth measurement, don't limit
21245 to just our entry guards for the test circuits. Otherwise we tend
21246 to have multiple test circuits going through a single entry guard,
21247 which makes our bandwidth test less accurate. Fixes part of bug 654;
21248 patch contributed by Josh Albrecht.
21250 o Minor features (directory authorities):
21251 - Try not to open more than one descriptor-downloading connection
21252 to an authority at once. This should reduce load on directory
21253 authorities. Fixes bug 366.
21254 - Add cross-certification to newly generated certificates, so that
21255 a signing key is enough information to look up a certificate. Start
21256 serving certificates by <identity digest, signing key digest>
21257 pairs. Implements proposal 157.
21258 - When a directory authority downloads a descriptor that it then
21259 immediately rejects, do not retry downloading it right away. Should
21260 save some bandwidth on authorities. Fix for bug 888. Patch by
21262 - Directory authorities now serve a /tor/dbg-stability.txt URL to
21263 help debug WFU and MTBF calculations.
21264 - In directory authorities' approved-routers files, allow
21265 fingerprints with or without space.
21267 o Minor features (directory mirrors):
21268 - When a download gets us zero good descriptors, do not notify
21269 Tor that new directory information has arrived.
21270 - Servers support a new URL scheme for consensus downloads that
21271 allows the client to specify which authorities are trusted.
21272 The server then only sends the consensus if the client will trust
21273 it. Otherwise a 404 error is sent back. Clients use this
21274 new scheme when the server supports it (meaning it's running
21275 0.2.1.1-alpha or later). Implements proposal 134.
21277 o Minor features (bridges):
21278 - If the bridge config line doesn't specify a port, assume 443.
21279 This makes bridge lines a bit smaller and easier for users to
21281 - If we're using bridges and our network goes away, be more willing
21282 to forgive our bridges and try again when we get an application
21285 o Minor features (hidden services):
21286 - When the client launches an introduction circuit, retry with a
21287 new circuit after 30 seconds rather than 60 seconds.
21288 - Launch a second client-side introduction circuit in parallel
21289 after a delay of 15 seconds (based on work by Christian Wilms).
21290 - Hidden services start out building five intro circuits rather
21291 than three, and when the first three finish they publish a service
21292 descriptor using those. Now we publish our service descriptor much
21293 faster after restart.
21294 - Drop the requirement to have an open dir port for storing and
21295 serving v2 hidden service descriptors.
21297 o Minor features (build and packaging):
21298 - On Linux, use the prctl call to re-enable core dumps when the User
21300 - Try to make sure that the version of Libevent we're running with
21301 is binary-compatible with the one we built with. May address bug
21303 - Add a new --enable-local-appdata configuration switch to change
21304 the default location of the datadir on win32 from APPDATA to
21305 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
21306 entirely. Patch from coderman.
21307 - Build correctly against versions of OpenSSL 0.9.8 or later that
21308 are built without support for deprecated functions.
21309 - On platforms with a maximum syslog string length, truncate syslog
21310 messages to that length ourselves, rather than relying on the
21311 system to do it for us.
21312 - Automatically detect MacOSX versions earlier than 10.4.0, and
21313 disable kqueue from inside Tor when running with these versions.
21314 We previously did this from the startup script, but that was no
21315 help to people who didn't use the startup script. Resolves bug 863.
21316 - Build correctly when configured to build outside the main source
21317 path. Patch from Michael Gold.
21318 - Disable GCC's strict alias optimization by default, to avoid the
21319 likelihood of its introducing subtle bugs whenever our code violates
21320 the letter of C99's alias rules.
21321 - Change the contrib/tor.logrotate script so it makes the new
21322 logs as "_tor:_tor" rather than the default, which is generally
21323 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
21324 - Change our header file guard macros to be less likely to conflict
21325 with system headers. Adam Langley noticed that we were conflicting
21326 with log.h on Android.
21327 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
21328 and stop using a warning that had become unfixably verbose under
21330 - Use a lockfile to make sure that two Tor processes are not
21331 simultaneously running with the same datadir.
21332 - Allow OpenSSL to use dynamic locks if it wants.
21333 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
21335 o Minor features (controllers):
21336 - When generating circuit events with verbose nicknames for
21337 controllers, try harder to look up nicknames for routers on a
21338 circuit. (Previously, we would look in the router descriptors we had
21339 for nicknames, but not in the consensus.) Partial fix for bug 941.
21340 - New controller event NEWCONSENSUS that lists the networkstatus
21341 lines for every recommended relay. Now controllers like Torflow
21342 can keep up-to-date on which relays they should be using.
21343 - New controller event "clients_seen" to report a geoip-based summary
21344 of which countries we've seen clients from recently. Now controllers
21345 like Vidalia can show bridge operators that they're actually making
21347 - Add a 'getinfo status/clients-seen' controller command, in case
21348 controllers want to hear clients_seen events but connect late.
21349 - New CONSENSUS_ARRIVED event to note when a new consensus has
21350 been fetched and validated.
21351 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
21352 controllers to prevent SIGHUP from reloading the configuration.
21354 - Return circuit purposes in response to GETINFO circuit-status.
21356 - Serve the latest v3 networkstatus consensus via the control
21357 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
21358 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
21359 controller can query our current bootstrap state in case it attaches
21360 partway through and wants to catch up.
21361 - Provide circuit purposes along with circuit events to the controller.
21363 o Minor features (tools):
21364 - Do not have tor-resolve automatically refuse all .onion addresses;
21365 if AutomapHostsOnResolve is set in your torrc, this will work fine.
21366 - Add a -p option to tor-resolve for specifying the SOCKS port: some
21367 people find host:port too confusing.
21368 - Print the SOCKS5 error message string as well as the error code
21369 when a tor-resolve request fails. Patch from Jacob.
21371 o Minor bugfixes (memory and resource management):
21372 - Clients no longer cache certificates for authorities they do not
21373 recognize. Bugfix on 0.2.0.9-alpha.
21374 - Do not use C's stdio library for writing to log files. This will
21375 improve logging performance by a minute amount, and will stop
21376 leaking fds when our disk is full. Fixes bug 861.
21377 - Stop erroneous use of O_APPEND in cases where we did not in fact
21378 want to re-seek to the end of a file before every last write().
21379 - Fix a small alignment and memory-wasting bug on buffer chunks.
21381 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
21382 to avoid unused RAM in buffer chunks and memory pools.
21383 - Reduce the default smartlist size from 32 to 16; it turns out that
21384 most smartlists hold around 8-12 elements tops.
21385 - Make dumpstats() log the fullness and size of openssl-internal
21387 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
21388 patch to their OpenSSL, turn it on to save memory on servers. This
21389 patch will (with any luck) get included in a mainline distribution
21391 - Fix a memory leak when v3 directory authorities load their keys
21392 and cert from disk. Bugfix on 0.2.0.1-alpha.
21393 - Stop using malloc_usable_size() to use more area than we had
21394 actually allocated: it was safe, but made valgrind really unhappy.
21395 - Make the assert_circuit_ok() function work correctly on circuits that
21396 have already been marked for close.
21397 - Fix uninitialized size field for memory area allocation: may improve
21398 memory performance during directory parsing.
21400 o Minor bugfixes (clients):
21401 - Stop reloading the router list from disk for no reason when we
21402 run out of reachable directory mirrors. Once upon a time reloading
21403 it would set the 'is_running' flag back to 1 for them. It hasn't
21404 done that for a long time.
21405 - When we had picked an exit node for a connection, but marked it as
21406 "optional", and it turned out we had no onion key for the exit,
21407 stop wanting that exit and try again. This situation may not
21408 be possible now, but will probably become feasible with proposal
21409 158. Spotted by rovv. Fixes another case of bug 752.
21410 - Fix a bug in address parsing that was preventing bridges or hidden
21411 service targets from being at IPv6 addresses.
21412 - Do not remove routers as too old if we do not have any consensus
21413 document. Bugfix on 0.2.0.7-alpha.
21414 - When an exit relay resolves a stream address to a local IP address,
21415 do not just keep retrying that same exit relay over and
21416 over. Instead, just close the stream. Addresses bug 872. Bugfix
21417 on 0.2.0.32. Patch from rovv.
21418 - Made Tor a little less aggressive about deleting expired
21419 certificates. Partial fix for bug 854.
21420 - Treat duplicate certificate fetches as failures, so that we do
21421 not try to re-fetch an expired certificate over and over and over.
21422 - Do not say we're fetching a certificate when we'll in fact skip it
21423 because of a pending download.
21424 - If we have correct permissions on $datadir, we complain to stdout
21425 and fail to start. But dangerous permissions on
21426 $datadir/cached-status/ would cause us to open a log and complain
21427 there. Now complain to stdout and fail to start in both cases. Fixes
21428 bug 820, reported by seeess.
21430 o Minor bugfixes (bridges):
21431 - When we made bridge authorities stop serving bridge descriptors over
21432 unencrypted links, we also broke DirPort reachability testing for
21433 bridges. So bridges with a non-zero DirPort were printing spurious
21434 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
21435 - Don't allow a bridge to publish its router descriptor to a
21436 non-bridge directory authority. Fixes part of bug 932.
21437 - When we change to or from being a bridge, reset our counts of
21438 client usage by country. Fixes bug 932.
21440 o Minor bugfixes (relays):
21441 - Log correct error messages for DNS-related network errors on
21443 - Actually return -1 in the error case for read_bandwidth_usage().
21444 Harmless bug, since we currently don't care about the return value
21445 anywhere. Bugfix on 0.2.0.9-alpha.
21446 - Provide a more useful log message if bug 977 (related to buffer
21447 freelists) ever reappears, and do not crash right away.
21448 - We were already rejecting relay begin cells with destination port
21449 of 0. Now also reject extend cells with destination port or address
21450 of 0. Suggested by lark.
21451 - When we can't transmit a DNS request due to a network error, retry
21452 it after a while, and eventually transmit a failing response to
21453 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
21454 - Solve a bug that kept hardware crypto acceleration from getting
21455 enabled when accounting was turned on. Fixes bug 907. Bugfix on
21457 - When a canonical connection appears later in our internal list
21458 than a noncanonical one for a given OR ID, always use the
21459 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
21461 - Avoid some nasty corner cases in the logic for marking connections
21462 as too old or obsolete or noncanonical for circuits. Partial
21464 - Fix another interesting corner-case of bug 891 spotted by rovv:
21465 Previously, if two hosts had different amounts of clock drift, and
21466 one of them created a new connection with just the wrong timing,
21467 the other might decide to deprecate the new connection erroneously.
21468 Bugfix on 0.1.1.13-alpha.
21469 - If one win32 nameserver fails to get added, continue adding the
21470 rest, and don't automatically fail.
21471 - Fix a bug where an unreachable relay would establish enough
21472 reachability testing circuits to do a bandwidth test -- if
21473 we already have a connection to the middle hop of the testing
21474 circuit, then it could establish the last hop by using the existing
21475 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
21476 circuits no longer use entry guards in 0.2.1.3-alpha.
21478 o Minor bugfixes (directory authorities):
21479 - Limit uploaded directory documents to be 16M rather than 500K.
21480 The directory authorities were refusing v3 consensus votes from
21481 other authorities, since the votes are now 504K. Fixes bug 959;
21482 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
21483 - Directory authorities should never send a 503 "busy" response to
21484 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
21486 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
21487 headers. Bugfix on 0.2.0.10-alpha.
21489 o Minor bugfixes (hidden services):
21490 - When we can't find an intro key for a v2 hidden service descriptor,
21491 fall back to the v0 hidden service descriptor and log a bug message.
21492 Workaround for bug 1024.
21493 - In very rare situations new hidden service descriptors were
21494 published earlier than 30 seconds after the last change to the
21495 service. (We currently think that a hidden service descriptor
21496 that's been stable for 30 seconds is worth publishing.)
21497 - If a hidden service sends us an END cell, do not consider
21498 retrying the connection; just close it. Patch from rovv.
21499 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
21500 service directories if they have no advertised dir port. Bugfix
21503 o Minor bugfixes (tools):
21504 - In the torify(1) manpage, mention that tsocks will leak your
21507 o Minor bugfixes (controllers):
21508 - If the controller claimed responsibility for a stream, but that
21509 stream never finished making its connection, it would live
21510 forever in circuit_wait state. Now we close it after SocksTimeout
21511 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
21512 - Make DNS resolved controller events into "CLOSED", not
21513 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
21515 - The control port would close the connection before flushing long
21516 replies, such as the network consensus, if a QUIT command was issued
21517 before the reply had completed. Now, the control port flushes all
21518 pending replies before closing the connection. Also fix a spurious
21519 warning when a QUIT command is issued after a malformed or rejected
21520 AUTHENTICATE command, but before the connection was closed. Patch
21521 by Marcus Griep. Fixes bugs 1015 and 1016.
21522 - Fix a bug that made stream bandwidth get misreported to the
21525 o Deprecated and removed features:
21526 - The old "tor --version --version" command, which would print out
21527 the subversion "Id" of most of the source files, is now removed. It
21528 turned out to be less useful than we'd expected, and harder to
21530 - RedirectExits has been removed. It was deprecated since
21532 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
21533 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
21534 - Cell pools are now always enabled; --disable-cell-pools is ignored.
21535 - Directory mirrors no longer fetch the v1 directory or
21536 running-routers files. They are obsolete, and nobody asks for them
21537 anymore. This is the first step to making v1 authorities obsolete.
21538 - Take out the TestVia config option, since it was a workaround for
21539 a bug that was fixed in Tor 0.1.1.21.
21540 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
21541 HiddenServiceExcludeNodes as obsolete: they never worked properly,
21542 and nobody seems to be using them. Fixes bug 754. Bugfix on
21543 0.1.0.1-rc. Patch from Christian Wilms.
21544 - Remove all backward-compatibility code for relays running
21545 versions of Tor so old that they no longer work at all on the
21548 o Code simplifications and refactoring:
21549 - Tool-assisted documentation cleanup. Nearly every function or
21550 static variable in Tor should have its own documentation now.
21551 - Rename the confusing or_is_obsolete field to the more appropriate
21552 is_bad_for_new_circs, and move it to or_connection_t where it
21554 - Move edge-only flags from connection_t to edge_connection_t: not
21555 only is this better coding, but on machines of plausible alignment,
21556 it should save 4-8 bytes per connection_t. "Every little bit helps."
21557 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
21558 for consistency; keep old option working for backward compatibility.
21559 - Simplify the code for finding connections to use for a circuit.
21560 - Revise the connection_new functions so that a more typesafe variant
21561 exists. This will work better with Coverity, and let us find any
21562 actual mistakes we're making here.
21563 - Refactor unit testing logic so that dmalloc can be used sensibly
21564 with unit tests to check for memory leaks.
21565 - Move all hidden-service related fields from connection and circuit
21566 structure to substructures: this way they won't eat so much memory.
21567 - Squeeze 2-5% out of client performance (according to oprofile) by
21568 improving the implementation of some policy-manipulation functions.
21569 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
21570 be more efficient. Formerly it was quadratic in the number of
21571 servers; now it should be linear. Fixes bug 509.
21572 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
21573 and n_conn_id_digest fields into a separate structure that's
21574 only needed when the circuit has not yet attached to an n_conn.
21575 - Optimize out calls to time(NULL) that occur for every IO operation,
21576 or for every cell. On systems like Windows where time() is a
21577 slow syscall, this fix will be slightly helpful.
21580 Changes in version 0.2.0.35 - 2009-06-24
21582 - Avoid crashing in the presence of certain malformed descriptors.
21583 Found by lark, and by automated fuzzing.
21584 - Fix an edge case where a malicious exit relay could convince a
21585 controller that the client's DNS question resolves to an internal IP
21586 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
21589 - Finally fix the bug where dynamic-IP relays disappear when their
21590 IP address changes: directory mirrors were mistakenly telling
21591 them their old address if they asked via begin_dir, so they
21592 never got an accurate answer about their new address, so they
21593 just vanished after a day. For belt-and-suspenders, relays that
21594 don't set Address in their config now avoid using begin_dir for
21595 all direct connections. Should fix bugs 827, 883, and 900.
21596 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
21597 that would occur on some exit nodes when DNS failures and timeouts
21598 occurred in certain patterns. Fix for bug 957.
21601 - When starting with a cache over a few days old, do not leak
21602 memory for the obsolete router descriptors in it. Bugfix on
21603 0.2.0.33; fixes bug 672.
21604 - Hidden service clients didn't use a cached service descriptor that
21605 was older than 15 minutes, but wouldn't fetch a new one either,
21606 because there was already one in the cache. Now, fetch a v2
21607 descriptor unless the same descriptor was added to the cache within
21608 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
21611 Changes in version 0.2.0.34 - 2009-02-08
21612 Tor 0.2.0.34 features several more security-related fixes. You should
21613 upgrade, especially if you run an exit relay (remote crash) or a
21614 directory authority (remote infinite loop), or you're on an older
21615 (pre-XP) or not-recently-patched Windows (remote exploit).
21617 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
21618 have many known flaws, and nobody should be using them. You should
21619 upgrade. If you're using a Linux or BSD and its packages are obsolete,
21620 stop using those packages and upgrade anyway.
21623 - Fix an infinite-loop bug on handling corrupt votes under certain
21624 circumstances. Bugfix on 0.2.0.8-alpha.
21625 - Fix a temporary DoS vulnerability that could be performed by
21626 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
21627 - Avoid a potential crash on exit nodes when processing malformed
21628 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
21629 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
21630 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
21633 - Fix compilation on systems where time_t is a 64-bit integer.
21634 Patch from Matthias Drochner.
21635 - Don't consider expiring already-closed client connections. Fixes
21636 bug 893. Bugfix on 0.0.2pre20.
21639 Changes in version 0.2.0.33 - 2009-01-21
21640 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
21641 useful to users. It also finally fixes a bug where a relay or client
21642 that's been off for many days would take a long time to bootstrap.
21644 This update also fixes an important security-related bug reported by
21645 Ilja van Sprundel. You should upgrade. (We'll send out more details
21646 about the bug once people have had some time to upgrade.)
21649 - Fix a heap-corruption bug that may be remotely triggerable on
21650 some platforms. Reported by Ilja van Sprundel.
21653 - When a stream at an exit relay is in state "resolving" or
21654 "connecting" and it receives an "end" relay cell, the exit relay
21655 would silently ignore the end cell and not close the stream. If
21656 the client never closes the circuit, then the exit relay never
21657 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
21658 reported by "wood".
21659 - When sending CREATED cells back for a given circuit, use a 64-bit
21660 connection ID to find the right connection, rather than an addr:port
21661 combination. Now that we can have multiple OR connections between
21662 the same ORs, it is no longer possible to use addr:port to uniquely
21663 identify a connection.
21664 - Bridge relays that had DirPort set to 0 would stop fetching
21665 descriptors shortly after startup, and then briefly resume
21666 after a new bandwidth test and/or after publishing a new bridge
21667 descriptor. Bridge users that try to bootstrap from them would
21668 get a recent networkstatus but would get descriptors from up to
21669 18 hours earlier, meaning most of the descriptors were obsolete
21670 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
21671 - Prevent bridge relays from serving their 'extrainfo' document
21672 to anybody who asks, now that extrainfo docs include potentially
21673 sensitive aggregated client geoip summaries. Bugfix on
21675 - If the cached networkstatus consensus is more than five days old,
21676 discard it rather than trying to use it. In theory it could be
21677 useful because it lists alternate directory mirrors, but in practice
21678 it just means we spend many minutes trying directory mirrors that
21679 are long gone from the network. Also discard router descriptors as
21680 we load them if they are more than five days old, since the onion
21681 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
21684 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
21685 could make gcc generate non-functional binary search code. Bugfix
21687 - Build correctly on platforms without socklen_t.
21688 - Compile without warnings on solaris.
21689 - Avoid potential crash on internal error during signature collection.
21690 Fixes bug 864. Patch from rovv.
21691 - Correct handling of possible malformed authority signing key
21692 certificates with internal signature types. Fixes bug 880.
21693 Bugfix on 0.2.0.3-alpha.
21694 - Fix a hard-to-trigger resource leak when logging credential status.
21696 - When we can't initialize DNS because the network is down, do not
21697 automatically stop Tor from starting. Instead, we retry failed
21698 dns_init() every 10 minutes, and change the exit policy to reject
21699 *:* until one succeeds. Fixes bug 691.
21700 - Use 64 bits instead of 32 bits for connection identifiers used with
21701 the controller protocol, to greatly reduce risk of identifier reuse.
21702 - When we're choosing an exit node for a circuit, and we have
21703 no pending streams, choose a good general exit rather than one that
21704 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
21705 - Fix another case of assuming, when a specific exit is requested,
21706 that we know more than the user about what hosts it allows.
21707 Fixes one case of bug 752. Patch from rovv.
21708 - Clip the MaxCircuitDirtiness config option to a minimum of 10
21709 seconds. Warn the user if lower values are given in the
21710 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
21711 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
21712 user if lower values are given in the configuration. Bugfix on
21713 0.1.1.17-rc. Patch by Sebastian.
21714 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
21715 the cache because we already had a v0 descriptor with the same ID.
21716 Bugfix on 0.2.0.18-alpha.
21717 - Fix a race condition when freeing keys shared between main thread
21718 and CPU workers that could result in a memory leak. Bugfix on
21719 0.1.0.1-rc. Fixes bug 889.
21720 - Send a valid END cell back when a client tries to connect to a
21721 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
21722 840. Patch from rovv.
21723 - Check which hops rendezvous stream cells are associated with to
21724 prevent possible guess-the-streamid injection attacks from
21725 intermediate hops. Fixes another case of bug 446. Based on patch
21727 - If a broken client asks a non-exit router to connect somewhere,
21728 do not even do the DNS lookup before rejecting the connection.
21729 Fixes another case of bug 619. Patch from rovv.
21730 - When a relay gets a create cell it can't decrypt (e.g. because it's
21731 using the wrong onion key), we were dropping it and letting the
21732 client time out. Now actually answer with a destroy cell. Fixes
21733 bug 904. Bugfix on 0.0.2pre8.
21735 o Minor bugfixes (hidden services):
21736 - Do not throw away existing introduction points on SIGHUP. Bugfix on
21737 0.0.6pre1. Patch by Karsten. Fixes bug 874.
21740 - Report the case where all signatures in a detached set are rejected
21741 differently than the case where there is an error handling the
21743 - When we realize that another process has modified our cached
21744 descriptors, print out a more useful error message rather than
21745 triggering an assertion. Fixes bug 885. Patch from Karsten.
21746 - Implement the 0x20 hack to better resist DNS poisoning: set the
21747 case on outgoing DNS requests randomly, and reject responses that do
21748 not match the case correctly. This logic can be disabled with the
21749 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
21750 of servers that do not reliably preserve case in replies. See
21751 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
21753 - Check DNS replies for more matching fields to better resist DNS
21755 - Never use OpenSSL compression: it wastes RAM and CPU trying to
21756 compress cells, which are basically all encrypted, compressed, or
21760 Changes in version 0.2.0.32 - 2008-11-20
21761 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
21762 packages (and maybe other packages) noticed by Theo de Raadt, fixes
21763 a smaller security flaw that might allow an attacker to access local
21764 services, further improves hidden service performance, and fixes a
21765 variety of other issues.
21768 - The "User" and "Group" config options did not clear the
21769 supplementary group entries for the Tor process. The "User" option
21770 is now more robust, and we now set the groups to the specified
21771 user's primary group. The "Group" option is now ignored. For more
21772 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
21773 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
21774 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
21775 - The "ClientDNSRejectInternalAddresses" config option wasn't being
21776 consistently obeyed: if an exit relay refuses a stream because its
21777 exit policy doesn't allow it, we would remember what IP address
21778 the relay said the destination address resolves to, even if it's
21779 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
21782 - Fix a DOS opportunity during the voting signature collection process
21783 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
21785 o Major bugfixes (hidden services):
21786 - When fetching v0 and v2 rendezvous service descriptors in parallel,
21787 we were failing the whole hidden service request when the v0
21788 descriptor fetch fails, even if the v2 fetch is still pending and
21789 might succeed. Similarly, if the last v2 fetch fails, we were
21790 failing the whole hidden service request even if a v0 fetch is
21791 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
21792 - When extending a circuit to a hidden service directory to upload a
21793 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
21794 requests failed, because the router descriptor has not been
21795 downloaded yet. In these cases, do not attempt to upload the
21796 rendezvous descriptor, but wait until the router descriptor is
21797 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
21798 descriptor from a hidden service directory for which the router
21799 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
21803 - Fix several infrequent memory leaks spotted by Coverity.
21804 - When testing for libevent functions, set the LDFLAGS variable
21805 correctly. Found by Riastradh.
21806 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
21807 bootstrapping with tunneled directory connections. Bugfix on
21808 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
21809 - When asked to connect to A.B.exit:80, if we don't know the IP for A
21810 and we know that server B rejects most-but-not all connections to
21811 port 80, we would previously reject the connection. Now, we assume
21812 the user knows what they were asking for. Fixes bug 752. Bugfix
21813 on 0.0.9rc5. Diagnosed by BarkerJr.
21814 - If we overrun our per-second write limits a little, count this as
21815 having used up our write allocation for the second, and choke
21816 outgoing directory writes. Previously, we had only counted this when
21817 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
21818 Bugfix on 0.2.0.x (??).
21819 - Remove the old v2 directory authority 'lefkada' from the default
21820 list. It has been gone for many months.
21821 - Stop doing unaligned memory access that generated bus errors on
21822 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
21823 - Make USR2 log-level switch take effect immediately. Bugfix on
21826 o Minor bugfixes (controller):
21827 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
21828 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
21831 Changes in version 0.2.0.31 - 2008-09-03
21832 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
21833 a big bug we're seeing where in rare cases traffic from one Tor stream
21834 gets mixed into another stream, and fixes a variety of smaller issues.
21837 - Make sure that two circuits can never exist on the same connection
21838 with the same circuit ID, even if one is marked for close. This
21839 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
21840 - Relays now reject risky extend cells: if the extend cell includes
21841 a digest of all zeroes, or asks to extend back to the relay that
21842 sent the extend cell, tear down the circuit. Ideas suggested
21844 - If not enough of our entry guards are available so we add a new
21845 one, we might use the new one even if it overlapped with the
21846 current circuit's exit relay (or its family). Anonymity bugfix
21847 pointed out by rovv.
21850 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
21851 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
21852 - Correctly detect the presence of the linux/netfilter_ipv4.h header
21853 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
21854 - Pick size of default geoip filename string correctly on windows.
21855 Fixes bug 806. Bugfix on 0.2.0.30.
21856 - Make the autoconf script accept the obsolete --with-ssl-dir
21857 option as an alias for the actually-working --with-openssl-dir
21858 option. Fix the help documentation to recommend --with-openssl-dir.
21859 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
21860 - When using the TransPort option on OpenBSD, and using the User
21861 option to change UID and drop privileges, make sure to open
21862 /dev/pf before dropping privileges. Fixes bug 782. Patch from
21863 Christopher Davis. Bugfix on 0.1.2.1-alpha.
21864 - Try to attach connections immediately upon receiving a RENDEZVOUS2
21865 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
21866 on the client side when connecting to a hidden service. Bugfix
21867 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
21868 - When closing an application-side connection because its circuit is
21869 getting torn down, generate the stream event correctly. Bugfix on
21870 0.1.2.x. Anonymous patch.
21873 Changes in version 0.2.0.30 - 2008-07-15
21874 This new stable release switches to a more efficient directory
21875 distribution design, adds features to make connections to the Tor
21876 network harder to block, allows Tor to act as a DNS proxy, adds separate
21877 rate limiting for relayed traffic to make it easier for clients to
21878 become relays, fixes a variety of potential anonymity problems, and
21879 includes the usual huge pile of other features and bug fixes.
21881 o New v3 directory design:
21882 - Tor now uses a new way to learn about and distribute information
21883 about the network: the directory authorities vote on a common
21884 network status document rather than each publishing their own
21885 opinion. Now clients and caches download only one networkstatus
21886 document to bootstrap, rather than downloading one for each
21887 authority. Clients only download router descriptors listed in
21888 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
21890 - Set up moria1, tor26, and dizum as v3 directory authorities
21891 in addition to being v2 authorities. Also add three new ones:
21892 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
21893 dannenberg (run by CCC).
21894 - Switch to multi-level keys for directory authorities: now their
21895 long-term identity key can be kept offline, and they periodically
21896 generate a new signing key. Clients fetch the "key certificates"
21897 to keep up to date on the right keys. Add a standalone tool
21898 "tor-gencert" to generate key certificates. Implements proposal 103.
21899 - Add a new V3AuthUseLegacyKey config option to make it easier for
21900 v3 authorities to change their identity keys if another bug like
21901 Debian's OpenSSL RNG flaw appears.
21902 - Authorities and caches fetch the v2 networkstatus documents
21903 less often, now that v3 is recommended.
21905 o Make Tor connections stand out less on the wire:
21906 - Use an improved TLS handshake designed by Steven Murdoch in proposal
21907 124, as revised in proposal 130. The new handshake is meant to
21908 be harder for censors to fingerprint, and it adds the ability
21909 to detect certain kinds of man-in-the-middle traffic analysis
21910 attacks. The new handshake format includes version negotiation for
21911 OR connections as described in proposal 105, which will allow us
21912 to improve Tor's link protocol more safely in the future.
21913 - Enable encrypted directory connections by default for non-relays,
21914 so censor tools that block Tor directory connections based on their
21915 plaintext patterns will no longer work. This means Tor works in
21916 certain censored countries by default again.
21917 - Stop including recognizeable strings in the commonname part of
21918 Tor's x509 certificates.
21920 o Implement bridge relays:
21921 - Bridge relays (or "bridges" for short) are Tor relays that aren't
21922 listed in the main Tor directory. Since there is no complete public
21923 list of them, even an ISP that is filtering connections to all the
21924 known Tor relays probably won't be able to block all the bridges.
21925 See doc/design-paper/blocking.pdf and proposal 125 for details.
21926 - New config option BridgeRelay that specifies you want to be a
21927 bridge relay rather than a normal relay. When BridgeRelay is set
21928 to 1, then a) you cache dir info even if your DirPort ins't on,
21929 and b) the default for PublishServerDescriptor is now "bridge"
21930 rather than "v2,v3".
21931 - New config option "UseBridges 1" for clients that want to use bridge
21932 relays instead of ordinary entry guards. Clients then specify
21933 bridge relays by adding "Bridge" lines to their config file. Users
21934 can learn about a bridge relay either manually through word of
21935 mouth, or by one of our rate-limited mechanisms for giving out
21936 bridge addresses without letting an attacker easily enumerate them
21937 all. See https://www.torproject.org/bridges for details.
21938 - Bridge relays behave like clients with respect to time intervals
21939 for downloading new v3 consensus documents -- otherwise they
21940 stand out. Bridge users now wait until the end of the interval,
21941 so their bridge relay will be sure to have a new consensus document.
21943 o Implement bridge directory authorities:
21944 - Bridge authorities are like normal directory authorities, except
21945 they don't serve a list of known bridges. Therefore users that know
21946 a bridge's fingerprint can fetch a relay descriptor for that bridge,
21947 including fetching updates e.g. if the bridge changes IP address,
21948 yet an attacker can't just fetch a list of all the bridges.
21949 - Set up Tonga as the default bridge directory authority.
21950 - Bridge authorities refuse to serve bridge descriptors or other
21951 bridge information over unencrypted connections (that is, when
21952 responding to direct DirPort requests rather than begin_dir cells.)
21953 - Bridge directory authorities do reachability testing on the
21954 bridges they know. They provide router status summaries to the
21955 controller via "getinfo ns/purpose/bridge", and also dump summaries
21956 to a file periodically, so we can keep internal stats about which
21957 bridges are functioning.
21958 - If bridge users set the UpdateBridgesFromAuthority config option,
21959 but the digest they ask for is a 404 on the bridge authority,
21960 they fall back to contacting the bridge directly.
21961 - Bridges always use begin_dir to publish their server descriptor to
21962 the bridge authority using an anonymous encrypted tunnel.
21963 - Early work on a "bridge community" design: if bridge authorities set
21964 the BridgePassword config option, they will serve a snapshot of
21965 known bridge routerstatuses from their DirPort to anybody who
21966 knows that password. Unset by default.
21967 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
21968 report sanitized aggregated summaries in their extra-info documents
21969 privately to the bridge authority, listing which countries are
21970 able to reach them. We hope this mechanism will let us learn when
21971 certain countries start trying to block bridges.
21972 - Bridge authorities write bridge descriptors to disk, so they can
21973 reload them after a reboot. They can also export the descriptors
21974 to other programs, so we can distribute them to blocked users via
21975 the BridgeDB interface, e.g. via https://bridges.torproject.org/
21976 and bridges@torproject.org.
21978 o Tor can be a DNS proxy:
21979 - The new client-side DNS proxy feature replaces the need for
21980 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
21981 for DNS requests on port 9999, use the Tor network to resolve them
21982 anonymously, and send the reply back like a regular DNS server.
21983 The code still only implements a subset of DNS.
21984 - Add a new AutomapHostsOnResolve option: when it is enabled, any
21985 resolve request for hosts matching a given pattern causes Tor to
21986 generate an internal virtual address mapping for that host. This
21987 allows DNSPort to work sensibly with hidden service users. By
21988 default, .exit and .onion addresses are remapped; the list of
21989 patterns can be reconfigured with AutomapHostsSuffixes.
21990 - Add an "-F" option to tor-resolve to force a resolve for a .onion
21991 address. Thanks to the AutomapHostsOnResolve option, this is no
21992 longer a completely silly thing to do.
21994 o Major features (relay usability):
21995 - New config options RelayBandwidthRate and RelayBandwidthBurst:
21996 a separate set of token buckets for relayed traffic. Right now
21997 relayed traffic is defined as answers to directory requests, and
21998 OR connections that don't have any local circuits on them. See
21999 proposal 111 for details.
22000 - Create listener connections before we setuid to the configured
22001 User and Group. Now non-Windows users can choose port values
22002 under 1024, start Tor as root, and have Tor bind those ports
22003 before it changes to another UID. (Windows users could already
22005 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
22006 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
22007 on "vserver" accounts. Patch from coderman.
22009 o Major features (directory authorities):
22010 - Directory authorities track weighted fractional uptime and weighted
22011 mean-time-between failures for relays. WFU is suitable for deciding
22012 whether a node is "usually up", while MTBF is suitable for deciding
22013 whether a node is "likely to stay up." We need both, because
22014 "usually up" is a good requirement for guards, while "likely to
22015 stay up" is a good requirement for long-lived connections.
22016 - Directory authorities use a new formula for selecting which relays
22017 to advertise as Guards: they must be in the top 7/8 in terms of
22018 how long we have known about them, and above the median of those
22019 nodes in terms of weighted fractional uptime.
22020 - Directory authorities use a new formula for selecting which relays
22021 to advertise as Stable: when we have 4 or more days of data, use
22022 median measured MTBF rather than median declared uptime. Implements
22024 - Directory authorities accept and serve "extra info" documents for
22025 routers. Routers now publish their bandwidth-history lines in the
22026 extra-info docs rather than the main descriptor. This step saves
22027 60% (!) on compressed router descriptor downloads. Servers upload
22028 extra-info docs to any authority that accepts them; directory
22029 authorities now allow multiple router descriptors and/or extra
22030 info documents to be uploaded in a single go. Authorities, and
22031 caches that have been configured to download extra-info documents,
22032 download them as needed. Implements proposal 104.
22033 - Authorities now list relays who have the same nickname as
22034 a different named relay, but list them with a new flag:
22035 "Unnamed". Now we can make use of relays that happen to pick the
22036 same nickname as a server that registered two years ago and then
22037 disappeared. Implements proposal 122.
22038 - Store routers in a file called cached-descriptors instead of in
22039 cached-routers. Initialize cached-descriptors from cached-routers
22040 if the old format is around. The new format allows us to store
22041 annotations along with descriptors, to record the time we received
22042 each descriptor, its source, and its purpose: currently one of
22043 general, controller, or bridge.
22045 o Major features (other):
22046 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
22047 Tor can warn and/or refuse connections to ports commonly used with
22048 vulnerable-plaintext protocols. Currently we warn on ports 23,
22049 109, 110, and 143, but we don't reject any. Based on proposal 129
22050 by Kevin Bauer and Damon McCoy.
22051 - Integrate Karsten Loesing's Google Summer of Code project to publish
22052 hidden service descriptors on a set of redundant relays that are a
22053 function of the hidden service address. Now we don't have to rely
22054 on three central hidden service authorities for publishing and
22055 fetching every hidden service descriptor. Implements proposal 114.
22056 - Allow tunnelled directory connections to ask for an encrypted
22057 "begin_dir" connection or an anonymized "uses a full Tor circuit"
22058 connection independently. Now we can make anonymized begin_dir
22059 connections for (e.g.) more secure hidden service posting and
22062 o Major bugfixes (crashes and assert failures):
22063 - Stop imposing an arbitrary maximum on the number of file descriptors
22064 used for busy servers. Bug reported by Olaf Selke; patch from
22066 - Avoid possible failures when generating a directory with routers
22067 with over-long versions strings, or too many flags set.
22068 - Fix a rare assert error when we're closing one of our threads:
22069 use a mutex to protect the list of logs, so we never write to the
22070 list as it's being freed. Fixes the very rare bug 575, which is
22071 kind of the revenge of bug 222.
22072 - Avoid segfault in the case where a badly behaved v2 versioning
22073 directory sends a signed networkstatus with missing client-versions.
22074 - When we hit an EOF on a log (probably because we're shutting down),
22075 don't try to remove the log from the list: just mark it as
22076 unusable. (Bulletproofs against bug 222.)
22078 o Major bugfixes (code security fixes):
22079 - Detect size overflow in zlib code. Reported by Justin Ferguson and
22081 - Rewrite directory tokenization code to never run off the end of
22082 a string. Fixes bug 455. Patch from croup.
22083 - Be more paranoid about overwriting sensitive memory on free(),
22084 as a defensive programming tactic to ensure forward secrecy.
22086 o Major bugfixes (anonymity fixes):
22087 - Reject requests for reverse-dns lookup of names that are in
22088 a private address space. Patch from lodger.
22089 - Never report that we've used more bandwidth than we're willing to
22090 relay: it leaks how much non-relay traffic we're using. Resolves
22092 - As a client, do not believe any server that tells us that an
22093 address maps to an internal address space.
22094 - Warn about unsafe ControlPort configurations.
22095 - Directory authorities now call routers Fast if their bandwidth is
22096 at least 100KB/s, and consider their bandwidth adequate to be a
22097 Guard if it is at least 250KB/s, no matter the medians. This fix
22098 complements proposal 107.
22099 - Directory authorities now never mark more than 2 servers per IP as
22100 Valid and Running (or 5 on addresses shared by authorities).
22101 Implements proposal 109, by Kevin Bauer and Damon McCoy.
22102 - If we're a relay, avoid picking ourselves as an introduction point,
22103 a rendezvous point, or as the final hop for internal circuits. Bug
22104 reported by taranis and lodger.
22105 - Exit relays that are used as a client can now reach themselves
22106 using the .exit notation, rather than just launching an infinite
22107 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
22108 - Fix a bug where, when we were choosing the 'end stream reason' to
22109 put in our relay end cell that we send to the exit relay, Tor
22110 clients on Windows were sometimes sending the wrong 'reason'. The
22111 anonymity problem is that exit relays may be able to guess whether
22112 the client is running Windows, thus helping partition the anonymity
22113 set. Down the road we should stop sending reasons to exit relays,
22114 or otherwise prevent future versions of this bug.
22115 - Only update guard status (usable / not usable) once we have
22116 enough directory information. This was causing us to discard all our
22117 guards on startup if we hadn't been running for a few weeks. Fixes
22119 - When our directory information has been expired for a while, stop
22120 being willing to build circuits using it. Fixes bug 401.
22122 o Major bugfixes (peace of mind for relay operators)
22123 - Non-exit relays no longer answer "resolve" relay cells, so they
22124 can't be induced to do arbitrary DNS requests. (Tor clients already
22125 avoid using non-exit relays for resolve cells, but now servers
22126 enforce this too.) Fixes bug 619. Patch from lodger.
22127 - When we setconf ClientOnly to 1, close any current OR and Dir
22128 listeners. Reported by mwenge.
22130 o Major bugfixes (other):
22131 - If we only ever used Tor for hidden service lookups or posts, we
22132 would stop building circuits and start refusing connections after
22133 24 hours, since we falsely believed that Tor was dormant. Reported
22135 - Add a new __HashedControlSessionPassword option for controllers
22136 to use for one-off session password hashes that shouldn't get
22137 saved to disk by SAVECONF --- Vidalia users were accumulating a
22138 pile of HashedControlPassword lines in their torrc files, one for
22139 each time they had restarted Tor and then clicked Save. Make Tor
22140 automatically convert "HashedControlPassword" to this new option but
22141 only when it's given on the command line. Partial fix for bug 586.
22142 - Patch from "Andrew S. Lists" to catch when we contact a directory
22143 mirror at IP address X and he says we look like we're coming from
22144 IP address X. Otherwise this would screw up our address detection.
22145 - Reject uploaded descriptors and extrainfo documents if they're
22146 huge. Otherwise we'll cache them all over the network and it'll
22147 clog everything up. Suggested by Aljosha Judmayer.
22148 - When a hidden service was trying to establish an introduction point,
22149 and Tor *did* manage to reuse one of the preemptively built
22150 circuits, it didn't correctly remember which one it used,
22151 so it asked for another one soon after, until there were no
22152 more preemptive circuits, at which point it launched one from
22153 scratch. Bugfix on 0.0.9.x.
22155 o Rate limiting and load balancing improvements:
22156 - When we add data to a write buffer in response to the data on that
22157 write buffer getting low because of a flush, do not consider the
22158 newly added data as a candidate for immediate flushing, but rather
22159 make it wait until the next round of writing. Otherwise, we flush
22160 and refill recursively, and a single greedy TLS connection can
22161 eat all of our bandwidth.
22162 - When counting the number of bytes written on a TLS connection,
22163 look at the BIO actually used for writing to the network, not
22164 at the BIO used (sometimes) to buffer data for the network.
22165 Looking at different BIOs could result in write counts on the
22166 order of ULONG_MAX. Fixes bug 614.
22167 - If we change our MaxAdvertisedBandwidth and then reload torrc,
22168 Tor won't realize it should publish a new relay descriptor. Fixes
22169 bug 688, reported by mfr.
22170 - Avoid using too little bandwidth when our clock skips a few seconds.
22171 - Choose which bridge to use proportional to its advertised bandwidth,
22172 rather than uniformly at random. This should speed up Tor for
22173 bridge users. Also do this for people who set StrictEntryNodes.
22175 o Bootstrapping faster and building circuits more intelligently:
22176 - Fix bug 660 that was preventing us from knowing that we should
22177 preemptively build circuits to handle expected directory requests.
22178 - When we're checking if we have enough dir info for each relay
22179 to begin establishing circuits, make sure that we actually have
22180 the descriptor listed in the consensus, not just any descriptor.
22181 - Correctly notify one-hop connections when a circuit build has
22182 failed. Possible fix for bug 669. Found by lodger.
22183 - Clients now hold circuitless TLS connections open for 1.5 times
22184 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
22185 rebuild a new circuit over them within that timeframe. Previously,
22186 they held them open only for KeepalivePeriod (5 minutes).
22188 o Performance improvements (memory):
22189 - Add OpenBSD malloc code from "phk" as an optional malloc
22190 replacement on Linux: some glibc libraries do very poorly with
22191 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
22192 ./configure to get the replacement malloc code.
22193 - Switch our old ring buffer implementation for one more like that
22194 used by free Unix kernels. The wasted space in a buffer with 1mb
22195 of data will now be more like 8k than 1mb. The new implementation
22196 also avoids realloc();realloc(); patterns that can contribute to
22197 memory fragmentation.
22198 - Change the way that Tor buffers data that it is waiting to write.
22199 Instead of queueing data cells in an enormous ring buffer for each
22200 client->OR or OR->OR connection, we now queue cells on a separate
22201 queue for each circuit. This lets us use less slack memory, and
22202 will eventually let us be smarter about prioritizing different kinds
22204 - Reference-count and share copies of address policy entries; only 5%
22205 of them were actually distinct.
22206 - Tune parameters for cell pool allocation to minimize amount of
22208 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
22209 for every single inactive connection_t. Free items from the
22210 4k/16k-buffer free lists when they haven't been used for a while.
22211 - Make memory debugging information describe more about history
22212 of cell allocation, so we can help reduce our memory use.
22213 - Be even more aggressive about releasing RAM from small
22214 empty buffers. Thanks to our free-list code, this shouldn't be too
22215 performance-intensive.
22216 - Log malloc statistics from mallinfo() on platforms where it exists.
22217 - Use memory pools to allocate cells with better speed and memory
22218 efficiency, especially on platforms where malloc() is inefficient.
22219 - Add a --with-tcmalloc option to the configure script to link
22220 against tcmalloc (if present). Does not yet search for non-system
22223 o Performance improvements (socket management):
22224 - Count the number of open sockets separately from the number of
22225 active connection_t objects. This will let us avoid underusing
22226 our allocated connection limit.
22227 - We no longer use socket pairs to link an edge connection to an
22228 anonymous directory connection or a DirPort test connection.
22229 Instead, we track the link internally and transfer the data
22230 in-process. This saves two sockets per "linked" connection (at the
22231 client and at the server), and avoids the nasty Windows socketpair()
22233 - We were leaking a file descriptor if Tor started with a zero-length
22234 cached-descriptors file. Patch by "freddy77".
22236 o Performance improvements (CPU use):
22237 - Never walk through the list of logs if we know that no log target
22238 is interested in a given message.
22239 - Call routerlist_remove_old_routers() much less often. This should
22240 speed startup, especially on directory caches.
22241 - Base64 decoding was actually showing up on our profile when parsing
22242 the initial descriptor file; switch to an in-process all-at-once
22243 implementation that's about 3.5x times faster than calling out to
22245 - Use a slightly simpler string hashing algorithm (copying Python's
22246 instead of Java's) and optimize our digest hashing algorithm to take
22247 advantage of 64-bit platforms and to remove some possibly-costly
22249 - When implementing AES counter mode, update only the portions of the
22250 counter buffer that need to change, and don't keep separate
22251 network-order and host-order counters on big-endian hosts (where
22252 they are the same).
22253 - Add an in-place version of aes_crypt() so that we can avoid doing a
22254 needless memcpy() call on each cell payload.
22255 - Use Critical Sections rather than Mutexes for synchronizing threads
22256 on win32; Mutexes are heavier-weight, and designed for synchronizing
22259 o Performance improvements (bandwidth use):
22260 - Don't try to launch new descriptor downloads quite so often when we
22261 already have enough directory information to build circuits.
22262 - Version 1 directories are no longer generated in full. Instead,
22263 authorities generate and serve "stub" v1 directories that list
22264 no servers. This will stop Tor versions 0.1.0.x and earlier from
22265 working, but (for security reasons) nobody should be running those
22267 - Avoid going directly to the directory authorities even if you're a
22268 relay, if you haven't found yourself reachable yet or if you've
22269 decided not to advertise your dirport yet. Addresses bug 556.
22270 - If we've gone 12 hours since our last bandwidth check, and we
22271 estimate we have less than 50KB bandwidth capacity but we could
22272 handle more, do another bandwidth test.
22273 - Support "If-Modified-Since" when answering HTTP requests for
22274 directories, running-routers documents, and v2 and v3 networkstatus
22275 documents. (There's no need to support it for router descriptors,
22276 since those are downloaded by descriptor digest.)
22277 - Stop fetching directory info so aggressively if your DirPort is
22278 on but your ORPort is off; stop fetching v2 dir info entirely.
22279 You can override these choices with the new FetchDirInfoEarly
22282 o Changed config option behavior (features):
22283 - Configuration files now accept C-style strings as values. This
22284 helps encode characters not allowed in the current configuration
22285 file format, such as newline or #. Addresses bug 557.
22286 - Add hidden services and DNSPorts to the list of things that make
22287 Tor accept that it has running ports. Change starting Tor with no
22288 ports from a fatal error to a warning; we might change it back if
22289 this turns out to confuse anybody. Fixes bug 579.
22290 - Make PublishServerDescriptor default to 1, so the default doesn't
22291 have to change as we invent new directory protocol versions.
22292 - Allow people to say PreferTunnelledDirConns rather than
22293 PreferTunneledDirConns, for those alternate-spellers out there.
22294 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
22295 accommodate the growing number of servers that use the default
22296 and are reaching it.
22297 - Make it possible to enable HashedControlPassword and
22298 CookieAuthentication at the same time.
22299 - When a TrackHostExits-chosen exit fails too many times in a row,
22300 stop using it. Fixes bug 437.
22302 o Changed config option behavior (bugfixes):
22303 - Do not read the configuration file when we've only been told to
22304 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
22305 based on patch from Sebastian Hahn.
22306 - Actually validate the options passed to AuthDirReject,
22307 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
22308 - Make "ClientOnly 1" config option disable directory ports too.
22309 - Don't stop fetching descriptors when FetchUselessDescriptors is
22310 set, even if we stop asking for circuits. Bug reported by tup
22312 - Servers used to decline to publish their DirPort if their
22313 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
22314 they look only at BandwidthRate and RelayBandwidthRate.
22315 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
22316 minus 1 byte: the actual maximum declared bandwidth.
22317 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
22318 - Make the NodeFamilies config option work. (Reported by
22319 lodger -- it has never actually worked, even though we added it
22321 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
22322 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
22324 o New config options:
22325 - New configuration options AuthDirMaxServersPerAddr and
22326 AuthDirMaxServersperAuthAddr to override default maximum number
22327 of servers allowed on a single IP address. This is important for
22328 running a test network on a single host.
22329 - Three new config options (AlternateDirAuthority,
22330 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
22331 user selectively replace the default directory authorities by type,
22332 rather than the all-or-nothing replacement that DirServer offers.
22333 - New config options AuthDirBadDir and AuthDirListBadDirs for
22334 authorities to mark certain relays as "bad directories" in the
22335 networkstatus documents. Also supports the "!baddir" directive in
22336 the approved-routers file.
22337 - New config option V2AuthoritativeDirectory that all v2 directory
22338 authorities must set. This lets v3 authorities choose not to serve
22339 v2 directory information.
22341 o Minor features (other):
22342 - When we're not serving v2 directory information, there is no reason
22343 to actually keep any around. Remove the obsolete files and directory
22344 on startup if they are very old and we aren't going to serve them.
22345 - When we negotiate a v2 link-layer connection (not yet implemented),
22346 accept RELAY_EARLY cells and turn them into RELAY cells if we've
22347 negotiated a v1 connection for their next step. Initial steps for
22349 - When we have no consensus, check FallbackNetworkstatusFile (defaults
22350 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
22351 we can start out knowing some directory caches. We don't ship with
22352 a fallback consensus by default though, because it was making
22353 bootstrapping take too long while we tried many down relays.
22354 - Authorities send back an X-Descriptor-Not-New header in response to
22355 an accepted-but-discarded descriptor upload. Partially implements
22357 - If we find a cached-routers file that's been sitting around for more
22358 than 28 days unmodified, then most likely it's a leftover from
22359 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
22361 - When we (as a cache) download a descriptor because it was listed
22362 in a consensus, remember when the consensus was supposed to expire,
22363 and don't expire the descriptor until then.
22364 - Optionally (if built with -DEXPORTMALLINFO) export the output
22365 of mallinfo via http, as tor/mallinfo.txt. Only accessible
22367 - Tag every guard node in our state file with the version that
22368 we believe added it, or with our own version if we add it. This way,
22369 if a user temporarily runs an old version of Tor and then switches
22370 back to a new one, she doesn't automatically lose her guards.
22371 - When somebody requests a list of statuses or servers, and we have
22372 none of those, return a 404 rather than an empty 200.
22373 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
22375 - Add an HSAuthorityRecordStats option that hidden service authorities
22376 can use to track statistics of overall hidden service usage without
22377 logging information that would be as useful to an attacker.
22378 - Allow multiple HiddenServicePort directives with the same virtual
22379 port; when they occur, the user is sent round-robin to one
22380 of the target ports chosen at random. Partially fixes bug 393 by
22381 adding limited ad-hoc round-robining.
22382 - Revamp file-writing logic so we don't need to have the entire
22383 contents of a file in memory at once before we write to disk. Tor,
22386 o Minor bugfixes (other):
22387 - Alter the code that tries to recover from unhandled write
22388 errors, to not try to flush onto a socket that's given us
22390 - Directory mirrors no longer include a guess at the client's IP
22391 address if the connection appears to be coming from the same /24
22392 network; it was producing too many wrong guesses.
22393 - If we're trying to flush the last bytes on a connection (for
22394 example, when answering a directory request), reset the
22395 time-to-give-up timeout every time we manage to write something
22397 - Reject router descriptors with out-of-range bandwidthcapacity or
22398 bandwidthburst values.
22399 - If we can't expand our list of entry guards (e.g. because we're
22400 using bridges or we have StrictEntryNodes set), don't mark relays
22401 down when they fail a directory request. Otherwise we're too quick
22402 to mark all our entry points down.
22403 - Authorities no longer send back "400 you're unreachable please fix
22404 it" errors to Tor servers that aren't online all the time. We're
22405 supposed to tolerate these servers now.
22406 - Let directory authorities startup even when they can't generate
22407 a descriptor immediately, e.g. because they don't know their
22409 - Correctly enforce that elements of directory objects do not appear
22410 more often than they are allowed to appear.
22411 - Stop allowing hibernating servers to be "stable" or "fast".
22412 - On Windows, we were preventing other processes from reading
22413 cached-routers while Tor was running. (Reported by janbar)
22414 - Check return values from pthread_mutex functions.
22415 - When opening /dev/null in finish_daemonize(), do not pass the
22416 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
22417 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
22419 o Controller features:
22420 - The GETCONF command now escapes and quotes configuration values
22421 that don't otherwise fit into the torrc file.
22422 - The SETCONF command now handles quoted values correctly.
22423 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
22424 ask about source, timestamp of arrival, purpose, etc. We need
22425 something like this to help Vidalia not do GeoIP lookups on bridge
22427 - Allow multiple HashedControlPassword config lines, to support
22428 multiple controller passwords.
22429 - Accept LF instead of CRLF on controller, since some software has a
22430 hard time generating real Internet newlines.
22431 - Add GETINFO values for the server status events
22432 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
22434 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
22435 GETINFO for Torstat to use until it can switch to using extrainfos.
22436 - New config option CookieAuthFile to choose a new location for the
22437 cookie authentication file, and config option
22438 CookieAuthFileGroupReadable to make it group-readable.
22439 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
22440 match requests to applications. Patch from Robert Hogan.
22441 - Add a RESOLVE command to launch hostname lookups. Original patch
22443 - Add GETINFO status/enough-dir-info to let controllers tell whether
22444 Tor has downloaded sufficient directory information. Patch from Tup.
22445 - You can now use the ControlSocket option to tell Tor to listen for
22446 controller connections on Unix domain sockets on systems that
22447 support them. Patch from Peter Palfrader.
22448 - New "GETINFO address-mappings/*" command to get address mappings
22449 with expiry information. "addr-mappings/*" is now deprecated.
22451 - Add a new config option __DisablePredictedCircuits designed for
22452 use by the controller, when we don't want Tor to build any circuits
22454 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
22455 so we can exit from the middle of the circuit.
22456 - Implement "getinfo status/circuit-established".
22457 - Implement "getinfo status/version/..." so a controller can tell
22458 whether the current version is recommended, and whether any versions
22459 are good, and how many authorities agree. Patch from "shibz".
22460 - Controllers should now specify cache=no or cache=yes when using
22461 the +POSTDESCRIPTOR command.
22462 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
22463 Robert Hogan. Fixes the first part of bug 681.
22464 - When reporting clock skew, and we know that the clock is _at least
22465 as skewed_ as some value, but we don't know the actual value,
22466 report the value as a "minimum skew."
22468 o Controller bugfixes:
22469 - Generate "STATUS_SERVER" events rather than misspelled
22470 "STATUS_SEVER" events. Caught by mwenge.
22471 - Reject controller commands over 1MB in length, so rogue
22472 processes can't run us out of memory.
22473 - Change the behavior of "getinfo status/good-server-descriptor"
22474 so it doesn't return failure when any authority disappears.
22475 - Send NAMESERVER_STATUS messages for a single failed nameserver
22477 - When the DANGEROUS_VERSION controller status event told us we're
22478 running an obsolete version, it used the string "OLD" to describe
22479 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
22480 "OBSOLETE" in both cases.
22481 - Respond to INT and TERM SIGNAL commands before we execute the
22482 signal, in case the signal shuts us down. We had a patch in
22483 0.1.2.1-alpha that tried to do this by queueing the response on
22484 the connection's buffer before shutting down, but that really
22485 isn't the same thing at all. Bug located by Matt Edman.
22486 - Provide DNS expiry times in GMT, not in local time. For backward
22487 compatibility, ADDRMAP events only provide GMT expiry in an extended
22488 field. "GETINFO address-mappings" always does the right thing.
22489 - Use CRLF line endings properly in NS events.
22490 - Make 'getinfo fingerprint' return a 551 error if we're not a
22491 server, so we match what the control spec claims we do. Reported
22493 - Fix a typo in an error message when extendcircuit fails that
22494 caused us to not follow the \r\n-based delimiter protocol. Reported
22496 - When tunneling an encrypted directory connection, and its first
22497 circuit fails, do not leave it unattached and ask the controller
22498 to deal. Fixes the second part of bug 681.
22499 - Treat some 403 responses from directory servers as INFO rather than
22500 WARN-severity events.
22502 o Portability / building / compiling:
22503 - When building with --enable-gcc-warnings, check for whether Apple's
22504 warning "-Wshorten-64-to-32" is available.
22505 - Support compilation to target iPhone; patch from cjacker huang.
22506 To build for iPhone, pass the --enable-iphone option to configure.
22507 - Port Tor to build and run correctly on Windows CE systems, using
22508 the wcecompat library. Contributed by Valerio Lupi.
22509 - Detect non-ASCII platforms (if any still exist) and refuse to
22510 build there: some of our code assumes that 'A' is 65 and so on.
22511 - Clear up some MIPSPro compiler warnings.
22512 - Make autoconf search for libevent, openssl, and zlib consistently.
22513 - Update deprecated macros in configure.in.
22514 - When warning about missing headers, tell the user to let us
22515 know if the compile succeeds anyway, so we can downgrade the
22517 - Include the current subversion revision as part of the version
22518 string: either fetch it directly if we're in an SVN checkout, do
22519 some magic to guess it if we're in an SVK checkout, or use
22520 the last-detected version if we're building from a .tar.gz.
22521 Use this version consistently in log messages.
22522 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
22523 - Read resolv.conf files correctly on platforms where read() returns
22524 partial results on small file reads.
22525 - Build without verbose warnings even on gcc 4.2 and 4.3.
22526 - On Windows, correctly detect errors when listing the contents of
22527 a directory. Fix from lodger.
22528 - Run 'make test' as part of 'make dist', so we stop releasing so
22529 many development snapshots that fail their unit tests.
22530 - Add support to detect Libevent versions in the 1.4.x series
22532 - Add command-line arguments to unit-test executable so that we can
22533 invoke any chosen test from the command line rather than having
22534 to run the whole test suite at once; and so that we can turn on
22535 logging for the unit tests.
22536 - Do not automatically run configure from autogen.sh. This
22537 non-standard behavior tended to annoy people who have built other
22539 - Fix a macro/CPP interaction that was confusing some compilers:
22540 some GCCs don't like #if/#endif pairs inside macro arguments.
22542 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
22543 Fixes bug 704; fix from Steven Murdoch.
22544 - Correctly detect transparent proxy support on Linux hosts that
22545 require in.h to be included before netfilter_ipv4.h. Patch
22548 o Logging improvements:
22549 - When we haven't had any application requests lately, don't bother
22550 logging that we have expired a bunch of descriptors.
22551 - When attempting to open a logfile fails, tell us why.
22552 - Only log guard node status when guard node status has changed.
22553 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
22554 make "INFO" 75% less verbose.
22555 - When SafeLogging is disabled, log addresses along with all TLS
22557 - Report TLS "zero return" case as a "clean close" and "IO error"
22558 as a "close". Stop calling closes "unexpected closes": existing
22559 Tors don't use SSL_close(), so having a connection close without
22560 the TLS shutdown handshake is hardly unexpected.
22561 - When we receive a consensus from the future, warn about skew.
22562 - Make "not enough dir info yet" warnings describe *why* Tor feels
22563 it doesn't have enough directory info yet.
22564 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
22565 consumers. (We already do this on HUP.)
22566 - Give more descriptive well-formedness errors for out-of-range
22567 hidden service descriptor/protocol versions.
22568 - Stop recommending that every server operator send mail to tor-ops.
22569 Resolves bug 597. Bugfix on 0.1.2.x.
22570 - Improve skew reporting: try to give the user a better log message
22571 about how skewed they are, and how much this matters.
22572 - New --quiet command-line option to suppress the default console log.
22573 Good in combination with --hash-password.
22574 - Don't complain that "your server has not managed to confirm that its
22575 ports are reachable" if we haven't been able to build any circuits
22577 - Detect the reason for failing to mmap a descriptor file we just
22578 wrote, and give a more useful log message. Fixes bug 533.
22579 - Always prepend "Bug: " to any log message about a bug.
22580 - When dumping memory usage, list bytes used in buffer memory
22582 - When running with dmalloc, dump more stats on hup and on exit.
22583 - Put a platform string (e.g. "Linux i686") in the startup log
22584 message, so when people paste just their logs, we know if it's
22585 OpenBSD or Windows or what.
22586 - When logging memory usage, break down memory used in buffers by
22588 - When we are reporting the DirServer line we just parsed, we were
22589 logging the second stanza of the key fingerprint, not the first.
22590 - Even though Windows is equally happy with / and \ as path separators,
22591 try to use \ consistently on Windows and / consistently on Unix: it
22592 makes the log messages nicer.
22593 - On OSX, stop warning the user that kqueue support in libevent is
22594 "experimental", since it seems to have worked fine for ages.
22596 o Contributed scripts and tools:
22597 - Update linux-tor-prio.sh script to allow QoS based on the uid of
22598 the Tor process. Patch from Marco Bonetti with tweaks from Mike
22600 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
22601 Unix users an easy way to script their Tor process (e.g. by
22602 adjusting bandwidth based on the time of the day).
22603 - In the exitlist script, only consider the most recently published
22604 server descriptor for each server. Also, when the user requests
22605 a list of servers that _reject_ connections to a given address,
22606 explicitly exclude the IPs that also have servers that accept
22607 connections to that address. Resolves bug 405.
22608 - Include a new contrib/tor-exit-notice.html file that exit relay
22609 operators can put on their website to help reduce abuse queries.
22611 o Newly deprecated features:
22612 - The status/version/num-versioning and status/version/num-concurring
22613 GETINFO controller options are no longer useful in the v3 directory
22614 protocol: treat them as deprecated, and warn when they're used.
22615 - The RedirectExits config option is now deprecated.
22617 o Removed features:
22618 - Drop the old code to choke directory connections when the
22619 corresponding OR connections got full: thanks to the cell queue
22620 feature, OR conns don't get full any more.
22621 - Remove the old "dns worker" server DNS code: it hasn't been default
22622 since 0.1.2.2-alpha, and all the servers are using the new
22624 - Remove the code to generate the oldest (v1) directory format.
22625 - Remove support for the old bw_accounting file: we've been storing
22626 bandwidth accounting information in the state file since
22627 0.1.2.5-alpha. This may result in bandwidth accounting errors
22628 if you try to upgrade from 0.1.1.x or earlier, or if you try to
22629 downgrade to 0.1.1.x or earlier.
22630 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
22631 it, it had no AES, and it hasn't seen any security patches since
22633 - Stop overloading the circuit_t.onionskin field for both "onionskin
22634 from a CREATE cell that we are waiting for a cpuworker to be
22635 assigned" and "onionskin from an EXTEND cell that we are going to
22636 send to an OR as soon as we are connected". Might help with bug 600.
22637 - Remove the tor_strpartition() function: its logic was confused,
22638 and it was only used for one thing that could be implemented far
22640 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
22641 and TorControl.py, as they use the old v0 controller protocol,
22642 and are obsoleted by TorFlow anyway.
22643 - Drop support for v1 rendezvous descriptors, since we never used
22644 them anyway, and the code has probably rotted by now. Based on
22645 patch from Karsten Loesing.
22646 - Stop allowing address masks that do not correspond to bit prefixes.
22647 We have warned about these for a really long time; now it's time
22648 to reject them. (Patch from croup.)
22649 - Remove an optimization in the AES counter-mode code that assumed
22650 that the counter never exceeded 2^68. When the counter can be set
22651 arbitrarily as an IV (as it is by Karsten's new hidden services
22652 code), this assumption no longer holds.
22653 - Disable the SETROUTERPURPOSE controller command: it is now
22657 Changes in version 0.1.2.19 - 2008-01-17
22658 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
22659 exit policy a little bit more conservative so it's safer to run an
22660 exit relay on a home system, and fixes a variety of smaller issues.
22663 - Exit policies now reject connections that are addressed to a
22664 relay's public (external) IP address too, unless
22665 ExitPolicyRejectPrivate is turned off. We do this because too
22666 many relays are running nearby to services that trust them based
22667 on network address.
22670 - When the clock jumps forward a lot, do not allow the bandwidth
22671 buckets to become negative. Fixes bug 544.
22672 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
22673 on every successful resolve. Reported by Mike Perry.
22674 - Purge old entries from the "rephist" database and the hidden
22675 service descriptor database even when DirPort is zero.
22676 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
22677 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
22678 crashing or mis-answering these requests.
22679 - When we decide to send a 503 response to a request for servers, do
22680 not then also send the server descriptors: this defeats the whole
22681 purpose. Fixes bug 539.
22684 - Changing the ExitPolicyRejectPrivate setting should cause us to
22685 rebuild our server descriptor.
22686 - Fix handling of hex nicknames when answering controller requests for
22687 networkstatus by name, or when deciding whether to warn about
22688 unknown routers in a config option. (Patch from mwenge.)
22689 - Fix a couple of hard-to-trigger autoconf problems that could result
22690 in really weird results on platforms whose sys/types.h files define
22691 nonstandard integer types.
22692 - Don't try to create the datadir when running --verify-config or
22693 --hash-password. Resolves bug 540.
22694 - If we were having problems getting a particular descriptor from the
22695 directory caches, and then we learned about a new descriptor for
22696 that router, we weren't resetting our failure count. Reported
22698 - Although we fixed bug 539 (where servers would send HTTP status 503
22699 responses _and_ send a body too), there are still servers out there
22700 that haven't upgraded. Therefore, make clients parse such bodies
22701 when they receive them.
22702 - Run correctly on systems where rlim_t is larger than unsigned long.
22703 This includes some 64-bit systems.
22704 - Run correctly on platforms (like some versions of OS X 10.5) where
22705 the real limit for number of open files is OPEN_FILES, not rlim_max
22706 from getrlimit(RLIMIT_NOFILES).
22707 - Avoid a spurious free on base64 failure.
22708 - Avoid segfaults on certain complex invocations of
22709 router_get_by_hexdigest().
22710 - Fix rare bug on REDIRECTSTREAM control command when called with no
22711 port set: it could erroneously report an error when none had
22715 Changes in version 0.1.2.18 - 2007-10-28
22716 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
22717 hidden service introduction that were causing huge delays, and a big
22718 bug that was causing some servers to disappear from the network status
22719 lists for a few hours each day.
22721 o Major bugfixes (crashes):
22722 - If a connection is shut down abruptly because of something that
22723 happened inside connection_flushed_some(), do not call
22724 connection_finished_flushing(). Should fix bug 451:
22725 "connection_stop_writing: Assertion conn->write_event failed"
22726 Bugfix on 0.1.2.7-alpha.
22727 - Fix possible segfaults in functions called from
22728 rend_process_relay_cell().
22730 o Major bugfixes (hidden services):
22731 - Hidden services were choosing introduction points uniquely by
22732 hexdigest, but when constructing the hidden service descriptor
22733 they merely wrote the (potentially ambiguous) nickname.
22734 - Clients now use the v2 intro format for hidden service
22735 connections: they specify their chosen rendezvous point by identity
22736 digest rather than by (potentially ambiguous) nickname. These
22737 changes could speed up hidden service connections dramatically.
22739 o Major bugfixes (other):
22740 - Stop publishing a new server descriptor just because we get a
22741 HUP signal. This led (in a roundabout way) to some servers getting
22742 dropped from the networkstatus lists for a few hours each day.
22743 - When looking for a circuit to cannibalize, consider family as well
22744 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
22745 circuit cannibalization).
22746 - When a router wasn't listed in a new networkstatus, we were leaving
22747 the flags for that router alone -- meaning it remained Named,
22748 Running, etc -- even though absence from the networkstatus means
22749 that it shouldn't be considered to exist at all anymore. Now we
22750 clear all the flags for routers that fall out of the networkstatus
22751 consensus. Fixes bug 529.
22754 - Don't try to access (or alter) the state file when running
22755 --list-fingerprint or --verify-config or --hash-password. Resolves
22757 - When generating information telling us how to extend to a given
22758 router, do not try to include the nickname if it is
22759 absent. Resolves bug 467.
22760 - Fix a user-triggerable segfault in expand_filename(). (There isn't
22761 a way to trigger this remotely.)
22762 - When sending a status event to the controller telling it that an
22763 OR address is reachable, set the port correctly. (Previously we
22764 were reporting the dir port.)
22765 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
22766 command. Bugfix on 0.1.2.17.
22767 - When loading bandwidth history, do not believe any information in
22768 the future. Fixes bug 434.
22769 - When loading entry guard information, do not believe any information
22771 - When we have our clock set far in the future and generate an
22772 onion key, then re-set our clock to be correct, we should not stop
22773 the onion key from getting rotated.
22774 - On some platforms, accept() can return a broken address. Detect
22775 this more quietly, and deal accordingly. Fixes bug 483.
22776 - It's not actually an error to find a non-pending entry in the DNS
22777 cache when canceling a pending resolve. Don't log unless stuff
22778 is fishy. Resolves bug 463.
22779 - Don't reset trusted dir server list when we set a configuration
22780 option. Patch from Robert Hogan.
22783 Changes in version 0.1.2.17 - 2007-08-30
22784 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
22785 X bundles. Vidalia 0.0.14 makes authentication required for the
22786 ControlPort in the default configuration, which addresses important
22787 security risks. Everybody who uses Vidalia (or another controller)
22790 In addition, this Tor update fixes major load balancing problems with
22791 path selection, which should speed things up a lot once many people
22794 o Major bugfixes (security):
22795 - We removed support for the old (v0) control protocol. It has been
22796 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
22797 become more of a headache than it's worth.
22799 o Major bugfixes (load balancing):
22800 - When choosing nodes for non-guard positions, weight guards
22801 proportionally less, since they already have enough load. Patch
22803 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
22804 will allow fast Tor servers to get more attention.
22805 - When we're upgrading from an old Tor version, forget our current
22806 guards and pick new ones according to the new weightings. These
22807 three load balancing patches could raise effective network capacity
22808 by a factor of four. Thanks to Mike Perry for measurements.
22810 o Major bugfixes (stream expiration):
22811 - Expire not-yet-successful application streams in all cases if
22812 they've been around longer than SocksTimeout. Right now there are
22813 some cases where the stream will live forever, demanding a new
22814 circuit every 15 seconds. Fixes bug 454; reported by lodger.
22816 o Minor features (controller):
22817 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
22818 is valid before any authentication has been received. It tells
22819 a controller what kind of authentication is expected, and what
22820 protocol is spoken. Implements proposal 119.
22822 o Minor bugfixes (performance):
22823 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
22824 greatly speeding up loading cached-routers from disk on startup.
22825 - Disable sentinel-based debugging for buffer code: we squashed all
22826 the bugs that this was supposed to detect a long time ago, and now
22827 its only effect is to change our buffer sizes from nice powers of
22828 two (which platform mallocs tend to like) to values slightly over
22829 powers of two (which make some platform mallocs sad).
22831 o Minor bugfixes (misc):
22832 - If exit bandwidth ever exceeds one third of total bandwidth, then
22833 use the correct formula to weight exit nodes when choosing paths.
22834 Based on patch from Mike Perry.
22835 - Choose perfectly fairly among routers when choosing by bandwidth and
22836 weighting by fraction of bandwidth provided by exits. Previously, we
22837 would choose with only approximate fairness, and correct ourselves
22838 if we ran off the end of the list.
22839 - If we require CookieAuthentication but we fail to write the
22840 cookie file, we would warn but not exit, and end up in a state
22841 where no controller could authenticate. Now we exit.
22842 - If we require CookieAuthentication, stop generating a new cookie
22843 every time we change any piece of our config.
22844 - Refuse to start with certain directory authority keys, and
22845 encourage people using them to stop.
22846 - Terminate multi-line control events properly. Original patch
22848 - Fix a minor memory leak when we fail to find enough suitable
22849 servers to choose a circuit.
22850 - Stop leaking part of the descriptor when we run into a particularly
22851 unparseable piece of it.
22854 Changes in version 0.1.2.16 - 2007-08-01
22855 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
22856 remote attacker in certain situations to rewrite the user's torrc
22857 configuration file. This can completely compromise anonymity of users
22858 in most configurations, including those running the Vidalia bundles,
22859 TorK, etc. Or worse.
22861 o Major security fixes:
22862 - Close immediately after missing authentication on control port;
22863 do not allow multiple authentication attempts.
22866 Changes in version 0.1.2.15 - 2007-07-17
22867 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
22868 problems, fixes compilation on BSD, and fixes a variety of other
22869 bugs. Everybody should upgrade.
22871 o Major bugfixes (compilation):
22872 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
22874 o Major bugfixes (crashes):
22875 - Try even harder not to dereference the first character after
22876 an mmap(). Reported by lodger.
22877 - Fix a crash bug in directory authorities when we re-number the
22878 routerlist while inserting a new router.
22879 - When the cached-routers file is an even multiple of the page size,
22880 don't run off the end and crash. (Fixes bug 455; based on idea
22882 - Fix eventdns.c behavior on Solaris: It is critical to include
22883 orconfig.h _before_ sys/types.h, so that we can get the expected
22884 definition of _FILE_OFFSET_BITS.
22886 o Major bugfixes (security):
22887 - Fix a possible buffer overrun when using BSD natd support. Bug
22889 - When sending destroy cells from a circuit's origin, don't include
22890 the reason for tearing down the circuit. The spec says we didn't,
22891 and now we actually don't. Reported by lodger.
22892 - Keep streamids from different exits on a circuit separate. This
22893 bug may have allowed other routers on a given circuit to inject
22894 cells into streams. Reported by lodger; fixes bug 446.
22895 - If there's a never-before-connected-to guard node in our list,
22896 never choose any guards past it. This way we don't expand our
22897 guard list unless we need to.
22899 o Minor bugfixes (guard nodes):
22900 - Weight guard selection by bandwidth, so that low-bandwidth nodes
22901 don't get overused as guards.
22903 o Minor bugfixes (directory):
22904 - Correctly count the number of authorities that recommend each
22905 version. Previously, we were under-counting by 1.
22906 - Fix a potential crash bug when we load many server descriptors at
22907 once and some of them make others of them obsolete. Fixes bug 458.
22909 o Minor bugfixes (hidden services):
22910 - Stop tearing down the whole circuit when the user asks for a
22911 connection to a port that the hidden service didn't configure.
22914 o Minor bugfixes (misc):
22915 - On Windows, we were preventing other processes from reading
22916 cached-routers while Tor was running. Reported by janbar.
22917 - Fix a possible (but very unlikely) bug in picking routers by
22918 bandwidth. Add a log message to confirm that it is in fact
22919 unlikely. Patch from lodger.
22920 - Backport a couple of memory leak fixes.
22921 - Backport miscellaneous cosmetic bugfixes.
22924 Changes in version 0.1.2.14 - 2007-05-25
22925 Tor 0.1.2.14 changes the addresses of two directory authorities (this
22926 change especially affects those who serve or use hidden services),
22927 and fixes several other crash- and security-related bugs.
22929 o Directory authority changes:
22930 - Two directory authorities (moria1 and moria2) just moved to new
22931 IP addresses. This change will particularly affect those who serve
22932 or use hidden services.
22934 o Major bugfixes (crashes):
22935 - If a directory server runs out of space in the connection table
22936 as it's processing a begin_dir request, it will free the exit stream
22937 but leave it attached to the circuit, leading to unpredictable
22938 behavior. (Reported by seeess, fixes bug 425.)
22939 - Fix a bug in dirserv_remove_invalid() that would cause authorities
22940 to corrupt memory under some really unlikely scenarios.
22941 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
22942 - Avoid segfaults when reading from mmaped descriptor file. (Reported
22945 o Major bugfixes (security):
22946 - When choosing an entry guard for a circuit, avoid using guards
22947 that are in the same family as the chosen exit -- not just guards
22948 that are exactly the chosen exit. (Reported by lodger.)
22950 o Major bugfixes (resource management):
22951 - If a directory authority is down, skip it when deciding where to get
22952 networkstatus objects or descriptors. Otherwise we keep asking
22953 every 10 seconds forever. Fixes bug 384.
22954 - Count it as a failure if we fetch a valid network-status but we
22955 don't want to keep it. Otherwise we'll keep fetching it and keep
22956 not wanting to keep it. Fixes part of bug 422.
22957 - If all of our dirservers have given us bad or no networkstatuses
22958 lately, then stop hammering them once per minute even when we
22959 think they're failed. Fixes another part of bug 422.
22962 - Actually set the purpose correctly for descriptors inserted with
22963 purpose=controller.
22964 - When we have k non-v2 authorities in our DirServer config,
22965 we ignored the last k authorities in the list when updating our
22967 - Correctly back-off from requesting router descriptors that we are
22968 having a hard time downloading.
22969 - Read resolv.conf files correctly on platforms where read() returns
22970 partial results on small file reads.
22971 - Don't rebuild the entire router store every time we get 32K of
22972 routers: rebuild it when the journal gets very large, or when
22973 the gaps in the store get very large.
22976 - When routers publish SVN revisions in their router descriptors,
22977 authorities now include those versions correctly in networkstatus
22979 - Warn when using a version of libevent before 1.3b to run a server on
22980 OSX or BSD: these versions interact badly with userspace threads.
22983 Changes in version 0.1.2.13 - 2007-04-24
22984 This release features some major anonymity fixes, such as safer path
22985 selection; better client performance; faster bootstrapping, better
22986 address detection, and better DNS support for servers; write limiting as
22987 well as read limiting to make servers easier to run; and a huge pile of
22988 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
22990 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
22991 of the Freenode IRC network, remembering his patience and vision for
22992 free speech on the Internet.
22994 o Major features, client performance:
22995 - Weight directory requests by advertised bandwidth. Now we can
22996 let servers enable write limiting but still allow most clients to
22997 succeed at their directory requests. (We still ignore weights when
22998 choosing a directory authority; I hope this is a feature.)
22999 - Stop overloading exit nodes -- avoid choosing them for entry or
23000 middle hops when the total bandwidth available from non-exit nodes
23001 is much higher than the total bandwidth available from exit nodes.
23002 - Rather than waiting a fixed amount of time between retrying
23003 application connections, we wait only 10 seconds for the first,
23004 10 seconds for the second, and 15 seconds for each retry after
23005 that. Hopefully this will improve the expected user experience.
23006 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
23007 to open a stream fails; now we do in more cases. This should
23008 make clients able to find a good exit faster in some cases, since
23009 unhandleable requests will now get an error rather than timing out.
23011 o Major features, client functionality:
23012 - Implement BEGIN_DIR cells, so we can connect to a directory
23013 server via TLS to do encrypted directory requests rather than
23014 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
23015 config options if you like. For now, this feature only works if
23016 you already have a descriptor for the destination dirserver.
23017 - Add support for transparent application connections: this basically
23018 bundles the functionality of trans-proxy-tor into the Tor
23019 mainline. Now hosts with compliant pf/netfilter implementations
23020 can redirect TCP connections straight to Tor without diverting
23021 through SOCKS. (Based on patch from tup.)
23022 - Add support for using natd; this allows FreeBSDs earlier than
23023 5.1.2 to have ipfw send connections through Tor without using
23024 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
23026 o Major features, servers:
23027 - Setting up a dyndns name for your server is now optional: servers
23028 with no hostname or IP address will learn their IP address by
23029 asking the directory authorities. This code only kicks in when you
23030 would normally have exited with a "no address" error. Nothing's
23031 authenticated, so use with care.
23032 - Directory servers now spool server descriptors, v1 directories,
23033 and v2 networkstatus objects to buffers as needed rather than en
23034 masse. They also mmap the cached-routers files. These steps save
23036 - Stop requiring clients to have well-formed certificates, and stop
23037 checking nicknames in certificates. (Clients have certificates so
23038 that they can look like Tor servers, but in the future we might want
23039 to allow them to look like regular TLS clients instead. Nicknames
23040 in certificates serve no purpose other than making our protocol
23041 easier to recognize on the wire.) Implements proposal 106.
23043 o Improvements on DNS support:
23044 - Add "eventdns" asynchronous dns library originally based on code
23045 from Adam Langley. Now we can discard the old rickety dnsworker
23046 concept, and support a wider variety of DNS functions. Allows
23047 multithreaded builds on NetBSD and OpenBSD again.
23048 - Add server-side support for "reverse" DNS lookups (using PTR
23049 records so clients can determine the canonical hostname for a given
23050 IPv4 address). Only supported by servers using eventdns; servers
23051 now announce in their descriptors if they don't support eventdns.
23052 - Workaround for name servers (like Earthlink's) that hijack failing
23053 DNS requests and replace the no-such-server answer with a "helpful"
23054 redirect to an advertising-driven search portal. Also work around
23055 DNS hijackers who "helpfully" decline to hijack known-invalid
23056 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
23057 lets you turn it off.
23058 - Servers now check for the case when common DNS requests are going to
23059 wildcarded addresses (i.e. all getting the same answer), and change
23060 their exit policy to reject *:* if it's happening.
23061 - When asked to resolve a hostname, don't use non-exit servers unless
23062 requested to do so. This allows servers with broken DNS to be
23063 useful to the network.
23064 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
23065 useless IPv6 DNS resolves.
23066 - Specify and implement client-side SOCKS5 interface for reverse DNS
23067 lookups (see doc/socks-extensions.txt). Also cache them.
23068 - When we change nameservers or IP addresses, reset and re-launch
23069 our tests for DNS hijacking.
23071 o Improvements on reachability testing:
23072 - Servers send out a burst of long-range padding cells once they've
23073 established that they're reachable. Spread them over 4 circuits,
23074 so hopefully a few will be fast. This exercises bandwidth and
23075 bootstraps them into the directory more quickly.
23076 - When we find our DirPort to be reachable, publish a new descriptor
23077 so we'll tell the world (reported by pnx).
23078 - Directory authorities now only decide that routers are reachable
23079 if their identity keys are as expected.
23080 - Do DirPort reachability tests less often, since a single test
23081 chews through many circuits before giving up.
23082 - Avoid some false positives during reachability testing: don't try
23083 to test via a server that's on the same /24 network as us.
23084 - Start publishing one minute or so after we find our ORPort
23085 to be reachable. This will help reduce the number of descriptors
23086 we have for ourselves floating around, since it's quite likely
23087 other things (e.g. DirPort) will change during that minute too.
23088 - Routers no longer try to rebuild long-term connections to directory
23089 authorities, and directory authorities no longer try to rebuild
23090 long-term connections to all servers. We still don't hang up
23091 connections in these two cases though -- we need to look at it
23092 more carefully to avoid flapping, and we likely need to wait til
23093 0.1.1.x is obsolete.
23095 o Improvements on rate limiting:
23096 - Enable write limiting as well as read limiting. Now we sacrifice
23097 capacity if we're pushing out lots of directory traffic, rather
23098 than overrunning the user's intended bandwidth limits.
23099 - Include TLS overhead when counting bandwidth usage; previously, we
23100 would count only the bytes sent over TLS, but not the bytes used
23102 - Servers decline directory requests much more aggressively when
23103 they're low on bandwidth. Otherwise they end up queueing more and
23104 more directory responses, which can't be good for latency.
23105 - But never refuse directory requests from local addresses.
23106 - Be willing to read or write on local connections (e.g. controller
23107 connections) even when the global rate limiting buckets are empty.
23108 - Flush local controller connection buffers periodically as we're
23109 writing to them, so we avoid queueing 4+ megabytes of data before
23111 - Revise and clean up the torrc.sample that we ship with; add
23112 a section for BandwidthRate and BandwidthBurst.
23114 o Major features, NT services:
23115 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
23116 command-line flag so that admins can override the default by saying
23117 "tor --service install --user "SomeUser"". This will not affect
23118 existing installed services. Also, warn the user that the service
23119 will look for its configuration file in the service user's
23120 %appdata% directory. (We can't do the "hardwire the user's appdata
23121 directory" trick any more, since we may not have read access to that
23123 - Support running the Tor service with a torrc not in the same
23124 directory as tor.exe and default to using the torrc located in
23125 the %appdata%\Tor\ of the user who installed the service. Patch
23127 - Add an --ignore-missing-torrc command-line option so that we can
23128 get the "use sensible defaults if the configuration file doesn't
23129 exist" behavior even when specifying a torrc location on the
23131 - When stopping an NT service, wait up to 10 sec for it to actually
23132 stop. (Patch from Matt Edman; resolves bug 295.)
23134 o Directory authority improvements:
23135 - Stop letting hibernating or obsolete servers affect uptime and
23137 - Stop listing hibernating servers in the v1 directory.
23138 - Authorities no longer recommend exits as guards if this would shift
23139 too much load to the exit nodes.
23140 - Authorities now specify server versions in networkstatus. This adds
23141 about 2% to the size of compressed networkstatus docs, and allows
23142 clients to tell which servers support BEGIN_DIR and which don't.
23143 The implementation is forward-compatible with a proposed future
23144 protocol version scheme not tied to Tor versions.
23145 - DirServer configuration lines now have an orport= option so
23146 clients can open encrypted tunnels to the authorities without
23147 having downloaded their descriptors yet. Enabled for moria1,
23148 moria2, tor26, and lefkada now in the default configuration.
23149 - Add a BadDirectory flag to network status docs so that authorities
23150 can (eventually) tell clients about caches they believe to be
23151 broken. Not used yet.
23152 - Allow authorities to list nodes as bad exits in their
23153 approved-routers file by fingerprint or by address. If most
23154 authorities set a BadExit flag for a server, clients don't think
23155 of it as a general-purpose exit. Clients only consider authorities
23156 that advertise themselves as listing bad exits.
23157 - Patch from Steve Hildrey: Generate network status correctly on
23158 non-versioning dirservers.
23159 - Have directory authorities allow larger amounts of drift in uptime
23160 without replacing the server descriptor: previously, a server that
23161 restarted every 30 minutes could have 48 "interesting" descriptors
23163 - Reserve the nickname "Unnamed" for routers that can't pick
23164 a hostname: any router can call itself Unnamed; directory
23165 authorities will never allocate Unnamed to any particular router;
23166 clients won't believe that any router is the canonical Unnamed.
23168 o Directory mirrors and clients:
23169 - Discard any v1 directory info that's over 1 month old (for
23170 directories) or over 1 week old (for running-routers lists).
23171 - Clients track responses with status 503 from dirservers. After a
23172 dirserver has given us a 503, we try not to use it until an hour has
23173 gone by, or until we have no dirservers that haven't given us a 503.
23174 - When we get a 503 from a directory, and we're not a server, we no
23175 longer count the failure against the total number of failures
23176 allowed for the object we're trying to download.
23177 - Prepare for servers to publish descriptors less often: never
23178 discard a descriptor simply for being too old until either it is
23179 recommended by no authorities, or until we get a better one for
23180 the same router. Make caches consider retaining old recommended
23181 routers for even longer.
23182 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
23183 headers for content, so that we can work better in the presence of
23184 caching HTTP proxies.
23185 - Stop fetching descriptors if you're not a dir mirror and you
23186 haven't tried to establish any circuits lately. (This currently
23187 causes some dangerous behavior, because when you start up again
23188 you'll use your ancient server descriptors.)
23190 o Major fixes, crashes:
23191 - Stop crashing when the controller asks us to resetconf more than
23192 one config option at once. (Vidalia 0.0.11 does this.)
23193 - Fix a longstanding obscure crash bug that could occur when we run
23194 out of DNS worker processes, if we're not using eventdns. (Resolves
23196 - Fix an assert that could trigger if a controller quickly set then
23197 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
23198 - Avoid crash when telling controller about stream-status and a
23199 stream is detached.
23200 - Avoid sending junk to controllers or segfaulting when a controller
23201 uses EVENT_NEW_DESC with verbose nicknames.
23202 - Stop triggering asserts if the controller tries to extend hidden
23203 service circuits (reported by mwenge).
23204 - If we start a server with ClientOnly 1, then set ClientOnly to 0
23205 and hup, stop triggering an assert based on an empty onion_key.
23206 - Mask out all signals in sub-threads; only the libevent signal
23207 handler should be processing them. This should prevent some crashes
23208 on some machines using pthreads. (Patch from coderman.)
23209 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
23211 o Major fixes, anonymity/security:
23212 - Automatically avoid picking more than one node from the same
23213 /16 network when constructing a circuit. Add an
23214 "EnforceDistinctSubnets" option to let people disable it if they
23215 want to operate private test networks on a single subnet.
23216 - When generating bandwidth history, round down to the nearest
23217 1k. When storing accounting data, round up to the nearest 1k.
23218 - When we're running as a server, remember when we last rotated onion
23219 keys, so that we will rotate keys once they're a week old even if
23220 we never stay up for a week ourselves.
23221 - If a client asked for a server by name, and there's a named server
23222 in our network-status but we don't have its descriptor yet, we
23223 could return an unnamed server instead.
23224 - Reject (most) attempts to use Tor circuits with length one. (If
23225 many people start using Tor as a one-hop proxy, exit nodes become
23226 a more attractive target for compromise.)
23227 - Just because your DirPort is open doesn't mean people should be
23228 able to remotely teach you about hidden service descriptors. Now
23229 only accept rendezvous posts if you've got HSAuthoritativeDir set.
23230 - Fix a potential race condition in the rpm installer. Found by
23232 - Do not log IPs with TLS failures for incoming TLS
23233 connections. (Fixes bug 382.)
23235 o Major fixes, other:
23236 - If our system clock jumps back in time, don't publish a negative
23237 uptime in the descriptor.
23238 - When we start during an accounting interval before it's time to wake
23239 up, remember to wake up at the correct time. (May fix bug 342.)
23240 - Previously, we would cache up to 16 old networkstatus documents
23241 indefinitely, if they came from nontrusted authorities. Now we
23242 discard them if they are more than 10 days old.
23243 - When we have a state file we cannot parse, tell the user and
23244 move it aside. Now we avoid situations where the user starts
23245 Tor in 1904, Tor writes a state file with that timestamp in it,
23246 the user fixes her clock, and Tor refuses to start.
23247 - Publish a new descriptor after we hup/reload. This is important
23248 if our config has changed such that we'll want to start advertising
23249 our DirPort now, etc.
23250 - If we are using an exit enclave and we can't connect, e.g. because
23251 its webserver is misconfigured to not listen on localhost, then
23252 back off and try connecting from somewhere else before we fail.
23254 o New config options or behaviors:
23255 - When EntryNodes are configured, rebuild the guard list to contain,
23256 in order: the EntryNodes that were guards before; the rest of the
23257 EntryNodes; the nodes that were guards before.
23258 - Do not warn when individual nodes in the configuration's EntryNodes,
23259 ExitNodes, etc are down: warn only when all possible nodes
23260 are down. (Fixes bug 348.)
23261 - Put a lower-bound on MaxAdvertisedBandwidth.
23262 - Start using the state file to store bandwidth accounting data:
23263 the bw_accounting file is now obsolete. We'll keep generating it
23264 for a while for people who are still using 0.1.2.4-alpha.
23265 - Try to batch changes to the state file so that we do as few
23266 disk writes as possible while still storing important things in
23268 - The state file and the bw_accounting file get saved less often when
23269 the AvoidDiskWrites config option is set.
23270 - Make PIDFile work on Windows.
23271 - Add internal descriptions for a bunch of configuration options:
23272 accessible via controller interface and in comments in saved
23274 - Reject *:563 (NNTPS) in the default exit policy. We already reject
23275 NNTP by default, so this seems like a sensible addition.
23276 - Clients now reject hostnames with invalid characters. This should
23277 avoid some inadvertent info leaks. Add an option
23278 AllowNonRFC953Hostnames to disable this behavior, in case somebody
23279 is running a private network with hosts called @, !, and #.
23280 - Check for addresses with invalid characters at the exit as well,
23281 and warn less verbosely when they fail. You can override this by
23282 setting ServerDNSAllowNonRFC953Addresses to 1.
23283 - Remove some options that have been deprecated since at least
23284 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
23285 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
23286 to set log options. Mark PathlenCoinWeight as obsolete.
23287 - Stop accepting certain malformed ports in configured exit policies.
23288 - When the user uses bad syntax in the Log config line, stop
23289 suggesting other bad syntax as a replacement.
23290 - Add new config option "ResolvConf" to let the server operator
23291 choose an alternate resolve.conf file when using eventdns.
23292 - If one of our entry guards is on the ExcludeNodes list, or the
23293 directory authorities don't think it's a good guard, treat it as
23294 if it were unlisted: stop using it as a guard, and throw it off
23295 the guards list if it stays that way for a long time.
23296 - Allow directory authorities to be marked separately as authorities
23297 for the v1 directory protocol, the v2 directory protocol, and
23298 as hidden service directories, to make it easier to retire old
23299 authorities. V1 authorities should set "HSAuthoritativeDir 1"
23300 to continue being hidden service authorities too.
23301 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
23302 - Make TrackExitHosts case-insensitive, and fix the behavior of
23303 ".suffix" TrackExitHosts items to avoid matching in the middle of
23305 - New DirPort behavior: if you have your dirport set, you download
23306 descriptors aggressively like a directory mirror, whether or not
23307 your ORPort is set.
23310 - Create a new file ReleaseNotes which was the old ChangeLog. The
23311 new ChangeLog file now includes the notes for all development
23313 - Add a new address-spec.txt document to describe our special-case
23314 addresses: .exit, .onion, and .noconnnect.
23315 - Fork the v1 directory protocol into its own spec document,
23316 and mark dir-spec.txt as the currently correct (v2) spec.
23318 o Packaging, porting, and contrib
23319 - "tor --verify-config" now exits with -1(255) or 0 depending on
23320 whether the config options are bad or good.
23321 - The Debian package now uses --verify-config when (re)starting,
23322 to distinguish configuration errors from other errors.
23323 - Adapt a patch from goodell to let the contrib/exitlist script
23324 take arguments rather than require direct editing.
23325 - Prevent the contrib/exitlist script from printing the same
23326 result more than once.
23327 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
23328 - In the hidden service example in torrc.sample, stop recommending
23329 esoteric and discouraged hidden service options.
23330 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
23331 values before failing, and always enables eventdns.
23332 - Try to detect Windows correctly when cross-compiling.
23333 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
23334 Try to fix this in configure.in by checking for most functions
23335 before we check for libevent.
23336 - Update RPMs to require libevent 1.2.
23337 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
23338 or later. Log when we are doing this, so we can diagnose it when
23339 it fails. (Also, recommend libevent 1.1b for kqueue and
23340 win32 methods; deprecate libevent 1.0b harder; make libevent
23341 recommendation system saner.)
23342 - Build with recent (1.3+) libevents on platforms that do not
23343 define the nonstandard types "u_int8_t" and friends.
23344 - Remove architecture from OS X builds. The official builds are
23345 now universal binaries.
23346 - Run correctly on OS X platforms with case-sensitive filesystems.
23347 - Correctly set maximum connection limit on Cygwin. (This time
23349 - Start compiling on MinGW on Windows (patches from Mike Chiussi
23351 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
23352 - Finally fix the openssl warnings from newer gccs that believe that
23353 ignoring a return value is okay, but casting a return value and
23354 then ignoring it is a sign of madness.
23355 - On architectures where sizeof(int)>4, still clamp declarable
23356 bandwidth to INT32_MAX.
23358 o Minor features, controller:
23359 - Warn the user when an application uses the obsolete binary v0
23360 control protocol. We're planning to remove support for it during
23361 the next development series, so it's good to give people some
23363 - Add STREAM_BW events to report per-entry-stream bandwidth
23364 use. (Patch from Robert Hogan.)
23365 - Rate-limit SIGNEWNYM signals in response to controllers that
23366 impolitely generate them for every single stream. (Patch from
23367 mwenge; closes bug 394.)
23368 - Add a REMAP status to stream events to note that a stream's
23369 address has changed because of a cached address or a MapAddress
23371 - Make REMAP stream events have a SOURCE (cache or exit), and
23372 make them generated in every case where we get a successful
23373 connected or resolved cell.
23374 - Track reasons for OR connection failure; make these reasons
23375 available via the controller interface. (Patch from Mike Perry.)
23376 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
23377 can learn when clients are sending malformed hostnames to Tor.
23378 - Specify and implement some of the controller status events.
23379 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
23380 - Reimplement GETINFO so that info/names stays in sync with the
23382 - Implement "GETINFO fingerprint".
23383 - Implement "SETEVENTS GUARD" so controllers can get updates on
23384 entry guard status as it changes.
23385 - Make all connections to addresses of the form ".noconnect"
23386 immediately get closed. This lets application/controller combos
23387 successfully test whether they're talking to the same Tor by
23388 watching for STREAM events.
23389 - Add a REASON field to CIRC events; for backward compatibility, this
23390 field is sent only to controllers that have enabled the extended
23391 event format. Also, add additional reason codes to explain why
23392 a given circuit has been destroyed or truncated. (Patches from
23394 - Add a REMOTE_REASON field to extended CIRC events to tell the
23395 controller why a remote OR told us to close a circuit.
23396 - Stream events also now have REASON and REMOTE_REASON fields,
23397 working much like those for circuit events.
23398 - There's now a GETINFO ns/... field so that controllers can ask Tor
23399 about the current status of a router.
23400 - A new event type "NS" to inform a controller when our opinion of
23401 a router's status has changed.
23402 - Add a GETINFO events/names and GETINFO features/names so controllers
23403 can tell which events and features are supported.
23404 - A new CLEARDNSCACHE signal to allow controllers to clear the
23405 client-side DNS cache without expiring circuits.
23406 - Fix CIRC controller events so that controllers can learn the
23407 identity digests of non-Named servers used in circuit paths.
23408 - Let controllers ask for more useful identifiers for servers. Instead
23409 of learning identity digests for un-Named servers and nicknames
23410 for Named servers, the new identifiers include digest, nickname,
23411 and indication of Named status. Off by default; see control-spec.txt
23412 for more information.
23413 - Add a "getinfo address" controller command so it can display Tor's
23414 best guess to the user.
23415 - New controller event to alert the controller when our server
23416 descriptor has changed.
23417 - Give more meaningful errors on controller authentication failure.
23418 - Export the default exit policy via the control port, so controllers
23419 don't need to guess what it is / will be later.
23421 o Minor bugfixes, controller:
23422 - When creating a circuit via the controller, send a 'launched'
23423 event when we're done, so we follow the spec better.
23424 - Correct the control spec to match how the code actually responds
23425 to 'getinfo addr-mappings/*'. Reported by daejees.
23426 - The control spec described a GUARDS event, but the code
23427 implemented a GUARD event. Standardize on GUARD, but let people
23428 ask for GUARDS too. Reported by daejees.
23429 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
23430 clear the corresponding on_circuit variable, and remember later
23431 that we don't need to send a redundant CLOSED event. (Resolves part
23433 - Report events where a resolve succeeded or where we got a socks
23434 protocol error correctly, rather than calling both of them
23436 - Change reported stream target addresses to IP consistently when
23437 we finally get the IP from an exit node.
23438 - Send log messages to the controller even if they happen to be very
23440 - Flush ERR-level controller status events just like we currently
23441 flush ERR-level log events, so that a Tor shutdown doesn't prevent
23442 the controller from learning about current events.
23443 - Report the circuit number correctly in STREAM CLOSED events. Bug
23444 reported by Mike Perry.
23445 - Do not report bizarre values for results of accounting GETINFOs
23446 when the last second's write or read exceeds the allotted bandwidth.
23447 - Report "unrecognized key" rather than an empty string when the
23448 controller tries to fetch a networkstatus that doesn't exist.
23449 - When the controller does a "GETINFO network-status", tell it
23450 about even those routers whose descriptors are very old, and use
23451 long nicknames where appropriate.
23452 - Fix handling of verbose nicknames with ORCONN controller events:
23453 make them show up exactly when requested, rather than exactly when
23455 - Controller signals now work on non-Unix platforms that don't define
23456 SIGUSR1 and SIGUSR2 the way we expect.
23457 - Respond to SIGNAL command before we execute the signal, in case
23458 the signal shuts us down. Suggested by Karsten Loesing.
23459 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
23461 o Minor features, code performance:
23462 - Major performance improvement on inserting descriptors: change
23463 algorithm from O(n^2) to O(n).
23464 - Do not rotate onion key immediately after setting it for the first
23466 - Call router_have_min_dir_info half as often. (This is showing up in
23467 some profiles, but not others.)
23468 - When using GCC, make log_debug never get called at all, and its
23469 arguments never get evaluated, when no debug logs are configured.
23470 (This is showing up in some profiles, but not others.)
23471 - Statistics dumped by -USR2 now include a breakdown of public key
23472 operations, for profiling.
23473 - Make the common memory allocation path faster on machines where
23474 malloc(0) returns a pointer.
23475 - Split circuit_t into origin_circuit_t and or_circuit_t, and
23476 split connection_t into edge, or, dir, control, and base structs.
23477 These will save quite a bit of memory on busy servers, and they'll
23478 also help us track down bugs in the code and bugs in the spec.
23479 - Use OpenSSL's AES implementation on platforms where it's faster.
23480 This could save us as much as 10% CPU usage.
23482 o Minor features, descriptors and descriptor handling:
23483 - Avoid duplicate entries on MyFamily line in server descriptor.
23484 - When Tor receives a router descriptor that it asked for, but
23485 no longer wants (because it has received fresh networkstatuses
23486 in the meantime), do not warn the user. Cache the descriptor if
23487 we're a cache; drop it if we aren't.
23488 - Servers no longer ever list themselves in their "family" line,
23489 even if configured to do so. This makes it easier to configure
23490 family lists conveniently.
23492 o Minor fixes, confusing/misleading log messages:
23493 - Display correct results when reporting which versions are
23494 recommended, and how recommended they are. (Resolves bug 383.)
23495 - Inform the server operator when we decide not to advertise a
23496 DirPort due to AccountingMax enabled or a low BandwidthRate.
23497 - Only include function names in log messages for info/debug messages.
23498 For notice/warn/err, the content of the message should be clear on
23499 its own, and printing the function name only confuses users.
23500 - Remove even more protocol-related warnings from Tor server logs,
23501 such as bad TLS handshakes and malformed begin cells.
23502 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
23503 when the IP address is mapped through MapAddress to a hostname.
23504 - Fix misleading log messages: an entry guard that is "unlisted",
23505 as well as not known to be "down" (because we've never heard
23506 of it), is not therefore "up".
23508 o Minor fixes, old/obsolete behavior:
23509 - Start assuming we can use a create_fast cell if we don't know
23510 what version a router is running.
23511 - We no longer look for identity and onion keys in "identity.key" and
23512 "onion.key" -- these were replaced by secret_id_key and
23513 secret_onion_key in 0.0.8pre1.
23514 - We no longer require unrecognized directory entries to be
23516 - Drop compatibility with obsolete Tors that permit create cells
23517 to have the wrong circ_id_type.
23518 - Remove code to special-case "-cvs" ending, since it has not
23519 actually mattered since 0.0.9.
23520 - Don't re-write the fingerprint file every restart, unless it has
23523 o Minor fixes, misc client-side behavior:
23524 - Always remove expired routers and networkstatus docs before checking
23525 whether we have enough information to build circuits. (Fixes
23527 - When computing clock skew from directory HTTP headers, consider what
23528 time it was when we finished asking for the directory, not what
23530 - Make our socks5 handling more robust to broken socks clients:
23531 throw out everything waiting on the buffer in between socks
23532 handshake phases, since they can't possibly (so the theory
23533 goes) have predicted what we plan to respond to them.
23534 - Expire socks connections if they spend too long waiting for the
23535 handshake to finish. Previously we would let them sit around for
23536 days, if the connecting application didn't close them either.
23537 - And if the socks handshake hasn't started, don't send a
23538 "DNS resolve socks failed" handshake reply; just close it.
23539 - If the user asks to use invalid exit nodes, be willing to use
23541 - Track unreachable entry guards correctly: don't conflate
23542 'unreachable by us right now' with 'listed as down by the directory
23543 authorities'. With the old code, if a guard was unreachable by us
23544 but listed as running, it would clog our guard list forever.
23545 - Behave correctly in case we ever have a network with more than
23546 2GB/s total advertised capacity.
23547 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
23548 - Fix a memory leak when we ask for "all" networkstatuses and we
23549 get one we don't recognize.
23552 Changes in version 0.1.1.26 - 2006-12-14
23553 o Security bugfixes:
23554 - Stop sending the HttpProxyAuthenticator string to directory
23555 servers when directory connections are tunnelled through Tor.
23556 - Clients no longer store bandwidth history in the state file.
23557 - Do not log introduction points for hidden services if SafeLogging
23561 - Fix an assert failure when a directory authority sets
23562 AuthDirRejectUnlisted and then receives a descriptor from an
23563 unlisted router (reported by seeess).
23566 Changes in version 0.1.1.25 - 2006-11-04
23568 - When a client asks us to resolve (rather than connect to)
23569 an address, and we have a cached answer, give them the cached
23570 answer. Previously, we would give them no answer at all.
23571 - We were building exactly the wrong circuits when we predict
23572 hidden service requirements, meaning Tor would have to build all
23573 its circuits on demand.
23574 - If none of our live entry guards have a high uptime, but we
23575 require a guard with a high uptime, try adding a new guard before
23576 we give up on the requirement. This patch should make long-lived
23577 connections more stable on average.
23578 - When testing reachability of our DirPort, don't launch new
23579 tests when there's already one in progress -- unreachable
23580 servers were stacking up dozens of testing streams.
23582 o Security bugfixes:
23583 - When the user sends a NEWNYM signal, clear the client-side DNS
23584 cache too. Otherwise we continue to act on previous information.
23587 - Avoid a memory corruption bug when creating a hash table for
23589 - Avoid possibility of controller-triggered crash when misusing
23590 certain commands from a v0 controller on platforms that do not
23591 handle printf("%s",NULL) gracefully.
23592 - Avoid infinite loop on unexpected controller input.
23593 - Don't log spurious warnings when we see a circuit close reason we
23594 don't recognize; it's probably just from a newer version of Tor.
23595 - Add Vidalia to the OS X uninstaller script, so when we uninstall
23596 Tor/Privoxy we also uninstall Vidalia.
23599 Changes in version 0.1.1.24 - 2006-09-29
23601 - Allow really slow clients to not hang up five minutes into their
23602 directory downloads (suggested by Adam J. Richter).
23603 - Fix major performance regression from 0.1.0.x: instead of checking
23604 whether we have enough directory information every time we want to
23605 do something, only check when the directory information has changed.
23606 This should improve client CPU usage by 25-50%.
23607 - Don't crash if, after a server has been running for a while,
23608 it can't resolve its hostname.
23609 - When a client asks us to resolve (not connect to) an address,
23610 and we have a cached answer, give them the cached answer.
23611 Previously, we would give them no answer at all.
23614 - Allow Tor to start when RunAsDaemon is set but no logs are set.
23615 - Don't crash when the controller receives a third argument to an
23616 "extendcircuit" request.
23617 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
23618 response; fix error code when "getinfo dir/status/" fails.
23619 - Fix configure.in to not produce broken configure files with
23620 more recent versions of autoconf. Thanks to Clint for his auto*
23622 - Fix security bug on NetBSD that could allow someone to force
23623 uninitialized RAM to be sent to a server's DNS resolver. This
23624 only affects NetBSD and other platforms that do not bounds-check
23626 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
23627 methods: these are known to be buggy.
23628 - If we're a directory mirror and we ask for "all" network status
23629 documents, we would discard status documents from authorities
23630 we don't recognize.
23633 Changes in version 0.1.1.23 - 2006-07-30
23635 - Fast Tor servers, especially exit nodes, were triggering asserts
23636 due to a bug in handling the list of pending DNS resolves. Some
23637 bugs still remain here; we're hunting them.
23638 - Entry guards could crash clients by sending unexpected input.
23639 - More fixes on reachability testing: if you find yourself reachable,
23640 then don't ever make any client requests (so you stop predicting
23641 circuits), then hup or have your clock jump, then later your IP
23642 changes, you won't think circuits are working, so you won't try to
23643 test reachability, so you won't publish.
23646 - Avoid a crash if the controller does a resetconf firewallports
23647 and then a setconf fascistfirewall=1.
23648 - Avoid an integer underflow when the dir authority decides whether
23649 a router is stable: we might wrongly label it stable, and compute
23650 a slightly wrong median stability, when a descriptor is published
23652 - Fix a place where we might trigger an assert if we can't build our
23653 own server descriptor yet.
23656 Changes in version 0.1.1.22 - 2006-07-05
23658 - Fix a big bug that was causing servers to not find themselves
23659 reachable if they changed IP addresses. Since only 0.1.1.22+
23660 servers can do reachability testing correctly, now we automatically
23661 make sure to test via one of these.
23662 - Fix to allow clients and mirrors to learn directory info from
23663 descriptor downloads that get cut off partway through.
23664 - Directory authorities had a bug in deciding if a newly published
23665 descriptor was novel enough to make everybody want a copy -- a few
23666 servers seem to be publishing new descriptors many times a minute.
23668 - Fix a rare bug that was causing some servers to complain about
23669 "closing wedged cpuworkers" and skip some circuit create requests.
23670 - Make the Exit flag in directory status documents actually work.
23673 Changes in version 0.1.1.21 - 2006-06-10
23674 o Crash and assert fixes from 0.1.1.20:
23675 - Fix a rare crash on Tor servers that have enabled hibernation.
23676 - Fix a seg fault on startup for Tor networks that use only one
23677 directory authority.
23678 - Fix an assert from a race condition that occurs on Tor servers
23679 while exiting, where various threads are trying to log that they're
23680 exiting, and delete the logs, at the same time.
23681 - Make our unit tests pass again on certain obscure platforms.
23684 - Add support for building SUSE RPM packages.
23685 - Speed up initial bootstrapping for clients: if we are making our
23686 first ever connection to any entry guard, then don't mark it down
23688 - When only one Tor server in the network is labelled as a guard,
23689 and we've already picked him, we would cycle endlessly picking him
23690 again, being unhappy about it, etc. Now we specifically exclude
23691 current guards when picking a new guard.
23692 - Servers send create cells more reliably after the TLS connection
23693 is established: we were sometimes forgetting to send half of them
23694 when we had more than one pending.
23695 - If we get a create cell that asks us to extend somewhere, but the
23696 Tor server there doesn't match the expected digest, we now send
23697 a destroy cell back, rather than silently doing nothing.
23698 - Make options->RedirectExit work again.
23699 - Make cookie authentication for the controller work again.
23700 - Stop being picky about unusual characters in the arguments to
23701 mapaddress. It's none of our business.
23702 - Add a new config option "TestVia" that lets you specify preferred
23703 middle hops to use for test circuits. Perhaps this will let me
23704 debug the reachability problems better.
23706 o Log / documentation fixes:
23707 - If we're a server and some peer has a broken TLS certificate, don't
23708 log about it unless ProtocolWarnings is set, i.e., we want to hear
23709 about protocol violations by others.
23710 - Fix spelling of VirtualAddrNetwork in man page.
23711 - Add a better explanation at the top of the autogenerated torrc file
23712 about what happened to our old torrc.
23715 Changes in version 0.1.1.20 - 2006-05-23
23716 o Crash and assert fixes from 0.1.0.17:
23717 - Fix assert bug in close_logs() on exit: when we close and delete
23718 logs, remove them all from the global "logfiles" list.
23719 - Fix an assert error when we're out of space in the connection_list
23720 and we try to post a hidden service descriptor (reported by Peter
23722 - Fix a rare assert error when we've tried all intro points for
23723 a hidden service and we try fetching the service descriptor again:
23724 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
23725 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
23726 out and refuse the setconf if it would fail.
23727 - If you specify a relative torrc path and you set RunAsDaemon in
23728 your torrc, then it chdir()'s to the new directory. If you then
23729 HUP, it tries to load the new torrc location, fails, and exits.
23730 The fix: no longer allow a relative path to torrc when using -f.
23731 - Check for integer overflows in more places, when adding elements
23732 to smartlists. This could possibly prevent a buffer overflow
23733 on malicious huge inputs.
23735 o Security fixes, major:
23736 - When we're printing strings from the network, don't try to print
23737 non-printable characters. Now we're safer against shell escape
23738 sequence exploits, and also against attacks to fool users into
23739 misreading their logs.
23740 - Implement entry guards: automatically choose a handful of entry
23741 nodes and stick with them for all circuits. Only pick new guards
23742 when the ones you have are unsuitable, and if the old guards
23743 become suitable again, switch back. This will increase security
23744 dramatically against certain end-point attacks. The EntryNodes
23745 config option now provides some hints about which entry guards you
23746 want to use most; and StrictEntryNodes means to only use those.
23747 Fixes CVE-2006-0414.
23748 - Implement exit enclaves: if we know an IP address for the
23749 destination, and there's a running Tor server at that address
23750 which allows exit to the destination, then extend the circuit to
23751 that exit first. This provides end-to-end encryption and end-to-end
23752 authentication. Also, if the user wants a .exit address or enclave,
23753 use 4 hops rather than 3, and cannibalize a general circ for it
23755 - Obey our firewall options more faithfully:
23756 . If we can't get to a dirserver directly, try going via Tor.
23757 . Don't ever try to connect (as a client) to a place our
23758 firewall options forbid.
23759 . If we specify a proxy and also firewall options, obey the
23760 firewall options even when we're using the proxy: some proxies
23761 can only proxy to certain destinations.
23762 - Make clients regenerate their keys when their IP address changes.
23763 - For the OS X package's modified privoxy config file, comment
23764 out the "logfile" line so we don't log everything passed
23766 - Our TLS handshakes were generating a single public/private
23767 keypair for the TLS context, rather than making a new one for
23768 each new connection. Oops. (But we were still rotating them
23769 periodically, so it's not so bad.)
23770 - When we were cannibalizing a circuit with a particular exit
23771 node in mind, we weren't checking to see if that exit node was
23772 already present earlier in the circuit. Now we are.
23773 - Require server descriptors to list IPv4 addresses -- hostnames
23774 are no longer allowed. This also fixes potential vulnerabilities
23775 to servers providing hostnames as their address and then
23776 preferentially resolving them so they can partition users.
23777 - Our logic to decide if the OR we connected to was the right guy
23778 was brittle and maybe open to a mitm for invalid routers.
23780 o Security fixes, minor:
23781 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
23782 Ian Goldberg can prove things about our handshake protocol more
23784 - Make directory authorities generate a separate "guard" flag to
23785 mean "would make a good entry guard". Clients now honor the
23786 is_guard flag rather than looking at is_fast or is_stable.
23787 - Try to list MyFamily elements by key, not by nickname, and warn
23788 if we've not heard of a server.
23789 - Start using RAND_bytes rather than RAND_pseudo_bytes from
23790 OpenSSL. Also, reseed our entropy every hour, not just at
23791 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
23792 - Refuse server descriptors where the fingerprint line doesn't match
23793 the included identity key. Tor doesn't care, but other apps (and
23794 humans) might actually be trusting the fingerprint line.
23795 - We used to kill the circuit when we receive a relay command we
23796 don't recognize. Now we just drop that cell.
23797 - Fix a bug found by Lasse Overlier: when we were making internal
23798 circuits (intended to be cannibalized later for rendezvous and
23799 introduction circuits), we were picking them so that they had
23800 useful exit nodes. There was no need for this, and it actually
23801 aids some statistical attacks.
23802 - Start treating internal circuits and exit circuits separately.
23803 It's important to keep them separate because internal circuits
23804 have their last hops picked like middle hops, rather than like
23805 exit hops. So exiting on them will break the user's expectations.
23806 - Fix a possible way to DoS dirservers.
23807 - When the client asked for a rendezvous port that the hidden
23808 service didn't want to provide, we were sending an IP address
23809 back along with the end cell. Fortunately, it was zero. But stop
23812 o Packaging improvements:
23813 - Implement --with-libevent-dir option to ./configure. Improve
23814 search techniques to find libevent, and use those for openssl too.
23815 - Fix a couple of bugs in OpenSSL detection. Deal better when
23816 there are multiple SSLs installed with different versions.
23817 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
23818 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
23820 - Make unit tests (and other invocations that aren't the real Tor)
23821 run without launching listeners, creating subdirectories, and so on.
23822 - The OS X installer was adding a symlink for tor_resolve but
23823 the binary was called tor-resolve (reported by Thomas Hardly).
23824 - Now we can target arch and OS in rpm builds (contributed by
23825 Phobos). Also make the resulting dist-rpm filename match the
23827 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
23828 if you log to syslog and want something other than LOG_DAEMON.
23829 - Fix the torify (tsocks) config file to not use Tor for localhost
23831 - Start shipping socks-extensions.txt, tor-doc-unix.html,
23832 tor-doc-server.html, and stylesheet.css in the tarball.
23833 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
23834 They are useless now.
23835 - Add Peter Palfrader's contributed check-tor script. It lets you
23836 easily check whether a given server (referenced by nickname)
23837 is reachable by you.
23838 - Add BSD-style contributed startup script "rc.subr" from Peter
23841 o Directory improvements -- new directory protocol:
23842 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
23843 - Authorities and caches publish individual descriptors (by
23844 digest, by fingerprint, by "all", and by "tell me yours").
23845 - Clients don't download or use the old directory anymore. Now they
23846 download network-statuses from the directory authorities, and
23847 fetch individual server descriptors as needed from mirrors.
23848 - Clients don't download descriptors of non-running servers.
23849 - Download descriptors by digest, not by fingerprint. Caches try to
23850 download all listed digests from authorities; clients try to
23851 download "best" digests from caches. This avoids partitioning
23852 and isolating attacks better.
23853 - Only upload a new server descriptor when options change, 18
23854 hours have passed, uptime is reset, or bandwidth changes a lot.
23855 - Directory authorities silently throw away new descriptors that
23856 haven't changed much if the timestamps are similar. We do this to
23857 tolerate older Tor servers that upload a new descriptor every 15
23858 minutes. (It seemed like a good idea at the time.)
23859 - Clients choose directory servers from the network status lists,
23860 not from their internal list of router descriptors. Now they can
23861 go to caches directly rather than needing to go to authorities
23862 to bootstrap the first set of descriptors.
23863 - When picking a random directory, prefer non-authorities if any
23865 - Add a new flag to network-status indicating whether the server
23866 can answer v2 directory requests too.
23867 - Directory mirrors now cache up to 16 unrecognized network-status
23868 docs, so new directory authorities will be cached too.
23869 - Stop parsing, storing, or using running-routers output (but
23870 mirrors still cache and serve it).
23871 - Clients consider a threshold of "versioning" directory authorities
23872 before deciding whether to warn the user that he's obsolete.
23873 - Authorities publish separate sorted lists of recommended versions
23874 for clients and for servers.
23875 - Change DirServers config line to note which dirs are v1 authorities.
23876 - Put nicknames on the DirServer line, so we can refer to them
23877 without requiring all our users to memorize their IP addresses.
23878 - Remove option when getting directory cache to see whether they
23879 support running-routers; they all do now. Replace it with one
23880 to see whether caches support v2 stuff.
23881 - Stop listing down or invalid nodes in the v1 directory. This
23882 reduces its bulk by about 1/3, and reduces load on mirrors.
23883 - Mirrors no longer cache the v1 directory as often.
23884 - If we as a directory mirror don't know of any v1 directory
23885 authorities, then don't try to cache any v1 directories.
23887 o Other directory improvements:
23888 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
23889 fifth authoritative directory servers.
23890 - Directory authorities no longer require an open connection from
23891 a server to consider him "reachable". We need this change because
23892 when we add new directory authorities, old servers won't know not
23893 to hang up on them.
23894 - Dir authorities now do their own external reachability testing
23895 of each server, and only list as running the ones they found to
23896 be reachable. We also send back warnings to the server's logs if
23897 it uploads a descriptor that we already believe is unreachable.
23898 - Spread the directory authorities' reachability testing over the
23899 entire testing interval, so we don't try to do 500 TLS's at once
23901 - Make the "stable" router flag in network-status be the median of
23902 the uptimes of running valid servers, and make clients pay
23903 attention to the network-status flags. Thus the cutoff adapts
23904 to the stability of the network as a whole, making IRC, IM, etc
23905 connections more reliable.
23906 - Make the v2 dir's "Fast" flag based on relative capacity, just
23907 like "Stable" is based on median uptime. Name everything in the
23908 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
23909 - Retry directory requests if we fail to get an answer we like
23910 from a given dirserver (we were retrying before, but only if
23911 we fail to connect).
23912 - Return a robots.txt on our dirport to discourage google indexing.
23914 o Controller protocol improvements:
23915 - Revised controller protocol (version 1) that uses ascii rather
23916 than binary: tor/doc/control-spec.txt. Add supporting libraries
23917 in python and java and c# so you can use the controller from your
23918 applications without caring how our protocol works.
23919 - Allow the DEBUG controller event to work again. Mark certain log
23920 entries as "don't tell this to controllers", so we avoid cycles.
23921 - New controller function "getinfo accounting", to ask how
23922 many bytes we've used in this time period.
23923 - Add a "resetconf" command so you can set config options like
23924 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
23925 a config option in the torrc with no value, then it clears it
23926 entirely (rather than setting it to its default).
23927 - Add a "getinfo config-file" to tell us where torrc is. Also
23928 expose guard nodes, config options/names.
23929 - Add a "quit" command (when when using the controller manually).
23930 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
23931 stop using any currently-dirty circuits for new streams, so we
23932 don't link new actions to old actions. This also occurs on HUP
23933 or "signal reload".
23934 - If we would close a stream early (e.g. it asks for a .exit that
23935 we know would refuse it) but the LeaveStreamsUnattached config
23936 option is set by the controller, then don't close it.
23937 - Add a new controller event type "authdir_newdescs" that allows
23938 controllers to get all server descriptors that were uploaded to
23939 a router in its role as directory authority.
23940 - New controller option "getinfo desc/all-recent" to fetch the
23941 latest server descriptor for every router that Tor knows about.
23942 - Fix the controller's "attachstream 0" command to treat conn like
23943 it just connected, doing address remapping, handling .exit and
23944 .onion idioms, and so on. Now we're more uniform in making sure
23945 that the controller hears about new and closing connections.
23946 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
23947 the controller. Also, rotate dns and cpu workers if the controller
23948 changes options that will affect them; and initialize the dns
23949 worker cache tree whether or not we start out as a server.
23950 - Add a new circuit purpose 'controller' to let the controller ask
23951 for a circuit that Tor won't try to use. Extend the "extendcircuit"
23952 controller command to let you specify the purpose if you're starting
23953 a new circuit. Add a new "setcircuitpurpose" controller command to
23954 let you change a circuit's purpose after it's been created.
23955 - Let the controller ask for "getinfo dir/server/foo" so it can ask
23956 directly rather than connecting to the dir port. "getinfo
23957 dir/status/foo" also works, but currently only if your DirPort
23959 - Let the controller tell us about certain router descriptors
23960 that it doesn't want Tor to use in circuits. Implement
23961 "setrouterpurpose" and modify "+postdescriptor" to do this.
23962 - If the controller's *setconf commands fail, collect an error
23963 message in a string and hand it back to the controller -- don't
23964 just tell them to go read their logs.
23966 o Scalability, resource management, and performance:
23967 - Fix a major load balance bug: we were round-robin reading in 16 KB
23968 chunks, and servers with bandwidthrate of 20 KB, while downloading
23969 a 600 KB directory, would starve their other connections. Now we
23970 try to be a bit more fair.
23971 - Be more conservative about whether to advertise our DirPort.
23972 The main change is to not advertise if we're running at capacity
23973 and either a) we could hibernate ever or b) our capacity is low
23974 and we're using a default DirPort.
23975 - We weren't cannibalizing circuits correctly for
23976 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
23977 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
23978 build those from scratch. This should make hidden services faster.
23979 - Predict required circuits better, with an eye toward making hidden
23980 services faster on the service end.
23981 - Compress exit policies even more: look for duplicate lines and
23983 - Generate 18.0.0.0/8 address policy format in descs when we can;
23984 warn when the mask is not reducible to a bit-prefix.
23985 - There used to be two ways to specify your listening ports in a
23986 server descriptor: on the "router" line and with a separate "ports"
23987 line. Remove support for the "ports" line.
23988 - Reduce memory requirements in our structs by changing the order
23989 of fields. Replace balanced trees with hash tables. Inline
23990 bottleneck smartlist functions. Add a "Map from digest to void*"
23991 abstraction so we can do less hex encoding/decoding, and use it
23992 in router_get_by_digest(). Many other CPU and memory improvements.
23993 - Allow tor_gzip_uncompress to extract as much as possible from
23994 truncated compressed data. Try to extract as many
23995 descriptors as possible from truncated http responses (when
23996 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
23997 - Make circ->onionskin a pointer, not a static array. moria2 was using
23998 125000 circuit_t's after it had been up for a few weeks, which
23999 translates to 20+ megs of wasted space.
24000 - The private half of our EDH handshake keys are now chosen out
24001 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
24002 - Stop doing the complex voodoo overkill checking for insecure
24003 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
24004 - Do round-robin writes for TLS of at most 16 kB per write. This
24005 might be more fair on loaded Tor servers.
24006 - Do not use unaligned memory access on alpha, mips, or mipsel.
24007 It *works*, but is very slow, so we treat them as if it doesn't.
24009 o Other bugfixes and improvements:
24010 - Start storing useful information to $DATADIR/state, so we can
24011 remember things across invocations of Tor. Retain unrecognized
24012 lines so we can be forward-compatible, and write a TorVersion line
24013 so we can be backward-compatible.
24014 - If ORPort is set, Address is not explicitly set, and our hostname
24015 resolves to a private IP address, try to use an interface address
24016 if it has a public address. Now Windows machines that think of
24017 themselves as localhost can guess their address.
24018 - Regenerate our local descriptor if it's dirty and we try to use
24019 it locally (e.g. if it changes during reachability detection).
24020 This was causing some Tor servers to keep publishing the same
24021 initial descriptor forever.
24022 - Tor servers with dynamic IP addresses were needing to wait 18
24023 hours before they could start doing reachability testing using
24024 the new IP address and ports. This is because they were using
24025 the internal descriptor to learn what to test, yet they were only
24026 rebuilding the descriptor once they decided they were reachable.
24027 - It turns out we couldn't bootstrap a network since we added
24028 reachability detection in 0.1.0.1-rc. Good thing the Tor network
24029 has never gone down. Add an AssumeReachable config option to let
24030 servers and authorities bootstrap. When we're trying to build a
24031 high-uptime or high-bandwidth circuit but there aren't enough
24032 suitable servers, try being less picky rather than simply failing.
24033 - Newly bootstrapped Tor networks couldn't establish hidden service
24034 circuits until they had nodes with high uptime. Be more tolerant.
24035 - Really busy servers were keeping enough circuits open on stable
24036 connections that they were wrapping around the circuit_id
24037 space. (It's only two bytes.) This exposed a bug where we would
24038 feel free to reuse a circuit_id even if it still exists but has
24039 been marked for close. Try to fix this bug. Some bug remains.
24040 - When we fail to bind or listen on an incoming or outgoing
24041 socket, we now close it before refusing, rather than just
24042 leaking it. (Thanks to Peter Palfrader for finding.)
24043 - Fix a file descriptor leak in start_daemon().
24044 - On Windows, you can't always reopen a port right after you've
24045 closed it. So change retry_listeners() to only close and re-open
24046 ports that have changed.
24047 - Workaround a problem with some http proxies that refuse GET
24048 requests that specify "Content-Length: 0". Reported by Adrian.
24049 - Recover better from TCP connections to Tor servers that are
24050 broken but don't tell you (it happens!); and rotate TLS
24051 connections once a week.
24052 - Fix a scary-looking but apparently harmless bug where circuits
24053 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
24054 servers, and never switch to state CIRCUIT_STATE_OPEN.
24055 - Check for even more Windows version flags when writing the platform
24056 string in server descriptors, and note any we don't recognize.
24057 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
24058 get a better idea of why their circuits failed. Not used yet.
24059 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
24060 We don't use them yet, but maybe one day our DNS resolver will be
24061 able to discover them.
24062 - Let people type "tor --install" as well as "tor -install" when they
24063 want to make it an NT service.
24064 - Looks like we were never delivering deflated (i.e. compressed)
24065 running-routers lists, even when asked. Oops.
24066 - We were leaking some memory every time the client changed IPs.
24067 - Clean up more of the OpenSSL memory when exiting, so we can detect
24068 memory leaks better.
24069 - Never call free() on tor_malloc()d memory. This will help us
24070 use dmalloc to detect memory leaks.
24071 - Some Tor servers process billions of cells per day. These
24072 statistics are now uint64_t's.
24073 - Check [X-]Forwarded-For headers in HTTP requests when generating
24074 log messages. This lets people run dirservers (and caches) behind
24075 Apache but still know which IP addresses are causing warnings.
24076 - Fix minor integer overflow in calculating when we expect to use up
24077 our bandwidth allocation before hibernating.
24078 - Lower the minimum required number of file descriptors to 1000,
24079 so we can have some overhead for Valgrind on Linux, where the
24080 default ulimit -n is 1024.
24081 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
24082 and its existence is confusing some users.
24084 o Config option fixes:
24085 - Add a new config option ExitPolicyRejectPrivate which defaults
24086 to on. Now all exit policies will begin with rejecting private
24087 addresses, unless the server operator explicitly turns it off.
24088 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
24089 - Add new ReachableORAddresses and ReachableDirAddresses options
24090 that understand address policies. FascistFirewall is now a synonym
24091 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
24092 - Start calling it FooListenAddress rather than FooBindAddress,
24093 since few of our users know what it means to bind an address
24095 - If the user gave Tor an odd number of command-line arguments,
24096 we were silently ignoring the last one. Now we complain and fail.
24097 This wins the oldest-bug prize -- this bug has been present since
24098 November 2002, as released in Tor 0.0.0.
24099 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
24100 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
24101 it would silently ignore the 6668.
24102 - If we get a linelist or linelist_s config option from the torrc,
24103 e.g. ExitPolicy, and it has no value, warn and skip rather than
24104 silently resetting it to its default.
24105 - Setconf was appending items to linelists, not clearing them.
24106 - Add MyFamily to torrc.sample in the server section, so operators
24107 will be more likely to learn that it exists.
24108 - Make ContactInfo mandatory for authoritative directory servers.
24109 - MaxConn has been obsolete for a while now. Document the ConnLimit
24110 config option, which is a *minimum* number of file descriptors
24111 that must be available else Tor refuses to start.
24112 - Get rid of IgnoreVersion undocumented config option, and make us
24113 only warn, never exit, when we're running an obsolete version.
24114 - Make MonthlyAccountingStart config option truly obsolete now.
24115 - Correct the man page entry on TrackHostExitsExpire.
24116 - Let directory authorities start even if they don't specify an
24117 Address config option.
24118 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
24119 reflect the updated flags in our v2 dir protocol.
24121 o Config option features:
24122 - Add a new config option FastFirstHopPK (on by default) so clients
24123 do a trivial crypto handshake for their first hop, since TLS has
24124 already taken care of confidentiality and authentication.
24125 - Let the user set ControlListenAddress in the torrc. This can be
24126 dangerous, but there are some cases (like a secured LAN) where it
24128 - New config options to help controllers: FetchServerDescriptors
24129 and FetchHidServDescriptors for whether to fetch server
24130 info and hidserv info or let the controller do it, and
24131 PublishServerDescriptor and PublishHidServDescriptors.
24132 - Also let the controller set the __AllDirActionsPrivate config
24133 option if you want all directory fetches/publishes to happen via
24134 Tor (it assumes your controller bootstraps your circuits).
24135 - Add "HardwareAccel" config option: support for crypto hardware
24136 accelerators via OpenSSL. Off by default, until we find somebody
24137 smart who can test it for us. (It appears to produce seg faults
24138 in at least some cases.)
24139 - New config option "AuthDirRejectUnlisted" for directory authorities
24140 as a panic button: if we get flooded with unusable servers we can
24141 revert to only listing servers in the approved-routers file.
24142 - Directory authorities can now reject/invalidate by key and IP,
24143 with the config options "AuthDirInvalid" and "AuthDirReject", or
24144 by marking a fingerprint as "!reject" or "!invalid" (as its
24145 nickname) in the approved-routers file. This is useful since
24146 currently we automatically list servers as running and usable
24147 even if we know they're jerks.
24148 - Add a new config option TestSocks so people can see whether their
24149 applications are using socks4, socks4a, socks5-with-ip, or
24150 socks5-with-fqdn. This way they don't have to keep mucking
24151 with tcpdump and wondering if something got cached somewhere.
24152 - Add "private:*" as an alias in configuration for policies. Now
24153 you can simplify your exit policy rather than needing to list
24154 every single internal or nonroutable network space.
24155 - Accept "private:*" in routerdesc exit policies; not generated yet
24156 because older Tors do not understand it.
24157 - Add configuration option "V1AuthoritativeDirectory 1" which
24158 moria1, moria2, and tor26 have set.
24159 - Implement an option, VirtualAddrMask, to set which addresses
24160 get handed out in response to mapaddress requests. This works
24161 around a bug in tsocks where 127.0.0.0/8 is never socksified.
24162 - Add a new config option FetchUselessDescriptors, off by default,
24163 for when you plan to run "exitlist" on your client and you want
24164 to know about even the non-running descriptors.
24165 - SocksTimeout: How long do we let a socks connection wait
24166 unattached before we fail it?
24167 - CircuitBuildTimeout: Cull non-open circuits that were born
24168 at least this many seconds ago.
24169 - CircuitIdleTimeout: Cull open clean circuits that were born
24170 at least this many seconds ago.
24171 - New config option SafeSocks to reject all application connections
24172 using unsafe socks protocols. Defaults to off.
24174 o Improved and clearer log messages:
24175 - Reduce clutter in server logs. We're going to try to make
24176 them actually usable now. New config option ProtocolWarnings that
24177 lets you hear about how _other Tors_ are breaking the protocol. Off
24179 - Divide log messages into logging domains. Once we put some sort
24180 of interface on this, it will let people looking at more verbose
24181 log levels specify the topics they want to hear more about.
24182 - Log server fingerprint on startup, so new server operators don't
24183 have to go hunting around their filesystem for it.
24184 - Provide dire warnings to any users who set DirServer manually;
24185 move it out of torrc.sample and into torrc.complete.
24186 - Make the log message less scary when all the dirservers are
24187 temporarily unreachable.
24188 - When tor_socketpair() fails in Windows, give a reasonable
24189 Windows-style errno back.
24190 - Improve tor_gettimeofday() granularity on windows.
24191 - We were printing the number of idle dns workers incorrectly when
24193 - Handle duplicate lines in approved-routers files without warning.
24194 - We were whining about using socks4 or socks5-with-local-lookup
24195 even when it's an IP address in the "virtual" range we designed
24196 exactly for this case.
24197 - Check for named servers when looking them up by nickname;
24198 warn when we're calling a non-named server by its nickname;
24199 don't warn twice about the same name.
24200 - Downgrade the dirserver log messages when whining about
24202 - Correct "your server is reachable" log entries to indicate that
24203 it was self-testing that told us so.
24204 - If we're trying to be a Tor server and running Windows 95/98/ME
24205 as a server, explain that we'll likely crash.
24206 - Provide a more useful warn message when our onion queue gets full:
24207 the CPU is too slow or the exit policy is too liberal.
24208 - Don't warn when we receive a 503 from a dirserver/cache -- this
24209 will pave the way for them being able to refuse if they're busy.
24210 - When we fail to bind a listener, try to provide a more useful
24211 log message: e.g., "Is Tor already running?"
24212 - Only start testing reachability once we've established a
24213 circuit. This will make startup on dir authorities less noisy.
24214 - Don't try to upload hidden service descriptors until we have
24215 established a circuit.
24216 - Tor didn't warn when it failed to open a log file.
24217 - Warn when listening on a public address for socks. We suspect a
24218 lot of people are setting themselves up as open socks proxies,
24219 and they have no idea that jerks on the Internet are using them,
24220 since they simply proxy the traffic into the Tor network.
24221 - Give a useful message when people run Tor as the wrong user,
24222 rather than telling them to start chowning random directories.
24223 - Fix a harmless bug that was causing Tor servers to log
24224 "Got an end because of misc error, but we're not an AP. Closing."
24225 - Fix wrong log message when you add a "HiddenServiceNodes" config
24226 line without any HiddenServiceDir line (reported by Chris Thomas).
24227 - Directory authorities now stop whining so loudly about bad
24228 descriptors that they fetch from other dirservers. So when there's
24229 a log complaint, it's for sure from a freshly uploaded descriptor.
24230 - When logging via syslog, include the pid whenever we provide
24231 a log entry. Suggested by Todd Fries.
24232 - When we're shutting down and we do something like try to post a
24233 server descriptor or rendezvous descriptor, don't complain that
24234 we seem to be unreachable. Of course we are, we're shutting down.
24235 - Change log line for unreachability to explicitly suggest /etc/hosts
24236 as the culprit. Also make it clearer what IP address and ports we're
24237 testing for reachability.
24238 - Put quotes around user-supplied strings when logging so users are
24239 more likely to realize if they add bad characters (like quotes)
24241 - NT service patch from Matt Edman to improve error messages on Win32.
24244 Changes in version 0.1.0.17 - 2006-02-17
24245 o Crash bugfixes on 0.1.0.x:
24246 - When servers with a non-zero DirPort came out of hibernation,
24247 sometimes they would trigger an assert.
24249 o Other important bugfixes:
24250 - On platforms that don't have getrlimit (like Windows), we were
24251 artificially constraining ourselves to a max of 1024
24252 connections. Now just assume that we can handle as many as 15000
24253 connections. Hopefully this won't cause other problems.
24255 o Backported features:
24256 - When we're a server, a client asks for an old-style directory,
24257 and our write bucket is empty, don't give it to him. This way
24258 small servers can continue to serve the directory *sometimes*,
24259 without getting overloaded.
24260 - Whenever you get a 503 in response to a directory fetch, try
24261 once more. This will become important once servers start sending
24262 503's whenever they feel busy.
24263 - Fetch a new directory every 120 minutes, not every 40 minutes.
24264 Now that we have hundreds of thousands of users running the old
24265 directory algorithm, it's starting to hurt a lot.
24266 - Bump up the period for forcing a hidden service descriptor upload
24267 from 20 minutes to 1 hour.
24270 Changes in version 0.1.0.16 - 2006-01-02
24271 o Crash bugfixes on 0.1.0.x:
24272 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
24273 corrupting the heap, losing FDs, or crashing when we need to resize
24274 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
24275 - It turns out sparc64 platforms crash on unaligned memory access
24276 too -- so detect and avoid this.
24277 - Handle truncated compressed data correctly (by detecting it and
24279 - Fix possible-but-unlikely free(NULL) in control.c.
24280 - When we were closing connections, there was a rare case that
24281 stomped on memory, triggering seg faults and asserts.
24282 - Avoid potential infinite recursion when building a descriptor. (We
24283 don't know that it ever happened, but better to fix it anyway.)
24284 - We were neglecting to unlink marked circuits from soon-to-close OR
24285 connections, which caused some rare scribbling on freed memory.
24286 - Fix a memory stomping race bug when closing the joining point of two
24287 rendezvous circuits.
24288 - Fix an assert in time parsing found by Steven Murdoch.
24290 o Other bugfixes on 0.1.0.x:
24291 - When we're doing reachability testing, provide more useful log
24292 messages so the operator knows what to expect.
24293 - Do not check whether DirPort is reachable when we are suppressing
24294 advertising it because of hibernation.
24295 - When building with -static or on Solaris, we sometimes needed -ldl.
24296 - One of the dirservers (tor26) changed its IP address.
24297 - When we're deciding whether a stream has enough circuits around
24298 that can handle it, count the freshly dirty ones and not the ones
24299 that are so dirty they won't be able to handle it.
24300 - When we're expiring old circuits, we had a logic error that caused
24301 us to close new rendezvous circuits rather than old ones.
24302 - Give a more helpful log message when you try to change ORPort via
24303 the controller: you should upgrade Tor if you want that to work.
24304 - We were failing to parse Tor versions that start with "Tor ".
24305 - Tolerate faulty streams better: when a stream fails for reason
24306 exitpolicy, stop assuming that the router is lying about his exit
24307 policy. When a stream fails for reason misc, allow it to retry just
24308 as if it was resolvefailed. When a stream has failed three times,
24309 reset its failure count so we can try again and get all three tries.
24312 Changes in version 0.1.0.15 - 2005-09-23
24313 o Bugfixes on 0.1.0.x:
24314 - Reject ports 465 and 587 (spam targets) in default exit policy.
24315 - Don't crash when we don't have any spare file descriptors and we
24316 try to spawn a dns or cpu worker.
24317 - Get rid of IgnoreVersion undocumented config option, and make us
24318 only warn, never exit, when we're running an obsolete version.
24319 - Don't try to print a null string when your server finds itself to
24320 be unreachable and the Address config option is empty.
24321 - Make the numbers in read-history and write-history into uint64s,
24322 so they don't overflow and publish negatives in the descriptor.
24323 - Fix a minor memory leak in smartlist_string_remove().
24324 - We were only allowing ourselves to upload a server descriptor at
24325 most every 20 minutes, even if it changed earlier than that.
24326 - Clean up log entries that pointed to old URLs.
24329 Changes in version 0.1.0.14 - 2005-08-08
24330 o Bugfixes on 0.1.0.x:
24331 - Fix the other half of the bug with crypto handshakes
24333 - Fix an assert trigger if you send a 'signal term' via the
24334 controller when it's listening for 'event info' messages.
24337 Changes in version 0.1.0.13 - 2005-08-04
24338 o Bugfixes on 0.1.0.x:
24339 - Fix a critical bug in the security of our crypto handshakes.
24340 - Fix a size_t underflow in smartlist_join_strings2() that made
24341 it do bad things when you hand it an empty smartlist.
24342 - Fix Windows installer to ship Tor license (thanks to Aphex for
24343 pointing out this oversight) and put a link to the doc directory
24345 - Explicitly set no-unaligned-access for sparc: it turns out the
24346 new gcc's let you compile broken code, but that doesn't make it
24350 Changes in version 0.1.0.12 - 2005-07-18
24351 o New directory servers:
24352 - tor26 has changed IP address.
24354 o Bugfixes on 0.1.0.x:
24355 - Fix a possible double-free in tor_gzip_uncompress().
24356 - When --disable-threads is set, do not search for or link against
24357 pthreads libraries.
24358 - Don't trigger an assert if an authoritative directory server
24359 claims its dirport is 0.
24360 - Fix bug with removing Tor as an NT service: some people were
24361 getting "The service did not return an error." Thanks to Matt
24365 Changes in version 0.1.0.11 - 2005-06-30
24366 o Bugfixes on 0.1.0.x:
24367 - Fix major security bug: servers were disregarding their
24368 exit policies if clients behaved unexpectedly.
24369 - Make OS X init script check for missing argument, so we don't
24370 confuse users who invoke it incorrectly.
24371 - Fix a seg fault in "tor --hash-password foo".
24372 - The MAPADDRESS control command was broken.
24375 Changes in version 0.1.0.10 - 2005-06-14
24377 - Make NT services work and start on startup on Win32 (based on
24378 patch by Matt Edman). See the FAQ entry for details.
24379 - Make 'platform' string in descriptor more accurate for Win32
24380 servers, so it's not just "unknown platform".
24381 - REUSEADDR on normal platforms means you can rebind to the port
24382 right after somebody else has let it go. But REUSEADDR on Win32
24383 means you can bind to the port _even when somebody else already
24384 has it bound_! So, don't do that on Win32.
24385 - Clean up the log messages when starting on Win32 with no config
24387 - Allow seeding the RNG on Win32 even when you're not running as
24388 Administrator. If seeding the RNG on Win32 fails, quit.
24390 o Assert / crash bugs:
24391 - Refuse relay cells that claim to have a length larger than the
24392 maximum allowed. This prevents a potential attack that could read
24393 arbitrary memory (e.g. keys) from an exit server's process
24395 - If unofficial Tor clients connect and send weird TLS certs, our
24396 Tor server triggers an assert. Stop asserting, and start handling
24397 TLS errors better in other situations too.
24398 - Fix a race condition that can trigger an assert when we have a
24399 pending create cell and an OR connection attempt fails.
24402 - Use pthreads for worker processes rather than forking. This was
24403 forced because when we forked, we ended up wasting a lot of
24404 duplicate ram over time.
24405 - Also switch to foo_r versions of some library calls to allow
24406 reentry and threadsafeness.
24407 - Implement --disable-threads configure option. Disable threads on
24408 netbsd and openbsd by default, because they have no reentrant
24409 resolver functions (!), and on solaris since it has other
24411 - Fix possible bug on threading platforms (e.g. win32) which was
24412 leaking a file descriptor whenever a cpuworker or dnsworker died.
24413 - Fix a minor memory leak when somebody establishes an introduction
24414 point at your Tor server.
24415 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
24417 - Add ./configure --with-dmalloc option, to track memory leaks.
24418 - And try to free all memory on closing, so we can detect what
24421 o Protocol correctness:
24422 - When we've connected to an OR and handshaked but didn't like
24423 the result, we were closing the conn without sending destroy
24424 cells back for pending circuits. Now send those destroys.
24425 - Start sending 'truncated' cells back rather than destroy cells
24426 if the circuit closes in front of you. This means we won't have
24427 to abandon partially built circuits.
24428 - Handle changed router status correctly when dirserver reloads
24429 fingerprint file. We used to be dropping all unverified descriptors
24430 right then. The bug was hidden because we would immediately
24431 fetch a directory from another dirserver, which would include the
24432 descriptors we just dropped.
24433 - Revise tor-spec to add more/better stream end reasons.
24434 - Revise all calls to connection_edge_end to avoid sending 'misc',
24435 and to take errno into account where possible.
24436 - Client now retries when streams end early for 'hibernating' or
24437 'resource limit' reasons, rather than failing them.
24438 - Try to be more zealous about calling connection_edge_end when
24439 things go bad with edge conns in connection.c.
24441 o Robustness improvements:
24442 - Better handling for heterogeneous / unreliable nodes:
24443 - Annotate circuits with whether they aim to contain high uptime
24444 nodes and/or high capacity nodes. When building circuits, choose
24446 - This means that every single node in an intro rend circuit,
24447 not just the last one, will have a minimum uptime.
24448 - New config option LongLivedPorts to indicate application streams
24449 that will want high uptime circuits.
24450 - Servers reset uptime when a dir fetch entirely fails. This
24451 hopefully reflects stability of the server's network connectivity.
24452 - If somebody starts his tor server in Jan 2004 and then fixes his
24453 clock, don't make his published uptime be a year.
24454 - Reset published uptime when we wake up from hibernation.
24455 - Introduce a notion of 'internal' circs, which are chosen without
24456 regard to the exit policy of the last hop. Intro and rendezvous
24457 circs must be internal circs, to avoid leaking information. Resolve
24458 and connect streams can use internal circs if they want.
24459 - New circuit pooling algorithm: keep track of what destination ports
24460 we've used recently (start out assuming we'll want to use 80), and
24461 make sure to have enough circs around to satisfy these ports. Also
24462 make sure to have 2 internal circs around if we've required internal
24463 circs lately (and with high uptime if we've seen that lately too).
24464 - Turn addr_policy_compare from a tristate to a quadstate; this should
24465 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
24466 for google.com" problem.
24467 - When a client asks us for a dir mirror and we don't have one,
24468 launch an attempt to get a fresh one.
24469 - First cut at support for "create-fast" cells. Clients can use
24470 these when extending to their first hop, since the TLS already
24471 provides forward secrecy and authentication. Not enabled on
24474 o Reachability testing.
24475 - Your Tor server will automatically try to see if its ORPort and
24476 DirPort are reachable from the outside, and it won't upload its
24477 descriptor until it decides at least ORPort is reachable (when
24478 DirPort is not yet found reachable, publish it as zero).
24479 - When building testing circs for ORPort testing, use only
24480 high-bandwidth nodes, so fewer circuits fail.
24481 - Notice when our IP changes, and reset stats/uptime/reachability.
24482 - Authdirservers don't do ORPort reachability detection, since
24483 they're in clique mode, so it will be rare to find a server not
24484 already connected to them.
24485 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
24489 - Now we allow two unverified servers with the same nickname
24490 but different keys. But if a nickname is verified, only that
24491 nickname+key are allowed.
24492 - If you're an authdirserver connecting to an address:port,
24493 and it's not the OR you were expecting, forget about that
24494 descriptor. If he *was* the one you were expecting, then forget
24495 about all other descriptors for that address:port.
24496 - Allow servers to publish descriptors from 12 hours in the future.
24497 Corollary: only whine about clock skew from the dirserver if
24498 he's a trusted dirserver (since now even verified servers could
24499 have quite wrong clocks).
24500 - Require servers that use the default dirservers to have public IP
24501 addresses. We have too many servers that are configured with private
24502 IPs and their admins never notice the log entries complaining that
24503 their descriptors are being rejected.
24505 o Efficiency improvements:
24506 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
24507 and /dev/poll), and hopefully work better on Windows too.
24508 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
24509 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
24510 - Find libevent even if it's hiding in /usr/local/ and your
24511 CFLAGS and LDFLAGS don't tell you to look there.
24512 - Be able to link with libevent as a shared library (the default
24513 after 1.0d), even if it's hiding in /usr/local/lib and even
24514 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
24515 assuming you're running gcc. Otherwise fail and give a useful
24517 - Switch to a new buffer management algorithm, which tries to avoid
24518 reallocing and copying quite as much. In first tests it looks like
24519 it uses *more* memory on average, but less cpu.
24520 - Switch our internal buffers implementation to use a ring buffer,
24521 to hopefully improve performance for fast servers a lot.
24522 - Reenable the part of the code that tries to flush as soon as an
24523 OR outbuf has a full TLS record available. Perhaps this will make
24524 OR outbufs not grow as huge except in rare cases, thus saving lots
24525 of CPU time plus memory.
24526 - Improve performance for dirservers: stop re-parsing the whole
24527 directory every time you regenerate it.
24528 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
24529 it much faster to look up a circuit for each relay cell.
24530 - Remove most calls to assert_all_pending_dns_resolves_ok(),
24531 since they're eating our cpu on exit nodes.
24532 - Stop wasting time doing a case insensitive comparison for every
24533 dns name every time we do any lookup. Canonicalize the names to
24534 lowercase when you first see them.
24537 - Handle unavailable hidden services better. Handle slow or busy
24538 hidden services better.
24539 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
24540 circ as necessary, if there are any completed ones lying around
24541 when we try to launch one.
24542 - Make hidden services try to establish a rendezvous for 30 seconds
24543 after fetching the descriptor, rather than for n (where n=3)
24544 attempts to build a circuit.
24545 - Adjust maximum skew and age for rendezvous descriptors: let skew
24546 be 48 hours rather than 90 minutes.
24547 - Reject malformed .onion addresses rather then passing them on as
24548 normal web requests.
24551 - More Tor controller support. See
24552 http://tor.eff.org/doc/control-spec.txt for all the new features,
24553 including signals to emulate unix signals from any platform;
24554 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
24555 closestream; closecircuit; etc.
24556 - Encode hashed controller passwords in hex instead of base64,
24557 to make it easier to write controllers.
24558 - Revise control spec and implementation to allow all log messages to
24559 be sent to controller with their severities intact (suggested by
24560 Matt Edman). Disable debug-level logs while delivering a debug-level
24561 log to the controller, to prevent loop. Update TorControl to handle
24562 new log event types.
24564 o New config options/defaults:
24565 - Begin scrubbing sensitive strings from logs by default. Turn off
24566 the config option SafeLogging if you need to do debugging.
24567 - New exit policy: accept most low-numbered ports, rather than
24568 rejecting most low-numbered ports.
24569 - Put a note in the torrc about abuse potential with the default
24571 - Add support for CONNECTing through https proxies, with "HttpsProxy"
24573 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
24574 based on patch from Adam Langley (basic auth only).
24575 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
24576 the fast servers that have been joining lately. (Clients are now
24577 willing to load balance over up to 2 MB of advertised bandwidth
24579 - New config option MaxAdvertisedBandwidth which lets you advertise
24580 a low bandwidthrate (to not attract as many circuits) while still
24581 allowing a higher bandwidthrate in reality.
24582 - Require BandwidthRate to be at least 20kB/s for servers.
24583 - Add a NoPublish config option, so you can be a server (e.g. for
24584 testing running Tor servers in other Tor networks) without
24585 publishing your descriptor to the primary dirservers.
24586 - Add a new AddressMap config directive to rewrite incoming socks
24587 addresses. This lets you, for example, declare an implicit
24588 required exit node for certain sites.
24589 - Add a new TrackHostExits config directive to trigger addressmaps
24590 for certain incoming socks addresses -- for sites that break when
24591 your exit keeps changing (based on patch from Mike Perry).
24592 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
24593 which describes how often we retry making new circuits if current
24594 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
24595 how long we're willing to make use of an already-dirty circuit.
24596 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
24597 a config option "ShutdownWaitLength" (when using kill -INT on
24599 - Fix an edge case in parsing config options: if they say "--"
24600 on the commandline, it's not a config option (thanks weasel).
24601 - New config option DirAllowPrivateAddresses for authdirservers.
24602 Now by default they refuse router descriptors that have non-IP or
24603 private-IP addresses.
24604 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
24605 smart" default value: low for servers and high for clients.
24606 - Some people were putting "Address " in their torrc, and they had
24607 a buggy resolver that resolved " " to 0.0.0.0. Oops.
24608 - If DataDir is ~/.tor, and that expands to /.tor, then default to
24609 LOCALSTATEDIR/tor instead.
24610 - Implement --verify-config command-line option to check if your torrc
24611 is valid without actually launching Tor.
24613 o Logging improvements:
24614 - When dirservers refuse a server descriptor, we now log its
24615 contactinfo, platform, and the poster's IP address.
24616 - Only warn once per nickname from add_nickname_list_to_smartlist()
24617 per failure, so an entrynode or exitnode choice that's down won't
24619 - When we're connecting to an OR and he's got a different nickname/key
24620 than we were expecting, only complain loudly if we're an OP or a
24621 dirserver. Complaining loudly to the OR admins just confuses them.
24622 - Whine at you if you're a server and you don't set your contactinfo.
24623 - Warn when exit policy implicitly allows local addresses.
24624 - Give a better warning when some other server advertises an
24625 ORPort that is actually an apache running ssl.
24626 - If we get an incredibly skewed timestamp from a dirserver mirror
24627 that isn't a verified OR, don't warn -- it's probably him that's
24629 - When a dirserver causes you to give a warn, mention which dirserver
24631 - Initialize libevent later in the startup process, so the logs are
24632 already established by the time we start logging libevent warns.
24633 - Use correct errno on win32 if libevent fails.
24634 - Check and warn about known-bad/slow libevent versions.
24635 - Stop warning about sigpipes in the logs. We're going to
24636 pretend that getting these occasionally is normal and fine.
24638 o New contrib scripts:
24639 - New experimental script tor/contrib/exitlist: a simple python
24640 script to parse directories and find Tor nodes that exit to listed
24642 - New experimental script tor/contrib/ExerciseServer.py (needs more
24643 work) that uses the controller interface to build circuits and
24644 fetch pages over them. This will help us bootstrap servers that
24645 have lots of capacity but haven't noticed it yet.
24646 - New experimental script tor/contrib/PathDemo.py (needs more work)
24647 that uses the controller interface to let you choose whole paths
24649 "<hostname>.<path,separated by dots>.<length of path>.path"
24650 - New contributed script "privoxy-tor-toggle" to toggle whether
24651 Privoxy uses Tor. Seems to be configured for Debian by default.
24652 - Have torctl.in/tor.sh.in check for location of su binary (needed
24656 - chdir() to your datadirectory at the *end* of the daemonize process,
24657 not the beginning. This was a problem because the first time you
24658 run tor, if your datadir isn't there, and you have runasdaemon set
24659 to 1, it will try to chdir to it before it tries to create it. Oops.
24660 - Fix several double-mark-for-close bugs, e.g. where we were finding
24661 a conn for a cell even if that conn is already marked for close.
24662 - Stop most cases of hanging up on a socks connection without sending
24664 - Fix a bug in the RPM package: set home directory for _tor to
24665 something more reasonable when first installing.
24666 - Stop putting nodename in the Platform string in server descriptors.
24667 It doesn't actually help, and it is confusing/upsetting some people.
24668 - When using preferred entry or exit nodes, ignore whether the
24669 circuit wants uptime or capacity. They asked for the nodes, they
24671 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
24672 artificially capped at 500kB.
24673 - Cache local dns resolves correctly even when they're .exit
24675 - If we're hibernating and we get a SIGINT, exit immediately.
24676 - tor-resolve requests were ignoring .exit if there was a working circuit
24677 they could use instead.
24678 - Pay more attention to the ClientOnly config option.
24679 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
24680 installer screens; and don't put stuff into StartupItems unless
24681 the user asks you to.
24684 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
24685 rather than just rejecting it.
24686 - If our clock jumps forward by 100 seconds or more, assume something
24687 has gone wrong with our network and abandon all not-yet-used circs.
24688 - When an application is using socks5, give him the whole variety of
24689 potential socks5 responses (connect refused, host unreachable, etc),
24690 rather than just "success" or "failure".
24691 - A more sane version numbering system. See
24692 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
24693 - Change version parsing logic: a version is "obsolete" if it is not
24694 recommended and (1) there is a newer recommended version in the
24695 same series, or (2) there are no recommended versions in the same
24696 series, but there are some recommended versions in a newer series.
24697 A version is "new" if it is newer than any recommended version in
24699 - Report HTTP reasons to client when getting a response from directory
24700 servers -- so you can actually know what went wrong.
24701 - Reject odd-looking addresses at the client (e.g. addresses that
24702 contain a colon), rather than having the server drop them because
24704 - Stop publishing socksport in the directory, since it's not
24705 actually meant to be public. For compatibility, publish a 0 there
24707 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
24708 cookies to disk and doesn't log each web request to disk. (Thanks
24709 to Brett Carrington for pointing this out.)
24710 - Add OSX uninstall instructions. An actual uninstall script will
24712 - Add "opt hibernating 1" to server descriptor to make it clearer
24713 whether the server is hibernating.
24716 Changes in version 0.0.9.10 - 2005-06-16
24717 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
24718 - Refuse relay cells that claim to have a length larger than the
24719 maximum allowed. This prevents a potential attack that could read
24720 arbitrary memory (e.g. keys) from an exit server's process
24724 Changes in version 0.0.9.9 - 2005-04-23
24725 o Bugfixes on 0.0.9.x:
24726 - If unofficial Tor clients connect and send weird TLS certs, our
24727 Tor server triggers an assert. This release contains a minimal
24728 backport from the broader fix that we put into 0.1.0.4-rc.
24731 Changes in version 0.0.9.8 - 2005-04-07
24732 o Bugfixes on 0.0.9.x:
24733 - We have a bug that I haven't found yet. Sometimes, very rarely,
24734 cpuworkers get stuck in the 'busy' state, even though the cpuworker
24735 thinks of itself as idle. This meant that no new circuits ever got
24736 established. Here's a workaround to kill any cpuworker that's been
24737 busy for more than 100 seconds.
24740 Changes in version 0.0.9.7 - 2005-04-01
24741 o Bugfixes on 0.0.9.x:
24742 - Fix another race crash bug (thanks to Glenn Fink for reporting).
24743 - Compare identity to identity, not to nickname, when extending to
24744 a router not already in the directory. This was preventing us from
24745 extending to unknown routers. Oops.
24746 - Make sure to create OS X Tor user in <500 range, so we aren't
24747 creating actual system users.
24748 - Note where connection-that-hasn't-sent-end was marked, and fix
24749 a few really loud instances of this harmless bug (it's fixed more
24753 Changes in version 0.0.9.6 - 2005-03-24
24754 o Bugfixes on 0.0.9.x (crashes and asserts):
24755 - Add new end stream reasons to maintenance branch. Fix bug where
24756 reason (8) could trigger an assert. Prevent bug from recurring.
24757 - Apparently win32 stat wants paths to not end with a slash.
24758 - Fix assert triggers in assert_cpath_layer_ok(), where we were
24759 blowing away the circuit that conn->cpath_layer points to, then
24760 checking to see if the circ is well-formed. Backport check to make
24761 sure we dont use the cpath on a closed connection.
24762 - Prevent circuit_resume_edge_reading_helper() from trying to package
24763 inbufs for marked-for-close streams.
24764 - Don't crash on hup if your options->address has become unresolvable.
24765 - Some systems (like OS X) sometimes accept() a connection and tell
24766 you the remote host is 0.0.0.0:0. If this happens, due to some
24767 other mis-features, we get confused; so refuse the conn for now.
24769 o Bugfixes on 0.0.9.x (other):
24770 - Fix harmless but scary "Unrecognized content encoding" warn message.
24771 - Add new stream error reason: TORPROTOCOL reason means "you are not
24772 speaking a version of Tor I understand; say bye-bye to your stream."
24773 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
24774 into the future, now that we are more tolerant of skew. This
24775 resolves a bug where a Tor server would refuse to cache a directory
24776 because all the directories it gets are too far in the future;
24777 yet the Tor server never logs any complaints about clock skew.
24778 - Mac packaging magic: make man pages useable, and do not overwrite
24779 existing torrc files.
24780 - Make OS X log happily to /var/log/tor/tor.log
24783 Changes in version 0.0.9.5 - 2005-02-22
24784 o Bugfixes on 0.0.9.x:
24785 - Fix an assert race at exit nodes when resolve requests fail.
24786 - Stop picking unverified dir mirrors--it only leads to misery.
24787 - Patch from Matt Edman to make NT services work better. Service
24788 support is still not compiled into the executable by default.
24789 - Patch from Dmitri Bely so the Tor service runs better under
24790 the win32 SYSTEM account.
24791 - Make tor-resolve actually work (?) on Win32.
24792 - Fix a sign bug when getrlimit claims to have 4+ billion
24793 file descriptors available.
24794 - Stop refusing to start when bandwidthburst == bandwidthrate.
24795 - When create cells have been on the onion queue more than five
24796 seconds, just send back a destroy and take them off the list.
24799 Changes in version 0.0.9.4 - 2005-02-03
24800 o Bugfixes on 0.0.9:
24801 - Fix an assert bug that took down most of our servers: when
24802 a server claims to have 1 GB of bandwidthburst, don't
24804 - Don't crash as badly if we have spawned the max allowed number
24805 of dnsworkers, or we're out of file descriptors.
24806 - Block more file-sharing ports in the default exit policy.
24807 - MaxConn is now automatically set to the hard limit of max
24808 file descriptors we're allowed (ulimit -n), minus a few for
24810 - Give a clearer message when servers need to raise their
24811 ulimit -n when they start running out of file descriptors.
24812 - SGI Compatibility patches from Jan Schaumann.
24813 - Tolerate a corrupt cached directory better.
24814 - When a dirserver hasn't approved your server, list which one.
24815 - Go into soft hibernation after 95% of the bandwidth is used,
24816 not 99%. This is especially important for daily hibernators who
24817 have a small accounting max. Hopefully it will result in fewer
24818 cut connections when the hard hibernation starts.
24819 - Load-balance better when using servers that claim more than
24820 800kB/s of capacity.
24821 - Make NT services work (experimental, only used if compiled in).
24824 Changes in version 0.0.9.3 - 2005-01-21
24825 o Bugfixes on 0.0.9:
24826 - Backport the cpu use fixes from main branch, so busy servers won't
24827 need as much processor time.
24828 - Work better when we go offline and then come back, or when we
24829 run Tor at boot before the network is up. We do this by
24830 optimistically trying to fetch a new directory whenever an
24831 application request comes in and we think we're offline -- the
24832 human is hopefully a good measure of when the network is back.
24833 - Backport some minimal hidserv bugfixes: keep rend circuits open as
24834 long as you keep using them; actually publish hidserv descriptors
24835 shortly after they change, rather than waiting 20-40 minutes.
24836 - Enable Mac startup script by default.
24837 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
24838 - When you update AllowUnverifiedNodes or FirewallPorts via the
24839 controller's setconf feature, we were always appending, never
24841 - When you update HiddenServiceDir via setconf, it was screwing up
24842 the order of reading the lines, making it fail.
24843 - Do not rewrite a cached directory back to the cache; otherwise we
24844 will think it is recent and not fetch a newer one on startup.
24845 - Workaround for webservers that lie about Content-Encoding: Tor
24846 now tries to autodetect compressed directories and compression
24847 itself. This lets us Proxypass dir fetches through apache.
24850 Changes in version 0.0.9.2 - 2005-01-04
24851 o Bugfixes on 0.0.9 (crashes and asserts):
24852 - Fix an assert on startup when the disk is full and you're logging
24854 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
24855 style address, then we'd crash.
24856 - Fix an assert trigger when the running-routers string we get from
24857 a dirserver is broken.
24858 - Make worker threads start and run on win32. Now win32 servers
24860 - Bandaid (not actually fix, but now it doesn't crash) an assert
24861 where the dns worker dies mysteriously and the main Tor process
24862 doesn't remember anything about the address it was resolving.
24864 o Bugfixes on 0.0.9 (Win32):
24865 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
24866 name out of the warning/assert messages.
24867 - Fix a superficial "unhandled error on read" bug on win32.
24868 - The win32 installer no longer requires a click-through for our
24869 license, since our Free Software license grants rights but does not
24871 - Win32: When connecting to a dirserver fails, try another one
24872 immediately. (This was already working for non-win32 Tors.)
24873 - Stop trying to parse $HOME on win32 when hunting for default
24875 - Make tor-resolve.c work on win32 by calling network_init().
24877 o Bugfixes on 0.0.9 (other):
24878 - Make 0.0.9.x build on Solaris again.
24879 - Due to a fencepost error, we were blowing away the \n when reporting
24880 confvalue items in the controller. So asking for multiple config
24881 values at once couldn't work.
24882 - When listing circuits that are pending on an opening OR connection,
24883 if we're an OR we were listing circuits that *end* at us as
24884 being pending on every listener, dns/cpu worker, etc. Stop that.
24885 - Dirservers were failing to create 'running-routers' or 'directory'
24886 strings if we had more than some threshold of routers. Fix them so
24887 they can handle any number of routers.
24888 - Fix a superficial "Duplicate mark for close" bug.
24889 - Stop checking for clock skew for OR connections, even for servers.
24890 - Fix a fencepost error that was chopping off the last letter of any
24891 nickname that is the maximum allowed nickname length.
24892 - Update URLs in log messages so they point to the new website.
24893 - Fix a potential problem in mangling server private keys while
24894 writing to disk (not triggered yet, as far as we know).
24895 - Include the licenses for other free software we include in Tor,
24896 now that we're shipping binary distributions more regularly.
24899 Changes in version 0.0.9.1 - 2004-12-15
24900 o Bugfixes on 0.0.9:
24901 - Make hibernation actually work.
24902 - Make HashedControlPassword config option work.
24903 - When we're reporting event circuit status to a controller,
24904 don't use the stream status code.
24907 Changes in version 0.0.9 - 2004-12-12
24908 o Bugfixes on 0.0.8.1 (Crashes and asserts):
24909 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
24910 write() call will fail and we handle it there.
24911 - When we run out of disk space, or other log writing error, don't
24912 crash. Just stop logging to that log and continue.
24913 - Fix isspace() and friends so they still make Solaris happy
24914 but also so they don't trigger asserts on win32.
24915 - Fix assert failure on malformed socks4a requests.
24916 - Fix an assert bug where a hidden service provider would fail if
24917 the first hop of his rendezvous circuit was down.
24918 - Better handling of size_t vs int, so we're more robust on 64
24921 o Bugfixes on 0.0.8.1 (Win32):
24922 - Make windows sockets actually non-blocking (oops), and handle
24923 win32 socket errors better.
24924 - Fix parse_iso_time on platforms without strptime (eg win32).
24925 - win32: when being multithreaded, leave parent fdarray open.
24926 - Better handling of winsock includes on non-MSV win32 compilers.
24927 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
24929 - Make unit tests work on win32.
24931 o Bugfixes on 0.0.8.1 (Path selection and streams):
24932 - Calculate timeout for waiting for a connected cell from the time
24933 we sent the begin cell, not from the time the stream started. If
24934 it took a long time to establish the circuit, we would time out
24935 right after sending the begin cell.
24936 - Fix router_compare_addr_to_addr_policy: it was not treating a port
24937 of * as always matching, so we were picking reject *:* nodes as
24938 exit nodes too. Oops.
24939 - When read() failed on a stream, we would close it without sending
24940 back an end. So 'connection refused' would simply be ignored and
24941 the user would get no response.
24942 - Stop a sigpipe: when an 'end' cell races with eof from the app,
24943 we shouldn't hold-open-until-flush if the eof arrived first.
24944 - Let resolve conns retry/expire also, rather than sticking around
24946 - Fix more dns related bugs: send back resolve_failed and end cells
24947 more reliably when the resolve fails, rather than closing the
24948 circuit and then trying to send the cell. Also attach dummy resolve
24949 connections to a circuit *before* calling dns_resolve(), to fix
24950 a bug where cached answers would never be sent in RESOLVED cells.
24952 o Bugfixes on 0.0.8.1 (Circuits):
24953 - Finally fix a bug that's been plaguing us for a year:
24954 With high load, circuit package window was reaching 0. Whenever
24955 we got a circuit-level sendme, we were reading a lot on each
24956 socket, but only writing out a bit. So we would eventually reach
24957 eof. This would be noticed and acted on even when there were still
24958 bytes sitting in the inbuf.
24959 - Use identity comparison, not nickname comparison, to choose which
24960 half of circuit-ID-space each side gets to use. This is needed
24961 because sometimes we think of a router as a nickname, and sometimes
24962 as a hex ID, and we can't predict what the other side will do.
24964 o Bugfixes on 0.0.8.1 (Other):
24965 - Fix a whole slew of memory leaks.
24966 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
24967 - If we are using select, make sure we stay within FD_SETSIZE.
24968 - When poll() is interrupted, we shouldn't believe the revents values.
24969 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
24970 and smartlist_len, which are two major profiling offenders.
24971 - If do_hup fails, actually notice.
24972 - Flush the log file descriptor after we print "Tor opening log file",
24973 so we don't see those messages days later.
24974 - Hidden service operators now correctly handle version 1 style
24975 INTRODUCE1 cells (nobody generates them still, so not a critical
24977 - Handle more errnos from accept() without closing the listener.
24978 Some OpenBSD machines were closing their listeners because
24979 they ran out of file descriptors.
24980 - Some people had wrapped their tor client/server in a script
24981 that would restart it whenever it died. This did not play well
24982 with our "shut down if your version is obsolete" code. Now people
24983 don't fetch a new directory if their local cached version is
24985 - Make our autogen.sh work on ksh as well as bash.
24986 - Better torrc example lines for dirbindaddress and orbindaddress.
24987 - Improved bounds checking on parsed ints (e.g. config options and
24988 the ones we find in directories.)
24989 - Stop using separate defaults for no-config-file and
24990 empty-config-file. Now you have to explicitly turn off SocksPort,
24991 if you don't want it open.
24992 - We were starting to daemonize before we opened our logs, so if
24993 there were any problems opening logs, we would complain to stderr,
24994 which wouldn't work, and then mysteriously exit.
24995 - If a verified OR connects to us before he's uploaded his descriptor,
24996 or we verify him and hup but he still has the original TLS
24997 connection, then conn->nickname is still set like he's unverified.
24999 o Code security improvements, inspired by Ilja:
25000 - tor_snprintf wrapper over snprintf with consistent (though not C99)
25002 - Replace sprintf with tor_snprintf. (I think they were all safe, but
25004 - Replace strcpy/strncpy with strlcpy in more places.
25005 - Avoid strcat; use tor_snprintf or strlcat instead.
25007 o Features (circuits and streams):
25008 - New circuit building strategy: keep a list of ports that we've
25009 used in the past 6 hours, and always try to have 2 circuits open
25010 or on the way that will handle each such port. Seed us with port
25011 80 so web users won't complain that Tor is "slow to start up".
25012 - Make kill -USR1 dump more useful stats about circuits.
25013 - When warning about retrying or giving up, print the address, so
25014 the user knows which one it's talking about.
25015 - If you haven't used a clean circuit in an hour, throw it away,
25016 just to be on the safe side. (This means after 6 hours a totally
25017 unused Tor client will have no circuits open.)
25018 - Support "foo.nickname.exit" addresses, to let Alice request the
25019 address "foo" as viewed by exit node "nickname". Based on a patch
25020 from Geoff Goodell.
25021 - If your requested entry or exit node has advertised bandwidth 0,
25023 - Be more greedy about filling up relay cells -- we try reading again
25024 once we've processed the stuff we read, in case enough has arrived
25025 to fill the last cell completely.
25026 - Refuse application socks connections to port 0.
25027 - Use only 0.0.9pre1 and later servers for resolve cells.
25029 o Features (bandwidth):
25030 - Hibernation: New config option "AccountingMax" lets you
25031 set how many bytes per month (in each direction) you want to
25032 allow your server to consume. Rather than spreading those
25033 bytes out evenly over the month, we instead hibernate for some
25034 of the month and pop up at a deterministic time, work until
25035 the bytes are consumed, then hibernate again. Config option
25036 "MonthlyAccountingStart" lets you specify which day of the month
25037 your billing cycle starts on.
25038 - Implement weekly/monthly/daily accounting: now you specify your
25039 hibernation properties by
25040 AccountingMax N bytes|KB|MB|GB|TB
25041 AccountingStart day|week|month [day] HH:MM
25042 Defaults to "month 1 0:00".
25043 - Let bandwidth and interval config options be specified as 5 bytes,
25044 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
25046 o Features (directories):
25047 - New "router-status" line in directory, to better bind each verified
25048 nickname to its identity key.
25049 - Clients can ask dirservers for /dir.z to get a compressed version
25050 of the directory. Only works for servers running 0.0.9, of course.
25051 - Make clients cache directories and use them to seed their router
25052 lists at startup. This means clients have a datadir again.
25053 - Respond to content-encoding headers by trying to uncompress as
25055 - Clients and servers now fetch running-routers; cache
25056 running-routers; compress running-routers; serve compressed
25058 - Make moria2 advertise a dirport of 80, so people behind firewalls
25059 will be able to get a directory.
25060 - Http proxy support
25061 - Dirservers translate requests for http://%s:%d/x to /x
25062 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
25063 be routed through this host.
25064 - Clients ask for /tor/x rather than /x for new enough dirservers.
25065 This way we can one day coexist peacefully with apache.
25066 - Clients specify a "Host: %s%d" http header, to be compatible
25067 with more proxies, and so running squid on an exit node can work.
25068 - Protect dirservers from overzealous descriptor uploading -- wait
25069 10 seconds after directory gets dirty, before regenerating.
25071 o Features (packages and install):
25072 - Add NSI installer contributed by J Doe.
25073 - Apply NT service patch from Osamu Fujino. Still needs more work.
25074 - Commit VC6 and VC7 workspace/project files.
25075 - Commit a tor.spec for making RPM files, with help from jbash.
25076 - Add contrib/torctl.in contributed by Glenn Fink.
25077 - Make expand_filename handle ~ and ~username.
25078 - Use autoconf to enable largefile support where necessary. Use
25079 ftello where available, since ftell can fail at 2GB.
25080 - Ship src/win32/ in the tarball, so people can use it to build.
25081 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
25084 o Features (ui controller):
25085 - Control interface: a separate program can now talk to your
25086 client/server over a socket, and get/set config options, receive
25087 notifications of circuits and streams starting/finishing/dying,
25088 bandwidth used, etc. The next step is to get some GUIs working.
25089 Let us know if you want to help out. See doc/control-spec.txt .
25090 - Ship a contrib/tor-control.py as an example script to interact
25091 with the control port.
25092 - "tor --hash-password zzyxz" will output a salted password for
25093 use in authenticating to the control interface.
25094 - Implement the control-spec's SAVECONF command, to write your
25095 configuration to torrc.
25096 - Get cookie authentication for the controller closer to working.
25097 - When set_conf changes our server descriptor, upload a new copy.
25098 But don't upload it too often if there are frequent changes.
25100 o Features (config and command-line):
25101 - Deprecate unofficial config option abbreviations, and abbreviations
25102 not on the command line.
25103 - Configuration infrastructure support for warning on obsolete
25105 - Give a slightly more useful output for "tor -h".
25106 - Break DirFetchPostPeriod into:
25107 - DirFetchPeriod for fetching full directory,
25108 - StatusFetchPeriod for fetching running-routers,
25109 - DirPostPeriod for posting server descriptor,
25110 - RendPostPeriod for posting hidden service descriptors.
25111 - New log format in config:
25112 "Log minsev[-maxsev] stdout|stderr|syslog" or
25113 "Log minsev[-maxsev] file /var/foo"
25114 - DirPolicy config option, to let people reject incoming addresses
25115 from their dirserver.
25116 - "tor --list-fingerprint" will list your identity key fingerprint
25118 - Make tor --version --version dump the cvs Id of every file.
25119 - New 'MyFamily nick1,...' config option for a server to
25120 specify other servers that shouldn't be used in the same circuit
25121 with it. Only believed if nick1 also specifies us.
25122 - New 'NodeFamily nick1,nick2,...' config option for a client to
25123 specify nodes that it doesn't want to use in the same circuit.
25124 - New 'Redirectexit pattern address:port' config option for a
25125 server to redirect exit connections, e.g. to a local squid.
25126 - Add "pass" target for RedirectExit, to make it easier to break
25127 out of a sequence of RedirectExit rules.
25128 - Make the dirservers file obsolete.
25129 - Include a dir-signing-key token in directories to tell the
25130 parsing entity which key is being used to sign.
25131 - Remove the built-in bulky default dirservers string.
25132 - New config option "Dirserver %s:%d [fingerprint]", which can be
25133 repeated as many times as needed. If no dirservers specified,
25134 default to moria1,moria2,tor26.
25135 - Make 'Routerfile' config option obsolete.
25136 - Discourage people from setting their dirfetchpostperiod more often
25137 than once per minute.
25139 o Features (other):
25140 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
25141 get back to normal.)
25142 - Accept *:706 (silc) in default exit policy.
25143 - Implement new versioning format for post 0.1.
25144 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
25145 log more informatively.
25146 - Check clock skew for verified servers, but allow unverified
25147 servers and clients to have any clock skew.
25148 - Make sure the hidden service descriptors are at a random offset
25149 from each other, to hinder linkability.
25150 - Clients now generate a TLS cert too, in preparation for having
25151 them act more like real nodes.
25152 - Add a pure-C tor-resolve implementation.
25153 - Use getrlimit and friends to ensure we can reach MaxConn (currently
25154 1024) file descriptors.
25155 - Raise the max dns workers from 50 to 100.
25158 Changes in version 0.0.8.1 - 2004-10-13
25160 - Fix a seg fault that can be triggered remotely for Tor
25161 clients/servers with an open dirport.
25162 - Fix a rare assert trigger, where routerinfos for entries in
25163 our cpath would expire while we're building the path.
25164 - Fix a bug in OutboundBindAddress so it (hopefully) works.
25165 - Fix a rare seg fault for people running hidden services on
25166 intermittent connections.
25167 - Fix a bug in parsing opt keywords with objects.
25168 - Fix a stale pointer assert bug when a stream detaches and
25170 - Fix a string format vulnerability (probably not exploitable)
25171 in reporting stats locally.
25172 - Fix an assert trigger: sometimes launching circuits can fail
25173 immediately, e.g. because too many circuits have failed recently.
25174 - Fix a compile warning on 64 bit platforms.
25177 Changes in version 0.0.8 - 2004-08-25
25179 - Made our unit tests compile again on OpenBSD 3.5, and tor
25180 itself compile again on OpenBSD on a sparc64.
25181 - We were neglecting milliseconds when logging on win32, so
25182 everything appeared to happen at the beginning of each second.
25183 - Check directory signature _before_ you decide whether you're
25184 you're running an obsolete version and should exit.
25185 - Check directory signature _before_ you parse the running-routers
25186 list to decide who's running.
25187 - Check return value of fclose while writing to disk, so we don't
25188 end up with broken files when servers run out of disk space.
25189 - Port it to SunOS 5.9 / Athena
25190 - Fix two bugs in saving onion keys to disk when rotating, so
25191 hopefully we'll get fewer people using old onion keys.
25192 - Remove our mostly unused -- and broken -- hex_encode()
25193 function. Use base16_encode() instead. (Thanks to Timo Lindfors
25194 for pointing out this bug.)
25195 - Only pick and establish intro points after we've gotten a
25197 - Fix assert triggers: if the other side returns an address 0.0.0.0,
25198 don't put it into the client dns cache.
25199 - If a begin failed due to exit policy, but we believe the IP
25200 address should have been allowed, switch that router to exitpolicy
25201 reject *:* until we get our next directory.
25203 o Protocol changes:
25204 - 'Extend' relay cell payloads now include the digest of the
25205 intended next hop's identity key. Now we can verify that we're
25206 extending to the right router, and also extend to routers we
25207 hadn't heard of before.
25210 - Tor nodes can now act as relays (with an advertised ORPort)
25211 without being manually verified by the dirserver operators.
25212 - Uploaded descriptors of unverified routers are now accepted
25213 by the dirservers, and included in the directory.
25214 - Verified routers are listed by nickname in the running-routers
25215 list; unverified routers are listed as "$<fingerprint>".
25216 - We now use hash-of-identity-key in most places rather than
25217 nickname or addr:port, for improved security/flexibility.
25218 - AllowUnverifiedNodes config option to let circuits choose no-name
25219 routers in entry,middle,exit,introduction,rendezvous positions.
25220 Allow middle and rendezvous positions by default.
25221 - When picking unverified routers, skip those with low uptime and/or
25222 low bandwidth, depending on what properties you care about.
25223 - ClientOnly option for nodes that never want to become servers.
25224 - Directory caching.
25225 - "AuthoritativeDir 1" option for the official dirservers.
25226 - Now other nodes (clients and servers) will cache the latest
25227 directory they've pulled down.
25228 - They can enable their DirPort to serve it to others.
25229 - Clients will pull down a directory from any node with an open
25230 DirPort, and check the signature/timestamp correctly.
25231 - Authoritative dirservers now fetch directories from other
25232 authdirservers, to stay better synced.
25233 - Running-routers list tells who's down also, along with noting
25234 if they're verified (listed by nickname) or unverified (listed
25236 - Allow dirservers to serve running-router list separately.
25237 This isn't used yet.
25238 - You can now fetch $DIRURL/running-routers to get just the
25239 running-routers line, not the whole descriptor list. (But
25240 clients don't use this yet.)
25241 - Clients choose nodes proportional to advertised bandwidth.
25242 - Clients avoid using nodes with low uptime as introduction points.
25243 - Handle servers with dynamic IP addresses: don't just replace
25244 options->Address with the resolved one at startup, and
25245 detect our address right before we make a routerinfo each time.
25246 - 'FascistFirewall' option to pick dirservers and ORs on specific
25247 ports; plus 'FirewallPorts' config option to tell FascistFirewall
25248 which ports are open. (Defaults to 80,443)
25249 - Try other dirservers immediately if the one you try is down. This
25250 should tolerate down dirservers better now.
25251 - ORs connect-on-demand to other ORs
25252 - If you get an extend cell to an OR you're not connected to,
25253 connect, handshake, and forward the create cell.
25254 - The authoritative dirservers stay connected to everybody,
25255 and everybody stays connected to 0.0.7 servers, but otherwise
25256 clients/servers expire unused connections after 5 minutes.
25257 - When servers get a sigint, they delay 30 seconds (refusing new
25258 connections) then exit. A second sigint causes immediate exit.
25259 - File and name management:
25260 - Look for .torrc if no CONFDIR "torrc" is found.
25261 - If no datadir is defined, then choose, make, and secure ~/.tor
25263 - If torrc not found, exitpolicy reject *:*.
25264 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
25265 - If no nickname is defined, derive default from hostname.
25266 - Rename secret key files, e.g. identity.key -> secret_id_key,
25267 to discourage people from mailing their identity key to tor-ops.
25268 - Refuse to build a circuit before the directory has arrived --
25269 it won't work anyway, since you won't know the right onion keys
25271 - Parse tor version numbers so we can do an is-newer-than check
25272 rather than an is-in-the-list check.
25273 - New socks command 'resolve', to let us shim gethostbyname()
25275 - A 'tor_resolve' script to access the socks resolve functionality.
25276 - A new socks-extensions.txt doc file to describe our
25277 interpretation and extensions to the socks protocols.
25278 - Add a ContactInfo option, which gets published in descriptor.
25279 - Write tor version at the top of each log file
25280 - New docs in the tarball:
25282 - Document that you should proxy your SSL traffic too.
25283 - Log a warning if the user uses an unsafe socks variant, so people
25284 are more likely to learn about privoxy or socat.
25285 - Log a warning if you're running an unverified server, to let you
25286 know you might want to get it verified.
25287 - Change the default exit policy to reject the default edonkey,
25288 kazaa, gnutella ports.
25289 - Add replace_file() to util.[ch] to handle win32's rename().
25290 - Publish OR uptime in descriptor (and thus in directory) too.
25291 - Remember used bandwidth (both in and out), and publish 15-minute
25292 snapshots for the past day into our descriptor.
25293 - Be more aggressive about trying to make circuits when the network
25294 has changed (e.g. when you unsuspend your laptop).
25295 - Check for time skew on http headers; report date in response to
25297 - If the entrynode config line has only one node, don't pick it as
25299 - Add strict{entry|exit}nodes config options. If set to 1, then
25300 we refuse to build circuits that don't include the specified entry
25302 - OutboundBindAddress config option, to bind to a specific
25303 IP address for outgoing connect()s.
25304 - End truncated log entries (e.g. directories) with "[truncated]".
25307 Changes in version 0.0.7.3 - 2004-08-12
25308 o Stop dnsworkers from triggering an assert failure when you
25309 ask them to resolve the host "".
25312 Changes in version 0.0.7.2 - 2004-07-07
25313 o A better fix for the 0.0.0.0 problem, that will hopefully
25314 eliminate the remaining related assertion failures.
25317 Changes in version 0.0.7.1 - 2004-07-04
25318 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
25319 since internally we use 0.0.0.0 to signify "not yet resolved".
25322 Changes in version 0.0.7 - 2004-06-07
25323 o Fixes for crashes and other obnoxious bugs:
25324 - Fix an epipe bug: sometimes when directory connections failed
25325 to connect, we would give them a chance to flush before closing
25327 - When we detached from a circuit because of resolvefailed, we
25328 would immediately try the same circuit twice more, and then
25329 give up on the resolve thinking we'd tried three different
25331 - Limit the number of intro circuits we'll attempt to build for a
25332 hidden service per 15-minute period.
25333 - Check recommended-software string *early*, before actually parsing
25334 the directory. Thus we can detect an obsolete version and exit,
25335 even if the new directory format doesn't parse.
25336 o Fixes for security bugs:
25337 - Remember which nodes are dirservers when you startup, and if a
25338 random OR enables his dirport, don't automatically assume he's
25339 a trusted dirserver.
25341 - Directory connections were asking the wrong poll socket to
25342 start writing, and not asking themselves to start writing.
25343 - When we detached from a circuit because we sent a begin but
25344 didn't get a connected, we would use it again the first time;
25345 but after that we would correctly switch to a different one.
25346 - Stop warning when the first onion decrypt attempt fails; they
25347 will sometimes legitimately fail now that we rotate keys.
25348 - Override unaligned-access-ok check when $host_cpu is ia64 or
25349 arm. Apparently they allow it but the kernel whines.
25350 - Dirservers try to reconnect periodically too, in case connections
25352 - Fix some memory leaks in directory servers.
25353 - Allow backslash in Win32 filenames.
25354 - Made Tor build complain-free on FreeBSD, hopefully without
25355 breaking other BSD builds. We'll see.
25356 - Check directory signatures based on name of signer, not on whom
25357 we got the directory from. This will let us cache directories more
25359 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
25362 - Doxygen markup on all functions and global variables.
25363 - Make directory functions update routerlist, not replace it. So
25364 now directory disagreements are not so critical a problem.
25365 - Remove the upper limit on number of descriptors in a dirserver's
25366 directory (not that we were anywhere close).
25367 - Allow multiple logfiles at different severity ranges.
25368 - Allow *BindAddress to specify ":port" rather than setting *Port
25369 separately. Allow multiple instances of each BindAddress config
25370 option, so you can bind to multiple interfaces if you want.
25371 - Allow multiple exit policy lines, which are processed in order.
25372 Now we don't need that huge line with all the commas in it.
25373 - Enable accept/reject policies on SOCKS connections, so you can bind
25374 to 0.0.0.0 but still control who can use your OP.
25375 - Updated the man page to reflect these features.
25378 Changes in version 0.0.6.2 - 2004-05-16
25379 o Our integrity-checking digest was checking only the most recent cell,
25380 not the previous cells like we'd thought.
25381 Thanks to Stefan Mark for finding the flaw!
25384 Changes in version 0.0.6.1 - 2004-05-06
25385 o Fix two bugs in our AES counter-mode implementation (this affected
25386 onion-level stream encryption, but not TLS-level). It turns
25387 out we were doing something much more akin to a 16-character
25388 polyalphabetic cipher. Oops.
25389 Thanks to Stefan Mark for finding the flaw!
25390 o Retire moria3 as a directory server, and add tor26 as a directory
25394 Changes in version 0.0.6 - 2004-05-02
25396 - Hidden services and rendezvous points are implemented. Go to
25397 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
25398 hidden services. (This only works via a socks4a proxy such as
25399 Privoxy, and currently it's quite slow.)
25400 - We now rotate link (tls context) keys and onion keys.
25401 - CREATE cells now include oaep padding, so you can tell
25402 if you decrypted them correctly.
25403 - Retry stream correctly when we fail to connect because of
25404 exit-policy-reject (should try another) or can't-resolve-address.
25405 - When we hup a dirserver and we've *removed* a server from the
25406 approved-routers list, now we remove that server from the
25407 in-memory directories too.
25408 - Add bandwidthburst to server descriptor.
25409 - Directories now say which dirserver signed them.
25410 - Use a tor_assert macro that logs failed assertions too.
25411 - Since we don't support truncateds much, don't bother sending them;
25412 just close the circ.
25413 - Fetch randomness from /dev/urandom better (not via fopen/fread)
25414 - Better debugging for tls errors
25415 - Set Content-Type on the directory and hidserv descriptor.
25416 - Remove IVs from cipher code, since AES-ctr has none.
25418 - Fix an assert trigger for exit nodes that's been plaguing us since
25419 the days of 0.0.2prexx (thanks weasel!)
25420 - Fix a bug where we were closing tls connections intermittently.
25421 It turns out openssl keeps its errors around -- so if an error
25422 happens, and you don't ask about it, and then another openssl
25423 operation happens and succeeds, and you ask if there was an error,
25424 it tells you about the first error.
25425 - Fix a bug that's been lurking since 27 may 03 (!)
25426 When passing back a destroy cell, we would use the wrong circ id.
25427 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
25428 - Some versions of openssl have an SSL_pending function that erroneously
25429 returns bytes when there is a non-application record pending.
25430 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
25431 o We were using an array of length zero in a few places.
25432 o Win32's gethostbyname can't resolve an IP to an IP.
25433 o Win32's close can't close a socket.
25434 o Handle windows socket errors correctly.
25436 - check for <sys/limits.h> so we build on FreeBSD again, and
25437 <machine/limits.h> for NetBSD.
25440 Changes in version 0.0.5 - 2004-03-30
25441 o Install torrc as torrc.sample -- we no longer clobber your
25443 o Fix mangled-state bug in directory fetching (was causing sigpipes).
25444 o Only build circuits after we've fetched the directory: clients were
25445 using only the directory servers before they'd fetched a directory.
25446 This also means longer startup time; so it goes.
25447 o Fix an assert trigger where an OP would fail to handshake, and we'd
25448 expect it to have a nickname.
25449 o Work around a tsocks bug: do a socks reject when AP connection dies
25450 early, else tsocks goes into an infinite loop.
25451 o Hold socks connection open until reply is flushed (if possible)
25452 o Make exit nodes resolve IPs to IPs immediately, rather than asking
25453 the dns farm to do it.
25454 o Fix c99 aliasing warnings in rephist.c
25455 o Don't include server descriptors that are older than 24 hours in the
25457 o Give socks 'reject' replies their whole 15s to attempt to flush,
25458 rather than seeing the 60s timeout and assuming the flush had failed.
25459 o Clean automake droppings from the cvs repository
25460 o Add in a 'notice' log level for things the operator should hear
25461 but that aren't warnings
25464 Changes in version 0.0.4 - 2004-03-26
25465 o When connecting to a dirserver or OR and the network is down,
25469 Changes in version 0.0.3 - 2004-03-26
25470 o Warn and fail if server chose a nickname with illegal characters
25471 o Port to Solaris and Sparc:
25472 - include missing header fcntl.h
25473 - have autoconf find -lsocket -lnsl automatically
25474 - deal with hardware word alignment
25475 - make uname() work (solaris has a different return convention)
25476 - switch from using signal() to sigaction()
25477 o Preliminary work on reputation system:
25478 - Keep statistics on success/fail of connect attempts; they're published
25479 by kill -USR1 currently.
25480 - Add a RunTesting option to try to learn link state by creating test
25481 circuits, even when SocksPort is off.
25482 - Remove unused open circuits when there are too many.
25485 Changes in version 0.0.2 - 2004-03-19
25486 - Include strlcpy and strlcat for safer string ops
25487 - define INADDR_NONE so we compile (but still not run) on solaris
25490 Changes in version 0.0.2pre27 - 2004-03-14
25492 - Allow internal tor networks (we were rejecting internal IPs,
25493 now we allow them if they're set explicitly).
25494 - And fix a few endian issues.
25497 Changes in version 0.0.2pre26 - 2004-03-14
25499 - If a stream times out after 15s without a connected cell, don't
25500 try that circuit again: try a new one.
25501 - Retry streams at most 4 times. Then give up.
25502 - When a dirserver gets a descriptor from an unknown router, it
25503 logs its fingerprint (so the dirserver operator can choose to
25504 accept it even without mail from the server operator).
25505 - Inform unapproved servers when we reject their descriptors.
25506 - Make tor build on Windows again. It works as a client, who knows
25508 - Clearer instructions in the torrc for how to set up a server.
25509 - Be more efficient about reading fd's when our global token bucket
25510 (used for rate limiting) becomes empty.
25512 - Stop asserting that computers always go forward in time. It's
25514 - When we sent a cell (e.g. destroy) and then marked an OR connection
25515 expired, we might close it before finishing a flush if the other
25516 side isn't reading right then.
25517 - Don't allow dirservers to start if they haven't defined
25518 RecommendedVersions
25519 - We were caching transient dns failures. Oops.
25520 - Prevent servers from publishing an internal IP as their address.
25521 - Address a strcat vulnerability in circuit.c
25524 Changes in version 0.0.2pre25 - 2004-03-04
25526 - Put the OR's IP in its router descriptor, not its fqdn. That way
25527 we'll stop being stalled by gethostbyname for nodes with flaky dns,
25530 - If the user typed in an address that didn't resolve, the server
25534 Changes in version 0.0.2pre24 - 2004-03-03
25536 - Fix an assertion failure in dns.c, where we were trying to dequeue
25537 a pending dns resolve even if it wasn't pending
25538 - Fix a spurious socks5 warning about still trying to write after the
25539 connection is finished.
25540 - Hold certain marked_for_close connections open until they're finished
25541 flushing, rather than losing bytes by closing them too early.
25542 - Correctly report the reason for ending a stream
25543 - Remove some duplicate calls to connection_mark_for_close
25544 - Put switch_id and start_daemon earlier in the boot sequence, so it
25545 will actually try to chdir() to options.DataDirectory
25546 - Make 'make test' exit(1) if a test fails; fix some unit tests
25547 - Make tor fail when you use a config option it doesn't know about,
25548 rather than warn and continue.
25549 - Make --version work
25550 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
25553 Changes in version 0.0.2pre23 - 2004-02-29
25555 - Print a statement when the first circ is finished, so the user
25556 knows it's working.
25557 - If a relay cell is unrecognized at the end of the circuit,
25558 send back a destroy. (So attacks to mutate cells are more
25560 - New config option 'excludenodes' to avoid certain nodes for circuits.
25561 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
25562 so you can collect coredumps there.
25564 - Fix a bug in tls flushing where sometimes data got wedged and
25565 didn't flush until more data got sent. Hopefully this bug was
25566 a big factor in the random delays we were seeing.
25567 - Make 'connected' cells include the resolved IP, so the client
25568 dns cache actually gets populated.
25569 - Disallow changing from ORPort=0 to ORPort>0 on hup.
25570 - When we time-out on a stream and detach from the circuit, send an
25571 end cell down it first.
25572 - Only warn about an unknown router (in exitnodes, entrynodes,
25573 excludenodes) after we've fetched a directory.
25576 Changes in version 0.0.2pre22 - 2004-02-26
25578 - Servers publish less revealing uname information in descriptors.
25579 - More memory tracking and assertions, to crash more usefully when
25581 - If the default torrc isn't there, just use some default defaults.
25582 Plus provide an internal dirservers file if they don't have one.
25583 - When the user tries to use Tor as an http proxy, give them an http
25584 501 failure explaining that we're a socks proxy.
25585 - Dump a new router.desc on hup, to help confused people who change
25586 their exit policies and then wonder why router.desc doesn't reflect
25588 - Clean up the generic tor.sh init script that we ship with.
25590 - If the exit stream is pending on the resolve, and a destroy arrives,
25591 then the stream wasn't getting removed from the pending list. I
25592 think this was the one causing recent server crashes.
25593 - Use a more robust poll on OSX 10.3, since their poll is flaky.
25594 - When it couldn't resolve any dirservers, it was useless from then on.
25595 Now it reloads the RouterFile (or default dirservers) if it has no
25597 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
25598 many users don't even *have* a /usr/local/sbin/.
25601 Changes in version 0.0.2pre21 - 2004-02-18
25603 - There's a ChangeLog file that actually reflects the changelog.
25604 - There's a 'torify' wrapper script, with an accompanying
25605 tor-tsocks.conf, that simplifies the process of using tsocks for
25606 tor. It even has a man page.
25607 - The tor binary gets installed to sbin rather than bin now.
25608 - Retry streams where the connected cell hasn't arrived in 15 seconds
25609 - Clean up exit policy handling -- get the default out of the torrc,
25610 so we can update it without forcing each server operator to fix
25612 - Allow imaps and pop3s in default exit policy
25614 - Prevent picking middleman nodes as the last node in the circuit
25617 Changes in version 0.0.2pre20 - 2004-01-30
25619 - We now have a deb package, and it's in debian unstable. Go to
25620 it, apt-getters. :)
25621 - I've split the TotalBandwidth option into BandwidthRate (how many
25622 bytes per second you want to allow, long-term) and
25623 BandwidthBurst (how many bytes you will allow at once before the cap
25624 kicks in). This better token bucket approach lets you, say, set
25625 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
25626 performance while not exceeding your monthly bandwidth quota.
25627 - Push out a tls record's worth of data once you've got it, rather
25628 than waiting until you've read everything waiting to be read. This
25629 may improve performance by pipelining better. We'll see.
25630 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
25631 from failed circuits (if they haven't been connected yet) and attach
25633 - Expire old streams that haven't managed to connect. Some day we'll
25634 have them reattach to new circuits instead.
25637 - Fix several memory leaks that were causing servers to become bloated
25639 - Fix a few very rare assert triggers. A few more remain.
25640 - Setuid to User _before_ complaining about running as root.
25643 Changes in version 0.0.2pre19 - 2004-01-07
25645 - Fix deadlock condition in dns farm. We were telling a child to die by
25646 closing the parent's file descriptor to him. But newer children were
25647 inheriting the open file descriptor from the parent, and since they
25648 weren't closing it, the socket never closed, so the child never read
25649 eof, so he never knew to exit. Similarly, dns workers were holding
25650 open other sockets, leading to all sorts of chaos.
25651 - New cleaner daemon() code for forking and backgrounding.
25652 - If you log to a file, it now prints an entry at the top of the
25653 logfile so you know it's working.
25654 - The onionskin challenge length was 30 bytes longer than necessary.
25655 - Started to patch up the spec so it's not quite so out of date.
25658 Changes in version 0.0.2pre18 - 2004-01-02
25660 - Fix endian issues with the 'integrity' field in the relay header.
25661 - Fix a potential bug where connections in state
25662 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
25665 Changes in version 0.0.2pre17 - 2003-12-30
25667 - Made --debuglogfile (or any second log file, actually) work.
25668 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
25669 adversary could force us into an infinite loop.
25672 - Each onionskin handshake now includes a hash of the computed key,
25673 to prove the server's identity and help perfect forward secrecy.
25674 - Changed cell size from 256 to 512 bytes (working toward compatibility
25676 - Changed cell length to 2 bytes, and moved it to the relay header.
25677 - Implemented end-to-end integrity checking for the payloads of
25679 - Separated streamid from 'recognized' (otherwise circuits will get
25680 messed up when we try to have streams exit from the middle). We
25681 use the integrity-checking to confirm that a cell is addressed to
25683 - Randomize the initial circid and streamid values, so an adversary who
25684 breaks into a node can't learn how many circuits or streams have
25688 Changes in version 0.0.2pre16 - 2003-12-14
25690 - Fixed a bug that made HUP trigger an assert
25691 - Fixed a bug where a circuit that immediately failed wasn't being
25692 counted as a failed circuit in counting retries.
25695 - Now we close the circuit when we get a truncated cell: otherwise we're
25696 open to an anonymity attack where a bad node in the path truncates
25697 the circuit and then we open streams at him.
25698 - Add port ranges to exit policies
25699 - Add a conservative default exit policy
25700 - Warn if you're running tor as root
25701 - on HUP, retry OR connections and close/rebind listeners
25702 - options.EntryNodes: try these nodes first when picking the first node
25703 - options.ExitNodes: if your best choices happen to include any of
25704 your preferred exit nodes, you choose among just those preferred
25706 - options.ExcludedNodes: nodes that are never picked in path building
25709 Changes in version 0.0.2pre15 - 2003-12-03
25710 o Robustness and bugfixes:
25711 - Sometimes clients would cache incorrect DNS resolves, which would
25712 really screw things up.
25713 - An OP that goes offline would slowly leak all its sockets and stop
25715 - A wide variety of bugfixes in exit node selection, exit policy
25716 handling, and processing pending streams when a new circuit is
25718 - Pick nodes for a path only from those the directory says are up
25719 - Choose randomly from all running dirservers, not always the first one
25720 - Increase allowed http header size for directory fetch.
25721 - Stop writing to stderr (if we're daemonized it will be closed).
25722 - Enable -g always, so cores will be more useful to me.
25723 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
25726 - Wrote a man page. It lists commonly used options.
25729 - Change default loglevel to warn.
25730 - Make PidFile default to null rather than littering in your CWD.
25731 - OnionRouter config option is now obsolete. Instead it just checks
25733 - Moved to a single unified torrc file for both clients and servers.
25736 Changes in version 0.0.2pre14 - 2003-11-29
25737 o Robustness and bugfixes:
25738 - Force the admin to make the DataDirectory himself
25739 - to get ownership/permissions right
25740 - so clients no longer make a DataDirectory and then never use it
25741 - fix bug where a client who was offline for 45 minutes would never
25742 pull down a directory again
25743 - fix (or at least hide really well) the dns assert bug that was
25744 causing server crashes
25745 - warnings and improved robustness wrt clockskew for certs
25746 - use the native daemon(3) to daemonize, when available
25747 - exit if bind() fails
25748 - exit if neither socksport nor orport is defined
25749 - include our own tor_timegm (Win32 doesn't have its own)
25750 - bugfix for win32 with lots of connections
25751 - fix minor bias in PRNG
25752 - make dirserver more robust to corrupt cached directory
25755 - Wrote the design document (woo)
25757 o Circuit building and exit policies:
25758 - Circuits no longer try to use nodes that the directory has told them
25760 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
25761 bitcounts (18.0.0.0/8).
25762 - Make AP connections standby for a circuit if no suitable circuit
25763 exists, rather than failing
25764 - Circuits choose exit node based on addr/port, exit policies, and
25765 which AP connections are standing by
25766 - Bump min pathlen from 2 to 3
25767 - Relay end cells have a payload to describe why the stream ended.
25768 - If the stream failed because of exit policy, try again with a new
25770 - Clients have a dns cache to remember resolved addresses.
25771 - Notice more quickly when we have no working circuits
25774 - APPort is now called SocksPort
25775 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
25777 - RecommendedVersions is now a config variable rather than
25778 hardcoded (for dirservers)
25779 - Reloads config on HUP
25780 - Usage info on -h or --help
25781 - If you set User and Group config vars, it'll setu/gid to them.
25783 Changes in version 0.0.2pre13 - 2003-10-19
25784 o General stability:
25785 - SSL_write no longer fails when it returns WANTWRITE and the number
25786 of bytes in the buf has changed by the next SSL_write call.
25787 - Fix segfault fetching directory when network is down
25788 - Fix a variety of minor memory leaks
25789 - Dirservers reload the fingerprints file on HUP, so I don't have
25790 to take down the network when I approve a new router
25791 - Default server config file has explicit Address line to specify fqdn
25794 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
25795 - Make listener connections not ever alloc bufs
25797 o Autoconf improvements:
25798 - don't clobber an external CFLAGS in ./configure
25799 - Make install now works
25800 - create var/lib/tor on make install
25801 - autocreate a tor.sh initscript to help distribs
25802 - autocreate the torrc and sample-server-torrc with correct paths
25804 o Log files and Daemonizing now work:
25805 - If --DebugLogFile is specified, log to it at -l debug
25806 - If --LogFile is specified, use it instead of commandline
25807 - If --RunAsDaemon is set, tor forks and backgrounds on startup