1 Changes in version 0.4.4.3-alpha - 2020-07-27
2 Tor 0.4.4.3-alpha fixes several annoyances in previous versions,
3 including one affecting NSS users, and several affecting the Linux
6 o Major features (fallback directory list):
7 - Replace the 148 fallback directories originally included in Tor
8 0.4.1.4-rc (of which around 105 are still functional) with a list
9 of 144 fallbacks generated in July 2020. Closes ticket 40061.
11 o Major bugfixes (NSS):
12 - When running with NSS enabled, make sure that NSS knows to expect
13 nonblocking sockets. Previously, we set our TCP sockets as
14 nonblocking, but did not tell NSS, which in turn could lead to
15 unexpected blocking behavior. Fixes bug 40035; bugfix
18 o Minor bugfixes (linux seccomp2 sandbox):
19 - Fix a regression on sandboxing rules for the openat() syscall. The
20 fix for bug 25440 fixed the problem on systems with glibc >= 2.27
21 but broke with versions of glibc. We now choose a rule based on
22 the glibc version. Patch from Daniel Pinto. Fixes bug 27315;
24 - Makes the seccomp sandbox allow the correct syscall for opendir
25 according to the running glibc version. This fixes crashes when
26 reloading torrc with sandbox enabled when running on glibc 2.15 to
27 2.21 and 2.26. Patch from Daniel Pinto. Fixes bug 40020; bugfix
30 o Minor bugfixes (relay, usability):
31 - Adjust the rules for when to warn about having too many
32 connections to other relays. Previously we'd tolerate up to 1.5
33 connections per relay on average. Now we tolerate more connections
34 for directory authorities, and raise the number of total
35 connections we need to see before we warn. Fixes bug 33880; bugfix
39 - Replace most http:// URLs in our code and documentation with
40 https:// URLs. (We have left unchanged the code in src/ext/, and
41 the text in LICENSE.) Closes ticket 31812. Patch from Jeremy Rand.
44 - Our "check-local" test target no longer tries to use the
45 Coccinelle semantic patching tool parse all the C files. While it
46 is a good idea to try to make sure Coccinelle works on our C
47 before we run a Coccinelle patch, doing so on every test run has
48 proven to be disruptive. You can still run this tool manually with
49 "make check-cocci". Closes ticket 40030.
52 Changes in version 0.4.4.2-alpha - 2020-07-09
53 This is the second alpha release in the 0.4.4.x series. It fixes a few
54 bugs in the previous release, and solves a few usability,
55 compatibility, and portability issues.
57 This release also fixes TROVE-2020-001, a medium-severity denial of
58 service vulnerability affecting all versions of Tor when compiled with
59 the NSS encryption library. (This is not the default configuration.)
60 Using this vulnerability, an attacker could cause an affected Tor
61 instance to crash remotely. This issue is also tracked as CVE-2020-
62 15572. Anybody running a version of Tor built with the NSS library
63 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
66 o Major bugfixes (NSS, security):
67 - Fix a crash due to an out-of-bound memory access when Tor is
68 compiled with NSS support. Fixes bug 33119; bugfix on
69 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
72 o Minor features (bootstrap reporting):
73 - Report more detailed reasons for bootstrap failure when the
74 failure happens due to a TLS error. Previously we would just call
75 these errors "MISC" when they happened during read, and "DONE"
76 when they happened during any other TLS operation. Closes
79 o Minor features (directory authority):
80 - Authorities now recommend the protocol versions that are supported
81 by Tor 0.3.5 and later. (Earlier versions of Tor have been
82 deprecated since January of this year.) This recommendation will
83 cause older clients and relays to give a warning on startup, or
84 when they download a consensus directory. Closes ticket 32696.
86 o Minor features (entry guards):
87 - Reinstate support for GUARD NEW/UP/DOWN control port events.
90 o Minor features (linux seccomp2 sandbox, portability):
91 - Allow Tor to build on platforms where it doesn't know how to
92 report which syscall caused the linux seccomp2 sandbox to fail.
93 This change should make the sandbox code more portable to less
94 common Linux architectures. Closes ticket 34382.
95 - Permit the unlinkat() syscall, which some Libc implementations use
96 to implement unlink(). Closes ticket 33346.
98 o Minor bugfix (CI, Windows):
99 - Use the correct 64-bit printf format when compiling with MINGW on
100 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
102 o Minor bugfix (onion service v3 client):
103 - Remove a BUG() warning that could occur naturally. Fixes bug
104 34087; bugfix on 0.3.2.1-alpha.
106 o Minor bugfix (SOCKS, onion service client):
107 - Detect v3 onion service addresses of the wrong length when
108 returning the F6 ExtendedErrors code. Fixes bug 33873; bugfix
111 o Minor bugfixes (compiler warnings):
112 - Fix a compiler warning on platforms with 32-bit time_t values.
113 Fixes bug 40028; bugfix on 0.3.2.8-rc.
115 o Minor bugfixes (control port, onion service):
116 - Consistently use 'address' in "Invalid v3 address" response to
117 ONION_CLIENT_AUTH commands. Previously, we would sometimes say
118 'addr'. Fixes bug 40005; bugfix on 0.4.3.1-alpha.
120 o Minor bugfixes (logging):
121 - Downgrade a noisy log message that could occur naturally when
122 receiving an extrainfo document that we no longer want. Fixes bug
123 16016; bugfix on 0.2.6.3-alpha.
125 o Minor bugfixes (onion services v3):
126 - Avoid a non-fatal assertion failure in certain edge-cases when
127 opening an intro circuit as a client. Fixes bug 34084; bugfix
130 o Deprecated features (onion service v2):
131 - Add a deprecation warning for version 2 onion services. Closes
134 o Removed features (IPv6, revert):
135 - Revert the change in the default value of ClientPreferIPv6OrPort:
136 it breaks the torsocks use case. The SOCKS resolve command has no
137 mechanism to ask for a specific address family (v4 or v6), and so
138 prioritizing IPv6 when an IPv4 address is requested on the SOCKS
139 interface resulted in a failure. Tor Browser explicitly sets
140 PreferIPv6, so this should not affect the majority of our users.
141 Closes ticket 33796; bugfix on 0.4.4.1-alpha.
144 Changes in version 0.4.4.1-alpha - 2020-06-16
145 This is the first alpha release in the 0.4.4.x series. It improves
146 our guard selection algorithms, improves the amount of code that
147 can be disabled when running without relay support, and includes numerous
148 small bugfixes and enhancements. It also lays the ground for some IPv6
149 features that we'll be developing more in the next (0.4.5) series.
151 Here are the changes since 0.4.3.5.
153 o Major features (Proposal 310, performance + security):
154 - Implements Proposal 310, "Bandaid on guard selection". Proposal
155 310 solves load-balancing issues with older versions of the guard
156 selection algorithm, and improves its security. Under this new
157 algorithm, a newly selected guard never becomes Primary unless all
158 previously sampled guards are unreachable. Implements
159 recommendation from 32088. (Proposal 310 is linked to the CLAPS
160 project researching optimal client location-aware path selections.
161 This project is a collaboration between the UCLouvain Crypto Group,
162 the U.S. Naval Research Laboratory, and Princeton University.)
164 o Major features (IPv6, relay):
165 - Consider IPv6-only EXTEND2 cells valid on relays. Log a protocol
166 warning if the IPv4 or IPv6 address is an internal address, and
167 internal addresses are not allowed. But continue to use the other
168 address, if it is valid. Closes ticket 33817.
169 - If a relay can extend over IPv4 and IPv6, and both addresses are
170 provided, it chooses between them uniformly at random. Closes
172 - Re-use existing IPv6 connections for circuit extends. Closes
174 - Relays may extend circuits over IPv6, if the relay has an IPv6
175 ORPort, and the client supplies the other relay's IPv6 ORPort in
176 the EXTEND2 cell. IPv6 extends will be used by the relay IPv6
177 ORPort self-tests in 33222. Closes ticket 33817.
179 o Major features (v3 onion services):
180 - Allow v3 onion services to act as OnionBalance backend instances,
181 by using the HiddenServiceOnionBalanceInstance torrc option.
184 o Minor feature (developer tools):
185 - Add a script to help check the alphabetical ordering of option
186 names in the manual page. Closes ticket 33339.
188 o Minor feature (onion service client, SOCKS5):
189 - Add 3 new SocksPort ExtendedErrors (F2, F3, F7) that reports back
190 new type of onion service connection failures. The semantics of
191 these error codes are documented in proposal 309. Closes
194 o Minor feature (onion service v3):
195 - If a service cannot upload its descriptor(s), log why at INFO
196 level. Closes ticket 33400; bugfix on 0.3.2.1-alpha.
198 o Minor feature (python scripts):
199 - Stop assuming that /usr/bin/python exists. Instead of using a
200 hardcoded path in scripts that still use Python 2, use
201 /usr/bin/env, similarly to the scripts that use Python 3. Fixes
202 bug 33192; bugfix on 0.4.2.
204 o Minor features (client-only compilation):
205 - Disable more code related to the ext_orport protocol when
206 compiling without support for relay mode. Closes ticket 33368.
207 - Disable more of our self-testing code when support for relay mode
208 is disabled. Closes ticket 33370.
210 o Minor features (code safety):
211 - Check for failures of tor_inet_ntop() and tor_inet_ntoa()
212 functions in DNS and IP address processing code, and adjust
213 codepaths to make them less likely to crash entire Tor instances.
214 Resolves issue 33788.
216 o Minor features (compilation size):
217 - Most server-side DNS code is now disabled when building without
218 support for relay mode. Closes ticket 33366.
220 o Minor features (continuous integration):
221 - Run unit-test and integration test (Stem, Chutney) jobs with
222 ALL_BUGS_ARE_FATAL macro being enabled on Travis and Appveyor.
223 Resolves ticket 32143.
225 o Minor features (control port):
226 - Return a descriptive error message from the 'GETINFO status/fresh-
227 relay-descs' command on the control port. Previously, we returned
228 a generic error of "Error generating descriptor". Closes ticket
229 32873. Patch by Neel Chauhan.
231 o Minor features (developer tooling):
232 - Refrain from listing all .a files that are generated by the Tor
233 build in .gitignore. Add a single wildcard *.a entry that covers
234 all of them for present and future. Closes ticket 33642.
235 - Add a script ("git-install-tools.sh") to install git hooks and
236 helper scripts. Closes ticket 33451.
238 o Minor features (directory authority, shared random):
239 - Refactor more authority-only parts of the shared-random scheduling
240 code to reside in the dirauth module, and to be disabled when
241 compiling with --disable-module-dirauth. Closes ticket 33436.
243 o Minor features (directory):
244 - Remember the number of bytes we have downloaded for each directory
245 purpose while bootstrapping, and while fully bootstrapped. Log
246 this information as part of the heartbeat message. Closes
249 o Minor features (IPv6 support):
250 - Adds IPv6 support to tor_addr_is_valid(). Adds tests for the above
251 changes and tor_addr_is_null(). Closes ticket 33679. Patch
253 - Allow clients and relays to send dual-stack and IPv6-only EXTEND2
254 cells. Parse dual-stack and IPv6-only EXTEND2 cells on relays.
257 o Minor features (logging):
258 - When trying to find our own address, add debug-level logging to
259 report the sources of candidate addresses. Closes ticket 32888.
261 o Minor features (testing, architecture):
262 - Our test scripts now double-check that subsystem initialization
263 order is consistent with the inter-module dependencies established
264 by our .may_include files. Implements ticket 31634.
265 - Initialize all subsystems at the beginning of our unit test
266 harness, to avoid crashes due to uninitialized subsystems. Follow-
267 up from ticket 33316.
269 o Minor features (v3 onion services):
270 - Add v3 onion service status to the dumpstats() call which is
271 triggered by a SIGUSR1 signal. Previously, we only did v2 onion
272 services. Closes ticket 24844. Patch by Neel Chauhan.
274 o Minor features (windows):
275 - Add support for console control signals like Ctrl+C in Windows.
276 Closes ticket 34211. Patch from Damon Harris (TheDcoder).
278 o Minor bugfix (onion service v3):
279 - Prevent an assert() that would occur when cleaning the client
280 descriptor cache, and attempting to close circuits for a non-
281 decrypted descriptor (lacking client authorization). Fixes bug
282 33458; bugfix on 0.4.2.1-alpha.
284 o Minor bugfix (refactoring):
285 - Lift circuit_build_times_disabled() out of the
286 circuit_expire_building() loop, to save CPU time when there are
287 many circuits open. Fixes bug 33977; bugfix on 0.3.5.9.
289 o Minor bugfixes (client performance):
290 - Resume use of preemptively-built circuits when UseEntryGuards is set
291 to 0. We accidentally disabled this feature with that config
292 setting, leading to slower load times. Fixes bug 34303; bugfix
295 o Minor bugfixes (directory authorities):
296 - Directory authorities now reject votes that arrive too late. In
297 particular, once an authority has started fetching missing votes,
298 it no longer accepts new votes posted by other authorities. This
299 change helps prevent a consensus split, where only some authorities
300 have the late vote. Fixes bug 4631; bugfix on 0.2.0.5-alpha.
302 o Minor bugfixes (git scripts):
303 - Stop executing the checked-out pre-commit hook from the pre-push
304 hook. Instead, execute the copy in the user's git directory. Fixes
305 bug 33284; bugfix on 0.4.1.1-alpha.
307 o Minor bugfixes (initialization):
308 - Initialize the subsystems in our code in an order more closely
309 corresponding to their dependencies, so that every system is
310 initialized before the ones that (theoretically) depend on it.
311 Fixes bug 33316; bugfix on 0.4.0.1-alpha.
313 o Minor bugfixes (IPv4, relay):
314 - Check for invalid zero IPv4 addresses and ports when sending and
315 receiving extend cells. Fixes bug 33900; bugfix on 0.2.4.8-alpha.
317 o Minor bugfixes (IPv6, relay):
318 - Consider IPv6 addresses when checking if a connection is
319 canonical. In 17604, relays assumed that a remote relay could
320 consider an IPv6 connection canonical, but did not set the
321 canonical flag on their side of the connection. Fixes bug 33899;
322 bugfix on 0.3.1.1-alpha.
323 - Log IPv6 addresses on connections where this relay is the
324 responder. Previously, responding relays would replace the remote
325 IPv6 address with the IPv4 address from the consensus. Fixes bug
326 33899; bugfix on 0.3.1.1-alpha.
328 o Minor bugfixes (linux seccomp sandbox nss):
329 - Fix a startup crash when tor is compiled with --enable-nss and
330 sandbox support is enabled. Fixes bug 34130; bugfix on
331 0.3.5.1-alpha. Patch by Daniel Pinto.
333 o Minor bugfixes (logging, testing):
334 - Make all of tor's assertion macros support the ALL_BUGS_ARE_FATAL
335 and DISABLE_ASSERTS_IN_UNIT_TESTS debugging modes. (IF_BUG_ONCE()
336 used to log a non-fatal warning, regardless of the debugging
337 mode.) Fixes bug 33917; bugfix on 0.2.9.1-alpha.
339 o Minor bugfixes (logs):
340 - Remove surprising empty line in the INFO-level log about circuit
341 build timeout. Fixes bug 33531; bugfix on 0.3.3.1-alpha.
343 o Minor bugfixes (mainloop):
344 - Better guard against growing a buffer past its maximum 2GB in
345 size. Fixes bug 33131; bugfix on 0.3.0.4-rc.
347 o Minor bugfixes (manual page):
348 - Update the man page to reflect that MinUptimeHidServDirectoryV2
349 defaults to 96 hours. Fixes bug 34299; bugfix on 0.2.6.3-alpha.
351 o Minor bugfixes (onion service v3, client):
352 - Remove a BUG() that was causing a stacktrace when a descriptor
353 changed at an unexpected time. Fixes bug 28992; bugfix
356 o Minor bugfixes (onion service, logging):
357 - Fix a typo in a log message PublishHidServDescriptors is set to 0.
358 Fixes bug 33779; bugfix on 0.3.2.1-alpha.
360 o Minor bugfixes (portability):
361 - Fix a portability error in the configure script, where we were
362 using "==" instead of "=". Fixes bug 34233; bugfix on 0.4.3.5.
364 o Minor bugfixes (protocol versions):
365 - Sort tor's supported protocol version lists, as recommended by the
366 tor directory specification. Fixes bug 33285; bugfix
369 o Minor bugfixes (relays):
370 - Stop advertising incorrect IPv6 ORPorts in relay and bridge
371 descriptors, when the IPv6 port was configured as "auto". Fixes
372 bug 32588; bugfix on 0.2.3.9-alpha.
374 o Code simplification and refactoring:
375 - Define and use a new constant TOR_ADDRPORT_BUF_LEN which is like
376 TOR_ADDR_BUF_LEN but includes enough space for an IP address,
377 brackets, separating colon, and port number. Closes ticket 33956.
378 Patch by Neel Chauhan.
379 - Merge the orconn and ocirc events into the "core" subsystem, which
380 manages or connections and origin circuits. Previously they were
381 isolated in subsystems of their own.
382 - Move LOG_PROTOCOL_WARN to app/config. Resolves a dependency
383 inversion. Closes ticket 33633.
384 - Move the circuit extend code to the relay module. Split the
385 circuit extend function into smaller functions. Closes
387 - Rewrite port_parse_config() to use the default port flags from
388 port_cfg_new(). Closes ticket 32994. Patch by MrSquanchee.
389 - Updated comments in 'scheduler.c' to reflect old code changes, and
390 simplified the scheduler channel state change code. Closes
394 - Document the limitations of using %include on config files with
395 seccomp sandbox enabled. Fixes documentation bug 34133; bugfix on
396 0.3.1.1-alpha. Patch by Daniel Pinto.
397 - Fix several doxygen warnings related to imbalanced groups. Closes
401 - Remove the ClientAutoIPv6ORPort option. This option attempted to
402 randomly choose between IPv4 and IPv6 for client connections, and
403 wasn't a true implementation of Happy Eyeballs. Often, this option
404 failed on IPv4-only or IPv6-only connections. Closes ticket 32905.
405 Patch by Neel Chauhan.
406 - Stop shipping contrib/dist/rc.subr file, as it is not being used
407 on FreeBSD anymore. Closes issue 31576.
410 - Add a basic IPv6 test to "make test-network". This test only runs
411 when the local machine has an IPv6 stack. Closes ticket 33300.
412 - Add test-network-ipv4 and test-network-ipv6 jobs to the Makefile.
413 These jobs run the IPv4-only and dual-stack chutney flavours from
414 test-network-all. Closes ticket 33280.
415 - Remove a redundant distcheck job. Closes ticket 33194.
416 - Run the test-network-ipv6 Makefile target in the Travis CI IPv6
417 chutney job. This job runs on macOS, so it's a bit slow. Closes
419 - Sort the Travis jobs in order of speed. Putting the slowest jobs
420 first takes full advantage of Travis job concurrency. Closes
422 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
423 previously configured to fast_finish (which requires
424 allow_failure), to speed up the build. Closes ticket 33195.
425 - Test v3 onion services to tor's mixed IPv4 chutney network. And
426 add a mixed IPv6 chutney network. These networks are used in the
427 test-network-all, test-network-ipv4, and test-network-ipv6 make
428 targets. Closes ticket 33334.
429 - Use the "bridges+hs-v23" chutney network flavour in "make test-
430 network". This test requires a recent version of chutney (mid-
431 February 2020). Closes ticket 28208.
432 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
433 tool to produce detailed diagnostic output. Closes ticket 32792.
435 o Code simplification and refactoring (onion service):
436 - Refactor configuration parsing to use the new config subsystem
437 code. Closes ticket 33014.
439 o Code simplification and refactoring (relay address):
440 - Move a series of functions related to address resolving into their
441 own files. Closes ticket 33789.
443 o Documentation (manual page):
444 - Add cross reference links and a table of contents to the HTML tor
445 manual page. Closes ticket 33369. Work by Swati Thacker as part of
446 Google Season of Docs.
447 - Alphabetize the Denial of Service Mitigation Options, Directory
448 Authority Server Options, Hidden Service Options, and Testing
449 Network Options sections of the tor(1) manual page. Closes ticket
450 33275. Work by Swati Thacker as part of Google Season of Docs.
451 - Refrain from mentioning nicknames in manpage section for MyFamily
452 torrc option. Resolves issue 33417.
453 - Updated the options set by TestingTorNetwork in the manual page.
457 Changes in version 0.4.3.5 - 2020-05-15
458 Tor 0.4.3.5 is the first stable release in the 0.4.3.x series. This
459 series adds support for building without relay code enabled, and
460 implements functionality needed for OnionBalance with v3 onion
461 services. It includes significant refactoring of our configuration and
462 controller functionality, and fixes numerous smaller bugs and
465 Per our support policy, we support each stable release series for nine
466 months after its first stable release, or three months after the first
467 stable release of the next series: whichever is longer. This means
468 that 0.4.3.x will be supported until around February 2021--later, if
469 0.4.4.x is later than anticipated.
471 Note also that support for 0.4.1.x is about to end on May 20 of this
472 year; 0.4.2.x will be supported until September 15. We still plan to
473 continue supporting 0.3.5.x, our long-term stable series, until
476 Below are the changes since 0.4.3.4-rc. For a complete list of changes
477 since 0.4.2.6, see the ReleaseNotes file.
479 o Minor bugfixes (compiler compatibility):
480 - Avoid compiler warnings from Clang 10 related to the use of GCC-
481 style "/* falls through */" comments. Both Clang and GCC allow
482 __attribute__((fallthrough)) instead, so that's what we're using
483 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
484 - Fix compilation warnings with GCC 10.0.1. Fixes bug 34077; bugfix
487 o Minor bugfixes (logging):
488 - Stop truncating IPv6 addresses and ports in channel and connection
489 logs. Fixes bug 33918; bugfix on 0.2.4.4-alpha.
490 - Fix a logic error in a log message about whether an address was
491 invalid. Previously, the code would never report that onion
492 addresses were onion addresses. Fixes bug 34131; bugfix
496 Changes in version 0.4.3.4-rc - 2020-04-13
497 Tor 0.4.3.4-rc is the first release candidate in its series. It fixes
498 several bugs from earlier versions, including one affecting DoS
499 defenses on bridges using pluggable transports.
501 o Major bugfixes (DoS defenses, bridges, pluggable transport):
502 - Fix a bug that was preventing DoS defenses from running on bridges
503 with a pluggable transport. Previously, the DoS subsystem was not
504 given the transport name of the client connection, thus failed to
505 find the GeoIP cache entry for that client address. Fixes bug
506 33491; bugfix on 0.3.3.2-alpha.
508 o Minor feature (sendme, flow control):
509 - Default to sending SENDME version 1 cells. (Clients are already
510 sending these, because of a consensus parameter telling them to do
511 so: this change only affects what clients would do if the
512 consensus didn't contain a recommendation.) Closes ticket 33623.
514 o Minor features (testing):
515 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
516 variable to specify a list of space-separated test cases that
517 should not be executed. We will use this to disable certain tests
518 that are failing on Appveyor because of mismatched OpenSSL
519 libraries. Part of ticket 33643.
521 o Minor bugfixes (--disable-module-relay):
522 - Fix an assertion failure when Tor is built without the relay
523 module, and then invoked with the "User" option. Fixes bug 33668;
524 bugfix on 0.4.3.1-alpha.
526 o Minor bugfixes (--disable-module-relay,--disable-module-dirauth):
527 - Set some output arguments in the relay and dirauth module stubs,
528 to guard against future stub argument handling bugs like 33668.
529 Fixes bug 33674; bugfix on 0.4.3.1-alpha.
531 o Minor bugfixes (build system):
532 - Correctly output the enabled module in the configure summary.
533 Before that, the list shown was just plain wrong. Fixes bug 33646;
534 bugfix on 0.4.3.2-alpha.
536 o Minor bugfixes (client, IPv6):
537 - Stop forcing all non-SocksPorts to prefer IPv6 exit connections.
538 Instead, prefer IPv6 connections by default, but allow users to
539 change their configs using the "NoPreferIPv6" port flag. Fixes bug
540 33608; bugfix on 0.4.3.1-alpha.
541 - Revert PreferIPv6 set by default on the SocksPort because it broke
542 the torsocks use case. Tor doesn't have a way for an application
543 to request the hostname to be resolved for a specific IP version,
544 but torsocks requires that. Up until now, IPv4 was used by default
545 so torsocks is expecting that, and can't handle a possible IPv6
546 being returned. Fixes bug 33804; bugfix on 0.4.3.1-alpha.
548 o Minor bugfixes (key portability):
549 - When reading PEM-encoded key data, tolerate CRLF line-endings even
550 if we are not running on Windows. Previously, non-Windows hosts
551 would reject these line-endings in certain positions, making
552 certain key files hard to move from one host to another. Fixes bug
553 33032; bugfix on 0.3.5.1-alpha.
555 o Minor bugfixes (logging):
556 - Flush stderr, stdout, and file logs during shutdown, if supported
557 by the OS. This change helps make sure that any final logs are
558 recorded. Fixes bug 33087; bugfix on 0.4.1.6.
559 - Stop closing stderr and stdout during shutdown. Closing these file
560 descriptors can hide sanitiser logs. Fixes bug 33087; bugfix
563 o Minor bugfixes (onion services v3):
564 - Relax severity of a log message that can appear naturally when
565 decoding onion service descriptors as a relay. Also add some
566 diagnostics to debug any future bugs in that area. Fixes bug
567 31669; bugfix on 0.3.0.1-alpha.
568 - Block a client-side assertion by disallowing the registration of
569 an x25519 client auth key that's all zeroes. Fixes bug 33545;
570 bugfix on 0.4.3.1-alpha. Based on patch from "cypherpunks".
572 o Code simplification and refactoring:
573 - Disable our coding standards best practices tracker in our git
574 hooks. (0.4.3 branches only.) Closes ticket 33678.
577 - Avoid conflicts between the fake sockets in tor's unit tests, and
578 real file descriptors. Resolves issues running unit tests with
579 GitHub Actions, where the process that embeds or launches the
580 tests has already opened a large number of file descriptors. Fixes
581 bug 33782; bugfix on 0.2.8.1-alpha. Found and fixed by
585 - In our Appveyor Windows CI, copy required DLLs to test and app
586 directories, before running tor's tests. This ensures that tor.exe
587 and test*.exe use the correct version of each DLL. This fix is not
588 required, but we hope it will avoid DLL search issues in future.
589 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
590 - On Appveyor, skip the crypto/openssl_version test, which is
591 failing because of a mismatched library installation. Fix
595 Changes in version 0.4.3.3-alpha - 2020-03-18
596 Tor 0.4.3.3-alpha fixes several bugs in previous releases, including
597 TROVE-2020-002, a major denial-of-service vulnerability that affected
598 all released Tor instances since 0.2.1.5-alpha. Using this
599 vulnerability, an attacker could cause Tor instances to consume a huge
600 amount of CPU, disrupting their operations for several seconds or
601 minutes. This attack could be launched by anybody against a relay, or
602 by a directory cache against any client that had connected to it. The
603 attacker could launch this attack as much as they wanted, thereby
604 disrupting service or creating patterns that could aid in traffic
605 analysis. This issue was found by OSS-Fuzz, and is also tracked
608 We do not have reason to believe that this attack is currently being
609 exploited in the wild, but nonetheless we advise everyone to upgrade
610 as soon as packages are available.
612 o Major bugfixes (security, denial-of-service):
613 - Fix a denial-of-service bug that could be used by anyone to
614 consume a bunch of CPU on any Tor relay or authority, or by
615 directories to consume a bunch of CPU on clients or hidden
616 services. Because of the potential for CPU consumption to
617 introduce observable timing patterns, we are treating this as a
618 high-severity security issue. Fixes bug 33119; bugfix on
619 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
620 as TROVE-2020-002 and CVE-2020-10592.
622 o Major bugfixes (circuit padding, memory leak):
623 - Avoid a remotely triggered memory leak in the case that a circuit
624 padding machine is somehow negotiated twice on the same circuit.
625 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
626 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
628 o Major bugfixes (directory authority):
629 - Directory authorities will now send a 503 (not enough bandwidth)
630 code to clients when under bandwidth pressure. Known relays and
631 other authorities will always be answered regardless of the
632 bandwidth situation. Fixes bug 33029; bugfix on 0.1.2.5-alpha.
634 o Minor features (diagnostic):
635 - Improve assertions and add some memory-poisoning code to try to
636 track down possible causes of a rare crash (32564) in the EWMA
637 code. Closes ticket 33290.
639 o Minor features (directory authorities):
640 - Directory authorities now reject descriptors from relays running
641 Tor versions from the 0.2.9 and 0.4.0 series. The 0.3.5 series is
642 still allowed. Resolves ticket 32672. Patch by Neel Chauhan.
644 o Minor features (usability):
645 - Include more information when failing to parse a configuration
646 value. This should make it easier to tell what's going wrong when
647 a configuration file doesn't parse. Closes ticket 33460.
649 o Minor bugfix (relay, configuration):
650 - Warn if the ContactInfo field is not set, and tell the relay
651 operator that not having a ContactInfo field set might cause their
652 relay to get rejected in the future. Fixes bug 33361; bugfix
655 o Minor bugfixes (coding best practices checks):
656 - Allow the "practracker" script to read unicode files when using
657 Python 2. We made the script use unicode literals in 0.4.3.1-alpha,
658 but didn't change the codec for opening files. Fixes bug 33374;
659 bugfix on 0.4.3.1-alpha.
661 o Minor bugfixes (continuous integration):
662 - Remove the buggy and unused mirroring job. Fixes bug 33213; bugfix
665 o Minor bugfixes (onion service v3, client):
666 - Remove a BUG() warning that would cause a stack trace if an onion
667 service descriptor was freed while we were waiting for a
668 rendezvous circuit to complete. Fixes bug 28992; bugfix
671 o Minor bugfixes (onion services v3):
672 - Fix an assertion failure that could result from a corrupted
673 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
674 bugfix on 0.3.3.1-alpha. This issue is also tracked
677 o Documentation (manpage):
678 - Alphabetize the Server and Directory server sections of the tor
679 manpage. Also split Statistics options into their own section of
680 the manpage. Closes ticket 33188. Work by Swati Thacker as part of
681 Google Season of Docs.
682 - Document the __OwningControllerProcess torrc option and specify
683 its polling interval. Resolves issue 32971.
685 o Testing (Travis CI):
686 - Remove a redundant distcheck job. Closes ticket 33194.
687 - Sort the Travis jobs in order of speed: putting the slowest jobs
688 first takes full advantage of Travis job concurrency. Closes
690 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
691 previously configured to fast_finish (which requires
692 allow_failure), to speed up the build. Closes ticket 33195.
693 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
694 tool to produce detailed diagnostic output. Closes ticket 32792.
697 Changes in version 0.4.2.7 - 2020-03-18
698 This is the third stable release in the 0.4.2.x series. It backports
699 numerous fixes from later releases, including a fix for TROVE-2020-
700 002, a major denial-of-service vulnerability that affected all
701 released Tor instances since 0.2.1.5-alpha. Using this vulnerability,
702 an attacker could cause Tor instances to consume a huge amount of CPU,
703 disrupting their operations for several seconds or minutes. This
704 attack could be launched by anybody against a relay, or by a directory
705 cache against any client that had connected to it. The attacker could
706 launch this attack as much as they wanted, thereby disrupting service
707 or creating patterns that could aid in traffic analysis. This issue
708 was found by OSS-Fuzz, and is also tracked as CVE-2020-10592.
710 We do not have reason to believe that this attack is currently being
711 exploited in the wild, but nonetheless we advise everyone to upgrade
712 as soon as packages are available.
714 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
715 - Fix a denial-of-service bug that could be used by anyone to
716 consume a bunch of CPU on any Tor relay or authority, or by
717 directories to consume a bunch of CPU on clients or hidden
718 services. Because of the potential for CPU consumption to
719 introduce observable timing patterns, we are treating this as a
720 high-severity security issue. Fixes bug 33119; bugfix on
721 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
722 as TROVE-2020-002 and CVE-2020-10592.
724 o Major bugfixes (circuit padding, memory leak, backport from 0.4.3.3-alpha):
725 - Avoid a remotely triggered memory leak in the case that a circuit
726 padding machine is somehow negotiated twice on the same circuit.
727 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
728 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
730 o Major bugfixes (directory authority, backport from 0.4.3.3-alpha):
731 - Directory authorities will now send a 503 (not enough bandwidth)
732 code to clients when under bandwidth pressure. Known relays and
733 other authorities will always be answered regardless of the
734 bandwidth situation. Fixes bug 33029; bugfix on 0.1.2.5-alpha.
736 o Minor features (continuous integration, backport from 0.4.3.2-alpha):
737 - Stop allowing failures on the Travis CI stem tests job. It looks
738 like all the stem hangs we were seeing before are now fixed.
741 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
742 - Lowercase the configured value of BridgeDistribution before adding
743 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
745 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
746 - If we encounter a bug when flushing a buffer to a TLS connection,
747 only log the bug once per invocation of the Tor process.
748 Previously we would log with every occurrence, which could cause
749 us to run out of disk space. Fixes bug 33093; bugfix
752 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
753 - Fix an assertion failure that could result from a corrupted
754 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
755 bugfix on 0.3.3.1-alpha. This issue is also tracked
758 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
759 - Fix a syntax warning given by newer versions of Rust that was
760 creating problems for our continuous integration. Fixes bug 33212;
761 bugfix on 0.3.5.1-alpha.
763 o Testing (Travis CI, backport from 0.4.3.3-alpha):
764 - Remove a redundant distcheck job. Closes ticket 33194.
765 - Sort the Travis jobs in order of speed: putting the slowest jobs
766 first takes full advantage of Travis job concurrency. Closes
768 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
769 previously configured to fast_finish (which requires
770 allow_failure), to speed up the build. Closes ticket 33195.
771 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
772 tool to produce detailed diagnostic output. Closes ticket 32792.
775 Changes in version 0.4.1.9 - 2020-03-18
776 Tor 0.4.1.9 backports important fixes from later Tor releases,
777 including a fix for TROVE-2020-002, a major denial-of-service
778 vulnerability that affected all released Tor instances since
779 0.2.1.5-alpha. Using this vulnerability, an attacker could cause Tor
780 instances to consume a huge amount of CPU, disrupting their operations
781 for several seconds or minutes. This attack could be launched by
782 anybody against a relay, or by a directory cache against any client
783 that had connected to it. The attacker could launch this attack as
784 much as they wanted, thereby disrupting service or creating patterns
785 that could aid in traffic analysis. This issue was found by OSS-Fuzz,
786 and is also tracked as CVE-2020-10592.
788 We do not have reason to believe that this attack is currently being
789 exploited in the wild, but nonetheless we advise everyone to upgrade
790 as soon as packages are available.
792 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
793 - Fix a denial-of-service bug that could be used by anyone to
794 consume a bunch of CPU on any Tor relay or authority, or by
795 directories to consume a bunch of CPU on clients or hidden
796 services. Because of the potential for CPU consumption to
797 introduce observable timing patterns, we are treating this as a
798 high-severity security issue. Fixes bug 33119; bugfix on
799 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
800 as TROVE-2020-002 and CVE-2020-10592.
802 o Major bugfixes (circuit padding, memory leak, backport from 0.4.3.3-alpha):
803 - Avoid a remotely triggered memory leak in the case that a circuit
804 padding machine is somehow negotiated twice on the same circuit.
805 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
806 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
808 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
809 - Lowercase the configured value of BridgeDistribution before adding
810 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
812 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
813 - If we encounter a bug when flushing a buffer to a TLS connection,
814 only log the bug once per invocation of the Tor process.
815 Previously we would log with every occurrence, which could cause
816 us to run out of disk space. Fixes bug 33093; bugfix
819 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
820 - Fix an assertion failure that could result from a corrupted
821 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
822 bugfix on 0.3.3.1-alpha. This issue is also tracked
825 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
826 - Fix a syntax warning given by newer versions of Rust that was
827 creating problems for our continuous integration. Fixes bug 33212;
828 bugfix on 0.3.5.1-alpha.
830 o Testing (Travis CI, backport from 0.4.3.3-alpha):
831 - Remove a redundant distcheck job. Closes ticket 33194.
832 - Sort the Travis jobs in order of speed: putting the slowest jobs
833 first takes full advantage of Travis job concurrency. Closes
835 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
836 previously configured to fast_finish (which requires
837 allow_failure), to speed up the build. Closes ticket 33195.
838 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
839 tool to produce detailed diagnostic output. Closes ticket 32792.
842 Changes in version 0.3.5.10 - 2020-03-18
843 Tor 0.3.5.10 backports many fixes from later Tor releases, including a
844 fix for TROVE-2020-002, a major denial-of-service vulnerability that
845 affected all released Tor instances since 0.2.1.5-alpha. Using this
846 vulnerability, an attacker could cause Tor instances to consume a huge
847 amount of CPU, disrupting their operations for several seconds or
848 minutes. This attack could be launched by anybody against a relay, or
849 by a directory cache against any client that had connected to it. The
850 attacker could launch this attack as much as they wanted, thereby
851 disrupting service or creating patterns that could aid in traffic
852 analysis. This issue was found by OSS-Fuzz, and is also tracked
855 We do not have reason to believe that this attack is currently being
856 exploited in the wild, but nonetheless we advise everyone to upgrade
857 as soon as packages are available.
859 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
860 - Fix a denial-of-service bug that could be used by anyone to
861 consume a bunch of CPU on any Tor relay or authority, or by
862 directories to consume a bunch of CPU on clients or hidden
863 services. Because of the potential for CPU consumption to
864 introduce observable timing patterns, we are treating this as a
865 high-severity security issue. Fixes bug 33119; bugfix on
866 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
867 as TROVE-2020-002 and CVE-2020-10592.
869 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
870 - Correct how we use libseccomp. Particularly, stop assuming that
871 rules are applied in a particular order or that more rules are
872 processed after the first match. Neither is the case! In
873 libseccomp <2.4.0 this lead to some rules having no effect.
874 libseccomp 2.4.0 changed how rules are generated, leading to a
875 different ordering, which in turn led to a fatal crash during
876 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
879 o Minor features (continuous integration, backport from 0.4.3.2-alpha):
880 - Stop allowing failures on the Travis CI stem tests job. It looks
881 like all the stem hangs we were seeing before are now fixed.
884 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
885 - Lowercase the configured value of BridgeDistribution before adding
886 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
888 o Minor bugfixes (crash, backport from 0.4.2.4-rc):
889 - When running Tor with an option like --verify-config or
890 --dump-config that does not start the event loop, avoid crashing
891 if we try to exit early because of an error. Fixes bug 32407;
892 bugfix on 0.3.3.1-alpha.
894 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
895 - If we encounter a bug when flushing a buffer to a TLS connection,
896 only log the bug once per invocation of the Tor process.
897 Previously we would log with every occurrence, which could cause
898 us to run out of disk space. Fixes bug 33093; bugfix
901 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
902 - Fix an assertion failure that could result from a corrupted
903 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
904 bugfix on 0.3.3.1-alpha. This issue is also tracked
907 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
908 - Fix a syntax warning given by newer versions of Rust that was
909 creating problems for our continuous integration. Fixes bug 33212;
910 bugfix on 0.3.5.1-alpha.
912 o Testing (backport from 0.4.3.1-alpha):
913 - Re-enable the Travis CI macOS Chutney build, but don't let it
914 prevent the Travis job from finishing. (The Travis macOS jobs are
915 slow, so we don't want to have it delay the whole CI process.)
917 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
918 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
919 fix the sandbox errors in 32722. Closes ticket 32240.
921 o Testing (continuous integration, backport from 0.4.3.1-alpha):
922 - Use zstd in our Travis Linux builds. Closes ticket 32242.
924 o Testing (Travis CI, backport from 0.4.3.3-alpha):
925 - Remove a redundant distcheck job. Closes ticket 33194.
926 - Sort the Travis jobs in order of speed: putting the slowest jobs
927 first takes full advantage of Travis job concurrency. Closes
929 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
930 previously configured to fast_finish (which requires
931 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
932 tool to produce detailed diagnostic output. Closes ticket 32792.
935 Changes in version 0.4.3.2-alpha - 2020-02-10
936 This is the second stable alpha release in the Tor 0.4.3.x series. It
937 fixes several bugs present in the previous alpha release. Anybody
938 running the previous alpha should upgrade, and look for bugs in this
941 o Major bugfixes (onion service client, authorization):
942 - On a NEWNYM signal, purge entries from the ephemeral client
943 authorization cache. The permanent ones are kept. Fixes bug 33139;
944 bugfix on 0.4.3.1-alpha.
946 o Minor features (best practices tracker):
947 - Practracker now supports a --regen-overbroad option to regenerate
948 the exceptions file, but only to revise exceptions to be _less_
949 tolerant of best-practices violations. Closes ticket 32372.
951 o Minor features (continuous integration):
952 - Run Doxygen Makefile target on Travis, so we can learn about
953 regressions in our internal documentation. Closes ticket 32455.
954 - Stop allowing failures on the Travis CI stem tests job. It looks
955 like all the stem hangs we were seeing before are now fixed.
958 o Minor bugfixes (build system):
959 - Revise configure options that were either missing or incorrect in
960 the configure summary. Fixes bug 32230; bugfix on 0.4.3.1-alpha.
962 o Minor bugfixes (controller protocol):
963 - Fix a memory leak introduced by refactoring of control reply
964 formatting code. Fixes bug 33039; bugfix on 0.4.3.1-alpha.
965 - Fix a memory leak in GETINFO responses. Fixes bug 33103; bugfix
967 - When receiving "ACTIVE" or "DORMANT" signals on the control port,
968 report them as SIGNAL events. Previously we would log a bug
969 warning. Fixes bug 33104; bugfix on 0.4.0.1-alpha.
971 o Minor bugfixes (logging):
972 - If we encounter a bug when flushing a buffer to a TLS connection,
973 only log the bug once per invocation of the Tor process.
974 Previously we would log with every occurrence, which could cause
975 us to run out of disk space. Fixes bug 33093; bugfix
977 - When logging a bug, do not say "Future instances of this warning
978 will be silenced" unless we are actually going to silence them.
979 Previously we would say this whenever a BUG() check failed in the
980 code. Fixes bug 33095; bugfix on 0.4.1.1-alpha.
982 o Minor bugfixes (onion service v2):
983 - Move a series of v2 onion service warnings to protocol-warning
984 level because they can all be triggered remotely by a malformed
985 request. Fixes bug 32706; bugfix on 0.1.1.14-alpha.
987 o Minor bugfixes (onion service v3, client authorization):
988 - When removing client authorization credentials using the control
989 port, also remove the associated descriptor, so the onion service
990 can no longer be contacted. Fixes bug 33148; bugfix
993 o Minor bugfixes (pluggable transports):
994 - When receiving a message on standard error from a pluggable
995 transport, log it at info level, rather than as a warning. Fixes
996 bug 33005; bugfix on 0.4.0.1-alpha.
998 o Minor bugfixes (rust, build):
999 - Fix a syntax warning given by newer versions of Rust that was
1000 creating problems for our continuous integration. Fixes bug 33212;
1001 bugfix on 0.3.5.1-alpha.
1003 o Minor bugfixes (TLS bug handling):
1004 - When encountering a bug in buf_read_from_tls(), return a "MISC"
1005 error code rather than "WANTWRITE". This change might help avoid
1006 some CPU-wasting loops if the bug is ever triggered. Bug reported
1007 by opara. Fixes bug 32673; bugfix on 0.3.0.4-alpha.
1009 o Code simplification and refactoring (mainloop):
1010 - Simplify the ip_address_changed() function by removing redundant
1011 checks. Closes ticket 33091.
1013 o Documentation (manpage):
1014 - Split "Circuit Timeout" options and "Node Selection" options into
1015 their own sections of the tor manpage. Closes tickets 32928 and
1016 32929. Work by Swati Thacker as part of Google Season of Docs.
1019 Changes in version 0.4.2.6 - 2020-01-30
1020 This is the second stable release in the 0.4.2.x series. It backports
1021 several bugfixes from 0.4.3.1-alpha, including some that had affected
1022 the Linux seccomp2 sandbox or Windows services. If you're running with
1023 one of those configurations, you'll probably want to upgrade;
1024 otherwise, you should be fine with 0.4.2.5.
1026 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
1027 - Correct how we use libseccomp. Particularly, stop assuming that
1028 rules are applied in a particular order or that more rules are
1029 processed after the first match. Neither is the case! In
1030 libseccomp <2.4.0 this led to some rules having no effect.
1031 libseccomp 2.4.0 changed how rules are generated, leading to a
1032 different ordering, which in turn led to a fatal crash during
1033 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
1035 - Fix crash when reloading logging configuration while the
1036 experimental sandbox is enabled. Fixes bug 32841; bugfix on
1037 0.4.1.7. Patch by Peter Gerber.
1039 o Minor bugfixes (correctness checks, backport from 0.4.3.1-alpha):
1040 - Use GCC/Clang's printf-checking feature to make sure that
1041 tor_assertf() arguments are correctly typed. Fixes bug 32765;
1042 bugfix on 0.4.1.1-alpha.
1044 o Minor bugfixes (logging, crash, backport from 0.4.3.1-alpha):
1045 - Avoid a possible crash when trying to log a (fatal) assertion
1046 failure about mismatched magic numbers in configuration objects.
1047 Fixes bug 32771; bugfix on 0.4.2.1-alpha.
1049 o Minor bugfixes (testing, backport from 0.4.3.1-alpha):
1050 - When TOR_DISABLE_PRACTRACKER is set, do not apply it to the
1051 test_practracker.sh script. Doing so caused a test failure. Fixes
1052 bug 32705; bugfix on 0.4.2.1-alpha.
1053 - When TOR_DISABLE_PRACTRACKER is set, log a notice to stderr when
1054 skipping practracker checks. Fixes bug 32705; bugfix
1057 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
1058 - Initialize the publish/subscribe system when running as a windows
1059 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
1061 o Testing (backport from 0.4.3.1-alpha):
1062 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
1063 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
1064 fix the sandbox errors in 32722. Closes ticket 32240.
1065 - Re-enable the Travis CI macOS Chutney build, but don't let it
1066 prevent the Travis job from finishing. (The Travis macOS jobs are
1067 slow, so we don't want to have it delay the whole CI process.)
1068 Closes ticket 32629.
1070 o Testing (continuous integration, backport from 0.4.3.1-alpha):
1071 - Use zstd in our Travis Linux builds. Closes ticket 32242.
1074 Changes in version 0.4.1.8 - 2020-01-30
1075 This release backports several bugfixes from later release series,
1076 including some that had affected the Linux seccomp2 sandbox or Windows
1077 services. If you're running with one of those configurations, you'll
1078 probably want to upgrade; otherwise, you should be fine with your
1079 current version of 0.4.1.x.
1081 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
1082 - Correct how we use libseccomp. Particularly, stop assuming that
1083 rules are applied in a particular order or that more rules are
1084 processed after the first match. Neither is the case! In
1085 libseccomp <2.4.0 this led to some rules having no effect.
1086 libseccomp 2.4.0 changed how rules are generated, leading to a
1087 different ordering, which in turn led to a fatal crash during
1088 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
1090 - Fix crash when reloading logging configuration while the
1091 experimental sandbox is enabled. Fixes bug 32841; bugfix on
1092 0.4.1.7. Patch by Peter Gerber.
1094 o Minor bugfixes (crash, backport form 0.4.2.4-rc):
1095 - When running Tor with an option like --verify-config or
1096 --dump-config that does not start the event loop, avoid crashing
1097 if we try to exit early because of an error. Fixes bug 32407;
1098 bugfix on 0.3.3.1-alpha.
1100 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
1101 - Initialize the publish/subscribe system when running as a windows
1102 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
1104 o Testing (backport from 0.4.3.1-alpha):
1105 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
1106 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
1107 fix the sandbox errors in 32722. Closes ticket 32240.
1108 - Re-enable the Travis CI macOS Chutney build, but don't let it
1109 prevent the Travis job from finishing. (The Travis macOS jobs are
1110 slow, so we don't want to have it delay the whole CI process.)
1111 Closes ticket 32629.
1113 o Testing (continuous integration, backport from 0.4.3.1-alpha):
1114 - Use zstd in our Travis Linux builds. Closes ticket 32242.
1117 Changes in version 0.4.3.1-alpha - 2020-01-22
1118 This is the first alpha release in the 0.4.3.x series. It includes
1119 improved support for application integration of onion services, support
1120 for building in a client-only mode, and newly improved internal
1121 documentation (online at https://src-ref.docs.torproject.org/tor/). It
1122 also has numerous other small bugfixes and features, as well as
1123 improvements to our code's internal organization that should help us
1124 write better code in the future.
1126 o New system requirements:
1127 - When building Tor, you now need to have Python 3 in order to run
1128 the integration tests. (Python 2 is officially unsupported
1129 upstream, as of 1 Jan 2020.) Closes ticket 32608.
1131 o Major features (build system):
1132 - The relay code can now be disabled using the --disable-module-relay
1133 configure option. When this option is set, we also disable the
1134 dirauth module. Closes ticket 32123.
1135 - When Tor is compiled --disable-module-relay, we also omit the code
1136 used to act as a directory cache. Closes ticket 32487.
1138 o Major features (directory authority, ed25519):
1139 - Add support for banning a relay's ed25519 keys in the approved-
1140 routers file. This will help us migrate away from RSA keys in the
1141 future. Previously, only RSA keys could be banned in approved-
1142 routers. Resolves ticket 22029. Patch by Neel Chauhan.
1144 o Major features (onion service, controller):
1145 - New control port commands to manage client-side onion service
1146 authorization credentials. The ONION_CLIENT_AUTH_ADD command adds
1147 a credential, ONION_CLIENT_AUTH_REMOVE deletes a credential, and
1148 ONION_CLIENT_AUTH_VIEW lists the credentials. Closes ticket 30381.
1150 o Major features (onion service, SOCKS5):
1151 - Introduce a new SocksPort flag, ExtendedErrors, to support more
1152 detailed error codes in information for applications that support
1153 them. Closes ticket 30382; implements proposal 304.
1155 o Major features (proxy):
1156 - In addition to its current supported proxy types (HTTP CONNECT,
1157 SOCKS4, and SOCKS5), Tor can now make its OR connections through a
1158 HAProxy server. A new torrc option was added to specify the
1159 address/port of the server: TCPProxy <protocol> <host>:<port>.
1160 Currently the only supported protocol for the option is haproxy.
1161 Closes ticket 31518. Patch done by Suphanat Chunhapanya (haxxpop).
1163 o Major bugfixes (linux seccomp sandbox):
1164 - Correct how we use libseccomp. Particularly, stop assuming that
1165 rules are applied in a particular order or that more rules are
1166 processed after the first match. Neither is the case! In
1167 libseccomp <2.4.0 this led to some rules having no effect.
1168 libseccomp 2.4.0 changed how rules are generated, leading to a
1169 different ordering, which in turn led to a fatal crash during
1170 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
1172 - Fix crash when reloading logging configuration while the
1173 experimental sandbox is enabled. Fixes bug 32841; bugfix on
1174 0.4.1.7. Patch by Peter Gerber.
1176 o Major bugfixes (networking):
1177 - Correctly handle IPv6 addresses in SOCKS5 RESOLVE_PTR requests,
1178 and accept strings as well as binary addresses. Fixes bug 32315;
1179 bugfix on 0.3.5.1-alpha.
1181 o Major bugfixes (onion service):
1182 - Report HS circuit failure back into the HS subsystem so we take
1183 appropriate action with regards to the client introduction point
1184 failure cache. This improves reachability of onion services, since
1185 now clients notice failing introduction circuits properly. Fixes
1186 bug 32020; bugfix on 0.3.2.1-alpha.
1188 o Minor feature (configure, build system):
1189 - Output a list of enabled/disabled features at the end of the
1190 configure process in a pleasing way. Closes ticket 31373.
1192 o Minor feature (heartbeat, onion service):
1193 - Add the DoS INTRODUCE2 defenses counter to the heartbeat DoS
1194 message. Closes ticket 31371.
1196 o Minor features (configuration validation):
1197 - Configuration validation can now be done by per-module callbacks,
1198 rather than a global validation function. This will let us reduce
1199 the size of config.c and some of its more cumbersome functions.
1200 Closes ticket 31241.
1202 o Minor features (configuration):
1203 - If a configured hardware crypto accelerator in AccelName is
1204 prefixed with "!", Tor now exits when it cannot be found. Closes
1206 - We now use flag-driven logic to warn about obsolete configuration
1207 fields, so that we can include their names. In 0.4.2, we used a
1208 special type, which prevented us from generating good warnings.
1209 Implements ticket 32404.
1211 o Minor features (controller):
1212 - Add stream isolation data to STREAM event. Closes ticket 19859.
1213 - Implement a new GETINFO command to fetch microdescriptor
1214 consensus. Closes ticket 31684.
1216 o Minor features (debugging, directory system):
1217 - Don't crash when we find a non-guard with a guard-fraction value
1218 set. Instead, log a bug warning, in an attempt to figure out how
1219 this happened. Diagnostic for ticket 32868.
1221 o Minor features (defense in depth):
1222 - Add additional checks around tor_vasprintf() usage, in case the
1223 function returns an error. Patch by Tobias Stoeckmann. Fixes
1226 o Minor features (developer tooling):
1227 - Remove the 0.2.9.x series branches from git scripts (git-merge-
1228 forward.sh, git-pull-all.sh, git-push-all.sh, git-setup-dirs.sh).
1229 Closes ticket 32772.
1231 o Minor features (developer tools):
1232 - Add a check_cocci_parse.sh script that checks that new code is
1233 parseable by Coccinelle. Add an exceptions file for unparseable
1234 files, and run the script from travis CI. Closes ticket 31919.
1235 - Call the check_cocci_parse.sh script from a 'check-cocci' Makefile
1236 target. Closes ticket 31919.
1237 - Add a rename_c_identifiers.py tool to rename a bunch of C
1238 identifiers at once, and generate a well-formed commit message
1239 describing the change. This should help with refactoring. Closes
1241 - Add some scripts in "scripts/coccinelle" to invoke the Coccinelle
1242 semantic patching tool with the correct flags. These flags are
1243 fairly easy to forget, and these scripts should help us use
1244 Coccinelle more effectively in the future. Closes ticket 31705.
1246 o Minor features (Doxygen):
1247 - Update Doxygen configuration file to a more recent template (from
1248 1.8.15). Closes ticket 32110.
1249 - "make doxygen" now works with out-of-tree builds. Closes
1251 - Make sure that doxygen outputs documentation for all of our C
1252 files. Previously, some were missing @file declarations, causing
1253 them to be ignored. Closes ticket 32307.
1254 - Our "make doxygen" target now respects --enable-fatal-warnings by
1255 default, and does not warn about items that are missing
1256 documentation. To warn about missing documentation, run configure
1257 with the "--enable-missing-doc-warnings" flag: doing so suspends
1258 fatal warnings for doxygen. Closes ticket 32385.
1260 o Minor features (git scripts):
1261 - Add TOR_EXTRA_CLONE_ARGS to git-setup-dirs.sh for git clone
1262 customisation. Closes ticket 32347.
1263 - Add git-setup-dirs.sh, which sets up an upstream git repository
1264 and worktrees for tor maintainers. Closes ticket 29603.
1265 - Add TOR_EXTRA_REMOTE_* to git-setup-dirs.sh for a custom extra
1266 remote. Closes ticket 32347.
1267 - Call the check_cocci_parse.sh script from the git commit and push
1268 hooks. Closes ticket 31919.
1269 - Make git-push-all.sh skip unchanged branches when pushing to
1270 upstream. The script already skipped unchanged test branches.
1271 Closes ticket 32216.
1272 - Make git-setup-dirs.sh create a master symlink in the worktree
1273 directory. Closes ticket 32347.
1274 - Skip unmodified source files when doing some existing git hook
1275 checks. Related to ticket 31919.
1277 o Minor features (IPv6, client):
1278 - Make Tor clients tell dual-stack exits that they prefer IPv6
1279 connections. This change is equivalent to setting the PreferIPv6
1280 flag on SOCKSPorts (and most other listener ports). Tor Browser
1281 has been setting this flag for some time, and we want to remove a
1282 client distinguisher at exits. Closes ticket 32637.
1284 o Minor features (portability, android):
1285 - When building for Android, disable some tests that depend on $HOME
1286 and/or pwdb, which Android doesn't have. Closes ticket 32825.
1287 Patch from Hans-Christoph Steiner.
1289 o Minor features (relay modularity):
1290 - Split the relay and server pluggable transport config code into
1291 separate files in the relay module. Disable this code when the
1292 relay module is disabled. Closes part of ticket 32213.
1293 - When the relay module is disabled, reject attempts to set the
1294 ORPort, DirPort, DirCache, BridgeRelay, ExtORPort, or
1295 ServerTransport* options, rather than ignoring the values of these
1296 options. Closes part of ticket 32213.
1298 o Minor features (relay):
1299 - When the relay module is disabled, change the default config so
1300 that DirCache is 0, and ClientOnly is 1. Closes ticket 32410.
1302 o Minor features (release tools):
1303 - Port our ChangeLog formatting and sorting tools to Python 3.
1304 Closes ticket 32704.
1306 o Minor features (testing):
1307 - Detect some common failure cases for test_parseconf.sh in
1308 src/test/conf_failures. Closes ticket 32451.
1309 - Allow test_parseconf.sh to test expected log outputs for successful
1310 configs, as well as failed configs. Closes ticket 32451.
1311 - The test_parseconf.sh script now supports result variants for any
1312 combination of the optional libraries lzma, nss, and zstd. Closes
1315 o Minor features (tests, Android):
1316 - When running the unit tests on Android, create temporary files in
1317 a subdirectory of /data/local/tmp. Closes ticket 32172. Based on a
1318 patch from Hans-Christoph Steiner.
1320 o Minor bugfixes (bridges):
1321 - Lowercase the configured value of BridgeDistribution before adding
1322 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
1324 o Minor bugfixes (build system):
1325 - Fix "make autostyle" for out-of-tree builds. Fixes bug 32370;
1326 bugfix on 0.4.1.2-alpha.
1328 o Minor bugfixes (configuration handling):
1329 - Make control_event_conf_changed() take in a config_line_t instead
1330 of a smartlist of alternating key/value entries. Fixes bug 31531;
1331 bugfix on 0.2.3.3-alpha. Patch by Neel Chauhan.
1333 o Minor bugfixes (configuration):
1334 - Check for multiplication overflow when parsing memory units inside
1335 configuration. Fixes bug 30920; bugfix on 0.0.9rc1.
1336 - When dumping the configuration, stop adding a trailing space after
1337 the option name when there is no option value. This issue only
1338 affects options that accept an empty value or list. (Most options
1339 reject empty values, or delete the entire line from the dumped
1340 options.) Fixes bug 32352; bugfix on 0.0.9pre6.
1341 - Avoid changing the user's value of HardwareAccel as stored by
1342 SAVECONF, when AccelName is set but HardwareAccel is not. Fixes
1343 bug 32382; bugfix on 0.2.2.1-alpha.
1344 - When creating a KeyDirectory with the same location as the
1345 DataDirectory (not recommended), respect the DataDirectory's
1346 group-readable setting if one has not been set for the
1347 KeyDirectory. Fixes bug 27992; bugfix on 0.3.3.1-alpha.
1349 o Minor bugfixes (controller):
1350 - In routerstatus_has_changed(), check all the fields that are
1351 output over the control port. Fixes bug 20218; bugfix
1354 o Minor bugfixes (correctness checks):
1355 - Use GCC/Clang's printf-checking feature to make sure that
1356 tor_assertf() arguments are correctly typed. Fixes bug 32765;
1357 bugfix on 0.4.1.1-alpha.
1359 o Minor bugfixes (developer tools):
1360 - Allow paths starting with ./ in scripts/add_c_file.py. Fixes bug
1361 31336; bugfix on 0.4.1.2-alpha.
1363 o Minor bugfixes (dirauth module):
1364 - Split the dirauth config code into a separate file in the dirauth
1365 module. Disable this code when the dirauth module is disabled.
1366 Closes ticket 32213.
1367 - When the dirauth module is disabled, reject attempts to set the
1368 AuthoritativeDir option, rather than ignoring the value of the
1369 option. Fixes bug 32213; bugfix on 0.3.4.1-alpha.
1371 o Minor bugfixes (embedded Tor):
1372 - When starting Tor any time after the first time in a process,
1373 register the thread in which it is running as the main thread.
1374 Previously, we only did this on Windows, which could lead to bugs
1375 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
1378 o Minor bugfixes (git scripts):
1379 - Avoid sleeping before the last push in git-push-all.sh. Closes
1381 - Forward all unrecognised arguments in git-push-all.sh to git push.
1382 Closes ticket 32216.
1384 o Minor bugfixes (hidden service v3):
1385 - Do not rely on a "circuit established" flag for intro circuits but
1386 instead always query the HS circuit map. This is to avoid sync
1387 issue with that flag and the map. Fixes bug 32094; bugfix
1390 o Minor bugfixes (logging, crash):
1391 - Avoid a possible crash when trying to log a (fatal) assertion
1392 failure about mismatched magic numbers in configuration objects.
1393 Fixes bug 32771; bugfix on 0.4.2.1-alpha.
1395 o Minor bugfixes (onion service v2):
1396 - When sending the INTRO cell for a v2 Onion Service, look at the
1397 failure cache alongside timeout values to check if the intro point
1398 is marked as failed. Previously, we only looked at the relay
1399 timeout values. Fixes bug 25568; bugfix on 0.2.7.3-rc. Patch by
1402 o Minor bugfixes (onion services v3, client):
1403 - Properly handle the client rendezvous circuit timeout. Previously
1404 Tor would sometimes timeout a rendezvous circuit awaiting the
1405 introduction ACK, and find itself unable to re-establish all
1406 circuits because the rendezvous circuit timed out too early. Fixes
1407 bug 32021; bugfix on 0.3.2.1-alpha.
1409 o Minor bugfixes (onion services):
1410 - In cancel_descriptor_fetches(), use
1411 connection_list_by_type_purpose() instead of
1412 connection_list_by_type_state(). Fixes bug 32639; bugfix on
1413 0.3.2.1-alpha. Patch by Neel Chauhan.
1415 o Minor bugfixes (scripts):
1416 - Fix update_versions.py for out-of-tree builds. Fixes bug 32371;
1417 bugfix on 0.4.0.1-alpha.
1419 o Minor bugfixes (test):
1420 - Use the same code to find the tor binary in all of our test
1421 scripts. This change makes sure we are always using the coverage
1422 binary when coverage is enabled. Fixes bug 32368; bugfix
1425 o Minor bugfixes (testing):
1426 - Stop ignoring "tor --dump-config" errors in test_parseconf.sh.
1427 Fixes bug 32468; bugfix on 0.4.2.1-alpha.
1428 - When TOR_DISABLE_PRACTRACKER is set, do not apply it to the
1429 test_practracker.sh script. Doing so caused a test failure. Fixes
1430 bug 32705; bugfix on 0.4.2.1-alpha.
1431 - When TOR_DISABLE_PRACTRACKER is set, log a notice to stderr when
1432 skipping practracker checks. Fixes bug 32705; bugfix
1435 o Minor bugfixes (tests):
1436 - Our option-validation tests no longer depend on specially
1437 configured non-default, non-passing sets of options. Previously,
1438 the tests had been written to assume that options would _not_ be
1439 set to their defaults, which led to needless complexity and
1440 verbosity. Fixes bug 32175; bugfix on 0.2.8.1-alpha.
1442 o Minor bugfixes (windows service):
1443 - Initialize the publish/subscribe system when running as a windows
1444 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
1446 o Deprecated features:
1447 - Deprecate the ClientAutoIPv6ORPort option. This option was not
1448 true "Happy Eyeballs", and often failed on connections that
1449 weren't reliably dual-stack. Closes ticket 32942. Patch by
1453 - Provide a quickstart guide for a Circuit Padding Framework, and
1454 documentation for researchers to implement and study circuit
1455 padding machines. Closes ticket 28804.
1456 - Add documentation in 'HelpfulTools.md' to describe how to build a
1457 tag file. Closes ticket 32779.
1458 - Create a high-level description of the long-term software
1459 architecture goals. Closes ticket 32206.
1460 - Describe the --dump-config command in the manual page. Closes
1462 - Unite coding advice from this_not_that.md in torguts repo into our
1463 coding standards document. Resolves ticket 31853.
1466 - Our Doxygen configuration no longer generates LaTeX output. The
1467 reference manual produced by doing this was over 4000 pages long,
1468 and generally unusable. Closes ticket 32099.
1469 - The option "TestingEstimatedDescriptorPropagationTime" is now
1470 marked as obsolete. It has had no effect since 0.3.0.7, when
1471 clients stopped rejecting consensuses "from the future". Closes
1473 - We no longer support consensus methods before method 28; these
1474 methods were only used by authorities running versions of Tor that
1475 are now at end-of-life. In effect, this means that clients,
1476 relays, and authorities now assume that authorities will be
1477 running version 0.3.5.x or later. Closes ticket 32695.
1480 - Add more test cases for tor's UTF-8 validation function. Also,
1481 check the arguments passed to the function for consistency. Closes
1483 - Improve test coverage for relay and dirauth config code, focusing
1484 on option validation and normalization. Closes ticket 32213.
1485 - Improve the consistency of test_parseconf.sh output, and run all
1486 the tests, even if one fails. Closes ticket 32213.
1487 - Re-enable the Travis CI macOS Chutney build, but don't let it
1488 prevent the Travis job from finishing. (The Travis macOS jobs are
1489 slow, so we don't want to have it delay the whole CI process.)
1490 Closes ticket 32629.
1491 - Run the practracker unit tests in the pre-commit git hook. Closes
1493 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
1494 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
1495 fix the sandbox errors in 32722. Closes ticket 32240.
1497 o Code simplification and refactoring (channel):
1498 - Channel layer had a variable length cell handler that was not used
1499 and thus removed. Closes ticket 32892.
1501 o Code simplification and refactoring (configuration):
1502 - Immutability is now implemented as a flag on individual
1503 configuration options rather than as part of the option-transition
1504 checking code. Closes ticket 32344.
1505 - Instead of keeping a list of configuration options to check for
1506 relative paths, check all the options whose type is "FILENAME".
1507 Solves part of ticket 32339.
1508 - Our default log (which ordinarily sends NOTICE-level messages to
1509 standard output) is now handled in a more logical manner.
1510 Previously, we replaced the configured log options if they were
1511 empty. Now, we interpret an empty set of log options as meaning
1512 "use the default log". Closes ticket 31999.
1513 - Remove some unused arguments from the options_validate() function,
1514 to simplify our code and tests. Closes ticket 32187.
1515 - Simplify the options_validate() code so that it looks at the
1516 default options directly, rather than taking default options as an
1517 argument. This change lets us simplify its interface. Closes
1519 - Use our new configuration architecture to move most authority-
1520 related options to the directory authority module. Closes
1522 - When parsing the command line, handle options that determine our
1523 "quiet level" and our mode of operation (e.g., --dump-config and
1524 so on) all in one table. Closes ticket 32003.
1526 o Code simplification and refactoring (controller):
1527 - Create a new abstraction for formatting control protocol reply
1528 lines based on key-value pairs. Refactor some existing control
1529 protocol code to take advantage of this. Closes ticket 30984.
1530 - Create a helper function that can fetch network status or
1531 microdesc consensuses. Closes ticket 31684.
1533 o Code simplification and refactoring (dirauth modularization):
1534 - Remove the last remaining HAVE_MODULE_DIRAUTH inside a function.
1535 Closes ticket 32163.
1536 - Replace some confusing identifiers in process_descs.c. Closes
1538 - Simplify some relay and dirauth config code. Closes ticket 32213.
1540 o Code simplification and refactoring (misc):
1541 - Make all the structs we declare follow the same naming convention
1542 of ending with "_t". Closes ticket 32415.
1543 - Move and rename some configuration-related code for clarity.
1544 Closes ticket 32304.
1545 - Our include.am files are now broken up by subdirectory.
1546 Previously, src/core/include.am covered all of the subdirectories
1547 in "core", "feature", and "app". Closes ticket 32137.
1548 - Remove underused NS*() macros from test code: they make our tests
1549 more confusing, especially for code-formatting tools. Closes
1552 o Code simplification and refactoring (relay modularization):
1553 - Disable relay_periodic when the relay module is disabled. Closes
1555 - Disable relay_sys when the relay module is disabled. Closes
1558 o Code simplification and refactoring (tool support):
1559 - Add numerous missing dependencies to our include files, so that
1560 they can be included in different reasonable orders and still
1561 compile. Addresses part of ticket 32764.
1562 - Fix some parts of our code that were difficult for Coccinelle to
1563 parse. Related to ticket 31705.
1564 - Fix some small issues in our code that prevented automatic
1565 formatting tools from working. Addresses part of ticket 32764.
1567 o Documentation (manpage):
1568 - Alphabetize the Client Options section of the tor manpage. Closes
1570 - Alphabetize the General Options section of the tor manpage. Closes
1572 - In the tor(1) manpage, reword and improve formatting of the
1573 COMMAND-LINE OPTIONS and DESCRIPTION sections. Closes ticket
1574 32277. Based on work by Swati Thacker as part of Google Season
1576 - In the tor(1) manpage, reword and improve formatting of the FILES,
1577 SEE ALSO, and BUGS sections. Closes ticket 32176. Based on work by
1578 Swati Thacker as part of Google Season of Docs.
1580 o Testing (circuit, EWMA):
1581 - Add unit tests for circuitmux and EWMA subsystems. Closes
1584 o Testing (continuous integration):
1585 - Use zstd in our Travis Linux builds. Closes ticket 32242.
1588 Changes in version 0.4.2.5 - 2019-12-09
1589 This is the first stable release in the 0.4.2.x series. This series
1590 improves reliability and stability, and includes several stability and
1591 correctness improvements for onion services. It also fixes many smaller
1592 bugs present in previous series.
1594 Per our support policy, we will support the 0.4.2.x series for nine
1595 months, or until three months after the release of a stable 0.4.3.x:
1596 whichever is longer. If you need longer-term support, please stick
1597 with 0.3.5.x, which will we plan to support until Feb 2022.
1599 Per our support policy, we will support the 0.4.2.x series for nine
1600 months, or until three months after the release of a stable 0.4.3.x:
1601 whichever is longer. If you need longer-term support, please stick
1602 with 0.3.5.x, which will we plan to support until Feb 2022.
1604 Below are the changes since 0.4.1.4-rc. For a complete list of changes
1605 since 0.4.1.5, see the ReleaseNotes file.
1607 o Minor features (geoip):
1608 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
1609 Country database. Closes ticket 32685.
1612 - Require C99 standards-conforming code in Travis CI, but allow GNU
1613 gcc extensions. Also activates clang's -Wtypedef-redefinition
1614 warnings. Build some jobs with -std=gnu99, and some jobs without.
1615 Closes ticket 32500.
1618 Changes in version 0.4.1.7 - 2019-12-09
1619 This release backports several bugfixes to improve stability and
1620 correctness. Anyone experiencing build problems or crashes with 0.4.1.6,
1621 including all relays relying on AccountingMax, should upgrade.
1623 o Major features (directory authorities, backport from 0.4.2.2-alpha):
1624 - Directory authorities now reject relays running all currently
1625 deprecated release series. The currently supported release series
1626 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
1628 o Major bugfixes (embedded Tor, backport from 0.4.2.2-alpha):
1629 - Avoid a possible crash when restarting Tor in embedded mode and
1630 enabling a different set of publish/subscribe messages. Fixes bug
1631 31898; bugfix on 0.4.1.1-alpha.
1633 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
1634 - Relays now respect their AccountingMax bandwidth again. When
1635 relays entered "soft" hibernation (which typically starts when
1636 we've hit 90% of our AccountingMax), we had stopped checking
1637 whether we should enter hard hibernation. Soft hibernation refuses
1638 new connections and new circuits, but the existing circuits can
1639 continue, meaning that relays could have exceeded their configured
1640 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
1642 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
1643 - Stop ignoring torrc options after an %include directive, when the
1644 included directory ends with a file that does not contain any
1645 config options (but does contain comments or whitespace). Fixes
1646 bug 31408; bugfix on 0.3.1.1-alpha.
1648 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
1649 - Onion services now always use the exact number of intro points
1650 configured with the HiddenServiceNumIntroductionPoints option (or
1651 fewer if nodes are excluded). Before, a service could sometimes
1652 pick more intro points than configured. Fixes bug 31548; bugfix
1655 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
1656 - When building on Appveyor and Travis, pass the "-k" flag to make,
1657 so that we are informed of all compilation failures, not just the
1658 first one or two. Closes ticket 31372.
1660 o Minor features (geoip, backport from 0.4.2.5):
1661 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
1662 Country database. Closes ticket 32685.
1664 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
1665 - Avoid spurious errors when Appveyor CI fails before the install step.
1666 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
1668 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
1669 - Fix a BUG() assertion that occurs within a very small race window
1670 between when a client intro circuit opens and when its descriptor
1671 gets cleaned up from the cache. The circuit is now closed early,
1672 which will trigger a re-fetch of the descriptor and continue the
1673 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
1675 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
1676 - Avoid trying to read data from closed connections, which can cause
1677 needless loops in Libevent and infinite loops in Shadow. Fixes bug
1678 30344; bugfix on 0.1.1.1-alpha.
1680 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
1681 - On abort, try harder to flush the output buffers of log messages.
1682 On some platforms (macOS), log messages could be discarded when
1683 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1684 - Report the tor version whenever an assertion fails. Previously, we
1685 only reported the Tor version on some crashes, and some non-fatal
1686 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1687 - When tor aborts due to an error, close log file descriptors before
1688 aborting. Closing the logs makes some OSes flush log file buffers,
1689 rather than deleting buffered log lines. Fixes bug 31594; bugfix
1692 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
1693 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
1694 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
1695 - Disable backtrace signal handlers when shutting down tor. Fixes
1696 bug 31614; bugfix on 0.2.5.2-alpha.
1697 - Rate-limit our the logging message about the obsolete .exit
1698 notation. Previously, there was no limit on this warning, which
1699 could potentially be triggered many times by a hostile website.
1700 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
1702 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
1703 - Do not log a nonfatal assertion failure when receiving a VERSIONS
1704 cell on a connection using the obsolete v1 link protocol. Log a
1705 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
1707 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
1708 - Reset the periodic events' "enabled" flag when Tor is shut down
1709 cleanly. Previously, this flag was left on, which caused periodic
1710 events not to be re-enabled when Tor was relaunched in-process
1711 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
1714 o Minor bugfixes (multithreading, backport from 0.4.2.2-alpha):
1715 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
1716 31736; bugfix on 0.0.7.
1718 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
1719 - Remove overly strict assertions that triggered when a pluggable
1720 transport failed to launch. Fixes bug 31091; bugfix
1722 - Remove an assertion in the Unix process backend. This assertion
1723 would trigger when we failed to find the executable for a child
1724 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
1726 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
1727 - Avoid crashing when starting with a corrupt keys directory where
1728 the old ntor key and the new ntor key are identical. Fixes bug
1729 30916; bugfix on 0.2.4.8-alpha.
1731 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
1732 - When testing port rebinding, don't busy-wait for tor to log.
1733 Instead, actually sleep for a short time before polling again.
1734 Also improve the formatting of control commands and log messages.
1735 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
1737 o Minor bugfixes (tests, SunOS, backport from 0.4.2.2-alpha):
1738 - Avoid a map_anon_nofork test failure due to a signed/unsigned
1739 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
1741 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
1742 - Log bugs about the TLS read buffer's length only once, rather than
1743 filling the logs with similar warnings. Fixes bug 31939; bugfix
1746 o Documentation (backport from 0.4.2.2-alpha):
1747 - Explain why we can't destroy the backtrace buffer mutex. Explain
1748 why we don't need to destroy the log mutex. Closes ticket 31736.
1750 o Testing (continuous integration, backport from 0.4.2.3-alpha):
1751 - Disable all but one Travis CI macOS build, to mitigate slow
1752 scheduling of Travis macOS jobs. Closes ticket 32177.
1753 - Run the chutney IPv6 networks as part of Travis CI. Closes
1755 - Simplify the Travis CI build matrix, and optimise for build time.
1756 Closes ticket 31859.
1757 - Use Windows Server 2019 instead of Windows Server 2016 in our
1758 Appveyor builds. Closes ticket 32086.
1760 o Testing (continuous integration, backport from 0.4.2.4-rc):
1761 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
1762 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
1763 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
1764 until we can fix some Bionic permissions issues (see ticket
1765 32240). Related to ticket 31919.
1766 - Install the mingw OpenSSL package in Appveyor. This makes sure
1767 that the OpenSSL headers and libraries match in Tor's Appveyor
1768 builds. (This bug was triggered by an Appveyor image update.)
1769 Fixes bug 32449; bugfix on 0.3.5.6-rc.
1771 o Testing (continuous integration, backport from 0.4.2.5):
1772 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
1773 extensions. Also activates clang's -Wtypedef-redefinition warnings.
1774 Build some jobs with -std=gnu99, and some jobs without.
1775 Closes ticket 32500.
1778 Changes in version 0.4.0.6 - 2019-12-09
1779 This is the second stable release in the 0.4.0.x series. This release
1780 backports several bugfixes to improve stability and correctness. Anyone
1781 experiencing build problems or crashes with 0.4.0.5, including all relays
1782 relying on AccountingMax, should upgrade.
1784 Note that, per our support policy, support for the 0.4.0.x series will end
1785 on 2 Feb 2020. Anyone still running 0.4.0.x should plan to upgrade to the
1786 latest stable release, or downgrade to 0.3.5.x, which will get long-term
1787 support until 1 Feb 2022.
1789 o Directory authority changes (backport from 0.4.1.5):
1790 - The directory authority "dizum" has a new IP address. Closes
1793 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
1794 - Consider our directory information to have changed when our list
1795 of bridges changes. Previously, Tor would not re-compute the
1796 status of its directory information when bridges changed, and
1797 therefore would not realize that it was no longer able to build
1798 circuits. Fixes part of bug 29875.
1799 - Do not count previously configured working bridges towards our
1800 total of working bridges. Previously, when Tor's list of bridges
1801 changed, it would think that the old bridges were still usable,
1802 and delay fetching router descriptors for the new ones. Fixes part
1803 of bug 29875; bugfix on 0.3.0.1-alpha.
1805 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
1806 - When considering upgrading circuits from "waiting for guard" to
1807 "open", always ignore circuits that are marked for close. Otherwise,
1808 we can end up in the situation where a subsystem is notified that
1809 a closing circuit has just opened, leading to undesirable
1810 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
1812 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
1813 - Properly clean up the introduction point map when circuits change
1814 purpose from onion service circuits to pathbias, measurement, or
1815 other circuit types. This should fix some service-side instances
1816 of introduction point failure. Fixes bug 29034; bugfix
1819 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
1820 - Fix an unreachable bug in which an introduction point could try to
1821 send an INTRODUCE_ACK with a status code that Trunnel would refuse
1822 to encode, leading the relay to assert(). We've consolidated the
1823 ABI values into Trunnel now. Fixes bug 30454; bugfix
1825 - Clients can now handle unknown status codes from INTRODUCE_ACK
1826 cells. (The NACK behavior will stay the same.) This will allow us
1827 to extend status codes in the future without breaking the normal
1828 client behavior. Fixes another part of bug 30454; bugfix
1831 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
1832 - Relays now respect their AccountingMax bandwidth again. When
1833 relays entered "soft" hibernation (which typically starts when
1834 we've hit 90% of our AccountingMax), we had stopped checking
1835 whether we should enter hard hibernation. Soft hibernation refuses
1836 new connections and new circuits, but the existing circuits can
1837 continue, meaning that relays could have exceeded their configured
1838 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
1840 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
1841 - Stop ignoring torrc options after an %include directive, when the
1842 included directory ends with a file that does not contain any
1843 config options (but does contain comments or whitespace). Fixes
1844 bug 31408; bugfix on 0.3.1.1-alpha.
1846 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
1847 - Onion services now always use the exact number of intro points
1848 configured with the HiddenServiceNumIntroductionPoints option (or
1849 fewer if nodes are excluded). Before, a service could sometimes
1850 pick more intro points than configured. Fixes bug 31548; bugfix
1853 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
1854 - Add a "--list-modules" command to print a list of which compile-
1855 time modules are enabled. Closes ticket 30452.
1857 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
1858 - Remove sudo configuration lines from .travis.yml as they are no
1859 longer needed with current Travis build environment. Resolves
1862 o Minor features (continuous integration, backport from 0.4.1.4-rc):
1863 - Our Travis configuration now uses Chutney to run some network
1864 integration tests automatically. Closes ticket 29280.
1866 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
1867 - When building on Appveyor and Travis, pass the "-k" flag to make,
1868 so that we are informed of all compilation failures, not just the
1869 first one or two. Closes ticket 31372.
1871 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
1872 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
1873 in December 2018 (of which ~122 were still functional), with a
1874 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
1875 in June 2019. Closes ticket 28795.
1877 o Minor features (geoip, backport from 0.4.2.5):
1878 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
1879 Country database. Closes ticket 32685.
1881 o Minor features (stem tests, backport from 0.4.2.1-alpha):
1882 - Change "make test-stem" so it only runs the stem tests that use
1883 tor. This change makes test-stem faster and more reliable. Closes
1886 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
1887 - Avoid spurious errors when Appveyor CI fails before the install step.
1888 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
1890 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
1891 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
1892 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
1894 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
1895 - Fix a logic error that prevented the SessionGroup sub-option from
1896 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
1898 o Minor bugfixes (circuit padding, backport from 0.4.1.4-rc):
1899 - On relays, properly check that a padding machine is absent before
1900 logging a warning about it being absent. Fixes bug 30649; bugfix
1903 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
1904 - Fix a BUG() assertion that occurs within a very small race window
1905 between when a client intro circuit opens and when its descriptor
1906 gets cleaned up from the cache. The circuit is now closed early,
1907 which will trigger a re-fetch of the descriptor and continue the
1908 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
1910 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
1911 - Don't believe clock skew results from NETINFO cells that appear to
1912 arrive before we sent the VERSIONS cells they are responding to.
1913 Previously, we would accept them up to 3 minutes "in the past".
1914 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
1916 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
1917 - Fix a compilation warning on Windows about casting a function
1918 pointer for GetTickCount64(). Fixes bug 31374; bugfix
1921 o Minor bugfixes (compilation, backport from 0.4.1.5):
1922 - Avoid using labs() on time_t, which can cause compilation warnings
1923 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
1925 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
1926 - Suppress spurious float-conversion warnings from GCC when calling
1927 floating-point classifier functions on FreeBSD. Fixes part of bug
1928 31687; bugfix on 0.3.1.5-alpha.
1930 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
1931 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
1932 due to missing declarations of abort(), and prevent other such
1933 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
1935 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
1936 - Fix a bug that prevented us from supporting SOCKS5 proxies that
1937 want authentication along with configured (but unused!)
1938 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
1940 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
1941 - Avoid trying to read data from closed connections, which can cause
1942 needless loops in Libevent and infinite loops in Shadow. Fixes bug
1943 30344; bugfix on 0.1.1.1-alpha.
1945 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
1946 - Allow the test-stem job to fail in Travis, because it sometimes
1947 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
1948 - Skip test_rebind on macOS in Travis, because it is unreliable on
1949 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
1950 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
1951 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
1953 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
1954 - Avoid a set of possible code paths that could try to use freed
1955 memory in routerlist_free() while Tor was exiting. Fixes bug
1956 31003; bugfix on 0.1.2.2-alpha.
1958 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
1959 - Stop crashing after parsing an unknown descriptor purpose
1960 annotation. We think this bug can only be triggered by modifying a
1961 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
1963 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
1964 - Move the "bandwidth-file-headers" line in directory authority
1965 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
1968 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
1969 - On abort, try harder to flush the output buffers of log messages.
1970 On some platforms (macOS), log messages could be discarded when
1971 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1972 - Report the tor version whenever an assertion fails. Previously, we
1973 only reported the Tor version on some crashes, and some non-fatal
1974 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1976 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
1977 - When extracting an IPv6 address from a PF-based proxy, verify that
1978 we are actually configured to receive an IPv6 address, and log an
1979 internal error if not. Fixes part of bug 31687; bugfix
1982 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
1983 - When tor is missing descriptors for some primary entry guards,
1984 make the log message less alarming. It's normal for descriptors to
1985 expire, as long as tor fetches new ones soon after. Fixes bug
1986 31657; bugfix on 0.3.3.1-alpha.
1988 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
1989 - Do not log a warning when running with an OpenSSL version other
1990 than the one Tor was compiled with, if the two versions should be
1991 compatible. Previously, we would warn whenever the version was
1992 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
1994 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
1995 - Change log level of message "Hash of session info was not as
1996 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
1999 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
2000 - Rate-limit our the logging message about the obsolete .exit
2001 notation. Previously, there was no limit on this warning, which
2002 could potentially be triggered many times by a hostile website.
2003 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
2005 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
2006 - Do not log a nonfatal assertion failure when receiving a VERSIONS
2007 cell on a connection using the obsolete v1 link protocol. Log a
2008 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
2010 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
2011 - Reset the periodic events' "enabled" flag when Tor is shut down
2012 cleanly. Previously, this flag was left on, which caused periodic
2013 events not to be re-enabled when Tor was relaunched in-process
2014 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
2017 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
2018 - Avoid a minor memory leak that could occur on relays when failing
2019 to create a "keys" directory. Fixes bug 30148; bugfix
2022 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
2023 - Fix a trivial memory leak when parsing an invalid value
2024 from a download schedule in the configuration. Fixes bug
2025 30894; bugfix on 0.3.4.1-alpha.
2027 o Minor bugfixes (NetBSD, backport from 0.4.1.2-alpha):
2028 - Fix usage of minherit() on NetBSD and other platforms that define
2029 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
2030 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
2032 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
2033 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
2034 implemenation) when failing to load an onion service client
2035 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
2037 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
2038 - When purging the DNS cache because of an out-of-memory condition,
2039 try purging just the older entries at first. Previously, we would
2040 always purge the whole thing. Fixes bug 29617; bugfix
2043 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
2044 - Avoid crashing in our tor_vasprintf() implementation on systems
2045 that define neither vasprintf() nor _vscprintf(). (This bug has
2046 been here long enough that we question whether people are running
2047 Tor on such systems, but we're applying the fix out of caution.)
2048 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
2051 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
2052 - Remove overly strict assertions that triggered when a pluggable
2053 transport failed to launch. Fixes bug 31091; bugfix
2055 - Remove an assertion in the Unix process backend. This assertion
2056 would trigger when we failed to find the executable for a child
2057 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
2059 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
2060 - Avoid crashing when starting with a corrupt keys directory where
2061 the old ntor key and the new ntor key are identical. Fixes bug
2062 30916; bugfix on 0.2.4.8-alpha.
2064 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
2065 - Correctly exclude a redundant rust build job in Travis. Fixes bug
2066 31463; bugfix on 0.3.5.4-alpha.
2068 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
2069 - When testing port rebinding, don't busy-wait for tor to log.
2070 Instead, actually sleep for a short time before polling again.
2071 Also improve the formatting of control commands and log messages.
2072 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
2074 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
2075 - Log bugs about the TLS read buffer's length only once, rather than
2076 filling the logs with similar warnings. Fixes bug 31939; bugfix
2079 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
2080 - Always retry v2 single onion service intro and rend circuits with
2081 a 3-hop path. Previously, v2 single onion services used a 3-hop
2082 path when rendezvous circuits were retried after a remote or
2083 delayed failure, but a 1-hop path for immediate retries. Fixes bug
2084 23818; bugfix on 0.2.9.3-alpha.
2085 - Make v3 single onion services fall back to a 3-hop intro, when all
2086 intro points are unreachable via a 1-hop path. Previously, v3
2087 single onion services failed when all intro nodes were unreachable
2088 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
2090 o Documentation (backport from 0.4.2.1-alpha):
2091 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
2092 notice.html so that operators no longer have to host it
2093 themselves. Closes ticket 31089.
2095 o Testing (backport from 0.4.1.2-alpha):
2096 - Specify torrc paths (with empty files) when launching tor in
2097 integration tests; refrain from reading user and system torrcs.
2098 Resolves issue 29702.
2100 o Testing (continuous integration, backport from 0.4.1.1-alpha):
2101 - In Travis, show stem's tor log after failure. Closes ticket 30234.
2103 o Testing (continuous integration, backport from 0.4.1.5):
2104 - In Travis, make stem log a controller trace to the console, and
2105 tail stem's tor log after failure. Closes ticket 30591.
2106 - In Travis, only run the stem tests that use a tor binary. Closes
2109 o Testing (continuous integration, backport from 0.4.2.3-alpha):
2110 - Disable all but one Travis CI macOS build, to mitigate slow
2111 scheduling of Travis macOS jobs. Closes ticket 32177.
2112 - Run the chutney IPv6 networks as part of Travis CI. Closes
2114 - Simplify the Travis CI build matrix, and optimise for build time.
2115 Closes ticket 31859.
2116 - Use Windows Server 2019 instead of Windows Server 2016 in our
2117 Appveyor builds. Closes ticket 32086.
2119 o Testing (continuous integration, backport from 0.4.2.4-rc):
2120 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
2121 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
2122 until we can fix some Bionic permissions issues (see ticket
2123 32240). Related to ticket 31919.
2124 - Install the mingw OpenSSL package in Appveyor. This makes sure
2125 that the OpenSSL headers and libraries match in Tor's Appveyor
2126 builds. (This bug was triggered by an Appveyor image update.)
2127 Fixes bug 32449; bugfix on 0.3.5.6-rc.
2128 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
2130 o Testing (continuous integration, backport from 0.4.2.5):
2131 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
2132 extensions. Also activates clang's -Wtypedef-redefinition warnings.
2133 Build some jobs with -std=gnu99, and some jobs without.
2134 Closes ticket 32500.
2136 Changes in version 0.3.5.9 - 2019-12-09
2137 Tor 0.3.5.9 backports serveral fixes from later releases, including
2138 several that affect bridge users, relay stability, onion services,
2141 o Directory authority changes (backport from 0.4.1.5):
2142 - The directory authority "dizum" has a new IP address. Closes
2145 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
2146 - Consider our directory information to have changed when our list
2147 of bridges changes. Previously, Tor would not re-compute the
2148 status of its directory information when bridges changed, and
2149 therefore would not realize that it was no longer able to build
2150 circuits. Fixes part of bug 29875.
2151 - Do not count previously configured working bridges towards our
2152 total of working bridges. Previously, when Tor's list of bridges
2153 changed, it would think that the old bridges were still usable,
2154 and delay fetching router descriptors for the new ones. Fixes part
2155 of bug 29875; bugfix on 0.3.0.1-alpha.
2157 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
2158 - When considering upgrading circuits from "waiting for guard" to
2159 "open", always ignore circuits that are marked for close. Otherwise,
2160 we can end up in the situation where a subsystem is notified that
2161 a closing circuit has just opened, leading to undesirable
2162 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
2164 o Major bugfixes (NSS, relay, backport from 0.4.0.4-rc):
2165 - When running with NSS, disable TLS 1.2 ciphersuites that use
2166 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
2167 these ciphersuites don't work -- which caused relays to fail to
2168 handshake with one another when these ciphersuites were enabled.
2169 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
2171 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
2172 - Properly clean up the introduction point map when circuits change
2173 purpose from onion service circuits to pathbias, measurement, or
2174 other circuit types. This should fix some service-side instances
2175 of introduction point failure. Fixes bug 29034; bugfix
2178 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
2179 - Fix an unreachable bug in which an introduction point could try to
2180 send an INTRODUCE_ACK with a status code that Trunnel would refuse
2181 to encode, leading the relay to assert(). We've consolidated the
2182 ABI values into Trunnel now. Fixes bug 30454; bugfix
2184 - Clients can now handle unknown status codes from INTRODUCE_ACK
2185 cells. (The NACK behavior will stay the same.) This will allow us
2186 to extend status codes in the future without breaking the normal
2187 client behavior. Fixes another part of bug 30454; bugfix
2190 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
2191 - Stop ignoring torrc options after an %include directive, when the
2192 included directory ends with a file that does not contain any
2193 config options (but does contain comments or whitespace). Fixes
2194 bug 31408; bugfix on 0.3.1.1-alpha.
2196 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
2197 - Onion services now always use the exact number of intro points
2198 configured with the HiddenServiceNumIntroductionPoints option (or
2199 fewer if nodes are excluded). Before, a service could sometimes
2200 pick more intro points than configured. Fixes bug 31548; bugfix
2203 o Minor features (address selection, backport from 0.4.0.3-alpha):
2204 - Treat the subnet 100.64.0.0/10 as public for some purposes;
2205 private for others. This subnet is the RFC 6598 (Carrier Grade
2206 NAT) IP range, and is deployed by many ISPs as an alternative to
2207 RFC 1918 that does not break existing internal networks. Tor now
2208 blocks SOCKS and control ports on these addresses and warns users
2209 if client ports or ExtORPorts are listening on a RFC 6598 address.
2210 Closes ticket 28525. Patch by Neel Chauhan.
2212 o Minor features (bandwidth authority, backport from 0.4.0.4-rc):
2213 - Make bandwidth authorities ignore relays that are reported in the
2214 bandwidth file with the flag "vote=0". This change allows us to
2215 report unmeasured relays for diagnostic reasons without including
2216 their bandwidth in the bandwidth authorities' vote. Closes
2219 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
2220 - Add a "--list-modules" command to print a list of which compile-
2221 time modules are enabled. Closes ticket 30452.
2223 o Minor features (continuous integration, backport from 0.4.0.4-rc):
2224 - On Travis Rust builds, cleanup Rust registry and refrain from
2225 caching the "target/" directory to speed up builds. Resolves
2228 o Minor features (continuous integration, backport from 0.4.0.5):
2229 - In Travis, tell timelimit to use stem's backtrace signals, and
2230 launch python directly from timelimit, so python receives the
2231 signals from timelimit, rather than make. Closes ticket 30117.
2233 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
2234 - Remove sudo configuration lines from .travis.yml as they are no
2235 longer needed with current Travis build environment. Resolves
2238 o Minor features (continuous integration, backport from 0.4.1.4-rc):
2239 - Our Travis configuration now uses Chutney to run some network
2240 integration tests automatically. Closes ticket 29280.
2242 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
2243 - When building on Appveyor and Travis, pass the "-k" flag to make,
2244 so that we are informed of all compilation failures, not just the
2245 first one or two. Closes ticket 31372.
2247 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
2248 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
2249 in December 2018 (of which ~122 were still functional), with a
2250 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
2251 in June 2019. Closes ticket 28795.
2253 o Minor features (geoip, backport from 0.4.2.5):
2254 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
2255 Country database. Closes ticket 32685.
2257 o Minor features (NSS, diagnostic, backport from 0.4.0.4-rc):
2258 - Try to log an error from NSS (if there is any) and a more useful
2259 description of our situation if we are using NSS and a call to
2260 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
2262 o Minor features (stem tests, backport from 0.4.2.1-alpha):
2263 - Change "make test-stem" so it only runs the stem tests that use
2264 tor. This change makes test-stem faster and more reliable. Closes
2267 o Minor bugfixes (security, backport from 0.4.0.4-rc):
2268 - Verify in more places that we are not about to create a buffer
2269 with more than INT_MAX bytes, to avoid possible OOB access in the
2270 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
2271 fixed by Tobias Stoeckmann.
2272 - Fix a potential double free bug when reading huge bandwidth files.
2273 The issue is not exploitable in the current Tor network because
2274 the vulnerable code is only reached when directory authorities
2275 read bandwidth files, but bandwidth files come from a trusted
2276 source (usually the authorities themselves). Furthermore, the
2277 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
2278 which are not used by any of the current authorities. Fixes bug
2279 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
2282 o Minor bugfix (continuous integration, backport from 0.4.0.4-rc):
2283 - Reset coverage state on disk after Travis CI has finished. This
2284 should prevent future coverage merge errors from causing the test
2285 suite for the "process" subsystem to fail. The process subsystem
2286 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
2288 - Terminate test-stem if it takes more than 9.5 minutes to run.
2289 (Travis terminates the job after 10 minutes of no output.)
2290 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
2292 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
2293 - Avoid spurious errors when Appveyor CI fails before the install step.
2294 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
2296 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
2297 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
2298 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
2300 o Minor bugfixes (C correctness, backport from 0.4.0.4-rc):
2301 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
2302 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
2305 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
2306 - Fix a logic error that prevented the SessionGroup sub-option from
2307 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
2309 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
2310 - Fix a BUG() assertion that occurs within a very small race window
2311 between when a client intro circuit opens and when its descriptor
2312 gets cleaned up from the cache. The circuit is now closed early,
2313 which will trigger a re-fetch of the descriptor and continue the
2314 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
2316 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
2317 - Don't believe clock skew results from NETINFO cells that appear to
2318 arrive before we sent the VERSIONS cells they are responding to.
2319 Previously, we would accept them up to 3 minutes "in the past".
2320 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
2322 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
2323 - Fix a compilation warning on Windows about casting a function
2324 pointer for GetTickCount64(). Fixes bug 31374; bugfix
2327 o Minor bugfixes (compilation, backport from 0.4.0.2-alpha):
2328 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
2329 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
2331 o Minor bugfixes (compilation, backport from 0.4.1.5):
2332 - Avoid using labs() on time_t, which can cause compilation warnings
2333 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
2335 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
2336 - Suppress spurious float-conversion warnings from GCC when calling
2337 floating-point classifier functions on FreeBSD. Fixes part of bug
2338 31687; bugfix on 0.3.1.5-alpha.
2340 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
2341 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
2342 due to missing declarations of abort(), and prevent other such
2343 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
2345 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
2346 - Fix a bug that prevented us from supporting SOCKS5 proxies that
2347 want authentication along with configured (but unused!)
2348 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
2350 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
2351 - Avoid trying to read data from closed connections, which can cause
2352 needless loops in Libevent and infinite loops in Shadow. Fixes bug
2353 30344; bugfix on 0.1.1.1-alpha.
2355 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
2356 - Allow the test-stem job to fail in Travis, because it sometimes
2357 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
2358 - Skip test_rebind on macOS in Travis, because it is unreliable on
2359 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
2360 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
2361 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
2363 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
2364 - Avoid a set of possible code paths that could try to use freed
2365 memory in routerlist_free() while Tor was exiting. Fixes bug
2366 31003; bugfix on 0.1.2.2-alpha.
2368 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
2369 - Stop crashing after parsing an unknown descriptor purpose
2370 annotation. We think this bug can only be triggered by modifying a
2371 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
2373 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
2374 - Move the "bandwidth-file-headers" line in directory authority
2375 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
2378 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
2379 - On abort, try harder to flush the output buffers of log messages.
2380 On some platforms (macOS), log messages could be discarded when
2381 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
2382 - Report the tor version whenever an assertion fails. Previously, we
2383 only reported the Tor version on some crashes, and some non-fatal
2384 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
2386 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
2387 - When extracting an IPv6 address from a PF-based proxy, verify that
2388 we are actually configured to receive an IPv6 address, and log an
2389 internal error if not. Fixes part of bug 31687; bugfix
2392 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
2393 - When tor is missing descriptors for some primary entry guards,
2394 make the log message less alarming. It's normal for descriptors to
2395 expire, as long as tor fetches new ones soon after. Fixes bug
2396 31657; bugfix on 0.3.3.1-alpha.
2398 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
2399 - Avoid logging that we are relaxing a circuit timeout when that
2400 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
2402 o Minor bugfixes (logging, backport from 0.4.0.3-alpha):
2403 - Correct a misleading error message when IPv4Only or IPv6Only is
2404 used but the resolved address can not be interpreted as an address
2405 of the specified IP version. Fixes bug 13221; bugfix on
2406 0.2.3.9-alpha. Patch from Kris Katterjohn.
2407 - Log the correct port number for listening sockets when "auto" is
2408 used to let Tor pick the port number. Previously, port 0 was
2409 logged instead of the actual port number. Fixes bug 29144; bugfix
2410 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
2411 - Stop logging a BUG() warning when Tor is waiting for exit
2412 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
2414 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
2415 - Do not log a warning when running with an OpenSSL version other
2416 than the one Tor was compiled with, if the two versions should be
2417 compatible. Previously, we would warn whenever the version was
2418 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
2420 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
2421 - Change log level of message "Hash of session info was not as
2422 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
2425 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
2426 - Rate-limit our the logging message about the obsolete .exit
2427 notation. Previously, there was no limit on this warning, which
2428 could potentially be triggered many times by a hostile website.
2429 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
2431 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
2432 - Do not log a nonfatal assertion failure when receiving a VERSIONS
2433 cell on a connection using the obsolete v1 link protocol. Log a
2434 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
2436 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
2437 - Reset the periodic events' "enabled" flag when Tor is shut down
2438 cleanly. Previously, this flag was left on, which caused periodic
2439 events not to be re-enabled when Tor was relaunched in-process
2440 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
2443 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
2444 - Avoid a minor memory leak that could occur on relays when failing
2445 to create a "keys" directory. Fixes bug 30148; bugfix
2448 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
2449 - Fix a trivial memory leak when parsing an invalid value
2450 from a download schedule in the configuration. Fixes bug
2451 30894; bugfix on 0.3.4.1-alpha.
2453 o Minor bugfixes (memory management, backport from 0.4.0.3-alpha):
2454 - Refactor the shared random state's memory management so that it
2455 actually takes ownership of the shared random value pointers.
2456 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
2458 o Minor bugfixes (memory management, testing, backport from 0.4.0.3-alpha):
2459 - Stop leaking parts of the shared random state in the shared-random
2460 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
2462 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
2463 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
2464 implemenation) when failing to load an onion service client
2465 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
2467 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
2468 - When purging the DNS cache because of an out-of-memory condition,
2469 try purging just the older entries at first. Previously, we would
2470 always purge the whole thing. Fixes bug 29617; bugfix
2473 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
2474 - Avoid crashing in our tor_vasprintf() implementation on systems
2475 that define neither vasprintf() nor _vscprintf(). (This bug has
2476 been here long enough that we question whether people are running
2477 Tor on such systems, but we're applying the fix out of caution.)
2478 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
2481 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
2482 - Avoid crashing when starting with a corrupt keys directory where
2483 the old ntor key and the new ntor key are identical. Fixes bug
2484 30916; bugfix on 0.2.4.8-alpha.
2486 o Minor bugfixes (rust, backport from 0.4.0.5):
2487 - Abort on panic in all build profiles, instead of potentially
2488 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
2490 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
2491 - Correctly exclude a redundant rust build job in Travis. Fixes bug
2492 31463; bugfix on 0.3.5.4-alpha.
2494 o Minor bugfixes (single onion services, backport from 0.4.0.3-alpha):
2495 - Allow connections to single onion services to remain idle without
2496 being disconnected. Previously, relays acting as rendezvous points
2497 for single onion services were mistakenly closing idle rendezvous
2498 circuits after 60 seconds, thinking that they were unused
2499 directory-fetching circuits that had served their purpose. Fixes
2500 bug 29665; bugfix on 0.2.1.26.
2502 o Minor bugfixes (stats, backport from 0.4.0.3-alpha):
2503 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
2504 relay and bridge extra-info documents. Fixes bug 29017; bugfix
2507 o Minor bugfixes (testing, backport from 0.4.0.3-alpha):
2508 - Downgrade some LOG_ERR messages in the address/* tests to
2509 warnings. The LOG_ERR messages were occurring when we had no
2510 configured network. We were failing the unit tests, because we
2511 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
2512 29530; bugfix on 0.3.5.8.
2513 - Fix our gcov wrapper script to look for object files at the
2514 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
2516 o Minor bugfixes (testing, backport from 0.4.0.4-rc):
2517 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
2518 recent test-network.sh to use new chutney features in CI. Fixes
2519 bug 29703; bugfix on 0.2.9.1-alpha.
2520 - Fix a test failure on Windows caused by an unexpected "BUG"
2521 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
2524 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
2525 - When testing port rebinding, don't busy-wait for tor to log.
2526 Instead, actually sleep for a short time before polling again.
2527 Also improve the formatting of control commands and log messages.
2528 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
2530 o Minor bugfixes (TLS protocol, backport form 0.4.0.4-rc):
2531 - When classifying a client's selection of TLS ciphers, if the
2532 client ciphers are not yet available, do not cache the result.
2533 Previously, we had cached the unavailability of the cipher list
2534 and never looked again, which in turn led us to assume that the
2535 client only supported the ancient V1 link protocol. This, in turn,
2536 was causing Stem integration tests to stall in some cases. Fixes
2537 bug 30021; bugfix on 0.2.4.8-alpha.
2539 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
2540 - Log bugs about the TLS read buffer's length only once, rather than
2541 filling the logs with similar warnings. Fixes bug 31939; bugfix
2544 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
2545 - Always retry v2 single onion service intro and rend circuits with
2546 a 3-hop path. Previously, v2 single onion services used a 3-hop
2547 path when rendezvous circuits were retried after a remote or
2548 delayed failure, but a 1-hop path for immediate retries. Fixes bug
2549 23818; bugfix on 0.2.9.3-alpha.
2550 - Make v3 single onion services fall back to a 3-hop intro, when all
2551 intro points are unreachable via a 1-hop path. Previously, v3
2552 single onion services failed when all intro nodes were unreachable
2553 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
2555 o Minor bugfixes (Windows, CI, backport from 0.4.0.3-alpha):
2556 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
2557 Windows Server 2012 R2 job. The remaining 2 jobs still provide
2558 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
2559 fast_finish, so failed jobs terminate the build immediately. Fixes
2560 bug 29601; bugfix on 0.3.5.4-alpha.
2562 o Documentation (backport from 0.4.2.1-alpha):
2563 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
2564 notice.html so that operators no longer have to host it
2565 themselves. Closes ticket 31089.
2567 o Testing (backport from 0.4.1.2-alpha):
2568 - Specify torrc paths (with empty files) when launching tor in
2569 integration tests; refrain from reading user and system torrcs.
2570 Resolves issue 29702.
2572 o Testing (continuous integration, backport from 0.4.1.1-alpha):
2573 - In Travis, show stem's tor log after failure. Closes ticket 30234.
2575 o Testing (continuous integration, backport from 0.4.1.5):
2576 - In Travis, make stem log a controller trace to the console, and
2577 tail stem's tor log after failure. Closes ticket 30591.
2578 - In Travis, only run the stem tests that use a tor binary. Closes
2581 o Testing (continuous integration, backport from 0.4.2.3-alpha):
2582 - Disable all but one Travis CI macOS build, to mitigate slow
2583 scheduling of Travis macOS jobs. Closes ticket 32177.
2584 - Run the chutney IPv6 networks as part of Travis CI. Closes
2586 - Simplify the Travis CI build matrix, and optimise for build time.
2587 Closes ticket 31859.
2588 - Use Windows Server 2019 instead of Windows Server 2016 in our
2589 Appveyor builds. Closes ticket 32086.
2591 o Testing (continuous integration, backport from 0.4.2.4-rc):
2592 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
2593 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
2594 until we can fix some Bionic permissions issues (see ticket
2595 32240). Related to ticket 31919.
2596 - Install the mingw OpenSSL package in Appveyor. This makes sure
2597 that the OpenSSL headers and libraries match in Tor's Appveyor
2598 builds. (This bug was triggered by an Appveyor image update.)
2599 Fixes bug 32449; bugfix on 0.3.5.6-rc.
2600 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
2602 o Testing (continuous integration, backport from 0.4.2.5):
2603 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
2604 extensions. Also activates clang's -Wtypedef-redefinition warnings.
2605 Build some jobs with -std=gnu99, and some jobs without.
2606 Closes ticket 32500.
2608 Changes in version 0.4.2.4-rc - 2019-11-15
2609 Tor 0.4.2.4-rc is the first release candidate in its series. It fixes
2610 several bugs from earlier versions, including a few that would result in
2611 stack traces or incorrect behavior.
2613 o Minor features (build system):
2614 - Make pkg-config use --prefix when cross-compiling, if
2615 PKG_CONFIG_PATH is not set. Closes ticket 32191.
2617 o Minor features (geoip):
2618 - Update geoip and geoip6 to the November 6 2019 Maxmind GeoLite2
2619 Country database. Closes ticket 32440.
2621 o Minor bugfixes (client, onion service v3):
2622 - Fix a BUG() assertion that occurs within a very small race window
2623 between when a client intro circuit opens and when its descriptor
2624 gets cleaned up from the cache. The circuit is now closed early,
2625 which will trigger a re-fetch of the descriptor and continue the
2626 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
2628 o Minor bugfixes (code quality):
2629 - Fix "make check-includes" so it runs correctly on out-of-tree
2630 builds. Fixes bug 31335; bugfix on 0.3.5.1-alpha.
2632 o Minor bugfixes (configuration):
2633 - Log the option name when skipping an obsolete option. Fixes bug
2634 32295; bugfix on 0.4.2.1-alpha.
2636 o Minor bugfixes (crash):
2637 - When running Tor with an option like --verify-config or
2638 --dump-config that does not start the event loop, avoid crashing
2639 if we try to exit early because of an error. Fixes bug 32407;
2640 bugfix on 0.3.3.1-alpha.
2642 o Minor bugfixes (directory):
2643 - When checking if a directory connection is anonymous, test if the
2644 circuit was marked for close before looking at its channel. This
2645 avoids a BUG() stacktrace if the circuit was previously closed.
2646 Fixes bug 31958; bugfix on 0.4.2.1-alpha.
2648 o Minor bugfixes (shellcheck):
2649 - Fix minor shellcheck errors in the git-*.sh scripts. Fixes bug
2650 32402; bugfix on 0.4.2.1-alpha.
2651 - Start checking most scripts for shellcheck errors again. Fixes bug
2652 32402; bugfix on 0.4.2.1-alpha.
2654 o Testing (continuous integration):
2655 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
2656 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
2657 until we can fix some Bionic permissions issues (see ticket
2658 32240). Related to ticket 31919.
2659 - Install the mingw OpenSSL package in Appveyor. This makes sure
2660 that the OpenSSL headers and libraries match in Tor's Appveyor
2661 builds. (This bug was triggered by an Appveyor image update.)
2662 Fixes bug 32449; bugfix on 0.3.5.6-rc.
2663 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
2666 Changes in version 0.4.2.3-alpha - 2019-10-24
2667 This release fixes several bugs from the previous alpha release, and
2668 from earlier versions of Tor.
2670 o Major bugfixes (relay):
2671 - Relays now respect their AccountingMax bandwidth again. When
2672 relays entered "soft" hibernation (which typically starts when
2673 we've hit 90% of our AccountingMax), we had stopped checking
2674 whether we should enter hard hibernation. Soft hibernation refuses
2675 new connections and new circuits, but the existing circuits can
2676 continue, meaning that relays could have exceeded their configured
2677 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
2679 o Major bugfixes (v3 onion services):
2680 - Onion services now always use the exact number of intro points
2681 configured with the HiddenServiceNumIntroductionPoints option (or
2682 fewer if nodes are excluded). Before, a service could sometimes
2683 pick more intro points than configured. Fixes bug 31548; bugfix
2686 o Minor feature (onion services, control port):
2687 - The ADD_ONION command's keyword "BEST" now defaults to ED25519-V3
2688 (v3) onion services. Previously it defaulted to RSA1024 (v2).
2689 Closes ticket 29669.
2691 o Minor features (testing):
2692 - When running tests that attempt to look up hostnames, replace the
2693 libc name lookup functions with ones that do not actually touch
2694 the network. This way, the tests complete more quickly in the
2695 presence of a slow or missing DNS resolver. Closes ticket 31841.
2697 o Minor features (testing, continuous integration):
2698 - Disable all but one Travis CI macOS build, to mitigate slow
2699 scheduling of Travis macOS jobs. Closes ticket 32177.
2700 - Run the chutney IPv6 networks as part of Travis CI. Closes
2702 - Simplify the Travis CI build matrix, and optimise for build time.
2703 Closes ticket 31859.
2704 - Use Windows Server 2019 instead of Windows Server 2016 in our
2705 Appveyor builds. Closes ticket 32086.
2707 o Minor bugfixes (build system):
2708 - Interpret "--disable-module-dirauth=no" correctly. Fixes bug
2709 32124; bugfix on 0.3.4.1-alpha.
2710 - Interpret "--with-tcmalloc=no" correctly. Fixes bug 32124; bugfix
2712 - Stop failing when jemalloc is requested, but tcmalloc is not
2713 found. Fixes bug 32124; bugfix on 0.3.5.1-alpha.
2714 - When pkg-config is not installed, or a library that depends on
2715 pkg-config is not found, tell the user what to do to fix the
2716 problem. Fixes bug 31922; bugfix on 0.3.1.1-alpha.
2718 o Minor bugfixes (connections):
2719 - Avoid trying to read data from closed connections, which can cause
2720 needless loops in Libevent and infinite loops in Shadow. Fixes bug
2721 30344; bugfix on 0.1.1.1-alpha.
2723 o Minor bugfixes (error handling):
2724 - Always lock the backtrace buffer before it is used. Fixes bug
2725 31734; bugfix on 0.2.5.3-alpha.
2727 o Minor bugfixes (mainloop, periodic events, in-process API):
2728 - Reset the periodic events' "enabled" flag when Tor is shut down
2729 cleanly. Previously, this flag was left on, which caused periodic
2730 events not to be re-enabled when Tor was relaunched in-process
2731 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
2734 o Minor bugfixes (process management):
2735 - Remove overly strict assertions that triggered when a pluggable
2736 transport failed to launch. Fixes bug 31091; bugfix
2738 - Remove an assertion in the Unix process backend. This assertion
2739 would trigger when we failed to find the executable for a child
2740 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
2742 o Minor bugfixes (testing):
2743 - Avoid intermittent test failures due to a test that had relied on
2744 inconsistent timing sources. Fixes bug 31995; bugfix
2746 - When testing port rebinding, don't busy-wait for tor to log.
2747 Instead, actually sleep for a short time before polling again.
2748 Also improve the formatting of control commands and log messages.
2749 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
2751 o Minor bugfixes (tls, logging):
2752 - Log bugs about the TLS read buffer's length only once, rather than
2753 filling the logs with similar warnings. Fixes bug 31939; bugfix
2756 o Minor bugfixes (v3 onion services):
2757 - Fix an implicit conversion from ssize_t to size_t discovered by
2758 Coverity. Fixes bug 31682; bugfix on 0.4.2.1-alpha.
2759 - Fix a memory leak in an unlikely error code path when encoding HS
2760 DoS establish intro extension cell. Fixes bug 32063; bugfix
2762 - When cleaning up intro circuits for a v3 onion service, don't
2763 remove circuits that have an established or pending circuit, even
2764 if they ran out of retries. This way, we don't remove a circuit on
2765 its last retry. Fixes bug 31652; bugfix on 0.3.2.1-alpha.
2768 - Correct the description of "GuardLifetime". Fixes bug 31189;
2769 bugfix on 0.3.0.1-alpha.
2770 - Make clear in the man page, in both the bandwidth section and the
2771 AccountingMax section, that Tor counts in powers of two, not
2772 powers of ten: 1 GByte is 1024*1024*1024 bytes, not one billion
2773 bytes. Resolves ticket 32106.
2776 Changes in version 0.4.2.2-alpha - 2019-10-07
2777 This release fixes several bugs from the previous alpha release, and
2778 from earlier versions. It also includes a change in authorities, so
2779 that they begin to reject the currently unsupported release series.
2781 o Major features (directory authorities):
2782 - Directory authorities now reject relays running all currently
2783 deprecated release series. The currently supported release series
2784 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
2786 o Major bugfixes (embedded Tor):
2787 - Avoid a possible crash when restarting Tor in embedded mode and
2788 enabling a different set of publish/subscribe messages. Fixes bug
2789 31898; bugfix on 0.4.1.1-alpha.
2791 o Major bugfixes (torrc parsing):
2792 - Stop ignoring torrc options after an %include directive, when the
2793 included directory ends with a file that does not contain any
2794 config options (but does contain comments or whitespace). Fixes
2795 bug 31408; bugfix on 0.3.1.1-alpha.
2797 o Minor features (auto-formatting scripts):
2798 - When annotating C macros, never generate a line that our check-
2799 spaces script would reject. Closes ticket 31759.
2800 - When annotating C macros, try to remove cases of double-negation.
2801 Closes ticket 31779.
2803 o Minor features (continuous integration):
2804 - When building on Appveyor and Travis, pass the "-k" flag to make,
2805 so that we are informed of all compilation failures, not just the
2806 first one or two. Closes ticket 31372.
2808 o Minor features (geoip):
2809 - Update geoip and geoip6 to the October 1 2019 Maxmind GeoLite2
2810 Country database. Closes ticket 31931.
2812 o Minor features (maintenance scripts):
2813 - Add a Coccinelle script to detect bugs caused by incrementing or
2814 decrementing a variable inside a call to log_debug(). Since
2815 log_debug() is a macro whose arguments are conditionally
2816 evaluated, it is usually an error to do this. One such bug was
2817 30628, in which SENDME cells were miscounted by a decrement
2818 operator inside a log_debug() call. Closes ticket 30743.
2820 o Minor features (onion services v3):
2821 - Assist users who try to setup v2 client authorization in v3 onion
2822 services by pointing them to the right documentation. Closes
2825 o Minor bugfixes (Appveyor continuous integration):
2826 - Avoid spurious errors when Appveyor CI fails before the install
2827 step. Fixes bug 31884; bugfix on 0.3.4.2-alpha.
2829 o Minor bugfixes (best practices tracker):
2830 - When listing overbroad exceptions, do not also list problems, and
2831 do not list insufficiently broad exceptions. Fixes bug 31338;
2832 bugfix on 0.4.2.1-alpha.
2834 o Minor bugfixes (controller protocol):
2835 - Fix the MAPADDRESS controller command to accept one or more
2836 arguments. Previously, it required two or more arguments, and
2837 ignored the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
2839 o Minor bugfixes (logging):
2840 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
2841 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
2842 - Disable backtrace signal handlers when shutting down tor. Fixes
2843 bug 31614; bugfix on 0.2.5.2-alpha.
2844 - Rate-limit our the logging message about the obsolete .exit
2845 notation. Previously, there was no limit on this warning, which
2846 could potentially be triggered many times by a hostile website.
2847 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
2848 - When initialising log domain masks, only set known log domains.
2849 Fixes bug 31854; bugfix on 0.2.1.1-alpha.
2851 o Minor bugfixes (logging, protocol violations):
2852 - Do not log a nonfatal assertion failure when receiving a VERSIONS
2853 cell on a connection using the obsolete v1 link protocol. Log a
2854 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
2856 o Minor bugfixes (modules):
2857 - Explain what the optional Directory Authority module is, and what
2858 happens when it is disabled. Fixes bug 31825; bugfix
2861 o Minor bugfixes (multithreading):
2862 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
2863 31736; bugfix on 0.0.7.
2865 o Minor bugfixes (relay):
2866 - Avoid crashing when starting with a corrupt keys directory where
2867 the old ntor key and the new ntor key are identical. Fixes bug
2868 30916; bugfix on 0.2.4.8-alpha.
2870 o Minor bugfixes (tests, SunOS):
2871 - Avoid a map_anon_nofork test failure due to a signed/unsigned
2872 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
2874 o Code simplification and refactoring:
2875 - Refactor connection_control_process_inbuf() to reduce the size of
2876 a practracker exception. Closes ticket 31840.
2877 - Refactor the microdescs_parse_from_string() function into smaller
2878 pieces, for better comprehensibility. Closes ticket 31675.
2879 - Use SEVERITY_MASK_IDX() to find the LOG_* mask indexes in the unit
2880 tests and fuzzers, rather than using hard-coded values. Closes
2882 - Interface for function `decrypt_desc_layer` cleaned up. Closes
2886 - Document the signal-safe logging behaviour in the tor man page.
2887 Also add some comments to the relevant functions. Closes
2889 - Explain why we can't destroy the backtrace buffer mutex. Explain
2890 why we don't need to destroy the log mutex. Closes ticket 31736.
2891 - The Tor source code repository now includes a (somewhat dated)
2892 description of Tor's modular architecture, in doc/HACKING/design.
2893 This is based on the old "tor-guts.git" repository, which we are
2894 adopting and superseding. Closes ticket 31849.
2897 Changes in version 0.4.1.6 - 2019-09-19
2898 This release backports several bugfixes to improve stability and
2899 correctness. Anyone experiencing build problems or crashes with 0.4.1.5,
2900 or experiencing reliability issues with single onion services, should
2903 o Major bugfixes (crash, Linux, Android, backport from 0.4.2.1-alpha):
2904 - Tolerate systems (including some Android installations) where
2905 madvise and MADV_DONTDUMP are available at build-time, but not at
2906 run time. Previously, these systems would notice a failed syscall
2907 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
2908 - Tolerate systems (including some Linux installations) where
2909 madvise and/or MADV_DONTFORK are available at build-time, but not
2910 at run time. Previously, these systems would notice a failed
2911 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
2913 o Minor features (stem tests, backport from 0.4.2.1-alpha):
2914 - Change "make test-stem" so it only runs the stem tests that use
2915 tor. This change makes test-stem faster and more reliable. Closes
2918 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
2919 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
2920 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
2922 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
2923 - Add more stub functions to fix compilation on Android with link-
2924 time optimization when --disable-module-dirauth is used.
2925 Previously, these compilation settings would make the compiler
2926 look for functions that didn't exist. Fixes bug 31552; bugfix
2928 - Suppress spurious float-conversion warnings from GCC when calling
2929 floating-point classifier functions on FreeBSD. Fixes part of bug
2930 31687; bugfix on 0.3.1.5-alpha.
2932 o Minor bugfixes (controller protocol):
2933 - Fix the MAPADDRESS controller command to accept one or more
2934 arguments. Previously, it required two or more arguments, and ignored
2935 the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
2937 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
2938 - When extracting an IPv6 address from a PF-based proxy, verify that
2939 we are actually configured to receive an IPv6 address, and log an
2940 internal error if not. Fixes part of bug 31687; bugfix
2943 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
2944 - When tor is missing descriptors for some primary entry guards,
2945 make the log message less alarming. It's normal for descriptors to
2946 expire, as long as tor fetches new ones soon after. Fixes bug
2947 31657; bugfix on 0.3.3.1-alpha.
2949 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
2950 - Change log level of message "Hash of session info was not as
2951 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
2954 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
2955 - Correctly exclude a redundant rust build job in Travis. Fixes bug
2956 31463; bugfix on 0.3.5.4-alpha.
2958 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
2959 - Always retry v2 single onion service intro and rend circuits with
2960 a 3-hop path. Previously, v2 single onion services used a 3-hop
2961 path when rendezvous circuits were retried after a remote or
2962 delayed failure, but a 1-hop path for immediate retries. Fixes bug
2963 23818; bugfix on 0.2.9.3-alpha.
2965 o Minor bugfixes (v3 single onion services, backport from 0.4.2.1-alpha):
2966 - Always retry v3 single onion service intro and rend circuits with
2967 a 3-hop path. Previously, v3 single onion services used a 3-hop
2968 path when rend circuits were retried after a remote or delayed
2969 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
2970 bugfix on 0.3.2.1-alpha.
2971 - Make v3 single onion services fall back to a 3-hop intro, when all
2972 intro points are unreachable via a 1-hop path. Previously, v3
2973 single onion services failed when all intro nodes were unreachable
2974 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
2976 o Documentation (backport from 0.4.2.1-alpha):
2977 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
2978 notice.html so that operators no longer have to host it
2979 themselves. Closes ticket 31089.
2982 Changes in version 0.4.2.1-alpha - 2019-09-17
2983 This is the first alpha release in the 0.4.2.x series. It adds new
2984 defenses for denial-of-service attacks against onion services. It also
2985 includes numerous kinds of bugfixes and refactoring to help improve
2986 Tor's stability and ease of development.
2988 o Major features (onion service v3, denial of service):
2989 - Add onion service introduction denial of service defenses. Intro
2990 points can now rate-limit client introduction requests, using
2991 parameters that can be sent by the service within the
2992 ESTABLISH_INTRO cell. If the cell extension for this is not used,
2993 the intro point will honor the consensus parameters. Closes
2996 o Major bugfixes (circuit build, guard):
2997 - When considering upgrading circuits from "waiting for guard" to
2998 "open", always ignore circuits that are marked for close.
2999 Previously we could end up in the situation where a subsystem is
3000 notified of a circuit opening, but the circuit is still marked for
3001 close, leading to undesirable behavior. Fixes bug 30871; bugfix
3004 o Major bugfixes (crash, Linux, Android):
3005 - Tolerate systems (including some Android installations) where
3006 madvise and MADV_DONTDUMP are available at build-time, but not at
3007 run time. Previously, these systems would notice a failed syscall
3008 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
3009 - Tolerate systems (including some Linux installations) where
3010 madvise and/or MADV_DONTFORK are available at build-time, but not
3011 at run time. Previously, these systems would notice a failed
3012 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
3014 o Minor features (best practices tracker):
3015 - Our best-practices tracker now integrates with our include-checker
3016 tool to keep track of how many layering violations we have not yet
3017 fixed. We hope to reduce this number over time to improve Tor's
3018 modularity. Closes ticket 31176.
3019 - Add a TOR_PRACTRACKER_OPTIONS variable for passing arguments to
3020 practracker from the environment. We may want this for continuous
3021 integration. Closes ticket 31309.
3022 - Give a warning rather than an error when a practracker exception
3023 is violated by a small amount, add a --list-overbroad option to
3024 practracker that lists exceptions that are stricter than they need
3025 to be, and provide an environment variable for disabling
3026 practracker. Closes ticket 30752.
3027 - Our best-practices tracker now looks at headers as well as C
3028 files. Closes ticket 31175.
3030 o Minor features (build system):
3031 - Add --disable-manpage and --disable-html-manual options to
3032 configure script. This will enable shortening build times by not
3033 building documentation. Resolves issue 19381.
3035 o Minor features (compilation):
3036 - Log a more useful error message when we are compiling and one of
3037 the compile-time hardening options we have selected can be linked
3038 but not executed. Closes ticket 27530.
3040 o Minor features (configuration):
3041 - The configuration code has been extended to allow splitting
3042 configuration data across multiple objects. Previously, all
3043 configuration data needed to be kept in a single object, which
3044 tended to become bloated. Closes ticket 31240.
3046 o Minor features (continuous integration):
3047 - When running CI builds on Travis, put some random data in
3048 ~/.torrc, to make sure no tests are reading the Tor configuration
3049 file from its default location. Resolves issue 30102.
3051 o Minor features (debugging):
3052 - Log a nonfatal assertion failure if we encounter a configuration
3053 line whose command is "CLEAR" but which has a nonempty value. This
3054 should be impossible, according to the rules of our configuration
3055 line parsing. Closes ticket 31529.
3057 o Minor features (git hooks):
3058 - Our pre-commit git hook now checks for a special file before
3059 running practracker, so that practracker only runs on branches
3060 that are based on master. Since the pre-push hook calls the pre-
3061 commit hook, practracker will also only run before pushes of
3062 branches based on master. Closes ticket 30979.
3064 o Minor features (git scripts):
3065 - Add a "--" command-line argument, to separate git-push-all.sh
3066 script arguments from arguments that are passed through to git
3067 push. Closes ticket 31314.
3068 - Add a -r <remote-name> argument to git-push-all.sh, so the script
3069 can push test branches to a personal remote. Closes ticket 31314.
3070 - Add a -t <test-branch-prefix> argument to git-merge-forward.sh and
3071 git-push-all.sh, which makes these scripts create, merge forward,
3072 and push test branches. Closes ticket 31314.
3073 - Add a -u argument to git-merge-forward.sh, so that the script can
3074 re-use existing test branches after a merge failure and fix.
3075 Closes ticket 31314.
3076 - Add a TOR_GIT_PUSH env var, which sets the default git push
3077 command and arguments for git-push-all.sh. Closes ticket 31314.
3078 - Add a TOR_PUSH_DELAY variable to git-push-all.sh, which makes the
3079 script push master and maint branches with a delay between each
3080 branch. These delays trigger the CI jobs in a set order, which
3081 should show the most likely failures first. Also make pushes
3082 atomic by default, and make the script pass any command-line
3083 arguments to git push. Closes ticket 29879.
3084 - Call the shellcheck script from the pre-commit hook. Closes
3086 - Skip pushing test branches that are the same as a remote
3087 maint/release/master branch in git-push-all.sh by default. Add a
3088 -s argument, so git-push-all.sh can push all test branches. Closes
3091 o Minor features (IPv6, logging):
3092 - Log IPv6 addresses as well as IPv4 addresses when describing
3093 routerinfos, routerstatuses, and nodes. Closes ticket 21003.
3095 o Minor features (onion service v3):
3096 - Do not allow single hop clients to fetch or post an HS descriptor
3097 from an HSDir. Closes ticket 24964.
3099 o Minor features (onion service):
3100 - Disallow single-hop clients at the introduction point. We've
3101 removed Tor2web support a while back and single-hop rendezvous
3102 attempts are blocked at the relays. This change should remove load
3103 off the network from spammy clients. Close ticket 24963.
3105 o Minor features (stem tests):
3106 - Change "make test-stem" so it only runs the stem tests that use
3107 tor. This change makes test-stem faster and more reliable. Closes
3110 o Minor features (testing):
3111 - Add a script to invoke "tor --dump-config" and "tor
3112 --verify-config" with various configuration options, and see
3113 whether tor's resulting configuration or error messages are what
3114 we expect. Use it for integration testing of our +Option and
3115 /Option flags. Closes ticket 31637.
3116 - Improve test coverage for our existing configuration parsing and
3117 management API. Closes ticket 30893.
3118 - Add integration tests to make sure that practracker gives the
3119 outputs we expect. Closes ticket 31477.
3120 - The practracker self-tests are now run as part of the Tor test
3121 suite. Closes ticket 31304.
3123 o Minor features (token bucket):
3124 - Implement a generic token bucket that uses a single counter, for
3125 use in anti-DoS onion service work. Closes ticket 30687.
3127 o Minor bugfixes (best practices tracker):
3128 - Fix a few issues in the best-practices script, including tests,
3129 tab tolerance, error reporting, and directory-exclusion logic.
3130 Fixes bug 29746; bugfix on 0.4.1.1-alpha.
3131 - When running check-best-practices, only consider files in the src
3132 subdirectory. Previously we had recursively considered all
3133 subdirectories, which made us get confused by the temporary
3134 directories made by "make distcheck". Fixes bug 31578; bugfix
3137 o Minor bugfixes (build system):
3138 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
3139 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
3141 o Minor bugfixes (chutney, makefiles, documentation):
3142 - "make test-network-all" now shows the warnings from each test-
3143 network.sh run on the console, so developers see new warnings
3144 early. We've also improved the documentation for this feature, and
3145 renamed a Makefile variable so the code is self-documenting. Fixes
3146 bug 30455; bugfix on 0.3.0.4-rc.
3148 o Minor bugfixes (compilation):
3149 - Add more stub functions to fix compilation on Android with link-
3150 time optimization when --disable-module-dirauth is used.
3151 Previously, these compilation settings would make the compiler
3152 look for functions that didn't exist. Fixes bug 31552; bugfix
3154 - Suppress spurious float-conversion warnings from GCC when calling
3155 floating-point classifier functions on FreeBSD. Fixes part of bug
3156 31687; bugfix on 0.3.1.5-alpha.
3158 o Minor bugfixes (configuration):
3159 - Invalid floating-point values in the configuration file are now
3160 treated as errors in the configuration. Previously, they were
3161 ignored and treated as zero. Fixes bug 31475; bugfix on 0.0.1.
3163 o Minor bugfixes (coverity):
3164 - Add an assertion when parsing a BEGIN cell so that coverity can be
3165 sure that we are not about to dereference a NULL address. Fixes
3166 bug 31026; bugfix on 0.2.4.7-alpha. This is CID 1447296.
3167 - In our siphash implementation, when building for coverity, use
3168 memcpy in place of a switch statement, so that coverity can tell
3169 we are not accessing out-of-bounds memory. Fixes bug 31025; bugfix
3170 on 0.2.8.1-alpha. This is tracked as CID 1447293 and 1447295.
3171 - Fix several coverity warnings from our unit tests. Fixes bug
3172 31030; bugfix on 0.2.4.1-alpha, 0.3.2.1-alpha, and 0.4.0.1-alpha.
3174 o Minor bugfixes (developer tooling):
3175 - Only log git script changes in the post-merge script when the
3176 merge was to the master branch. Fixes bug 31040; bugfix
3179 o Minor bugfixes (directory authorities):
3180 - Return a distinct status when formatting annotations fails. Fixes
3181 bug 30780; bugfix on 0.2.0.8-alpha.
3183 o Minor bugfixes (error handling):
3184 - On abort, try harder to flush the output buffers of log messages.
3185 On some platforms (macOS), log messages could be discarded when
3186 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3187 - Report the tor version whenever an assertion fails. Previously, we
3188 only reported the Tor version on some crashes, and some non-fatal
3189 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3190 - When tor aborts due to an error, close log file descriptors before
3191 aborting. Closing the logs makes some OSes flush log file buffers,
3192 rather than deleting buffered log lines. Fixes bug 31594; bugfix
3195 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6):
3196 - When extracting an IPv6 address from a PF-based proxy, verify that
3197 we are actually configured to receive an IPv6 address, and log an
3198 internal error if not. Fixes part of bug 31687; bugfix
3201 o Minor bugfixes (git hooks):
3202 - Remove a duplicate call to practracker from the pre-push hook. The
3203 pre-push hook already calls the pre-commit hook, which calls
3204 practracker. Fixes bug 31462; bugfix on 0.4.1.1-alpha.
3206 o Minor bugfixes (git scripts):
3207 - Stop hard-coding the bash path in the git scripts. Some OSes don't
3208 have bash in /usr/bin, others have an ancient bash at this path.
3209 Fixes bug 30840; bugfix on 0.4.0.1-alpha.
3210 - Stop hard-coding the tor master branch name and worktree path in
3211 the git scripts. Fixes bug 30841; bugfix on 0.4.0.1-alpha.
3212 - Allow git-push-all.sh to be run from any directory. Previously,
3213 the script only worked if run from an upstream worktree directory.
3214 Closes ticket 31678.
3216 o Minor bugfixes (guards):
3217 - When tor is missing descriptors for some primary entry guards,
3218 make the log message less alarming. It's normal for descriptors to
3219 expire, as long as tor fetches new ones soon after. Fixes bug
3220 31657; bugfix on 0.3.3.1-alpha.
3222 o Minor bugfixes (ipv6):
3223 - Check for private IPv6 addresses alongside their IPv4 equivalents
3224 when authorities check descriptors. Previously, we only checked
3225 for private IPv4 addresses. Fixes bug 31088; bugfix on
3226 0.2.3.21-rc. Patch by Neel Chauhan.
3227 - When parsing microdescriptors, we should check the IPv6 exit
3228 policy alongside IPv4. Previously, we checked both exit policies
3229 for only router info structures, while microdescriptors were
3230 IPv4-only. Fixes bug 27284; bugfix on 0.2.3.1-alpha. Patch by
3233 o Minor bugfixes (logging):
3234 - Change log level of message "Hash of session info was not as
3235 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
3237 - Fix a code issue that would have broken our parsing of log domains
3238 as soon as we had 33 of them. Fortunately, we still only have 29.
3239 Fixes bug 31451; bugfix on 0.4.1.4-rc.
3241 o Minor bugfixes (memory management):
3242 - Stop leaking a small amount of memory in nt_service_install(), in
3243 unreachable code. Fixes bug 30799; bugfix on 0.2.0.7-alpha. Patch
3246 o Minor bugfixes (networking, IP addresses):
3247 - When parsing addresses via Tor's internal DNS lookup API, reject
3248 IPv4 addresses in square brackets, and accept IPv6 addresses in
3249 square brackets. This change completes the work started in 23082,
3250 making address parsing consistent between tor's internal DNS
3251 lookup and address parsing APIs. Fixes bug 30721; bugfix
3253 - When parsing addresses via Tor's internal address:port parsing and
3254 DNS lookup APIs, require IPv6 addresses with ports to have square
3255 brackets. But allow IPv6 addresses without ports, whether or not
3256 they have square brackets. Fixes bug 30721; bugfix
3259 o Minor bugfixes (onion service v3):
3260 - When purging the client descriptor cache, close any introduction
3261 point circuits associated with purged cache entries. This avoids
3262 picking those circuits later when connecting to the same
3263 introduction points. Fixes bug 30921; bugfix on 0.3.2.1-alpha.
3265 o Minor bugfixes (onion services):
3266 - In the hs_ident_circuit_t data structure, remove the unused field
3267 circuit_type and the respective argument in hs_ident_circuit_new().
3268 This field was set by clients (for introduction) and services (for
3269 introduction and rendezvous) but was never used afterwards. Fixes
3270 bug 31490; bugfix on 0.3.2.1-alpha. Patch by Neel Chauhan.
3272 o Minor bugfixes (operator tools):
3273 - Make tor-print-ed-signing-cert(1) print certificate expiration
3274 date in RFC 1123 and UNIX timestamp formats, to make output
3275 machine readable. Fixes bug 31012; bugfix on 0.3.5.1-alpha.
3277 o Minor bugfixes (rust):
3278 - Correctly exclude a redundant rust build job in Travis. Fixes bug
3279 31463; bugfix on 0.3.5.4-alpha.
3280 - Raise the minimum rustc version to 1.31.0, as checked by configure
3281 and CI. Fixes bug 31442; bugfix on 0.3.5.4-alpha.
3283 o Minor bugfixes (sendme, code structure):
3284 - Rename the trunnel SENDME file definition from sendme.trunnel to
3285 sendme_cell.trunnel to avoid having twice sendme.{c|h} in the
3286 repository. Fixes bug 30769; bugfix on 0.4.1.1-alpha.
3288 o Minor bugfixes (statistics):
3289 - Stop removing the ed25519 signature if the extra info file is too
3290 big. If the signature data was removed, but the keyword was kept,
3291 this could result in an unparseable extra info file. Fixes bug
3292 30958; bugfix on 0.2.7.2-alpha.
3294 o Minor bugfixes (subsystems):
3295 - Make the subsystem init order match the subsystem module
3296 dependencies. Call windows process security APIs as early as
3297 possible. Initialize logging before network and time, so that
3298 network and time can use logging. Fixes bug 31615; bugfix
3301 o Minor bugfixes (testing):
3302 - Teach the util/socketpair_ersatz test to work correctly when we
3303 have no network stack configured. Fixes bug 30804; bugfix
3306 o Minor bugfixes (v2 single onion services):
3307 - Always retry v2 single onion service intro and rend circuits with
3308 a 3-hop path. Previously, v2 single onion services used a 3-hop
3309 path when rendezvous circuits were retried after a remote or
3310 delayed failure, but a 1-hop path for immediate retries. Fixes bug
3311 23818; bugfix on 0.2.9.3-alpha.
3313 o Minor bugfixes (v3 single onion services):
3314 - Always retry v3 single onion service intro and rend circuits with
3315 a 3-hop path. Previously, v3 single onion services used a 3-hop
3316 path when rend circuits were retried after a remote or delayed
3317 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
3318 bugfix on 0.3.2.1-alpha.
3319 - Make v3 single onion services fall back to a 3-hop intro, when all
3320 intro points are unreachable via a 1-hop path. Previously, v3
3321 single onion services failed when all intro nodes were unreachable
3322 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
3325 - Improve documentation in circuit padding subsystem. Patch by
3326 Tobias Pulls. Closes ticket 31113.
3327 - Include an example usage for IPv6 ORPort in our sample torrc.
3328 Closes ticket 31320; patch from Ali Raheem.
3329 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
3330 notice.html so that operators no longer have to host it
3331 themselves. Closes ticket 31089.
3334 - No longer include recommended package digests in votes as detailed
3335 in proposal 301. The RecommendedPackages torrc option is
3336 deprecated and will no longer have any effect. "package" lines
3337 will still be considered when computing consensuses for consensus
3338 methods that include them. (This change has no effect on the list
3339 of recommended Tor versions, which is still in use.) Closes
3341 - Remove torctl.in from contrib/dist directory. Resolves
3345 - Run shellcheck for all non-third-party shell scripts that are
3346 shipped with Tor. Closes ticket 29533.
3347 - When checking shell scripts, ignore any user-created directories.
3348 Closes ticket 30967.
3350 o Code simplification and refactoring (config handling):
3351 - Extract our variable manipulation code from confparse.c to a new
3352 lower-level typedvar.h module. Closes ticket 30864.
3353 - Lower another layer of object management from confparse.c to a
3354 more general tool. Now typed structure members are accessible via
3355 an abstract type. Implements ticket 30914.
3356 - Move our backend logic for working with configuration and state
3357 files into a lower-level library, since it no longer depends on
3358 any tor-specific functionality. Closes ticket 31626.
3359 - Numerous simplifications in configuration-handling logic: remove
3360 duplicated macro definitions, replace magical names with flags,
3361 and refactor "TestingTorNetwork" to use the same default-option
3362 logic as the rest of Tor. Closes ticket 30935.
3363 - Replace our ad-hoc set of flags for configuration variables and
3364 configuration variable types with fine-grained orthogonal flags
3365 corresponding to the actual behavior we want. Closes ticket 31625.
3367 o Code simplification and refactoring (misc):
3368 - Eliminate some uses of lower-level control reply abstractions,
3369 primarily in the onion_helper functions. Closes ticket 30889.
3370 - Rework bootstrap tracking to use the new publish-subscribe
3371 subsystem. Closes ticket 29976.
3372 - Rewrite format_node_description() and router_get_verbose_nickname()
3373 to use strlcpy() and strlcat(). The previous implementation used
3374 memcpy() and pointer arithmetic, which was error-prone. Closes
3375 ticket 31545. This is CID 1452819.
3376 - Split extrainfo_dump_to_string() into smaller functions. Closes
3378 - Use the ptrdiff_t type consistently for expressing variable
3379 offsets and pointer differences. Previously we incorrectly (but
3380 harmlessly) used int and sometimes off_t for these cases. Closes
3382 - Use the subsystems mechanism to manage the main event loop code.
3383 Closes ticket 30806.
3384 - Various simplifications and minor improvements to the circuit
3385 padding machines. Patch by Tobias Pulls. Closes tickets 31112
3388 o Documentation (hard-coded directories):
3389 - Improve the documentation for the DirAuthority and FallbackDir
3390 torrc options. Closes ticket 30955.
3392 o Documentation (tor.1 man page):
3393 - Fix typo in tor.1 man page: the option is "--help", not "-help".
3394 Fixes bug 31008; bugfix on 0.2.2.9-alpha.
3397 Changes in version 0.4.1.5 - 2019-08-20
3398 This is the first stable release in the 0.4.1.x series. This series
3399 adds experimental circuit-level padding, authenticated SENDME cells to
3400 defend against certain attacks, and several performance improvements
3401 to save on CPU consumption. It fixes bugs in bootstrapping and v3
3402 onion services. It also includes numerous smaller features and
3403 bugfixes on earlier versions.
3405 Per our support policy, we will support the 0.4.1.x series for nine
3406 months, or until three months after the release of a stable 0.4.2.x:
3407 whichever is longer. If you need longer-term support, please stick
3408 with 0.3.5.x, which will we plan to support until Feb 2022.
3410 Below are the changes since 0.4.1.4-rc. For a complete list of changes
3411 since 0.4.0.5, see the ReleaseNotes file.
3413 o Directory authority changes:
3414 - The directory authority "dizum" has a new IP address. Closes
3417 o Minor features (circuit padding logging):
3418 - Demote noisy client-side warn logs about circuit padding to
3419 protocol warnings. Add additional log messages and circuit ID
3420 fields to help with bug 30992 and any other future issues.
3422 o Minor bugfixes (circuit padding negotiation):
3423 - Bump the circuit padding protocol version to explicitly signify
3424 that the HS setup machine support is finalized in 0.4.1.x-stable.
3425 This also means that 0.4.1.x-alpha clients will not negotiate
3426 padding with 0.4.1.x-stable relays, and 0.4.1.x-stable clients
3427 will not negotiate padding with 0.4.1.x-alpha relays (or 0.4.0.x
3428 relays). Fixes bug 31356; bugfix on 0.4.1.1-alpha.
3430 o Minor bugfixes (circuit padding):
3431 - Ignore non-padding cells on padding circuits. This addresses
3432 various warning messages from subsystems that were not expecting
3433 padding circuits. Fixes bug 30942; bugfix on 0.4.1.1-alpha.
3435 o Minor bugfixes (clock skew detection):
3436 - Don't believe clock skew results from NETINFO cells that appear to
3437 arrive before we sent the VERSIONS cells they are responding to.
3438 Previously, we would accept them up to 3 minutes "in the past".
3439 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
3441 o Minor bugfixes (compatibility, standards compliance):
3442 - Fix a bug that would invoke undefined behavior on certain
3443 operating systems when trying to asprintf() a string exactly
3444 INT_MAX bytes long. We don't believe this is exploitable, but it's
3445 better to fix it anyway. Fixes bug 31001; bugfix on 0.2.2.11-alpha.
3446 Found and fixed by Tobias Stoeckmann.
3448 o Minor bugfixes (compilation warning):
3449 - Fix a compilation warning on Windows about casting a function
3450 pointer for GetTickCount64(). Fixes bug 31374; bugfix
3453 o Minor bugfixes (compilation):
3454 - Avoid using labs() on time_t, which can cause compilation warnings
3455 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
3457 o Minor bugfixes (distribution):
3458 - Do not ship any temporary files found in the
3459 scripts/maint/practracker directory. Fixes bug 31311; bugfix
3462 o Testing (continuous integration):
3463 - In Travis, make stem log a controller trace to the console, and
3464 tail stem's tor log after failure. Closes ticket 30591.
3465 - In Travis, only run the stem tests that use a tor binary. Closes
3469 Changes in version 0.4.1.4-rc - 2019-07-25
3470 Tor 0.4.1.4-rc fixes a few bugs from previous versions of Tor, and
3471 updates to a new list of fallback directories. If no new bugs are
3472 found, the next release in the 0.4.1.x serious should be stable.
3474 o Major bugfixes (circuit build, guard):
3475 - When considering upgrading circuits from "waiting for guard" to
3476 "open", always ignore circuits that are marked for close. Otherwise,
3477 we can end up in the situation where a subsystem is notified that
3478 a closing circuit has just opened, leading to undesirable
3479 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
3481 o Minor features (continuous integration):
3482 - Our Travis configuration now uses Chutney to run some network
3483 integration tests automatically. Closes ticket 29280.
3485 o Minor features (fallback directory list):
3486 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
3487 in December 2018 (of which ~122 were still functional), with a
3488 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
3489 in June 2019. Closes ticket 28795.
3491 o Minor bugfixes (circuit padding):
3492 - On relays, properly check that a padding machine is absent before
3493 logging a warning about it being absent. Fixes bug 30649; bugfix
3495 - Add two NULL checks in unreachable places to silence Coverity (CID
3496 144729 and 1447291) and better future-proof ourselves. Fixes bug
3497 31024; bugfix on 0.4.1.1-alpha.
3499 o Minor bugfixes (crash on exit):
3500 - Avoid a set of possible code paths that could try to use freed
3501 memory in routerlist_free() while Tor was exiting. Fixes bug
3502 31003; bugfix on 0.1.2.2-alpha.
3504 o Minor bugfixes (logging):
3505 - Fix a conflict between the flag used for messaging-domain log
3506 messages, and the LD_NO_MOCK testing flag. Fixes bug 31080; bugfix
3509 o Minor bugfixes (memory leaks):
3510 - Fix a trivial memory leak when parsing an invalid value from a
3511 download schedule in the configuration. Fixes bug 30894; bugfix
3514 o Code simplification and refactoring:
3515 - Remove some dead code from circpad_machine_remove_token() to fix
3516 some Coverity warnings (CID 1447298). Fixes bug 31027; bugfix
3520 Changes in version 0.4.1.3-alpha - 2019-06-25
3521 Tor 0.4.1.3-alpha resolves numerous bugs left over from the previous
3522 alpha, most of them from earlier release series.
3524 o Major bugfixes (Onion service reachability):
3525 - Properly clean up the introduction point map when circuits change
3526 purpose from onion service circuits to pathbias, measurement, or
3527 other circuit types. This should fix some service-side instances
3528 of introduction point failure. Fixes bug 29034; bugfix
3531 o Minor features (geoip):
3532 - Update geoip and geoip6 to the June 10 2019 Maxmind GeoLite2
3533 Country database. Closes ticket 30852.
3535 o Minor features (logging):
3536 - Give a more useful assertion failure message if we think we have
3537 minherit() but we fail to make a region non-inheritable. Give a
3538 compile-time warning if our support for minherit() is incomplete.
3539 Closes ticket 30686.
3541 o Minor bugfixes (circuit isolation):
3542 - Fix a logic error that prevented the SessionGroup sub-option from
3543 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
3545 o Minor bugfixes (continuous integration):
3546 - Allow the test-stem job to fail in Travis, because it sometimes
3547 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
3548 - Skip test_rebind on macOS in Travis, because it is unreliable on
3549 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3550 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
3551 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3553 o Minor bugfixes (directory authorities):
3554 - Stop crashing after parsing an unknown descriptor purpose
3555 annotation. We think this bug can only be triggered by modifying a
3556 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
3558 o Minor bugfixes (pluggable transports):
3559 - When running as a bridge with pluggable transports, always publish
3560 pluggable transport information in our extrainfo descriptor, even
3561 if ExtraInfoStatistics is 0. This information is needed by
3562 BridgeDB. Fixes bug 30956; bugfix on 0.4.1.1-alpha.
3565 - Mention URLs for Travis/Appveyor/Jenkins in ReleasingTor.md.
3566 Closes ticket 30630.
3569 Changes in version 0.4.1.2-alpha - 2019-06-06
3570 Tor 0.4.1.2-alpha resolves numerous bugs--some of them from the
3571 previous alpha, and some much older. It also contains minor testing
3572 improvements, and an improvement to the security of our authenticated
3573 SENDME implementation.
3575 o Major bugfixes (bridges):
3576 - Consider our directory information to have changed when our list
3577 of bridges changes. Previously, Tor would not re-compute the
3578 status of its directory information when bridges changed, and
3579 therefore would not realize that it was no longer able to build
3580 circuits. Fixes part of bug 29875.
3581 - Do not count previously configured working bridges towards our
3582 total of working bridges. Previously, when Tor's list of bridges
3583 changed, it would think that the old bridges were still usable,
3584 and delay fetching router descriptors for the new ones. Fixes part
3585 of bug 29875; bugfix on 0.3.0.1-alpha.
3587 o Major bugfixes (flow control, SENDME):
3588 - Decrement the stream-level package window after packaging a cell.
3589 Previously, it was done inside a log_debug() call, meaning that if
3590 debug logs were not enabled, the decrement would never happen, and
3591 thus the window would be out of sync with the other end point.
3592 Fixes bug 30628; bugfix on 0.4.1.1-alpha.
3594 o Major bugfixes (onion service reachability):
3595 - Properly clean up the introduction point map and associated state
3596 when circuits change purpose from onion service circuits to
3597 pathbias, measurement, or other circuit types. This may fix some
3598 instances of introduction point failure. Fixes bug 29034; bugfix
3601 o Minor features (authenticated SENDME):
3602 - Ensure that there is enough randomness on every circuit to prevent
3603 an attacker from successfully predicting the hashes they will need
3604 to include in authenticated SENDME cells. At a random interval, if
3605 we have not sent randomness already, we now leave some extra space
3606 at the end of a cell that we can fill with random bytes. Closes
3609 o Minor features (continuous integration):
3610 - When running coverage builds on Travis, we now set
3611 TOR_TEST_RNG_SEED, to avoid RNG-based coverage differences. Part
3614 o Minor features (maintenance):
3615 - Add a new "make autostyle" target that developers can use to apply
3616 all automatic Tor style and consistency conversions to the
3617 codebase. Closes ticket 30539.
3619 o Minor features (testing):
3620 - The circuitpadding tests now use a reproducible RNG implementation,
3621 so that if a test fails, we can learn why. Part of ticket 28878.
3622 - Tor's tests now support an environment variable, TOR_TEST_RNG_SEED,
3623 to set the RNG seed for tests that use a reproducible RNG. Part of
3625 - When running tests in coverage mode, take additional care to make
3626 our coverage deterministic, so that we can accurately track
3627 changes in code coverage. Closes ticket 30519.
3629 o Minor bugfixes (configuration, proxies):
3630 - Fix a bug that prevented us from supporting SOCKS5 proxies that
3631 want authentication along with configured (but unused!)
3632 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
3634 o Minor bugfixes (controller):
3635 - POSTDESCRIPTOR requests should work again. Previously, they were
3636 broken if a "purpose=" flag was specified. Fixes bug 30580; bugfix
3638 - Repair the HSFETCH command so that it works again. Previously, it
3639 expected a body when it shouldn't have. Fixes bug 30646; bugfix
3642 o Minor bugfixes (developer tooling):
3643 - Fix pre-push hook to allow fixup and squash commits when pushing
3644 to non-upstream git remote. Fixes bug 30286; bugfix
3647 o Minor bugfixes (directory authority):
3648 - Move the "bandwidth-file-headers" line in directory authority
3649 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
3652 o Minor bugfixes (NetBSD):
3653 - Fix usage of minherit() on NetBSD and other platforms that define
3654 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
3655 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
3657 o Minor bugfixes (out-of-memory handler):
3658 - When purging the DNS cache because of an out-of-memory condition,
3659 try purging just the older entries at first. Previously, we would
3660 always purge the whole thing. Fixes bug 29617; bugfix
3663 o Minor bugfixes (portability):
3664 - Avoid crashing in our tor_vasprintf() implementation on systems
3665 that define neither vasprintf() nor _vscprintf(). (This bug has
3666 been here long enough that we question whether people are running
3667 Tor on such systems, but we're applying the fix out of caution.)
3668 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
3671 o Minor bugfixes (shutdown, libevent, memory safety):
3672 - Avoid use-after-free bugs when shutting down, by making sure that
3673 we shut down libevent only after shutting down all of its users.
3674 We believe these are harmless in practice, since they only occur
3675 on the shutdown path, and do not involve any attacker-controlled
3676 data. Fixes bug 30629; bugfix on 0.4.1.1-alpha.
3678 o Minor bugfixes (static analysis):
3679 - Fix several spurious Coverity warnings about the unit tests, to
3680 lower our chances of missing real warnings in the future. Fixes
3681 bug 30150; bugfix on 0.3.5.1-alpha and various other Tor versions.
3684 - Specify torrc paths (with empty files) when launching tor in
3685 integration tests; refrain from reading user and system torrcs.
3686 Resolves issue 29702.
3689 Changes in version 0.4.1.1-alpha - 2019-05-22
3690 This is the first alpha in the 0.4.1.x series. It introduces
3691 lightweight circuit padding to make some onion-service circuits harder
3692 to distinguish, includes a new "authenticated SENDME" feature to make
3693 certain denial-of-service attacks more difficult, and improves
3694 performance in several areas.
3696 o Major features (circuit padding):
3697 - Onion service clients now add padding cells at the start of their
3698 INTRODUCE and RENDEZVOUS circuits, to make those circuits' traffic
3699 look more like general purpose Exit traffic. The overhead for this
3700 is 2 extra cells in each direction for RENDEZVOUS circuits, and 1
3701 extra upstream cell and 10 downstream cells for INTRODUCE
3702 circuits. This feature is only enabled when also supported by the
3703 circuit's middle node. (Clients may specify fixed middle nodes
3704 with the MiddleNodes option, and may force-disable this feature
3705 with the CircuitPadding option.) Closes ticket 28634.
3707 o Major features (code organization):
3708 - Tor now includes a generic publish-subscribe message-passing
3709 subsystem that we can use to organize intermodule dependencies. We
3710 hope to use this to reduce dependencies between modules that don't
3711 need to be related, and to generally simplify our codebase. Closes
3714 o Major features (controller protocol):
3715 - Controller commands are now parsed using a generalized parsing
3716 subsystem. Previously, each controller command was responsible for
3717 parsing its own input, which led to strange inconsistencies.
3718 Closes ticket 30091.
3720 o Major features (flow control):
3721 - Implement authenticated SENDMEs as detailed in proposal 289. A
3722 SENDME cell now includes the digest of the traffic that it
3723 acknowledges, so that once an end point receives the SENDME, it
3724 can confirm the other side's knowledge of the previous cells that
3725 were sent, and prevent certain types of denial-of-service attacks.
3726 This behavior is controlled by two new consensus parameters: see
3727 the proposal for more details. Fixes ticket 26288.
3729 o Major features (performance):
3730 - Our node selection algorithm now excludes nodes in linear time.
3731 Previously, the algorithm was quadratic, which could slow down
3732 heavily used onion services. Closes ticket 30307.
3734 o Major features (performance, RNG):
3735 - Tor now constructs a fast secure pseudorandom number generator for
3736 each thread, to use when performance is critical. This PRNG is
3737 based on AES-CTR, using a buffering construction similar to
3738 libottery and the (newer) OpenBSD arc4random() code. It
3739 outperforms OpenSSL 1.1.1a's CSPRNG by roughly a factor of 100 for
3740 small outputs. Although we believe it to be cryptographically
3741 strong, we are only using it when necessary for performance.
3742 Implements tickets 29023 and 29536.
3744 o Major bugfixes (onion service v3):
3745 - Fix an unreachable bug in which an introduction point could try to
3746 send an INTRODUCE_ACK with a status code that Trunnel would refuse
3747 to encode, leading the relay to assert(). We've consolidated the
3748 ABI values into Trunnel now. Fixes bug 30454; bugfix
3750 - Clients can now handle unknown status codes from INTRODUCE_ACK
3751 cells. (The NACK behavior will stay the same.) This will allow us
3752 to extend status codes in the future without breaking the normal
3753 client behavior. Fixes another part of bug 30454; bugfix
3756 o Minor features (circuit padding):
3757 - We now use a fast PRNG when scheduling circuit padding. Part of
3759 - Allow the padding machine designer to pick the edges of their
3760 histogram instead of trying to compute them automatically using an
3761 exponential formula. Resolves some undefined behavior in the case
3762 of small histograms and allows greater flexibility on machine
3763 design. Closes ticket 29298; bugfix on 0.4.0.1-alpha.
3764 - Allow circuit padding machines to hold a circuit open until they
3765 are done padding it. Closes ticket 28780.
3767 o Minor features (compile-time modules):
3768 - Add a "--list-modules" command to print a list of which compile-
3769 time modules are enabled. Closes ticket 30452.
3771 o Minor features (continuous integration):
3772 - Remove sudo configuration lines from .travis.yml as they are no
3773 longer needed with current Travis build environment. Resolves
3775 - In Travis, show stem's tor log after failure. Closes ticket 30234.
3777 o Minor features (controller):
3778 - Add onion service version 3 support to the HSFETCH command.
3779 Previously, only version 2 onion services were supported. Closes
3780 ticket 25417. Patch by Neel Chauhan.
3782 o Minor features (debugging):
3783 - Introduce tor_assertf() and tor_assertf_nonfatal() to enable
3784 logging of additional information during assert failure. Now we
3785 can use format strings to include information for trouble
3786 shooting. Resolves ticket 29662.
3788 o Minor features (defense in depth):
3789 - In smartlist_remove_keeporder(), set unused pointers to NULL, in
3790 case a bug causes them to be used later. Closes ticket 30176.
3791 Patch from Tobias Stoeckmann.
3792 - Tor now uses a cryptographically strong PRNG even for decisions
3793 that we do not believe are security-sensitive. Previously, for
3794 performance reasons, we had used a trivially predictable linear
3795 congruential generator algorithm for certain load-balancing and
3796 statistical sampling decisions. Now we use our fast RNG in those
3797 cases. Closes ticket 29542.
3799 o Minor features (developer tools):
3800 - Tor's "practracker" test script now checks for files and functions
3801 that seem too long and complicated. Existing overlong functions
3802 and files are accepted for now, but should eventually be
3803 refactored. Closes ticket 29221.
3804 - Add some scripts used for git maintenance to scripts/git. Closes
3806 - Call practracker from pre-push and pre-commit git hooks to let
3807 developers know if they made any code style violations. Closes
3809 - Add a script to check that each header has a well-formed and
3810 unique guard macro. Closes ticket 29756.
3812 o Minor features (geoip):
3813 - Update geoip and geoip6 to the May 13 2019 Maxmind GeoLite2
3814 Country database. Closes ticket 30522.
3816 o Minor features (HTTP tunnel):
3817 - Return an informative web page when the HTTPTunnelPort is used as
3818 an HTTP proxy. Closes ticket 27821, patch by "eighthave".
3820 o Minor features (IPv6, v3 onion services):
3821 - Make v3 onion services put IPv6 addresses in service descriptors.
3822 Before this change, service descriptors only contained IPv4
3823 addresses. Implements 26992.
3825 o Minor features (modularity):
3826 - The "--disable-module-dirauth" compile-time option now disables
3827 even more dirauth-only code. Closes ticket 30345.
3829 o Minor features (performance):
3830 - Use OpenSSL's implementations of SHA3 when available (in OpenSSL
3831 1.1.1 and later), since they tend to be faster than tiny-keccak.
3832 Closes ticket 28837.
3834 o Minor features (testing):
3835 - Tor's unit test code now contains helper functions to replace the
3836 PRNG with a deterministic or reproducible version for testing.
3837 Previously, various tests implemented this in various ways.
3838 Implements ticket 29732.
3839 - We now have a script, cov-test-determinism.sh, to identify places
3840 where our unit test coverage has become nondeterministic. Closes
3842 - Check that representative subsets of values of `int` and `unsigned
3843 int` can be represented by `void *`. Resolves issue 29537.
3845 o Minor bugfixes (bridge authority):
3846 - Bridge authorities now set bridges as running or non-running when
3847 about to dump their status to a file. Previously, they set bridges
3848 as running in response to a GETINFO command, but those shouldn't
3849 modify data structures. Fixes bug 24490; bugfix on 0.2.0.13-alpha.
3850 Patch by Neel Chauhan.
3852 o Minor bugfixes (channel padding statistics):
3853 - Channel padding write totals and padding-enabled totals are now
3854 counted properly in relay extrainfo descriptors. Fixes bug 29231;
3855 bugfix on 0.3.1.1-alpha.
3857 o Minor bugfixes (circuit padding):
3858 - Add a "CircuitPadding" torrc option to disable circuit padding.
3859 Fixes bug 28693; bugfix on 0.4.0.1-alpha.
3860 - Allow circuit padding machines to specify that they do not
3861 contribute much overhead, and provide consensus flags and torrc
3862 options to force clients to only use these low overhead machines.
3863 Fixes bug 29203; bugfix on 0.4.0.1-alpha.
3864 - Provide a consensus parameter to fully disable circuit padding, to
3865 be used in emergency network overload situations. Fixes bug 30173;
3866 bugfix on 0.4.0.1-alpha.
3867 - The circuit padding subsystem will no longer schedule padding if
3868 dormant mode is enabled. Fixes bug 28636; bugfix on 0.4.0.1-alpha.
3869 - Inspect a circuit-level cell queue before sending padding, to
3870 avoid sending padding while too much data is already queued. Fixes
3871 bug 29204; bugfix on 0.4.0.1-alpha.
3872 - Avoid calling monotime_absolute_usec() in circuit padding machines
3873 that do not use token removal or circuit RTT estimation. Fixes bug
3874 29085; bugfix on 0.4.0.1-alpha.
3876 o Minor bugfixes (compilation, unusual configurations):
3877 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
3878 due to missing declarations of abort(), and prevent other such
3879 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
3881 o Minor bugfixes (controller protocol):
3882 - Teach the controller parser to distinguish an object preceded by
3883 an argument list from one without. Previously, it couldn't
3884 distinguish an argument list from the first line of a multiline
3885 object. Fixes bug 29984; bugfix on 0.2.3.8-alpha.
3887 o Minor bugfixes (directory authority, ipv6):
3888 - Directory authorities with IPv6 support now always mark themselves
3889 as reachable via IPv6. Fixes bug 24338; bugfix on 0.2.4.1-alpha.
3890 Patch by Neel Chauhan.
3892 o Minor bugfixes (documentation):
3893 - Improve the documentation for using MapAddress with ".exit". Fixes
3894 bug 30109; bugfix on 0.1.0.1-rc.
3895 - Improve the monotonic time module and function documentation to
3896 explain what "monotonic" actually means, and document some results
3897 that have surprised people. Fixes bug 29640; bugfix
3899 - Use proper formatting when providing an example on quoting options
3900 that contain whitespace. Fixes bug 29635; bugfix on 0.2.3.18-rc.
3902 o Minor bugfixes (logging):
3903 - Do not log a warning when running with an OpenSSL version other
3904 than the one Tor was compiled with, if the two versions should be
3905 compatible. Previously, we would warn whenever the version was
3906 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
3907 - Warn operators when the MyFamily option is set but ContactInfo is
3908 missing, as the latter should be set too. Fixes bug 25110; bugfix
3911 o Minor bugfixes (memory leak):
3912 - Avoid a minor memory leak that could occur on relays when failing
3913 to create a "keys" directory. Fixes bug 30148; bugfix
3916 o Minor bugfixes (onion services):
3917 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
3918 implemenation) when failing to load an onion service client
3919 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
3920 - When refusing to launch a controller's HSFETCH request because of
3921 rate-limiting, respond to the controller with a new response,
3922 "QUERY_RATE_LIMITED". Previously, we would log QUERY_NO_HSDIR for
3923 this case. Fixes bug 28269; bugfix on 0.3.1.1-alpha. Patch by
3925 - When relaunching a circuit to a rendezvous service, mark the
3926 circuit as needing high-uptime routers as appropriate. Fixes bug
3927 17357; bugfix on 0.1.0.1-rc. Patch by Neel Chauhan.
3928 - Stop ignoring IPv6 link specifiers sent to v3 onion services.
3929 (IPv6 support for v3 onion services is still incomplete: see
3930 ticket 23493 for details.) Fixes bug 23588; bugfix on
3931 0.3.2.1-alpha. Patch by Neel Chauhan.
3933 o Minor bugfixes (onion services, performance):
3934 - When building circuits to onion services, call tor_addr_parse()
3935 less often. Previously, we called tor_addr_parse() in
3936 circuit_is_acceptable() even if its output wasn't used. This
3937 change should improve performance when building circuits. Fixes
3938 bug 22210; bugfix on 0.2.8.12. Patch by Neel Chauhan.
3940 o Minor bugfixes (performance):
3941 - When checking whether a node is a bridge, use a fast check to make
3942 sure that its identity is set. Previously, we used a constant-time
3943 check, which is not necessary in this case. Fixes bug 30308;
3944 bugfix on 0.3.5.1-alpha.
3946 o Minor bugfixes (pluggable transports):
3947 - Tor now sets TOR_PT_EXIT_ON_STDIN_CLOSE=1 for client transports as
3948 well as servers. Fixes bug 25614; bugfix on 0.2.7.1-alpha.
3950 o Minor bugfixes (probability distributions):
3951 - Refactor and improve parts of the probability distribution code
3952 that made Coverity complain. Fixes bug 29805; bugfix
3955 o Minor bugfixes (python):
3956 - Stop assuming that /usr/bin/python3 exists. For scripts that work
3957 with python2, use /usr/bin/python. Otherwise, use /usr/bin/env
3958 python3. Fixes bug 29913; bugfix on 0.2.5.3-alpha.
3960 o Minor bugfixes (relay):
3961 - When running as a relay, if IPv6Exit is set to 1 while ExitRelay
3962 is auto, act as if ExitRelay is 1. Previously, we would ignore
3963 IPv6Exit if ExitRelay was 0 or auto. Fixes bug 29613; bugfix on
3964 0.3.5.1-alpha. Patch by Neel Chauhan.
3966 o Minor bugfixes (stats):
3967 - When ExtraInfoStatistics is 0, stop including bandwidth usage
3968 statistics, GeoIPFile hashes, ServerTransportPlugin lines, and
3969 bridge statistics by country in extra-info documents. Fixes bug
3970 29018; bugfix on 0.2.4.1-alpha.
3972 o Minor bugfixes (testing):
3973 - Call setrlimit() to disable core dumps in test_bt_cl.c. Previously
3974 we used `ulimit -c` in test_bt.sh, which violates POSIX shell
3975 compatibility. Fixes bug 29061; bugfix on 0.3.5.1-alpha.
3976 - Fix some incorrect code in the v3 onion service unit tests. Fixes
3977 bug 29243; bugfix on 0.3.2.1-alpha.
3978 - In the "routerkeys/*" tests, check the return values of mkdir()
3979 for possible failures. Fixes bug 29939; bugfix on 0.2.7.2-alpha.
3980 Found by Coverity as CID 1444254.
3981 - Split test_utils_general() into several smaller test functions.
3982 This makes it easier to perform resource deallocation on assert
3983 failure, and fixes Coverity warnings CID 1444117 and CID 1444118.
3984 Fixes bug 29823; bugfix on 0.2.9.1-alpha.
3986 o Minor bugfixes (tor-resolve):
3987 - Fix a memory leak in tor-resolve that could happen if Tor gave it
3988 a malformed SOCKS response. (Memory leaks in tor-resolve don't
3989 actually matter, but it's good to fix them anyway.) Fixes bug
3990 30151; bugfix on 0.4.0.1-alpha.
3992 o Code simplification and refactoring:
3993 - Abstract out the low-level formatting of replies on the control
3994 port. Implements ticket 30007.
3995 - Add several assertions in an attempt to fix some Coverity
3996 warnings. Closes ticket 30149.
3997 - Introduce a connection_dir_buf_add() helper function that checks
3998 for compress_state of dir_connection_t and automatically writes a
3999 string to directory connection with or without compression.
4000 Resolves issue 28816.
4001 - Make the base32_decode() API return the number of bytes written,
4002 for consistency with base64_decode(). Closes ticket 28913.
4003 - Move most relay-only periodic events out of mainloop.c into the
4004 relay subsystem. Closes ticket 30414.
4005 - Refactor and encapsulate parts of the codebase that manipulate
4006 crypt_path_t objects. Resolves issue 30236.
4007 - Refactor several places in our code that Coverity incorrectly
4008 believed might have memory leaks. Closes ticket 30147.
4009 - Remove redundant return values in crypto_format, and the
4010 associated return value checks elsewhere in the code. Make the
4011 implementations in crypto_format consistent, and remove redundant
4012 code. Resolves ticket 29660.
4013 - Rename tor_mem_is_zero() to fast_mem_is_zero(), to emphasize that
4014 it is not a constant-time function. Closes ticket 30309.
4015 - Replace hs_desc_link_specifier_t with link_specifier_t, and remove
4016 all hs_desc_link_specifier_t-specific code. Fixes bug 22781;
4017 bugfix on 0.3.2.1-alpha.
4018 - Simplify v3 onion service link specifier handling code. Fixes bug
4019 23576; bugfix on 0.3.2.1-alpha.
4020 - Split crypto_digest.c into NSS code, OpenSSL code, and shared
4021 code. Resolves ticket 29108.
4022 - Split control.c into several submodules, in preparation for
4023 distributing its current responsibilities throughout the codebase.
4024 Closes ticket 29894.
4025 - Start to move responsibility for knowing about periodic events to
4026 the appropriate subsystems, so that the mainloop doesn't need to
4027 know all the periodic events in the rest of the codebase.
4028 Implements tickets 30293 and 30294.
4031 - Document how to find git commits and tags for bug fixes in
4032 CodingStandards.md. Update some file documentation. Closes
4036 - Remove the linux-tor-prio.sh script from contrib/operator-tools
4037 directory. Resolves issue 29434.
4038 - Remove the obsolete OpenSUSE initscript. Resolves issue 30076.
4039 - Remove the obsolete script at contrib/dist/tor.sh.in. Resolves
4042 o Code simplification and refactoring (shell scripts):
4043 - Clean up many of our shell scripts to fix shellcheck warnings.
4044 These include autogen.sh (ticket 26069), test_keygen.sh (ticket
4045 29062), test_switch_id.sh (ticket 29065), test_rebind.sh (ticket
4046 29063), src/test/fuzz/minimize.sh (ticket 30079), test_rust.sh
4047 (ticket 29064), torify (ticket 29070), asciidoc-helper.sh (29926),
4048 fuzz_multi.sh (30077), fuzz_static_testcases.sh (ticket 29059),
4049 nagios-check-tor-authority-cert (ticket 29071),
4050 src/test/fuzz/fixup_filenames.sh (ticket 30078), test-network.sh
4051 (ticket 29060), test_key_expiration.sh (ticket 30002),
4052 zero_length_keys.sh (ticket 29068), and test_workqueue_*.sh
4055 o Testing (chutney):
4056 - In "make test-network-all", test IPv6-only v3 single onion
4057 services, using the chutney network single-onion-v23-ipv6-md.
4058 Closes ticket 27251.
4061 Changes in version 0.4.0.5 - 2019-05-02
4062 This is the first stable release in the 0.4.0.x series. It contains
4063 improvements for power management and bootstrap reporting, as well as
4064 preliminary backend support for circuit padding to prevent some kinds
4065 of traffic analysis. It also continues our work in refactoring Tor for
4066 long-term maintainability.
4068 Per our support policy, we will support the 0.4.0.x series for nine
4069 months, or until three months after the release of a stable 0.4.1.x:
4070 whichever is longer. If you need longer-term support, please stick
4071 with 0.3.5.x, which will we plan to support until Feb 2022.
4073 Below are the changes since 0.4.0.4-rc. For a complete list of changes
4074 since 0.3.5.7, see the ReleaseNotes file.
4076 o Minor features (continuous integration):
4077 - In Travis, tell timelimit to use stem's backtrace signals, and
4078 launch python directly from timelimit, so python receives the
4079 signals from timelimit, rather than make. Closes ticket 30117.
4081 o Minor features (diagnostic):
4082 - Add more diagnostic log messages in an attempt to solve the issue
4083 of NUL bytes appearing in a microdescriptor cache. Related to
4086 o Minor features (testing):
4087 - Use the approx_time() function when setting the "Expires" header
4088 in directory replies, to make them more testable. Needed for
4091 o Minor bugfixes (rust):
4092 - Abort on panic in all build profiles, instead of potentially
4093 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
4095 o Minor bugfixes (shellcheck):
4096 - Look for scripts in their correct locations during "make
4097 shellcheck". Previously we had looked in the wrong place during
4098 out-of-tree builds. Fixes bug 30263; bugfix on 0.4.0.1-alpha.
4100 o Minor bugfixes (testing):
4101 - Check the time in the "Expires" header using approx_time(). Fixes
4102 bug 30001; bugfix on 0.4.0.4-rc.
4104 o Minor bugfixes (UI):
4105 - Lower log level of unlink() errors during bootstrap. Fixes bug
4106 29930; bugfix on 0.4.0.1-alpha.
4109 Changes in version 0.4.0.4-rc - 2019-04-11
4110 Tor 0.4.0.4-rc is the first release candidate in its series; it fixes
4111 several bugs from earlier versions, including some that had affected
4112 stability, and one that prevented relays from working with NSS.
4114 o Major bugfixes (NSS, relay):
4115 - When running with NSS, disable TLS 1.2 ciphersuites that use
4116 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
4117 these ciphersuites don't work -- which caused relays to fail to
4118 handshake with one another when these ciphersuites were enabled.
4119 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
4121 o Minor features (bandwidth authority):
4122 - Make bandwidth authorities ignore relays that are reported in the
4123 bandwidth file with the flag "vote=0". This change allows us to
4124 report unmeasured relays for diagnostic reasons without including
4125 their bandwidth in the bandwidth authorities' vote. Closes
4127 - When a directory authority is using a bandwidth file to obtain the
4128 bandwidth values that will be included in the next vote, serve
4129 this bandwidth file at /tor/status-vote/next/bandwidth. Closes
4132 o Minor features (circuit padding):
4133 - Stop warning about undefined behavior in the probability
4134 distribution tests. Float division by zero may technically be
4135 undefined behavior in C, but it's well defined in IEEE 754.
4136 Partial backport of 29298. Closes ticket 29527; bugfix
4139 o Minor features (continuous integration):
4140 - On Travis Rust builds, cleanup Rust registry and refrain from
4141 caching the "target/" directory to speed up builds. Resolves
4144 o Minor features (dormant mode):
4145 - Add a DormantCanceledByStartup option to tell Tor that it should
4146 treat a startup event as cancelling any previous dormant state.
4147 Integrators should use this option with caution: it should only be
4148 used if Tor is being started because of something that the user
4149 did, and not if Tor is being automatically started in the
4150 background. Closes ticket 29357.
4152 o Minor features (geoip):
4153 - Update geoip and geoip6 to the April 2 2019 Maxmind GeoLite2
4154 Country database. Closes ticket 29992.
4156 o Minor features (NSS, diagnostic):
4157 - Try to log an error from NSS (if there is any) and a more useful
4158 description of our situation if we are using NSS and a call to
4159 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
4161 o Minor bugfixes (security):
4162 - Fix a potential double free bug when reading huge bandwidth files.
4163 The issue is not exploitable in the current Tor network because
4164 the vulnerable code is only reached when directory authorities
4165 read bandwidth files, but bandwidth files come from a trusted
4166 source (usually the authorities themselves). Furthermore, the
4167 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
4168 which are not used by any of the current authorities. Fixes bug
4169 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
4171 - Verify in more places that we are not about to create a buffer
4172 with more than INT_MAX bytes, to avoid possible OOB access in the
4173 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
4174 fixed by Tobias Stoeckmann.
4176 o Minor bugfix (continuous integration):
4177 - Reset coverage state on disk after Travis CI has finished. This
4178 should prevent future coverage merge errors from causing the test
4179 suite for the "process" subsystem to fail. The process subsystem
4180 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
4182 - Terminate test-stem if it takes more than 9.5 minutes to run.
4183 (Travis terminates the job after 10 minutes of no output.)
4184 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
4186 o Minor bugfixes (bootstrap reporting):
4187 - During bootstrap reporting, correctly distinguish pluggable
4188 transports from plain proxies. Fixes bug 28925; bugfix
4191 o Minor bugfixes (C correctness):
4192 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
4193 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
4196 o Minor bugfixes (circuitpadding testing):
4197 - Minor tweaks to avoid rare test failures related to timers and
4198 monotonic time. Fixes bug 29500; bugfix on 0.4.0.1-alpha.
4200 o Minor bugfixes (directory authorities):
4201 - Actually include the bandwidth-file-digest line in directory
4202 authority votes. Fixes bug 29959; bugfix on 0.4.0.2-alpha.
4204 o Minor bugfixes (logging):
4205 - On Windows, when errors cause us to reload a consensus from disk,
4206 tell the user that we are retrying at log level "notice".
4207 Previously we only logged this information at "info", which was
4208 confusing because the errors themselves were logged at "warning".
4209 Improves previous fix for 28614. Fixes bug 30004; bugfix
4212 o Minor bugfixes (pluggable transports):
4213 - Restore old behavior when it comes to discovering the path of a
4214 given Pluggable Transport executable file. A change in
4215 0.4.0.1-alpha had broken this behavior on paths containing a
4216 space. Fixes bug 29874; bugfix on 0.4.0.1-alpha.
4218 o Minor bugfixes (testing):
4219 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
4220 recent test-network.sh to use new chutney features in CI. Fixes
4221 bug 29703; bugfix on 0.2.9.1-alpha.
4222 - Fix a test failure on Windows caused by an unexpected "BUG"
4223 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
4226 o Minor bugfixes (TLS protocol):
4227 - When classifying a client's selection of TLS ciphers, if the
4228 client ciphers are not yet available, do not cache the result.
4229 Previously, we had cached the unavailability of the cipher list
4230 and never looked again, which in turn led us to assume that the
4231 client only supported the ancient V1 link protocol. This, in turn,
4232 was causing Stem integration tests to stall in some cases. Fixes
4233 bug 30021; bugfix on 0.2.4.8-alpha.
4235 o Code simplification and refactoring:
4236 - Introduce a connection_dir_buf_add() helper function that detects
4237 whether compression is in use, and adds a string accordingly.
4238 Resolves issue 28816.
4239 - Refactor handle_get_next_bandwidth() to use
4240 connection_dir_buf_add(). Implements ticket 29897.
4243 - Clarify that Tor performs stream isolation among *Port listeners
4244 by default. Resolves issue 29121.
4247 Changes in version 0.4.0.3-alpha - 2019-03-22
4248 Tor 0.4.0.3-alpha is the third in its series; it fixes several small
4249 bugs from earlier versions.
4251 o Minor features (address selection):
4252 - Treat the subnet 100.64.0.0/10 as public for some purposes;
4253 private for others. This subnet is the RFC 6598 (Carrier Grade
4254 NAT) IP range, and is deployed by many ISPs as an alternative to
4255 RFC 1918 that does not break existing internal networks. Tor now
4256 blocks SOCKS and control ports on these addresses and warns users
4257 if client ports or ExtORPorts are listening on a RFC 6598 address.
4258 Closes ticket 28525. Patch by Neel Chauhan.
4260 o Minor features (geoip):
4261 - Update geoip and geoip6 to the March 4 2019 Maxmind GeoLite2
4262 Country database. Closes ticket 29666.
4264 o Minor bugfixes (circuitpadding):
4265 - Inspect the circuit-level cell queue before sending padding, to
4266 avoid sending padding when too much data is queued. Fixes bug
4267 29204; bugfix on 0.4.0.1-alpha.
4269 o Minor bugfixes (logging):
4270 - Correct a misleading error message when IPv4Only or IPv6Only is
4271 used but the resolved address can not be interpreted as an address
4272 of the specified IP version. Fixes bug 13221; bugfix on
4273 0.2.3.9-alpha. Patch from Kris Katterjohn.
4274 - Log the correct port number for listening sockets when "auto" is
4275 used to let Tor pick the port number. Previously, port 0 was
4276 logged instead of the actual port number. Fixes bug 29144; bugfix
4277 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
4278 - Stop logging a BUG() warning when Tor is waiting for exit
4279 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
4281 o Minor bugfixes (memory management):
4282 - Refactor the shared random state's memory management so that it
4283 actually takes ownership of the shared random value pointers.
4284 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
4286 o Minor bugfixes (memory management, testing):
4287 - Stop leaking parts of the shared random state in the shared-random
4288 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
4290 o Minor bugfixes (pluggable transports):
4291 - Fix an assertion failure crash bug when a pluggable transport is
4292 terminated during the bootstrap phase. Fixes bug 29562; bugfix
4295 o Minor bugfixes (Rust, protover):
4296 - Add a missing "Padding" value to the Rust implementation of
4297 protover. Fixes bug 29631; bugfix on 0.4.0.1-alpha.
4299 o Minor bugfixes (single onion services):
4300 - Allow connections to single onion services to remain idle without
4301 being disconnected. Previously, relays acting as rendezvous points
4302 for single onion services were mistakenly closing idle rendezvous
4303 circuits after 60 seconds, thinking that they were unused
4304 directory-fetching circuits that had served their purpose. Fixes
4305 bug 29665; bugfix on 0.2.1.26.
4307 o Minor bugfixes (stats):
4308 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
4309 relay and bridge extra-info documents. Fixes bug 29017; bugfix
4312 o Minor bugfixes (testing):
4313 - Downgrade some LOG_ERR messages in the address/* tests to
4314 warnings. The LOG_ERR messages were occurring when we had no
4315 configured network. We were failing the unit tests, because we
4316 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
4317 29530; bugfix on 0.3.5.8.
4318 - Fix our gcov wrapper script to look for object files at the
4319 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
4320 - Decrease the false positive rate of stochastic probability
4321 distribution tests. Fixes bug 29693; bugfix on 0.4.0.1-alpha.
4323 o Minor bugfixes (Windows, CI):
4324 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
4325 Windows Server 2012 R2 job. The remaining 2 jobs still provide
4326 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
4327 fast_finish, so failed jobs terminate the build immediately. Fixes
4328 bug 29601; bugfix on 0.3.5.4-alpha.
4331 Changes in version 0.3.5.8 - 2019-02-21
4332 Tor 0.3.5.8 backports several fixes from later releases, including fixes
4333 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
4336 It also includes a fix for a medium-severity security bug affecting Tor
4337 0.3.2.1-alpha and later. All Tor instances running an affected release
4338 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
4340 o Major bugfixes (cell scheduler, KIST, security):
4341 - Make KIST consider the outbuf length when computing what it can
4342 put in the outbuf. Previously, KIST acted as though the outbuf
4343 were empty, which could lead to the outbuf becoming too full. It
4344 is possible that an attacker could exploit this bug to cause a Tor
4345 client or relay to run out of memory and crash. Fixes bug 29168;
4346 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
4347 TROVE-2019-001 and CVE-2019-8955.
4349 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
4350 - Gracefully handle empty username/password fields in SOCKS5
4351 username/password auth message and allow SOCKS5 handshake to
4352 continue. Previously, we had rejected these handshakes, breaking
4353 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
4355 o Minor features (compilation, backport from 0.4.0.2-alpha):
4356 - Compile correctly when OpenSSL is built with engine support
4357 disabled, or with deprecated APIs disabled. Closes ticket 29026.
4358 Patches from "Mangix".
4360 o Minor features (geoip):
4361 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
4362 Country database. Closes ticket 29478.
4364 o Minor features (testing, backport from 0.4.0.2-alpha):
4365 - Treat all unexpected ERR and BUG messages as test failures. Closes
4368 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
4369 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
4370 connection waiting for a descriptor that we actually have in the
4371 cache. It turns out that this can actually happen, though it is
4372 rare. Now, tor will recover and retry the descriptor. Fixes bug
4373 28669; bugfix on 0.3.2.4-alpha.
4375 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
4376 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
4377 IPv6 socket was bound using an address family of AF_INET instead
4378 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
4381 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
4382 - Update Cargo.lock file to match the version made by the latest
4383 version of Rust, so that "make distcheck" will pass again. Fixes
4384 bug 29244; bugfix on 0.3.3.4-alpha.
4386 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
4387 - Select guards even if the consensus has expired, as long as the
4388 consensus is still reasonably live. Fixes bug 24661; bugfix
4391 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
4392 - Compile correctly on OpenBSD; previously, we were missing some
4393 headers required in order to detect it properly. Fixes bug 28938;
4394 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
4396 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
4397 - Describe the contents of the v3 onion service client authorization
4398 files correctly: They hold public keys, not private keys. Fixes
4399 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
4401 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
4402 - Rework rep_hist_log_link_protocol_counts() to iterate through all
4403 link protocol versions when logging incoming/outgoing connection
4404 counts. Tor no longer skips version 5, and we won't have to
4405 remember to update this function when new link protocol version is
4406 developed. Fixes bug 28920; bugfix on 0.2.6.10.
4408 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
4409 - Log more information at "warning" level when unable to read a
4410 private key; log more information at "info" level when unable to
4411 read a public key. We had warnings here before, but they were lost
4412 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
4414 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
4415 - The amount of total available physical memory is now determined
4416 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
4417 when it is defined and a 64-bit variant is not available. Fixes
4418 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
4420 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
4421 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
4422 than one private key for a hidden service. Fixes bug 29040; bugfix
4424 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
4425 "debug" level. Tor used to log it as a warning, which caused very
4426 long log lines to appear for some users. Fixes bug 29135; bugfix
4428 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
4429 as a warning. Instead, log it as a protocol warning, because there
4430 is nothing that relay operators can do to fix it. Fixes bug 29029;
4431 bugfix on 0.2.5.7-rc.
4433 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
4434 - Mark outdated dirservers when Tor only has a reasonably live
4435 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
4437 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
4438 - Detect and suppress "bug" warnings from the util/time test on
4439 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
4440 - Do not log an error-level message if we fail to find an IPv6
4441 network interface from the unit tests. Fixes bug 29160; bugfix
4444 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
4445 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
4446 Some users took this phrasing to mean that the mentioned guard was
4447 under their control or responsibility, which it is not. Fixes bug
4448 28895; bugfix on Tor 0.3.0.1-alpha.
4451 Changes in version 0.3.4.11 - 2019-02-21
4452 Tor 0.3.4.11 is the third stable release in its series. It includes
4453 a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
4454 later. All Tor instances running an affected release should upgrade to
4455 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
4457 o Major bugfixes (cell scheduler, KIST, security):
4458 - Make KIST consider the outbuf length when computing what it can
4459 put in the outbuf. Previously, KIST acted as though the outbuf
4460 were empty, which could lead to the outbuf becoming too full. It
4461 is possible that an attacker could exploit this bug to cause a Tor
4462 client or relay to run out of memory and crash. Fixes bug 29168;
4463 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
4464 TROVE-2019-001 and CVE-2019-8955.
4466 o Minor features (geoip):
4467 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
4468 Country database. Closes ticket 29478.
4470 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
4471 - Update Cargo.lock file to match the version made by the latest
4472 version of Rust, so that "make distcheck" will pass again. Fixes
4473 bug 29244; bugfix on 0.3.3.4-alpha.
4475 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
4476 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
4477 as a warning. Instead, log it as a protocol warning, because there
4478 is nothing that relay operators can do to fix it. Fixes bug 29029;
4479 bugfix on 0.2.5.7-rc.
4482 Changes in version 0.3.3.12 - 2019-02-21
4483 Tor 0.3.3.12 fixes a medium-severity security bug affecting Tor
4484 0.3.2.1-alpha and later. All Tor instances running an affected release
4485 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
4487 This release marks the end of support for the Tor 0.3.3.x series. We
4488 recommend that users switch to either the Tor 0.3.4 series (supported
4489 until at least 10 June 2019), or the Tor 0.3.5 series, which will
4490 receive long-term support until at least 1 Feb 2022.
4492 o Major bugfixes (cell scheduler, KIST, security):
4493 - Make KIST consider the outbuf length when computing what it can
4494 put in the outbuf. Previously, KIST acted as though the outbuf
4495 were empty, which could lead to the outbuf becoming too full. It
4496 is possible that an attacker could exploit this bug to cause a Tor
4497 client or relay to run out of memory and crash. Fixes bug 29168;
4498 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
4499 TROVE-2019-001 and CVE-2019-8955.
4501 o Minor features (geoip):
4502 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
4503 Country database. Closes ticket 29478.
4505 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
4506 - Update Cargo.lock file to match the version made by the latest
4507 version of Rust, so that "make distcheck" will pass again. Fixes
4508 bug 29244; bugfix on 0.3.3.4-alpha.
4510 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
4511 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
4512 as a warning. Instead, log it as a protocol warning, because there
4513 is nothing that relay operators can do to fix it. Fixes bug 29029;
4514 bugfix on 0.2.5.7-rc.
4517 Changes in version 0.4.0.2-alpha - 2019-02-21
4518 Tor 0.4.0.2-alpha is the second alpha in its series; it fixes several
4519 bugs from earlier versions, including several that had broken
4520 backward compatibility.
4522 It also includes a fix for a medium-severity security bug affecting Tor
4523 0.3.2.1-alpha and later. All Tor instances running an affected release
4524 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
4526 o Major bugfixes (cell scheduler, KIST, security):
4527 - Make KIST consider the outbuf length when computing what it can
4528 put in the outbuf. Previously, KIST acted as though the outbuf
4529 were empty, which could lead to the outbuf becoming too full. It
4530 is possible that an attacker could exploit this bug to cause a Tor
4531 client or relay to run out of memory and crash. Fixes bug 29168;
4532 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
4533 TROVE-2019-001 and CVE-2019-8955.
4535 o Major bugfixes (networking):
4536 - Gracefully handle empty username/password fields in SOCKS5
4537 username/password auth messsage and allow SOCKS5 handshake to
4538 continue. Previously, we had rejected these handshakes, breaking
4539 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
4541 o Major bugfixes (windows, startup):
4542 - When reading a consensus file from disk, detect whether it was
4543 written in text mode, and re-read it in text mode if so. Always
4544 write consensus files in binary mode so that we can map them into
4545 memory later. Previously, we had written in text mode, which
4546 confused us when we tried to map the file on windows. Fixes bug
4547 28614; bugfix on 0.4.0.1-alpha.
4549 o Minor features (compilation):
4550 - Compile correctly when OpenSSL is built with engine support
4551 disabled, or with deprecated APIs disabled. Closes ticket 29026.
4552 Patches from "Mangix".
4554 o Minor features (developer tooling):
4555 - Check that bugfix versions in changes files look like Tor versions
4556 from the versions spec. Warn when bugfixes claim to be on a future
4557 release. Closes ticket 27761.
4558 - Provide a git pre-commit hook that disallows committing if we have
4559 any failures in our code and changelog formatting checks. It is
4560 now available in scripts/maint/pre-commit.git-hook. Implements
4563 o Minor features (directory authority):
4564 - When a directory authority is using a bandwidth file to obtain
4565 bandwidth values, include the digest of that file in the vote.
4566 Closes ticket 26698.
4568 o Minor features (geoip):
4569 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
4570 Country database. Closes ticket 29478.
4572 o Minor features (testing):
4573 - Treat all unexpected ERR and BUG messages as test failures. Closes
4576 o Minor bugfixes (build, compatibility, rust):
4577 - Update Cargo.lock file to match the version made by the latest
4578 version of Rust, so that "make distcheck" will pass again. Fixes
4579 bug 29244; bugfix on 0.3.3.4-alpha.
4581 o Minor bugfixes (compilation):
4582 - Fix compilation warnings in test_circuitpadding.c. Fixes bug
4583 29169; bugfix on 0.4.0.1-alpha.
4584 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
4585 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
4587 o Minor bugfixes (documentation):
4588 - Describe the contents of the v3 onion service client authorization
4589 files correctly: They hold public keys, not private keys. Fixes
4590 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
4592 o Minor bugfixes (linux seccomp sandbox):
4593 - Fix startup crash when experimental sandbox support is enabled.
4594 Fixes bug 29150; bugfix on 0.4.0.1-alpha. Patch by Peter Gerber.
4596 o Minor bugfixes (logging):
4597 - Avoid logging that we are relaxing a circuit timeout when that
4598 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
4599 - Log more information at "warning" level when unable to read a
4600 private key; log more information at "info" level when unable to
4601 read a public key. We had warnings here before, but they were lost
4602 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
4604 o Minor bugfixes (misc):
4605 - The amount of total available physical memory is now determined
4606 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
4607 when it is defined and a 64-bit variant is not available. Fixes
4608 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
4610 o Minor bugfixes (onion services):
4611 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
4612 than one private key for a hidden service. Fixes bug 29040; bugfix
4614 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
4615 "debug" level. Tor used to log it as a warning, which caused very
4616 long log lines to appear for some users. Fixes bug 29135; bugfix
4618 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
4619 as a warning. Instead, log it as a protocol warning, because there
4620 is nothing that relay operators can do to fix it. Fixes bug 29029;
4621 bugfix on 0.2.5.7-rc.
4623 o Minor bugfixes (scheduler):
4624 - When re-adding channels to the pending list, check the correct
4625 channel's sched_heap_idx. This issue has had no effect in mainline
4626 Tor, but could have led to bugs down the road in improved versions
4627 of our circuit scheduling code. Fixes bug 29508; bugfix
4630 o Minor bugfixes (tests):
4631 - Fix intermittent failures on an adaptive padding test. Fixes one
4632 case of bug 29122; bugfix on 0.4.0.1-alpha.
4633 - Disable an unstable circuit-padding test that was failing
4634 intermittently because of an ill-defined small histogram. Such
4635 histograms will be allowed again after 29298 is implemented. Fixes
4636 a second case of bug 29122; bugfix on 0.4.0.1-alpha.
4637 - Detect and suppress "bug" warnings from the util/time test on
4638 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
4639 - Do not log an error-level message if we fail to find an IPv6
4640 network interface from the unit tests. Fixes bug 29160; bugfix
4644 - In the manpage entry describing MapAddress torrc setting, use
4645 example IP addresses from ranges specified for use in documentation
4646 by RFC 5737. Resolves issue 28623.
4649 - Remove the old check-tor script. Resolves issue 29072.
4652 Changes in version 0.4.0.1-alpha - 2019-01-18
4653 Tor 0.4.0.1-alpha is the first release in the new 0.4.0.x series. It
4654 introduces improved features for power and bandwidth conservation,
4655 more accurate reporting of bootstrap progress for user interfaces, and
4656 an experimental backend for an exciting new adaptive padding feature.
4657 There is also the usual assortment of bugfixes and minor features, all
4660 o Major features (battery management, client, dormant mode):
4661 - When Tor is running as a client, and it is unused for a long time,
4662 it can now enter a "dormant" state. When Tor is dormant, it avoids
4663 network and CPU activity until it is reawoken either by a user
4664 request or by a controller command. For more information, see the
4665 configuration options starting with "Dormant". Implements tickets
4667 - The client's memory of whether it is "dormant", and how long it
4668 has spent idle, persists across invocations. Implements
4670 - There is a DormantOnFirstStartup option that integrators can use
4671 if they expect that in many cases, Tor will be installed but
4674 o Major features (bootstrap reporting):
4675 - When reporting bootstrap progress, report the first connection
4676 uniformly, regardless of whether it's a connection for building
4677 application circuits. This allows finer-grained reporting of early
4678 progress than previously possible, with the improvements of ticket
4679 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.
4680 - When reporting bootstrap progress, treat connecting to a proxy or
4681 pluggable transport as separate from having successfully used that
4682 proxy or pluggable transport to connect to a relay. Closes tickets
4685 o Major features (circuit padding):
4686 - Implement preliminary support for the circuit padding portion of
4687 Proposal 254. The implementation supports Adaptive Padding (aka
4688 WTF-PAD) state machines for use between experimental clients and
4689 relays. Support is also provided for APE-style state machines that
4690 use probability distributions instead of histograms to specify
4691 inter-packet delay. At the moment, Tor does not provide any
4692 padding state machines that are used in normal operation: for now,
4693 this feature exists solely for experimentation. Closes
4696 o Major features (refactoring):
4697 - Tor now uses an explicit list of its own subsystems when
4698 initializing and shutting down. Previously, these systems were
4699 managed implicitly in various places throughout the codebase.
4700 (There may still be some subsystems using the old system.) Closes
4703 o Minor features (bootstrap reporting):
4704 - When reporting bootstrap progress, stop distinguishing between
4705 situations where only internal paths are available and situations
4706 where external paths are available. Previously, Tor would often
4707 erroneously report that it had only internal paths. Closes
4710 o Minor features (continuous integration):
4711 - Log Python version during each Travis CI job. Resolves
4714 o Minor features (controller):
4715 - Add a DROPOWNERSHIP command to undo the effects of TAKEOWNERSHIP.
4716 Implements ticket 28843.
4718 o Minor features (developer tooling):
4719 - Provide a git hook script to prevent "fixup!" and "squash!"
4720 commits from ending up in the master branch, as scripts/main/pre-
4721 push.git-hook. Closes ticket 27993.
4723 o Minor features (directory authority):
4724 - Directory authorities support a new consensus algorithm, under
4725 which the family lines in microdescriptors are encoded in a
4726 canonical form. This change makes family lines more compressible
4727 in transit, and on the client. Closes ticket 28266; implements
4730 o Minor features (directory authority, relay):
4731 - Authorities now vote on a "StaleDesc" flag to indicate that a
4732 relay's descriptor is so old that the relay should upload again
4733 soon. Relays treat this flag as a signal to upload a new
4734 descriptor. This flag will eventually let us remove the
4735 'published' date from routerstatus entries, and make our consensus
4736 diffs much smaller. Closes ticket 26770; implements proposal 293.
4738 o Minor features (fallback directory mirrors):
4739 - Update the fallback whitelist based on operator opt-ins and opt-
4740 outs. Closes ticket 24805, patch by Phoul.
4742 o Minor features (FreeBSD):
4743 - On FreeBSD-based systems, warn relay operators if the
4744 "net.inet.ip.random_id" sysctl (IP ID randomization) is disabled.
4745 Closes ticket 28518.
4747 o Minor features (HTTP standards compliance):
4748 - Stop sending the header "Content-type: application/octet-stream"
4749 along with transparently compressed documents: this confused
4750 browsers. Closes ticket 28100.
4752 o Minor features (IPv6):
4753 - We add an option ClientAutoIPv6ORPort, to make clients randomly
4754 prefer a node's IPv4 or IPv6 ORPort. The random preference is set
4755 every time a node is loaded from a new consensus or bridge config.
4756 We expect that this option will enable clients to bootstrap more
4757 quickly without having to determine whether they support IPv4,
4758 IPv6, or both. Closes ticket 27490. Patch by Neel Chauhan.
4759 - When using addrs_in_same_network_family(), avoid choosing circuit
4760 paths that pass through the same IPv6 subnet more than once.
4761 Previously, we only checked IPv4 subnets. Closes ticket 24393.
4762 Patch by Neel Chauhan.
4764 o Minor features (log messages):
4765 - Improve log message in v3 onion services that could print out
4766 negative revision counters. Closes ticket 27707. Patch
4769 o Minor features (memory usage):
4770 - Save memory by storing microdescriptor family lists with a more
4771 compact representation. Closes ticket 27359.
4772 - Tor clients now use mmap() to read consensus files from disk, so
4773 that they no longer need keep the full text of a consensus in
4774 memory when parsing it or applying a diff. Closes ticket 27244.
4776 o Minor features (parsing):
4777 - Directory authorities now validate that router descriptors and
4778 ExtraInfo documents are in a valid subset of UTF-8, and reject
4779 them if they are not. Closes ticket 27367.
4781 o Minor features (performance):
4782 - Cache the results of summarize_protocol_flags(), so that we don't
4783 have to parse the same protocol-versions string over and over.
4784 This should save us a huge number of malloc calls on startup, and
4785 may reduce memory fragmentation with some allocators. Closes
4787 - Remove a needless memset() call from get_token_arguments, thereby
4788 speeding up the tokenization of directory objects by about 20%.
4789 Closes ticket 28852.
4790 - Replace parse_short_policy() with a faster implementation, to
4791 improve microdescriptor parsing time. Closes ticket 28853.
4792 - Speed up directory parsing a little by avoiding use of the non-
4793 inlined strcmp_len() function. Closes ticket 28856.
4794 - Speed up microdescriptor parsing by about 30%, to help improve
4795 startup time. Closes ticket 28839.
4797 o Minor features (pluggable transports):
4798 - Add support for emitting STATUS updates to Tor's control port from
4799 a pluggable transport process. Closes ticket 28846.
4800 - Add support for logging to Tor's logging subsystem from a
4801 pluggable transport process. Closes ticket 28180.
4803 o Minor features (process management):
4804 - Add a new process API for handling child processes. This new API
4805 allows Tor to have bi-directional communication with child
4806 processes on both Unix and Windows. Closes ticket 28179.
4807 - Use the subsystem manager to initialize and shut down the process
4808 module. Closes ticket 28847.
4810 o Minor features (relay):
4811 - When listing relay families, list them in canonical form including
4812 the relay's own identity, and try to give a more useful set of
4813 warnings. Part of ticket 28266 and proposal 298.
4815 o Minor features (required protocols):
4816 - Before exiting because of a missing required protocol, Tor will
4817 now check the publication time of the consensus, and not exit
4818 unless the consensus is newer than the Tor program's own release
4819 date. Previously, Tor would not check the consensus publication
4820 time, and so might exit because of a missing protocol that might
4821 no longer be required in a current consensus. Implements proposal
4822 297; closes ticket 27735.
4824 o Minor features (testing):
4825 - Allow a HeartbeatPeriod of less than 30 minutes in testing Tor
4826 networks. Closes ticket 28840. Patch by Rob Jansen.
4828 o Minor bugfixes (client, clock skew):
4829 - Bootstrap successfully even when Tor's clock is behind the clocks
4830 on the authorities. Fixes bug 28591; bugfix on 0.2.0.9-alpha.
4831 - Select guards even if the consensus has expired, as long as the
4832 consensus is still reasonably live. Fixes bug 24661; bugfix
4835 o Minor bugfixes (compilation):
4836 - Compile correctly on OpenBSD; previously, we were missing some
4837 headers required in order to detect it properly. Fixes bug 28938;
4838 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
4840 o Minor bugfixes (directory clients):
4841 - Mark outdated dirservers when Tor only has a reasonably live
4842 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
4844 o Minor bugfixes (directory mirrors):
4845 - Even when a directory mirror's clock is behind the clocks on the
4846 authorities, we now allow the mirror to serve "future"
4847 consensuses. Fixes bug 28654; bugfix on 0.3.0.1-alpha.
4849 o Minor bugfixes (DNS):
4850 - Gracefully handle an empty or absent resolve.conf file by falling
4851 back to using "localhost" as a DNS server (and hoping it works).
4852 Previously, we would just stop running as an exit. Fixes bug
4853 21900; bugfix on 0.2.1.10-alpha.
4855 o Minor bugfixes (guards):
4856 - In count_acceptable_nodes(), the minimum number is now one bridge
4857 or guard node, and two non-guard nodes for a circuit. Previously,
4858 we had added up the sum of all nodes with a descriptor, but that
4859 could cause us to build failing circuits when we had either too
4860 many bridges or not enough guard nodes. Fixes bug 25885; bugfix on
4861 0.2.3.1-alpha. Patch by Neel Chauhan.
4863 o Minor bugfixes (IPv6):
4864 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
4865 IPv6 socket was bound using an address family of AF_INET instead
4866 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
4869 o Minor bugfixes (logging):
4870 - Rework rep_hist_log_link_protocol_counts() to iterate through all
4871 link protocol versions when logging incoming/outgoing connection
4872 counts. Tor no longer skips version 5, and we won't have to
4873 remember to update this function when new link protocol version is
4874 developed. Fixes bug 28920; bugfix on 0.2.6.10.
4876 o Minor bugfixes (networking):
4877 - Introduce additional checks into tor_addr_parse() to reject
4878 certain incorrect inputs that previously were not detected. Fixes
4879 bug 23082; bugfix on 0.2.0.10-alpha.
4881 o Minor bugfixes (onion service v3, client):
4882 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
4883 connection waiting for a descriptor that we actually have in the
4884 cache. It turns out that this can actually happen, though it is
4885 rare. Now, tor will recover and retry the descriptor. Fixes bug
4886 28669; bugfix on 0.3.2.4-alpha.
4888 o Minor bugfixes (periodic events):
4889 - Refrain from calling routerlist_remove_old_routers() from
4890 check_descriptor_callback(). Instead, create a new hourly periodic
4891 event. Fixes bug 27929; bugfix on 0.2.8.1-alpha.
4893 o Minor bugfixes (pluggable transports):
4894 - Make sure that data is continously read from standard output and
4895 standard error pipes of a pluggable transport child-process, to
4896 avoid deadlocking when a pipe's buffer is full. Fixes bug 26360;
4897 bugfix on 0.2.3.6-alpha.
4899 o Minor bugfixes (unit tests):
4900 - Instead of relying on hs_free_all() to clean up all onion service
4901 objects in test_build_descriptors(), we now deallocate them one by
4902 one. This lets Coverity know that we are not leaking memory there
4903 and fixes CID 1442277. Fixes bug 28989; bugfix on 0.3.5.1-alpha.
4905 o Minor bugfixes (usability):
4906 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
4907 Some users took this phrasing to mean that the mentioned guard was
4908 under their control or responsibility, which it is not. Fixes bug
4909 28895; bugfix on Tor 0.3.0.1-alpha.
4911 o Code simplification and refactoring:
4912 - Reimplement NETINFO cell parsing and generation to rely on
4913 trunnel-generated wire format handling code. Closes ticket 27325.
4914 - Remove unnecessary unsafe code from the Rust macro "cstr!". Closes
4916 - Rework SOCKS wire format handling to rely on trunnel-generated
4917 parsing/generation code. Resolves ticket 27620.
4918 - Split out bootstrap progress reporting from control.c into a
4919 separate file. Part of ticket 27402.
4920 - The .may_include files that we use to describe our directory-by-
4921 directory dependency structure now describe a noncircular
4922 dependency graph over the directories that they cover. Our
4923 checkIncludes.py tool now enforces this noncircularity. Closes
4927 - Mention that you cannot add a new onion service if Tor is already
4928 running with Sandbox enabled. Closes ticket 28560.
4929 - Improve ControlPort documentation. Mention that it accepts
4930 address:port pairs, and can be used multiple times. Closes
4932 - Document the exact output of "tor --version". Closes ticket 28889.
4935 - Stop responding to the 'GETINFO status/version/num-concurring' and
4936 'GETINFO status/version/num-versioning' control port commands, as
4937 those were deprecated back in 0.2.0.30. Also stop listing them in
4938 output of 'GETINFO info/names'. Resolves ticket 28757.
4939 - The scripts used to generate and maintain the list of fallback
4940 directories have been extracted into a new "fallback-scripts"
4941 repository. Closes ticket 27914.
4944 - Run shellcheck for scripts in the in scripts/ directory. Closes
4946 - Add unit tests for tokenize_string() and get_next_token()
4947 functions. Resolves ticket 27625.
4949 o Code simplification and refactoring (onion service v3):
4950 - Consolidate the authorized client descriptor cookie computation
4951 code from client and service into one function. Closes
4954 o Code simplification and refactoring (shell scripts):
4955 - Cleanup scan-build.sh to silence shellcheck warnings. Closes
4957 - Fix issues that shellcheck found in chutney-git-bisect.sh.
4958 Resolves ticket 28006.
4959 - Fix issues that shellcheck found in updateRustDependencies.sh.
4960 Resolves ticket 28012.
4961 - Fix shellcheck warnings in cov-diff script. Resolves issue 28009.
4962 - Fix shellcheck warnings in run_calltool.sh. Resolves ticket 28011.
4963 - Fix shellcheck warnings in run_trunnel.sh. Resolves issue 28010.
4964 - Fix shellcheck warnings in scripts/test/coverage. Resolves
4968 Changes in version 0.3.3.11 - 2019-01-07
4969 Tor 0.3.3.11 backports numerous fixes from later versions of Tor.
4970 numerous fixes, including an important fix for anyone using OpenSSL
4971 1.1.1. Anyone running an earlier version of Tor 0.3.3 should upgrade
4972 to this version, or to a later series.
4974 As a reminder, support the Tor 0.3.3 series will end on 22 Feb 2019.
4975 We anticipate that this will be the last release of Tor 0.3.3, unless
4976 some major bug is before then. Some time between now and then, users
4977 should switch to either the Tor 0.3.4 series (supported until at least
4978 10 June 2019), or the Tor 0.3.5 series, which will receive long-term
4979 support until at least 1 Feb 2022.
4981 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
4982 - Fix our usage of named groups when running as a TLS 1.3 client in
4983 OpenSSL 1.1.1. Previously, we only initialized EC groups when
4984 running as a relay, which caused clients to fail to negotiate TLS
4985 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
4988 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
4989 - Fix a use-after-free error that could be caused by passing Tor an
4990 impossible set of options that would fail during options_act().
4991 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
4993 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
4994 - Only run one online rust build in Travis, to reduce network
4995 errors. Skip offline rust builds on Travis for Linux gcc, because
4996 they're redundant. Implements ticket 27252.
4997 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
4998 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
4999 Linux with default settings, because all the non-default builds
5000 use gcc on Linux. Implements ticket 27252.
5002 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
5003 - Use the Travis Homebrew addon to install packages on macOS during
5004 Travis CI. The package list is the same, but the Homebrew addon
5005 does not do a `brew update` by default. Implements ticket 27738.
5007 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
5008 - Replace the 150 fallbacks originally introduced in Tor
5009 0.3.3.1-alpha in January 2018 (of which ~115 were still
5010 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
5011 removed) generated in December 2018. Closes ticket 24803.
5013 o Minor features (geoip):
5014 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
5015 Country database. Closes ticket 29012.
5017 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
5018 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
5019 key export function from handling long labels. When this bug is
5020 detected, Tor will disable TLS 1.3. We recommend upgrading to a
5021 version of OpenSSL without this bug when it becomes available.
5022 Closes ticket 28973.
5024 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
5025 - Update relay descriptor on bandwidth changes only when the uptime
5026 is smaller than 24h, in order to reduce the efficiency of guard
5027 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
5029 o Minor bugfixes (C correctness, backport from 0.3.5.4-alpha):
5030 - Avoid undefined behavior in an end-of-string check when parsing
5031 the BEGIN line in a directory object. Fixes bug 28202; bugfix
5034 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
5035 - Rewrite our assertion macros so that they no longer suppress the
5036 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
5038 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
5039 - Initialize a variable unconditionally in aes_new_cipher(), since
5040 some compilers cannot tell that we always initialize it before
5041 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
5043 o Minor bugfixes (directory authority, backport from 0.3.5.4-alpha):
5044 - Log additional info when we get a relay that shares an ed25519 ID
5045 with a different relay, instead making a BUG() warning. Fixes bug
5046 27800; bugfix on 0.3.2.1-alpha.
5048 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
5049 - When a user requests a group-readable DataDirectory, give it to
5050 them. Previously, when the DataDirectory and the CacheDirectory
5051 were the same, the default setting (0) for
5052 CacheDirectoryGroupReadable would override the setting for
5053 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
5056 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
5057 - When the onion service directory can't be created or has the wrong
5058 permissions, do not log a stack trace. Fixes bug 27335; bugfix
5061 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
5062 - Close all SOCKS request (for the same .onion) if the newly fetched
5063 descriptor is unusable. Before that, we would close only the first
5064 one leaving the other hanging and let to time out by themselves.
5065 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
5067 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
5068 - Don't warn so loudly when Tor is unable to decode an onion
5069 descriptor. This can now happen as a normal use case if a client
5070 gets a descriptor with client authorization but the client is not
5071 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
5073 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
5074 - When deleting an ephemeral onion service (DEL_ONION), do not close
5075 any rendezvous circuits in order to let the existing client
5076 connections finish by themselves or closed by the application. The
5077 HS v2 is doing that already so now we have the same behavior for
5078 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
5080 o Minor bugfixes (HTTP tunnel):
5081 - Fix a bug warning when closing an HTTP tunnel connection due to
5082 an HTTP request we couldn't handle. Fixes bug 26470; bugfix on
5085 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
5086 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
5087 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
5089 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
5090 - Ensure circuitmux queues are empty before scheduling or sending
5091 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
5093 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
5094 - Reject protocol names containing bytes other than alphanumeric
5095 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
5098 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
5099 - Compute protover votes correctly in the rust version of the
5100 protover code. Previously, the protover rewrite in 24031 allowed
5101 repeated votes from the same voter for the same protocol version
5102 to be counted multiple times in protover_compute_vote(). Fixes bug
5103 27649; bugfix on 0.3.3.5-rc.
5104 - Reject protover names that contain invalid characters. Fixes bug
5105 27687; bugfix on 0.3.3.1-alpha.
5107 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
5108 - protover_all_supported() would attempt to allocate up to 16GB on
5109 some inputs, leading to a potential memory DoS. Fixes bug 27206;
5110 bugfix on 0.3.3.5-rc.
5112 o Minor bugfixes (rust, backport from 0.3.5.4-alpha):
5113 - Fix a potential null dereference in protover_all_supported(). Add
5114 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
5115 - Return a string that can be safely freed by C code, not one
5116 created by the rust allocator, in protover_all_supported(). Fixes
5117 bug 27740; bugfix on 0.3.3.1-alpha.
5118 - Fix an API mismatch in the rust implementation of
5119 protover_compute_vote(). This bug could have caused crashes on any
5120 directory authorities running Tor with Rust (which we do not yet
5121 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
5123 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
5124 - If a unit test running in a subprocess exits abnormally or with a
5125 nonzero status code, treat the test as having failed, even if the
5126 test reported success. Without this fix, memory leaks don't cause
5127 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
5128 bugfix on 0.2.2.4-alpha.
5130 o Minor bugfixes (testing, backport from 0.3.5.4-alpha):
5131 - Treat backtrace test failures as expected on BSD-derived systems
5132 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
5133 (FreeBSD failures have been treated as expected since 18204 in
5134 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
5136 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
5137 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
5138 bugfix on 0.3.0.1-alpha.
5141 Changes in version 0.3.4.10 - 2019-01-07
5142 Tor 0.3.4.9 is the second stable release in its series; it backports
5143 numerous fixes, including an important fix for relays, and for anyone
5144 using OpenSSL 1.1.1. Anyone running an earlier version of Tor 0.3.4
5147 As a reminder, the Tor 0.3.4 series will be supported until 10 June
5148 2019. Some time between now and then, users should switch to the Tor
5149 0.3.5 series, which will receive long-term support until at least 1
5152 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
5153 - Fix our usage of named groups when running as a TLS 1.3 client in
5154 OpenSSL 1.1.1. Previously, we only initialized EC groups when
5155 running as a relay, which caused clients to fail to negotiate TLS
5156 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
5159 o Major bugfixes (relay, directory, backport from 0.3.5.7):
5160 - Always reactivate linked connections in the main loop so long as
5161 any linked connection has been active. Previously, connections
5162 serving directory information wouldn't get reactivated after the
5163 first chunk of data was sent (usually 32KB), which would prevent
5164 clients from bootstrapping. Fixes bug 28912; bugfix on
5165 0.3.4.1-alpha. Patch by "cypherpunks3".
5167 o Minor features (continuous integration, Windows, backport from 0.3.5.6-rc):
5168 - Always show the configure and test logs, and upload them as build
5169 artifacts, when building for Windows using Appveyor CI.
5172 o Minor features (controller, backport from 0.3.5.1-alpha):
5173 - For purposes of CIRC_BW-based dropped cell detection, track half-
5174 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
5175 bias check cells to arrive without counting it as dropped until
5176 either the END arrives, or the windows are empty. Closes
5179 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
5180 - Replace the 150 fallbacks originally introduced in Tor
5181 0.3.3.1-alpha in January 2018 (of which ~115 were still
5182 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
5183 removed) generated in December 2018. Closes ticket 24803.
5185 o Minor features (geoip):
5186 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
5187 Country database. Closes ticket 28395.
5189 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
5190 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
5191 key export function from handling long labels. When this bug is
5192 detected, Tor will disable TLS 1.3. We recommend upgrading to a
5193 version of OpenSSL without this bug when it becomes available.
5194 Closes ticket 28973.
5196 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
5197 - Initialize a variable unconditionally in aes_new_cipher(), since
5198 some compilers cannot tell that we always initialize it before
5199 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
5201 o Minor bugfixes (connection, relay, backport from 0.3.5.5-alpha):
5202 - Avoid a logging a BUG() stacktrace when closing connection held
5203 open because the write side is rate limited but not the read side.
5204 Now, the connection read side is simply shut down until Tor is
5205 able to flush the connection and close it. Fixes bug 27750; bugfix
5208 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.5-alpha):
5209 - Manually configure the zstd compiler options, when building using
5210 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
5211 not come with a pkg-config file. Fixes bug 28454; bugfix
5213 - Stop using an external OpenSSL install, and stop installing MSYS2
5214 packages, when building using mingw on Appveyor Windows CI. Fixes
5215 bug 28399; bugfix on 0.3.4.1-alpha.
5217 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.6-rc):
5218 - Explicitly specify the path to the OpenSSL library and do not
5219 download OpenSSL from Pacman, but instead use the library that is
5220 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
5222 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
5223 - When a user requests a group-readable DataDirectory, give it to
5224 them. Previously, when the DataDirectory and the CacheDirectory
5225 were the same, the default setting (0) for
5226 CacheDirectoryGroupReadable would override the setting for
5227 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
5230 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
5231 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
5232 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
5234 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
5235 - Don't warn so loudly when Tor is unable to decode an onion
5236 descriptor. This can now happen as a normal use case if a client
5237 gets a descriptor with client authorization but the client is not
5238 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
5240 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
5241 - When deleting an ephemeral onion service (DEL_ONION), do not close
5242 any rendezvous circuits in order to let the existing client
5243 connections finish by themselves or closed by the application. The
5244 HS v2 is doing that already so now we have the same behavior for
5245 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
5247 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
5248 - Update relay descriptor on bandwidth changes only when the uptime
5249 is smaller than 24h, in order to reduce the efficiency of guard
5250 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
5252 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
5253 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
5254 bugfix on 0.3.0.1-alpha.
5257 Changes in version 0.3.5.7 - 2019-01-07
5258 Tor 0.3.5.7 is the first stable release in its series; it includes
5259 compilation and portability fixes, and a fix for a severe problem
5260 affecting directory caches.
5262 The Tor 0.3.5 series includes several new features and performance
5263 improvements, including client authorization for v3 onion services,
5264 cleanups to bootstrap reporting, support for improved bandwidth-
5265 measurement tools, experimental support for NSS in place of OpenSSL,
5266 and much more. It also begins a full reorganization of Tor's code
5267 layout, for improved modularity and maintainability in the future.
5268 Finally, there is the usual set of performance improvements and
5269 bugfixes that we try to do in every release series.
5271 There are a couple of changes in the 0.3.5 that may affect
5272 compatibility. First, the default version for newly created onion
5273 services is now v3. Use the HiddenServiceVersion option if you want to
5274 override this. Second, some log messages related to bootstrapping have
5275 changed; if you use stem, you may need to update to the latest version
5276 so it will recognize them.
5278 We have designated 0.3.5 as a "long-term support" (LTS) series: we
5279 will continue to patch major bugs in typical configurations of 0.3.5
5280 until at least 1 Feb 2022. (We do not plan to provide long-term
5281 support for embedding, Rust support, NSS support, running a directory
5282 authority, or unsupported platforms. For these, you will need to stick
5283 with the latest stable release.)
5285 Below are the changes since 0.3.5.6-rc. For a complete list of changes
5286 since 0.3.4.9, see the ReleaseNotes file.
5288 o Major bugfixes (relay, directory):
5289 - Always reactivate linked connections in the main loop so long as
5290 any linked connection has been active. Previously, connections
5291 serving directory information wouldn't get reactivated after the
5292 first chunk of data was sent (usually 32KB), which would prevent
5293 clients from bootstrapping. Fixes bug 28912; bugfix on
5294 0.3.4.1-alpha. Patch by "cypherpunks3".
5296 o Minor features (compilation):
5297 - When possible, place our warning flags in a separate file, to
5298 avoid flooding verbose build logs. Closes ticket 28924.
5300 o Minor features (geoip):
5301 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
5302 Country database. Closes ticket 29012.
5304 o Minor features (OpenSSL bug workaround):
5305 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
5306 key export function from handling long labels. When this bug is
5307 detected, Tor will disable TLS 1.3. We recommend upgrading to a
5308 version of OpenSSL without this bug when it becomes available.
5309 Closes ticket 28973.
5311 o Minor features (performance):
5312 - Remove about 96% of the work from the function that we run at
5313 startup to test our curve25519_basepoint implementation. Since
5314 this function has yet to find an actual failure, we now only run
5315 it for 8 iterations instead of 200. Based on our profile
5316 information, this change should save around 8% of our startup time
5317 on typical desktops, and may have a similar effect on other
5318 platforms. Closes ticket 28838.
5319 - Stop re-validating our hardcoded Diffie-Hellman parameters on
5320 every startup. Doing this wasted time and cycles, especially on
5321 low-powered devices. Closes ticket 28851.
5323 o Minor bugfixes (compilation):
5324 - Fix compilation for Android by adding a missing header to
5325 freespace.c. Fixes bug 28974; bugfix on 0.3.5.1-alpha.
5327 o Minor bugfixes (correctness):
5328 - Fix an unreached code path where we checked the value of
5329 "hostname" inside send_resolved_hostname_cell(). Previously, we
5330 used it before checking it; now we check it first. Fixes bug
5331 28879; bugfix on 0.1.2.7-alpha.
5333 o Minor bugfixes (testing):
5334 - Make sure that test_rebind.py actually obeys its timeout, even
5335 when it receives a large number of log messages. Fixes bug 28883;
5336 bugfix on 0.3.5.4-alpha.
5337 - Stop running stem's unit tests as part of "make test-stem", but
5338 continue to run stem's unit and online tests during "make test-
5339 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
5341 o Minor bugfixes (windows services):
5342 - Make Tor start correctly as an NT service again: previously it was
5343 broken by refactoring. Fixes bug 28612; bugfix on 0.3.5.3-alpha.
5345 o Code simplification and refactoring:
5346 - When parsing a port configuration, make it more obvious to static
5347 analyzer tools that we always initialize the address. Closes
5351 Changes in version 0.3.5.6-rc - 2018-12-18
5352 Tor 0.3.5.6-rc fixes numerous small bugs in earlier versions of Tor.
5353 It is the first release candidate in the 0.3.5.x series; if no further
5354 huge bugs are found, our next release may be the stable 0.3.5.x.
5356 o Minor features (continuous integration, Windows):
5357 - Always show the configure and test logs, and upload them as build
5358 artifacts, when building for Windows using Appveyor CI.
5361 o Minor features (fallback directory list):
5362 - Replace the 150 fallbacks originally introduced in Tor
5363 0.3.3.1-alpha in January 2018 (of which ~115 were still
5364 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
5365 removed) generated in December 2018. Closes ticket 24803.
5367 o Minor features (geoip):
5368 - Update geoip and geoip6 to the December 5 2018 Maxmind GeoLite2
5369 Country database. Closes ticket 28744.
5371 o Minor bugfixes (compilation):
5372 - Add missing dependency on libgdi32.dll for tor-print-ed-signing-
5373 cert.exe on Windows. Fixes bug 28485; bugfix on 0.3.5.1-alpha.
5375 o Minor bugfixes (continuous integration, Windows):
5376 - Explicitly specify the path to the OpenSSL library and do not
5377 download OpenSSL from Pacman, but instead use the library that is
5378 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
5380 o Minor bugfixes (onion service v3):
5381 - When deleting an ephemeral onion service (DEL_ONION), do not close
5382 any rendezvous circuits in order to let the existing client
5383 connections finish by themselves or closed by the application. The
5384 HS v2 is doing that already so now we have the same behavior for
5385 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
5387 o Minor bugfixes (restart-in-process, boostrap):
5388 - Add missing resets of bootstrap tracking state when shutting down
5389 (regression caused by ticket 27169). Fixes bug 28524; bugfix
5392 o Minor bugfixes (testing):
5393 - Use a separate DataDirectory for the test_rebind script.
5394 Previously, this script would run using the default DataDirectory,
5395 and sometimes fail. Fixes bug 28562; bugfix on 0.3.5.1-alpha.
5396 Patch from Taylor R Campbell.
5397 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
5398 bugfix on 0.3.0.1-alpha.
5400 o Minor bugfixes (Windows):
5401 - Correctly identify Windows 8.1, Windows 10, and Windows Server
5402 2008 and later from their NT versions. Fixes bug 28096; bugfix on
5403 0.2.2.34; reported by Keifer Bly.
5404 - On recent Windows versions, the GetVersionEx() function may report
5405 an earlier Windows version than the running OS. To avoid user
5406 confusion, add "[or later]" to Tor's version string on affected
5407 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
5409 - Remove Windows versions that were never supported by the
5410 GetVersionEx() function. Stop duplicating the latest Windows
5411 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
5412 reported by Keifer Bly.
5415 - Increase logging and tag all log entries with timestamps in
5416 test_rebind.py. Provides diagnostics for issue 28229.
5418 o Code simplification and refactoring (shared random, dirauth):
5419 - Change many tor_assert() to use BUG() instead. The idea is to not
5420 crash a dirauth but rather scream loudly with a stacktrace and let
5421 it continue run. The shared random subsystem is very resilient and
5422 if anything wrong happens with it, at worst a non coherent value
5423 will be put in the vote and discarded by the other authorities.
5424 Closes ticket 19566.
5426 o Documentation (onion services):
5427 - Document in the man page that changing ClientOnionAuthDir value or
5428 adding a new file in the directory will not work at runtime upon
5429 sending a HUP if Sandbox 1. Closes ticket 28128.
5430 - Note in the man page that the only real way to fully revoke an
5431 onion service v3 client authorization is by restarting the tor
5432 process. Closes ticket 28275.
5435 Changes in version 0.3.5.5-alpha - 2018-11-16
5436 Tor 0.3.5.5-alpha includes numerous bugfixes on earlier releases,
5437 including several that we hope to backport to older release series in
5440 o Major bugfixes (OpenSSL, portability):
5441 - Fix our usage of named groups when running as a TLS 1.3 client in
5442 OpenSSL 1.1.1. Previously, we only initialized EC groups when
5443 running as a relay, which caused clients to fail to negotiate TLS
5444 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
5447 o Minor features (geoip):
5448 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
5449 Country database. Closes ticket 28395.
5451 o Minor bugfixes (compilation):
5452 - Initialize a variable unconditionally in aes_new_cipher(), since
5453 some compilers cannot tell that we always initialize it before
5454 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
5456 o Minor bugfixes (connection, relay):
5457 - Avoid a logging a BUG() stacktrace when closing connection held
5458 open because the write side is rate limited but not the read side.
5459 Now, the connection read side is simply shut down until Tor is
5460 able to flush the connection and close it. Fixes bug 27750; bugfix
5463 o Minor bugfixes (continuous integration, Windows):
5464 - Manually configure the zstd compiler options, when building using
5465 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
5466 not come with a pkg-config file. Fixes bug 28454; bugfix
5468 - Stop using an external OpenSSL install, and stop installing MSYS2
5469 packages, when building using mingw on Appveyor Windows CI. Fixes
5470 bug 28399; bugfix on 0.3.4.1-alpha.
5472 o Minor bugfixes (documentation):
5473 - Make Doxygen work again after the code movement in the 0.3.5
5474 source tree. Fixes bug 28435; bugfix on 0.3.5.1-alpha.
5476 o Minor bugfixes (Linux seccomp2 sandbox):
5477 - Permit the "shutdown()" system call, which is apparently used by
5478 OpenSSL under some circumstances. Fixes bug 28183; bugfix
5481 o Minor bugfixes (logging):
5482 - Stop talking about the Named flag in log messages. Clients have
5483 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
5486 o Minor bugfixes (memory leaks):
5487 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
5488 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
5490 o Minor bugfixes (onion services):
5491 - On an intro point for a version 3 onion service, stop closing
5492 introduction circuits on an NACK. This lets the client decide
5493 whether to reuse the circuit or discard it. Previously, we closed
5494 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
5495 0.3.2.1-alpha. Patch by Neel Chaunan.
5496 - When replacing a descriptor in the client cache, make sure to
5497 close all client introduction circuits for the old descriptor, so
5498 we don't end up with unusable leftover circuits. Fixes bug 27471;
5499 bugfix on 0.3.2.1-alpha.
5502 Changes in version 0.3.5.4-alpha - 2018-11-08
5503 Tor 0.3.5.4-alpha includes numerous bugfixes on earlier versions and
5504 improves our continuous integration support. It continues our attempts
5505 to stabilize this alpha branch and build it into a foundation for an
5506 acceptable long-term-support release.
5508 o Major bugfixes (compilation, rust):
5509 - Rust tests can now build and run successfully with the
5510 --enable-fragile-hardening option enabled. Doing this currently
5511 requires the rust beta channel; it will be possible with stable
5512 rust once Rust version 1.31 is released. Patch from Alex Crichton.
5513 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
5515 o Major bugfixes (embedding, main loop):
5516 - When DisableNetwork becomes set, actually disable periodic events
5517 that are already enabled. (Previously, we would refrain from
5518 enabling new ones, but we would leave the old ones turned on.)
5519 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
5521 o Minor features (continuous integration):
5522 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
5524 - Add new CI job to Travis configuration to run stem-based
5525 integration tests. Closes ticket 27913.
5527 o Minor features (Windows, continuous integration):
5528 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
5529 Appveyor's CI. Closes ticket 28318.
5531 o Minor bugfixes (C correctness, also in 0.3.4.9):
5532 - Avoid undefined behavior in an end-of-string check when parsing
5533 the BEGIN line in a directory object. Fixes bug 28202; bugfix
5536 o Minor bugfixes (compilation):
5537 - Fix a pair of missing headers on OpenBSD. Fixes bug 28303; bugfix
5538 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
5540 o Minor bugfixes (compilation, OpenSolaris):
5541 - Fix compilation on OpenSolaris and its descendants by adding a
5542 missing include to compat_pthreads.c. Fixes bug 27963; bugfix
5545 o Minor bugfixes (configuration):
5546 - Refuse to start with relative file paths and RunAsDaemon set
5547 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
5550 o Minor bugfixes (directory authority, also in 0.3.4.9):
5551 - Log additional info when we get a relay that shares an ed25519 ID
5552 with a different relay, instead of a BUG() warning with a
5553 backtrace. Fixes bug 27800; bugfix on 0.3.2.1-alpha.
5555 o Minor bugfixes (onion service v3):
5556 - Build the service descriptor's signing key certificate before
5557 uploading, so we always have a fresh one: leaving no chances for
5558 it to expire service side. Fixes bug 27838; bugfix
5561 o Minor bugfixes (onion service v3, client authorization):
5562 - Fix an assert() when adding a client authorization for the first
5563 time and then sending a HUP signal to the service. Before that,
5564 Tor would stop abruptly. Fixes bug 27995; bugfix on 0.3.5.1-alpha.
5566 o Minor bugfixes (onion services):
5567 - Unless we have explicitly set HiddenServiceVersion, detect the
5568 onion service version and then look for invalid options.
5569 Previously, we did the reverse, but that broke existing configs
5570 which were pointed to a v2 service and had options like
5571 HiddenServiceAuthorizeClient set. Fixes bug 28127; bugfix on
5572 0.3.5.1-alpha. Patch by Neel Chauhan.
5574 o Minor bugfixes (portability):
5575 - Make the OPE code (which is used for v3 onion services) run
5576 correctly on big-endian platforms. Fixes bug 28115; bugfix
5579 o Minor bugfixes (protover, rust):
5580 - Reject extra commas in version strings. Fixes bug 27197; bugfix
5583 o Minor bugfixes (relay shutdown, systemd):
5584 - Notify systemd of ShutdownWaitLength so it can be set to longer
5585 than systemd's TimeoutStopSec. In Tor's systemd service file, set
5586 TimeoutSec to 60 seconds to allow Tor some time to shut down.
5587 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
5589 o Minor bugfixes (rust, also in 0.3.4.9):
5590 - Fix a potential null dereference in protover_all_supported(). Add
5591 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
5592 - Return a string that can be safely freed by C code, not one
5593 created by the rust allocator, in protover_all_supported(). Fixes
5594 bug 27740; bugfix on 0.3.3.1-alpha.
5596 o Minor bugfixes (rust, directory authority, also in 0.3.4.9):
5597 - Fix an API mismatch in the rust implementation of
5598 protover_compute_vote(). This bug could have caused crashes on any
5599 directory authorities running Tor with Rust (which we do not yet
5600 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
5602 o Minor bugfixes (testing):
5603 - Avoid hangs and race conditions in test_rebind.py. Fixes bug
5604 27968; bugfix on 0.3.5.1-alpha.
5606 o Minor bugfixes (testing, also in 0.3.4.9):
5607 - Treat backtrace test failures as expected on BSD-derived systems
5608 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
5609 (FreeBSD failures have been treated as expected since 18204 in
5610 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
5612 o Documentation (onion service manpage):
5613 - Improve HSv3 client authorization by making some options more
5614 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
5617 Changes in version 0.3.4.9 - 2018-11-02
5618 Tor 0.3.4.9 is the second stable release in its series; it backports
5619 numerous fixes, including a fix for a bandwidth management bug that
5620 was causing memory exhaustion on relays. Anyone running an earlier
5621 version of Tor 0.3.4.9 should upgrade.
5623 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
5624 - Fix compilation on ARM (and other less-used CPUs) when compiling
5625 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
5627 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
5628 - Make sure Tor bootstraps and works properly if only the
5629 ControlPort is set. Prior to this fix, Tor would only bootstrap
5630 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
5631 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
5633 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
5634 - When our write bandwidth limit is exhausted, stop writing on the
5635 connection. Previously, we had a typo in the code that would make
5636 us stop reading instead, leading to relay connections being stuck
5637 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
5640 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
5641 - Fix a use-after-free error that could be caused by passing Tor an
5642 impossible set of options that would fail during options_act().
5643 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
5645 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
5646 - Don't do a distcheck with --disable-module-dirauth in Travis.
5647 Implements ticket 27252.
5648 - Only run one online rust build in Travis, to reduce network
5649 errors. Skip offline rust builds on Travis for Linux gcc, because
5650 they're redundant. Implements ticket 27252.
5651 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
5652 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
5653 Linux with default settings, because all the non-default builds
5654 use gcc on Linux. Implements ticket 27252.
5656 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
5657 - Use the Travis Homebrew addon to install packages on macOS during
5658 Travis CI. The package list is the same, but the Homebrew addon
5659 does not do a `brew update` by default. Implements ticket 27738.
5661 o Minor features (geoip):
5662 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
5663 Country database. Closes ticket 27991.
5665 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
5666 - Fix an integer overflow bug in our optimized 32-bit millisecond-
5667 difference algorithm for 32-bit Apple platforms. Previously, it
5668 would overflow when calculating the difference between two times
5669 more than 47 days apart. Fixes part of bug 27139; bugfix
5671 - Improve the precision of our 32-bit millisecond difference
5672 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
5673 bugfix on 0.3.4.1-alpha.
5674 - Relax the tolerance on the mainloop/update_time_jumps test when
5675 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
5678 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
5679 - Avoid undefined behavior in an end-of-string check when parsing
5680 the BEGIN line in a directory object. Fixes bug 28202; bugfix
5683 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
5684 - Only install the necessary mingw packages during our appveyor
5685 builds. This change makes the build a little faster, and prevents
5686 a conflict with a preinstalled mingw openssl that appveyor now
5687 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
5689 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
5690 - Rewrite our assertion macros so that they no longer suppress the
5691 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
5693 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
5694 - Stop reinstalling identical packages in our Windows CI. Fixes bug
5695 27464; bugfix on 0.3.4.1-alpha.
5697 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
5698 - Log additional info when we get a relay that shares an ed25519 ID
5699 with a different relay, instead making a BUG() warning. Fixes bug
5700 27800; bugfix on 0.3.2.1-alpha.
5702 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
5703 - Avoid a double-close when shutting down a stalled directory
5704 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
5706 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
5707 - Fix a bug warning when closing an HTTP tunnel connection due to an
5708 HTTP request we couldn't handle. Fixes bug 26470; bugfix
5711 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
5712 - Ensure circuitmux queues are empty before scheduling or sending
5713 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
5715 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
5716 - When the onion service directory can't be created or has the wrong
5717 permissions, do not log a stack trace. Fixes bug 27335; bugfix
5720 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
5721 - Close all SOCKS request (for the same .onion) if the newly fetched
5722 descriptor is unusable. Before that, we would close only the first
5723 one leaving the other hanging and let to time out by themselves.
5724 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
5726 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
5727 - When selecting a v3 rendezvous point, don't only look at the
5728 protover, but also check whether the curve25519 onion key is
5729 present. This way we avoid picking a relay that supports the v3
5730 rendezvous but for which we don't have the microdescriptor. Fixes
5731 bug 27797; bugfix on 0.3.2.1-alpha.
5733 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
5734 - Reject protocol names containing bytes other than alphanumeric
5735 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
5738 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
5739 - Compute protover votes correctly in the rust version of the
5740 protover code. Previously, the protover rewrite in 24031 allowed
5741 repeated votes from the same voter for the same protocol version
5742 to be counted multiple times in protover_compute_vote(). Fixes bug
5743 27649; bugfix on 0.3.3.5-rc.
5744 - Reject protover names that contain invalid characters. Fixes bug
5745 27687; bugfix on 0.3.3.1-alpha.
5747 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
5748 - protover_all_supported() would attempt to allocate up to 16GB on
5749 some inputs, leading to a potential memory DoS. Fixes bug 27206;
5750 bugfix on 0.3.3.5-rc.
5752 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
5753 - Fix an API mismatch in the rust implementation of
5754 protover_compute_vote(). This bug could have caused crashes on any
5755 directory authorities running Tor with Rust (which we do not yet
5756 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
5758 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
5759 - Fix a potential null dereference in protover_all_supported(). Add
5760 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
5761 - Return a string that can be safely freed by C code, not one
5762 created by the rust allocator, in protover_all_supported(). Fixes
5763 bug 27740; bugfix on 0.3.3.1-alpha.
5765 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
5766 - If a unit test running in a subprocess exits abnormally or with a
5767 nonzero status code, treat the test as having failed, even if the
5768 test reported success. Without this fix, memory leaks don't cause
5769 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
5770 bugfix on 0.2.2.4-alpha.
5772 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
5773 - Make the hs_service tests use the same time source when creating
5774 the introduction point and when testing it. Now tests work better
5775 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
5778 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
5779 - Treat backtrace test failures as expected on BSD-derived systems
5780 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
5781 (FreeBSD failures have been treated as expected since 18204 in
5782 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
5785 Changes in version 0.3.5.3-alpha - 2018-10-17
5786 Tor 0.3.5.3-alpha fixes several bugs, mostly from previous 0.3.5.x
5787 versions. One important fix for relays addresses a problem with rate-
5788 limiting code from back in 0.3.4.x: If the fix works out, we'll be
5789 backporting it soon. This release is still an alpha, but we hope it's
5790 getting closer and closer to stability.
5792 o Major features (onion services):
5793 - Version 3 onion services can now use the per-service
5794 HiddenServiceExportCircuitID option to differentiate client
5795 circuits. It communicates with the service by using the HAProxy
5796 protocol to assign virtual IP addresses to inbound client
5797 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
5799 o Major bugfixes (compilation):
5800 - Fix compilation on ARM (and other less-used CPUs) when compiling
5801 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
5803 o Major bugfixes (initialization, crash):
5804 - Fix an assertion crash that would stop Tor from starting up if it
5805 tried to activate a periodic event too early. Fixes bug 27861;
5806 bugfix on 0.3.5.1-alpha.
5808 o Major bugfixes (mainloop, bootstrap):
5809 - Make sure Tor bootstraps and works properly if only the
5810 ControlPort is set. Prior to this fix, Tor would only bootstrap
5811 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
5812 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
5814 o Major bugfixes (relay):
5815 - When our write bandwidth limit is exhausted, stop writing on the
5816 connection. Previously, we had a typo in the code that would make
5817 us stop reading instead, leading to relay connections being stuck
5818 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
5821 o Minor features (continuous integration):
5822 - Use the Travis Homebrew addon to install packages on macOS during
5823 Travis CI. The package list is the same, but the Homebrew addon
5824 does not do a `brew update` by default. Implements ticket 27738.
5825 - Report what program produced the mysterious core file that we
5826 occasionally see on Travis CI during make distcheck. Closes
5829 o Minor features (geoip):
5830 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
5831 Country database. Closes ticket 27991.
5833 o Minor bugfixes (code safety):
5834 - Rewrite our assertion macros so that they no longer suppress the
5835 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
5838 o Minor bugfixes (compilation):
5839 - Compile the ed25519-donna code with a correct declaration of
5840 crypto_strongest_rand(). Previously, we built it with one type,
5841 but linked it against another in the unit tests, which caused
5842 compilation failures with LTO enabled. This could have caused
5843 other undefined behavior in the tests. Fixes bug 27728; bugfix
5846 o Minor bugfixes (compilation, netbsd):
5847 - Add a missing include back into procmon.c. Fixes bug 27990; bugfix
5850 o Minor bugfixes (continuous integration, appveyor):
5851 - Install only the necessary mingw packages during our appveyor
5852 builds. This change makes the build a little faster, and prevents
5853 a conflict with a preinstalled mingw openssl that appveyor now
5854 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
5856 o Minor bugfixes (directory permissions):
5857 - When a user requests a group-readable DataDirectory, give it to
5858 them. Previously, when the DataDirectory and the CacheDirectory
5859 were the same, the default setting (0) for
5860 CacheDirectoryGroupReadable would override the setting for
5861 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
5864 o Minor bugfixes (memory leaks):
5865 - Fix a small memory leak when calling Tor with --dump-config. Fixes
5866 bug 27893; bugfix on 0.3.2.1-alpha.
5868 o Minor bugfixes (networking):
5869 - In retry_listeners_ports(), make sure that we're removing a member
5870 of old_conns smartlist at most once. Fixes bug 27808; bugfix
5872 - Refrain from attempting socket rebinding when old and new
5873 listeners are in different address families. Fixes bug 27928;
5874 bugfix on 0.3.5.1-alpha.
5876 o Minor bugfixes (onion service v3):
5877 - Stop dumping a stack trace when trying to connect to an intro
5878 point without having a descriptor for it. Fixes bug 27774; bugfix
5880 - Don't warn so loudly when Tor is unable to decode an onion
5881 descriptor. This can now happen as a normal use case if a client
5882 gets a descriptor with client authorization but the client is not
5883 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
5884 - When selecting a v3 rendezvous point, don't only look at the
5885 protover, but also check whether the curve25519 onion key is
5886 present. This way we avoid picking a relay that supports the v3
5887 rendezvous but for which we don't have the microdescriptor. Fixes
5888 bug 27797; bugfix on 0.3.2.1-alpha.
5890 o Minor bugfixes (protover):
5891 - Reject protocol names containing bytes other than alphanumeric
5892 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
5895 o Minor bugfixes (testing):
5896 - Make the hs_service tests use the same time source when creating
5897 the introduction point and when testing it. Now tests work better
5898 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
5900 - In test_rebind.py, check if the Python version is in the supported
5901 range. Fixes bug 27675; bugfix on 0.3.5.1-alpha.
5903 o Code simplification and refactoring:
5904 - Divide more large Tor source files -- especially ones that span
5905 multiple areas of functionality -- into smaller parts, including
5906 onion.c and main.c. Closes ticket 26747.
5907 - Divide the "routerparse.c" module into separate modules for each
5908 group of parsed objects. Closes ticket 27924.
5909 - Move protover_rust.c to the same place protover.c was moved to.
5910 Closes ticket 27814.
5911 - Split directory.c into separate pieces for client, server, and
5912 common functionality. Closes ticket 26744.
5913 - Split the non-statistics-related parts from the rephist.c and
5914 geoip.c modules. Closes ticket 27892.
5915 - Split the router.c file into relay-only and shared components, to
5916 help with future modularization. Closes ticket 27864.
5919 - In the tor-resolve(1) manpage, fix the reference to socks-
5920 extensions.txt by adding a web URL. Resolves ticket 27853.
5921 - Mention that we require Python to be 2.7 or newer for some
5922 integration tests that we ship with Tor. Resolves ticket 27677.
5925 Changes in version 0.3.5.2-alpha - 2018-09-21
5926 Tor 0.3.5.2-alpha fixes several bugs in 0.3.5.1-alpha, including one
5927 that made Tor think it had run out of sockets. Anybody running a relay
5928 or an onion service on 0.3.5.1-alpha should upgrade.
5930 o Major bugfixes (relay bandwidth statistics):
5931 - When we close relayed circuits, report the data in the circuit
5932 queues as being written in our relay bandwidth stats. This
5933 mitigates guard discovery and other attacks that close circuits
5934 for the explicit purpose of noticing this discrepancy in
5935 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
5937 o Major bugfixes (socket accounting):
5938 - In our socket accounting code, count a socket as closed even when
5939 it is closed indirectly by the TLS layer. Previously, we would
5940 count these sockets as still in use, and incorrectly believe that
5941 we had run out of sockets. Fixes bug 27795; bugfix
5944 o Minor bugfixes (32-bit OSX and iOS, timing):
5945 - Fix an integer overflow bug in our optimized 32-bit millisecond-
5946 difference algorithm for 32-bit Apple platforms. Previously, it
5947 would overflow when calculating the difference between two times
5948 more than 47 days apart. Fixes part of bug 27139; bugfix
5950 - Improve the precision of our 32-bit millisecond difference
5951 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
5952 bugfix on 0.3.4.1-alpha.
5953 - Relax the tolerance on the mainloop/update_time_jumps test when
5954 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
5957 o Minor bugfixes (onion service v3):
5958 - Close all SOCKS request (for the same .onion) if the newly fetched
5959 descriptor is unusable. Before that, we would close only the first
5960 one leaving the other hanging and let to time out by themselves.
5961 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
5963 o Minor bugfixes (memory leak):
5964 - Fix an unlikely memory leak when trying to read a private key from
5965 a ridiculously large file. Fixes bug 27764; bugfix on
5966 0.3.5.1-alpha. This is CID 1439488.
5968 o Minor bugfixes (NSS):
5969 - Correctly detect failure to open a dummy TCP socket when stealing
5970 ownership of an fd from the NSS layer. Fixes bug 27782; bugfix
5973 o Minor bugfixes (rust):
5974 - protover_all_supported() would attempt to allocate up to 16GB on
5975 some inputs, leading to a potential memory DoS. Fixes bug 27206;
5976 bugfix on 0.3.3.5-rc.
5978 o Minor bugfixes (testing):
5979 - Revise the "conditionvar_timeout" test so that it succeeds even on
5980 heavily loaded systems where the test threads are not scheduled
5981 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
5983 o Code simplification and refactoring:
5984 - Divide the routerlist.c and dirserv.c modules into smaller parts.
5985 Closes ticket 27799.
5988 Changes in version 0.3.5.1-alpha - 2018-09-18
5989 Tor 0.3.5.1-alpha is the first release of the 0.3.5.x series. It adds
5990 client authorization for modern (v3) onion services, improves
5991 bootstrap reporting, begins reorganizing Tor's codebase, adds optional
5992 support for NSS in place of OpenSSL, and much more.
5994 o Major features (onion services, UI change):
5995 - For a newly created onion service, the default version is now 3.
5996 Tor still supports existing version 2 services, but the operator
5997 now needs to set "HiddenServiceVersion 2" in order to create a new
5998 version 2 service. For existing services, Tor now learns the
5999 version by reading the key file. Closes ticket 27215.
6001 o Major features (relay, UI change):
6002 - Relays no longer run as exits by default. If the "ExitRelay"
6003 option is auto (or unset), and no exit policy is specified with
6004 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
6005 Previously in this case, we allowed exit traffic and logged a
6006 warning message. Closes ticket 21530. Patch by Neel Chauhan.
6007 - Tor now validates that the ContactInfo config option is valid UTF-
6008 8 when parsing torrc. Closes ticket 27428.
6010 o Major features (bootstrap):
6011 - Don't report directory progress until after a connection to a
6012 relay or bridge has succeeded. Previously, we'd report 80%
6013 progress based on cached directory information when we couldn't
6014 even connect to the network. Closes ticket 27169.
6016 o Major features (new code layout):
6017 - Nearly all of Tor's source code has been moved around into more
6018 logical places. The "common" directory is now divided into a set
6019 of libraries in "lib", and files in the "or" directory have been
6020 split into "core" (logic absolutely needed for onion routing),
6021 "feature" (independent modules in Tor), and "app" (to configure
6022 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
6023 more information. Closes ticket 26481.
6025 This refactoring is not complete: although the libraries have been
6026 refactored to be acyclic, the main body of Tor is still too
6027 interconnected. We will attempt to improve this in the future.
6029 o Major features (onion services v3):
6030 - Implement onion service client authorization at the descriptor
6031 level: only authorized clients can decrypt a service's descriptor
6032 to find out how to contact it. A new torrc option was added to
6033 control this client side: ClientOnionAuthDir <path>. On the
6034 service side, if the "authorized_clients/" directory exists in the
6035 onion service directory path, client configurations are read from
6036 the files within. See the manpage for more details. Closes ticket
6037 27547. Patch done by Suphanat Chunhapanya (haxxpop).
6038 - Improve revision counter generation in next-gen onion services.
6039 Onion services can now scale by hosting multiple instances on
6040 different hosts without synchronization between them, which was
6041 previously impossible because descriptors would get rejected by
6042 HSDirs. Addresses ticket 25552.
6044 o Major features (portability, cryptography, experimental, TLS):
6045 - Tor now has the option to compile with the NSS library instead of
6046 OpenSSL. This feature is experimental, and we expect that bugs may
6047 remain. It is mainly intended for environments where Tor's
6048 performance is not CPU-bound, and where NSS is already known to be
6049 installed. To try it out, configure Tor with the --enable-nss
6050 flag. Closes tickets 26631, 26815, and 26816.
6052 If you are experimenting with this option and using an old cached
6053 consensus, Tor may fail to start. To solve this, delete your
6054 "cached-consensus" and "cached-microdesc-consensus" files,
6055 (if present), and restart Tor.
6057 o Major bugfixes (directory authority):
6058 - Actually check that the address we get from DirAuthority
6059 configuration line is valid IPv4. Explicitly disallow DirAuthority
6060 address to be a DNS hostname. Fixes bug 26488; bugfix
6063 o Major bugfixes (restart-in-process):
6064 - Fix a use-after-free error that could be caused by passing Tor an
6065 impossible set of options that would fail during options_act().
6066 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
6068 o Minor features (admin tools):
6069 - Add a new --key-expiration option to print the expiration date of
6070 the signing cert in an ed25519_signing_cert file. Resolves
6073 o Minor features (build):
6074 - If you pass the "--enable-pic" option to configure, Tor will try
6075 to tell the compiler to build position-independent code suitable
6076 to link into a dynamic library. (The default remains -fPIE, for
6077 code suitable for a relocatable executable.) Closes ticket 23846.
6079 o Minor features (code correctness, testing):
6080 - Tor's build process now includes a "check-includes" make target to
6081 verify that no module of Tor relies on any headers from a higher-
6082 level module. We hope to use this feature over time to help
6083 refactor our codebase. Closes ticket 26447.
6085 o Minor features (code layout):
6086 - We have a new "lowest-level" error-handling API for use by code
6087 invoked from within the logging module. With this interface, the
6088 logging code is no longer at risk of calling into itself if a
6089 failure occurs while it is trying to log something. Closes
6092 o Minor features (compilation):
6093 - Tor's configure script now supports a --with-malloc= option to
6094 select your malloc implementation. Supported options are
6095 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
6096 default). Addresses part of ticket 20424. Based on a patch from
6099 o Minor features (config):
6100 - The "auto" keyword in torrc is now case-insensitive. Closes
6103 o Minor features (continuous integration):
6104 - Don't do a distcheck with --disable-module-dirauth in Travis.
6105 Implements ticket 27252.
6106 - Install libcap-dev and libseccomp2-dev so these optional
6107 dependencies get tested on Travis CI. Closes ticket 26560.
6108 - Only run one online rust build in Travis, to reduce network
6109 errors. Skip offline rust builds on Travis for Linux gcc, because
6110 they're redundant. Implements ticket 27252.
6111 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
6112 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
6113 Linux with default settings, because all the non-default builds
6114 use gcc on Linux. Implements ticket 27252.
6116 o Minor features (controller):
6117 - Emit CIRC_BW events as soon as we detect that we processed an
6118 invalid or otherwise dropped cell on a circuit. This allows
6119 vanguards and other controllers to react more quickly to dropped
6120 cells. Closes ticket 27678.
6121 - For purposes of CIRC_BW-based dropped cell detection, track half-
6122 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
6123 bias check cells to arrive without counting it as dropped until
6124 either the END arrives, or the windows are empty. Closes
6126 - Implement a 'GETINFO md/all' controller command to enable getting
6127 all known microdescriptors. Closes ticket 8323.
6128 - The GETINFO command now support an "uptime" argument, to return
6129 Tor's uptime in seconds. Closes ticket 25132.
6131 o Minor features (denial-of-service avoidance):
6132 - Make our OOM handler aware of the DNS cache so that it doesn't
6133 fill up the memory. This check is important for our DoS mitigation
6134 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
6136 o Minor features (development):
6137 - Tor's makefile now supports running the "clippy" Rust style tool
6138 on our Rust code. Closes ticket 22156.
6140 o Minor features (directory authority):
6141 - There is no longer an artificial upper limit on the length of
6142 bandwidth lines. Closes ticket 26223.
6143 - When a bandwidth file is used to obtain the bandwidth measurements,
6144 include this bandwidth file headers in the votes. Closes
6146 - Improved support for networks with only a single authority or a
6147 single fallback directory. Patch from Gabriel Somlo. Closes
6150 o Minor features (embedding API):
6151 - The Tor controller API now supports a function to launch Tor with
6152 a preconstructed owning controller FD, so that embedding
6153 applications don't need to manage controller ports and
6154 authentication. Closes ticket 24204.
6155 - The Tor controller API now has a function that returns the name
6156 and version of the backend implementing the API. Closes
6159 o Minor features (geoip):
6160 - Update geoip and geoip6 to the September 6 2018 Maxmind GeoLite2
6161 Country database. Closes ticket 27631.
6163 o Minor features (memory management):
6164 - Get Libevent to use the same memory allocator as Tor, by calling
6165 event_set_mem_functions() during initialization. Resolves
6168 o Minor features (memory usage):
6169 - When not using them, store legacy TAP public onion keys in DER-
6170 encoded format, rather than as expanded public keys. This should
6171 save several megabytes on typical clients. Closes ticket 27246.
6173 o Minor features (OpenSSL):
6174 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
6175 than our own. Resolves ticket 19979.
6177 o Minor features (Rust, code quality):
6178 - Improve rust code quality in the rust protover implementation by
6179 making it more idiomatic. Includes changing an internal API to
6180 take &str instead of &String. Closes ticket 26492.
6182 o Minor features (testing):
6183 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
6184 chutney. Implements ticket 27211.
6186 o Minor features (tor-resolve):
6187 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
6188 Side-effect of the refactoring for ticket 26526.
6190 o Minor features (UI):
6191 - Log each included configuration file or directory as we read it,
6192 to provide more visibility about where Tor is reading from. Patch
6193 from Unto Sten; closes ticket 27186.
6194 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
6195 Closes ticket 26703.
6197 o Minor bugfixes (bootstrap):
6198 - Try harder to get descriptors in non-exit test networks, by using
6199 the mid weight for the third hop when there are no exits. Fixes
6200 bug 27237; bugfix on 0.2.6.2-alpha.
6202 o Minor bugfixes (C correctness):
6203 - Avoid casting smartlist index to int implicitly, as it may trigger
6204 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
6205 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
6206 - Use time_t for all values in
6207 predicted_ports_prediction_time_remaining(). Rework the code that
6208 computes difference between durations/timestamps. Fixes bug 27165;
6209 bugfix on 0.3.1.1-alpha.
6211 o Minor bugfixes (client, memory usage):
6212 - When not running as a directory cache, there is no need to store
6213 the text of the current consensus networkstatus in RAM.
6214 Previously, however, clients would store it anyway, at a cost of
6215 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
6218 o Minor bugfixes (client, reachableaddresses):
6219 - Instead of adding a "reject *:*" line to ReachableAddresses when
6220 loading the configuration, add one to the policy after parsing it
6221 in parse_reachable_addresses(). This prevents extra "reject *.*"
6222 lines from accumulating on reloads. Fixes bug 20874; bugfix on
6223 0.1.1.5-alpha. Patch by Neel Chauhan.
6225 o Minor bugfixes (code quality):
6226 - Rename sandbox_getaddrinfo() and other functions to no longer
6227 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
6228 bugfix on 0.2.7.1-alpha.
6230 o Minor bugfixes (configuration, Onion Services):
6231 - In rend_service_parse_port_config(), disallow any input to remain
6232 after address-port pair was parsed. This will catch address and
6233 port being whitespace-separated by mistake of the user. Fixes bug
6234 27044; bugfix on 0.2.9.10.
6236 o Minor bugfixes (continuous integration):
6237 - Stop reinstalling identical packages in our Windows CI. Fixes bug
6238 27464; bugfix on 0.3.4.1-alpha.
6240 o Minor bugfixes (controller):
6241 - Consider all routerinfo errors other than "not a server" to be
6242 transient for the purpose of "GETINFO exit-policy/*" controller
6243 request. Print stacktrace in the unlikely case of failing to
6244 recompute routerinfo digest. Fixes bug 27034; bugfix
6247 o Minor bugfixes (directory connection shutdown):
6248 - Avoid a double-close when shutting down a stalled directory
6249 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
6251 o Minor bugfixes (HTTP tunnel):
6252 - Fix a bug warning when closing an HTTP tunnel connection due to an
6253 HTTP request we couldn't handle. Fixes bug 26470; bugfix
6256 o Minor bugfixes (ipv6):
6257 - In addrs_in_same_network_family(), we choose the subnet size based
6258 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
6259 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
6260 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
6262 o Minor bugfixes (logging):
6263 - As a precaution, do an early return from log_addr_has_changed() if
6264 Tor is running as client. Also, log a stack trace for debugging as
6265 this function should only be called when Tor runs as server. Fixes
6266 bug 26892; bugfix on 0.1.1.9-alpha.
6267 - Refrain from mentioning bug 21018 in the logs, as it is already
6268 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
6270 o Minor bugfixes (logging, documentation):
6271 - When SafeLogging is enabled, scrub IP address in
6272 channel_tls_process_netinfo_cell(). Also, add a note to manpage
6273 that scrubbing is not guaranteed on loglevels below Notice. Fixes
6274 bug 26882; bugfix on 0.2.4.10-alpha.
6276 o Minor bugfixes (netflow padding):
6277 - Ensure circuitmux queues are empty before scheduling or sending
6278 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
6280 o Minor bugfixes (onion service v2):
6281 - Log at level "info", not "warning", in the case that we do not
6282 have a consensus when a .onion request comes in. This can happen
6283 normally while bootstrapping. Fixes bug 27040; bugfix
6286 o Minor bugfixes (onion service v3):
6287 - When the onion service directory can't be created or has the wrong
6288 permissions, do not log a stack trace. Fixes bug 27335; bugfix
6291 o Minor bugfixes (OS compatibility):
6292 - Properly handle configuration changes that move a listener to/from
6293 wildcard IP address. If the first attempt to bind a socket fails,
6294 close the old listener and try binding the socket again. Fixes bug
6295 17873; bugfix on 0.0.8pre-1.
6297 o Minor bugfixes (performance)::
6298 - Rework node_is_a_configured_bridge() to no longer call
6299 node_get_all_orports(), which was performing too many memory
6300 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
6302 o Minor bugfixes (relay statistics):
6303 - Update relay descriptor on bandwidth changes only when the uptime
6304 is smaller than 24h, in order to reduce the efficiency of guard
6305 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
6307 o Minor bugfixes (relays):
6308 - Consider the fact that we'll be making direct connections to our
6309 entry and guard nodes when computing the fraction of nodes that
6310 have their descriptors. Also, if we are using bridges and there is
6311 at least one bridge with a full descriptor, treat the fraction of
6312 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
6313 Patch by Neel Chauhan.
6314 - Update the message logged on relays when DirCache is disabled.
6315 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
6316 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
6318 o Minor bugfixes (rust, protover):
6319 - Compute protover votes correctly in the rust version of the
6320 protover code. Previously, the protover rewrite in 24031 allowed
6321 repeated votes from the same voter for the same protocol version
6322 to be counted multiple times in protover_compute_vote(). Fixes bug
6323 27649; bugfix on 0.3.3.5-rc.
6324 - Reject protover names that contain invalid characters. Fixes bug
6325 27687; bugfix on 0.3.3.1-alpha.
6327 o Minor bugfixes (testing):
6328 - Fix two unit tests to work when HOME environment variable is not
6329 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
6330 - If a unit test running in a subprocess exits abnormally or with a
6331 nonzero status code, treat the test as having failed, even if the
6332 test reported success. Without this fix, memory leaks don't cause
6333 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
6334 bugfix on 0.2.2.4-alpha.
6335 - When logging a version mismatch in our openssl_version tests,
6336 report the actual offending version strings. Fixes bug 26152;
6337 bugfix on 0.2.9.1-alpha.
6338 - Fix forking tests on Windows when there is a space somewhere in
6339 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
6341 o Code simplification and refactoring:
6342 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
6343 longer needed. Closes ticket 26502.
6344 - Include paths to header files within Tor are now qualified by
6345 directory within the top-level src directory.
6346 - Many structures have been removed from the centralized "or.h"
6347 header, and moved into their own headers. This will allow us to
6348 reduce the number of places in the code that rely on each
6349 structure's contents and layout. Closes ticket 26383.
6350 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
6351 - Remove GetAdaptersAddresses_fn_t. The code that used it was
6352 removed as part of the 26481 refactor. Closes ticket 27467.
6353 - Rework Tor SOCKS server code to use Trunnel and benefit from
6354 autogenerated functions for parsing and generating SOCKS wire
6355 format. New implementation is cleaner, more maintainable and
6356 should be less prone to heartbleed-style vulnerabilities.
6357 Implements a significant fraction of ticket 3569.
6358 - Split sampled_guards_update_from_consensus() and
6359 select_entry_guard_for_circuit() into subfunctions. In
6360 entry_guards_update_primary() unite three smartlist enumerations
6361 into one and move smartlist comparison code out of the function.
6362 Closes ticket 21349.
6363 - Tor now assumes that you have standards-conformant stdint.h and
6364 inttypes.h headers when compiling. Closes ticket 26626.
6365 - Unify our bloom filter logic. Previously we had two copies of this
6366 code: one for routerlist filtering, and one for address set
6367 calculations. Closes ticket 26510.
6368 - Use the simpler strcmpstart() helper in
6369 rend_parse_v2_service_descriptor instead of strncmp(). Closes
6371 - Utility functions that can perform a DNS lookup are now wholly
6372 separated from those that can't, in separate headers and C
6373 modules. Closes ticket 26526.
6376 - Copy paragraph and URL to Tor's code of conduct document from
6377 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
6378 - Remove old instructions from INSTALL document. Closes ticket 26588.
6379 - Warn users that they should not include MyFamily line(s) in their
6380 torrc when running Tor bridge. Closes ticket 26908.
6383 - Tor no longer supports building with the dmalloc library. For
6384 debugging memory issues, we suggest using gperftools or msan
6385 instead. Closes ticket 26426.
6386 - Tor no longer attempts to run on Windows environments without the
6387 GetAdaptersAddresses() function. This function has existed since
6388 Windows XP, which is itself already older than we support.
6389 - Remove Tor2web functionality for version 2 onion services. The
6390 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
6391 (This feature was never shipped in vanilla Tor and it was only
6392 possible to use this feature by building the support at compile
6393 time. Tor2webMode is not implemented for version 3 onion services.)
6394 Closes ticket 26367.
6397 Changes in version 0.2.9.17 - 2018-09-10
6398 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
6400 o Minor features (compatibility, backport from 0.3.4.8):
6401 - Tell OpenSSL to maintain backward compatibility with previous
6402 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
6403 ciphers are disabled by default. Closes ticket 27344.
6405 o Minor features (continuous integration, backport from 0.3.4.7-rc):
6406 - Enable macOS builds in our Travis CI configuration. Closes
6408 - Install libcap-dev and libseccomp2-dev so these optional
6409 dependencies get tested on Travis CI. Closes ticket 26560.
6410 - Run asciidoc during Travis CI. Implements ticket 27087.
6411 - Use ccache in our Travis CI configuration. Closes ticket 26952.
6413 o Minor features (geoip):
6414 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
6415 Country database. Closes ticket 27089.
6417 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
6418 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
6419 tell the compiler not to include the system malloc implementation.
6420 Fixes bug 20424; bugfix on 0.2.0.20-rc.
6422 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
6423 - Silence a spurious compiler warning on the GetAdaptersAddresses
6424 function pointer cast. This issue is already fixed by 26481 in
6425 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
6426 bugfix on 0.2.3.11-alpha.
6427 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
6428 supported, and always fails. Some compilers warn about the
6429 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
6432 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
6433 - Don't link or search for pthreads when building for Windows, even
6434 if we are using build environment (like mingw) that provides a
6435 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
6437 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
6438 - Skip a pair of unreliable key generation tests on Windows, until
6439 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
6440 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
6442 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
6443 - Pass the module flags to distcheck configure, and log the flags
6444 before running configure. (Backported to 0.2.9 and later as a
6445 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
6447 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
6448 - When a Travis build fails, and showing a log fails, keep trying to
6449 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
6450 - When we use echo in Travis, don't pass a --flag as the first
6451 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
6453 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
6454 - When voting for recommended versions, make sure that all of the
6455 versions are well-formed and parsable. Fixes bug 26485; bugfix
6458 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
6459 - Fix a bug in out sandboxing rules for the openat() syscall.
6460 Previously, no openat() call would be permitted, which would break
6461 filesystem operations on recent glibc versions. Fixes bug 25440;
6462 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
6464 o Minor bugfixes (onion services, backport from 0.3.4.8):
6465 - Silence a spurious compiler warning in
6466 rend_client_send_introduction(). Fixes bug 27463; bugfix
6469 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
6470 - Log a protocol warning when single onion services or Tor2web clients
6471 fail to authenticate direct connections to relays.
6472 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
6474 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
6475 - Disable core dumps in test_bt.sh, to avoid failures in "make
6476 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
6478 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
6479 - Before running make test-network-all, delete old logs and test
6480 result files, to avoid spurious failures. Fixes bug 27295; bugfix
6483 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
6484 - Our "tortls/cert_matches_key" unit test no longer relies on
6485 OpenSSL internals. Previously, it relied on unsupported OpenSSL
6486 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
6487 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
6489 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
6490 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
6491 27185; bugfix on 0.2.2.2-alpha.
6494 Changes in version 0.3.2.12 - 2018-09-10
6495 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
6497 o Minor features (compatibility, backport from 0.3.4.8):
6498 - Tell OpenSSL to maintain backward compatibility with previous
6499 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
6500 ciphers are disabled by default. Closes ticket 27344.
6502 o Minor features (continuous integration, backport from 0.3.4.7-rc):
6503 - Enable macOS builds in our Travis CI configuration. Closes
6505 - Install libcap-dev and libseccomp2-dev so these optional
6506 dependencies get tested on Travis CI. Closes ticket 26560.
6507 - Run asciidoc during Travis CI. Implements ticket 27087.
6508 - Use ccache in our Travis CI configuration. Closes ticket 26952.
6510 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
6511 - Use cargo cache in our Travis CI configuration. Closes
6514 o Minor features (controller, backport from 0.3.4.6-rc):
6515 - The control port now exposes the list of HTTPTunnelPorts and
6516 ExtOrPorts via GETINFO net/listeners/httptunnel and
6517 net/listeners/extor respectively. Closes ticket 26647.
6519 o Minor features (directory authorities, backport from 0.3.4.7-rc):
6520 - Authorities no longer vote to make the subprotocol version
6521 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
6522 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
6524 o Minor features (geoip):
6525 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
6526 Country database. Closes ticket 27089.
6528 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
6529 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
6530 tell the compiler not to include the system malloc implementation.
6531 Fixes bug 20424; bugfix on 0.2.0.20-rc.
6532 - Don't try to use a pragma to temporarily disable the
6533 -Wunused-const-variable warning if the compiler doesn't support
6534 it. Fixes bug 26785; bugfix on 0.3.2.11.
6536 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
6537 - Silence a spurious compiler warning on the GetAdaptersAddresses
6538 function pointer cast. This issue is already fixed by 26481 in
6539 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
6540 bugfix on 0.2.3.11-alpha.
6541 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
6542 supported, and always fails. Some compilers warn about the
6543 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
6546 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
6547 - Don't link or search for pthreads when building for Windows, even
6548 if we are using build environment (like mingw) that provides a
6549 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
6551 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
6552 - Skip a pair of unreliable key generation tests on Windows, until
6553 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
6554 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
6556 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
6557 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
6558 - Pass the module flags to distcheck configure, and log the flags
6559 before running configure. (Backported to 0.2.9 and later as a
6560 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
6562 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
6563 - When a Travis build fails, and showing a log fails, keep trying to
6564 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
6565 - When we use echo in Travis, don't pass a --flag as the first
6566 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
6568 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
6569 - When voting for recommended versions, make sure that all of the
6570 versions are well-formed and parsable. Fixes bug 26485; bugfix
6573 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
6574 - Fix a bug in out sandboxing rules for the openat() syscall.
6575 Previously, no openat() call would be permitted, which would break
6576 filesystem operations on recent glibc versions. Fixes bug 25440;
6577 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
6579 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
6580 - Improve the log message when connection initiators fail to
6581 authenticate direct connections to relays. Fixes bug 26927; bugfix
6584 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
6585 - Fix bug that causes services to not ever rotate their descriptors
6586 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
6589 o Minor bugfixes (onion services, backport from 0.3.4.8):
6590 - Silence a spurious compiler warning in
6591 rend_client_send_introduction(). Fixes bug 27463; bugfix
6594 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
6595 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
6597 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
6598 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
6599 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
6600 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
6602 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
6603 - Log a protocol warning when single onion services or Tor2web clients
6604 fail to authenticate direct connections to relays.
6605 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
6607 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
6608 - Disable core dumps in test_bt.sh, to avoid failures in "make
6609 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
6611 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
6612 - When running make test-network-all, use the mixed+hs-v2 network.
6613 (A previous fix to chutney removed v3 onion services from the
6614 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
6615 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
6616 - Before running make test-network-all, delete old logs and test
6617 result files, to avoid spurious failures. Fixes bug 27295; bugfix
6620 o Minor bugfixes (testing, openssl compatibility):
6621 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
6622 internals. Previously, it relied on unsupported OpenSSL behavior in
6623 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
6624 bugfix on 0.2.5.1-alpha.
6626 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
6627 - Our "tortls/cert_matches_key" unit test no longer relies on
6628 OpenSSL internals. Previously, it relied on unsupported OpenSSL
6629 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
6630 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
6632 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
6633 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
6634 27185; bugfix on 0.2.2.2-alpha.
6637 Changes in version 0.3.3.10 - 2018-09-10
6638 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
6640 o Minor features (bug workaround, backport from 0.3.4.7-rc):
6641 - Compile correctly on systems that provide the C11 stdatomic.h
6642 header, but where C11 atomic functions don't actually compile.
6643 Closes ticket 26779; workaround for Debian issue 903709.
6645 o Minor features (compatibility, backport from 0.3.4.8):
6646 - Tell OpenSSL to maintain backward compatibility with previous
6647 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
6648 ciphers are disabled by default. Closes ticket 27344.
6650 o Minor features (continuous integration, backport from 0.3.4.7-rc):
6651 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
6652 - Enable macOS builds in our Travis CI configuration. Closes
6654 - Install libcap-dev and libseccomp2-dev so these optional
6655 dependencies get tested on Travis CI. Closes ticket 26560.
6656 - Run asciidoc during Travis CI. Implements ticket 27087.
6657 - Use ccache in our Travis CI configuration. Closes ticket 26952.
6659 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
6660 - Use cargo cache in our Travis CI configuration. Closes
6663 o Minor features (controller, backport from 0.3.4.6-rc):
6664 - The control port now exposes the list of HTTPTunnelPorts and
6665 ExtOrPorts via GETINFO net/listeners/httptunnel and
6666 net/listeners/extor respectively. Closes ticket 26647.
6668 o Minor features (directory authorities, backport from 0.3.4.7-rc):
6669 - Authorities no longer vote to make the subprotocol version
6670 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
6671 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
6673 o Minor features (geoip):
6674 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
6675 Country database. Closes ticket 27089.
6677 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
6678 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
6679 tell the compiler not to include the system malloc implementation.
6680 Fixes bug 20424; bugfix on 0.2.0.20-rc.
6681 - Don't try to use a pragma to temporarily disable the
6682 -Wunused-const-variable warning if the compiler doesn't support
6683 it. Fixes bug 26785; bugfix on 0.3.2.11.
6685 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
6686 - Silence a spurious compiler warning on the GetAdaptersAddresses
6687 function pointer cast. This issue is already fixed by 26481 in
6688 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
6689 bugfix on 0.2.3.11-alpha.
6690 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
6691 supported, and always fails. Some compilers warn about the
6692 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
6695 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
6696 - Don't link or search for pthreads when building for Windows, even
6697 if we are using build environment (like mingw) that provides a
6698 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
6700 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
6701 - Skip a pair of unreliable key generation tests on Windows, until
6702 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
6703 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
6705 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
6706 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
6707 - Pass the module flags to distcheck configure, and log the flags
6708 before running configure. (Backported to 0.2.9 and later as a
6709 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
6711 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
6712 - When a Travis build fails, and showing a log fails, keep trying to
6713 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
6714 - When we use echo in Travis, don't pass a --flag as the first
6715 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
6717 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
6718 - When voting for recommended versions, make sure that all of the
6719 versions are well-formed and parsable. Fixes bug 26485; bugfix
6722 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
6723 - Always call tor_free_all() when leaving tor_run_main(). When we
6724 did not, restarting tor in-process would cause an assertion
6725 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
6727 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
6728 - Fix a bug in our sandboxing rules for the openat() syscall.
6729 Previously, no openat() call would be permitted, which would break
6730 filesystem operations on recent glibc versions. Fixes bug 25440;
6731 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
6733 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
6734 - Improve the log message when connection initiators fail to
6735 authenticate direct connections to relays. Fixes bug 26927; bugfix
6738 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
6739 - Fix bug that causes services to not ever rotate their descriptors
6740 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
6743 o Minor bugfixes (onion services, backport from 0.3.4.8):
6744 - Silence a spurious compiler warning in
6745 rend_client_send_introduction(). Fixes bug 27463; bugfix
6748 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
6749 - Work around two different bugs in the OS X 10.10 and later SDKs
6750 that would prevent us from successfully targeting earlier versions
6751 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
6753 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
6754 - Fix compilation of the unit tests on GNU/Hurd, which does not
6755 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
6758 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
6759 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
6761 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
6762 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
6763 - Protover parsing was accepting the presence of whitespace in
6764 version strings, which the C implementation would choke on, e.g.
6765 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
6766 - Protover parsing was ignoring a 2nd hyphen and everything after
6767 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
6769 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
6770 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
6771 - cd to ${abs_top_builddir}/src/rust before running cargo in
6772 src/test/test_rust.sh. This makes the working directory consistent
6773 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
6775 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
6776 - Log a protocol warning when single onion services or Tor2web clients
6777 fail to authenticate direct connections to relays.
6778 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
6780 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
6781 - Disable core dumps in test_bt.sh, to avoid failures in "make
6782 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
6784 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
6785 - When running make test-network-all, use the mixed+hs-v2 network.
6786 (A previous fix to chutney removed v3 onion services from the
6787 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
6788 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
6789 - Before running make test-network-all, delete old logs and test
6790 result files, to avoid spurious failures. Fixes bug 27295; bugfix
6793 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
6794 - Our "tortls/cert_matches_key" unit test no longer relies on
6795 OpenSSL internals. Previously, it relied on unsupported OpenSSL
6796 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
6797 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
6799 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
6800 - Stop sending ed25519 link specifiers in v3 onion service introduce
6801 cells and descriptors, when the rendezvous or introduction point
6802 doesn't support ed25519 link authentication. Fixes bug 26627;
6803 bugfix on 0.3.2.4-alpha.
6805 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
6806 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
6807 27185; bugfix on 0.2.2.2-alpha.
6810 Changes in version 0.3.4.8 - 2018-09-10
6811 Tor 0.3.4.8 is the first stable release in its series; it includes
6812 compilation and portability fixes.
6814 The Tor 0.3.4 series includes improvements for running Tor in
6815 low-power and embedded environments, which should help performance in
6816 general. We've begun work on better modularity, and included preliminary
6817 changes on the directory authority side to accommodate a new bandwidth
6818 measurement system. We've also integrated more continuous-integration
6819 systems into our development process, and made corresponding changes to
6820 Tor's testing infrastructure. Finally, we've continued to refine
6821 our anti-denial-of-service code.
6823 Below are the changes since 0.3.4.7-rc. For a complete list of changes
6824 since 0.3.3.9, see the ReleaseNotes file.
6826 o Minor features (compatibility):
6827 - Tell OpenSSL to maintain backward compatibility with previous
6828 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
6829 ciphers are disabled by default. Closes ticket 27344.
6831 o Minor features (continuous integration):
6832 - Log the compiler path and version during Appveyor builds.
6833 Implements ticket 27449.
6834 - Show config.log and test-suite.log after failed Appveyor builds.
6835 Also upload the zipped full logs as a build artifact. Implements
6838 o Minor bugfixes (compilation):
6839 - Silence a spurious compiler warning on the GetAdaptersAddresses
6840 function pointer cast. This issue is already fixed by 26481 in
6841 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
6842 bugfix on 0.2.3.11-alpha.
6843 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
6844 supported, and always fails. Some compilers warn about the
6845 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
6848 o Minor bugfixes (continuous integration):
6849 - Disable gcc hardening in Appveyor Windows 64-bit builds. As of
6850 August 29 2018, Appveyor images come with gcc 8.2.0 by default.
6851 Executables compiled for 64-bit Windows with this version of gcc
6852 crash when Tor's --enable-gcc-hardening flag is set. Fixes bug
6853 27460; bugfix on 0.3.4.1-alpha.
6854 - When a Travis build fails, and showing a log fails, keep trying to
6855 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
6856 - When we use echo in Travis, don't pass a --flag as the first
6857 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
6859 o Minor bugfixes (onion services):
6860 - Silence a spurious compiler warning in
6861 rend_client_send_introduction(). Fixes bug 27463; bugfix
6864 o Minor bugfixes (testing, chutney):
6865 - When running make test-network-all, use the mixed+hs-v2 network.
6866 (A previous fix to chutney removed v3 onion services from the
6867 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
6868 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
6869 - Before running make test-network-all, delete old logs and test
6870 result files, to avoid spurious failures. Fixes bug 27295; bugfix
6873 Changes in version 0.3.4.7-rc - 2018-08-24
6874 Tor 0.3.4.7-rc fixes several small compilation, portability, and
6875 correctness issues in previous versions of Tor. This version is a
6876 release candidate: if no serious bugs are found, we expect that the
6877 stable 0.3.4 release will be (almost) the same as this release.
6879 o Minor features (bug workaround):
6880 - Compile correctly on systems that provide the C11 stdatomic.h
6881 header, but where C11 atomic functions don't actually compile.
6882 Closes ticket 26779; workaround for Debian issue 903709.
6884 o Minor features (continuous integration):
6885 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
6886 - Enable macOS builds in our Travis CI configuration. Closes
6888 - Install libcap-dev and libseccomp2-dev so these optional
6889 dependencies get tested on Travis CI. Closes ticket 26560.
6890 - Only post Appveyor IRC notifications when the build fails.
6891 Implements ticket 27275.
6892 - Run asciidoc during Travis CI. Implements ticket 27087.
6893 - Use ccache in our Travis CI configuration. Closes ticket 26952.
6895 o Minor features (continuous integration, rust):
6896 - Use cargo cache in our Travis CI configuration. Closes
6899 o Minor features (directory authorities):
6900 - Authorities no longer vote to make the subprotocol version
6901 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
6902 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
6904 o Minor features (geoip):
6905 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
6906 Country database. Closes ticket 27089.
6908 o Minor bugfixes (compilation, windows):
6909 - Don't link or search for pthreads when building for Windows, even
6910 if we are using build environment (like mingw) that provides a
6911 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
6913 o Minor bugfixes (continuous integration):
6914 - Improve Appveyor CI IRC logging. Generate correct branches and
6915 URLs for pull requests and tags. Use unambiguous short commits.
6916 Fixes bug 26979; bugfix on master.
6917 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
6918 - Pass the module flags to distcheck configure, and log the flags
6919 before running configure. (Backported to 0.2.9 and later as a
6920 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
6922 o Minor bugfixes (in-process restart):
6923 - Always call tor_free_all() when leaving tor_run_main(). When we
6924 did not, restarting tor in-process would cause an assertion
6925 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
6927 o Minor bugfixes (linux seccomp2 sandbox):
6928 - Fix a bug in out sandboxing rules for the openat() syscall.
6929 Previously, no openat() call would be permitted, which would break
6930 filesystem operations on recent glibc versions. Fixes bug 25440;
6931 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
6933 o Minor bugfixes (onion services):
6934 - Fix bug that causes services to not ever rotate their descriptors
6935 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
6938 o Minor bugfixes (portability):
6939 - Fix compilation of the unit tests on GNU/Hurd, which does not
6940 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
6943 o Minor bugfixes (rust):
6944 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
6946 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
6947 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
6948 - Protover parsing was accepting the presence of whitespace in
6949 version strings, which the C implementation would choke on, e.g.
6950 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
6951 - Protover parsing was ignoring a 2nd hyphen and everything after
6952 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
6954 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
6955 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
6956 - cd to ${abs_top_builddir}/src/rust before running cargo in
6957 src/test/test_rust.sh. This makes the working directory consistent
6958 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
6960 o Minor bugfixes (testing, bootstrap):
6961 - When calculating bootstrap progress, check exit policies and the
6962 exit flag. Previously, Tor would only check the exit flag, which
6963 caused race conditions in small and fast networks like chutney.
6964 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
6966 o Minor bugfixes (testing, openssl compatibility):
6967 - Our "tortls/cert_matches_key" unit test no longer relies on
6968 OpenSSL internals. Previously, it relied on unsupported OpenSSL
6969 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
6970 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
6972 o Minor bugfixes (Windows, compilation):
6973 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
6974 27185; bugfix on 0.2.2.2-alpha.
6977 Changes in version 0.3.4.6-rc - 2018-08-06
6978 Tor 0.3.4.6-rc fixes several small compilation, portability, and
6979 correctness issues in previous versions of Tor. This version is a
6980 release candidate: if no serious bugs are found, we expect that the
6981 stable 0.3.4 release will be (almost) the same as this release.
6983 o Major bugfixes (event scheduler):
6984 - When we enable a periodic event, schedule it in the event loop
6985 rather than running it immediately. Previously, we would re-run
6986 periodic events immediately in the middle of (for example)
6987 changing our options, with unpredictable effects. Fixes bug 27003;
6988 bugfix on 0.3.4.1-alpha.
6990 o Minor features (compilation):
6991 - When building Tor, prefer to use Python 3 over Python 2, and more
6992 recent (contemplated) versions over older ones. Closes
6994 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
6995 tell the compiler not to include the system malloc implementation.
6996 Fixes bug 20424; bugfix on 0.2.0.20-rc.
6997 - Don't try to use a pragma to temporarily disable the
6998 -Wunused-const-variable warning if the compiler doesn't support
6999 it. Fixes bug 26785; bugfix on 0.3.2.11.
7001 o Minor bugfixes (continuous integration):
7002 - Skip a pair of unreliable key generation tests on Windows, until
7003 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
7004 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
7006 o Minor features (controller):
7007 - The control port now exposes the list of HTTPTunnelPorts and
7008 ExtOrPorts via GETINFO net/listeners/httptunnel and
7009 net/listeners/extor respectively. Closes ticket 26647.
7011 o Minor bugfixes (directory authority):
7012 - When voting for recommended versions, make sure that all of the
7013 versions are well-formed and parsable. Fixes bug 26485; bugfix
7016 o Minor features (geoip):
7017 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
7018 Country database. Closes ticket 26674.
7020 o Minor features (Rust, portability):
7021 - Rust cross-compilation is now supported. Closes ticket 25895.
7023 o Minor bugfixes (compilation):
7024 - Update build system so that tor builds again with --disable-unittests
7025 after recent refactoring. Fixes bug 26789; bugfix on 0.3.4.3-alpha.
7026 - Fix a compilation warning on some versions of GCC when building
7027 code that calls routerinfo_get_my_routerinfo() twice, assuming
7028 that the second call will succeed if the first one did. Fixes bug
7029 26269; bugfix on 0.2.8.2-alpha.
7031 o Minor bugfixes (controller):
7032 - Report the port correctly when a port is configured to bind to
7033 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
7034 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
7035 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
7036 on 0.3.3.1-alpha. Patch by "akwizgran".
7038 o Minor bugfixes (correctness, flow control):
7039 - Upon receiving a stream-level SENDME cell, verify that our window
7040 has not grown too large. Fixes bug 26214; bugfix on svn
7043 o Minor bugfixes (memory, correctness):
7044 - Fix a number of small memory leaks identified by coverity. Fixes
7045 bug 26467; bugfix on numerous Tor versions.
7047 o Minor bugfixes (logging):
7048 - Improve the log message when connection initiators fail to
7049 authenticate direct connections to relays. Fixes bug 26927; bugfix
7052 o Minor bugfixes (portability):
7053 - Avoid a compilation error in test_bwmgt.c on Solaris 10. Fixes bug
7054 26994; bugfix on 0.3.4.1-alpha.
7055 - Work around two different bugs in the OS X 10.10 and later SDKs
7056 that would prevent us from successfully targeting earlier versions
7057 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
7059 o Minor bugfixes (single onion services, Tor2web):
7060 - Log a protocol warning when single onion services or Tor2web
7061 clients fail to authenticate direct connections to relays. Fixes
7062 bug 26924; bugfix on 0.2.9.1-alpha.
7064 o Minor bugfixes (testing):
7065 - Disable core dumps in test_bt.sh, to avoid failures in "make
7066 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
7068 o Minor bugfixes (testing, compatibility):
7069 - When running the ntor_ref.py and hs_ntor_ref.py tests, make sure
7070 only to pass strings (rather than "bytes" objects) to the Python
7071 subprocess module. Python 3 on Windows seems to require this.
7072 Fixes bug 26535; bugfix on 0.2.5.5-alpha (for ntor_ref.py) and
7073 0.3.1.1-alpha (for hs_ntor_ref.py).
7075 o Minor bugfixes (v3 onion services):
7076 - Stop sending ed25519 link specifiers in v3 onion service introduce
7077 cells and descriptors, when the rendezvous or introduction point
7078 doesn't support ed25519 link authentication. Fixes bug 26627;
7079 bugfix on 0.3.2.4-alpha.
7082 Changes in version 0.3.4.5-rc - 2018-07-13
7083 Tor 0.3.4.5-rc moves to a new bridge authority, meaning people running
7084 bridge relays should upgrade.
7086 o Directory authority changes:
7087 - The "Bifroest" bridge authority has been retired; the new bridge
7088 authority is "Serge", and it is operated by George from the
7089 TorBSD project. Closes ticket 26771.
7092 Changes in version 0.3.3.9 - 2018-07-13
7093 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
7094 bridge relays should upgrade.
7096 o Directory authority changes:
7097 - The "Bifroest" bridge authority has been retired; the new bridge
7098 authority is "Serge", and it is operated by George from the
7099 TorBSD project. Closes ticket 26771.
7102 Changes in version 0.3.2.11 - 2018-07-13
7103 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
7104 bridge relays should upgrade. We also take this opportunity to backport
7107 o Directory authority changes:
7108 - The "Bifroest" bridge authority has been retired; the new bridge
7109 authority is "Serge", and it is operated by George from the
7110 TorBSD project. Closes ticket 26771.
7112 o Directory authority changes (backport from 0.3.3.7):
7113 - Add an IPv6 address for the "dannenberg" directory authority.
7114 Closes ticket 26343.
7116 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
7117 - When directory authorities read a zero-byte bandwidth file, they
7118 would previously log a warning with the contents of an
7119 uninitialised buffer. They now log a warning about the empty file
7120 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
7122 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
7123 - Correctly detect when onion services get disabled after HUP. Fixes
7124 bug 25761; bugfix on 0.3.2.1.
7126 o Minor features (sandbox, backport from 0.3.3.4-alpha):
7127 - Explicitly permit the poll() system call when the Linux
7128 seccomp2-based sandbox is enabled: apparently, some versions of
7129 libc use poll() when calling getpwnam(). Closes ticket 25313.
7131 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
7132 - Update the Travis CI configuration to use the stable Rust channel,
7133 now that we have decided to require that. Closes ticket 25714.
7135 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
7136 - Our .travis.yml configuration now includes support for testing the
7137 results of "make distcheck". (It's not uncommon for "make check"
7138 to pass but "make distcheck" to fail.) Closes ticket 25814.
7139 - Our Travis CI configuration now integrates with the Coveralls
7140 coverage analysis tool. Closes ticket 25818.
7142 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
7143 - Add several checks to detect whether Tor relays are uploading
7144 their descriptors without specifying why they regenerated them.
7145 Diagnostic for ticket 25686.
7147 o Minor features (compilation, backport from 0.3.4.4-rc):
7148 - When building Tor, prefer to use Python 3 over Python 2, and more
7149 recent (contemplated) versions over older ones. Closes
7152 o Minor features (geoip):
7153 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
7154 Country database. Closes ticket 26674.
7156 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
7157 - Upon receiving a malformed connected cell, stop processing the
7158 cell immediately. Previously we would mark the connection for
7159 close, but continue processing the cell as if the connection were
7160 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
7162 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
7163 - Allow the nanosleep() system call, which glibc uses to implement
7164 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
7166 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
7167 - When running the hs_ntor_ref.py test, make sure only to pass
7168 strings (rather than "bytes" objects) to the Python subprocess
7169 module. Python 3 on Windows seems to require this. Fixes bug
7170 26535; bugfix on 0.3.1.1-alpha.
7171 - When running the ntor_ref.py test, make sure only to pass strings
7172 (rather than "bytes" objects) to the Python subprocess module.
7173 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
7176 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
7177 - Work around a change in OpenSSL 1.1.1 where return values that
7178 would previously indicate "no password" now indicate an empty
7179 password. Without this workaround, Tor instances running with
7180 OpenSSL 1.1.1 would accept descriptors that other Tor instances
7181 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
7183 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
7184 - Document that the PerConnBW{Rate,Burst} options will fall back to
7185 their corresponding consensus parameters only if those parameters
7186 are set. Previously we had claimed that these values would always
7187 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
7189 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
7190 - Fix a compilation warning on some versions of GCC when building
7191 code that calls routerinfo_get_my_routerinfo() twice, assuming
7192 that the second call will succeed if the first one did. Fixes bug
7193 26269; bugfix on 0.2.8.2-alpha.
7195 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
7196 - Don't consider Tor running as a client if the ControlPort is open,
7197 but no actual client ports are open. Fixes bug 26062; bugfix
7200 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
7201 - Prevent a possible out-of-bounds smartlist read in
7202 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
7204 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
7205 - Fix a very unlikely (impossible, we believe) null pointer
7206 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
7207 Coverity; this is CID 1430932.
7209 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
7210 - Fix a memory leak when a v3 onion service is configured and gets a
7211 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
7212 - When parsing the descriptor signature, look for the token plus an
7213 extra white-space at the end. This is more correct but also will
7214 allow us to support new fields that might start with "signature".
7215 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
7217 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
7218 - Relays now correctly block attempts to re-extend to the previous
7219 relay by Ed25519 identity. Previously they would warn in this
7220 case, but not actually reject the attempt. Fixes bug 26158; bugfix
7223 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
7224 - Avoid a crash when running with DirPort set but ORPort turned off.
7225 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
7227 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
7228 - Silence unused-const-variable warnings in zstd.h with some GCC
7229 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
7231 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
7232 - Avoid intermittent test failures due to a test that had relied on
7233 onion service introduction point creation finishing within 5
7234 seconds of real clock time. Fixes bug 25450; bugfix
7237 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
7238 - Fix a C99 compliance issue in our configuration script that caused
7239 compilation issues when compiling Tor with certain versions of
7240 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
7242 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
7243 - Fix a number of small memory leaks identified by coverity. Fixes
7244 bug 26467; bugfix on numerous Tor versions.
7246 o Code simplification and refactoring (backport from 0.3.3.5-rc):
7247 - Move the list of default directory authorities to its own file.
7248 Closes ticket 24854. Patch by "beastr0".
7251 Changes in version 0.2.9.16 - 2018-07-13
7252 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
7253 bridge relays should upgrade. We also take this opportunity to backport
7256 o Directory authority changes:
7257 - The "Bifroest" bridge authority has been retired; the new bridge
7258 authority is "Serge", and it is operated by George from the
7259 TorBSD project. Closes ticket 26771.
7261 o Directory authority changes (backport from 0.3.3.7):
7262 - Add an IPv6 address for the "dannenberg" directory authority.
7263 Closes ticket 26343.
7265 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
7266 - When directory authorities read a zero-byte bandwidth file, they
7267 would previously log a warning with the contents of an
7268 uninitialised buffer. They now log a warning about the empty file
7269 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
7271 o Minor features (sandbox, backport from 0.3.3.4-alpha):
7272 - Explicitly permit the poll() system call when the Linux
7273 seccomp2-based sandbox is enabled: apparently, some versions of
7274 libc use poll() when calling getpwnam(). Closes ticket 25313.
7276 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
7277 - Our .travis.yml configuration now includes support for testing the
7278 results of "make distcheck". (It's not uncommon for "make check"
7279 to pass but "make distcheck" to fail.) Closes ticket 25814.
7280 - Our Travis CI configuration now integrates with the Coveralls
7281 coverage analysis tool. Closes ticket 25818.
7283 o Minor features (compilation, backport from 0.3.4.4-rc):
7284 - When building Tor, prefer to use Python 3 over Python 2, and more
7285 recent (contemplated) versions over older ones. Closes
7288 o Minor features (geoip):
7289 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
7290 Country database. Closes ticket 26674.
7292 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
7293 - Upon receiving a malformed connected cell, stop processing the
7294 cell immediately. Previously we would mark the connection for
7295 close, but continue processing the cell as if the connection were
7296 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
7298 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
7299 - Allow the nanosleep() system call, which glibc uses to implement
7300 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
7302 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
7303 - When running the ntor_ref.py test, make sure only to pass strings
7304 (rather than "bytes" objects) to the Python subprocess module.
7305 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
7308 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
7309 - Work around a change in OpenSSL 1.1.1 where return values that
7310 would previously indicate "no password" now indicate an empty
7311 password. Without this workaround, Tor instances running with
7312 OpenSSL 1.1.1 would accept descriptors that other Tor instances
7313 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
7315 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
7316 - Fix a compilation warning on some versions of GCC when building
7317 code that calls routerinfo_get_my_routerinfo() twice, assuming
7318 that the second call will succeed if the first one did. Fixes bug
7319 26269; bugfix on 0.2.8.2-alpha.
7321 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
7322 - Don't consider Tor running as a client if the ControlPort is open,
7323 but no actual client ports are open. Fixes bug 26062; bugfix
7326 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
7327 - Prevent a possible out-of-bounds smartlist read in
7328 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
7330 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
7331 - Fix a very unlikely (impossible, we believe) null pointer
7332 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
7333 Coverity; this is CID 1430932.
7335 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
7336 - Fix a number of small memory leaks identified by coverity. Fixes
7337 bug 26467; bugfix on numerous Tor versions.
7339 o Code simplification and refactoring (backport from 0.3.3.5-rc):
7340 - Move the list of default directory authorities to its own file.
7341 Closes ticket 24854. Patch by "beastr0".
7344 Changes in version 0.3.4.4-rc - 2018-07-09
7345 Tor 0.3.4.4-rc fixes several small compilation, portability, and
7346 correctness issues in previous versions of Tor. This version is a
7347 release candidate: if no serious bugs are found, we expect that the
7348 stable 0.3.4 release will be (almost) the same as this release.
7350 o Minor features (compilation):
7351 - When building Tor, prefer to use Python 3 over Python 2, and more
7352 recent (contemplated) versions over older ones. Closes
7355 o Minor features (geoip):
7356 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
7357 Country database. Closes ticket 26674.
7359 o Minor features (Rust, portability):
7360 - Rust cross-compilation is now supported. Closes ticket 25895.
7362 o Minor bugfixes (compilation):
7363 - Fix a compilation warning on some versions of GCC when building
7364 code that calls routerinfo_get_my_routerinfo() twice, assuming
7365 that the second call will succeed if the first one did. Fixes bug
7366 26269; bugfix on 0.2.8.2-alpha.
7368 o Minor bugfixes (control port):
7369 - Report the port correctly when a port is configured to bind to
7370 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
7371 - Handle the HSADDRESS= argument to the HSPOST command properly.
7372 (Previously, this argument was misparsed and thus ignored.) Fixes
7373 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
7375 o Minor bugfixes (correctness, flow control):
7376 - Upon receiving a stream-level SENDME cell, verify that our window
7377 has not grown too large. Fixes bug 26214; bugfix on svn
7380 o Minor bugfixes (memory, correctness):
7381 - Fix a number of small memory leaks identified by coverity. Fixes
7382 bug 26467; bugfix on numerous Tor versions.
7384 o Minor bugfixes (testing, compatibility):
7385 - When running the hs_ntor_ref.py test, make sure only to pass
7386 strings (rather than "bytes" objects) to the Python subprocess
7387 module. Python 3 on Windows seems to require this. Fixes bug
7388 26535; bugfix on 0.3.1.1-alpha.
7389 - When running the ntor_ref.py test, make sure only to pass strings
7390 (rather than "bytes" objects) to the Python subprocess module.
7391 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
7395 Changes in version 0.3.3.8 - 2018-07-09
7396 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
7397 fixes for a memory leak affecting directory authorities.
7399 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
7400 - Stop leaking memory on directory authorities when planning to
7401 vote. This bug was crashing authorities by exhausting their
7402 memory. Fixes bug 26435; bugfix on 0.3.3.6.
7404 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
7405 - Make sure that failing tests in Rust will actually cause the build
7406 to fail: previously, they were ignored. Fixes bug 26258; bugfix
7409 o Minor features (compilation, backport from 0.3.4.4-rc):
7410 - When building Tor, prefer to use Python 3 over Python 2, and more
7411 recent (contemplated) versions over older ones. Closes
7414 o Minor features (geoip):
7415 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
7416 Country database. Closes ticket 26674.
7418 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
7419 - Add several checks to detect whether Tor relays are uploading
7420 their descriptors without specifying why they regenerated them.
7421 Diagnostic for ticket 25686.
7423 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
7424 - Don't count path selection failures as circuit build failures.
7425 This change should eliminate cases where Tor blames its guard or
7426 the network for situations like insufficient microdescriptors
7427 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
7430 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
7431 - Fix a compilation warning on some versions of GCC when building
7432 code that calls routerinfo_get_my_routerinfo() twice, assuming
7433 that the second call will succeed if the first one did. Fixes bug
7434 26269; bugfix on 0.2.8.2-alpha.
7436 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
7437 - Handle the HSADDRESS= argument to the HSPOST command properly.
7438 (Previously, this argument was misparsed and thus ignored.) Fixes
7439 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
7441 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
7442 - Fix a number of small memory leaks identified by coverity. Fixes
7443 bug 26467; bugfix on numerous Tor versions.
7445 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
7446 - Relays now correctly block attempts to re-extend to the previous
7447 relay by Ed25519 identity. Previously they would warn in this
7448 case, but not actually reject the attempt. Fixes bug 26158; bugfix
7451 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
7452 - When shutting down, Tor now clears all the flags in the control.c
7453 module. This should prevent a bug where authentication cookies are
7454 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
7456 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
7457 - When running the hs_ntor_ref.py test, make sure only to pass
7458 strings (rather than "bytes" objects) to the Python subprocess
7459 module. Python 3 on Windows seems to require this. Fixes bug
7460 26535; bugfix on 0.3.1.1-alpha.
7461 - When running the ntor_ref.py test, make sure only to pass strings
7462 (rather than "bytes" objects) to the Python subprocess module.
7463 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
7467 Changes in version 0.3.4.3-alpha - 2018-06-26
7468 Tor 0.3.4.3-alpha fixes several bugs in earlier versions, including
7469 one that was causing stability issues on directory authorities.
7471 o Major bugfixes (directory authority):
7472 - Stop leaking memory on directory authorities when planning to
7473 vote. This bug was crashing authorities by exhausting their
7474 memory. Fixes bug 26435; bugfix on 0.3.3.6.
7476 o Major bugfixes (rust, testing):
7477 - Make sure that failing tests in Rust will actually cause the build
7478 to fail: previously, they were ignored. Fixes bug 26258; bugfix
7481 o Minor feature (directory authorities):
7482 - Stop warning about incomplete bw lines before the first complete
7483 bw line has been found, so that additional header lines can be
7484 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
7486 o Minor features (relay, diagnostic):
7487 - Add several checks to detect whether Tor relays are uploading
7488 their descriptors without specifying why they regenerated them.
7489 Diagnostic for ticket 25686.
7491 o Minor features (unit tests):
7492 - Test complete bandwidth measurements files, and test that
7493 incomplete bandwidth lines only give warnings when the end of the
7494 header has not been detected. Fixes bug 25947; bugfix
7497 o Minor bugfixes (compilation):
7498 - Refrain from compiling unit testing related object files when
7499 --disable-unittests is set to configure script. Fixes bug 24891;
7500 bugfix on 0.2.5.1-alpha.
7501 - When linking the libtor_testing.a library, only include the
7502 dirauth object files once. Previously, they were getting added
7503 twice. Fixes bug 26402; bugfix on 0.3.4.1-alpha.
7504 - The --enable-fatal-warnings flag now affects Rust code as well.
7505 Closes ticket 26245.
7507 o Minor bugfixes (onion services):
7508 - Recompute some consensus information after detecting a clock jump,
7509 or after transitioning from a non-live consensus to a live
7510 consensus. We do this to avoid having an outdated state, and
7511 miscalculating the index for next-generation onion services. Fixes
7512 bug 24977; bugfix on 0.3.2.1-alpha.
7514 o Minor bugfixes (relay):
7515 - Relays now correctly block attempts to re-extend to the previous
7516 relay by Ed25519 identity. Previously they would warn in this
7517 case, but not actually reject the attempt. Fixes bug 26158; bugfix
7520 o Minor bugfixes (testing):
7521 - Fix compilation of the doctests in the Rust crypto crate. Fixes
7522 bug 26415; bugfix on 0.3.4.1-alpha.
7523 - Instead of trying to read the geoip configuration files from
7524 within the unit tests, instead create our own ersatz files with
7525 just enough geoip data in the format we expect. Trying to read
7526 from the source directory created problems on Windows with mingw,
7527 where the build system's paths are not the same as the platform's
7528 paths. Fixes bug 25787; bugfix on 0.3.4.1-alpha.
7529 - Refrain from trying to get an item from an empty smartlist in
7530 test_bridges_clear_bridge_list. Set DEBUG_SMARTLIST in unit tests
7531 to catch improper smartlist usage. Furthermore, enable
7532 DEBUG_SMARTLIST globally when build is configured with fragile
7533 hardening. Fixes bug 26196; bugfix on 0.3.4.1-alpha.
7536 Changes in version 0.3.3.7 - 2018-06-12
7537 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
7538 fixes for bugs affecting compatibility and stability.
7540 o Directory authority changes:
7541 - Add an IPv6 address for the "dannenberg" directory authority.
7542 Closes ticket 26343.
7544 o Minor features (geoip):
7545 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
7546 Country database. Closes ticket 26351.
7548 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
7549 - Work around a change in OpenSSL 1.1.1 where return values that
7550 would previously indicate "no password" now indicate an empty
7551 password. Without this workaround, Tor instances running with
7552 OpenSSL 1.1.1 would accept descriptors that other Tor instances
7553 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
7555 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
7556 - Silence unused-const-variable warnings in zstd.h with some GCC
7557 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
7559 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
7560 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
7561 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
7562 miscounting the total number of circuits for these field values.)
7563 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
7565 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
7566 - Prevent a possible out-of-bounds smartlist read in
7567 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
7569 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
7570 - Only select relays when they have the descriptors we prefer to use
7571 for them. This change fixes a bug where we could select a relay
7572 because it had _some_ descriptor, but reject it later with a
7573 nonfatal assertion error because it didn't have the exact one we
7574 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
7577 Changes in version 0.3.4.2-alpha - 2018-06-12
7578 Tor 0.3.4.2-alpha fixes several minor bugs in the previous alpha
7579 release, and forward-ports an authority-only security fix from 0.3.3.6.
7581 o Directory authority changes:
7582 - Add an IPv6 address for the "dannenberg" directory authority.
7583 Closes ticket 26343.
7585 o Major bugfixes (security, directory authority, denial-of-service, also in 0.3.3.6):
7586 - Fix a bug that could have allowed an attacker to force a directory
7587 authority to use up all its RAM by passing it a maliciously
7588 crafted protocol versions string. Fixes bug 25517; bugfix on
7589 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
7591 o Minor features (continuous integration):
7592 - Add the necessary configuration files for continuous integration
7593 testing on Windows, via the Appveyor platform. Closes ticket
7594 25549. Patches from Marcin Cieślak and Isis Lovecruft.
7596 o Minor features (geoip):
7597 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
7598 Country database. Closes ticket 26351.
7600 o Minor bugfixes (compatibility, openssl):
7601 - Work around a change in OpenSSL 1.1.1 where return values that
7602 would previously indicate "no password" now indicate an empty
7603 password. Without this workaround, Tor instances running with
7604 OpenSSL 1.1.1 would accept descriptors that other Tor instances
7605 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
7607 o Minor bugfixes (compilation):
7608 - Silence unused-const-variable warnings in zstd.h with some GCC
7609 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
7610 - Fix compilation when using OpenSSL 1.1.0 with the "no-deprecated"
7611 flag enabled. Fixes bug 26156; bugfix on 0.3.4.1-alpha.
7612 - Avoid a compiler warning when casting the return value of
7613 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
7614 26283; bugfix on 0.2.4.10-alpha.
7616 o Minor bugfixes (control port):
7617 - Do not count 0-length RELAY_COMMAND_DATA cells as valid data in
7618 CIRC_BW events. Previously, such cells were counted entirely in
7619 the OVERHEAD field. Now they are not. Fixes bug 26259; bugfix
7622 o Minor bugfixes (controller):
7623 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
7624 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
7625 miscounting the total number of circuits for these field values.)
7626 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
7628 o Minor bugfixes (hardening):
7629 - Prevent a possible out-of-bounds smartlist read in
7630 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
7632 o Minor bugfixes (onion services):
7633 - Fix a bug that blocked the creation of ephemeral v3 onion
7634 services. Fixes bug 25939; bugfix on 0.3.4.1-alpha.
7636 o Minor bugfixes (test coverage tools):
7637 - Update our "cov-diff" script to handle output from the latest
7638 version of gcov, and to remove extraneous timestamp information
7639 from its output. Fixes bugs 26101 and 26102; bugfix
7643 Changes in version 0.3.3.6 - 2018-05-22
7644 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
7645 backports several important fixes from the 0.3.4.1-alpha.
7647 The Tor 0.3.3 series includes controller support and other
7648 improvements for v3 onion services, official support for embedding Tor
7649 within other applications, and our first non-trivial module written in
7650 the Rust programming language. (Rust is still not enabled by default
7651 when building Tor.) And as usual, there are numerous other smaller
7652 bugfixes, features, and improvements.
7654 Below are the changes since 0.3.3.5-rc. For a list of all changes
7655 since 0.3.2.10, see the ReleaseNotes file.
7657 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
7658 - When directory authorities read a zero-byte bandwidth file, they
7659 would previously log a warning with the contents of an
7660 uninitialised buffer. They now log a warning about the empty file
7661 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
7663 o Major bugfixes (security, directory authority, denial-of-service):
7664 - Fix a bug that could have allowed an attacker to force a directory
7665 authority to use up all its RAM by passing it a maliciously
7666 crafted protocol versions string. Fixes bug 25517; bugfix on
7667 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
7669 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
7670 - Avoid a rare assertion failure in the circuit build timeout code
7671 if we fail to allow any circuits to actually complete. Fixes bug
7672 25733; bugfix on 0.2.2.2-alpha.
7674 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
7675 - Avoid a crash when testing router reachability on a router that
7676 could have an ed25519 ID, but which does not. Fixes bug 25415;
7677 bugfix on 0.3.3.2-alpha.
7679 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
7680 - Correctly detect when onion services get disabled after HUP. Fixes
7681 bug 25761; bugfix on 0.3.2.1.
7683 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
7684 - Impose a limit on circuit cell queue size. The limit can be
7685 controlled by a consensus parameter. Fixes bug 25226; bugfix
7688 o Minor features (compatibility, backport from 0.3.4.1-alpha):
7689 - Avoid some compilation warnings with recent versions of LibreSSL.
7690 Closes ticket 26006.
7692 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
7693 - Our .travis.yml configuration now includes support for testing the
7694 results of "make distcheck". (It's not uncommon for "make check"
7695 to pass but "make distcheck" to fail.) Closes ticket 25814.
7696 - Our Travis CI configuration now integrates with the Coveralls
7697 coverage analysis tool. Closes ticket 25818.
7699 o Minor features (geoip):
7700 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
7701 database. Closes ticket 26104.
7703 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
7704 - Don't consider Tor running as a client if the ControlPort is open,
7705 but no actual client ports are open. Fixes bug 26062; bugfix
7708 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
7709 - Upon receiving a malformed connected cell, stop processing the
7710 cell immediately. Previously we would mark the connection for
7711 close, but continue processing the cell as if the connection were
7712 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
7714 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
7715 - Stop saying in the manual that clients cache ipv4 dns answers from
7716 exit relays. We haven't used them since 0.2.6.3-alpha, and in
7717 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
7718 we forgot to say so in the man page. Fixes bug 26052; bugfix
7721 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
7722 - Allow the nanosleep() system call, which glibc uses to implement
7723 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
7725 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
7726 - Fix a memory leak when a v3 onion service is configured and gets a
7727 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
7728 - When parsing the descriptor signature, look for the token plus an
7729 extra white-space at the end. This is more correct but also will
7730 allow us to support new fields that might start with "signature".
7731 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
7733 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
7734 - Avoid a crash when running with DirPort set but ORPort turned off.
7735 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
7737 o Documentation (backport from 0.3.4.1-alpha):
7738 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
7739 ticket 25857. Patch from "CTassisF".
7742 Changes in version 0.3.4.1-alpha - 2018-05-17
7743 Tor 0.3.4.1-alpha is the first release in the 0.3.4.x series. It
7744 includes refactoring to begin reducing Tor's binary size and idle CPU
7745 usage on mobile, along with prep work for new bandwidth scanners,
7746 improvements to the experimental "vanguards" feature, and numerous
7747 other small features and bugfixes.
7749 o New system requirements:
7750 - Tor no longer tries to support old operating systems without
7751 mmap() or some local equivalent. Apparently, compilation on such
7752 systems has been broken for some time, without anybody noticing or
7753 complaining. Closes ticket 25398.
7755 o Major feature (directory authority, modularization):
7756 - The directory authority subsystem has been modularized. The code
7757 is now located in src/or/dirauth/, and is compiled in by default.
7758 To disable the module, the configure option
7759 --disable-module-dirauth has been added. This module may be
7760 disabled by default in some future release. Closes ticket 25610.
7762 o Major features (main loop, CPU usage):
7763 - When Tor is disabled (via DisableNetwork or via hibernation), it
7764 no longer needs to run any per-second events. This change should
7765 make it easier for mobile applications to disable Tor while the
7766 device is sleeping, or Tor is not running. Closes ticket 26063.
7767 - Tor no longer enables all of its periodic events by default.
7768 Previously, Tor would enable all possible main loop events,
7769 regardless of whether it needed them. Furthermore, many of these
7770 events are now disabled with Tor is hibernating or DisableNetwork
7771 is set. This is a big step towards reducing client CPU usage by
7772 reducing the amount of wake-ups the daemon does. Closes ticket
7774 - The bandwidth-limitation logic has been refactored so that
7775 bandwidth calculations are performed on-demand, rather than every
7776 TokenBucketRefillInterval milliseconds. This change should improve
7777 the granularity of our bandwidth calculations, and limit the
7778 number of times that the Tor process needs to wake up when it is
7779 idle. Closes ticket 25373.
7780 - Move responsibility for many operations from a once-per-second
7781 callback to a callback that is only scheduled as needed. Moving
7782 this functionality has allowed us to disable the callback when
7783 Tor's network is disabled. Once enough items are removed from our
7784 once-per-second callback, we can eliminate it entirely to conserve
7785 CPU when idle. The functionality removed includes: closing
7786 connections, circuits, and channels (ticket 25932); consensus
7787 voting (25937); flushing log callbacks (25951); honoring delayed
7788 SIGNEWNYM requests (25949); rescanning the consensus cache
7789 (25931); saving the state file to disk (25948); warning relay
7790 operators about unreachable ports (25952); and keeping track of
7791 Tor's uptime (26009).
7793 o Major bugfixes (directory authorities, security):
7794 - When directory authorities read a zero-byte bandwidth file, they
7795 would previously log a warning with the contents of an
7796 uninitialised buffer. They now log a warning about the empty file
7797 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
7799 o Major bugfixes (crash):
7800 - Avoid a rare assertion failure in the circuit build timeout code
7801 if we fail to allow any circuits to actually complete. Fixes bug
7802 25733; bugfix on 0.2.2.2-alpha.
7804 o Major bugfixes (directory authority):
7805 - Avoid a crash when testing router reachability on a router that
7806 could have an ed25519 ID, but which does not. Fixes bug 25415;
7807 bugfix on 0.3.3.2-alpha.
7809 o Major bugfixes (onion service):
7810 - Correctly detect when onion services get disabled after HUP. Fixes
7811 bug 25761; bugfix on 0.3.2.1.
7813 o Major bugfixes (protover, voting):
7814 - Revise Rust implementation of protover to use a more memory-
7815 efficient voting algorithm and corresponding data structures, thus
7816 avoiding a potential (but small impact) DoS attack where specially
7817 crafted protocol strings would expand to several potential
7818 megabytes in memory. In the process, several portions of code were
7819 revised to be methods on new, custom types, rather than functions
7820 taking interchangeable types, thus increasing type safety of the
7821 module. Custom error types and handling were added as well, in
7822 order to facilitate better error dismissal/handling in outside
7823 crates and avoid mistakenly passing an internal error string to C
7824 over the FFI boundary. Many tests were added, and some previous
7825 differences between the C and Rust implementations have been
7826 remedied. Fixes bug 24031; bugfix on 0.3.3.1-alpha.
7828 o Major bugfixes (relay, denial of service):
7829 - Impose a limit on circuit cell queue size. The limit can be
7830 controlled by a consensus parameter. Fixes bug 25226; bugfix
7833 o Minor features (accounting):
7834 - When Tor becomes dormant, it now uses a scheduled event to wake up
7835 at the right time. Previously, we would use the per-second timer
7836 to check whether to wake up, but we no longer have any per-second
7837 timers enabled when the network is disabled. Closes ticket 26064.
7839 o Minor features (code quality):
7840 - Add optional spell-checking for the Tor codebase, using the
7841 "misspell" program. To use this feature, run "make check-typos".
7842 Closes ticket 25024.
7844 o Minor features (compatibility):
7845 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
7846 the no-deprecated option, and builds correctly with them. Closes
7847 tickets 19429, 19981, and 25353.
7848 - Avoid some compilation warnings with recent versions of LibreSSL.
7849 Closes ticket 26006.
7851 o Minor features (compression, zstd):
7852 - When running with zstd, Tor now considers using advanced functions
7853 that the zstd maintainers have labeled as potentially unstable. To
7854 prevent breakage, Tor will only use this functionality when the
7855 runtime version of the zstd library matches the version with which
7856 Tor was compiled. Closes ticket 25162.
7858 o Minor features (configuration):
7859 - The "DownloadSchedule" options have been renamed to end with
7860 "DownloadInitialDelay". The old names are still allowed, but will
7861 produce a warning. Comma-separated lists are still permitted for
7862 these options, but all values after the first are ignored (as they
7863 have been since 0.2.9). Closes ticket 23354.
7865 o Minor features (continuous integration):
7866 - Our .travis.yml configuration now includes support for testing the
7867 results of "make distcheck". (It's not uncommon for "make check"
7868 to pass but "make distcheck" to fail.) Closes ticket 25814.
7869 - Our Travis CI configuration now integrates with the Coveralls
7870 coverage analysis tool. Closes ticket 25818.
7872 o Minor features (control port):
7873 - Introduce GETINFO "current-time/{local,utc}" to return the local
7874 and UTC times respectively in ISO format. This helps a controller
7875 like Tor Browser detect a time-related error. Closes ticket 25511.
7876 Patch by Neel Chauhan.
7877 - Introduce new fields to the CIRC_BW event. There are two new
7878 fields in each of the read and written directions. The DELIVERED
7879 fields report the total valid data on the circuit, as measured by
7880 the payload sizes of verified and error-checked relay command
7881 cells. The OVERHEAD fields report the total unused bytes in each
7882 of these cells. Closes ticket 25903.
7884 o Minor features (directory authority):
7885 - Directory authorities now open their key-pinning files as O_SYNC,
7886 to limit their chances of accidentally writing partial lines.
7887 Closes ticket 23909.
7889 o Minor features (directory authority, forward compatibility):
7890 - Make the lines of the measured bandwidth file able to contain
7891 their entries in any order. Previously, the node_id entry needed
7892 to come first. Closes ticket 26004.
7894 o Minor features (entry guards):
7895 - Introduce a new torrc option NumPrimaryGuards for controlling the
7896 number of primary guards. Closes ticket 25843.
7898 o Minor features (geoip):
7899 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
7900 database. Closes ticket 26104.
7902 o Minor features (performance):
7903 - Avoid a needless call to malloc() when processing an incoming
7904 relay cell. Closes ticket 24914.
7905 - Make our timing-wheel code run a tiny bit faster on 32-bit
7906 platforms, by preferring 32-bit math to 64-bit. Closes
7908 - Avoid a needless malloc()/free() pair every time we handle an ntor
7909 handshake. Closes ticket 25150.
7911 o Minor features (testing):
7912 - Add a unit test for voting_schedule_get_start_of_next_interval().
7913 Closes ticket 26014, and helps make unit test coverage
7915 - A new unittests module specifically for testing the functions in
7916 the (new-ish) bridges.c module has been created with new
7917 unittests, raising the code coverage percentages. Closes 25425.
7918 - We now have improved testing for addressmap_get_virtual_address()
7919 function. This should improve our test coverage, and make our test
7920 coverage more deterministic. Closes ticket 25993.
7922 o Minor features (timekeeping, circuit scheduling):
7923 - When keeping track of how busy each circuit have been recently on
7924 a given connection, use coarse-grained monotonic timers rather
7925 than gettimeofday(). This change should marginally increase
7926 accuracy and performance. Implements part of ticket 25927.
7928 o Minor bugfixes (bandwidth management):
7929 - Consider ourselves "low on write bandwidth" if we have exhausted
7930 our write bandwidth some time in the last second. This was the
7931 documented behavior before, but the actual behavior was to change
7932 this value every TokenBucketRefillInterval. Fixes bug 25828;
7933 bugfix on 0.2.3.5-alpha.
7935 o Minor bugfixes (C correctness):
7936 - Add a missing lock acquisition in the shutdown code of the control
7937 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
7938 Coverity; this is CID 1433643.
7940 o Minor bugfixes (circuit path selection):
7941 - Don't count path selection failures as circuit build failures.
7942 This change should eliminate cases where Tor blames its guard or
7943 the network for situations like insufficient microdescriptors
7944 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
7947 o Minor bugfixes (client):
7948 - Don't consider Tor running as a client if the ControlPort is open,
7949 but no actual client ports are open. Fixes bug 26062; bugfix
7952 o Minor bugfixes (code style):
7953 - Fixed multiple includes of transports.h in src/or/connection.c
7954 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
7955 - Remove the unused variable n_possible from the function
7956 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
7958 o Minor bugfixes (control interface):
7959 - Respond with more human-readable error messages to GETINFO exit-
7960 policy/* requests. Also, let controller know if an error is
7961 transient (response code 551) or not (response code 552). Fixes
7962 bug 25852; bugfix on 0.2.8.1-alpha.
7964 o Minor bugfixes (controller):
7965 - Make CIRC_BW event reflect the total of all data sent on a
7966 circuit, including padding and dropped cells. Also fix a mis-
7967 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
7968 bugfix on 0.2.5.2-alpha.
7970 o Minor bugfixes (correctness, client):
7971 - Upon receiving a malformed connected cell, stop processing the cell
7972 immediately. Previously we would mark the connection for close, but
7973 continue processing the cell as if the connection were open. Fixes bug
7974 26072; bugfix on 0.2.4.7-alpha.
7976 o Minor bugfixes (directory client):
7977 - When unverified-consensus is verified, rename it to cached-
7978 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
7979 - Fixed launching a certificate fetch always during the scheduled
7980 periodic consensus fetch by fetching only in those cases when
7981 consensus are waiting for certs. Fixes bug 24740; bugfix
7984 o Minor bugfixes (documentation):
7985 - Stop saying in the manual that clients cache ipv4 dns answers from
7986 exit relays. We haven't used them since 0.2.6.3-alpha, and in
7987 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
7988 we forgot to say so in the man page. Fixes bug 26052; bugfix
7991 o Minor bugfixes (error reporting):
7992 - Improve tolerance for directory authorities with skewed clocks.
7993 Previously, an authority with a clock more than 60 seconds ahead
7994 could cause a client with a correct clock to warn that the
7995 client's clock was behind. Now the clocks of a majority of
7996 directory authorities have to be ahead of the client before this
7997 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
7999 o Minor bugfixes (Linux seccomp2 sandbox):
8000 - Allow the nanosleep() system call, which glibc uses to implement
8001 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
8003 o Minor bugfixes (onion service):
8004 - Fix a memory leak when a v3 onion service is configured and gets a
8005 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
8006 - When parsing the descriptor signature, look for the token plus an
8007 extra white-space at the end. This is more correct but also will
8008 allow us to support new fields that might start with "signature".
8009 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
8011 o Minor bugfixes (path selection):
8012 - Only select relays when they have the descriptors we prefer to use
8013 for them. This change fixes a bug where we could select a relay
8014 because it had _some_ descriptor, but reject it later with a
8015 nonfatal assertion error because it didn't have the exact one we
8016 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
8018 o Minor bugfixes (portability):
8019 - Do not align mmap length, as it is not required by POSIX, and the
8020 getpagesize function is deprecated. Fixes bug 25399; bugfix
8023 o Minor bugfixes (portability, FreeBSD):
8024 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
8025 does not stringify on FreeBSD, so we switch to tor_asprintf().
8026 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
8028 o Minor bugfixes (relay statistics):
8029 - When a relay is collecting internal statistics about how many
8030 create cell requests it has seen of each type, accurately count
8031 the requests from relays that temporarily fall out of the
8032 consensus. (To be extra conservative, we were already ignoring
8033 requests from clients in our counts, and we continue ignoring them
8034 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
8036 o Minor bugfixes (relay, crash):
8037 - Avoid a crash when running with DirPort set but ORPort turned off.
8038 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
8040 o Minor bugfixes (restart-in-process):
8041 - When shutting down, Tor now clears all the flags in the control.c
8042 module. This should prevent a bug where authentication cookies are
8043 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
8045 o Minor bugfixes (testing):
8046 - When testing workqueue event-cancellation, make sure that we
8047 actually cancel an event, and that cancel each event with equal
8048 probability. (It was previously possible, though extremely
8049 unlikely, for our event-canceling test not to cancel any events.)
8050 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
8051 - Repeat part of the test in test_client_pick_intro() a number of
8052 times, to give it consistent coverage. Fixes bug 25996; bugfix
8054 - Remove randomness from the hs_common/responsible_hsdirs test, so
8055 that it always takes the same path through the function it tests.
8056 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
8057 - Change the behavior of the "channel/outbound" test so that it
8058 never causes a 10-second rollover for the EWMA circuitmux code.
8059 Previously, this behavior would happen randomly, and result in
8060 fluctuating test coverage. Fixes bug 25994; bugfix
8062 - Use X509_new() to allocate certificates that will be freed later
8063 with X509_free(). Previously, some parts of the unit tests had
8064 used tor_malloc_zero(), which is incorrect, and which caused test
8065 failures on Windows when they were built with extra hardening.
8066 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
8068 - While running the circuit_timeout test, fix the PRNG to a
8069 deterministic AES stream, so that the test coverage from this test
8070 will itself be deterministic. Fixes bug 25995; bugfix
8073 o Minor bugfixes (vanguards):
8074 - Allow the last hop in a vanguard circuit to be the same as our
8075 first, to prevent the adversary from influencing guard node choice
8076 by choice of last hop. Also prevent the creation of A - B - A
8077 paths, or A - A paths, which are forbidden by relays. Fixes bug
8078 25870; bugfix on 0.3.3.1-alpha.
8080 o Code simplification and refactoring:
8081 - Remove duplicate code in parse_{c,s}method_line and bootstrap
8082 their functionalities into a single function. Fixes bug 6236;
8083 bugfix on 0.2.3.6-alpha.
8084 - We remove the PortForwarding and PortForwardingHelper options,
8085 related functions, and the port_forwarding tests. These options
8086 were used by the now-deprecated Vidalia to help ordinary users
8087 become Tor relays or bridges. Closes ticket 25409. Patch by
8089 - In order to make the OR and dir checking function in router.c less
8090 confusing we renamed some functions and
8091 consider_testing_reachability() has been split into
8092 router_should_check_reachability() and
8093 router_do_reachability_checks(). Also we improved the documentation
8094 in some functions. Closes ticket 18918.
8095 - Initial work to isolate Libevent usage to a handful of modules in
8096 our codebase, to simplify our call structure, and so that we can
8097 more easily change event loops in the future if needed. Closes
8099 - Introduce a function to call getsockname() and return tor_addr_t,
8100 to save a little complexity throughout the codebase. Closes
8102 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
8103 as hsdir_index is always present. Also, we move hsdir_index_t into
8104 or.h. Closes ticket 23094. Patch by Neel Chauhan.
8105 - Merge functions used for describing nodes and suppress the
8106 functions that do not allocate memory for the output buffer
8107 string. NODE_DESC_BUF_LEN constant and format_node_description()
8108 function cannot be used externally from router.c module anymore.
8109 Closes ticket 25432. Patch by valentecaio.
8110 - Our main loop has been simplified so that all important operations
8111 happen inside events. Previously, some operations had to happen
8112 outside the event loop, to prevent infinite sequences of event
8113 activations. Closes ticket 25374.
8114 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
8115 it in register_intro_circ() and service_intro_point_new(). This
8116 prevents the digest from being re-calculated each time. Closes
8117 ticket 23107. Patch by Neel Chauhan.
8118 - Refactor token-bucket implementations to use a common backend.
8119 Closes ticket 25766.
8120 - Remove extern declaration of stats_n_seconds_working variable from
8121 main, protecting its accesses with get_uptime() and reset_uptime()
8122 functions. Closes ticket 25081, patch by “valentecaio”.
8123 - Remove our previous logic for "cached gettimeofday()" -- our
8124 coarse monotonic timers are fast enough for this purpose, and far
8125 less error-prone. Implements part of ticket 25927.
8126 - Remove the return value for fascist_firewall_choose_address_base(),
8127 and sister functions such as fascist_firewall_choose_address_node()
8128 and fascist_firewall_choose_address_rs(). Also, while we're here,
8129 initialize the ap argument as leaving it uninitialized can pose a
8130 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
8131 - Rename two fields of connection_t struct. timestamp_lastwritten is
8132 renamed to timestamp_last_write_allowed and timestamp_lastread is
8133 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
8135 - Since Tor requires C99, remove our old workaround code for libc
8136 implementations where free(NULL) doesn't work. Closes ticket 24484.
8137 - Use our standard rate-limiting code to deal with excessive
8138 libevent failures, rather than the hand-rolled logic we had
8139 before. Closes ticket 26016.
8140 - We remove the return value of node_get_prim_orport() and
8141 node_get_prim_dirport(), and introduce node_get_prim_orport() in
8142 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
8143 check for a null address. Closes ticket 23873. Patch by
8145 - We switch to should_record_bridge_info() in
8146 geoip_note_client_seen() and options_need_geoip_info() instead of
8147 accessing the configuration values directly. Fixes bug 25290;
8148 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
8150 o Deprecated features:
8151 - As we are not recommending 0.2.5 anymore, we require relays that
8152 once had an ed25519 key associated with their RSA key to always
8153 have that key, instead of allowing them to drop back to a version
8154 that didn't support ed25519. This means they need to use a new RSA
8155 key if they want to downgrade to an older version of tor without
8156 ed25519. Closes ticket 20522.
8159 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
8160 ticket 25857. Patch from "CTassisF".
8163 - Directory authorities will no longer support voting according to
8164 any consensus method before consensus method 25. This keeps
8165 authorities compatible with all authorities running 0.2.9.8 and
8166 later, and does not break any clients or relays. Implements ticket
8167 24378 and proposal 290.
8168 - The PortForwarding and PortForwardingHelper features have been
8169 removed. The reasoning is, given that implementations of NAT
8170 traversal protocols within common consumer grade routers are
8171 frequently buggy, and that the target audience for a NAT punching
8172 feature is a perhaps less-technically-inclined relay operator,
8173 when the helper fails to setup traversal the problems are usually
8174 deep, ugly, and very router specific, making them horrendously
8175 impossible for technical support to reliable assist with, and thus
8176 resulting in frustration all around. Unfortunately, relay
8177 operators who would like to run relays behind NATs will need to
8178 become more familiar with the port forwarding configurations on
8179 their local router. Closes 25409.
8180 - The TestingEnableTbEmptyEvent option has been removed. It was used
8181 in testing simulations to measure how often connection buckets
8182 were emptied, in order to improve our scheduling, but it has not
8183 been actively used in years. Closes ticket 25760.
8184 - The old "round-robin" circuit multiplexer (circuitmux)
8185 implementation has been removed, along with a fairly large set of
8186 code that existed to support it. It has not been the default
8187 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
8188 but it still required an unreasonable amount of memory and CPU.
8189 Closes ticket 25268.
8192 Changes in version 0.3.3.5-rc - 2018-04-15
8193 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
8194 including some that could affect reliability or correctness.
8196 This is the first release candidate in the 0.3.3 series. If we find no
8197 new bugs or regression here, then the first stable 0.3.3 release will
8198 be nearly identical to this one.
8200 o Major bugfixes (security, protover, voting):
8201 - Revise Rust implementation of protover to use a more memory-
8202 efficient voting algorithm and corresponding data structures, thus
8203 avoiding a potential memory-based DoS attack where specially
8204 crafted protocol strings would expand to fill available memory.
8205 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
8207 o Major bugfixes (performance, load balancing):
8208 - Directory authorities no longer vote in favor of the Guard flag
8209 for relays without directory support. Starting in Tor
8210 0.3.0.1-alpha, clients have been avoiding using such relays in the
8211 Guard position, leading to increasingly broken load balancing for
8212 the 5%-or-so of Guards that don't advertise directory support.
8213 Fixes bug 22310; bugfix on 0.3.0.6.
8215 o Minor feature (continuous integration):
8216 - Update the Travis CI configuration to use the stable Rust channel,
8217 now that we have decided to require that. Closes ticket 25714.
8219 o Minor features (config options):
8220 - Change the way the default value for MaxMemInQueues is calculated.
8221 We now use 40% of the hardware RAM if the system has 8 GB RAM or
8222 more. Otherwise we use the former value of 75%. Closes
8225 o Minor features (geoip):
8226 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
8227 Country database. Closes ticket 25718.
8229 o Minor bugfixes (client):
8230 - When using a listed relay as a bridge, and also using
8231 microdescriptors, and considering that relay as a non-bridge in a
8232 circuit, treat its microdescriptor as a valid source of
8233 information about that relay. This change should prevent a non-
8234 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
8236 o Minor bugfixes (controller):
8237 - Restore the correct operation of the RESOLVE command, which had
8238 been broken since we added the ability to enable/disable DNS on
8239 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
8241 o Minor bugfixes (distribution, compilation, rust):
8242 - Build correctly when the rust dependencies submodule is loaded,
8243 but the TOR_RUST_DEPENDENCIES environment variable is not set.
8244 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
8245 - Actually include all of our Rust source in our source
8246 distributions. (Previously, a few of the files were accidentally
8247 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
8249 o Minor bugfixes (documentation):
8250 - Document that the PerConnBW{Rate,Burst} options will fall back to
8251 their corresponding consensus parameters only if those parameters
8252 are set. Previously we had claimed that these values would always
8253 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
8254 - Revert a misformatting issue in the ExitPolicy documentation.
8255 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
8257 o Minor bugfixes (exit relay DNS retries):
8258 - Re-attempt timed-out DNS queries 3 times before failure, since our
8259 timeout is 5 seconds for them, but clients wait 10-15. Also allow
8260 slightly more timeouts per resolver when an exit has multiple
8261 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
8263 o Minor bugfixes (onion services):
8264 - Re-instate counting the client HSDir fetch circuits against the
8265 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
8267 - Remove underscores from the _HSLayer{2,3}Nodes options. This
8268 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
8269 Fixes bug 25581; bugfix on 0.3.3.1-alpha
8271 o Code simplification and refactoring:
8272 - Move the list of default directory authorities to its own file.
8273 Closes ticket 24854. Patch by "beastr0".
8275 o Documentation (manpage, denial of service):
8276 - Provide more detail about the denial-of-service options, by
8277 listing each mitigation and explaining how they relate. Closes
8281 Changes in version 0.3.3.4-alpha - 2018-03-29
8282 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
8283 the alpha testing of earlier releases in its series. We are
8284 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
8286 o New system requirements:
8287 - When built with Rust, Tor now depends on version 0.2.39 of the
8288 libc crate. Closes tickets 25310 and 25664.
8290 o Major bugfixes (relay, connection):
8291 - If we have failed to connect to a relay and received a connection
8292 refused, timeout, or similar error (at the TCP level), do not try
8293 that same address/port again for 60 seconds after the failure has
8294 occurred. Fixes bug 24767; bugfix on 0.0.6.
8296 o Minor features (geoip):
8297 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
8298 Country database. Closes ticket 25469.
8300 o Minor features (log messages):
8301 - Improve log message in the out-of-memory handler to include
8302 information about memory usage from the different compression
8303 backends. Closes ticket 25372.
8305 o Minor features (sandbox):
8306 - Explicitly permit the poll() system call when the Linux
8307 seccomp2-based sandbox is enabled: apparently, some versions of
8308 libc use poll() when calling getpwnam(). Closes ticket 25313.
8310 o Minor bugfixes (C correctness):
8311 - Fix a very unlikely (impossible, we believe) null pointer
8312 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
8313 Coverity; this is CID 1430932.
8315 o Minor bugfixes (channel, client):
8316 - Better identify client connection when reporting to the geoip
8317 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
8319 o Minor bugfixes (compilation):
8320 - Fix a C99 compliance issue in our configuration script that caused
8321 compilation issues when compiling Tor with certain versions of
8322 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
8324 o Minor bugfixes (controller, reliability):
8325 - Avoid a (nonfatal) assertion failure when extending a one-hop
8326 circuit from the controller to become a multihop circuit. Fixes
8327 bug 24903; bugfix on 0.2.5.2-alpha.
8329 o Major bugfixes (networking):
8330 - Tor will no longer reject IPv6 address strings from Tor Browser
8331 when they are passed as hostnames in SOCKS5 requests. Fixes bug
8332 25036, bugfix on Tor 0.3.1.2.
8334 o Minor bugfixes (networking):
8335 - string_is_valid_hostname() will not consider IP strings to be
8336 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
8338 o Minor bugfixes (onion service v3):
8339 - Avoid an assertion failure when the next onion service
8340 descriptor rotation type is out of sync with the consensus's
8341 valid-after time. Instead, log a warning message with extra
8342 information, so we can better hunt down the cause of this
8343 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
8345 o Minor bugfixes (testing):
8346 - Avoid intermittent test failures due to a test that had relied on
8347 onion service introduction point creation finishing within 5
8348 seconds of real clock time. Fixes bug 25450; bugfix
8350 - Rust crates are now automatically detected and tested. Previously,
8351 some crates were not tested by `make test-rust` due to a static
8352 string in the `src/test/test_rust.sh` script specifying which
8353 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
8355 o Minor bugfixes (testing, benchmarks):
8356 - Fix a crash when running benchmark tests on win32 systems. The
8357 crash was due to a mutex that wasn't initialized before logging
8358 and options were initialized. Fixes bug 25479; bugfix
8361 o Minor bugfixes (warnings, ipv6):
8362 - Avoid a bug warning that could occur when trying to connect to a
8363 relay over IPv6. This warning would occur on a Tor instance that
8364 downloads router descriptors, but prefers to use microdescriptors.
8365 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
8367 o Code simplification and refactoring:
8368 - Remove the old (deterministic) directory retry logic entirely:
8369 We've used exponential backoff exclusively for some time. Closes
8373 - Improved the documentation of AccountingStart parameter. Closes
8375 - Update the documentation for "Log" to include the current list of
8376 logging domains. Closes ticket 25378.
8379 Changes in version 0.3.1.10 - 2018-03-03
8380 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
8383 It includes an important security fix for a remote crash attack
8384 against directory authorities, tracked as TROVE-2018-001.
8386 This release also backports our new system for improved resistance to
8387 denial-of-service attacks against relays.
8389 This release also fixes several minor bugs and annoyances from
8392 All directory authorities should upgrade to one of the versions
8393 released today. Relays running 0.3.1.x may wish to update to one of
8394 the versions released today, for the DoS mitigations.
8396 Please note: according to our release calendar, Tor 0.3.1 will no
8397 longer be supported after 1 July 2018. If you will be running Tor
8398 after that date, you should make sure to plan to upgrade to the latest
8399 stable version, or downgrade to 0.2.9 (which will receive long-term
8402 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
8403 - Fix a protocol-list handling bug that could be used to remotely crash
8404 directory authorities with a null-pointer exception. Fixes bug 25074;
8405 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
8408 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
8409 - Give relays some defenses against the recent network overload. We
8410 start with three defenses (default parameters in parentheses).
8411 First: if a single client address makes too many concurrent
8412 connections (>100), hang up on further connections. Second: if a
8413 single client address makes circuits too quickly (more than 3 per
8414 second, with an allowed burst of 90) while also having too many
8415 connections open (3), refuse new create cells for the next while
8416 (1-2 hours). Third: if a client asks to establish a rendezvous
8417 point to you directly, ignore the request. These defenses can be
8418 manually controlled by new torrc options, but relays will also
8419 take guidance from consensus parameters, so there's no need to
8420 configure anything manually. Implements ticket 24902.
8422 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
8423 - Update the sandbox rules so that they should now work correctly
8424 with Glibc 2.26. Closes ticket 24315.
8426 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
8427 - Fix an "off by 2" error in counting rendezvous failures on the
8428 onion service side. While we thought we would stop the rendezvous
8429 attempt after one failed circuit, we were actually making three
8430 circuit attempts before giving up. Now switch to a default of 2,
8431 and allow the consensus parameter "hs_service_max_rdv_failures" to
8432 override. Fixes bug 24895; bugfix on 0.0.6.
8434 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
8435 - Add Link protocol version 5 to the supported protocols list. Fixes
8436 bug 25070; bugfix on 0.3.1.1-alpha.
8438 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
8439 - Fix a set of false positives where relays would consider
8440 connections to other relays as being client-only connections (and
8441 thus e.g. deserving different link padding schemes) if those
8442 relays fell out of the consensus briefly. Now we look only at the
8443 initial handshake and whether the connection authenticated as a
8444 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
8446 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
8447 - Make our OOM handler aware of the geoip client history cache so it
8448 doesn't fill up the memory. This check is important for IPv6 and
8449 our DoS mitigation subsystem. Closes ticket 25122.
8451 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
8452 - Change relay bandwidth reporting stats interval from 4 hours to 24
8453 hours in order to reduce the efficiency of guard discovery
8454 attacks. Fixes ticket 23856.
8456 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
8457 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
8458 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
8459 since they neither disabled TLS 1.3 nor enabled any of the
8460 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
8461 Closes ticket 24978.
8463 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
8464 - The fallback directory list has been re-generated based on the
8465 current status of the network. Tor uses fallback directories to
8466 bootstrap when it doesn't yet have up-to-date directory
8467 information. Closes ticket 24801.
8468 - Make the default DirAuthorityFallbackRate 0.1, so that clients
8469 prefer to bootstrap from fallback directory mirrors. This is a
8470 follow-up to 24679, which removed weights from the default
8471 fallbacks. Implements ticket 24681.
8473 o Minor features (geoip):
8474 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
8477 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
8478 - Use the actual observed address of an incoming relay connection,
8479 not the canonical address of the relay from its descriptor, when
8480 making decisions about how to handle the incoming connection.
8481 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
8483 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
8484 - Directory authorities, when refusing a descriptor from a rejected
8485 relay, now explicitly tell the relay (in its logs) to set a valid
8486 ContactInfo address and contact the bad-relays@ mailing list.
8487 Fixes bug 25170; bugfix on 0.2.9.1.
8489 o Minor bugfixes (address selection, backport from 0.3.2.9):
8490 - When the fascist_firewall_choose_address_ functions don't find a
8491 reachable address, set the returned address to the null address
8492 and port. This is a precautionary measure, because some callers do
8493 not check the return value. Fixes bug 24736; bugfix
8496 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
8497 - Fetch descriptors aggressively whenever we lack enough to build
8498 circuits, regardless of how many descriptors we are missing.
8499 Previously, we would delay launching the fetch when we had fewer
8500 than 15 missing descriptors, even if some of those descriptors
8501 were blocking circuits from building. Fixes bug 23985; bugfix on
8502 0.1.1.11-alpha. The effects of this bug became worse in
8503 0.3.0.3-alpha, when we began treating missing descriptors from our
8504 primary guards as a reason to delay circuits.
8505 - Don't try fetching microdescriptors from relays that have failed
8506 to deliver them in the past. Fixes bug 23817; bugfix
8509 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
8510 - Fix a signed/unsigned comparison warning introduced by our fix to
8511 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
8513 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
8514 - Avoid a crash when attempting to use the seccomp2 sandbox together
8515 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
8518 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
8519 - Fix a possible crash on malformed consensus. If a consensus had
8520 contained an unparseable protocol line, it could have made clients
8521 and relays crash with a null-pointer exception. To exploit this
8522 issue, however, an attacker would need to be able to subvert the
8523 directory authority system. Fixes bug 25251; bugfix on
8524 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
8526 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
8527 - Recover better from empty or corrupt files in the consensus cache
8528 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
8529 - When a consensus diff calculation is only partially successful,
8530 only record the successful parts as having succeeded. Partial
8531 success can happen if (for example) one compression method fails
8532 but the others succeed. Previously we misrecorded all the
8533 calculations as having succeeded, which would later cause a
8534 nonfatal assertion failure. Fixes bug 24086; bugfix
8537 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
8538 - Tor now updates its guard state when it reads a consensus
8539 regardless of whether it's missing descriptors. That makes tor use
8540 its primary guards to fetch descriptors in some edge cases where
8541 it would previously have used fallback directories. Fixes bug
8542 23862; bugfix on 0.3.0.1-alpha.
8544 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
8545 - Don't treat inability to store a cached consensus object as a bug:
8546 it can happen normally when we are out of disk space. Fixes bug
8547 24859; bugfix on 0.3.1.1-alpha.
8549 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
8550 - When queuing DESTROY cells on a channel, only queue the circuit-id
8551 and reason fields: not the entire 514-byte cell. This fix should
8552 help mitigate any bugs or attacks that fill up these queues, and
8553 free more RAM for other uses. Fixes bug 24666; bugfix
8556 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
8557 - When closing a connection via close_connection_immediately(), we
8558 mark it as "not blocked on bandwidth", to prevent later calls from
8559 trying to unblock it, and give it permission to read. This fixes a
8560 backtrace warning that can happen on relays under various
8561 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
8563 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
8564 - When selecting relays by bandwidth, avoid a rounding error that
8565 could sometimes cause load to be imbalanced incorrectly.
8566 Previously, we would always round upwards; now, we round towards
8567 the nearest integer. This had the biggest effect when a relay's
8568 weight adjustments should have given it weight 0, but it got
8569 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
8570 - When calculating the fraction of nodes that have descriptors, and
8571 all nodes in the network have zero bandwidths, count the number of
8572 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
8573 - Actually log the total bandwidth in compute_weighted_bandwidths().
8574 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
8576 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
8577 - Improve the performance of our consensus-diff application code
8578 when Tor is built with the --enable-fragile-hardening option set.
8579 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
8581 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
8582 - Don't exit the Tor process if setrlimit() fails to change the file
8583 limit (which can happen sometimes on some versions of OSX). Fixes
8584 bug 21074; bugfix on 0.0.9pre5.
8586 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
8587 - Fix a bug in the bit-counting parts of our timing-wheel code on
8588 MSVC. (Note that MSVC is still not a supported build platform, due
8589 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
8592 o Minor bugfixes (relay, partial backport):
8593 - Make the internal channel_is_client() function look at what sort
8594 of connection handshake the other side used, rather than whether
8595 the other side ever sent a create_fast cell to us. Backports part
8596 of the fixes from bugs 22805 and 24898.
8598 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
8599 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
8601 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
8602 bugfix on 0.2.9.4-alpha.
8604 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
8605 - Update the "rust dependencies" submodule to be a project-level
8606 repository, rather than a user repository. Closes ticket 25323.
8609 Changes in version 0.2.9.15 - 2018-03-03
8610 Tor 0.2.9.15 backports important security and stability bugfixes from
8613 It includes an important security fix for a remote crash attack
8614 against directory authorities, tracked as TROVE-2018-001.
8616 This release also backports our new system for improved resistance to
8617 denial-of-service attacks against relays.
8619 This release also fixes several minor bugs and annoyances from
8622 All directory authorities should upgrade to one of the versions
8623 released today. Relays running 0.2.9.x may wish to update to one of
8624 the versions released today, for the DoS mitigations.
8626 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
8627 - Fix a protocol-list handling bug that could be used to remotely crash
8628 directory authorities with a null-pointer exception. Fixes bug 25074;
8629 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
8632 o Major features (denial-of-service mitigation):
8633 - Give relays some defenses against the recent network overload. We
8634 start with three defenses (default parameters in parentheses).
8635 First: if a single client address makes too many concurrent
8636 connections (>100), hang up on further connections. Second: if a
8637 single client address makes circuits too quickly (more than 3 per
8638 second, with an allowed burst of 90) while also having too many
8639 connections open (3), refuse new create cells for the next while
8640 (1-2 hours). Third: if a client asks to establish a rendezvous
8641 point to you directly, ignore the request. These defenses can be
8642 manually controlled by new torrc options, but relays will also
8643 take guidance from consensus parameters, so there's no need to
8644 configure anything manually. Implements ticket 24902.
8646 o Major bugfixes (bootstrapping):
8647 - Fetch descriptors aggressively whenever we lack enough to build
8648 circuits, regardless of how many descriptors we are missing.
8649 Previously, we would delay launching the fetch when we had fewer
8650 than 15 missing descriptors, even if some of those descriptors
8651 were blocking circuits from building. Fixes bug 23985; bugfix on
8652 0.1.1.11-alpha. The effects of this bug became worse in
8653 0.3.0.3-alpha, when we began treating missing descriptors from our
8654 primary guards as a reason to delay circuits.
8656 o Major bugfixes (onion services, retry behavior):
8657 - Fix an "off by 2" error in counting rendezvous failures on the
8658 onion service side. While we thought we would stop the rendezvous
8659 attempt after one failed circuit, we were actually making three
8660 circuit attempts before giving up. Now switch to a default of 2,
8661 and allow the consensus parameter "hs_service_max_rdv_failures" to
8662 override. Fixes bug 24895; bugfix on 0.0.6.
8664 o Minor feature (relay statistics):
8665 - Change relay bandwidth reporting stats interval from 4 hours to 24
8666 hours in order to reduce the efficiency of guard discovery
8667 attacks. Fixes ticket 23856.
8669 o Minor features (compatibility, OpenSSL):
8670 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
8671 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
8672 since they neither disabled TLS 1.3 nor enabled any of the
8673 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
8674 Closes ticket 24978.
8676 o Minor features (denial-of-service avoidance):
8677 - Make our OOM handler aware of the geoip client history cache so it
8678 doesn't fill up the memory. This check is important for IPv6 and
8679 our DoS mitigation subsystem. Closes ticket 25122.
8681 o Minor features (fallback directory mirrors):
8682 - The fallback directory list has been re-generated based on the
8683 current status of the network. Tor uses fallback directories to
8684 bootstrap when it doesn't yet have up-to-date directory
8685 information. Closes ticket 24801.
8686 - Make the default DirAuthorityFallbackRate 0.1, so that clients
8687 prefer to bootstrap from fallback directory mirrors. This is a
8688 follow-up to 24679, which removed weights from the default
8689 fallbacks. Implements ticket 24681.
8691 o Minor features (geoip):
8692 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
8695 o Minor features (linux seccomp2 sandbox):
8696 - Update the sandbox rules so that they should now work correctly
8697 with Glibc 2.26. Closes ticket 24315.
8699 o Minor bugfix (channel connection):
8700 - Use the actual observed address of an incoming relay connection,
8701 not the canonical address of the relay from its descriptor, when
8702 making decisions about how to handle the incoming connection.
8703 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
8705 o Minor bugfix (directory authority):
8706 - Directory authorities, when refusing a descriptor from a rejected
8707 relay, now explicitly tell the relay (in its logs) to set a valid
8708 ContactInfo address and contact the bad-relays@ mailing list.
8709 Fixes bug 25170; bugfix on 0.2.9.1.
8711 o Minor bugfixes (address selection):
8712 - When the fascist_firewall_choose_address_ functions don't find a
8713 reachable address, set the returned address to the null address
8714 and port. This is a precautionary measure, because some callers do
8715 not check the return value. Fixes bug 24736; bugfix
8718 o Minor bugfixes (compilation):
8719 - Fix a signed/unsigned comparison warning introduced by our fix to
8720 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
8722 o Minor bugfixes (control port, linux seccomp2 sandbox):
8723 - Avoid a crash when attempting to use the seccomp2 sandbox together
8724 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
8727 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
8728 - Fix a possible crash on malformed consensus. If a consensus had
8729 contained an unparseable protocol line, it could have made clients
8730 and relays crash with a null-pointer exception. To exploit this
8731 issue, however, an attacker would need to be able to subvert the
8732 directory authority system. Fixes bug 25251; bugfix on
8733 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
8735 o Minor bugfixes (memory usage):
8736 - When queuing DESTROY cells on a channel, only queue the circuit-id
8737 and reason fields: not the entire 514-byte cell. This fix should
8738 help mitigate any bugs or attacks that fill up these queues, and
8739 free more RAM for other uses. Fixes bug 24666; bugfix
8742 o Minor bugfixes (network layer):
8743 - When closing a connection via close_connection_immediately(), we
8744 mark it as "not blocked on bandwidth", to prevent later calls from
8745 trying to unblock it, and give it permission to read. This fixes a
8746 backtrace warning that can happen on relays under various
8747 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
8749 o Minor bugfixes (OSX):
8750 - Don't exit the Tor process if setrlimit() fails to change the file
8751 limit (which can happen sometimes on some versions of OSX). Fixes
8752 bug 21074; bugfix on 0.0.9pre5.
8754 o Minor bugfixes (path selection):
8755 - When selecting relays by bandwidth, avoid a rounding error that
8756 could sometimes cause load to be imbalanced incorrectly.
8757 Previously, we would always round upwards; now, we round towards
8758 the nearest integer. This had the biggest effect when a relay's
8759 weight adjustments should have given it weight 0, but it got
8760 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
8761 - When calculating the fraction of nodes that have descriptors, and
8762 all nodes in the network have zero bandwidths, count the number of
8763 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
8764 - Actually log the total bandwidth in compute_weighted_bandwidths().
8765 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
8767 o Minor bugfixes (portability, msvc):
8768 - Fix a bug in the bit-counting parts of our timing-wheel code on
8769 MSVC. (Note that MSVC is still not a supported build platform, due
8770 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
8773 o Minor bugfixes (relay):
8774 - Make the internal channel_is_client() function look at what sort
8775 of connection handshake the other side used, rather than whether
8776 the other side ever sent a create_fast cell to us. Backports part
8777 of the fixes from bugs 22805 and 24898.
8779 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
8780 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
8782 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
8783 bugfix on 0.2.9.4-alpha.
8786 Changes in version 0.3.2.10 - 2018-03-03
8787 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
8788 backports a number of bugfixes, including important fixes for security
8791 It includes an important security fix for a remote crash attack
8792 against directory authorities, tracked as TROVE-2018-001.
8794 Additionally, it backports a fix for a bug whose severity we have
8795 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
8796 triggered in order to crash relays with a use-after-free pattern. As
8797 such, we are now tracking that bug as TROVE-2018-002 and
8798 CVE-2018-0491, and backporting it to earlier releases. This bug
8799 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
8802 This release also backports our new system for improved resistance to
8803 denial-of-service attacks against relays.
8805 This release also fixes several minor bugs and annoyances from
8808 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
8809 today, for the fix to TROVE-2018-002. Directory authorities should
8810 also upgrade. (Relays on earlier versions might want to update too for
8811 the DoS mitigations.)
8813 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
8814 - Fix a protocol-list handling bug that could be used to remotely crash
8815 directory authorities with a null-pointer exception. Fixes bug 25074;
8816 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
8819 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
8820 - Avoid adding the same channel twice in the KIST scheduler pending
8821 list, which could lead to remote denial-of-service use-after-free
8822 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
8824 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
8825 - Give relays some defenses against the recent network overload. We
8826 start with three defenses (default parameters in parentheses).
8827 First: if a single client address makes too many concurrent
8828 connections (>100), hang up on further connections. Second: if a
8829 single client address makes circuits too quickly (more than 3 per
8830 second, with an allowed burst of 90) while also having too many
8831 connections open (3), refuse new create cells for the next while
8832 (1-2 hours). Third: if a client asks to establish a rendezvous
8833 point to you directly, ignore the request. These defenses can be
8834 manually controlled by new torrc options, but relays will also
8835 take guidance from consensus parameters, so there's no need to
8836 configure anything manually. Implements ticket 24902.
8838 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
8839 - Fix an "off by 2" error in counting rendezvous failures on the
8840 onion service side. While we thought we would stop the rendezvous
8841 attempt after one failed circuit, we were actually making three
8842 circuit attempts before giving up. Now switch to a default of 2,
8843 and allow the consensus parameter "hs_service_max_rdv_failures" to
8844 override. Fixes bug 24895; bugfix on 0.0.6.
8845 - New-style (v3) onion services now obey the "max rendezvous circuit
8846 attempts" logic. Previously they would make as many rendezvous
8847 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
8848 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
8850 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
8851 - Add Link protocol version 5 to the supported protocols list. Fixes
8852 bug 25070; bugfix on 0.3.1.1-alpha.
8854 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
8855 - Fix a set of false positives where relays would consider
8856 connections to other relays as being client-only connections (and
8857 thus e.g. deserving different link padding schemes) if those
8858 relays fell out of the consensus briefly. Now we look only at the
8859 initial handshake and whether the connection authenticated as a
8860 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
8862 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
8863 - The scheduler subsystem was failing to promptly notice changes in
8864 consensus parameters, making it harder to switch schedulers
8865 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
8867 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
8868 - Make our OOM handler aware of the geoip client history cache so it
8869 doesn't fill up the memory. This check is important for IPv6 and
8870 our DoS mitigation subsystem. Closes ticket 25122.
8872 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
8873 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
8874 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
8875 since they neither disabled TLS 1.3 nor enabled any of the
8876 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
8877 Closes ticket 24978.
8879 o Minor features (geoip):
8880 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
8883 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
8884 - When logging a failure to create an onion service's descriptor,
8885 also log what the problem with the descriptor was. Diagnostic
8888 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
8889 - Use the actual observed address of an incoming relay connection,
8890 not the canonical address of the relay from its descriptor, when
8891 making decisions about how to handle the incoming connection.
8892 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
8894 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
8895 - Fix a possible crash on malformed consensus. If a consensus had
8896 contained an unparseable protocol line, it could have made clients
8897 and relays crash with a null-pointer exception. To exploit this
8898 issue, however, an attacker would need to be able to subvert the
8899 directory authority system. Fixes bug 25251; bugfix on
8900 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
8902 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
8903 - Directory authorities, when refusing a descriptor from a rejected
8904 relay, now explicitly tell the relay (in its logs) to set a valid
8905 ContactInfo address and contact the bad-relays@ mailing list.
8906 Fixes bug 25170; bugfix on 0.2.9.1.
8908 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
8909 - When building with Rust on OSX, link against libresolv, to work
8910 around the issue at https://github.com/rust-lang/rust/issues/46797.
8911 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
8913 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
8914 - Remove a BUG() statement when a client fetches an onion descriptor
8915 that has a lower revision counter than the one in its cache. This
8916 can happen in normal circumstances due to HSDir desync. Fixes bug
8917 24976; bugfix on 0.3.2.1-alpha.
8919 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
8920 - Don't treat inability to store a cached consensus object as a bug:
8921 it can happen normally when we are out of disk space. Fixes bug
8922 24859; bugfix on 0.3.1.1-alpha.
8924 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
8925 - Improve the performance of our consensus-diff application code
8926 when Tor is built with the --enable-fragile-hardening option set.
8927 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
8929 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
8930 - Don't exit the Tor process if setrlimit() fails to change the file
8931 limit (which can happen sometimes on some versions of OSX). Fixes
8932 bug 21074; bugfix on 0.0.9pre5.
8934 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
8935 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
8937 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
8938 bugfix on 0.2.9.4-alpha.
8940 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
8941 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
8942 25005; bugfix on 0.3.2.7-rc.
8944 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
8945 - Look at the "HSRend" protocol version, not the "HSDir" protocol
8946 version, when deciding whether a consensus entry can support the
8947 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
8948 bugfix on 0.3.2.1-alpha.
8950 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
8951 - Update the "rust dependencies" submodule to be a project-level
8952 repository, rather than a user repository. Closes ticket 25323.
8954 o Documentation (backport from 0.3.3.1-alpha)
8955 - Document that operators who run more than one relay or bridge are
8956 expected to set MyFamily and ContactInfo correctly. Closes
8960 Changes in version 0.3.3.3-alpha - 2018-03-03
8961 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
8962 It includes an important security fix for a remote crash attack
8963 against directory authorities tracked as TROVE-2018-001.
8965 Additionally, with this release, we are upgrading the severity of a
8966 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
8967 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
8968 a use-after-free pattern. As such, we are now tracking that bug as
8969 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
8970 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
8972 This release also fixes several minor bugs and annoyances from
8975 Relays running 0.3.2.x should upgrade to one of the versions released
8976 today, for the fix to TROVE-2018-002. Directory authorities should
8977 also upgrade. (Relays on earlier versions might want to update too for
8978 the DoS mitigations.)
8980 o Major bugfixes (denial-of-service, directory authority):
8981 - Fix a protocol-list handling bug that could be used to remotely crash
8982 directory authorities with a null-pointer exception. Fixes bug 25074;
8983 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
8986 o Minor features (compatibility, OpenSSL):
8987 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
8988 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
8989 since they neither disabled TLS 1.3 nor enabled any of the
8990 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
8991 Closes ticket 24978.
8993 o Minor features (logging):
8994 - Clarify the log messages produced when getrandom() or a related
8995 entropy-generation mechanism gives an error. Closes ticket 25120.
8997 o Minor features (testing):
8998 - Add a "make test-rust" target to run the rust tests only. Closes
9001 o Minor bugfixes (denial-of-service):
9002 - Fix a possible crash on malformed consensus. If a consensus had
9003 contained an unparseable protocol line, it could have made clients
9004 and relays crash with a null-pointer exception. To exploit this
9005 issue, however, an attacker would need to be able to subvert the
9006 directory authority system. Fixes bug 25251; bugfix on
9007 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
9009 o Minor bugfixes (DoS mitigation):
9010 - Add extra safety checks when refilling the circuit creation bucket
9011 to ensure we never set a value above the allowed maximum burst.
9012 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
9013 - When a new consensus arrives, don't update our DoS-mitigation
9014 parameters if we aren't a public relay. Fixes bug 25223; bugfix
9017 o Minor bugfixes (man page, SocksPort):
9018 - Remove dead code from the old "SocksSocket" option, and rename
9019 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
9020 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
9022 o Minor bugfixes (performance):
9023 - Reduce the number of circuits that will be opened at once during
9024 the circuit build timeout phase. This is done by increasing the
9025 idle timeout to 3 minutes, and lowering the maximum number of
9026 concurrent learning circuits to 10. Fixes bug 24769; bugfix
9029 o Minor bugfixes (spec conformance):
9030 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
9032 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
9033 bugfix on 0.2.9.4-alpha.
9035 o Minor bugfixes (spec conformance, rust):
9036 - Resolve a denial-of-service issue caused by an infinite loop in
9037 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
9038 Also tracked as TROVE-2018-003.
9040 o Code simplification and refactoring:
9041 - Update the "rust dependencies" submodule to be a project-level
9042 repository, rather than a user repository. Closes ticket 25323.
9045 Changes in version 0.3.3.2-alpha - 2018-02-10
9046 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
9047 introduces a mechanism to handle the high loads that many relay
9048 operators have been reporting recently. It also fixes several bugs in
9049 older releases. If this new code proves reliable, we plan to backport
9050 it to older supported release series.
9052 o Major features (denial-of-service mitigation):
9053 - Give relays some defenses against the recent network overload. We
9054 start with three defenses (default parameters in parentheses).
9055 First: if a single client address makes too many concurrent
9056 connections (>100), hang up on further connections. Second: if a
9057 single client address makes circuits too quickly (more than 3 per
9058 second, with an allowed burst of 90) while also having too many
9059 connections open (3), refuse new create cells for the next while
9060 (1-2 hours). Third: if a client asks to establish a rendezvous
9061 point to you directly, ignore the request. These defenses can be
9062 manually controlled by new torrc options, but relays will also
9063 take guidance from consensus parameters, so there's no need to
9064 configure anything manually. Implements ticket 24902.
9066 o Major bugfixes (netflow padding):
9067 - Stop adding unneeded channel padding right after we finish
9068 flushing to a connection that has been trying to flush for many
9069 seconds. Instead, treat all partial or complete flushes as
9070 activity on the channel, which will defer the time until we need
9071 to add padding. This fix should resolve confusing and scary log
9072 messages like "Channel padding timeout scheduled 221453ms in the
9073 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
9075 o Major bugfixes (protocol versions):
9076 - Add Link protocol version 5 to the supported protocols list. Fixes
9077 bug 25070; bugfix on 0.3.1.1-alpha.
9079 o Major bugfixes (scheduler, consensus):
9080 - The scheduler subsystem was failing to promptly notice changes in
9081 consensus parameters, making it harder to switch schedulers
9082 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
9084 o Minor features (denial-of-service avoidance):
9085 - Make our OOM handler aware of the geoip client history cache so it
9086 doesn't fill up the memory. This check is important for IPv6 and
9087 our DoS mitigation subsystem. Closes ticket 25122.
9089 o Minor features (directory authority):
9090 - When directory authorities are unable to add signatures to a
9091 pending consensus, log the reason why. Closes ticket 24849.
9093 o Minor features (geoip):
9094 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
9097 o Minor features (logging, diagnostic):
9098 - When logging a failure to create an onion service's descriptor,
9099 also log what the problem with the descriptor was. Diagnostic for
9102 o Minor bugfix (channel connection):
9103 - Use the actual observed address of an incoming relay connection,
9104 not the canonical address of the relay from its descriptor, when
9105 making decisions about how to handle the incoming connection.
9106 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
9108 o Minor bugfix (directory authority):
9109 - Directory authorities, when refusing a descriptor from a rejected
9110 relay, now explicitly tell the relay (in its logs) to set a valid
9111 ContactInfo address and contact the bad-relays@ mailing list.
9112 Fixes bug 25170; bugfix on 0.2.9.1.
9114 o Minor bugfixes (all versions of Tor):
9115 - Use the "misspell" tool to detect and fix typos throughout the
9116 source code. Fixes bug 23650; bugfix on various versions of Tor.
9117 Patch from Deepesh Pathak.
9119 o Minor bugfixes (circuit, cannibalization):
9120 - Don't cannibalize preemptively-built circuits if we no longer
9121 recognize their first hop. This situation can happen if our Guard
9122 relay went off the consensus after the circuit was created. Fixes
9123 bug 24469; bugfix on 0.0.6.
9125 o Minor bugfixes (correctness):
9126 - Remove a nonworking, unnecessary check to see whether a circuit
9127 hop's identity digest was set when the circuit failed. Fixes bug
9128 24927; bugfix on 0.2.4.4-alpha.
9130 o Minor bugfixes (logging):
9131 - Don't treat inability to store a cached consensus object as a bug:
9132 it can happen normally when we are out of disk space. Fixes bug
9133 24859; bugfix on 0.3.1.1-alpha.
9134 - Fix a (mostly harmless) race condition when invoking
9135 LOG_PROTOCOL_WARN message from a subthread while the torrc options
9136 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
9138 o Minor bugfixes (onion services):
9139 - Remove a BUG() statement when a client fetches an onion descriptor
9140 that has a lower revision counter than the one in its cache. This
9141 can happen in normal circumstances due to HSDir desync. Fixes bug
9142 24976; bugfix on 0.3.2.1-alpha.
9143 - If we are configured to offer a single onion service, don't log
9144 long-term established one hop rendezvous points in the heartbeat.
9145 Fixes bug 25116; bugfix on 0.2.9.6-rc.
9147 o Minor bugfixes (performance):
9148 - Avoid calling protocol_list_supports_protocol() from inside tight
9149 loops when running with cached routerinfo_t objects. Instead,
9150 summarize the relevant protocols as flags in the routerinfo_t, as
9151 we do for routerstatus_t objects. This change simplifies our code
9152 a little, and saves a large amount of short-term memory allocation
9153 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
9155 o Minor bugfixes (Rust FFI):
9156 - Fix a minor memory leak which would happen whenever the C code
9157 would call the Rust implementation of
9158 protover_get_supported_protocols(). This was due to the C version
9159 returning a static string, whereas the Rust version newly allocated
9160 a CString to pass across the FFI boundary. Consequently, the C
9161 code was not expecting to need to free() what it was given. Fixes
9162 bug 25127; bugfix on 0.3.2.1-alpha.
9164 o Minor bugfixes (scheduler, KIST):
9165 - Avoid adding the same channel twice in the KIST scheduler pending
9166 list, which would waste CPU cycles. Fixes bug 24700; bugfix
9169 o Minor bugfixes (unit test, monotonic time):
9170 - Increase a constant (1msec to 10msec) in the monotonic time test
9171 that makes sure the nsec/usec/msec times read are synchronized.
9172 This change was needed to accommodate slow systems like armel or
9173 when the clock_gettime() is not a VDSO on the running kernel.
9174 Fixes bug 25113; bugfix on 0.2.9.1.
9176 o Minor bugfixes (v3 onion services):
9177 - Look at the "HSRend" protocol version, not the "HSDir" protocol
9178 version, when deciding whether a consensus entry can support the
9179 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
9180 bugfix on 0.3.2.1-alpha.
9182 o Code simplification and refactoring:
9183 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
9185 - Remove a series of counters used to track circuit extend attempts
9186 and connection status but that in reality we aren't using for
9187 anything other than stats logged by a SIGUSR1 signal. Closes
9190 o Documentation (man page):
9191 - The HiddenServiceVersion torrc option accepts only one number:
9192 either version 2 or 3. Closes ticket 25026; bugfix
9196 Changes in version 0.3.3.1-alpha - 2018-01-25
9197 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
9198 several new features to Tor, including several improvements to
9199 bootstrapping, and support for an experimental "vanguards" feature to
9200 resist guard discovery attacks. This series also includes better
9201 support for applications that need to embed Tor or manage v3
9204 o Major features (embedding):
9205 - There is now a documented stable API for programs that need to
9206 embed Tor. See tor_api.h for full documentation and known bugs.
9207 Closes ticket 23684.
9208 - Tor now has support for restarting in the same process.
9209 Controllers that run Tor using the "tor_api.h" interface can now
9210 restart Tor after Tor has exited. This support is incomplete,
9211 however: we fixed crash bugs that prevented it from working at
9212 all, but many bugs probably remain, including a possibility of
9213 security issues. Implements ticket 24581.
9215 o Major features (IPv6, directory documents):
9216 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
9217 consensus. This information makes it easier for IPv6 clients to
9218 bootstrap and choose reachable entry guards. Implements ticket 23826.
9219 - Add consensus method 28, which removes IPv6 ORPorts from
9220 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
9221 are redundant in microdescs. This change will be used by Tor clients
9222 on 0.2.8.x and later. (That is to say, with all Tor clients that
9223 have IPv6 bootstrap and guard support.) Implements ticket 23828.
9224 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
9225 set by different numbers of authorities. Fixes 23870
9228 o Major features (onion service v3, control port):
9229 - The control port now supports commands and events for v3 onion
9230 services. It is now possible to create ephemeral v3 services using
9231 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
9232 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
9233 DEL_ONION) have been extended to support v3 onion services. Closes
9234 ticket 20699; implements proposal 284.
9236 o Major features (onion services):
9237 - Provide torrc options to pin the second and third hops of onion
9238 service circuits to a list of nodes. The option HSLayer2Guards
9239 pins the second hop, and the option HSLayer3Guards pins the third
9240 hop. These options are for use in conjunction with experiments
9241 with "vanguards" for preventing guard enumeration attacks. Closes
9244 o Major features (rust, portability, experimental):
9245 - Tor now ships with an optional implementation of one of its
9246 smaller modules (protover.c) in the Rust programming language. To
9247 try it out, install a Rust build environment, and configure Tor
9248 with "--enable-rust --enable-cargo-online-mode". This should not
9249 cause any user-visible changes, but should help us gain more
9250 experience with Rust, and plan future Rust integration work.
9251 Implementation by Chelsea Komlo. Closes ticket 22840.
9253 o Minor features (storage, configuration):
9254 - Users can store cached directory documents somewhere other than
9255 the DataDirectory by using the CacheDirectory option. Similarly,
9256 the storage location for relay's keys can be overridden with the
9257 KeyDirectory option. Closes ticket 22703.
9259 o Major features (v3 onion services, ipv6):
9260 - When v3 onion service clients send introduce cells, they now
9261 include the IPv6 address of the rendezvous point, if it has one.
9262 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
9263 in future Tor versions, IPv6-only v3 single onion services will be
9264 able to use IPv6 addresses to connect directly to the rendezvous
9265 point. Closes ticket 23577. Patch by Neel Chauhan.
9267 o Major bugfixes (onion services, retry behavior):
9268 - Fix an "off by 2" error in counting rendezvous failures on the
9269 onion service side. While we thought we would stop the rendezvous
9270 attempt after one failed circuit, we were actually making three
9271 circuit attempts before giving up. Now switch to a default of 2,
9272 and allow the consensus parameter "hs_service_max_rdv_failures" to
9273 override. Fixes bug 24895; bugfix on 0.0.6.
9274 - New-style (v3) onion services now obey the "max rendezvous circuit
9275 attempts" logic. Previously they would make as many rendezvous
9276 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
9277 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
9279 o Major bugfixes (relays):
9280 - Fix a set of false positives where relays would consider
9281 connections to other relays as being client-only connections (and
9282 thus e.g. deserving different link padding schemes) if those
9283 relays fell out of the consensus briefly. Now we look only at the
9284 initial handshake and whether the connection authenticated as a
9285 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
9287 o Minor feature (IPv6):
9288 - Make IPv6-only clients wait for microdescs for relays, even if we
9289 were previously using descriptors (or were using them as a bridge)
9290 and have a cached descriptor for them. Implements ticket 23827.
9291 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
9292 them, rather than waiting to download microdescriptors.
9293 Implements ticket 23827.
9295 o Minor features (cleanup):
9296 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
9297 when it stops. Closes ticket 23271.
9299 o Minor features (defensive programming):
9300 - Most of the functions in Tor that free objects have been replaced
9301 with macros that free the objects and set the corresponding
9302 pointers to NULL. This change should help prevent a large class of
9303 dangling pointer bugs. Closes ticket 24337.
9304 - Where possible, the tor_free() macro now only evaluates its input
9305 once. Part of ticket 24337.
9306 - Check that microdesc ed25519 ids are non-zero in
9307 node_get_ed25519_id() before returning them. Implements ticket
9308 24001, patch by "aruna1234".
9310 o Minor features (embedding):
9311 - Tor can now start with a preauthenticated control connection
9312 created by the process that launched it. This feature is meant for
9313 use by programs that want to launch and manage a Tor process
9314 without allowing other programs to manage it as well. For more
9315 information, see the __OwningControllerFD option documented in
9316 control-spec.txt. Closes ticket 23900.
9317 - On most errors that would cause Tor to exit, it now tries to
9318 return from the tor_main() function, rather than calling the
9319 system exit() function. Most users won't notice a difference here,
9320 but it should be significant for programs that run Tor inside
9321 a separate thread: they should now be able to survive Tor's exit
9322 conditions rather than having Tor shut down the entire process.
9323 Closes ticket 23848.
9324 - Applications that want to embed Tor can now tell Tor not to
9325 register any of its own POSIX signal handlers, using the
9326 __DisableSignalHandlers option. Closes ticket 24588.
9328 o Minor features (fallback directory list):
9329 - Avoid selecting fallbacks that change their IP addresses too
9330 often. Select more fallbacks by ignoring the Guard flag, and
9331 allowing lower cutoffs for the Running and V2Dir flags. Also allow
9332 a lower bandwidth, and a higher number of fallbacks per operator
9333 (5% of the list). Implements ticket 24785.
9334 - Update the fallback whitelist and blacklist based on opt-ins and
9335 relay changes. Closes tickets 22321, 24678, 22527, 24135,
9338 o Minor features (fallback directory mirror configuration):
9339 - Add a nickname to each fallback in a C comment. This makes it
9340 easier for operators to find their relays, and allows stem to use
9341 nicknames to identify fallbacks. Implements ticket 24600.
9342 - Add a type and version header to the fallback directory mirror
9343 file. Also add a delimiter to the end of each fallback entry. This
9344 helps external parsers like stem and Relay Search. Implements
9346 - Add an extrainfo cache flag for each fallback in a C comment. This
9347 allows stem to use fallbacks to fetch extra-info documents, rather
9348 than using authorities. Implements ticket 22759.
9349 - Add the generateFallbackDirLine.py script for automatically
9350 generating fallback directory mirror lines from relay fingerprints.
9351 No more typos! Add the lookupFallbackDirContact.py script for
9352 automatically looking up operator contact info from relay
9353 fingerprints. Implements ticket 24706, patch by teor and atagar.
9354 - Reject any fallback directory mirror that serves an expired
9355 consensus. Implements ticket 20942, patch by "minik".
9356 - Remove commas and equals signs from external string inputs to the
9357 fallback list. This avoids format confusion attacks. Implements
9359 - Remove the "weight=10" line from fallback directory mirror
9360 entries. Ticket 24681 will maintain the current fallback weights
9361 by changing Tor's default fallback weight to 10. Implements
9363 - Stop logging excessive information about fallback netblocks.
9364 Implements ticket 24791.
9366 o Minor features (forward-compatibility):
9367 - If a relay supports some link authentication protocol that we do
9368 not recognize, then include that relay's ed25519 key when telling
9369 other relays to extend to it. Previously, we treated future
9370 versions as if they were too old to support ed25519 link
9371 authentication. Closes ticket 20895.
9373 o Minor features (heartbeat):
9374 - Add onion service information to our heartbeat logs, displaying
9375 stats about the activity of configured onion services. Closes
9378 o Minor features (instrumentation, development):
9379 - Add the MainloopStats option to allow developers to get
9380 instrumentation information from the main event loop via the
9381 heartbeat messages. We hope to use this to improve Tor's behavior
9382 when it's trying to sleep. Closes ticket 24605.
9384 o Minor features (log messages):
9385 - Improve a warning message that happens when we fail to re-parse an
9386 old router because of an expired certificate. Closes ticket 20020.
9387 - Make the log more quantitative when we hit MaxMemInQueues
9388 threshold exposing some values. Closes ticket 24501.
9390 o Minor features (logging, android):
9391 - Added support for the Android logging subsystem. Closes
9394 o Minor features (performance):
9395 - Support predictive circuit building for onion service circuits
9396 with multiple layers of guards. Closes ticket 23101.
9397 - Use stdatomic.h where available, rather than mutexes, to implement
9398 atomic_counter_t. Closes ticket 23953.
9400 o Minor features (performance, 32-bit):
9401 - Improve performance on 32-bit systems by avoiding 64-bit division
9402 when calculating the timestamp in milliseconds for channel padding
9403 computations. Implements ticket 24613.
9404 - Improve performance on 32-bit systems by avoiding 64-bit division
9405 when timestamping cells and buffer chunks for OOM calculations.
9406 Implements ticket 24374.
9408 o Minor features (performance, OSX, iOS):
9409 - Use the mach_approximate_time() function (when available) to
9410 implement coarse monotonic time. Having a coarse time function
9411 should avoid a large number of system calls, and improve
9412 performance slightly, especially under load. Closes ticket 24427.
9414 o Minor features (performance, windows):
9415 - Improve performance on Windows Vista and Windows 7 by adjusting
9416 TCP send window size according to the recommendation from
9417 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
9420 o Major features (relay):
9421 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
9422 operator to use a more reasonable ("reduced") exit policy, rather
9423 than the default one. If you want to run an exit node without
9424 thinking too hard about which ports to allow, this one is for you.
9425 Closes ticket 13605. Patch from Neel Chauhan.
9427 o Minor features (testing, debugging, embedding):
9428 - For development purposes, Tor now has a mode in which it runs for
9429 a few seconds, then stops, and starts again without exiting the
9430 process. This mode is meant to help us debug various issues with
9431 ticket 23847. To use this feature, compile with
9432 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
9433 environment variable. This is expected to crash a lot, and is
9434 really meant for developers only. It will likely be removed in a
9435 future release. Implements ticket 24583.
9437 o Minor bugfix (network IPv6 test):
9438 - Tor's test scripts now check if "ping -6 ::1" works when the user
9439 runs "make test-network-all". Fixes bug 24677; bugfix on
9440 0.2.9.3-alpha. Patch by "ffmancera".
9442 o Minor bugfixes (build, rust):
9443 - Fix output of autoconf checks to display success messages for Rust
9444 dependencies and a suitable rustc compiler version. Fixes bug
9445 24612; bugfix on 0.3.1.3-alpha.
9446 - When building with Rust on OSX, link against libresolv, to work
9447 around the issue at https://github.com/rust-lang/rust/issues/46797.
9448 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
9449 - Don't pass the --quiet option to cargo: it seems to suppress some
9450 errors, which is not what we want to do when building. Fixes bug
9451 24518; bugfix on 0.3.1.7.
9452 - Build correctly when building from outside Tor's source tree with
9453 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
9456 o Minor bugfixes (directory authorities, IPv6):
9457 - When creating a routerstatus (vote) from a routerinfo (descriptor),
9458 set the IPv6 address to the unspecified IPv6 address, and
9459 explicitly initialize the port to zero. Fixes bug 24488; bugfix
9462 o Minor bugfixes (fallback directory mirrors):
9463 - Make updateFallbackDirs.py search harder for python. (Some OSs
9464 don't put it in /usr/bin.) Fixes bug 24708; bugfix
9467 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
9468 - When hibernating, close connections normally and allow them to
9469 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
9471 - Do not attempt to launch self-reachability tests when entering
9472 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
9473 - Resolve several bugs related to descriptor fetching on bridge
9474 clients with bandwidth accounting enabled. (This combination is
9475 not recommended!) Fixes a case of bug 12062; bugfix
9477 - When hibernating, do not attempt to launch DNS checks. Fixes a
9478 case of bug 12062; bugfix on 0.1.2.2-alpha.
9479 - When hibernating, do not try to upload or download descriptors.
9480 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
9482 o Minor bugfixes (IPv6, bridges):
9483 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
9484 bugfix on 0.2.8.2-alpha.
9485 - Tor now sets IPv6 address in the routerstatus as well as in the
9486 router descriptors when updating addresses for a bridge. Closes
9487 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
9489 o Minor bugfixes (linux seccomp2 sandbox):
9490 - When running with the sandbox enabled, reload configuration files
9491 correctly even when %include was used. Previously we would crash.
9492 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
9494 o Minor bugfixes (memory leaks):
9495 - Avoid possible at-exit memory leaks related to use of Libevent's
9496 event_base_once() function. (This function tends to leak memory if
9497 the event_base is closed before the event fires.) Fixes bug 24584;
9498 bugfix on 0.2.8.1-alpha.
9499 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
9502 o Minor bugfixes (OSX):
9503 - Don't exit the Tor process if setrlimit() fails to change the file
9504 limit (which can happen sometimes on some versions of OSX). Fixes
9505 bug 21074; bugfix on 0.0.9pre5.
9507 o Minor bugfixes (performance, fragile-hardening):
9508 - Improve the performance of our consensus-diff application code
9509 when Tor is built with the --enable-fragile-hardening option set.
9510 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
9512 o Minor bugfixes (performance, timeouts):
9513 - Consider circuits for timeout as soon as they complete a hop. This
9514 is more accurate than applying the timeout in
9515 circuit_expire_building() because that function is only called
9516 once per second, which is now too slow for typical timeouts on the
9517 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
9518 - Use onion service circuits (and other circuits longer than 3 hops)
9519 to calculate a circuit build timeout. Previously, Tor only
9520 calculated its build timeout based on circuits that planned to be
9521 exactly 3 hops long. With this change, we include measurements
9522 from all circuits at the point where they complete their third
9523 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
9525 o Minor bugfixes (testing):
9526 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
9527 bugfix on 0.2.3.1-alpha.
9528 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
9529 25005; bugfix on 0.3.2.7-rc.
9531 o Code simplification and refactoring:
9532 - Remove /usr/athena from search path in configure.ac. Closes
9534 - Remove duplicate code in node_has_curve25519_onion_key() and
9535 node_get_curve25519_onion_key(), and add a check for a zero
9536 microdesc curve25519 onion key. Closes ticket 23966, patch by
9537 "aruna1234" and teor.
9538 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
9539 memory allocations with large numbers of OR connections (e.g.
9540 relays). Closes ticket 24119.
9541 - Separate the function that deletes ephemeral files when Tor
9543 - Small changes to Tor's buf_t API to make it suitable for use as a
9544 general-purpose safe string constructor. Closes ticket 22342.
9545 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
9546 avoid source code identifier confusion. Closes ticket 24467.
9547 - The tor_git_revision[] constant no longer needs to be redeclared
9548 by everything that links against the rest of Tor. Done as part of
9549 ticket 23845, to simplify our external API.
9550 - We make extend_info_from_node() use node_get_curve25519_onion_key()
9551 introduced in ticket 23577 to access the curve25519 public keys
9552 rather than accessing it directly. Closes ticket 23760. Patch by
9554 - Add a function to log channels' scheduler state changes to aid
9555 debugging efforts. Closes ticket 24531.
9558 - Add documentation on how to build tor with Rust dependencies
9559 without having to be online. Closes ticket 22907; bugfix
9561 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
9562 traffic. Closes ticket 24318.
9563 - Document that OutboundBindAddress doesn't apply to DNS requests.
9564 Closes ticket 22145. Patch from Aruna Maurya.
9565 - Document that operators who run more than one relay or bridge are
9566 expected to set MyFamily and ContactInfo correctly. Closes
9569 o Code simplification and refactoring (channels):
9570 - Remove the incoming and outgoing channel queues. These were never
9571 used, but still took up a step in our fast path.
9572 - The majority of the channel unit tests have been rewritten and the
9573 code coverage has now been raised to 83.6% for channel.c. Closes
9575 - Remove other dead code from the channel subsystem: All together,
9576 this cleanup has removed more than 1500 lines of code overall and
9577 adding very little except for unit test.
9579 o Code simplification and refactoring (circuit rendezvous):
9580 - Split the client-side rendezvous circuit lookup into two
9581 functions: one that returns only established circuits and another
9582 that returns all kinds of circuits. Closes ticket 23459.
9584 o Code simplification and refactoring (controller):
9585 - Make most of the variables in networkstatus_getinfo_by_purpose()
9586 const. Implements ticket 24489.
9589 Changes in version 0.3.2.9 - 2018-01-09
9590 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
9592 The 0.3.2 series includes our long-anticipated new onion service
9593 design, with numerous security features. (For more information, see
9594 our blog post at https://blog.torproject.org/fall-harvest.) We also
9595 have a new circuit scheduler algorithm for improved performance on
9596 relays everywhere (see https://blog.torproject.org/kist-and-tell),
9597 along with many smaller features and bugfixes.
9599 Per our stable release policy, we plan to support each stable release
9600 series for at least the next nine months, or for three months after
9601 the first stable release of the next series: whichever is longer. If
9602 you need a release with long-term support, we recommend that you stay
9603 with the 0.2.9 series.
9605 Below is a list of the changes since 0.3.2.8-rc. For a list of all
9606 changes since 0.3.1, see the ReleaseNotes file.
9608 o Minor features (fallback directory mirrors):
9609 - The fallback directory list has been re-generated based on the
9610 current status of the network. Tor uses fallback directories to
9611 bootstrap when it doesn't yet have up-to-date directory
9612 information. Closes ticket 24801.
9613 - Make the default DirAuthorityFallbackRate 0.1, so that clients
9614 prefer to bootstrap from fallback directory mirrors. This is a
9615 follow-up to 24679, which removed weights from the default
9616 fallbacks. Implements ticket 24681.
9618 o Minor features (geoip):
9619 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
9622 o Minor bugfixes (address selection):
9623 - When the fascist_firewall_choose_address_ functions don't find a
9624 reachable address, set the returned address to the null address
9625 and port. This is a precautionary measure, because some callers do
9626 not check the return value. Fixes bug 24736; bugfix
9629 o Minor bugfixes (compilation):
9630 - Resolve a few shadowed-variable warnings in the onion service
9631 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
9633 o Minor bugfixes (portability, msvc):
9634 - Fix a bug in the bit-counting parts of our timing-wheel code on
9635 MSVC. (Note that MSVC is still not a supported build platform, due
9636 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
9640 Changes in version 0.3.2.8-rc - 2017-12-21
9641 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
9642 schedulers that had led servers under heavy load to overload their
9643 outgoing connections. All relay operators running earlier 0.3.2.x
9644 versions should upgrade. This version also includes a mitigation for
9645 over-full DESTROY queues leading to out-of-memory conditions: if it
9646 works, we will soon backport it to earlier release series.
9648 This is the second release candidate in the 0.3.2 series. If we find
9649 no new bugs or regression here, then the first stable 0.3.2 release
9650 will be nearly identical to this.
9652 o Major bugfixes (KIST, scheduler):
9653 - The KIST scheduler did not correctly account for data already
9654 enqueued in each connection's send socket buffer, particularly in
9655 cases when the TCP/IP congestion window was reduced between
9656 scheduler calls. This situation lead to excessive per-connection
9657 buffering in the kernel, and a potential memory DoS. Fixes bug
9658 24665; bugfix on 0.3.2.1-alpha.
9660 o Minor features (geoip):
9661 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
9664 o Minor bugfixes (hidden service v3):
9665 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
9666 the probability of reaching a service for a client missing
9667 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
9669 o Minor bugfixes (memory usage):
9670 - When queuing DESTROY cells on a channel, only queue the circuit-id
9671 and reason fields: not the entire 514-byte cell. This fix should
9672 help mitigate any bugs or attacks that fill up these queues, and
9673 free more RAM for other uses. Fixes bug 24666; bugfix
9676 o Minor bugfixes (scheduler, KIST):
9677 - Use a sane write limit for KISTLite when writing onto a connection
9678 buffer instead of using INT_MAX and shoving as much as it can.
9679 Because the OOM handler cleans up circuit queues, we are better
9680 off at keeping them in that queue instead of the connection's
9681 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
9684 Changes in version 0.3.2.7-rc - 2017-12-14
9685 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
9686 including some that could affect reliability or correctness.
9688 This is the first release candidate in the 0.3.2 series. If we find no
9689 new bugs or regression here, then the first stable 0.3.2. release will
9690 be nearly identical to this.
9692 o Major bugfixes (circuit prediction):
9693 - Fix circuit prediction logic so that a client doesn't treat a port
9694 as being "handled" by a circuit if that circuit already has
9695 isolation settings on it. This change should make Tor clients more
9696 responsive by improving their chances of having a pre-created
9697 circuit ready for use when a request arrives. Fixes bug 18859;
9698 bugfix on 0.2.3.3-alpha.
9700 o Minor features (logging):
9701 - Provide better warnings when the getrandom() syscall fails. Closes
9704 o Minor features (portability):
9705 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
9706 (It doesn't yet work with the sandbox enabled.) Closes
9709 o Minor bugfixes (bridge clients, bootstrap):
9710 - Retry directory downloads when we get our first bridge descriptor
9711 during bootstrap or while reconnecting to the network. Keep
9712 retrying every time we get a bridge descriptor, until we have a
9713 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
9714 - Stop delaying bridge descriptor fetches when we have cached bridge
9715 descriptors. Instead, only delay bridge descriptor fetches when we
9716 have at least one reachable bridge. Fixes part of bug 24367;
9717 bugfix on 0.2.0.3-alpha.
9718 - Stop delaying directory fetches when we have cached bridge
9719 descriptors. Instead, only delay bridge descriptor fetches when
9720 all our bridges are definitely unreachable. Fixes part of bug
9721 24367; bugfix on 0.2.0.3-alpha.
9723 o Minor bugfixes (compilation):
9724 - Fix a signed/unsigned comparison warning introduced by our fix to
9725 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
9727 o Minor bugfixes (correctness):
9728 - Fix several places in our codebase where a C compiler would be
9729 likely to eliminate a check, based on assuming that undefined
9730 behavior had not happened elsewhere in the code. These cases are
9731 usually a sign of redundant checking or dubious arithmetic. Found
9732 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
9733 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
9736 o Minor bugfixes (onion service v3):
9737 - Fix a race where an onion service would launch a new intro circuit
9738 after closing an old one, but fail to register it before freeing
9739 the previously closed circuit. This bug was making the service
9740 unable to find the established intro circuit and thus not upload
9741 its descriptor, thus making a service unavailable for up to 24
9742 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
9744 o Minor bugfixes (scheduler, KIST):
9745 - Properly set the scheduler state of an unopened channel in the
9746 KIST scheduler main loop. This prevents a harmless but annoying
9747 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
9748 - Avoid a possible integer overflow when computing the available
9749 space on the TCP buffer of a channel. This had no security
9750 implications; but could make KIST allow too many cells on a
9751 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
9752 - Downgrade to "info" a harmless warning about the monotonic time
9753 moving backwards: This can happen on platform not supporting
9754 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
9757 Changes in version 0.3.2.6-alpha - 2017-12-01
9758 This version of Tor is the latest in the 0.3.2 alpha series. It
9759 includes fixes for several important security issues. All Tor users
9760 should upgrade to this release, or to one of the other releases coming
9763 o Major bugfixes (security):
9764 - Fix a denial of service bug where an attacker could use a
9765 malformed directory object to cause a Tor instance to pause while
9766 OpenSSL would try to read a passphrase from the terminal. (Tor
9767 instances run without a terminal, which is the case for most Tor
9768 packages, are not impacted.) Fixes bug 24246; bugfix on every
9769 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9770 Found by OSS-Fuzz as testcase 6360145429790720.
9771 - Fix a denial of service issue where an attacker could crash a
9772 directory authority using a malformed router descriptor. Fixes bug
9773 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
9775 - When checking for replays in the INTRODUCE1 cell data for a
9776 (legacy) onion service, correctly detect replays in the RSA-
9777 encrypted part of the cell. We were previously checking for
9778 replays on the entire cell, but those can be circumvented due to
9779 the malleability of Tor's legacy hybrid encryption. This fix helps
9780 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9781 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9784 o Major bugfixes (security, onion service v2):
9785 - Fix a use-after-free error that could crash v2 Tor onion services
9786 when they failed to open circuits while expiring introduction
9787 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9788 also tracked as TROVE-2017-013 and CVE-2017-8823.
9790 o Major bugfixes (security, relay):
9791 - When running as a relay, make sure that we never build a path
9792 through ourselves, even in the case where we have somehow lost the
9793 version of our descriptor appearing in the consensus. Fixes part
9794 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9795 as TROVE-2017-012 and CVE-2017-8822.
9796 - When running as a relay, make sure that we never choose ourselves
9797 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
9798 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
9800 o Minor feature (relay statistics):
9801 - Change relay bandwidth reporting stats interval from 4 hours to 24
9802 hours in order to reduce the efficiency of guard discovery
9803 attacks. Fixes ticket 23856.
9805 o Minor features (directory authority):
9806 - Add an IPv6 address for the "bastet" directory authority. Closes
9809 o Minor bugfixes (client):
9810 - By default, do not enable storage of client-side DNS values. These
9811 values were unused by default previously, but they should not have
9812 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
9815 Changes in version 0.3.1.9 - 2017-12-01:
9816 Tor 0.3.1.9 backports important security and stability fixes from the
9817 0.3.2 development series. All Tor users should upgrade to this
9818 release, or to another of the releases coming out today.
9820 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9821 - Fix a denial of service bug where an attacker could use a
9822 malformed directory object to cause a Tor instance to pause while
9823 OpenSSL would try to read a passphrase from the terminal. (Tor
9824 instances run without a terminal, which is the case for most Tor
9825 packages, are not impacted.) Fixes bug 24246; bugfix on every
9826 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9827 Found by OSS-Fuzz as testcase 6360145429790720.
9828 - Fix a denial of service issue where an attacker could crash a
9829 directory authority using a malformed router descriptor. Fixes bug
9830 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
9832 - When checking for replays in the INTRODUCE1 cell data for a
9833 (legacy) onion service, correctly detect replays in the RSA-
9834 encrypted part of the cell. We were previously checking for
9835 replays on the entire cell, but those can be circumvented due to
9836 the malleability of Tor's legacy hybrid encryption. This fix helps
9837 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9838 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9841 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
9842 - Fix a use-after-free error that could crash v2 Tor onion services
9843 when they failed to open circuits while expiring introduction
9844 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9845 also tracked as TROVE-2017-013 and CVE-2017-8823.
9847 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9848 - When running as a relay, make sure that we never build a path
9849 through ourselves, even in the case where we have somehow lost the
9850 version of our descriptor appearing in the consensus. Fixes part
9851 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9852 as TROVE-2017-012 and CVE-2017-8822.
9853 - When running as a relay, make sure that we never choose ourselves
9854 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
9855 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
9857 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
9858 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
9859 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
9860 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
9861 identifying and finding a workaround to this bug and to Moritz,
9862 Arthur Edelstein, and Roger for helping to track it down and
9865 o Minor features (bridge):
9866 - Bridges now include notice in their descriptors that they are
9867 bridges, and notice of their distribution status, based on their
9868 publication settings. Implements ticket 18329. For more fine-
9869 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9872 o Minor features (directory authority, backport from 0.3.2.6-alpha):
9873 - Add an IPv6 address for the "bastet" directory authority. Closes
9876 o Minor features (geoip):
9877 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9880 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
9881 - Avoid unnecessary calls to directory_fetches_from_authorities() on
9882 relays, to prevent spurious address resolutions and descriptor
9883 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
9884 bugfix on in 0.2.8.1-alpha.
9886 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
9887 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
9888 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
9890 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
9891 - When a circuit is marked for close, do not attempt to package any
9892 cells for channels on that circuit. Previously, we would detect
9893 this condition lower in the call stack, when we noticed that the
9894 circuit had no attached channel, and log an annoying message.
9895 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
9897 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
9898 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
9899 so it matches dir-spec.txt. Fixes bug 24262; bugfix
9902 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
9903 - Avoid a crash when transitioning from client mode to bridge mode.
9904 Previously, we would launch the worker threads whenever our
9905 "public server" mode changed, but not when our "server" mode
9906 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
9909 Changes in version 0.3.0.13 - 2017-12-01
9910 Tor 0.3.0.13 backports important security and stability bugfixes from
9911 later Tor releases. All Tor users should upgrade to this release, or
9912 to another of the releases coming out today.
9914 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
9915 2018. If you need a release with long-term support, please stick with
9916 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9918 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9919 - Fix a denial of service bug where an attacker could use a
9920 malformed directory object to cause a Tor instance to pause while
9921 OpenSSL would try to read a passphrase from the terminal. (Tor
9922 instances run without a terminal, which is the case for most Tor
9923 packages, are not impacted.) Fixes bug 24246; bugfix on every
9924 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9925 Found by OSS-Fuzz as testcase 6360145429790720.
9926 - Fix a denial of service issue where an attacker could crash a
9927 directory authority using a malformed router descriptor. Fixes bug
9928 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
9930 - When checking for replays in the INTRODUCE1 cell data for a
9931 (legacy) onion service, correctly detect replays in the RSA-
9932 encrypted part of the cell. We were previously checking for
9933 replays on the entire cell, but those can be circumvented due to
9934 the malleability of Tor's legacy hybrid encryption. This fix helps
9935 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9936 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9939 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
9940 - Fix a use-after-free error that could crash v2 Tor onion services
9941 when they failed to open circuits while expiring introduction
9942 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9943 also tracked as TROVE-2017-013 and CVE-2017-8823.
9945 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9946 - When running as a relay, make sure that we never build a path
9947 through ourselves, even in the case where we have somehow lost the
9948 version of our descriptor appearing in the consensus. Fixes part
9949 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9950 as TROVE-2017-012 and CVE-2017-8822.
9951 - When running as a relay, make sure that we never choose ourselves
9952 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
9953 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
9955 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
9956 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
9957 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
9958 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
9959 identifying and finding a workaround to this bug and to Moritz,
9960 Arthur Edelstein, and Roger for helping to track it down and
9963 o Minor features (security, windows, backport from 0.3.1.1-alpha):
9964 - Enable a couple of pieces of Windows hardening: one
9965 (HeapEnableTerminationOnCorruption) that has been on-by-default
9966 since Windows 8, and unavailable before Windows 7; and one
9967 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
9968 affect us, but shouldn't do any harm. Closes ticket 21953.
9970 o Minor features (bridge, backport from 0.3.1.9):
9971 - Bridges now include notice in their descriptors that they are
9972 bridges, and notice of their distribution status, based on their
9973 publication settings. Implements ticket 18329. For more fine-
9974 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9977 o Minor features (directory authority, backport from 0.3.2.6-alpha):
9978 - Add an IPv6 address for the "bastet" directory authority. Closes
9981 o Minor features (geoip):
9982 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9985 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
9986 - Avoid unnecessary calls to directory_fetches_from_authorities() on
9987 relays, to prevent spurious address resolutions and descriptor
9988 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
9989 bugfix on in 0.2.8.1-alpha.
9991 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
9992 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
9993 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
9995 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
9996 - When a circuit is marked for close, do not attempt to package any
9997 cells for channels on that circuit. Previously, we would detect
9998 this condition lower in the call stack, when we noticed that the
9999 circuit had no attached channel, and log an annoying message.
10000 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
10002 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
10003 - Avoid a crash when transitioning from client mode to bridge mode.
10004 Previously, we would launch the worker threads whenever our
10005 "public server" mode changed, but not when our "server" mode
10006 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
10008 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
10009 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
10010 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
10013 Changes in version 0.2.9.14 - 2017-12-01
10014 Tor 0.3.0.13 backports important security and stability bugfixes from
10015 later Tor releases. All Tor users should upgrade to this release, or
10016 to another of the releases coming out today.
10018 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
10019 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
10020 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
10021 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
10022 identifying and finding a workaround to this bug and to Moritz,
10023 Arthur Edelstein, and Roger for helping to track it down and
10026 o Major bugfixes (security, backport from 0.3.2.6-alpha):
10027 - Fix a denial of service bug where an attacker could use a
10028 malformed directory object to cause a Tor instance to pause while
10029 OpenSSL would try to read a passphrase from the terminal. (Tor
10030 instances run without a terminal, which is the case for most Tor
10031 packages, are not impacted.) Fixes bug 24246; bugfix on every
10032 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
10033 Found by OSS-Fuzz as testcase 6360145429790720.
10034 - Fix a denial of service issue where an attacker could crash a
10035 directory authority using a malformed router descriptor. Fixes bug
10036 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
10038 - When checking for replays in the INTRODUCE1 cell data for a
10039 (legacy) onion service, correctly detect replays in the RSA-
10040 encrypted part of the cell. We were previously checking for
10041 replays on the entire cell, but those can be circumvented due to
10042 the malleability of Tor's legacy hybrid encryption. This fix helps
10043 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
10044 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
10047 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
10048 - Fix a use-after-free error that could crash v2 Tor onion services
10049 when they failed to open circuits while expiring introduction
10050 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
10051 also tracked as TROVE-2017-013 and CVE-2017-8823.
10053 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
10054 - When running as a relay, make sure that we never build a path
10055 through ourselves, even in the case where we have somehow lost the
10056 version of our descriptor appearing in the consensus. Fixes part
10057 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
10058 as TROVE-2017-012 and CVE-2017-8822.
10060 o Minor features (bridge, backport from 0.3.1.9):
10061 - Bridges now include notice in their descriptors that they are
10062 bridges, and notice of their distribution status, based on their
10063 publication settings. Implements ticket 18329. For more fine-
10064 grained control of how a bridge is distributed, upgrade to 0.3.2.x
10067 o Minor features (directory authority, backport from 0.3.2.6-alpha):
10068 - Add an IPv6 address for the "bastet" directory authority. Closes
10071 o Minor features (geoip):
10072 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
10075 o Minor features (security, windows, backport from 0.3.1.1-alpha):
10076 - Enable a couple of pieces of Windows hardening: one
10077 (HeapEnableTerminationOnCorruption) that has been on-by-default
10078 since Windows 8, and unavailable before Windows 7; and one
10079 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
10080 affect us, but shouldn't do any harm. Closes ticket 21953.
10082 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
10083 - Avoid unnecessary calls to directory_fetches_from_authorities() on
10084 relays, to prevent spurious address resolutions and descriptor
10085 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
10086 bugfix on in 0.2.8.1-alpha.
10088 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
10089 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
10090 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
10092 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
10093 - When a circuit is marked for close, do not attempt to package any
10094 cells for channels on that circuit. Previously, we would detect
10095 this condition lower in the call stack, when we noticed that the
10096 circuit had no attached channel, and log an annoying message.
10097 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
10099 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
10100 - Avoid a crash when transitioning from client mode to bridge mode.
10101 Previously, we would launch the worker threads whenever our
10102 "public server" mode changed, but not when our "server" mode
10103 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
10105 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
10106 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
10107 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
10110 Changes in version 0.2.8.17 - 2017-12-01
10111 Tor 0.2.8.17 backports important security and stability bugfixes from
10112 later Tor releases. All Tor users should upgrade to this release, or
10113 to another of the releases coming out today.
10115 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
10116 2018. If you need a release with long-term support, please upgrade with
10117 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
10119 o Major bugfixes (security, backport from 0.3.2.6-alpha):
10120 - Fix a denial of service bug where an attacker could use a
10121 malformed directory object to cause a Tor instance to pause while
10122 OpenSSL would try to read a passphrase from the terminal. (Tor
10123 instances run without a terminal, which is the case for most Tor
10124 packages, are not impacted.) Fixes bug 24246; bugfix on every
10125 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
10126 Found by OSS-Fuzz as testcase 6360145429790720.
10127 - When checking for replays in the INTRODUCE1 cell data for a
10128 (legacy) onion service, correctly detect replays in the RSA-
10129 encrypted part of the cell. We were previously checking for
10130 replays on the entire cell, but those can be circumvented due to
10131 the malleability of Tor's legacy hybrid encryption. This fix helps
10132 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
10133 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
10136 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
10137 - Fix a use-after-free error that could crash v2 Tor onion services
10138 when they failed to open circuits while expiring introduction
10139 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
10140 also tracked as TROVE-2017-013 and CVE-2017-8823.
10142 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
10143 - When running as a relay, make sure that we never build a path through
10144 ourselves, even in the case where we have somehow lost the version of
10145 our descriptor appearing in the consensus. Fixes part of bug 21534;
10146 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
10149 o Minor features (bridge, backport from 0.3.1.9):
10150 - Bridges now include notice in their descriptors that they are
10151 bridges, and notice of their distribution status, based on their
10152 publication settings. Implements ticket 18329. For more fine-
10153 grained control of how a bridge is distributed, upgrade to 0.3.2.x
10156 o Minor features (directory authority, backport from 0.3.2.6-alpha):
10157 - Add an IPv6 address for the "bastet" directory authority. Closes
10160 o Minor features (geoip):
10161 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
10164 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
10165 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
10166 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
10169 Changes in version 0.2.5.16 - 2017-12-01
10170 Tor 0.2.5.13 backports important security and stability bugfixes from
10171 later Tor releases. All Tor users should upgrade to this release, or
10172 to another of the releases coming out today.
10174 Note: the Tor 0.2.5 series will no longer be supported after 1 May
10175 2018. If you need a release with long-term support, please upgrade to
10176 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
10178 o Major bugfixes (security, backport from 0.3.2.6-alpha):
10179 - Fix a denial of service bug where an attacker could use a
10180 malformed directory object to cause a Tor instance to pause while
10181 OpenSSL would try to read a passphrase from the terminal. (Tor
10182 instances run without a terminal, which is the case for most Tor
10183 packages, are not impacted.) Fixes bug 24246; bugfix on every
10184 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
10185 Found by OSS-Fuzz as testcase 6360145429790720.
10186 - When checking for replays in the INTRODUCE1 cell data for a
10187 (legacy) onion service, correctly detect replays in the RSA-
10188 encrypted part of the cell. We were previously checking for
10189 replays on the entire cell, but those can be circumvented due to
10190 the malleability of Tor's legacy hybrid encryption. This fix helps
10191 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
10192 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
10195 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
10196 - When running as a relay, make sure that we never build a path
10197 through ourselves, even in the case where we have somehow lost the
10198 version of our descriptor appearing in the consensus. Fixes part
10199 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
10200 as TROVE-2017-012 and CVE-2017-8822.
10202 o Minor features (bridge, backport from 0.3.1.9):
10203 - Bridges now include notice in their descriptors that they are
10204 bridges, and notice of their distribution status, based on their
10205 publication settings. Implements ticket 18329. For more fine-
10206 grained control of how a bridge is distributed, upgrade to 0.3.2.x
10209 o Minor features (geoip):
10210 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
10214 Changes in version 0.3.2.5-alpha - 2017-11-22
10215 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
10216 fixes several stability and reliability bugs, including a fix for
10217 intermittent bootstrapping failures that some people have been seeing
10218 since the 0.3.0.x series.
10220 Please test this alpha out -- many of these fixes will soon be
10221 backported to stable Tor versions if no additional bugs are found
10224 o Major bugfixes (bootstrapping):
10225 - Fetch descriptors aggressively whenever we lack enough to build
10226 circuits, regardless of how many descriptors we are missing.
10227 Previously, we would delay launching the fetch when we had fewer
10228 than 15 missing descriptors, even if some of those descriptors
10229 were blocking circuits from building. Fixes bug 23985; bugfix on
10230 0.1.1.11-alpha. The effects of this bug became worse in
10231 0.3.0.3-alpha, when we began treating missing descriptors from our
10232 primary guards as a reason to delay circuits.
10233 - Don't try fetching microdescriptors from relays that have failed
10234 to deliver them in the past. Fixes bug 23817; bugfix
10237 o Minor features (directory authority):
10238 - Make the "Exit" flag assignment only depend on whether the exit
10239 policy allows connections to ports 80 and 443. Previously relays
10240 would get the Exit flag if they allowed connections to one of
10241 these ports and also port 6667. Resolves ticket 23637.
10243 o Minor features (geoip):
10244 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
10247 o Minor features (linux seccomp2 sandbox):
10248 - Update the sandbox rules so that they should now work correctly
10249 with Glibc 2.26. Closes ticket 24315.
10251 o Minor features (logging):
10252 - Downgrade a pair of log messages that could occur when an exit's
10253 resolver gave us an unusual (but not forbidden) response. Closes
10255 - Improve the message we log when re-enabling circuit build timeouts
10256 after having received a consensus. Closes ticket 20963.
10258 o Minor bugfixes (compilation):
10259 - Fix a memory leak warning in one of the libevent-related
10260 configuration tests that could occur when manually specifying
10261 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
10262 Found and patched by Alex Xu.
10263 - When detecting OpenSSL on Windows from our configure script, make
10264 sure to try linking with the ws2_32 library. Fixes bug 23783;
10265 bugfix on 0.3.2.2-alpha.
10267 o Minor bugfixes (control port, linux seccomp2 sandbox):
10268 - Avoid a crash when attempting to use the seccomp2 sandbox together
10269 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
10272 o Minor bugfixes (control port, onion services):
10273 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
10274 HS_DESC event when a service is not able to upload a descriptor.
10275 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
10277 o Minor bugfixes (directory cache):
10278 - Recover better from empty or corrupt files in the consensus cache
10279 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
10280 - When a consensus diff calculation is only partially successful,
10281 only record the successful parts as having succeeded. Partial
10282 success can happen if (for example) one compression method fails
10283 but the others succeed. Previously we misrecorded all the
10284 calculations as having succeeded, which would later cause a
10285 nonfatal assertion failure. Fixes bug 24086; bugfix
10288 o Minor bugfixes (logging):
10289 - Only log once if we notice that KIST support is gone. Fixes bug
10290 24158; bugfix on 0.3.2.1-alpha.
10291 - Suppress a log notice when relay descriptors arrive. We already
10292 have a bootstrap progress for this so no need to log notice
10293 everytime tor receives relay descriptors. Microdescriptors behave
10294 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
10296 o Minor bugfixes (network layer):
10297 - When closing a connection via close_connection_immediately(), we
10298 mark it as "not blocked on bandwidth", to prevent later calls from
10299 trying to unblock it, and give it permission to read. This fixes a
10300 backtrace warning that can happen on relays under various
10301 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
10303 o Minor bugfixes (onion services):
10304 - The introduction circuit was being timed out too quickly while
10305 waiting for the rendezvous circuit to complete. Keep the intro
10306 circuit around longer instead of timing out and reopening new ones
10307 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
10308 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
10309 so it matches dir-spec.txt. Fixes bug 24262; bugfix
10311 - Silence a warning about failed v3 onion descriptor uploads that
10312 can happen naturally under certain edge cases. Fixes part of bug
10313 23662; bugfix on 0.3.2.1-alpha.
10315 o Minor bugfixes (tests):
10316 - Fix a memory leak in one of the bridge-distribution test cases.
10317 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
10318 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
10319 to correctly handle cases where a caller gives it an RSA key of
10320 under 160 bits. (This is not actually a bug in Tor itself, but
10321 rather in our fuzzing code.) Fixes bug 24247; bugfix on
10322 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
10325 - Add notes in man page regarding OS support for the various
10326 scheduler types. Attempt to use less jargon in the scheduler
10327 section. Closes ticket 24254.
10330 Changes in version 0.3.2.4-alpha - 2017-11-08
10331 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
10332 It fixes several stability and reliability bugs, especially including
10333 a major reliability issue that has been plaguing fast exit relays in
10336 o Major bugfixes (exit relays, DNS):
10337 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
10338 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
10339 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
10340 identifying and finding a workaround to this bug and to Moritz,
10341 Arthur Edelstein, and Roger for helping to track it down and
10344 o Major bugfixes (scheduler, channel):
10345 - Stop processing scheduled channels if they closed while flushing
10346 cells. This can happen if the write on the connection fails
10347 leading to the channel being closed while in the scheduler loop.
10348 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
10350 o Minor features (logging, scheduler):
10351 - Introduce a SCHED_BUG() function to log extra information about
10352 the scheduler state if we ever catch a bug in the scheduler.
10353 Closes ticket 23753.
10355 o Minor features (removed deprecations):
10356 - The ClientDNSRejectInternalAddresses flag can once again be set in
10357 non-testing Tor networks, so long as they do not use the default
10358 directory authorities. This change also removes the deprecation of
10359 this flag from 0.2.9.2-alpha. Closes ticket 21031.
10361 o Minor features (testing):
10362 - Our fuzzing tests now test the encrypted portions of v3 onion
10363 service descriptors. Implements more of 21509.
10365 o Minor bugfixes (directory client):
10366 - On failure to download directory information, delay retry attempts
10367 by a random amount based on the "decorrelated jitter" algorithm.
10368 Our previous delay algorithm tended to produce extra-long delays
10369 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
10371 o Minor bugfixes (IPv6, v3 single onion services):
10372 - Remove buggy code for IPv6-only v3 single onion services, and
10373 reject attempts to configure them. This release supports IPv4,
10374 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
10375 stack v3 single onion services. Fixes bug 23820; bugfix
10378 o Minor bugfixes (logging, relay):
10379 - Give only a protocol warning when the ed25519 key is not
10380 consistent between the descriptor and microdescriptor of a relay.
10381 This can happen, for instance, if the relay has been flagged
10382 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
10384 o Minor bugfixes (manpage, onion service):
10385 - Document that the HiddenServiceNumIntroductionPoints option is
10386 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
10387 bugfix on 0.3.2.1-alpha.
10389 o Minor bugfixes (memory leaks):
10390 - Fix a minor memory leak at exit in the KIST scheduler. This bug
10391 should have no user-visible impact. Fixes bug 23774; bugfix
10393 - Fix a memory leak when decrypting a badly formatted v3 onion
10394 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
10395 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
10397 o Minor bugfixes (onion services):
10398 - Cache some needed onion service client information instead of
10399 constantly computing it over and over again. Fixes bug 23623;
10400 bugfix on 0.3.2.1-alpha.
10401 - Properly retry HSv3 descriptor fetches when missing required
10402 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
10404 o Minor bugfixes (path selection):
10405 - When selecting relays by bandwidth, avoid a rounding error that
10406 could sometimes cause load to be imbalanced incorrectly.
10407 Previously, we would always round upwards; now, we round towards
10408 the nearest integer. This had the biggest effect when a relay's
10409 weight adjustments should have given it weight 0, but it got
10410 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
10411 - When calculating the fraction of nodes that have descriptors, and
10412 all nodes in the network have zero bandwidths, count the number of
10413 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
10414 - Actually log the total bandwidth in compute_weighted_bandwidths().
10415 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
10417 o Minor bugfixes (relay, crash):
10418 - Avoid a crash when transitioning from client mode to bridge mode.
10419 Previously, we would launch the worker threads whenever our
10420 "public server" mode changed, but not when our "server" mode
10421 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
10423 o Minor bugfixes (testing):
10424 - Fix a spurious fuzzing-only use of an uninitialized value. Found
10425 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
10426 - Test that IPv6-only clients can use microdescriptors when running
10427 "make test-network-all". Requires chutney master 61c28b9 or later.
10428 Closes ticket 24109.
10431 Changes in version 0.3.2.3-alpha - 2017-10-27
10432 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
10433 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
10434 directory authority, Bastet.
10436 o Directory authority changes:
10437 - Add "Bastet" as a ninth directory authority to the default list.
10438 Closes ticket 23910.
10439 - The directory authority "Longclaw" has changed its IP address.
10440 Closes ticket 23592.
10442 o Minor features (bridge):
10443 - Bridge relays can now set the BridgeDistribution config option to
10444 add a "bridge-distribution-request" line to their bridge
10445 descriptor, which tells BridgeDB how they'd like their bridge
10446 address to be given out. (Note that as of Oct 2017, BridgeDB does
10447 not yet implement this feature.) As a side benefit, this feature
10448 provides a way to distinguish bridge descriptors from non-bridge
10449 descriptors. Implements tickets 18329.
10451 o Minor features (client, entry guards):
10452 - Improve log messages when missing descriptors for primary guards.
10453 Resolves ticket 23670.
10455 o Minor features (geoip):
10456 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10459 o Minor bugfixes (bridge):
10460 - Overwrite the bridge address earlier in the process of retrieving
10461 its descriptor, to make sure we reach it on the configured
10462 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
10464 o Minor bugfixes (documentation):
10465 - Document better how to read gcov, and what our gcov postprocessing
10466 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
10468 o Minor bugfixes (entry guards):
10469 - Tor now updates its guard state when it reads a consensus
10470 regardless of whether it's missing descriptors. That makes tor use
10471 its primary guards to fetch descriptors in some edge cases where
10472 it would previously have used fallback directories. Fixes bug
10473 23862; bugfix on 0.3.0.1-alpha.
10475 o Minor bugfixes (hidden service client):
10476 - When handling multiple SOCKS request for the same .onion address,
10477 only fetch the service descriptor once.
10478 - When a descriptor fetch fails with a non-recoverable error, close
10479 all pending SOCKS requests for that .onion. Fixes bug 23653;
10480 bugfix on 0.3.2.1-alpha.
10482 o Minor bugfixes (hidden service):
10483 - Always regenerate missing hidden service public key files. Prior
10484 to this, if the public key was deleted from disk, it wouldn't get
10485 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
10487 - Make sure that we have a usable ed25519 key when the intro point
10488 relay supports ed25519 link authentication. Fixes bug 24002;
10489 bugfix on 0.3.2.1-alpha.
10491 o Minor bugfixes (hidden service, v2):
10492 - When reloading configured hidden services, copy all information
10493 from the old service object. Previously, some data was omitted,
10494 causing delays in descriptor upload, and other bugs. Fixes bug
10495 23790; bugfix on 0.2.1.9-alpha.
10497 o Minor bugfixes (memory safety, defensive programming):
10498 - Clear the target address when node_get_prim_orport() returns
10499 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
10501 o Minor bugfixes (relay):
10502 - Avoid a BUG warning when receiving a dubious CREATE cell while an
10503 option transition is in progress. Fixes bug 23952; bugfix
10506 o Minor bugfixes (testing):
10507 - Adjust the GitLab CI configuration to more closely match that of
10508 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
10509 - Prevent scripts/test/coverage from attempting to move gcov output
10510 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
10511 - When running unit tests as root, skip a test that would fail
10512 because it expects a permissions error. This affects some
10513 continuous integration setups. Fixes bug 23758; bugfix
10515 - Stop unconditionally mirroring the tor repository in GitLab CI.
10516 This prevented developers from enabling GitLab CI on master. Fixes
10517 bug 23755; bugfix on 0.3.2.2-alpha.
10518 - Fix the hidden service v3 descriptor decoding fuzzing to use the
10519 latest decoding API correctly. Fixes bug 21509; bugfix
10522 o Minor bugfixes (warnings):
10523 - When we get an HTTP request on a SOCKS port, tell the user about
10524 the new HTTPTunnelPort option. Previously, we would give a "Tor is
10525 not an HTTP Proxy" message, which stopped being true when
10526 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
10530 Changes in version 0.2.5.15 - 2017-10-25
10531 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
10532 series. It also adds a new directory authority, Bastet.
10534 Note: the Tor 0.2.5 series will no longer be supported after 1 May
10535 2018. If you need a release with long-term support, please upgrade to
10536 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
10538 o Directory authority changes:
10539 - Add "Bastet" as a ninth directory authority to the default list.
10540 Closes ticket 23910.
10541 - The directory authority "Longclaw" has changed its IP address.
10542 Closes ticket 23592.
10544 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
10545 - Avoid an assertion failure bug affecting our implementation of
10546 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
10547 handling of "0xx" differs from what we had expected. Fixes bug
10548 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
10550 o Minor features (geoip):
10551 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10554 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
10555 - Fix a memset() off the end of an array when packing cells. This
10556 bug should be harmless in practice, since the corrupted bytes are
10557 still in the same structure, and are always padding bytes,
10558 ignored, or immediately overwritten, depending on compiler
10559 behavior. Nevertheless, because the memset()'s purpose is to make
10560 sure that any other cell-handling bugs can't expose bytes to the
10561 network, we need to fix it. Fixes bug 22737; bugfix on
10562 0.2.4.11-alpha. Fixes CID 1401591.
10564 o Build features (backport from 0.3.1.5-alpha):
10565 - Tor's repository now includes a Travis Continuous Integration (CI)
10566 configuration file (.travis.yml). This is meant to help new
10567 developers and contributors who fork Tor to a Github repository be
10568 better able to test their changes, and understand what we expect
10569 to pass. To use this new build feature, you must fork Tor to your
10570 Github account, then go into the "Integrations" menu in the
10571 repository settings for your fork and enable Travis, then push
10572 your changes. Closes ticket 22636.
10575 Changes in version 0.2.8.16 - 2017-10-25
10576 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
10577 series, including a bugfix for a crash issue that had affected relays
10578 under memory pressure. It also adds a new directory authority, Bastet.
10580 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
10581 2018. If you need a release with long-term support, please stick with
10582 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
10584 o Directory authority changes:
10585 - Add "Bastet" as a ninth directory authority to the default list.
10586 Closes ticket 23910.
10587 - The directory authority "Longclaw" has changed its IP address.
10588 Closes ticket 23592.
10590 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
10591 - Fix a timing-based assertion failure that could occur when the
10592 circuit out-of-memory handler freed a connection's output buffer.
10593 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10595 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
10596 - Remove longclaw's IPv6 address, as it will soon change. Authority
10597 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10598 3/8 directory authorities with IPv6 addresses, but there are also
10599 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10601 o Minor features (geoip):
10602 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10606 Changes in version 0.2.9.13 - 2017-10-25
10607 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
10608 series, including a bugfix for a crash issue that had affected relays
10609 under memory pressure. It also adds a new directory authority, Bastet.
10611 o Directory authority changes:
10612 - Add "Bastet" as a ninth directory authority to the default list.
10613 Closes ticket 23910.
10614 - The directory authority "Longclaw" has changed its IP address.
10615 Closes ticket 23592.
10617 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
10618 - Fix a timing-based assertion failure that could occur when the
10619 circuit out-of-memory handler freed a connection's output buffer.
10620 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10622 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
10623 - Remove longclaw's IPv6 address, as it will soon change. Authority
10624 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10625 3/8 directory authorities with IPv6 addresses, but there are also
10626 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10628 o Minor features (geoip):
10629 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10632 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
10633 - When a directory authority rejects a descriptor or extrainfo with
10634 a given digest, mark that digest as undownloadable, so that we do
10635 not attempt to download it again over and over. We previously
10636 tried to avoid downloading such descriptors by other means, but we
10637 didn't notice if we accidentally downloaded one anyway. This
10638 behavior became problematic in 0.2.7.2-alpha, when authorities
10639 began pinning Ed25519 keys. Fixes bug 22349; bugfix
10642 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
10643 - Clear the address when node_get_prim_orport() returns early.
10644 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
10646 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
10647 - When running as a Windows service, set the ID of the main thread
10648 correctly. Failure to do so made us fail to send log messages to
10649 the controller in 0.2.1.16-rc, slowed down controller event
10650 delivery in 0.2.7.3-rc and later, and crash with an assertion
10651 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
10652 Patch and diagnosis from "Vort".
10655 Changes in version 0.3.0.12 - 2017-10-25
10656 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
10657 series, including a bugfix for a crash issue that had affected relays
10658 under memory pressure. It also adds a new directory authority, Bastet.
10660 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
10661 2018. If you need a release with long-term support, please stick with
10662 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
10664 o Directory authority changes:
10665 - Add "Bastet" as a ninth directory authority to the default list.
10666 Closes ticket 23910.
10667 - The directory authority "Longclaw" has changed its IP address.
10668 Closes ticket 23592.
10670 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
10671 - Fix a timing-based assertion failure that could occur when the
10672 circuit out-of-memory handler freed a connection's output buffer.
10673 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10675 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
10676 - Remove longclaw's IPv6 address, as it will soon change. Authority
10677 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10678 3/8 directory authorities with IPv6 addresses, but there are also
10679 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10681 o Minor features (geoip):
10682 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10685 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
10686 - When a directory authority rejects a descriptor or extrainfo with
10687 a given digest, mark that digest as undownloadable, so that we do
10688 not attempt to download it again over and over. We previously
10689 tried to avoid downloading such descriptors by other means, but we
10690 didn't notice if we accidentally downloaded one anyway. This
10691 behavior became problematic in 0.2.7.2-alpha, when authorities
10692 began pinning Ed25519 keys. Fixes bug 22349; bugfix
10695 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
10696 - Avoid a possible double close of a circuit by the intro point on
10697 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
10698 bugfix on 0.3.0.1-alpha.
10700 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
10701 - Clear the address when node_get_prim_orport() returns early.
10702 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
10704 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
10705 - When running as a Windows service, set the ID of the main thread
10706 correctly. Failure to do so made us fail to send log messages to
10707 the controller in 0.2.1.16-rc, slowed down controller event
10708 delivery in 0.2.7.3-rc and later, and crash with an assertion
10709 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
10710 Patch and diagnosis from "Vort".
10713 Changes in version 0.3.1.8 - 2017-10-25
10714 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
10715 It includes several bugfixes, including a bugfix for a crash issue
10716 that had affected relays under memory pressure. It also adds
10717 a new directory authority, Bastet.
10719 o Directory authority changes:
10720 - Add "Bastet" as a ninth directory authority to the default list.
10721 Closes ticket 23910.
10722 - The directory authority "Longclaw" has changed its IP address.
10723 Closes ticket 23592.
10725 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
10726 - Fix a timing-based assertion failure that could occur when the
10727 circuit out-of-memory handler freed a connection's output buffer.
10728 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10730 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
10731 - Remove longclaw's IPv6 address, as it will soon change. Authority
10732 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10733 3/8 directory authorities with IPv6 addresses, but there are also
10734 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10736 o Minor features (geoip):
10737 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10740 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
10741 - Fix a compilation warning when building with zstd support on
10742 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
10743 and fixed by Andreas Stieger.
10745 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
10746 - Handle a pathological case when decompressing Zstandard data when
10747 the output buffer size is zero. Fixes bug 23551; bugfix
10750 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
10751 - Remove the length limit on HTTP status lines that authorities can
10752 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
10754 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
10755 - Avoid a possible double close of a circuit by the intro point on
10756 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
10757 bugfix on 0.3.0.1-alpha.
10759 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
10760 - Clear the address when node_get_prim_orport() returns early.
10761 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
10763 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
10764 - Fix additional channelpadding unit test failures by using mocked
10765 time instead of actual time for all tests. Fixes bug 23608; bugfix
10769 Changes in version 0.3.2.2-alpha - 2017-09-29
10770 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
10771 release fixes several minor bugs in the new scheduler and next-
10772 generation onion services; both features were newly added in the 0.3.2
10773 series. Other fixes in this alpha include several fixes for non-fatal
10774 tracebacks which would appear in logs.
10776 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
10777 alpha does not contain any substantial new features. Minor features
10778 include better testing and logging.
10780 The following comprises the complete list of changes included
10783 o Major bugfixes (relay, crash, assertion failure):
10784 - Fix a timing-based assertion failure that could occur when the
10785 circuit out-of-memory handler freed a connection's output buffer.
10786 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10788 o Major bugfixes (scheduler):
10789 - If a channel is put into the scheduler's pending list, then it
10790 starts closing, and then if the scheduler runs before it finishes
10791 closing, the scheduler will get stuck trying to flush its cells
10792 while the lower layers refuse to cooperate. Fix that race
10793 condition by giving the scheduler an escape method. Fixes bug
10794 23676; bugfix on 0.3.2.1-alpha.
10796 o Minor features (build, compilation):
10797 - The "check-changes" feature is now part of the "make check" tests;
10798 we'll use it to try to prevent misformed changes files from
10799 accumulating. Closes ticket 23564.
10800 - Tor builds should now fail if there are any mismatches between the
10801 C type representing a configuration variable and the C type the
10802 data-driven parser uses to store a value there. Previously, we
10803 needed to check these by hand, which sometimes led to mistakes.
10804 Closes ticket 23643.
10806 o Minor features (directory authorities):
10807 - Remove longclaw's IPv6 address, as it will soon change. Authority
10808 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10809 3/8 directory authorities with IPv6 addresses, but there are also
10810 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10812 o Minor features (hidden service, circuit, logging):
10813 - Improve logging of many callsite in the circuit subsystem to print
10814 the circuit identifier(s).
10815 - Log when we cleanup an intro point from a service so we know when
10816 and for what reason it happened. Closes ticket 23604.
10818 o Minor features (logging):
10819 - Log more circuit information whenever we are about to try to
10820 package a relay cell on a circuit with a nonexistent n_chan.
10821 Attempt to diagnose ticket 8185.
10822 - Improve info-level log identification of particular circuits, to
10823 help with debugging. Closes ticket 23645.
10825 o Minor features (relay):
10826 - When choosing which circuits can be expired as unused, consider
10827 circuits from clients even if those clients used regular CREATE
10828 cells to make them; and do not consider circuits from relays even
10829 if they were made with CREATE_FAST. Part of ticket 22805.
10831 o Minor features (robustness):
10832 - Change several fatal assertions when flushing buffers into non-
10833 fatal assertions, to prevent any recurrence of 23690.
10835 o Minor features (spec conformance, bridge, diagnostic):
10836 - When handling the USERADDR command on an ExtOrPort, warn when the
10837 transports provides a USERADDR with no port. In a future version,
10838 USERADDR commands of this format may be rejected. Detects problems
10839 related to ticket 23080.
10841 o Minor features (testing):
10842 - Add a unit test to make sure that our own generated platform
10843 string will be accepted by directory authorities. Closes
10846 o Minor bugfixes (bootstrapping):
10847 - When warning about state file clock skew, report the correct
10848 direction for the detected skew. Fixes bug 23606; bugfix
10850 - Avoid an assertion failure when logging a state file clock skew
10851 very early in bootstrapping. Fixes bug 23607; bugfix
10854 o Minor bugfixes (build, compilation):
10855 - Fix a compilation warning when building with zstd support on
10856 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
10857 and fixed by Andreas Stieger.
10858 - When searching for OpenSSL, don't accept any OpenSSL library that
10859 lacks TLSv1_1_method(): Tor doesn't build with those versions.
10860 Additionally, look in /usr/local/opt/openssl, if it's present.
10861 These changes together repair the default build on OSX systems
10862 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
10864 o Minor bugfixes (compression):
10865 - Handle a pathological case when decompressing Zstandard data when
10866 the output buffer size is zero. Fixes bug 23551; bugfix
10869 o Minor bugfixes (documentation):
10870 - Fix manpage to not refer to the obsolete (and misspelled)
10871 UseEntryGuardsAsDirectoryGuards parameter in the description of
10872 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
10874 o Minor bugfixes (hidden service v3):
10875 - Don't log an assertion failure when we can't find the right
10876 information to extend to an introduction point. In rare cases,
10877 this could happen, causing a warning, even though tor would
10878 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
10879 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
10880 much bigger so the rendezvous point can't distinguish which hidden
10881 service protocol is being used. Fixes bug 23420; bugfix
10884 o Minor bugfixes (hidden service, relay):
10885 - Avoid a possible double close of a circuit by the intro point on
10886 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
10887 bugfix on 0.3.0.1-alpha.
10889 o Minor bugfixes (logging, relay shutdown, annoyance):
10890 - When a circuit is marked for close, do not attempt to package any
10891 cells for channels on that circuit. Previously, we would detect
10892 this condition lower in the call stack, when we noticed that the
10893 circuit had no attached channel, and log an annoying message.
10894 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
10896 o Minor bugfixes (scheduler):
10897 - When switching schedulers due to a consensus change, we didn't
10898 give the new scheduler a chance to react to the consensus. Fix
10899 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
10900 - Make the KISTSchedRunInterval option a non negative value. With
10901 this, the way to disable KIST through the consensus is to set it
10902 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
10903 - Only notice log the selected scheduler when we switch scheduler
10904 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
10905 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
10906 by a different tv_usec data type. Fixes bug 23575; bugfix
10908 - Make a hard exit if tor is unable to pick a scheduler which can
10909 happen if the user specifies a scheduler type that is not
10910 supported and not other types in Schedulers. Fixes bug 23581;
10911 bugfix on 0.3.2.1-alpha.
10912 - Properly initialize the scheduler last run time counter so it is
10913 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
10915 o Minor bugfixes (testing):
10916 - Capture and detect several "Result does not fit" warnings in unit
10917 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
10919 - Fix additional channelpadding unit test failures by using mocked
10920 time instead of actual time for all tests. Fixes bug 23608; bugfix
10922 - The removal of some old scheduler options caused some tests to
10923 fail on BSD systems. Assume current behavior is correct and make
10924 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
10926 o Code simplification and refactoring:
10927 - Remove various ways of testing circuits and connections for
10928 "clientness"; instead, favor channel_is_client(). Part of
10931 o Deprecated features:
10932 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
10933 now deprecated; they do not apply to relays, and they have had no
10934 effect on clients since 0.2.8.x. Closes ticket 19704.
10937 - HiddenServiceVersion man page entry wasn't mentioning the now
10938 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
10939 - Clarify that the Address option is entirely about setting an
10940 advertised IPv4 address. Closes ticket 18891.
10941 - Clarify the manpage's use of the term "address" to clarify what
10942 kind of address is intended. Closes ticket 21405.
10943 - Document that onion service subdomains are allowed, and ignored.
10944 Closes ticket 18736.
10947 Changes in version 0.3.2.1-alpha - 2017-09-18
10948 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
10949 includes support for our next-generation ("v3") onion service
10950 protocol, and adds a new circuit scheduler for more responsive
10951 forwarding decisions from relays. There are also numerous other small
10952 features and bugfixes here.
10954 Below are the changes since Tor 0.3.1.7.
10956 o Major feature (scheduler, channel):
10957 - Tor now uses new schedulers to decide which circuits should
10958 deliver cells first, in order to improve congestion at relays. The
10959 first type is called "KIST" ("Kernel Informed Socket Transport"),
10960 and is only available on Linux-like systems: it uses feedback from
10961 the kernel to prevent the kernel's TCP buffers from growing too
10962 full. The second new scheduler type is called "KISTLite": it
10963 behaves the same as KIST, but runs on systems without kernel
10964 support for inspecting TCP implementation details. The old
10965 scheduler is still available, under the name "Vanilla". To change
10966 the default scheduler preference order, use the new "Schedulers"
10967 option. (The default preference order is "KIST,KISTLite,Vanilla".)
10969 Matt Traudt implemented KIST, based on research by Rob Jansen,
10970 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
10971 more information, see the design paper at
10972 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
10973 followup implementation paper at https://arxiv.org/abs/1709.01044.
10974 Closes ticket 12541.
10976 o Major features (next-generation onion services):
10977 - Tor now supports the next-generation onion services protocol for
10978 clients and services! As part of this release, the core of
10979 proposal 224 has been implemented and is available for
10980 experimentation and testing by our users. This newer version of
10981 onion services ("v3") features many improvements over the legacy
10984 a) Better crypto (replaced SHA1/DH/RSA1024
10985 with SHA3/ed25519/curve25519)
10987 b) Improved directory protocol, leaking much less information to
10990 c) Improved directory protocol, with smaller surface for
10993 d) Better onion address security against impersonation.
10995 e) More extensible introduction/rendezvous protocol.
10997 f) A cleaner and more modular codebase.
10999 You can identify a next-generation onion address by its length:
11000 they are 56 characters long, as in
11001 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
11003 In the future, we will release more options and features for v3
11004 onion services, but we first need a testing period, so that the
11005 current codebase matures and becomes more robust. Planned features
11006 include: offline keys, advanced client authorization, improved
11007 guard algorithms, and statistics. For full details, see
11010 Legacy ("v2") onion services will still work for the foreseeable
11011 future, and will remain the default until this new codebase gets
11012 tested and hardened. Service operators who want to experiment with
11013 the new system can use the 'HiddenServiceVersion 3' torrc
11014 directive along with the regular onion service configuration
11015 options. We will publish a blog post about this new feature
11018 o Major bugfixes (usability, control port):
11019 - Report trusted clock skew indications as bootstrap errors, so
11020 controllers can more easily alert users when their clocks are
11021 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
11023 o Minor features (bug detection):
11024 - Log a warning message with a stack trace for any attempt to call
11025 get_options() during option validation. This pattern has caused
11026 subtle bugs in the past. Closes ticket 22281.
11028 o Minor features (client):
11029 - You can now use Tor as a tunneled HTTP proxy: use the new
11030 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
11031 requests. Closes ticket 22407.
11032 - Add an extra check to make sure that we always use the newer guard
11033 selection code for picking our guards. Closes ticket 22779.
11034 - When downloading (micro)descriptors, don't split the list into
11035 multiple requests unless we want at least 32 descriptors.
11036 Previously, we split at 4, not 32, which led to significant
11037 overhead in HTTP request size and degradation in compression
11038 performance. Closes ticket 23220.
11040 o Minor features (command line):
11041 - Add a new commandline option, --key-expiration, which prints when
11042 the current signing key is going to expire. Implements ticket
11043 17639; patch by Isis Lovecruft.
11045 o Minor features (control port):
11046 - If an application tries to use the control port as an HTTP proxy,
11047 respond with a meaningful "This is the Tor control port" message,
11048 and log the event. Closes ticket 1667. Patch from Ravi
11050 - Provide better error message for GETINFO desc/(id|name) when not
11051 fetching router descriptors. Closes ticket 5847. Patch by
11053 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
11054 whether Tor will try to download router descriptors and
11055 microdescriptors respectively. Closes ticket 22684.
11056 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
11057 so controllers can tell whether the geoip databases are loaded.
11058 Closes ticket 23237.
11059 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
11060 events. Closes ticket 19254. Patch by "DonnchaC".
11062 o Minor features (development support):
11063 - Developers can now generate a call-graph for Tor using the
11064 "calltool" python program, which post-processes object dumps. It
11065 should work okay on many Linux and OSX platforms, and might work
11066 elsewhere too. To run it, install calltool from
11067 https://gitweb.torproject.org/user/nickm/calltool.git and run
11068 "make callgraph". Closes ticket 19307.
11070 o Minor features (ed25519):
11071 - Add validation function to checks for torsion components in
11072 ed25519 public keys, used by prop224 client-side code. Closes
11073 ticket 22006. Math help by Ian Goldberg.
11075 o Minor features (exit relay, DNS):
11076 - Improve the clarity and safety of the log message from evdns when
11077 receiving an apparently spoofed DNS reply. Closes ticket 3056.
11079 o Minor features (integration, hardening):
11080 - Add a new NoExec option to prevent Tor from running other
11081 programs. When this option is set to 1, Tor will never try to run
11082 another program, regardless of the settings of
11083 PortForwardingHelper, ClientTransportPlugin, or
11084 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
11085 without restarting Tor. Closes ticket 22976.
11087 o Minor features (logging):
11088 - Improve the warning message for specifying a relay by nickname.
11089 The previous message implied that nickname registration was still
11090 part of the Tor network design, which it isn't. Closes
11092 - If the sandbox filter fails to load, suggest to the user that
11093 their kernel might not support seccomp2. Closes ticket 23090.
11095 o Minor features (portability):
11096 - Check at configure time whether uint8_t is the same type as
11097 unsigned char. Lots of existing code already makes this
11098 assumption, and there could be strict aliasing issues if the
11099 assumption is violated. Closes ticket 22410.
11101 o Minor features (relay, configuration):
11102 - Reject attempts to use relative file paths when RunAsDaemon is
11103 set. Previously, Tor would accept these, but the directory-
11104 changing step of RunAsDaemon would give strange and/or confusing
11105 results. Closes ticket 22731.
11107 o Minor features (startup, safety):
11108 - When configured to write a PID file, Tor now exits if it is unable
11109 to do so. Previously, it would warn and continue. Closes
11112 o Minor features (static analysis):
11113 - The BUG() macro has been changed slightly so that Coverity no
11114 longer complains about dead code if the bug is impossible. Closes
11117 o Minor features (testing):
11118 - The default chutney network tests now include tests for the v3
11119 hidden service design. Make sure you have the latest version of
11120 chutney if you want to run these. Closes ticket 22437.
11121 - Add a unit test to verify that we can parse a hardcoded v2 hidden
11122 service descriptor. Closes ticket 15554.
11124 o Minor bugfixes (certificate handling):
11125 - Fix a time handling bug in Tor certificates set to expire after
11126 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
11127 Coverity as CID 1415728.
11129 o Minor bugfixes (client, usability):
11130 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
11131 SOCKS4a requests that contain IP address strings, even when
11132 SafeSocks in enabled, as this prevents user from connecting to
11133 known IP addresses without relying on DNS for resolving. SafeSocks
11134 still rejects SOCKS connections that connect to IP addresses when
11135 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
11136 bugfix on Tor 0.2.6.2-alpha.
11138 o Minor bugfixes (code correctness):
11139 - Call htons() in extend_cell_format() for encoding a 16-bit value.
11140 Previously we used ntohs(), which happens to behave the same on
11141 all the platforms we support, but which isn't really correct.
11142 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
11143 - For defense-in-depth, make the controller's write_escaped_data()
11144 function robust to extremely long inputs. Fixes bug 19281; bugfix
11145 on 0.1.1.1-alpha. Reported by Guido Vranken.
11147 o Minor bugfixes (compilation):
11148 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
11149 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
11151 o Minor bugfixes (consensus expiry):
11152 - Check for adequate directory information correctly. Previously, Tor
11153 would reconsider whether it had sufficient directory information
11154 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
11156 o Minor bugfixes (directory protocol):
11157 - Directory servers now include a "Date:" http header for response
11158 codes other than 200. Clients starting with a skewed clock and a
11159 recent consensus were getting "304 Not modified" responses from
11160 directory authorities, so without the Date header, the client
11161 would never hear about a wrong clock. Fixes bug 23499; bugfix
11163 - Make clients wait for 6 seconds before trying to download a
11164 consensus from an authority. Fixes bug 17750; bugfix
11167 o Minor bugfixes (DoS-resistance):
11168 - If future code asks if there are any running bridges, without
11169 checking if bridges are enabled, log a BUG warning rather than
11170 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
11172 o Minor bugfixes (format strictness):
11173 - Restrict several data formats to decimal. Previously, the
11174 BuildTimeHistogram entries in the state file, the "bw=" entries in
11175 the bandwidth authority file, and the process IDs passed to the
11176 __OwningControllerProcess option could all be specified in hex or
11177 octal as well as in decimal. This was not an intentional feature.
11178 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
11181 o Minor bugfixes (heartbeat):
11182 - If we fail to write a heartbeat message, schedule a retry for the
11183 minimum heartbeat interval number of seconds in the future. Fixes
11184 bug 19476; bugfix on 0.2.3.1-alpha.
11186 o Minor bugfixes (linux seccomp2 sandbox, logging):
11187 - Fix some messages on unexpected errors from the seccomp2 library.
11188 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
11190 o Minor bugfixes (logging):
11191 - Remove duplicate log messages regarding opening non-local
11192 SocksPorts upon parsing config and opening listeners at startup.
11193 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
11194 - Use a more comprehensible log message when telling the user
11195 they've excluded every running exit node. Fixes bug 7890; bugfix
11197 - When logging the number of descriptors we intend to download per
11198 directory request, do not log a number higher than then the number
11199 of descriptors we're fetching in total. Fixes bug 19648; bugfix
11201 - When warning about a directory owned by the wrong user, log the
11202 actual name of the user owning the directory. Previously, we'd log
11203 the name of the process owner twice. Fixes bug 23487; bugfix
11205 - The tor specification says hop counts are 1-based, so fix two log
11206 messages that mistakenly logged 0-based hop counts. Fixes bug
11207 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
11208 Credit to Xiaofan Li for reporting this issue.
11210 o Minor bugfixes (portability):
11211 - Stop using the PATH_MAX variable, which is not defined on GNU
11212 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
11214 o Minor bugfixes (relay):
11215 - When uploading our descriptor for the first time after startup,
11216 report the reason for uploading as "Tor just started" rather than
11217 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
11218 - Avoid unnecessary calls to directory_fetches_from_authorities() on
11219 relays, to prevent spurious address resolutions and descriptor
11220 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
11221 bugfix on in 0.2.8.1-alpha.
11223 o Minor bugfixes (tests):
11224 - Fix a broken unit test for the OutboundAddress option: the parsing
11225 function was never returning an error on failure. Fixes bug 23366;
11226 bugfix on 0.3.0.3-alpha.
11227 - Fix a signed-integer overflow in the unit tests for
11228 dir/download_status_random_backoff, which was untriggered until we
11229 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
11231 o Minor bugfixes (usability, control port):
11232 - Stop making an unnecessary routerlist check in NETINFO clock skew
11233 detection; this was preventing clients from reporting NETINFO clock
11234 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
11236 o Code simplification and refactoring:
11237 - Extract the code for handling newly-open channels into a separate
11238 function from the general code to handle channel state
11239 transitions. This change simplifies our callgraph, reducing the
11240 size of the largest strongly connected component by roughly a
11241 factor of two. Closes ticket 22608.
11242 - Remove dead code for largely unused statistics on the number of
11243 times we've attempted various public key operations. Fixes bug
11244 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
11245 - Remove several now-obsolete functions for asking about old
11246 variants directory authority status. Closes ticket 22311; patch
11248 - Remove some of the code that once supported "Named" and "Unnamed"
11249 routers. Authorities no longer vote for these flags. Closes
11251 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
11252 and old hidden services, to indicate that they aren't suitable for
11253 new protocols or formats. Closes ticket 23026.
11254 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
11255 22521. Patch from Neel Chauhan.
11256 - Split the enormous circuit_send_next_onion_skin() function into
11257 multiple subfunctions. Closes ticket 22804.
11258 - Split the portions of the buffer.c module that handle particular
11259 protocols into separate modules. Part of ticket 23149.
11260 - Use our test macros more consistently, to produce more useful
11261 error messages when our unit tests fail. Add coccinelle patches to
11262 allow us to re-check for test macro uses. Closes ticket 22497.
11264 o Deprecated features:
11265 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
11266 only applies to direct unencrypted HTTP connections to your
11267 directory server, which your Tor probably isn't using. Closes
11271 - Clarify in the manual that "Sandbox 1" is only supported on Linux
11272 kernels. Closes ticket 22677.
11273 - Document all values of PublishServerDescriptor in the manpage.
11274 Closes ticket 15645.
11275 - Improve the documentation for the directory port part of the
11276 DirAuthority line. Closes ticket 20152.
11277 - Restore documentation for the authorities' "approved-routers"
11278 file. Closes ticket 21148.
11280 o Removed features:
11281 - The AllowDotExit option has been removed as unsafe. It has been
11282 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
11283 - The ClientDNSRejectInternalAddresses flag can no longer be set on
11284 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
11285 Closes ticket 21031.
11286 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
11287 nobody was using it any longer. Closes ticket 22377.
11290 Changes in version 0.2.8.15 - 2017-09-18
11291 Tor 0.2.8.15 backports a collection of bugfixes from later
11294 Most significantly, it includes a fix for TROVE-2017-008, a
11295 security bug that affects hidden services running with the
11296 SafeLogging option disabled. For more information, see
11297 https://trac.torproject.org/projects/tor/ticket/23490
11299 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
11300 2018. We suggest that you upgrade to the latest stable release if
11301 possible. If you can't, we recommend that you upgrade at least to
11302 0.2.9, which will be supported until 2020.
11304 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
11305 - Avoid an assertion failure bug affecting our implementation of
11306 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
11307 handling of "0xx" differs from what we had expected. Fixes bug
11308 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
11311 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
11314 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
11315 - Backport a fix for an "unused variable" warning that appeared
11316 in some versions of mingw. Fixes bug 22838; bugfix on
11319 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
11320 - Fix a memset() off the end of an array when packing cells. This
11321 bug should be harmless in practice, since the corrupted bytes are
11322 still in the same structure, and are always padding bytes,
11323 ignored, or immediately overwritten, depending on compiler
11324 behavior. Nevertheless, because the memset()'s purpose is to make
11325 sure that any other cell-handling bugs can't expose bytes to the
11326 network, we need to fix it. Fixes bug 22737; bugfix on
11327 0.2.4.11-alpha. Fixes CID 1401591.
11329 o Build features (backport from 0.3.1.5-alpha):
11330 - Tor's repository now includes a Travis Continuous Integration (CI)
11331 configuration file (.travis.yml). This is meant to help new
11332 developers and contributors who fork Tor to a Github repository be
11333 better able to test their changes, and understand what we expect
11334 to pass. To use this new build feature, you must fork Tor to your
11335 Github account, then go into the "Integrations" menu in the
11336 repository settings for your fork and enable Travis, then push
11337 your changes. Closes ticket 22636.
11340 Changes in version 0.2.9.12 - 2017-09-18
11341 Tor 0.2.9.12 backports a collection of bugfixes from later
11344 Most significantly, it includes a fix for TROVE-2017-008, a
11345 security bug that affects hidden services running with the
11346 SafeLogging option disabled. For more information, see
11347 https://trac.torproject.org/projects/tor/ticket/23490
11349 o Major features (security, backport from 0.3.0.2-alpha):
11350 - Change the algorithm used to decide DNS TTLs on client and server
11351 side, to better resist DNS-based correlation attacks like the
11352 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
11353 Feamster. Now relays only return one of two possible DNS TTL
11354 values, and clients are willing to believe DNS TTL values up to 3
11355 hours long. Closes ticket 19769.
11357 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
11358 - Fix a rare crash when sending a begin cell on a circuit whose
11359 linked directory connection had already been closed. Fixes bug
11360 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
11362 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
11363 - Fix a bug that prevented exit nodes from caching DNS records for
11364 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
11366 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
11367 - Fix a typo that had prevented TPROXY-based transparent proxying
11368 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
11369 Patch from "d4fq0fQAgoJ".
11371 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
11372 - Avoid an assertion failure bug affecting our implementation of
11373 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
11374 handling of "0xx" differs from what we had expected. Fixes bug
11375 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
11377 o Minor features (code style, backport from 0.3.1.3-alpha):
11378 - Add "Falls through" comments to our codebase, in order to silence
11379 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
11380 Stieger. Closes ticket 22446.
11382 o Minor features (geoip):
11383 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
11386 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
11387 - Roll over monthly accounting at the configured hour and minute,
11388 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
11389 Found by Andrey Karpov with PVS-Studio.
11391 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
11392 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
11393 bugfix on 0.2.8.1-alpha.
11394 - Fix warnings when building with libscrypt and openssl scrypt support
11395 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
11396 - When building with certain versions the mingw C header files, avoid
11397 float-conversion warnings when calling the C functions isfinite(),
11398 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
11400 o Minor bugfixes (compilation, backport from 0.3.1.7):
11401 - Avoid compiler warnings in the unit tests for running tor_sscanf()
11402 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
11404 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
11405 - Backport a fix for an "unused variable" warning that appeared
11406 in some versions of mingw. Fixes bug 22838; bugfix on
11409 o Minor bugfixes (controller, backport from 0.3.1.7):
11410 - Do not crash when receiving a HSPOST command with an empty body.
11411 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
11412 - Do not crash when receiving a POSTDESCRIPTOR command with an
11413 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
11415 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
11416 - Avoid Coverity build warnings related to our BUG() macro. By
11417 default, Coverity treats BUG() as the Linux kernel does: an
11418 instant abort(). We need to override that so our BUG() macro
11419 doesn't prevent Coverity from analyzing functions that use it.
11420 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
11422 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
11423 - Fix a memset() off the end of an array when packing cells. This
11424 bug should be harmless in practice, since the corrupted bytes are
11425 still in the same structure, and are always padding bytes,
11426 ignored, or immediately overwritten, depending on compiler
11427 behavior. Nevertheless, because the memset()'s purpose is to make
11428 sure that any other cell-handling bugs can't expose bytes to the
11429 network, we need to fix it. Fixes bug 22737; bugfix on
11430 0.2.4.11-alpha. Fixes CID 1401591.
11432 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
11433 - When setting the maximum number of connections allowed by the OS,
11434 always allow some extra file descriptors for other files. Fixes
11435 bug 22797; bugfix on 0.2.0.10-alpha.
11437 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
11438 - Avoid a sandbox failure when trying to re-bind to a socket and
11439 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
11441 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
11442 - Permit the fchmod system call, to avoid crashing on startup when
11443 starting with the seccomp2 sandbox and an unexpected set of
11444 permissions on the data directory or its contents. Fixes bug
11445 22516; bugfix on 0.2.5.4-alpha.
11447 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
11448 - Avoid a double-marked-circuit warning that could happen when we
11449 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
11452 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
11453 - Reject version numbers with non-numeric prefixes (such as +, -, or
11454 whitespace). Disallowing whitespace prevents differential version
11455 parsing between POSIX-based and Windows platforms. Fixes bug 21507
11456 and part of 21508; bugfix on 0.0.8pre1.
11458 o Build features (backport from 0.3.1.5-alpha):
11459 - Tor's repository now includes a Travis Continuous Integration (CI)
11460 configuration file (.travis.yml). This is meant to help new
11461 developers and contributors who fork Tor to a Github repository be
11462 better able to test their changes, and understand what we expect
11463 to pass. To use this new build feature, you must fork Tor to your
11464 Github account, then go into the "Integrations" menu in the
11465 repository settings for your fork and enable Travis, then push
11466 your changes. Closes ticket 22636.
11469 Changes in version 0.3.0.11 - 2017-09-18
11470 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
11473 Most significantly, it includes a fix for TROVE-2017-008, a
11474 security bug that affects hidden services running with the
11475 SafeLogging option disabled. For more information, see
11476 https://trac.torproject.org/projects/tor/ticket/23490
11478 o Minor features (code style, backport from 0.3.1.7):
11479 - Add "Falls through" comments to our codebase, in order to silence
11480 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
11481 Stieger. Closes ticket 22446.
11484 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
11487 o Minor bugfixes (compilation, backport from 0.3.1.7):
11488 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
11489 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
11491 o Minor bugfixes (controller, backport from 0.3.1.7):
11492 - Do not crash when receiving a HSPOST command with an empty body.
11493 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
11494 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
11495 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
11497 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
11498 - When setting the maximum number of connections allowed by the OS,
11499 always allow some extra file descriptors for other files. Fixes
11500 bug 22797; bugfix on 0.2.0.10-alpha.
11502 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
11503 - Remove a forgotten debugging message when an introduction point
11504 successfully establishes a hidden service prop224 circuit with
11506 - Change three other log_warn() for an introduction point to
11507 protocol warnings, because they can be failure from the network
11508 and are not relevant to the operator. Fixes bug 23078; bugfix on
11509 0.3.0.1-alpha and 0.3.0.2-alpha.
11512 Changes in version 0.3.1.7 - 2017-09-18
11513 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
11515 With the 0.3.1 series, Tor now serves and downloads directory
11516 information in more compact formats, to save on bandwidth overhead. It
11517 also contains a new padding system to resist netflow-based traffic
11518 analysis, and experimental support for building parts of Tor in Rust
11519 (though no parts of Tor are in Rust yet). There are also numerous
11520 small features, bugfixes on earlier release series, and groundwork for
11521 the hidden services revamp of 0.3.2.
11523 This release also includes a fix for TROVE-2017-008, a security bug
11524 that affects hidden services running with the SafeLogging option
11525 disabled. For more information, see
11526 https://trac.torproject.org/projects/tor/ticket/23490
11528 Per our stable release policy, we plan to support each stable release
11529 series for at least the next nine months, or for three months after
11530 the first stable release of the next series: whichever is longer. If
11531 you need a release with long-term support, we recommend that you stay
11532 with the 0.2.9 series.
11534 Below is a list of the changes since 0.3.1.6-rc. For a list of all
11535 changes since 0.3.0, see the ReleaseNotes file.
11537 o Major bugfixes (security, hidden services, loggging):
11538 - Fix a bug where we could log uninitialized stack when a certain
11539 hidden service error occurred while SafeLogging was disabled.
11540 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
11541 TROVE-2017-008 and CVE-2017-0380.
11543 o Minor features (defensive programming):
11544 - Create a pair of consensus parameters, nf_pad_tor2web and
11545 nf_pad_single_onion, to disable netflow padding in the consensus
11546 for non-anonymous connections in case the overhead is high. Closes
11549 o Minor features (diagnostic):
11550 - Add a stack trace to the bug warnings that can be logged when
11551 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
11552 attempt for bug 23105.
11554 o Minor features (geoip):
11555 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
11558 o Minor bugfixes (compilation):
11559 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
11560 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
11562 o Minor bugfixes (controller):
11563 - Do not crash when receiving a HSPOST command with an empty body.
11564 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
11565 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
11566 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
11568 o Minor bugfixes (relay):
11569 - Inform the geoip and rephist modules about all requests, even on
11570 relays that are only fetching microdescriptors. Fixes a bug
11571 related to 21585; bugfix on 0.3.0.1-alpha.
11573 o Minor bugfixes (unit tests):
11574 - Fix a channelpadding unit test failure on slow systems by using
11575 mocked time instead of actual time. Fixes bug 23077; bugfix
11579 Changes in version 0.3.1.6-rc - 2017-09-05
11580 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
11581 release series, including a bug that produced weird behavior on
11582 Windows directory caches.
11584 This is the first release candidate in the Tor 0.3.1 series. If we
11585 find no new bugs or regressions here, the first stable 0.3.1 release
11586 will be nearly identical to it.
11588 o Major bugfixes (windows, directory cache):
11589 - On Windows, do not try to delete cached consensus documents and
11590 diffs before they are unmapped from memory--Windows won't allow
11591 that. Instead, allow the consensus cache directory to grow larger,
11592 to hold files that might need to stay around longer. Fixes bug
11593 22752; bugfix on 0.3.1.1-alpha.
11595 o Minor features (directory authority):
11596 - Improve the message that authorities report to relays that present
11597 RSA/Ed25519 keypairs that conflict with previously pinned keys.
11598 Closes ticket 22348.
11600 o Minor features (geoip):
11601 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
11604 o Minor features (testing):
11605 - Add more tests for compression backend initialization. Closes
11608 o Minor bugfixes (directory cache):
11609 - Fix a memory leak when recovering space in the consensus cache.
11610 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
11612 o Minor bugfixes (hidden service):
11613 - Increase the number of circuits that a service is allowed to
11614 open over a specific period of time. The value was lower than it
11615 should be (8 vs 12) in the normal case of 3 introduction points.
11616 Fixes bug 22159; bugfix on 0.3.0.5-rc.
11617 - Fix a BUG warning during HSv3 descriptor decoding that could be
11618 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
11619 on 0.3.0.1-alpha. Bug found by "haxxpop".
11620 - Rate-limit the log messages if we exceed the maximum number of
11621 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
11623 o Minor bugfixes (logging, relay):
11624 - Remove a forgotten debugging message when an introduction point
11625 successfully establishes a hidden service prop224 circuit with
11627 - Change three other log_warn() for an introduction point to
11628 protocol warnings, because they can be failure from the network
11629 and are not relevant to the operator. Fixes bug 23078; bugfix on
11630 0.3.0.1-alpha and 0.3.0.2-alpha.
11632 o Minor bugfixes (relay):
11633 - When a relay is not running as a directory cache, it will no
11634 longer generate compressed consensuses and consensus diff
11635 information. Previously, this was a waste of disk and CPU. Fixes
11636 bug 23275; bugfix on 0.3.1.1-alpha.
11638 o Minor bugfixes (robustness, error handling):
11639 - Improve our handling of the cases where OpenSSL encounters a
11640 memory error while encoding keys and certificates. We haven't
11641 observed these errors in the wild, but if they do happen, we now
11642 detect and respond better. Fixes bug 19418; bugfix on all versions
11643 of Tor. Reported by Guido Vranken.
11645 o Minor bugfixes (stability):
11646 - Avoid crashing on a double-free when unable to load or process an
11647 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
11648 with the clang static analyzer.
11650 o Minor bugfixes (testing):
11651 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
11652 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
11653 - Port the hs_ntor handshake test to work correctly with recent
11654 versions of the pysha3 module. Fixes bug 23071; bugfix
11657 o Minor bugfixes (Windows service):
11658 - When running as a Windows service, set the ID of the main thread
11659 correctly. Failure to do so made us fail to send log messages to
11660 the controller in 0.2.1.16-rc, slowed down controller event
11661 delivery in 0.2.7.3-rc and later, and crash with an assertion
11662 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
11663 Patch and diagnosis from "Vort".
11666 Changes in version 0.3.0.10 - 2017-08-02
11667 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
11668 from the current Tor alpha series. OpenBSD users and TPROXY users
11669 should upgrade; others are probably okay sticking with 0.3.0.9.
11671 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
11672 - Tor's repository now includes a Travis Continuous Integration (CI)
11673 configuration file (.travis.yml). This is meant to help new
11674 developers and contributors who fork Tor to a Github repository be
11675 better able to test their changes, and understand what we expect
11676 to pass. To use this new build feature, you must fork Tor to your
11677 Github account, then go into the "Integrations" menu in the
11678 repository settings for your fork and enable Travis, then push
11679 your changes. Closes ticket 22636.
11681 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
11682 - Fix a typo that had prevented TPROXY-based transparent proxying
11683 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
11684 Patch from "d4fq0fQAgoJ".
11686 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
11687 - Avoid an assertion failure bug affecting our implementation of
11688 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
11689 handling of "0xbar" differs from what we had expected. Fixes bug
11690 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
11692 o Minor features (backport from 0.3.1.5-alpha):
11693 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
11696 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
11697 - Roll over monthly accounting at the configured hour and minute,
11698 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
11699 Found by Andrey Karpov with PVS-Studio.
11701 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
11702 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
11703 bugfix on 0.2.8.1-alpha.
11704 - Fix warnings when building with libscrypt and openssl scrypt
11705 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
11706 - When building with certain versions of the mingw C header files,
11707 avoid float-conversion warnings when calling the C functions
11708 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
11711 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
11712 - Backport a fix for an "unused variable" warning that appeared
11713 in some versions of mingw. Fixes bug 22838; bugfix on
11716 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
11717 - Avoid Coverity build warnings related to our BUG() macro. By
11718 default, Coverity treats BUG() as the Linux kernel does: an
11719 instant abort(). We need to override that so our BUG() macro
11720 doesn't prevent Coverity from analyzing functions that use it.
11721 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
11723 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
11724 - When rejecting a router descriptor for running an obsolete version
11725 of Tor without ntor support, warn about the obsolete tor version,
11726 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
11728 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
11729 - Avoid a sandbox failure when trying to re-bind to a socket and
11730 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
11732 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
11733 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
11734 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
11737 Changes in version 0.3.1.5-alpha - 2017-08-01
11738 Tor 0.3.1.5-alpha improves the performance of consensus diff
11739 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
11740 several other bugs. If no serious bugs are found in this version, the
11741 next version will be a release candidate.
11743 This release also marks the end of support for the Tor 0.2.4.x,
11744 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
11745 further bug or security fixes. Anyone still running or distributing
11746 one of those versions should upgrade.
11748 o Major features (build system, continuous integration):
11749 - Tor's repository now includes a Travis Continuous Integration (CI)
11750 configuration file (.travis.yml). This is meant to help new
11751 developers and contributors who fork Tor to a Github repository be
11752 better able to test their changes, and understand what we expect
11753 to pass. To use this new build feature, you must fork Tor to your
11754 Github account, then go into the "Integrations" menu in the
11755 repository settings for your fork and enable Travis, then push
11756 your changes. Closes ticket 22636.
11758 o Major bugfixes (openbsd, denial-of-service):
11759 - Avoid an assertion failure bug affecting our implementation of
11760 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
11761 handling of "0xbar" differs from what we had expected. Fixes bug
11762 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
11764 o Major bugfixes (relay, performance):
11765 - Perform circuit handshake operations at a higher priority than we
11766 use for consensus diff creation and compression. This should
11767 prevent circuits from starving when a relay or bridge receives a
11768 new consensus, especially on lower-powered machines. Fixes bug
11769 22883; bugfix on 0.3.1.1-alpha.
11771 o Minor features (bridge authority):
11772 - Add "fingerprint" lines to the networkstatus-bridges file produced
11773 by bridge authorities. Closes ticket 22207.
11775 o Minor features (directory cache, consensus diff):
11776 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
11777 operators with low-resource environments to adjust the number of
11778 consensuses they'll store and generate diffs from. Most cache
11779 operators should leave it unchanged. Helps to work around
11782 o Minor features (geoip):
11783 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
11786 o Minor features (relay, performance):
11787 - Always start relays with at least two worker threads, to prevent
11788 priority inversion on slow tasks. Part of the fix for bug 22883.
11789 - Allow background work to be queued with different priorities, so
11790 that a big pile of slow low-priority jobs will not starve out
11791 higher priority jobs. This lays the groundwork for a fix for
11794 o Minor bugfixes (build system, rust):
11795 - Fix a problem where Rust toolchains were not being found when
11796 building without --enable-cargo-online-mode, due to setting the
11797 $HOME environment variable instead of $CARGO_HOME. Fixes bug
11798 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
11800 o Minor bugfixes (compatibility, zstd):
11801 - Write zstd epilogues correctly when the epilogue requires
11802 reallocation of the output buffer, even with zstd 1.3.0.
11803 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
11804 22927; bugfix on 0.3.1.1-alpha.
11806 o Minor bugfixes (compilation warnings):
11807 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
11808 22915; bugfix on 0.2.8.1-alpha.
11809 - Fix warnings when building with libscrypt and openssl scrypt
11810 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
11811 - Compile correctly when both openssl 1.1.0 and libscrypt are
11812 detected. Previously this would cause an error. Fixes bug 22892;
11813 bugfix on 0.3.1.1-alpha.
11814 - When building with certain versions of the mingw C header files,
11815 avoid float-conversion warnings when calling the C functions
11816 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
11819 o Minor bugfixes (coverity build support):
11820 - Avoid Coverity build warnings related to our BUG() macro. By
11821 default, Coverity treats BUG() as the Linux kernel does: an
11822 instant abort(). We need to override that so our BUG() macro
11823 doesn't prevent Coverity from analyzing functions that use it.
11824 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
11826 o Minor bugfixes (directory authority):
11827 - When a directory authority rejects a descriptor or extrainfo with
11828 a given digest, mark that digest as undownloadable, so that we do
11829 not attempt to download it again over and over. We previously
11830 tried to avoid downloading such descriptors by other means, but we
11831 didn't notice if we accidentally downloaded one anyway. This
11832 behavior became problematic in 0.2.7.2-alpha, when authorities
11833 began pinning Ed25519 keys. Fixes bug 22349; bugfix
11836 o Minor bugfixes (error reporting, windows):
11837 - When formatting Windows error messages, use the English format to
11838 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
11841 o Minor bugfixes (file limits, osx):
11842 - When setting the maximum number of connections allowed by the OS,
11843 always allow some extra file descriptors for other files. Fixes
11844 bug 22797; bugfix on 0.2.0.10-alpha.
11846 o Minor bugfixes (linux seccomp2 sandbox):
11847 - Avoid a sandbox failure when trying to re-bind to a socket and
11848 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
11850 o Minor bugfixes (memory leaks):
11851 - Fix a small memory leak when validating a configuration that uses
11852 two or more AF_UNIX sockets for the same port type. Fixes bug
11853 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
11855 o Minor bugfixes (unit tests):
11856 - test_consdiff_base64cmp would fail on OS X because while OS X
11857 follows the standard of (less than zero/zero/greater than zero),
11858 it doesn't follow the convention of (-1/0/+1). Make the test
11859 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
11860 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
11861 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
11864 Changes in version 0.3.1.4-alpha - 2017-06-29
11865 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
11866 to use a guard that was in the same network family as a chosen exit
11867 relay. This is a security regression; all clients running earlier
11868 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
11871 This release also fixes several other bugs introduced in 0.3.0.x
11872 and 0.3.1.x, including others that can affect bandwidth usage
11875 o New dependencies:
11876 - To build with zstd and lzma support, Tor now requires the
11877 pkg-config tool at build time. (This requirement was new in
11878 0.3.1.1-alpha, but was not noted at the time. Noting it here to
11879 close ticket 22623.)
11881 o Major bugfixes (path selection, security):
11882 - When choosing which guard to use for a circuit, avoid the exit's
11883 family along with the exit itself. Previously, the new guard
11884 selection logic avoided the exit, but did not consider its family.
11885 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
11886 006 and CVE-2017-0377.
11888 o Major bugfixes (compression, zstd):
11889 - Correctly detect a full buffer when decompressing a large zstd-
11890 compressed input. Previously, we would sometimes treat a full
11891 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
11893 o Major bugfixes (directory protocol):
11894 - Ensure that we send "304 Not modified" as HTTP status code when a
11895 client is attempting to fetch a consensus or consensus diff, and
11896 the best one we can send them is one they already have. Fixes bug
11897 22702; bugfix on 0.3.1.1-alpha.
11899 o Major bugfixes (entry guards):
11900 - When starting with an old consensus, do not add new entry guards
11901 unless the consensus is "reasonably live" (under 1 day old). Fixes
11902 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
11904 o Minor features (bug mitigation, diagnostics, logging):
11905 - Avoid an assertion failure, and log a better error message, when
11906 unable to remove a file from the consensus cache on Windows.
11907 Attempts to mitigate and diagnose bug 22752.
11909 o Minor features (geoip):
11910 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
11913 o Minor bugfixes (compression):
11914 - When compressing or decompressing a buffer, check for a failure to
11915 create a compression object. Fixes bug 22626; bugfix
11917 - When decompressing a buffer, check for extra data after the end of
11918 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
11919 - When decompressing an object received over an anonymous directory
11920 connection, if we have already decompressed it using an acceptable
11921 compression method, do not reject it for looking like an
11922 unacceptable compression method. Fixes part of bug 22670; bugfix
11924 - When serving directory votes compressed with zlib, do not claim to
11925 have compressed them with zstd. Fixes bug 22669; bugfix
11927 - When spooling compressed data to an output buffer, don't try to
11928 spool more data when there is no more data to spool and we are not
11929 trying to flush the input. Previously, we would sometimes launch
11930 compression requests with nothing to do, which interferes with our
11931 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
11933 o Minor bugfixes (defensive programming):
11934 - Detect and break out of infinite loops in our compression code. We
11935 don't think that any such loops exist now, but it's best to be
11936 safe. Closes ticket 22672.
11937 - Fix a memset() off the end of an array when packing cells. This
11938 bug should be harmless in practice, since the corrupted bytes are
11939 still in the same structure, and are always padding bytes,
11940 ignored, or immediately overwritten, depending on compiler
11941 behavior. Nevertheless, because the memset()'s purpose is to make
11942 sure that any other cell-handling bugs can't expose bytes to the
11943 network, we need to fix it. Fixes bug 22737; bugfix on
11944 0.2.4.11-alpha. Fixes CID 1401591.
11946 o Minor bugfixes (linux seccomp2 sandbox):
11947 - Permit the fchmod system call, to avoid crashing on startup when
11948 starting with the seccomp2 sandbox and an unexpected set of
11949 permissions on the data directory or its contents. Fixes bug
11950 22516; bugfix on 0.2.5.4-alpha.
11951 - Fix a crash in the LZMA module, when the sandbox was enabled, and
11952 liblzma would allocate more than 16 MB of memory. We solve this by
11953 bumping the mprotect() limit in the sandbox module from 16 MB to
11954 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
11956 o Minor bugfixes (logging):
11957 - When decompressing, do not warn if we fail to decompress using a
11958 compression method that we merely guessed. Fixes part of bug
11959 22670; bugfix on 0.1.1.14-alpha.
11960 - When decompressing, treat mismatch between content-encoding and
11961 actual compression type as a protocol warning. Fixes part of bug
11962 22670; bugfix on 0.1.1.9-alpha.
11963 - Downgrade "assigned_to_cpuworker failed" message to info-level
11964 severity. In every case that can reach it, either a better warning
11965 has already been logged, or no warning is warranted. Fixes bug
11966 22356; bugfix on 0.2.6.3-alpha.
11967 - Demote a warn that was caused by libevent delays to info if
11968 netflow padding is less than 4.5 seconds late, or to notice
11969 if it is more (4.5 seconds is the amount of time that a netflow
11970 record might be emitted after, if we chose the maximum timeout).
11971 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
11973 o Minor bugfixes (process behavior):
11974 - When exiting because of an error, always exit with a nonzero exit
11975 status. Previously, we would fail to report an error in our exit
11976 status in cases related to __OwningControllerProcess failure,
11977 lockfile contention, and Ed25519 key initialization. Fixes bug
11978 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
11979 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
11983 - Add a manpage description for the key-pinning-journal file. Closes
11985 - Correctly note that bandwidth accounting values are stored in the
11986 state file, and the bw_accounting file is now obsolete. Closes
11988 - Document more of the files in the Tor data directory, including
11989 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
11990 approved-routers, sr-random, and diff-cache. Found while fixing
11994 Changes in version 0.3.0.9 - 2017-06-29
11995 Tor 0.3.0.9 fixes a path selection bug that would allow a client
11996 to use a guard that was in the same network family as a chosen exit
11997 relay. This is a security regression; all clients running earlier
11998 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
12001 This release also backports several other bugfixes from the 0.3.1.x
12004 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
12005 - When choosing which guard to use for a circuit, avoid the exit's
12006 family along with the exit itself. Previously, the new guard
12007 selection logic avoided the exit, but did not consider its family.
12008 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
12009 006 and CVE-2017-0377.
12011 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
12012 - Don't block bootstrapping when a primary bridge is offline and we
12013 can't get its descriptor. Fixes bug 22325; fixes one case of bug
12014 21969; bugfix on 0.3.0.3-alpha.
12016 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
12017 - When starting with an old consensus, do not add new entry guards
12018 unless the consensus is "reasonably live" (under 1 day old). Fixes
12019 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
12021 o Minor features (geoip):
12022 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
12025 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
12026 - Reject version numbers with non-numeric prefixes (such as +, -, or
12027 whitespace). Disallowing whitespace prevents differential version
12028 parsing between POSIX-based and Windows platforms. Fixes bug 21507
12029 and part of 21508; bugfix on 0.0.8pre1.
12031 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
12032 - Permit the fchmod system call, to avoid crashing on startup when
12033 starting with the seccomp2 sandbox and an unexpected set of
12034 permissions on the data directory or its contents. Fixes bug
12035 22516; bugfix on 0.2.5.4-alpha.
12037 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
12038 - Fix a memset() off the end of an array when packing cells. This
12039 bug should be harmless in practice, since the corrupted bytes are
12040 still in the same structure, and are always padding bytes,
12041 ignored, or immediately overwritten, depending on compiler
12042 behavior. Nevertheless, because the memset()'s purpose is to make
12043 sure that any other cell-handling bugs can't expose bytes to the
12044 network, we need to fix it. Fixes bug 22737; bugfix on
12045 0.2.4.11-alpha. Fixes CID 1401591.
12048 Changes in version 0.3.1.3-alpha - 2017-06-08
12049 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
12050 remotely crash a hidden service with an assertion failure. Anyone
12051 running a hidden service should upgrade to this version, or to some
12052 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
12054 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
12055 that sometimes made relays unreliable, as well as several other
12056 bugfixes described below.
12058 o Major bugfixes (hidden service, relay, security):
12059 - Fix a remotely triggerable assertion failure when a hidden service
12060 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
12061 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
12062 - Fix a remotely triggerable assertion failure caused by receiving a
12063 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
12064 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
12067 o Major bugfixes (relay, link handshake):
12068 - When performing the v3 link handshake on a TLS connection, report
12069 that we have the x509 certificate that we actually used on that
12070 connection, even if we have changed certificates since that
12071 connection was first opened. Previously, we would claim to have
12072 used our most recent x509 link certificate, which would sometimes
12073 make the link handshake fail. Fixes one case of bug 22460; bugfix
12076 o Major bugfixes (relays, key management):
12077 - Regenerate link and authentication certificates whenever the key
12078 that signs them changes; also, regenerate link certificates
12079 whenever the signed key changes. Previously, these processes were
12080 only weakly coupled, and we relays could (for minutes to hours)
12081 wind up with an inconsistent set of keys and certificates, which
12082 other relays would not accept. Fixes two cases of bug 22460;
12083 bugfix on 0.3.0.1-alpha.
12084 - When sending an Ed25519 signing->link certificate in a CERTS cell,
12085 send the certificate that matches the x509 certificate that we
12086 used on the TLS connection. Previously, there was a race condition
12087 if the TLS context rotated after we began the TLS handshake but
12088 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
12091 o Major bugfixes (torrc, crash):
12092 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
12093 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
12095 o Minor features (code style):
12096 - Add "Falls through" comments to our codebase, in order to silence
12097 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
12098 Stieger. Closes ticket 22446.
12100 o Minor features (diagnostic):
12101 - Add logging messages to try to diagnose a rare bug that seems to
12102 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
12103 think this is happening because of incorrect system clocks, but
12104 we'd like to know for certain. Diagnostic for bug 22466.
12106 o Minor bugfixes (correctness):
12107 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
12108 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
12110 o Minor bugfixes (directory protocol):
12111 - Check for libzstd >= 1.1, because older versions lack the
12112 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
12114 o Minor bugfixes (link handshake):
12115 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
12116 months, and regenerate it when it is within one month of expiring.
12117 Previously, we had generated this certificate at startup with a
12118 ten-year lifetime, but that could lead to weird behavior when Tor
12119 was started with a grossly inaccurate clock. Mitigates bug 22466;
12120 mitigation on 0.3.0.1-alpha.
12122 o Minor bugfixes (storage directories):
12123 - Always check for underflows in the cached storage directory usage.
12124 If the usage does underflow, re-calculate it. Also, avoid a
12125 separate underflow when the usage is not known. Fixes bug 22424;
12126 bugfix on 0.3.1.1-alpha.
12128 o Minor bugfixes (unit tests):
12129 - The unit tests now pass on systems where localhost is misconfigured
12130 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
12134 - Clarify the manpage for the (deprecated) torify script. Closes
12137 Changes in version 0.3.0.8 - 2017-06-08
12138 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
12139 remotely crash a hidden service with an assertion failure. Anyone
12140 running a hidden service should upgrade to this version, or to some
12141 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
12143 Tor 0.3.0.8 also includes fixes for several key management bugs
12144 that sometimes made relays unreliable, as well as several other
12145 bugfixes described below.
12147 o Major bugfixes (hidden service, relay, security, backport
12148 from 0.3.1.3-alpha):
12149 - Fix a remotely triggerable assertion failure when a hidden service
12150 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
12151 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
12152 - Fix a remotely triggerable assertion failure caused by receiving a
12153 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
12154 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
12157 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
12158 - When performing the v3 link handshake on a TLS connection, report
12159 that we have the x509 certificate that we actually used on that
12160 connection, even if we have changed certificates since that
12161 connection was first opened. Previously, we would claim to have
12162 used our most recent x509 link certificate, which would sometimes
12163 make the link handshake fail. Fixes one case of bug 22460; bugfix
12166 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
12167 - Regenerate link and authentication certificates whenever the key
12168 that signs them changes; also, regenerate link certificates
12169 whenever the signed key changes. Previously, these processes were
12170 only weakly coupled, and we relays could (for minutes to hours)
12171 wind up with an inconsistent set of keys and certificates, which
12172 other relays would not accept. Fixes two cases of bug 22460;
12173 bugfix on 0.3.0.1-alpha.
12174 - When sending an Ed25519 signing->link certificate in a CERTS cell,
12175 send the certificate that matches the x509 certificate that we
12176 used on the TLS connection. Previously, there was a race condition
12177 if the TLS context rotated after we began the TLS handshake but
12178 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
12181 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
12182 - Stop rejecting v3 hidden service descriptors because their size
12183 did not match an old padding rule. Fixes bug 22447; bugfix on
12186 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
12187 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
12188 December 2016 (of which ~126 were still functional) with a list of
12189 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
12190 2017. Resolves ticket 21564.
12192 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
12193 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
12194 bug 22252; bugfix on 0.2.9.3-alpha.
12196 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
12197 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
12198 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
12200 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
12201 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
12202 months, and regenerate it when it is within one month of expiring.
12203 Previously, we had generated this certificate at startup with a
12204 ten-year lifetime, but that could lead to weird behavior when Tor
12205 was started with a grossly inaccurate clock. Mitigates bug 22466;
12206 mitigation on 0.3.0.1-alpha.
12208 o Minor bugfixes (memory leak, directory authority, backport from
12210 - When directory authorities reject a router descriptor due to
12211 keypinning, free the router descriptor rather than leaking the
12212 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
12215 Changes in version 0.2.9.11 - 2017-06-08
12216 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
12217 remotely crash a hidden service with an assertion failure. Anyone
12218 running a hidden service should upgrade to this version, or to some
12219 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
12220 are not affected by TROVE-2017-004.)
12222 Tor 0.2.9.11 also backports fixes for several key management bugs
12223 that sometimes made relays unreliable, as well as several other
12224 bugfixes described below.
12226 o Major bugfixes (hidden service, relay, security, backport
12227 from 0.3.1.3-alpha):
12228 - Fix a remotely triggerable assertion failure caused by receiving a
12229 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
12230 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
12233 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
12234 - When performing the v3 link handshake on a TLS connection, report
12235 that we have the x509 certificate that we actually used on that
12236 connection, even if we have changed certificates since that
12237 connection was first opened. Previously, we would claim to have
12238 used our most recent x509 link certificate, which would sometimes
12239 make the link handshake fail. Fixes one case of bug 22460; bugfix
12242 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
12243 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
12244 December 2016 (of which ~126 were still functional) with a list of
12245 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
12246 2017. Resolves ticket 21564.
12248 o Minor features (future-proofing, backport from 0.3.0.7):
12249 - Tor no longer refuses to download microdescriptors or descriptors if
12250 they are listed as "published in the future". This change will
12251 eventually allow us to stop listing meaningful "published" dates
12252 in microdescriptor consensuses, and thereby allow us to reduce the
12253 resources required to download consensus diffs by over 50%.
12254 Implements part of ticket 21642; implements part of proposal 275.
12256 o Minor features (directory authorities, backport from 0.3.0.4-rc)
12257 - Directory authorities now reject relays running versions
12258 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
12259 suffer from bug 20499 and don't keep their consensus cache
12260 up-to-date. Resolves ticket 20509.
12262 o Minor features (geoip):
12263 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
12266 o Minor bugfixes (control port, backport from 0.3.0.6):
12267 - The GETINFO extra-info/digest/<digest> command was broken because
12268 of a wrong base16 decode return value check, introduced when
12269 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
12271 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
12272 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
12273 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
12275 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
12276 - The getpid() system call is now permitted under the Linux seccomp2
12277 sandbox, to avoid crashing with versions of OpenSSL (and other
12278 libraries) that attempt to learn the process's PID by using the
12279 syscall rather than the VDSO code. Fixes bug 21943; bugfix
12282 o Minor bugfixes (memory leak, directory authority, backport
12283 from 0.3.1.2-alpha):
12284 - When directory authorities reject a router descriptor due to
12285 keypinning, free the router descriptor rather than leaking the
12286 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
12288 Changes in version 0.2.8.14 - 2017-06-08
12289 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
12290 remotely crash a hidden service with an assertion failure. Anyone
12291 running a hidden service should upgrade to this version, or to some
12292 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
12293 are not affected by TROVE-2017-004.)
12295 o Major bugfixes (hidden service, relay, security):
12296 - Fix a remotely triggerable assertion failure caused by receiving a
12297 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
12298 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
12301 o Minor features (geoip):
12302 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
12305 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
12306 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
12307 December 2016 (of which ~126 were still functional) with a list of
12308 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
12309 2017. Resolves ticket 21564.
12311 o Minor bugfixes (correctness):
12312 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
12313 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
12315 Changes in version 0.2.7.8 - 2017-06-08
12316 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
12317 remotely crash a hidden service with an assertion failure. Anyone
12318 running a hidden service should upgrade to this version, or to some
12319 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
12320 are not affected by TROVE-2017-004.)
12322 o Major bugfixes (hidden service, relay, security):
12323 - Fix a remotely triggerable assertion failure caused by receiving a
12324 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
12325 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
12328 o Minor features (geoip):
12329 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
12332 o Minor bugfixes (correctness):
12333 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
12334 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
12337 Changes in version 0.2.6.12 - 2017-06-08
12338 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
12339 remotely crash a hidden service with an assertion failure. Anyone
12340 running a hidden service should upgrade to this version, or to some
12341 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
12342 are not affected by TROVE-2017-004.)
12344 o Major bugfixes (hidden service, relay, security):
12345 - Fix a remotely triggerable assertion failure caused by receiving a
12346 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
12347 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
12350 o Minor features (geoip):
12351 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
12354 o Minor bugfixes (correctness):
12355 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
12356 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
12358 Changes in version 0.2.5.14 - 2017-06-08
12359 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
12360 remotely crash a hidden service with an assertion failure. Anyone
12361 running a hidden service should upgrade to this version, or to some
12362 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
12363 are not affected by TROVE-2017-004.)
12365 o Major bugfixes (hidden service, relay, security):
12366 - Fix a remotely triggerable assertion failure caused by receiving a
12367 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
12368 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
12371 o Minor features (geoip):
12372 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
12375 o Minor bugfixes (correctness):
12376 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
12377 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
12379 Changes in version 0.2.4.29 - 2017-06-08
12380 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
12381 remotely crash a hidden service with an assertion failure. Anyone
12382 running a hidden service should upgrade to this version, or to some
12383 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
12384 are not affected by TROVE-2017-004.)
12386 o Major bugfixes (hidden service, relay, security):
12387 - Fix a remotely triggerable assertion failure caused by receiving a
12388 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
12389 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
12392 o Minor features (geoip):
12393 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
12396 o Minor bugfixes (correctness):
12397 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
12398 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
12401 Changes in version 0.3.1.2-alpha - 2017-05-26
12402 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
12403 fixes a few bugs found while testing 0.3.1.1-alpha, including a
12404 memory corruption bug that affected relay stability.
12406 o Major bugfixes (crash, relay):
12407 - Fix a memory-corruption bug in relays that set MyFamily.
12408 Previously, they would double-free MyFamily elements when making
12409 the next descriptor or when changing their configuration. Fixes
12410 bug 22368; bugfix on 0.3.1.1-alpha.
12412 o Minor bugfixes (logging):
12413 - Log a better message when a directory authority replies to an
12414 upload with an unexpected status code. Fixes bug 11121; bugfix
12417 o Minor bugfixes (memory leak, directory authority):
12418 - When directory authorities reject a router descriptor due to
12419 keypinning, free the router descriptor rather than leaking the
12420 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
12423 Changes in version 0.3.1.1-alpha - 2017-05-22
12424 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
12425 reduces the bandwidth usage for Tor's directory protocol, adds some
12426 basic padding to resist netflow-based traffic analysis and to serve as
12427 the basis of other padding in the future, and adds rust support to the
12430 It also contains numerous other small features and improvements to
12431 security, correctness, and performance.
12433 Below are the changes since 0.3.0.7.
12435 o Major features (directory protocol):
12436 - Tor relays and authorities can now serve clients an abbreviated
12437 version of the consensus document, containing only the changes
12438 since an older consensus document that the client holds. Clients
12439 now request these documents when available. When both client and
12440 server use this new protocol, they will use far less bandwidth (up
12441 to 94% less) to keep the client's consensus up-to-date. Implements
12442 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
12443 - Tor can now compress directory traffic with lzma or with zstd
12444 compression algorithms, which can deliver better bandwidth
12445 performance. Because lzma is computationally expensive, it's only
12446 used for documents that can be compressed once and served many
12447 times. Support for these algorithms requires that tor is built
12448 with the libzstd and/or liblzma libraries available. Implements
12449 proposal 278; closes ticket 21662.
12450 - Relays now perform the more expensive compression operations, and
12451 consensus diff generation, in worker threads. This separation
12452 avoids delaying the main thread when a new consensus arrives.
12454 o Major features (experimental):
12455 - Tor can now build modules written in Rust. To turn this on, pass
12456 the "--enable-rust" flag to the configure script. It's not time to
12457 get excited yet: currently, there is no actual Rust functionality
12458 beyond some simple glue code, and a notice at startup to tell you
12459 that Rust is running. Still, we hope that programmers and
12460 packagers will try building Tor with Rust support, so that we can
12461 find issues and solve portability problems. Closes ticket 22106.
12463 o Major features (traffic analysis resistance):
12464 - Connections between clients and relays now send a padding cell in
12465 each direction every 1.5 to 9.5 seconds (tunable via consensus
12466 parameters). This padding will not resist specialized
12467 eavesdroppers, but it should be enough to make many ISPs' routine
12468 network flow logging less useful in traffic analysis against
12471 Padding is negotiated using Tor's link protocol, so both relays
12472 and clients must upgrade for this to take effect. Clients may
12473 still send padding despite the relay's version by setting
12474 ConnectionPadding 1 in torrc, and may disable padding by setting
12475 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
12476 users with the torrc option ReducedConnectionPadding. Implements
12477 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
12478 - Relays will publish 24 hour totals of padding and non-padding cell
12479 counts to their extra-info descriptors, unless PaddingStatistics 0
12480 is set in torrc. These 24 hour totals are also rounded to
12481 multiples of 10000.
12483 o Major bugfixes (connection usage):
12484 - We use NETINFO cells to try to determine if both relays involved
12485 in a connection will agree on the canonical status of that
12486 connection. We prefer the connections where this is the case for
12487 extend cells, and try to close connections where relays disagree
12488 on their canonical status early. Also, we now prefer the oldest
12489 valid connection for extend cells. These two changes should reduce
12490 the number of long-term connections that are kept open between
12491 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
12492 - Relays now log hourly statistics (look for
12493 "channel_check_for_duplicates" lines) on the total number of
12494 connections to other relays. If the number of connections per
12495 relay is unexpectedly large, this log message is at notice level.
12496 Otherwise it is at info.
12498 o Major bugfixes (entry guards):
12499 - Don't block bootstrapping when a primary bridge is offline and we
12500 can't get its descriptor. Fixes bug 22325; fixes one case of bug
12501 21969; bugfix on 0.3.0.3-alpha.
12503 o Major bugfixes (linux TPROXY support):
12504 - Fix a typo that had prevented TPROXY-based transparent proxying
12505 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
12506 Patch from "d4fq0fQAgoJ".
12508 o Minor features (security, windows):
12509 - Enable a couple of pieces of Windows hardening: one
12510 (HeapEnableTerminationOnCorruption) that has been on-by-default
12511 since Windows 8, and unavailable before Windows 7; and one
12512 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
12513 affect us, but shouldn't do any harm. Closes ticket 21953.
12515 o Minor features (config options):
12516 - Allow "%include" directives in torrc configuration files. These
12517 directives import the settings from other files, or from all the
12518 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
12519 - Make SAVECONF return an error when overwriting a torrc that has
12520 includes. Using SAVECONF with the FORCE option will allow it to
12521 overwrite torrc even if includes are used. Related to ticket 1922.
12522 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
12523 will work without the FORCE option. Related to ticket 1922.
12525 o Minor features (controller):
12526 - Warn the first time that a controller requests data in the long-
12527 deprecated 'GETINFO network-status' format. Closes ticket 21703.
12529 o Minor features (defaults):
12530 - The default value for UseCreateFast is now 0: clients which
12531 haven't yet received a consensus document will now use a proper
12532 ntor handshake to talk to their directory servers whenever they
12533 can. Closes ticket 21407.
12534 - Onion key rotation and expiry intervals are now defined as a
12535 network consensus parameter, per proposal 274. The default
12536 lifetime of an onion key is increased from 7 to 28 days. Old onion
12537 keys will expire after 7 days by default. This change will make
12538 consensus diffs much smaller, and save significant bandwidth.
12539 Closes ticket 21641.
12541 o Minor features (fallback directory list):
12542 - Update the fallback directory mirror whitelist and blacklist based
12543 on operator emails. Closes task 21121.
12544 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
12545 December 2016 (of which ~126 were still functional) with a list of
12546 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
12547 2017. Resolves ticket 21564.
12549 o Minor features (hidden services, logging):
12550 - Log a message when a hidden service descriptor has fewer
12551 introduction points than specified in
12552 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
12553 - Log a message when a hidden service reaches its introduction point
12554 circuit limit, and when that limit is reset. Follow up to ticket
12555 21594; closes ticket 21622.
12556 - Warn user if multiple entries in EntryNodes and at least one
12557 HiddenService are used together. Pinning EntryNodes along with a
12558 hidden service can be possibly harmful; for instance see ticket
12559 14917 or 21155. Closes ticket 21155.
12561 o Minor features (linux seccomp2 sandbox):
12562 - We now have a document storage backend compatible with the Linux
12563 seccomp2 sandbox. This backend is used for consensus documents and
12564 diffs between them; in the long term, we'd like to use it for
12565 unparseable directory material too. Closes ticket 21645
12566 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
12567 from 1MB to 16MB. This was necessary with the glibc allocator in
12568 order to allow worker threads to allocate more memory -- which in
12569 turn is necessary because of our new use of worker threads for
12570 compression. Closes ticket 22096.
12572 o Minor features (logging):
12573 - Log files are no longer created world-readable by default.
12574 (Previously, most distributors would store the logs in a non-
12575 world-readable location to prevent inappropriate access. This
12576 change is an extra precaution.) Closes ticket 21729; patch
12579 o Minor features (performance):
12580 - Our Keccak (SHA-3) implementation now accesses memory more
12581 efficiently, especially on little-endian systems. Closes
12583 - Add an O(1) implementation of channel_find_by_global_id(), to
12584 speed some controller functions.
12586 o Minor features (relay, configuration):
12587 - The MyFamily option may now be repeated as many times as desired,
12588 for relays that want to configure large families. Closes ticket
12589 4998; patch by Daniel Pinto.
12591 o Minor features (safety):
12592 - Add an explicit check to extrainfo_parse_entry_from_string() for
12593 NULL inputs. We don't believe this can actually happen, but it may
12594 help silence a warning from the Clang analyzer. Closes
12597 o Minor features (testing):
12598 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
12599 When Tor is compiled with this option, we disable a number of
12600 redundant memory-safety failsafes that are intended to stop bugs
12601 from becoming security issues. This makes it easier to hunt for
12602 bugs that would be security issues without the failsafes turned
12603 on. Closes ticket 21439.
12604 - Add a general event-tracing instrumentation support to Tor. This
12605 subsystem will enable developers and researchers to add fine-
12606 grained instrumentation to their Tor instances, for use when
12607 examining Tor network performance issues. There are no trace
12608 events yet, and event-tracing is off by default unless enabled at
12609 compile time. Implements ticket 13802.
12610 - Improve our version parsing tests: add tests for typical version
12611 components, add tests for invalid versions, including numeric
12612 range and non-numeric prefixes. Unit tests 21278, 21450, and
12613 21507. Partially implements 21470.
12615 o Minor bugfixes (bandwidth accounting):
12616 - Roll over monthly accounting at the configured hour and minute,
12617 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
12618 Found by Andrey Karpov with PVS-Studio.
12620 o Minor bugfixes (code correctness):
12621 - Accurately identify client connections by their lack of peer
12622 authentication. This means that we bail out earlier if asked to
12623 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
12626 o Minor bugfixes (configuration):
12627 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
12628 bug 22252; bugfix on 0.2.9.3-alpha.
12630 o Minor bugfixes (connection lifespan):
12631 - Allow more control over how long TLS connections are kept open:
12632 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
12633 single option called CircuitsAvailableTimeout. Also, allow the
12634 consensus to control the default values for both this preference
12635 and the lifespan of relay-to-relay connections. Fixes bug 17592;
12636 bugfix on 0.2.5.5-alpha.
12637 - Increase the initial circuit build timeout testing frequency, to
12638 help ensure that ReducedConnectionPadding clients finish learning
12639 a timeout before their orconn would expire. The initial testing
12640 rate was set back in the days of TAP and before the Tor Browser
12641 updater, when we had to be much more careful about new clients
12642 making lots of circuits. With this change, a circuit build timeout
12643 is learned in about 15-20 minutes, instead of 100-120 minutes.
12645 o Minor bugfixes (controller):
12646 - GETINFO onions/current and onions/detached no longer respond with
12647 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
12648 - Trigger HS descriptor events on the control port when the client
12649 fails to pick a hidden service directory for a hidden service.
12650 This can happen if all the hidden service directories are in
12651 ExcludeNodes, or they have all been queried within the last 15
12652 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
12654 o Minor bugfixes (directory authority):
12655 - When rejecting a router descriptor for running an obsolete version
12656 of Tor without ntor support, warn about the obsolete tor version,
12657 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
12658 - Prevent the shared randomness subsystem from asserting when
12659 initialized by a bridge authority with an incomplete configuration
12660 file. Fixes bug 21586; bugfix on 0.2.9.8.
12662 o Minor bugfixes (exit-side DNS):
12663 - Fix an untriggerable assertion that checked the output of a
12664 libevent DNS error, so that the assertion actually behaves as
12665 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
12666 Karpov using PVS-Studio.
12668 o Minor bugfixes (fallback directories):
12669 - Make the usage example in updateFallbackDirs.py actually work, and
12670 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
12671 - Decrease the guard flag average required to be a fallback. This
12672 allows us to keep relays that have their guard flag removed when
12673 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
12674 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
12675 bugfix on 0.2.8.1-alpha.
12676 - Make sure fallback directory mirrors have the same address, port,
12677 and relay identity key for at least 30 days before they are
12678 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
12680 o Minor bugfixes (hidden services):
12681 - Stop printing a cryptic warning when a hidden service gets a
12682 request to connect to a virtual port that it hasn't configured.
12683 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
12684 - Simplify hidden service descriptor creation by using an existing
12685 flag to check if an introduction point is established. Fixes bug
12686 21599; bugfix on 0.2.7.2-alpha.
12688 o Minor bugfixes (memory leak):
12689 - Fix a small memory leak at exit from the backtrace handler code.
12690 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
12692 o Minor bugfixes (protocol, logging):
12693 - Downgrade a log statement about unexpected relay cells from "bug"
12694 to "protocol warning", because there is at least one use case
12695 where it can be triggered by a buggy tor implementation. Fixes bug
12696 21293; bugfix on 0.1.1.14-alpha.
12698 o Minor bugfixes (testing):
12699 - Use unbuffered I/O for utility functions around the
12700 process_handle_t type. This fixes unit test failures reported on
12701 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
12702 - Make display of captured unit test log messages consistent. Fixes
12703 bug 21510; bugfix on 0.2.9.3-alpha.
12704 - Make test-network.sh always call chutney's test-network.sh.
12705 Previously, this only worked on systems which had bash installed,
12706 due to some bash-specific code in the script. Fixes bug 19699;
12707 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
12709 o Minor bugfixes (voting consistency):
12710 - Reject version numbers with non-numeric prefixes (such as +, -, or
12711 whitespace). Disallowing whitespace prevents differential version
12712 parsing between POSIX-based and Windows platforms. Fixes bug 21507
12713 and part of 21508; bugfix on 0.0.8pre1.
12715 o Minor bugfixes (windows, relay):
12716 - Resolve "Failure from drain_fd: No error" warnings on Windows
12717 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
12719 o Code simplification and refactoring:
12720 - Break up the 630-line function connection_dir_client_reached_eof()
12721 into a dozen smaller functions. This change should help
12722 maintainability and readability of the client directory code.
12723 - Isolate our use of the openssl headers so that they are only
12724 included from our crypto wrapper modules, and from tests that
12725 examine those modules' internals. Closes ticket 21841.
12726 - Simplify our API to launch directory requests, making it more
12727 extensible and less error-prone. Now it's easier to add extra
12728 headers to directory requests. Closes ticket 21646.
12729 - Our base64 decoding functions no longer overestimate the output
12730 space that they need when parsing unpadded inputs. Closes
12732 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
12733 Resolves ticket 22213.
12734 - The logic that directory caches use to spool request to clients,
12735 serving them one part at a time so as not to allocate too much
12736 memory, has been refactored for consistency. Previously there was
12737 a separate spooling implementation per type of spoolable data. Now
12738 there is one common spooling implementation, with extensible data
12739 types. Closes ticket 21651.
12740 - Tor's compression module now supports multiple backends. Part of
12741 the implementation for proposal 278; closes ticket 21663.
12744 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
12745 Closes ticket 21873.
12746 - Correct documentation about the default DataDirectory value.
12747 Closes ticket 21151.
12748 - Document the default behavior of NumEntryGuards and
12749 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
12751 - Document key=value pluggable transport arguments for Bridge lines
12752 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
12753 - Note that bandwidth-limiting options don't affect TCP headers or
12754 DNS. Closes ticket 17170.
12756 o Removed features (configuration options, all in ticket 22060):
12757 - These configuration options are now marked Obsolete, and no longer
12758 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
12759 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
12760 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
12761 in 0.2.9.2-alpha and have now been removed. The previous default
12762 behavior is now always chosen; the previous (less secure) non-
12763 default behavior is now unavailable.
12764 - CloseHSClientCircuitsImmediatelyOnTimeout and
12765 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
12766 0.2.9.2-alpha and now have been removed. HS circuits never close
12767 on circuit build timeout; they have a longer timeout period.
12768 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
12769 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
12770 (and others) to configure listen-only and advertise-only addresses.
12772 o Removed features (tools):
12773 - We've removed the tor-checkkey tool from src/tools. Long ago, we
12774 used it to help people detect RSA keys that were generated by
12775 versions of Debian affected by CVE-2008-0166. But those keys have
12776 been out of circulation for ages, and this tool is no longer
12777 required. Closes ticket 21842.
12780 Changes in version 0.3.0.7 - 2017-05-15
12781 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
12782 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
12783 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
12784 clients are not affected.
12786 o Major bugfixes (hidden service directory, security):
12787 - Fix an assertion failure in the hidden service directory code, which
12788 could be used by an attacker to remotely cause a Tor relay process to
12789 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
12790 should upgrade. This security issue is tracked as TROVE-2017-002.
12791 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
12794 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
12797 o Minor features (future-proofing):
12798 - Tor no longer refuses to download microdescriptors or descriptors
12799 if they are listed as "published in the future". This change will
12800 eventually allow us to stop listing meaningful "published" dates
12801 in microdescriptor consensuses, and thereby allow us to reduce the
12802 resources required to download consensus diffs by over 50%.
12803 Implements part of ticket 21642; implements part of proposal 275.
12805 o Minor bugfixes (Linux seccomp2 sandbox):
12806 - The getpid() system call is now permitted under the Linux seccomp2
12807 sandbox, to avoid crashing with versions of OpenSSL (and other
12808 libraries) that attempt to learn the process's PID by using the
12809 syscall rather than the VDSO code. Fixes bug 21943; bugfix
12813 Changes in version 0.3.0.6 - 2017-04-26
12814 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
12816 With the 0.3.0 series, clients and relays now use Ed25519 keys to
12817 authenticate their link connections to relays, rather than the old
12818 RSA1024 keys that they used before. (Circuit crypto has been
12819 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
12820 the guard selection and replacement algorithm to behave more robustly
12821 in the presence of unreliable networks, and to resist guard-
12824 This series also includes numerous other small features and bugfixes,
12825 along with more groundwork for the upcoming hidden-services revamp.
12827 Per our stable release policy, we plan to support the Tor 0.3.0
12828 release series for at least the next nine months, or for three months
12829 after the first stable release of the 0.3.1 series: whichever is
12830 longer. If you need a release with long-term support, we recommend
12831 that you stay with the 0.2.9 series.
12833 Below are the changes since 0.3.0.5-rc. For a list of all changes
12834 since 0.2.9, see the ReleaseNotes file.
12836 o Minor features (geoip):
12837 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
12840 o Minor bugfixes (control port):
12841 - The GETINFO extra-info/digest/<digest> command was broken because
12842 of a wrong base16 decode return value check, introduced when
12843 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
12845 o Minor bugfixes (crash prevention):
12846 - Fix a (currently untriggerable, but potentially dangerous) crash
12847 bug when base32-encoding inputs whose sizes are not a multiple of
12848 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
12851 Changes in version 0.3.0.5-rc - 2017-04-05
12852 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
12853 0.3.0 release series.
12855 This is the second release candidate in the Tor 0.3.0 series, and has
12856 much fewer changes than the first. If we find no new bugs or
12857 regressions here, the first stable 0.3.0 release will be nearly
12860 o Major bugfixes (crash, directory connections):
12861 - Fix a rare crash when sending a begin cell on a circuit whose
12862 linked directory connection had already been closed. Fixes bug
12863 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
12865 o Major bugfixes (guard selection):
12866 - Fix a guard selection bug where Tor would refuse to bootstrap in
12867 some cases if the user swapped a bridge for another bridge in
12868 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
12869 Reported by "torvlnt33r".
12871 o Minor features (geoip):
12872 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
12875 o Minor bugfix (compilation):
12876 - Fix a warning when compiling hs_service.c. Previously, it had no
12877 exported symbols when compiled for libor.a, resulting in a
12878 compilation warning from clang. Fixes bug 21825; bugfix
12881 o Minor bugfixes (hidden services):
12882 - Make hidden services check for failed intro point connections,
12883 even when they have exceeded their intro point creation limit.
12884 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
12885 - Make hidden services with 8 to 10 introduction points check for
12886 failed circuits immediately after startup. Previously, they would
12887 wait for 5 minutes before performing their first checks. Fixes bug
12888 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
12890 o Minor bugfixes (memory leaks):
12891 - Fix a memory leak when using GETCONF on a port option. Fixes bug
12892 21682; bugfix on 0.3.0.3-alpha.
12894 o Minor bugfixes (relay):
12895 - Avoid a double-marked-circuit warning that could happen when we
12896 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
12899 o Minor bugfixes (tests):
12900 - Run the entry_guard_parse_from_state_full() test with the time set
12901 to a specific date. (The guard state that this test was parsing
12902 contained guards that had expired since the test was first
12903 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
12906 - Update the description of the directory server options in the
12907 manual page, to clarify that a relay no longer needs to set
12908 DirPort in order to be a directory cache. Closes ticket 21720.
12912 Changes in version 0.2.8.13 - 2017-03-03
12913 Tor 0.2.8.13 backports a security fix from later Tor
12914 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
12915 this release, if for some reason they cannot upgrade to a later
12916 release series, and if they build Tor with the --enable-expensive-hardening
12919 Note that support for Tor 0.2.8.x is ending next year: we will not issue
12920 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
12921 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
12923 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12924 - Fix an integer underflow bug when comparing malformed Tor
12925 versions. This bug could crash Tor when built with
12926 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12927 0.2.9.8, which were built with -ftrapv by default. In other cases
12928 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12929 on 0.0.8pre1. Found by OSS-Fuzz.
12931 o Minor features (geoip):
12932 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12936 Changes in version 0.2.7.7 - 2017-03-03
12937 Tor 0.2.7.7 backports a number of security fixes from later Tor
12938 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
12939 this release, if for some reason they cannot upgrade to a later
12942 Note that support for Tor 0.2.7.x is ending this year: we will not issue
12943 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
12944 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
12946 o Directory authority changes (backport from 0.2.8.5-rc):
12947 - Urras is no longer a directory authority. Closes ticket 19271.
12949 o Directory authority changes (backport from 0.2.9.2-alpha):
12950 - The "Tonga" bridge authority has been retired; the new bridge
12951 authority is "Bifroest". Closes tickets 19728 and 19690.
12953 o Directory authority key updates (backport from 0.2.8.1-alpha):
12954 - Update the V3 identity key for the dannenberg directory authority:
12955 it was changed on 18 November 2015. Closes task 17906. Patch
12958 o Major bugfixes (parsing, security, backport from 0.2.9.8):
12959 - Fix a bug in parsing that could cause clients to read a single
12960 byte past the end of an allocated region. This bug could be used
12961 to cause hardened clients (built with --enable-expensive-hardening)
12962 to crash if they tried to visit a hostile hidden service. Non-
12963 hardened clients are only affected depending on the details of
12964 their platform's memory allocator. Fixes bug 21018; bugfix on
12965 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12966 2016-12-002 and as CVE-2016-1254.
12968 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
12969 - Stop a crash that could occur when a client running with DNSPort
12970 received a query with multiple address types, and the first
12971 address type was not supported. Found and fixed by Scott Dial.
12972 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
12973 - Prevent a class of security bugs caused by treating the contents
12974 of a buffer chunk as if they were a NUL-terminated string. At
12975 least one such bug seems to be present in all currently used
12976 versions of Tor, and would allow an attacker to remotely crash
12977 most Tor instances, especially those compiled with extra compiler
12978 hardening. With this defense in place, such bugs can't crash Tor,
12979 though we should still fix them as they occur. Closes ticket
12980 20384 (TROVE-2016-10-001).
12982 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
12983 - Avoid a difficult-to-trigger heap corruption attack when extending
12984 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12985 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12986 Reported by Guido Vranken.
12988 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
12989 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12990 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12992 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
12993 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12994 pointer to the previous (uninitialized) key value. The impact here
12995 should be limited to a difficult-to-trigger crash, if OpenSSL is
12996 running an engine that makes key generation failures possible, or
12997 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12998 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
13001 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
13002 - Fix an integer underflow bug when comparing malformed Tor
13003 versions. This bug could crash Tor when built with
13004 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
13005 0.2.9.8, which were built with -ftrapv by default. In other cases
13006 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
13007 on 0.0.8pre1. Found by OSS-Fuzz.
13009 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
13010 - Make memwipe() do nothing when passed a NULL pointer or buffer of
13011 zero size. Check size argument to memwipe() for underflow. Fixes
13012 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
13015 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
13016 - Make Tor survive errors involving connections without a
13017 corresponding event object. Previously we'd fail with an
13018 assertion; now we produce a log message. Related to bug 16248.
13020 o Minor features (geoip):
13021 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
13025 Changes in version 0.2.6.11 - 2017-03-03
13026 Tor 0.2.6.11 backports a number of security fixes from later Tor
13027 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
13028 this release, if for some reason they cannot upgrade to a later
13031 Note that support for Tor 0.2.6.x is ending this year: we will not issue
13032 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
13033 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
13035 o Directory authority changes (backport from 0.2.8.5-rc):
13036 - Urras is no longer a directory authority. Closes ticket 19271.
13038 o Directory authority changes (backport from 0.2.9.2-alpha):
13039 - The "Tonga" bridge authority has been retired; the new bridge
13040 authority is "Bifroest". Closes tickets 19728 and 19690.
13042 o Directory authority key updates (backport from 0.2.8.1-alpha):
13043 - Update the V3 identity key for the dannenberg directory authority:
13044 it was changed on 18 November 2015. Closes task 17906. Patch
13047 o Major features (security fixes, backport from 0.2.9.4-alpha):
13048 - Prevent a class of security bugs caused by treating the contents
13049 of a buffer chunk as if they were a NUL-terminated string. At
13050 least one such bug seems to be present in all currently used
13051 versions of Tor, and would allow an attacker to remotely crash
13052 most Tor instances, especially those compiled with extra compiler
13053 hardening. With this defense in place, such bugs can't crash Tor,
13054 though we should still fix them as they occur. Closes ticket
13055 20384 (TROVE-2016-10-001).
13057 o Major bugfixes (parsing, security, backport from 0.2.9.8):
13058 - Fix a bug in parsing that could cause clients to read a single
13059 byte past the end of an allocated region. This bug could be used
13060 to cause hardened clients (built with --enable-expensive-hardening)
13061 to crash if they tried to visit a hostile hidden service. Non-
13062 hardened clients are only affected depending on the details of
13063 their platform's memory allocator. Fixes bug 21018; bugfix on
13064 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
13065 2016-12-002 and as CVE-2016-1254.
13067 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
13068 - Stop a crash that could occur when a client running with DNSPort
13069 received a query with multiple address types, and the first
13070 address type was not supported. Found and fixed by Scott Dial.
13071 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
13073 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
13074 - Fix an error that could cause us to read 4 bytes before the
13075 beginning of an openssl string. This bug could be used to cause
13076 Tor to crash on systems with unusual malloc implementations, or
13077 systems with unusual hardening installed. Fixes bug 17404; bugfix
13080 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
13081 - Avoid a difficult-to-trigger heap corruption attack when extending
13082 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
13083 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
13084 Reported by Guido Vranken.
13086 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
13087 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
13088 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
13090 o Major bugfixes (guard selection, backport from 0.2.7.6):
13091 - Actually look at the Guard flag when selecting a new directory
13092 guard. When we implemented the directory guard design, we
13093 accidentally started treating all relays as if they have the Guard
13094 flag during guard selection, leading to weaker anonymity and worse
13095 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
13098 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
13099 - If OpenSSL fails to generate an RSA key, do not retain a dangling
13100 pointer to the previous (uninitialized) key value. The impact here
13101 should be limited to a difficult-to-trigger crash, if OpenSSL is
13102 running an engine that makes key generation failures possible, or
13103 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
13104 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
13107 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
13108 - Fix an integer underflow bug when comparing malformed Tor
13109 versions. This bug could crash Tor when built with
13110 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
13111 0.2.9.8, which were built with -ftrapv by default. In other cases
13112 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
13113 on 0.0.8pre1. Found by OSS-Fuzz.
13115 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
13116 - Make memwipe() do nothing when passed a NULL pointer or buffer of
13117 zero size. Check size argument to memwipe() for underflow. Fixes
13118 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
13121 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
13122 - Make Tor survive errors involving connections without a
13123 corresponding event object. Previously we'd fail with an
13124 assertion; now we produce a log message. Related to bug 16248.
13126 o Minor features (geoip):
13127 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
13130 o Minor bugfixes (compilation, backport from 0.2.7.6):
13131 - Fix a compilation warning with Clang 3.6: Do not check the
13132 presence of an address which can never be NULL. Fixes bug 17781.
13135 Changes in version 0.2.5.13 - 2017-03-03
13136 Tor 0.2.5.13 backports a number of security fixes from later Tor
13137 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
13138 this release, if for some reason they cannot upgrade to a later
13141 Note that support for Tor 0.2.5.x is ending next year: we will not issue
13142 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
13143 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
13145 o Directory authority changes (backport from 0.2.8.5-rc):
13146 - Urras is no longer a directory authority. Closes ticket 19271.
13148 o Directory authority changes (backport from 0.2.9.2-alpha):
13149 - The "Tonga" bridge authority has been retired; the new bridge
13150 authority is "Bifroest". Closes tickets 19728 and 19690.
13152 o Directory authority key updates (backport from 0.2.8.1-alpha):
13153 - Update the V3 identity key for the dannenberg directory authority:
13154 it was changed on 18 November 2015. Closes task 17906. Patch
13157 o Major features (security fixes, backport from 0.2.9.4-alpha):
13158 - Prevent a class of security bugs caused by treating the contents
13159 of a buffer chunk as if they were a NUL-terminated string. At
13160 least one such bug seems to be present in all currently used
13161 versions of Tor, and would allow an attacker to remotely crash
13162 most Tor instances, especially those compiled with extra compiler
13163 hardening. With this defense in place, such bugs can't crash Tor,
13164 though we should still fix them as they occur. Closes ticket
13165 20384 (TROVE-2016-10-001).
13167 o Major bugfixes (parsing, security, backport from 0.2.9.8):
13168 - Fix a bug in parsing that could cause clients to read a single
13169 byte past the end of an allocated region. This bug could be used
13170 to cause hardened clients (built with --enable-expensive-hardening)
13171 to crash if they tried to visit a hostile hidden service. Non-
13172 hardened clients are only affected depending on the details of
13173 their platform's memory allocator. Fixes bug 21018; bugfix on
13174 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
13175 2016-12-002 and as CVE-2016-1254.
13177 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
13178 - Stop a crash that could occur when a client running with DNSPort
13179 received a query with multiple address types, and the first
13180 address type was not supported. Found and fixed by Scott Dial.
13181 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
13183 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
13184 - Fix an error that could cause us to read 4 bytes before the
13185 beginning of an openssl string. This bug could be used to cause
13186 Tor to crash on systems with unusual malloc implementations, or
13187 systems with unusual hardening installed. Fixes bug 17404; bugfix
13190 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
13191 - Avoid a difficult-to-trigger heap corruption attack when extending
13192 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
13193 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
13194 Reported by Guido Vranken.
13196 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
13197 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
13198 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
13200 o Major bugfixes (guard selection, backport from 0.2.7.6):
13201 - Actually look at the Guard flag when selecting a new directory
13202 guard. When we implemented the directory guard design, we
13203 accidentally started treating all relays as if they have the Guard
13204 flag during guard selection, leading to weaker anonymity and worse
13205 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
13208 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
13209 - If OpenSSL fails to generate an RSA key, do not retain a dangling
13210 pointer to the previous (uninitialized) key value. The impact here
13211 should be limited to a difficult-to-trigger crash, if OpenSSL is
13212 running an engine that makes key generation failures possible, or
13213 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
13214 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
13217 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
13218 - Fix an integer underflow bug when comparing malformed Tor
13219 versions. This bug could crash Tor when built with
13220 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
13221 0.2.9.8, which were built with -ftrapv by default. In other cases
13222 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
13223 on 0.0.8pre1. Found by OSS-Fuzz.
13225 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
13226 - Make memwipe() do nothing when passed a NULL pointer or buffer of
13227 zero size. Check size argument to memwipe() for underflow. Fixes
13228 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
13231 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
13232 - Make Tor survive errors involving connections without a
13233 corresponding event object. Previously we'd fail with an
13234 assertion; now we produce a log message. Related to bug 16248.
13236 o Minor features (geoip):
13237 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
13240 o Minor bugfixes (compilation, backport from 0.2.7.6):
13241 - Fix a compilation warning with Clang 3.6: Do not check the
13242 presence of an address which can never be NULL. Fixes bug 17781.
13244 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
13245 - Check for failures from crypto_early_init, and refuse to continue.
13246 A previous typo meant that we could keep going with an
13247 uninitialized crypto library, and would have OpenSSL initialize
13248 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
13249 when implementing ticket 4900. Patch by "teor".
13251 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
13252 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
13253 a client authorized hidden service. Fixes bug 15823; bugfix
13257 Changes in version 0.2.4.28 - 2017-03-03
13258 Tor 0.2.4.28 backports a number of security fixes from later Tor
13259 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
13260 this release, if for some reason they cannot upgrade to a later
13263 Note that support for Tor 0.2.4.x is ending soon: we will not issue
13264 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
13265 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
13267 o Directory authority changes (backport from 0.2.8.5-rc):
13268 - Urras is no longer a directory authority. Closes ticket 19271.
13270 o Directory authority changes (backport from 0.2.9.2-alpha):
13271 - The "Tonga" bridge authority has been retired; the new bridge
13272 authority is "Bifroest". Closes tickets 19728 and 19690.
13274 o Directory authority key updates (backport from 0.2.8.1-alpha):
13275 - Update the V3 identity key for the dannenberg directory authority:
13276 it was changed on 18 November 2015. Closes task 17906. Patch
13279 o Major features (security fixes, backport from 0.2.9.4-alpha):
13280 - Prevent a class of security bugs caused by treating the contents
13281 of a buffer chunk as if they were a NUL-terminated string. At
13282 least one such bug seems to be present in all currently used
13283 versions of Tor, and would allow an attacker to remotely crash
13284 most Tor instances, especially those compiled with extra compiler
13285 hardening. With this defense in place, such bugs can't crash Tor,
13286 though we should still fix them as they occur. Closes ticket
13287 20384 (TROVE-2016-10-001).
13289 o Major bugfixes (parsing, security, backport from 0.2.9.8):
13290 - Fix a bug in parsing that could cause clients to read a single
13291 byte past the end of an allocated region. This bug could be used
13292 to cause hardened clients (built with --enable-expensive-hardening)
13293 to crash if they tried to visit a hostile hidden service. Non-
13294 hardened clients are only affected depending on the details of
13295 their platform's memory allocator. Fixes bug 21018; bugfix on
13296 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
13297 2016-12-002 and as CVE-2016-1254.
13299 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
13300 - Fix an error that could cause us to read 4 bytes before the
13301 beginning of an openssl string. This bug could be used to cause
13302 Tor to crash on systems with unusual malloc implementations, or
13303 systems with unusual hardening installed. Fixes bug 17404; bugfix
13306 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
13307 - Avoid a difficult-to-trigger heap corruption attack when extending
13308 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
13309 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
13310 Reported by Guido Vranken.
13312 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
13313 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
13314 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
13316 o Major bugfixes (guard selection, backport from 0.2.7.6):
13317 - Actually look at the Guard flag when selecting a new directory
13318 guard. When we implemented the directory guard design, we
13319 accidentally started treating all relays as if they have the Guard
13320 flag during guard selection, leading to weaker anonymity and worse
13321 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
13324 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
13325 - If OpenSSL fails to generate an RSA key, do not retain a dangling
13326 pointer to the previous (uninitialized) key value. The impact here
13327 should be limited to a difficult-to-trigger crash, if OpenSSL is
13328 running an engine that makes key generation failures possible, or
13329 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
13330 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
13333 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
13334 - Fix an integer underflow bug when comparing malformed Tor
13335 versions. This bug could crash Tor when built with
13336 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
13337 0.2.9.8, which were built with -ftrapv by default. In other cases
13338 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
13339 on 0.0.8pre1. Found by OSS-Fuzz.
13341 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
13342 - Make memwipe() do nothing when passed a NULL pointer or buffer of
13343 zero size. Check size argument to memwipe() for underflow. Fixes
13344 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
13347 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
13348 - Make Tor survive errors involving connections without a
13349 corresponding event object. Previously we'd fail with an
13350 assertion; now we produce a log message. Related to bug 16248.
13352 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
13353 - Make it harder for attackers to overload hidden services with
13354 introductions, by blocking multiple introduction requests on the
13355 same circuit. Resolves ticket 15515.
13357 o Minor features (geoip):
13358 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
13361 o Minor bugfixes (compilation, backport from 0.2.7.6):
13362 - Fix a compilation warning with Clang 3.6: Do not check the
13363 presence of an address which can never be NULL. Fixes bug 17781.
13365 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
13366 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
13367 a client authorized hidden service. Fixes bug 15823; bugfix
13371 Changes in version 0.3.0.4-rc - 2017-03-01
13372 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
13373 0.3.0 release series, and introduces a few reliability features to
13374 keep them from coming back.
13376 This is the first release candidate in the Tor 0.3.0 series. If we
13377 find no new bugs or regressions here, the first stable 0.3.0 release
13378 will be nearly identical to it.
13380 o Major bugfixes (bridges):
13381 - When the same bridge is configured multiple times with the same
13382 identity, but at different address:port combinations, treat those
13383 bridge instances as separate guards. This fix restores the ability
13384 of clients to configure the same bridge with multiple pluggable
13385 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
13387 o Major bugfixes (hidden service directory v3):
13388 - Stop crashing on a failed v3 hidden service descriptor lookup
13389 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
13391 o Major bugfixes (parsing):
13392 - When parsing a malformed content-length field from an HTTP
13393 message, do not read off the end of the buffer. This bug was a
13394 potential remote denial-of-service attack against Tor clients and
13395 relays. A workaround was released in October 2016, to prevent this
13396 bug from crashing Tor. This is a fix for the underlying issue,
13397 which should no longer matter (if you applied the earlier patch).
13398 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
13399 using AFL (http://lcamtuf.coredump.cx/afl/).
13400 - Fix an integer underflow bug when comparing malformed Tor
13401 versions. This bug could crash Tor when built with
13402 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
13403 0.2.9.8, which were built with -ftrapv by default. In other cases
13404 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
13405 on 0.0.8pre1. Found by OSS-Fuzz.
13407 o Minor feature (protocol versioning):
13408 - Add new protocol version for proposal 224. HSIntro now advertises
13409 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
13411 o Minor features (directory authorities):
13412 - Directory authorities now reject descriptors that claim to be
13413 malformed versions of Tor. Helps prevent exploitation of
13415 - Reject version numbers with components that exceed INT32_MAX.
13416 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
13417 Fixes bug 21450; bugfix on 0.0.8pre1.
13418 - Directory authorities now reject relays running versions
13419 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
13420 suffer from bug 20499 and don't keep their consensus cache
13421 up-to-date. Resolves ticket 20509.
13423 o Minor features (geoip):
13424 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
13427 o Minor features (reliability, crash):
13428 - Try better to detect problems in buffers where they might grow (or
13429 think they have grown) over 2 GB in size. Diagnostic for
13432 o Minor features (testing):
13433 - During 'make test-network-all', if tor logs any warnings, ask
13434 chutney to output them. Requires a recent version of chutney with
13435 the 21572 patch. Implements 21570.
13437 o Minor bugfixes (certificate expiration time):
13438 - Avoid using link certificates that don't become valid till some
13439 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
13441 o Minor bugfixes (code correctness):
13442 - Repair a couple of (unreachable or harmless) cases of the risky
13443 comparison-by-subtraction pattern that caused bug 21278.
13444 - Remove a redundant check for the UseEntryGuards option from the
13445 options_transition_affects_guards() function. Fixes bug 21492;
13446 bugfix on 0.3.0.1-alpha.
13448 o Minor bugfixes (directory mirrors):
13449 - Allow relays to use directory mirrors without a DirPort: these
13450 relays need to be contacted over their ORPorts using a begindir
13451 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
13452 - Clarify the message logged when a remote relay is unexpectedly
13453 missing an ORPort or DirPort: users were confusing this with a
13454 local port. Fixes another case of bug 20711; bugfix
13457 o Minor bugfixes (guards):
13458 - Don't warn about a missing guard state on timeout-measurement
13459 circuits: they aren't supposed to be using guards. Fixes an
13460 instance of bug 21007; bugfix on 0.3.0.1-alpha.
13461 - Silence a BUG() warning when attempting to use a guard whose
13462 descriptor we don't know, and make this scenario less likely to
13463 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
13465 o Minor bugfixes (hidden service):
13466 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
13467 cells. Previously, we were using sizeof() on a pointer, instead of
13468 the real destination buffer. Fortunately, that value was only used
13469 to double-check that there was enough room--which was already
13470 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
13472 o Minor bugfixes (testing):
13473 - Fix Raspbian build issues related to missing socket errno in
13474 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
13476 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
13477 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
13478 - Use bash in src/test/test-network.sh. This ensures we reliably
13479 call chutney's newer tools/test-network.sh when available. Fixes
13480 bug 21562; bugfix on 0.2.9.1-alpha.
13483 - Small fixes to the fuzzing documentation. Closes ticket 21472.
13486 Changes in version 0.2.9.10 - 2017-03-01
13487 Tor 0.2.9.10 backports a security fix from later Tor release. It also
13488 includes fixes for some major issues affecting directory authorities,
13489 LibreSSL compatibility, and IPv6 correctness.
13491 The Tor 0.2.9.x release series is now marked as a long-term-support
13492 series. We intend to backport security fixes to 0.2.9.x until at
13493 least January of 2020.
13495 o Major bugfixes (directory authority, 0.3.0.3-alpha):
13496 - During voting, when marking a relay as a probable sybil, do not
13497 clear its BadExit flag: sybils can still be bad in other ways
13498 too. (We still clear the other flags.) Fixes bug 21108; bugfix
13501 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
13502 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
13503 any IPv6 addresses. Instead, only reject a port over IPv6 if the
13504 exit policy rejects that port on more than an IPv6 /16 of
13505 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
13506 which rejected a relay's own IPv6 address by default. Fixes bug
13507 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
13509 o Major bugfixes (parsing, also in 0.3.0.4-rc):
13510 - Fix an integer underflow bug when comparing malformed Tor
13511 versions. This bug could crash Tor when built with
13512 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
13513 0.2.9.8, which were built with -ftrapv by default. In other cases
13514 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
13515 on 0.0.8pre1. Found by OSS-Fuzz.
13517 o Minor features (directory authorities, also in 0.3.0.4-rc):
13518 - Directory authorities now reject descriptors that claim to be
13519 malformed versions of Tor. Helps prevent exploitation of
13521 - Reject version numbers with components that exceed INT32_MAX.
13522 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
13523 Fixes bug 21450; bugfix on 0.0.8pre1.
13525 o Minor features (geoip):
13526 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
13529 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
13530 - Autoconf now checks to determine if OpenSSL structures are opaque,
13531 instead of explicitly checking for OpenSSL version numbers. Part
13533 - Support building with recent LibreSSL code that uses opaque
13534 structures. Closes ticket 21359.
13536 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
13537 - Repair a couple of (unreachable or harmless) cases of the risky
13538 comparison-by-subtraction pattern that caused bug 21278.
13540 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
13541 - The tor-resolve command line tool now rejects hostnames over 255
13542 characters in length. Previously, it would silently truncate them,
13543 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
13544 Patch by "junglefowl".
13547 Changes in version 0.3.0.3-alpha - 2017-02-03
13548 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
13549 0.3.0.x development series, including some that could cause
13550 authorities to behave badly. There is also a fix for a longstanding
13551 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
13552 includes some smaller features and bugfixes.
13554 The Tor 0.3.0.x release series is now in patch-freeze: no additional
13555 features will be considered for inclusion in 0.3.0.x. We suspect that
13556 some bugs will probably remain, however, and we encourage people to
13559 o Major bugfixes (directory authority):
13560 - During voting, when marking a relay as a probable sybil, do not
13561 clear its BadExit flag: sybils can still be bad in other ways
13562 too. (We still clear the other flags.) Fixes bug 21108; bugfix
13564 - When deciding whether we have just found a router to be reachable,
13565 do not penalize it for not having performed an Ed25519 link
13566 handshake if it does not claim to support an Ed25519 handshake.
13567 Previously, we would treat such relays as non-running. Fixes bug
13568 21107; bugfix on 0.3.0.1-alpha.
13570 o Major bugfixes (entry guards):
13571 - Stop trying to build circuits through entry guards for which we
13572 have no descriptor. Also, stop crashing in the case that we *do*
13573 accidentally try to build a circuit in such a state. Fixes bug
13574 21242; bugfix on 0.3.0.1-alpha.
13576 o Major bugfixes (IPv6 Exits):
13577 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
13578 any IPv6 addresses. Instead, only reject a port over IPv6 if the
13579 exit policy rejects that port on more than an IPv6 /16 of
13580 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
13581 which rejected a relay's own IPv6 address by default. Fixes bug
13582 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
13584 o Minor feature (client):
13585 - Enable IPv6 traffic on the SocksPort by default. To disable this,
13586 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
13588 o Minor feature (fallback scripts):
13589 - Add a check_existing mode to updateFallbackDirs.py, which checks
13590 if fallbacks in the hard-coded list are working. Closes ticket
13591 20174. Patch by haxxpop.
13593 o Minor features (ciphersuite selection):
13594 - Clients now advertise a list of ciphersuites closer to the ones
13595 preferred by Firefox. Closes part of ticket 15426.
13596 - Allow relays to accept a wider range of ciphersuites, including
13597 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
13599 o Minor features (controller, configuration):
13600 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
13601 and so on, now comes with a __*Port variant that will not be saved
13602 to the torrc file by the controller's SAVECONF command. This
13603 change allows TorBrowser to set up a single-use domain socket for
13604 each time it launches Tor. Closes ticket 20956.
13605 - The GETCONF command can now query options that may only be
13606 meaningful in context-sensitive lists. This allows the controller
13607 to query the mixed SocksPort/__SocksPort style options introduced
13608 in feature 20956. Implements ticket 21300.
13610 o Minor features (portability, compilation):
13611 - Autoconf now checks to determine if OpenSSL structures are opaque,
13612 instead of explicitly checking for OpenSSL version numbers. Part
13614 - Support building with recent LibreSSL code that uses opaque
13615 structures. Closes ticket 21359.
13617 o Minor features (relay):
13618 - We now allow separation of exit and relay traffic to different
13619 source IP addresses, using the OutboundBindAddressExit and
13620 OutboundBindAddressOR options respectively. Closes ticket 17975.
13621 Written by Michael Sonntag.
13623 o Minor bugfix (logging):
13624 - Don't recommend the use of Tor2web in non-anonymous mode.
13625 Recommending Tor2web is a bad idea because the client loses all
13626 anonymity. Tor2web should only be used in specific cases by users
13627 who *know* and understand the issues. Fixes bug 21294; bugfix
13630 o Minor bugfixes (client):
13631 - Always recover from failures in extend_info_from_node(), in an
13632 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
13633 bugfix on 0.2.3.1-alpha.
13635 o Minor bugfixes (client, entry guards):
13636 - Fix a bug warning (with backtrace) when we fail a channel that
13637 circuits to fallback directories on it. Fixes bug 21128; bugfix
13639 - Fix a spurious bug warning (with backtrace) when removing an
13640 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
13641 - Fix a bug of the new guard algorithm where tor could stall for up
13642 to 10 minutes before retrying a guard after a long period of no
13643 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
13644 - Do not try to build circuits until we have descriptors for our
13645 primary entry guards. Related to fix for bug 21242.
13647 o Minor bugfixes (configure, autoconf):
13648 - Rename the configure option --enable-expensive-hardening to
13649 --enable-fragile-hardening. Expensive hardening makes the tor
13650 daemon abort when some kinds of issues are detected. Thus, it
13651 makes tor more at risk of remote crashes but safer against RCE or
13652 heartbleed bug category. We now try to explain this issue in a
13653 message from the configure script. Fixes bug 21290; bugfix
13656 o Minor bugfixes (controller):
13657 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
13658 20824; bugfix on 0.3.0.1-alpha.
13660 o Minor bugfixes (hidden service):
13661 - Clean up the code for expiring intro points with no associated
13662 circuits. It was causing, rarely, a service with some expiring
13663 introduction points to not open enough additional introduction
13664 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
13665 - Stop setting the torrc option HiddenServiceStatistics to "0" just
13666 because we're not a bridge or relay. Instead, we preserve whatever
13667 value the user set (or didn't set). Fixes bug 21150; bugfix
13669 - Resolve two possible underflows which could lead to creating and
13670 closing a lot of introduction point circuits in a non-stop loop.
13671 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
13673 o Minor bugfixes (portability):
13674 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
13675 It is supported by OpenBSD itself, and also by most OpenBSD
13676 variants (such as Bitrig). Fixes bug 20980; bugfix
13678 - When mapping a file of length greater than SIZE_MAX, do not
13679 silently truncate its contents. This issue could occur on 32 bit
13680 systems with large file support and files which are larger than 4
13681 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
13683 o Minor bugfixes (tor-resolve):
13684 - The tor-resolve command line tool now rejects hostnames over 255
13685 characters in length. Previously, it would silently truncate them,
13686 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
13687 Patch by "junglefowl".
13689 o Minor bugfixes (Windows services):
13690 - Be sure to initialize the monotonic time subsystem before using
13691 it, even when running as an NT service. Fixes bug 21356; bugfix
13695 Changes in version 0.3.0.2-alpha - 2017-01-23
13696 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
13697 cause relays and clients to crash, even if they were not built with
13698 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
13699 versions, and also affects 0.3.0.1-alpha: all relays running an affected
13700 version should upgrade.
13702 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
13703 time-to-live values, makes directory authorities enforce the 1-to-1
13704 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
13705 client-side onion service reachability bug, does better at selecting
13706 the set of fallback directories, and more.
13708 o Major bugfixes (security, also in 0.2.9.9):
13709 - Downgrade the "-ftrapv" option from "always on" to "only on when
13710 --enable-expensive-hardening is provided." This hardening option, like
13711 others, can turn survivable bugs into crashes--and having it on by
13712 default made a (relatively harmless) integer overflow bug into a
13713 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
13716 o Major features (security):
13717 - Change the algorithm used to decide DNS TTLs on client and server
13718 side, to better resist DNS-based correlation attacks like the
13719 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
13720 Feamster. Now relays only return one of two possible DNS TTL
13721 values, and clients are willing to believe DNS TTL values up to 3
13722 hours long. Closes ticket 19769.
13724 o Major features (directory authority, security):
13725 - The default for AuthDirPinKeys is now 1: directory authorities
13726 will reject relays where the RSA identity key matches a previously
13727 seen value, but the Ed25519 key has changed. Closes ticket 18319.
13729 o Major bugfixes (client, guard, crash):
13730 - In circuit_get_global_origin_list(), return the actual list of
13731 origin circuits. The previous version of this code returned the
13732 list of all the circuits, and could have caused strange bugs,
13733 including possible crashes. Fixes bug 21118; bugfix
13736 o Major bugfixes (client, onion service, also in 0.2.9.9):
13737 - Fix a client-side onion service reachability bug, where multiple
13738 socks requests to an onion service (or a single slow request)
13739 could cause us to mistakenly mark some of the service's
13740 introduction points as failed, and we cache that failure so
13741 eventually we run out and can't reach the service. Also resolves a
13742 mysterious "Remote server sent bogus reason code 65021" log
13743 warning. The bug was introduced in ticket 17218, where we tried to
13744 remember the circuit end reason as a uint16_t, which mangled
13745 negative values. Partially fixes bug 21056 and fixes bug 20307;
13746 bugfix on 0.2.8.1-alpha.
13748 o Major bugfixes (DNS):
13749 - Fix a bug that prevented exit nodes from caching DNS records for
13750 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
13752 o Minor features (controller):
13753 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
13754 shared-random values to the controller. Closes ticket 19925.
13756 o Minor features (entry guards):
13757 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
13758 break regression tests.
13759 - Require UseEntryGuards when UseBridges is set, in order to make
13760 sure bridges aren't bypassed. Resolves ticket 20502.
13762 o Minor features (fallback directories):
13763 - Select 200 fallback directories for each release. Closes
13765 - Allow 3 fallback relays per operator, which is safe now that we
13766 are choosing 200 fallback relays. Closes ticket 20912.
13767 - Exclude relays affected by bug 20499 from the fallback list.
13768 Exclude relays from the fallback list if they are running versions
13769 known to be affected by bug 20499, or if in our tests they deliver
13770 a stale consensus (i.e. one that expired more than 24 hours ago).
13771 Closes ticket 20539.
13772 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
13774 - Require fallback directories to have the same address and port for
13775 7 days (now that we have enough relays with this stability).
13776 Relays whose OnionOO stability timer is reset on restart by bug
13777 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
13778 this issue. Closes ticket 20880; maintains short-term fix
13780 - Require fallbacks to have flags for 90% of the time (weighted
13781 decaying average), rather than 95%. This allows at least 73% of
13782 clients to bootstrap in the first 5 seconds without contacting an
13783 authority. Part of ticket 18828.
13784 - Annotate updateFallbackDirs.py with the bandwidth and consensus
13785 weight for each candidate fallback. Closes ticket 20878.
13786 - Make it easier to change the output sort order of fallbacks.
13787 Closes ticket 20822.
13788 - Display the relay fingerprint when downloading consensuses from
13789 fallbacks. Closes ticket 20908.
13791 o Minor features (geoip, also in 0.2.9.9):
13792 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
13795 o Minor features (next-gen onion service directories):
13796 - Remove the "EnableOnionServicesV3" consensus parameter that we
13797 introduced in 0.3.0.1-alpha: relays are now always willing to act
13798 as v3 onion service directories. Resolves ticket 19899.
13800 o Minor features (linting):
13801 - Enhance the changes file linter to warn on Tor versions that are
13802 prefixed with "tor-". Closes ticket 21096.
13804 o Minor features (logging):
13805 - In several places, describe unset ed25519 keys as "<unset>",
13806 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
13808 o Minor bugfix (control protocol):
13809 - The reply to a "GETINFO config/names" request via the control
13810 protocol now spells the type "Dependent" correctly. This is a
13811 breaking change in the control protocol. (The field seems to be
13812 ignored by the most common known controllers.) Fixes bug 18146;
13813 bugfix on 0.1.1.4-alpha.
13815 o Minor bugfixes (bug resilience):
13816 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
13817 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
13818 Hans Jerry Illikainen.
13820 o Minor bugfixes (build):
13821 - Replace obsolete Autoconf macros with their modern equivalent and
13822 prevent similar issues in the future. Fixes bug 20990; bugfix
13825 o Minor bugfixes (client, guards):
13826 - Fix bug where Tor would think that there are circuits waiting for
13827 better guards even though those circuits have been freed. Fixes
13828 bug 21142; bugfix on 0.3.0.1-alpha.
13830 o Minor bugfixes (config):
13831 - Don't assert on startup when trying to get the options list and
13832 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
13833 options so of course they aren't ready yet. Fixes bug 21062;
13834 bugfix on 0.2.9.3-alpha.
13836 o Minor bugfixes (controller):
13837 - Make the GETINFO interface for inquiring about entry guards
13838 support the new guards backend. Fixes bug 20823; bugfix
13841 o Minor bugfixes (dead code):
13842 - Remove a redundant check for PidFile changes at runtime in
13843 options_transition_allowed(): this check is already performed
13844 regardless of whether the sandbox is active. Fixes bug 21123;
13845 bugfix on 0.2.5.4-alpha.
13847 o Minor bugfixes (documentation):
13848 - Update the tor manual page to document every option that can not
13849 be changed while tor is running. Fixes bug 21122.
13851 o Minor bugfixes (fallback directories):
13852 - Stop failing when a relay has no uptime data in
13853 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
13854 - Avoid checking fallback candidates' DirPorts if they are down in
13855 OnionOO. When a relay operator has multiple relays, this
13856 prioritizes relays that are up over relays that are down. Fixes
13857 bug 20926; bugfix on 0.2.8.3-alpha.
13858 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
13859 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
13861 o Minor bugfixes (guards, bootstrapping):
13862 - When connecting to a directory guard during bootstrap, do not mark
13863 the guard as successful until we receive a good-looking directory
13864 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
13866 o Minor bugfixes (onion services):
13867 - Fix the config reload pruning of old vs new services so it
13868 actually works when both ephemeral and non-ephemeral services are
13869 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
13870 - Allow the number of introduction points to be as low as 0, rather
13871 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
13873 o Minor bugfixes (IPv6):
13874 - Make IPv6-using clients try harder to find an IPv6 directory
13875 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
13876 - When IPv6 addresses have not been downloaded yet (microdesc
13877 consensus documents don't list relay IPv6 addresses), use hard-
13878 coded addresses for authorities, fallbacks, and configured
13879 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
13880 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
13882 o Minor bugfixes (memory leaks):
13883 - Fix a memory leak when configuring hidden services. Fixes bug
13884 20987; bugfix on 0.3.0.1-alpha.
13886 o Minor bugfixes (portability, also in 0.2.9.9):
13887 - Avoid crashing when Tor is built using headers that contain
13888 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
13889 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
13891 - Fix Libevent detection on platforms without Libevent 1 headers
13892 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
13894 o Minor bugfixes (relay):
13895 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
13896 initializing the keys would reset the DataDirectory to 0700
13897 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
13898 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
13900 o Minor bugfixes (testing):
13901 - Remove undefined behavior from the backtrace generator by removing
13902 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
13904 o Minor bugfixes (unit tests):
13905 - Allow the unit tests to pass even when DNS lookups of bogus
13906 addresses do not fail as expected. Fixes bug 20862 and 20863;
13907 bugfix on unit tests introduced in 0.2.8.1-alpha
13908 through 0.2.9.4-alpha.
13910 o Code simplification and refactoring:
13911 - Refactor code to manipulate global_origin_circuit_list into
13912 separate functions. Closes ticket 20921.
13914 o Documentation (formatting):
13915 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
13916 blocks were incorrectly appearing. Closes ticket 20885.
13918 o Documentation (man page):
13919 - Clarify many options in tor.1 and add some min/max values for
13920 HiddenService options. Closes ticket 21058.
13923 Changes in version 0.2.9.9 - 2017-01-23
13924 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
13925 cause relays and clients to crash, even if they were not built with
13926 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
13927 versions, and also affects 0.3.0.1-alpha: all relays running an affected
13928 version should upgrade.
13930 This release also resolves a client-side onion service reachability
13931 bug, and resolves a pair of small portability issues.
13933 o Major bugfixes (security):
13934 - Downgrade the "-ftrapv" option from "always on" to "only on when
13935 --enable-expensive-hardening is provided." This hardening option,
13936 like others, can turn survivable bugs into crashes -- and having
13937 it on by default made a (relatively harmless) integer overflow bug
13938 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
13939 bugfix on 0.2.9.1-alpha.
13941 o Major bugfixes (client, onion service):
13942 - Fix a client-side onion service reachability bug, where multiple
13943 socks requests to an onion service (or a single slow request)
13944 could cause us to mistakenly mark some of the service's
13945 introduction points as failed, and we cache that failure so
13946 eventually we run out and can't reach the service. Also resolves a
13947 mysterious "Remote server sent bogus reason code 65021" log
13948 warning. The bug was introduced in ticket 17218, where we tried to
13949 remember the circuit end reason as a uint16_t, which mangled
13950 negative values. Partially fixes bug 21056 and fixes bug 20307;
13951 bugfix on 0.2.8.1-alpha.
13953 o Minor features (geoip):
13954 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
13957 o Minor bugfixes (portability):
13958 - Avoid crashing when Tor is built using headers that contain
13959 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
13960 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
13962 - Fix Libevent detection on platforms without Libevent 1 headers
13963 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
13966 Changes in version 0.3.0.1-alpha - 2016-12-19
13967 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
13968 series. It strengthens Tor's link and circuit handshakes by
13969 identifying relays by their Ed25519 keys, improves the algorithm that
13970 clients use to choose and maintain their list of guards, and includes
13971 additional backend support for the next-generation hidden service
13972 design. It also contains numerous other small features and
13973 improvements to security, correctness, and performance.
13975 Below are the changes since 0.2.9.8.
13977 o Major features (guard selection algorithm):
13978 - Tor's guard selection algorithm has been redesigned from the
13979 ground up, to better support unreliable networks and restrictive
13980 sets of entry nodes, and to better resist guard-capture attacks by
13981 hostile local networks. Implements proposal 271; closes
13984 o Major features (next-generation hidden services):
13985 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
13986 prop224 aka "Next Generation Hidden Services". Service and clients
13987 don't use this functionality yet. Closes ticket 19043. Based on
13988 initial code by Alec Heifetz.
13989 - Relays now support the HSDir version 3 protocol, so that they can
13990 can store and serve v3 descriptors. This is part of the next-
13991 generation onion service work detailed in proposal 224. Closes
13994 o Major features (protocol, ed25519 identity keys):
13995 - Relays now use Ed25519 to prove their Ed25519 identities and to
13996 one another, and to clients. This algorithm is faster and more
13997 secure than the RSA-based handshake we've been doing until now.
13998 Implements the second big part of proposal 220; Closes
14000 - Clients now support including Ed25519 identity keys in the EXTEND2
14001 cells they generate. By default, this is controlled by a consensus
14002 parameter, currently disabled. You can turn this feature on for
14003 testing by setting ExtendByEd25519ID in your configuration. This
14004 might make your traffic appear different than the traffic
14005 generated by other users, however. Implements part of ticket
14006 15056; part of proposal 220.
14007 - Relays now understand requests to extend to other relays by their
14008 Ed25519 identity keys. When an Ed25519 identity key is included in
14009 an EXTEND2 cell, the relay will only extend the circuit if the
14010 other relay can prove ownership of that identity. Implements part
14011 of ticket 15056; part of proposal 220.
14013 o Major bugfixes (scheduler):
14014 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
14015 caused the channel scheduler to behave more or less randomly,
14016 rather than preferring channels with higher-priority circuits.
14017 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
14019 o Minor features (controller):
14020 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
14021 rather than "unrecognized." Closes ticket 20389; patch from
14024 o Minor features (diagnostic, directory client):
14025 - Warn when we find an unexpected inconsistency in directory
14026 download status objects. Prevents some negative consequences of
14029 o Minor features (directory authority):
14030 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
14031 default) to control whether authorities should try to probe relays
14032 by their Ed25519 link keys. This option will go away in a few
14033 releases--unless we encounter major trouble in our ed25519 link
14034 protocol rollout, in which case it will serve as a safety option.
14036 o Minor features (directory cache):
14037 - Relays and bridges will now refuse to serve the consensus they
14038 have if they know it is too old for a client to use. Closes
14041 o Minor features (ed25519 link handshake):
14042 - Advertise support for the ed25519 link handshake using the
14043 subprotocol-versions mechanism, so that clients can tell which
14044 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
14046 o Minor features (fingerprinting resistance, authentication):
14047 - Extend the length of RSA keys used for TLS link authentication to
14048 2048 bits. (These weren't used for forward secrecy; for forward
14049 secrecy, we used P256.) Closes ticket 13752.
14051 o Minor features (infrastructure):
14052 - Implement smartlist_add_strdup() function. Replaces the use of
14053 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
14055 o Minor bugfixes (client):
14056 - When clients that use bridges start up with a cached consensus on
14057 disk, they were ignoring it and downloading a new one. Now they
14058 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
14060 o Minor bugfixes (configuration):
14061 - Accept non-space whitespace characters after the severity level in
14062 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
14063 - Support "TByte" and "TBytes" units in options given in bytes.
14064 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
14065 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
14067 o Minor bugfixes (consensus weight):
14068 - Add new consensus method that initializes bw weights to 1 instead
14069 of 0. This prevents a zero weight from making it all the way to
14070 the end (happens in small testing networks) and causing an error.
14071 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
14073 o Minor bugfixes (descriptors):
14074 - Correctly recognise downloaded full descriptors as valid, even
14075 when using microdescriptors as circuits. This affects clients with
14076 FetchUselessDescriptors set, and may affect directory authorities.
14077 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
14079 o Minor bugfixes (directory system):
14080 - Download all consensus flavors, descriptors, and authority
14081 certificates when FetchUselessDescriptors is set, regardless of
14082 whether tor is a directory cache or not. Fixes bug 20667; bugfix
14083 on all recent tor versions.
14084 - Bridges and relays now use microdescriptors (like clients do)
14085 rather than old-style router descriptors. Now bridges will blend
14086 in with clients in terms of the circuits they build. Fixes bug
14087 6769; bugfix on 0.2.3.2-alpha.
14089 o Minor bugfixes (ed25519 certificates):
14090 - Correctly interpret ed25519 certificates that would expire some
14091 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
14093 o Minor bugfixes (hidden services):
14094 - Stop ignoring misconfigured hidden services. Instead, refuse to
14095 start tor until the misconfigurations have been corrected. Fixes
14096 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
14099 o Minor bugfixes (memory leak at exit):
14100 - Fix a small harmless memory leak at exit of the previously unused
14101 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
14104 o Minor bugfixes (util):
14105 - When finishing writing a file to disk, if we were about to replace
14106 the file with the temporary file created before and we fail to
14107 replace it, remove the temporary file so it doesn't stay on disk.
14108 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
14110 o Minor bugfixes (Windows):
14111 - Check for getpagesize before using it to mmap files. This fixes
14112 compilation in some MinGW environments. Fixes bug 20530; bugfix on
14113 0.1.2.1-alpha. Reported by "ice".
14115 o Code simplification and refactoring:
14116 - Abolish all global guard context in entrynodes.c; replace with new
14117 guard_selection_t structure as preparation for proposal 271.
14118 Closes ticket 19858.
14119 - Introduce rend_service_is_ephemeral() that tells if given onion
14120 service is ephemeral. Replace unclear NULL-checkings for service
14121 directory with this function. Closes ticket 20526.
14122 - Extract magic numbers in circuituse.c into defined variables.
14123 - Refactor circuit_is_available_for_use to remove unnecessary check.
14124 - Refactor circuit_predict_and_launch_new for readability and
14125 testability. Closes ticket 18873.
14126 - Refactor large if statement in purpose_needs_anonymity to use
14127 switch statement instead. Closes part of ticket 20077.
14128 - Refactor the hashing API to return negative values for errors, as
14129 is done as throughout the codebase. Closes ticket 20717.
14130 - Remove data structures that were used to index or_connection
14131 objects by their RSA identity digests. These structures are fully
14132 redundant with the similar structures used in the
14133 channel abstraction.
14134 - Remove duplicate code in the channel_write_*cell() functions.
14135 Closes ticket 13827; patch from Pingl.
14136 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
14137 use only purpose_needs_anonymity. Closes part of ticket 20077.
14138 - The code to generate and parse EXTEND and EXTEND2 cells has been
14139 replaced with code automatically generated by the
14143 - Include the "TBits" unit in Tor's man page. Fixes part of bug
14144 20622; bugfix on 0.2.5.1-alpha.
14145 - Change '1' to 'weight_scale' in consensus bw weights calculation
14146 comments, as that is reality. Closes ticket 20273. Patch
14148 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
14149 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
14151 - Stop the man page from incorrectly stating that HiddenServiceDir
14152 must already exist. Fixes 20486.
14153 - Clarify that when ClientRejectInternalAddresses is enabled (which
14154 is the default), multicast DNS hostnames for machines on the local
14155 network (of the form *.local) are also rejected. Closes
14158 o Removed features:
14159 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
14160 limit for relays running on a single IP applies to authority IP
14161 addresses as well as to non-authority IP addresses. Closes
14163 - The UseDirectoryGuards torrc option no longer exists: all users
14164 that use entry guards will also use directory guards. Related to
14165 proposal 271; implements part of ticket 20831.
14168 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
14169 from "overcaffeinated".
14170 - Perform the coding style checks when running the tests and fail
14171 when coding style violations are found. Closes ticket 5500.
14172 - Add tests for networkstatus_compute_bw_weights_v10.
14173 - Add unit tests circuit_predict_and_launch_new.
14174 - Extract dummy_origin_circuit_new so it can be used by other
14178 Changes in version 0.2.8.12 - 2016-12-19
14179 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
14180 below) where Tor clients could crash when attempting to visit a
14181 hostile hidden service. Clients are recommended to upgrade as packages
14182 become available for their systems.
14184 It also includes an updated list of fallback directories, backported
14187 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
14188 backported to 0.2.8 in the future.
14190 o Major bugfixes (parsing, security, backported from 0.2.9.8):
14191 - Fix a bug in parsing that could cause clients to read a single
14192 byte past the end of an allocated region. This bug could be used
14193 to cause hardened clients (built with --enable-expensive-hardening)
14194 to crash if they tried to visit a hostile hidden service. Non-
14195 hardened clients are only affected depending on the details of
14196 their platform's memory allocator. Fixes bug 21018; bugfix on
14197 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
14198 2016-12-002 and as CVE-2016-1254.
14200 o Minor features (fallback directory list, backported from 0.2.9.8):
14201 - Replace the 81 remaining fallbacks of the 100 originally
14202 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
14203 fallbacks (123 new, 54 existing, 27 removed) generated in December
14204 2016. Resolves ticket 20170.
14206 o Minor features (geoip, backported from 0.2.9.7-rc):
14207 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
14211 Changes in version 0.2.9.8 - 2016-12-19
14212 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
14214 The Tor 0.2.9 series makes mandatory a number of security features
14215 that were formerly optional. It includes support for a new shared-
14216 randomness protocol that will form the basis for next generation
14217 hidden services, includes a single-hop hidden service mode for
14218 optimizing .onion services that don't actually want to be hidden,
14219 tries harder not to overload the directory authorities with excessive
14220 downloads, and supports a better protocol versioning scheme for
14221 improved compatibility with other implementations of the Tor protocol.
14223 And of course, there are numerous other bugfixes and improvements.
14225 This release also includes a fix for a medium-severity issue (bug
14226 21018 below) where Tor clients could crash when attempting to visit a
14227 hostile hidden service. Clients are recommended to upgrade as packages
14228 become available for their systems.
14230 Below are the changes since 0.2.9.7-rc. For a list of all changes
14231 since 0.2.8, see the ReleaseNotes file.
14233 o Major bugfixes (parsing, security):
14234 - Fix a bug in parsing that could cause clients to read a single
14235 byte past the end of an allocated region. This bug could be used
14236 to cause hardened clients (built with --enable-expensive-hardening)
14237 to crash if they tried to visit a hostile hidden service. Non-
14238 hardened clients are only affected depending on the details of
14239 their platform's memory allocator. Fixes bug 21018; bugfix on
14240 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
14241 2016-12-002 and as CVE-2016-1254.
14243 o Minor features (fallback directory list):
14244 - Replace the 81 remaining fallbacks of the 100 originally
14245 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
14246 fallbacks (123 new, 54 existing, 27 removed) generated in December
14247 2016. Resolves ticket 20170.
14250 Changes in version 0.2.9.7-rc - 2016-12-12
14251 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
14252 including a few that had prevented tests from passing on
14255 o Minor features (geoip):
14256 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
14259 o Minor bugfix (build):
14260 - The current Git revision when building from a local repository is
14261 now detected correctly when using git worktrees. Fixes bug 20492;
14262 bugfix on 0.2.3.9-alpha.
14264 o Minor bugfixes (directory authority):
14265 - When computing old Tor protocol line version in protover, we were
14266 looking at 0.2.7.5 twice instead of a specific case for
14267 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
14269 o Minor bugfixes (download scheduling):
14270 - Resolve a "bug" warning when considering a download schedule whose
14271 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
14273 o Minor bugfixes (logging):
14274 - Downgrade a harmless log message about the
14275 pending_entry_connections list from "warn" to "info". Mitigates
14278 o Minor bugfixes (memory leak):
14279 - Fix a small memory leak when receiving AF_UNIX connections on a
14280 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
14281 - When moving a signed descriptor object from a source to an
14282 existing destination, free the allocated memory inside that
14283 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
14285 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
14286 - Fix a memory leak and use-after-free error when removing entries
14287 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
14288 0.2.5.5-alpha. Patch from "cypherpunks".
14290 o Minor bugfixes (portability):
14291 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
14292 Fixes bug 20935; bugfix on 0.2.9.6-rc.
14294 o Minor bugfixes (unit tests):
14295 - Stop expecting NetBSD unit tests to report success for ipfw. Part
14296 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
14297 - Fix tolerances in unit tests for monotonic time comparisons
14298 between nanoseconds and microseconds. Previously, we accepted a 10
14299 us difference only, which is not realistic on every platform's
14300 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
14301 - Remove a double-free in the single onion service unit test. Stop
14302 ignoring a return value. Make future changes less error-prone.
14303 Fixes bug 20864; bugfix on 0.2.9.6-rc.
14306 Changes in version 0.2.8.11 - 2016-12-08
14307 Tor 0.2.8.11 backports fixes for additional portability issues that
14308 could prevent Tor from building correctly on OSX Sierra, or with
14309 OpenSSL 1.1. Affected users should upgrade; others can safely stay
14312 o Minor bugfixes (portability):
14313 - Avoid compilation errors when building on OSX Sierra. Sierra began
14314 to support the getentropy() and clock_gettime() APIs, but created
14315 a few problems in doing so. Tor 0.2.9 has a more thorough set of
14316 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
14317 monotonic time interfaces. Fixes bug 20865. Bugfix
14320 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
14321 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
14322 architectures. Closes ticket 20588.
14325 Changes in version 0.2.8.10 - 2016-12-02
14326 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
14327 unusable after they left standby mode. It also backports fixes for
14328 a few portability issues and a small but problematic memory leak.
14330 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
14331 - When Tor leaves standby because of a new application request, open
14332 circuits as needed to serve that request. Previously, we would
14333 potentially wait a very long time. Fixes part of bug 19969; bugfix
14336 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
14337 - Clients now respond to new application stream requests immediately
14338 when they arrive, rather than waiting up to one second before
14339 starting to handle them. Fixes part of bug 19969; bugfix
14342 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
14343 - Work around a bug in the OSX 10.12 SDK that would prevent us from
14344 successfully targeting earlier versions of OSX. Resolves
14347 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
14348 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
14349 20551; bugfix on 0.2.1.1-alpha.
14351 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
14352 - Work around a memory leak in OpenSSL 1.1 when encoding public
14353 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
14355 o Minor features (geoip):
14356 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
14359 Changes in version 0.2.9.6-rc - 2016-12-02
14360 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
14361 version. We hope that it will be ready to become stable soon, and we
14362 encourage everyone to test this release. If no showstopper bugs are
14363 found here, the next 0.2.9 release will be stable.
14365 o Major bugfixes (relay, resolver, logging):
14366 - For relays that don't know their own address, avoid attempting a
14367 local hostname resolve for each descriptor we download. This
14368 will cut down on the number of "Success: chose address 'x.x.x.x'"
14369 log lines, and also avoid confusing clock jumps if the resolver
14370 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
14372 o Minor bugfixes (client, fascistfirewall):
14373 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
14374 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
14376 o Minor bugfixes (hidden services):
14377 - Stop ignoring the anonymity status of saved keys for hidden
14378 services and single onion services when first starting tor.
14379 Instead, refuse to start tor if any hidden service key has been
14380 used in a different hidden service anonymity mode. Fixes bug
14381 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
14383 o Minor bugfixes (portability):
14384 - Work around a bug in the OSX 10.12 SDK that would prevent us from
14385 successfully targeting earlier versions of OSX. Resolves
14387 - Run correctly when built on Windows build environments that
14388 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
14390 o Minor bugfixes (single onion services, Tor2web):
14391 - Stop complaining about long-term one-hop circuits deliberately
14392 created by single onion services and Tor2web. These log messages
14393 are intended to diagnose issue 8387, which relates to circuits
14394 hanging around forever for no reason. Fixes bug 20613; bugfix on
14395 0.2.9.1-alpha. Reported by "pastly".
14397 o Minor bugfixes (unit tests):
14398 - Stop spurious failures in the local interface address discovery
14399 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
14403 - Correct the minimum bandwidth value in torrc.sample, and queue a
14404 corresponding change for torrc.minimal. Closes ticket 20085.
14407 Changes in version 0.2.9.5-alpha - 2016-11-08
14408 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
14409 version. We believe one or two probably remain, and we encourage
14410 everyone to test this release.
14412 o Major bugfixes (client performance):
14413 - Clients now respond to new application stream requests immediately
14414 when they arrive, rather than waiting up to one second before
14415 starting to handle them. Fixes part of bug 19969; bugfix
14418 o Major bugfixes (client reliability):
14419 - When Tor leaves standby because of a new application request, open
14420 circuits as needed to serve that request. Previously, we would
14421 potentially wait a very long time. Fixes part of bug 19969; bugfix
14424 o Major bugfixes (download scheduling):
14425 - When using an exponential backoff schedule, do not give up on
14426 downloading just because we have failed a bunch of times. Since
14427 each delay is longer than the last, retrying indefinitely won't
14428 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
14429 - If a consensus expires while we are waiting for certificates to
14430 download, stop waiting for certificates.
14431 - If we stop waiting for certificates less than a minute after we
14432 started downloading them, do not consider the certificate download
14433 failure a separate failure. Fixes bug 20533; bugfix
14435 - Remove the maximum delay on exponential-backoff scheduling. Since
14436 we now allow an infinite number of failures (see ticket 20536), we
14437 must now allow the time to grow longer on each failure. Fixes part
14438 of bug 20534; bugfix on 0.2.9.1-alpha.
14439 - Make our initial download delays closer to those from 0.2.8. Fixes
14440 another part of bug 20534; bugfix on 0.2.9.1-alpha.
14441 - When determining when to download a directory object, handle times
14442 after 2038 if the operating system supports them. (Someday this
14443 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
14444 - When using exponential backoff in test networks, use a lower
14445 exponent, so the delays do not vary as much. This helps test
14446 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
14448 o Minor features (geoip):
14449 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
14452 o Minor bugfixes (client directory scheduling):
14453 - Treat "relay too busy to answer request" as a failed request and a
14454 reason to back off on our retry frequency. This is safe now that
14455 exponential backoffs retry indefinitely, and avoids a bug where we
14456 would reset our download schedule erroneously. Fixes bug 20593;
14457 bugfix on 0.2.9.1-alpha.
14459 o Minor bugfixes (client, logging):
14460 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
14461 assume all nodes support EXTEND2. Use ntor whenever a key is
14462 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
14463 - On DNSPort, stop logging a BUG warning on a failed hostname
14464 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
14466 o Minor bugfixes (hidden services):
14467 - When configuring hidden services, check every hidden service
14468 directory's permissions. Previously, we only checked the last
14469 hidden service. Fixes bug 20529; bugfix the work to fix 13942
14472 o Minor bugfixes (portability):
14473 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
14474 architectures. Closes ticket 20588.
14475 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
14476 removed the ECDH ciphers which caused the tests to fail on
14477 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
14478 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
14479 20551; bugfix on 0.2.1.1-alpha.
14481 o Minor bugfixes (relay bootstrap):
14482 - Ensure relays don't make multiple connections during bootstrap.
14483 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
14485 o Minor bugfixes (relay):
14486 - Work around a memory leak in OpenSSL 1.1 when encoding public
14487 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
14488 - Avoid a small memory leak when informing worker threads about
14489 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
14490 - Do not try to parallelize workers more than 16x without the user
14491 explicitly configuring us to do so, even if we do detect more than
14492 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
14494 o Minor bugfixes (single onion services):
14495 - Start correctly when creating a single onion service in a
14496 directory that did not previously exist. Fixes bug 20484; bugfix
14499 o Minor bugfixes (testing):
14500 - Avoid a unit test failure on systems with over 16 detectable CPU
14501 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
14504 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
14505 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
14506 - Module-level documentation for several more modules. Closes
14507 tickets 19287 and 19290.
14510 Changes in version 0.2.8.9 - 2016-10-17
14511 Tor 0.2.8.9 backports a fix for a security hole in previous versions
14512 of Tor that would allow a remote attacker to crash a Tor client,
14513 hidden service, relay, or authority. All Tor users should upgrade to
14514 this version, or to 0.2.9.4-alpha. Patches will be released for older
14517 o Major features (security fixes, also in 0.2.9.4-alpha):
14518 - Prevent a class of security bugs caused by treating the contents
14519 of a buffer chunk as if they were a NUL-terminated string. At
14520 least one such bug seems to be present in all currently used
14521 versions of Tor, and would allow an attacker to remotely crash
14522 most Tor instances, especially those compiled with extra compiler
14523 hardening. With this defense in place, such bugs can't crash Tor,
14524 though we should still fix them as they occur. Closes ticket
14525 20384 (TROVE-2016-10-001).
14527 o Minor features (geoip):
14528 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
14532 Changes in version 0.2.9.4-alpha - 2016-10-17
14533 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
14534 that would allow a remote attacker to crash a Tor client, hidden
14535 service, relay, or authority. All Tor users should upgrade to this
14536 version, or to 0.2.8.9. Patches will be released for older versions
14539 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
14540 previous versions of Tor, including the implementation of a feature to
14541 future- proof the Tor ecosystem against protocol changes, some bug
14542 fixes necessary for Tor Browser to use unix domain sockets correctly,
14543 and several portability improvements. We anticipate that this will be
14544 the last alpha in the Tor 0.2.9 series, and that the next release will
14545 be a release candidate.
14547 o Major features (security fixes):
14548 - Prevent a class of security bugs caused by treating the contents
14549 of a buffer chunk as if they were a NUL-terminated string. At
14550 least one such bug seems to be present in all currently used
14551 versions of Tor, and would allow an attacker to remotely crash
14552 most Tor instances, especially those compiled with extra compiler
14553 hardening. With this defense in place, such bugs can't crash Tor,
14554 though we should still fix them as they occur. Closes ticket
14555 20384 (TROVE-2016-10-001).
14557 o Major features (subprotocol versions):
14558 - Tor directory authorities now vote on a set of recommended
14559 subprotocol versions, and on a set of required subprotocol
14560 versions. Clients and relays that lack support for a _required_
14561 subprotocol version will not start; those that lack support for a
14562 _recommended_ subprotocol version will warn the user to upgrade.
14563 Closes ticket 19958; implements part of proposal 264.
14564 - Tor now uses "subprotocol versions" to indicate compatibility.
14565 Previously, versions of Tor looked at the declared Tor version of
14566 a relay to tell whether they could use a given feature. Now, they
14567 should be able to rely on its declared subprotocol versions. This
14568 change allows compatible implementations of the Tor protocol(s) to
14569 exist without pretending to be 100% bug-compatible with particular
14570 releases of Tor itself. Closes ticket 19958; implements part of
14573 o Minor feature (fallback directories):
14574 - Remove broken fallbacks from the hard-coded fallback directory
14575 list. Closes ticket 20190; patch by teor.
14577 o Minor features (client, directory):
14578 - Since authorities now omit all routers that lack the Running and
14579 Valid flags, we assume that any relay listed in the consensus must
14580 have those flags. Closes ticket 20001; implements part of
14583 o Minor features (compilation, portability):
14584 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
14587 o Minor features (development tools, etags):
14588 - Teach the "make tags" Makefile target how to correctly find
14589 "MOCK_IMPL" function definitions. Patch from nherring; closes
14592 o Minor features (geoip):
14593 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
14596 o Minor features (unix domain sockets):
14597 - When configuring a unix domain socket for a SocksPort,
14598 ControlPort, or Hidden service, you can now wrap the address in
14599 quotes, using C-style escapes inside the quotes. This allows unix
14600 domain socket paths to contain spaces.
14602 o Minor features (virtual addresses):
14603 - Increase the maximum number of bits for the IPv6 virtual network
14604 prefix from 16 to 104. In this way, the condition for address
14605 allocation is less restrictive. Closes ticket 20151; feature
14608 o Minor bugfixes (address discovery):
14609 - Stop reordering IP addresses returned by the OS. This makes it
14610 more likely that Tor will guess the same relay IP address every
14611 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
14612 Reported by René Mayrhofer, patch by "cypherpunks".
14614 o Minor bugfixes (client, unix domain sockets):
14615 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
14616 the client address is meaningless. Fixes bug 20261; bugfix
14619 o Minor bugfixes (compilation, OpenBSD):
14620 - Detect Libevent2 functions correctly on systems that provide
14621 libevent2, but where libevent1 is linked with -levent. Fixes bug
14622 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
14624 o Minor bugfixes (configuration):
14625 - When parsing quoted configuration values from the torrc file,
14626 handle windows line endings correctly. Fixes bug 19167; bugfix on
14627 0.2.0.16-alpha. Patch from "Pingl".
14629 o Minor bugfixes (getpass):
14630 - Defensively fix a non-triggerable heap corruption at do_getpass()
14631 to protect ourselves from mistakes in the future. Fixes bug
14632 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
14635 o Minor bugfixes (hidden service):
14636 - Allow hidden services to run on IPv6 addresses even when the
14637 IPv6Exit option is not set. Fixes bug 18357; bugfix
14641 - Add module-level internal documentation for 36 C files that
14642 previously didn't have a high-level overview. Closes ticket #20385.
14644 o Required libraries:
14645 - When building with OpenSSL, Tor now requires version 1.0.1 or
14646 later. OpenSSL 1.0.0 and earlier are no longer supported by the
14647 OpenSSL team, and should not be used. Closes ticket 20303.
14650 Changes in version 0.2.9.3-alpha - 2016-09-23
14651 Tor 0.2.9.3-alpha adds improved support for entities that want to make
14652 high-performance services available through the Tor .onion mechanism
14653 without themselves receiving anonymity as they host those services. It
14654 also tries harder to ensure that all steps on a circuit are using the
14655 strongest crypto possible, strengthens some TLS properties, and
14656 resolves several bugs -- including a pair of crash bugs from the 0.2.8
14657 series. Anybody running an earlier version of 0.2.9.x should upgrade.
14659 o Major bugfixes (crash, also in 0.2.8.8):
14660 - Fix a complicated crash bug that could affect Tor clients
14661 configured to use bridges when replacing a networkstatus consensus
14662 in which one of their bridges was mentioned. OpenBSD users saw
14663 more crashes here, but all platforms were potentially affected.
14664 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
14666 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
14667 - Fix a timing-dependent assertion failure that could occur when we
14668 tried to flush from a circuit after having freed its cells because
14669 of an out-of-memory condition. Fixes bug 20203; bugfix on
14670 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
14673 o Major features (circuit building, security):
14674 - Authorities, relays and clients now require ntor keys in all
14675 descriptors, for all hops (except for rare hidden service protocol
14676 cases), for all circuits, and for all other roles. Part of
14678 - Tor authorities, relays, and clients only use ntor, except for
14679 rare cases in the hidden service protocol. Part of ticket 19163.
14681 o Major features (single-hop "hidden" services):
14682 - Add experimental HiddenServiceSingleHopMode and
14683 HiddenServiceNonAnonymousMode options. When both are set to 1,
14684 every hidden service on a Tor instance becomes a non-anonymous
14685 Single Onion Service. Single Onions make one-hop (direct)
14686 connections to their introduction and rendezvous points. One-hop
14687 circuits make Single Onion servers easily locatable, but clients
14688 remain location-anonymous. This is compatible with the existing
14689 hidden service implementation, and works on the current tor
14690 network without any changes to older relays or clients. Implements
14691 proposal 260, completes ticket 17178. Patch by teor and asn.
14693 o Major features (resource management):
14694 - Tor can now notice it is about to run out of sockets, and
14695 preemptively close connections of lower priority. (This feature is
14696 off by default for now, since the current prioritizing method is
14697 yet not mature enough. You can enable it by setting
14698 "DisableOOSCheck 0", but watch out: it might close some sockets
14699 you would rather have it keep.) Closes ticket 18640.
14701 o Major bugfixes (circuit building):
14702 - Hidden service client-to-intro-point and service-to-rendezvous-
14703 point circuits use the TAP key supplied by the protocol, to avoid
14704 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
14706 o Major bugfixes (compilation, OpenBSD):
14707 - Fix a Libevent-detection bug in our autoconf script that would
14708 prevent Tor from linking successfully on OpenBSD. Patch from
14709 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
14711 o Major bugfixes (hidden services):
14712 - Clients now require hidden services to include the TAP keys for
14713 their intro points in the hidden service descriptor. This prevents
14714 an inadvertent upgrade to ntor, which a malicious hidden service
14715 could use to distinguish clients by consensus version. Fixes bug
14716 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
14718 o Minor features (security, TLS):
14719 - Servers no longer support clients that without AES ciphersuites.
14720 (3DES is no longer considered an acceptable cipher.) We believe
14721 that no such Tor clients currently exist, since Tor has required
14722 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
14724 o Minor feature (fallback directories):
14725 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
14726 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
14727 2016. Closes ticket 20190; patch by teor.
14729 o Minor features (geoip, also in 0.2.8.8):
14730 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
14733 o Minor feature (port flags):
14734 - Add new flags to the *Port options to finer control over which
14735 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
14736 and the synthetic flag OnionTrafficOnly, which is equivalent to
14737 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
14738 18693; patch by "teor".
14740 o Minor features (directory authority):
14741 - After voting, if the authorities decide that a relay is not
14742 "Valid", they no longer include it in the consensus at all. Closes
14743 ticket 20002; implements part of proposal 272.
14745 o Minor features (testing):
14746 - Disable memory protections on OpenBSD when performing our unit
14747 tests for memwipe(). The test deliberately invokes undefined
14748 behavior, and the OpenBSD protections interfere with this. Patch
14749 from "rubiate". Closes ticket 20066.
14751 o Minor features (testing, ipv6):
14752 - Add the single-onion and single-onion-ipv6 chutney targets to
14753 "make test-network-all". This requires a recent chutney version
14754 with the single onion network flavours (git c72a652 or later).
14755 Closes ticket 20072; patch by teor.
14756 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
14757 tests. Remove bridges+hs, as it's somewhat redundant. This
14758 requires a recent chutney version that supports IPv6 clients,
14759 relays, and authorities. Closes ticket 20069; patch by teor.
14761 o Minor features (Tor2web):
14762 - Make Tor2web clients respect ReachableAddresses. This feature was
14763 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
14764 0.2.8.7. Implements feature 20034. Patch by teor.
14766 o Minor features (unit tests):
14767 - We've done significant work to make the unit tests run faster.
14768 - Our link-handshake unit tests now check that when invalid
14769 handshakes fail, they fail with the error messages we expected.
14770 - Our unit testing code that captures log messages no longer
14771 prevents them from being written out if the user asked for them
14772 (by passing --debug or --info or or --notice --warn to the "test"
14773 binary). This change prevents us from missing unexpected log
14774 messages simply because we were looking for others. Related to
14776 - The unit tests now log all warning messages with the "BUG" flag.
14777 Previously, they only logged errors by default. This change will
14778 help us make our testing code more correct, and make sure that we
14779 only hit this code when we mean to. In the meantime, however,
14780 there will be more warnings in the unit test logs than before.
14781 This is preparatory work for ticket 19999.
14782 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
14783 assertion as a test failure.
14785 o Minor bug fixes (circuits):
14786 - Use the CircuitBuildTimeout option whenever
14787 LearnCircuitBuildTimeout is disabled. Previously, we would respect
14788 the option when a user disabled it, but not when it was disabled
14789 because some other option was set. Fixes bug 20073; bugfix on
14790 0.2.4.12-alpha. Patch by teor.
14792 o Minor bugfixes (allocation):
14793 - Change how we allocate memory for large chunks on buffers, to
14794 avoid a (currently impossible) integer overflow, and to waste less
14795 space when allocating unusually large chunks. Fixes bug 20081;
14796 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
14797 - Always include orconfig.h before including any other C headers.
14798 Sometimes, it includes macros that affect the behavior of the
14799 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
14800 first version to use AC_USE_SYSTEM_EXTENSIONS).
14801 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
14802 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
14803 Patch from Gisle Vanem.
14804 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
14805 They apparently require a set of annotations that we aren't
14806 currently using, and they create false positives in our pthreads
14807 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
14809 o Minor bugfixes (directory authority):
14810 - Die with a more useful error when the operator forgets to place
14811 the authority_signing_key file into the keys directory. This
14812 avoids an uninformative assert & traceback about having an invalid
14813 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
14814 - When allowing private addresses, mark Exits that only exit to
14815 private locations as such. Fixes bug 20064; bugfix
14818 o Minor bugfixes (documentation):
14819 - Document the default PathsNeededToBuildCircuits value that's used
14820 by clients when the directory authorities don't set
14821 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
14822 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
14823 - Fix manual for the User option: it takes a username, not a UID.
14824 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
14827 o Minor bugfixes (hidden services):
14828 - Stop logging intro point details to the client log on certain
14829 error conditions. Fixed as part of bug 20012; bugfix on
14830 0.2.4.8-alpha. Patch by teor.
14832 o Minor bugfixes (IPv6, testing):
14833 - Check for IPv6 correctly on Linux when running test networks.
14834 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
14836 o Minor bugfixes (Linux seccomp2 sandbox):
14837 - Add permission to run the sched_yield() and sigaltstack() system
14838 calls, in order to support versions of Tor compiled with asan or
14839 ubsan code that use these calls. Now "sandbox 1" and
14840 "--enable-expensive-hardening" should be compatible on more
14841 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
14843 o Minor bugfixes (logging):
14844 - When logging a message from the BUG() macro, be explicit about
14845 what we were asserting. Previously we were confusing what we were
14846 asserting with what the bug was. Fixes bug 20093; bugfix
14848 - When we are unable to remove the bw_accounting file, do not warn
14849 if the reason we couldn't remove it was that it didn't exist.
14850 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
14852 o Minor bugfixes (option parsing):
14853 - Count unix sockets when counting client listeners (SOCKS, Trans,
14854 NATD, and DNS). This has no user-visible behaviour changes: these
14855 options are set once, and never read. Required for correct
14856 behaviour in ticket 17178. Fixes bug 19677; bugfix on
14857 0.2.6.3-alpha. Patch by teor.
14859 o Minor bugfixes (options):
14860 - Check the consistency of UseEntryGuards and EntryNodes more
14861 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
14863 - Stop changing the configured value of UseEntryGuards on
14864 authorities and Tor2web clients. Fixes bug 20074; bugfix on
14865 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
14868 o Minor bugfixes (Tor2web):
14869 - Prevent Tor2web clients running hidden services, these services
14870 are not anonymous due to the one-hop client paths. Fixes bug
14871 19678. Patch by teor.
14873 o Minor bugfixes (unit tests):
14874 - Fix a shared-random unit test that was failing on big endian
14875 architectures due to internal representation of a integer copied
14876 to a buffer. The test is changed to take a full 32 bytes of data
14877 and use the output of a python script that make the COMMIT and
14878 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
14880 - The tor_tls_server_info_callback unit test no longer crashes when
14881 debug-level logging is turned on. Fixes bug 20041; bugfix
14885 Changes in version 0.2.8.8 - 2016-09-23
14886 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
14887 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
14888 who select public relays as their bridges.
14890 o Major bugfixes (crash):
14891 - Fix a complicated crash bug that could affect Tor clients
14892 configured to use bridges when replacing a networkstatus consensus
14893 in which one of their bridges was mentioned. OpenBSD users saw
14894 more crashes here, but all platforms were potentially affected.
14895 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
14897 o Major bugfixes (relay, OOM handler):
14898 - Fix a timing-dependent assertion failure that could occur when we
14899 tried to flush from a circuit after having freed its cells because
14900 of an out-of-memory condition. Fixes bug 20203; bugfix on
14901 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
14904 o Minor feature (fallback directories):
14905 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
14906 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
14907 2016. Closes ticket 20190; patch by teor.
14909 o Minor features (geoip):
14910 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
14914 Changes in version 0.2.9.2-alpha - 2016-08-24
14915 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
14916 several new features and bugfixes. It also includes an important
14917 authority update and an important bugfix from 0.2.8.7. Everyone who
14918 sets the ReachableAddresses option, and all bridges, are strongly
14919 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
14921 o Directory authority changes (also in 0.2.8.7):
14922 - The "Tonga" bridge authority has been retired; the new bridge
14923 authority is "Bifroest". Closes tickets 19728 and 19690.
14925 o Major bugfixes (client, security, also in 0.2.8.7):
14926 - Only use the ReachableAddresses option to restrict the first hop
14927 in a path. In earlier versions of 0.2.8.x, it would apply to
14928 every hop in the path, with a possible degradation in anonymity
14929 for anyone using an uncommon ReachableAddress setting. Fixes bug
14930 19973; bugfix on 0.2.8.2-alpha.
14932 o Major features (user interface):
14933 - Tor now supports the ability to declare options deprecated, so
14934 that we can recommend that people stop using them. Previously,
14935 this was done in an ad-hoc way. Closes ticket 19820.
14937 o Major bugfixes (directory downloads):
14938 - Avoid resetting download status for consensuses hourly, since we
14939 already have another, smarter retry mechanism. Fixes bug 8625;
14940 bugfix on 0.2.0.9-alpha.
14942 o Minor features (config):
14943 - Warn users when descriptor and port addresses are inconsistent.
14944 Mitigates bug 13953; patch by teor.
14946 o Minor features (geoip):
14947 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
14950 o Minor features (user interface):
14951 - There is a new --list-deprecated-options command-line option to
14952 list all of the deprecated options. Implemented as part of
14955 o Minor bugfixes (code style):
14956 - Fix an integer signedness conversion issue in the case conversion
14957 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
14959 o Minor bugfixes (compilation):
14960 - Build correctly on versions of libevent2 without support for
14961 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
14963 - Fix a compilation warning on GCC versions before 4.6. Our
14964 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
14965 when it is also required as an argument to the compiler pragma.
14966 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
14968 o Minor bugfixes (compilation, also in 0.2.8.7):
14969 - Remove an inappropriate "inline" in tortls.c that was causing
14970 warnings on older versions of GCC. Fixes bug 19903; bugfix
14973 o Minor bugfixes (fallback directories, also in 0.2.8.7):
14974 - Avoid logging a NULL string pointer when loading fallback
14975 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
14976 and 0.2.8.1-alpha. Report and patch by "rubiate".
14978 o Minor bugfixes (logging):
14979 - Log a more accurate message when we fail to dump a microdescriptor.
14980 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
14982 o Minor bugfixes (memory leak):
14983 - Fix a series of slow memory leaks related to parsing torrc files
14984 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
14986 o Deprecated features:
14987 - A number of DNS-cache-related sub-options for client ports are now
14988 deprecated for security reasons, and may be removed in a future
14989 version of Tor. (We believe that client-side DNS caching is a bad
14990 idea for anonymity, and you should not turn it on.) The options
14991 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
14992 UseIPv4Cache, and UseIPv6Cache.
14993 - A number of options are deprecated for security reasons, and may
14994 be removed in a future version of Tor. The options are:
14995 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
14996 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
14997 CloseHSClientCircuitsImmediatelyOnTimeout,
14998 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
14999 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
15000 UseNTorHandshake, and WarnUnsafeSocks.
15001 - The *ListenAddress options are now deprecated as unnecessary: the
15002 corresponding *Port options should be used instead. These options
15003 may someday be removed. The affected options are:
15004 ControlListenAddress, DNSListenAddress, DirListenAddress,
15005 NATDListenAddress, ORListenAddress, SocksListenAddress,
15006 and TransListenAddress.
15009 - Correct the IPv6 syntax in our documentation for the
15010 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
15013 - We no longer include the (dead, deprecated) bufferevent code in
15014 Tor. Closes ticket 19450. Based on a patch from U+039b.
15017 Changes in version 0.2.8.7 - 2016-08-24
15018 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
15019 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
15020 who sets the ReachableAddresses option, and all bridges, are strongly
15021 encouraged to upgrade.
15023 o Directory authority changes:
15024 - The "Tonga" bridge authority has been retired; the new bridge
15025 authority is "Bifroest". Closes tickets 19728 and 19690.
15027 o Major bugfixes (client, security):
15028 - Only use the ReachableAddresses option to restrict the first hop
15029 in a path. In earlier versions of 0.2.8.x, it would apply to
15030 every hop in the path, with a possible degradation in anonymity
15031 for anyone using an uncommon ReachableAddress setting. Fixes bug
15032 19973; bugfix on 0.2.8.2-alpha.
15034 o Minor features (geoip):
15035 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
15038 o Minor bugfixes (compilation):
15039 - Remove an inappropriate "inline" in tortls.c that was causing
15040 warnings on older versions of GCC. Fixes bug 19903; bugfix
15043 o Minor bugfixes (fallback directories):
15044 - Avoid logging a NULL string pointer when loading fallback
15045 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
15046 and 0.2.8.1-alpha. Report and patch by "rubiate".
15049 Changes in version 0.2.9.1-alpha - 2016-08-08
15050 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
15051 series. It improves our support for hardened builds and compiler
15052 warnings, deploys some critical infrastructure for improvements to
15053 hidden services, includes a new timing backend that we hope to use for
15054 better support for traffic padding, makes it easier for programmers to
15055 log unexpected events, and contains other small improvements to
15056 security, correctness, and performance.
15058 Below are the changes since 0.2.8.6.
15060 o New system requirements:
15061 - Tor now requires Libevent version 2.0.10-stable or later. Older
15062 versions of Libevent have less efficient backends for several
15063 platforms, and lack the DNS code that we use for our server-side
15064 DNS support. This implements ticket 19554.
15065 - Tor now requires zlib version 1.2 or later, for security,
15066 efficiency, and (eventually) gzip support. (Back when we started,
15067 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
15068 released in 2003. We recommend the latest version.)
15070 o Major features (build, hardening):
15071 - Tor now builds with -ftrapv by default on compilers that support
15072 it. This option detects signed integer overflow (which C forbids),
15073 and turns it into a hard-failure. We do not apply this option to
15074 code that needs to run in constant time to avoid side-channels;
15075 instead, we use -fwrapv in that code. Closes ticket 17983.
15076 - When --enable-expensive-hardening is selected, stop applying the
15077 clang/gcc sanitizers to code that needs to run in constant time.
15078 Although we are aware of no introduced side-channels, we are not
15079 able to prove that there are none. Related to ticket 17983.
15081 o Major features (compilation):
15082 - Our big list of extra GCC warnings is now enabled by default when
15083 building with GCC (or with anything like Clang that claims to be
15084 GCC-compatible). To make all warnings into fatal compilation
15085 errors, pass --enable-fatal-warnings to configure. Closes
15087 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
15088 turn on C and POSIX extensions. (Previously, we attempted to do
15089 this on an ad hoc basis.) Closes ticket 19139.
15091 o Major features (directory authorities, hidden services):
15092 - Directory authorities can now perform the shared randomness
15093 protocol specified by proposal 250. Using this protocol, directory
15094 authorities generate a global fresh random value every day. In the
15095 future, this value will be used by hidden services to select
15096 HSDirs. This release implements the directory authority feature;
15097 the hidden service side will be implemented in the future as part
15098 of proposal 224. Resolves ticket 16943; implements proposal 250.
15100 o Major features (downloading, random exponential backoff):
15101 - When we fail to download an object from a directory service, wait
15102 for an (exponentially increasing) randomized amount of time before
15103 retrying, rather than a fixed interval as we did before. This
15104 prevents a group of Tor instances from becoming too synchronized,
15105 or a single Tor instance from becoming too predictable, in its
15106 download schedule. Closes ticket 15942.
15108 o Major bugfixes (exit policies):
15109 - Avoid disclosing exit outbound bind addresses, configured port
15110 bind addresses, and local interface addresses in relay descriptors
15111 by default under ExitPolicyRejectPrivate. Instead, only reject
15112 these (otherwise unlisted) addresses if
15113 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
15114 0.2.7.2-alpha. Patch by teor.
15116 o Major bugfixes (hidden service client):
15117 - Allow Tor clients with appropriate controllers to work with
15118 FetchHidServDescriptors set to 0. Previously, this option also
15119 disabled descriptor cache lookup, thus breaking hidden services
15120 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
15122 o Minor features (build, hardening):
15123 - Detect and work around a libclang_rt problem that would prevent
15124 clang from finding __mulodi4() on some 32-bit platforms, and thus
15125 keep -ftrapv from linking on those systems. Closes ticket 19079.
15126 - When building on a system without runtime support for the runtime
15127 hardening options, try to log a useful warning at configuration
15128 time, rather than an incomprehensible warning at link time. If
15129 expensive hardening was requested, this warning becomes an error.
15130 Closes ticket 18895.
15132 o Minor features (code safety):
15133 - In our integer-parsing functions, ensure that maxiumum value we
15134 give is no smaller than the minimum value. Closes ticket 19063;
15137 o Minor features (controller):
15138 - Implement new GETINFO queries for all downloads that use
15139 download_status_t to schedule retries. This allows controllers to
15140 examine the schedule for pending downloads. Closes ticket 19323.
15141 - Allow controllers to configure basic client authorization on
15142 hidden services when they create them with the ADD_ONION control
15143 command. Implements ticket 15588. Patch by "special".
15144 - Fire a STATUS_SERVER controller event whenever the hibernation
15145 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
15147 o Minor features (directory authority):
15148 - Directory authorities now only give the Guard flag to a relay if
15149 they are also giving it the Stable flag. This change allows us to
15150 simplify path selection for clients. It should have minimal effect
15151 in practice, since >99% of Guards already have the Stable flag.
15152 Implements ticket 18624.
15153 - Directory authorities now write their v3-status-votes file out to
15154 disk earlier in the consensus process, so we have a record of the
15155 votes even if we abort the consensus process. Resolves
15158 o Minor features (hidden service):
15159 - Stop being so strict about the payload length of "rendezvous1"
15160 cells. We used to be locked in to the "TAP" handshake length, and
15161 now we can handle better handshakes like "ntor". Resolves
15164 o Minor features (infrastructure, time):
15165 - Tor now uses the operating system's monotonic timers (where
15166 available) for internal fine-grained timing. Previously we would
15167 look at the system clock, and then attempt to compensate for the
15168 clock running backwards. Closes ticket 18908.
15169 - Tor now includes an improved timer backend, so that we can
15170 efficiently support tens or hundreds of thousands of concurrent
15171 timers, as will be needed for some of our planned anti-traffic-
15172 analysis work. This code is based on William Ahern's "timeout.c"
15173 project, which implements a "tickless hierarchical timing wheel".
15174 Closes ticket 18365.
15176 o Minor features (logging):
15177 - Provide a more useful warning message when configured with an
15178 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
15179 - When dumping unparseable router descriptors, optionally store them
15180 in separate files, named by digest, up to a configurable size
15181 limit. You can change the size limit by setting the
15182 MaxUnparseableDescSizeToLog option, and disable this feature by
15183 setting that option to 0. Closes ticket 18322.
15184 - Add a set of macros to check nonfatal assertions, for internal
15185 use. Migrating more of our checks to these should help us avoid
15186 needless crash bugs. Closes ticket 18613.
15188 o Minor features (performance):
15189 - Change the "optimistic data" extension from "off by default" to
15190 "on by default". The default was ordinarily overridden by a
15191 consensus option, but when clients were bootstrapping for the
15192 first time, they would not have a consensus to get the option
15193 from. Changing this default saves a round-trip during startup.
15194 Closes ticket 18815.
15196 o Minor features (relay, usability):
15197 - When the directory authorities refuse a bad relay's descriptor,
15198 encourage the relay operator to contact us. Many relay operators
15199 won't notice this line in their logs, but it's a win if even a few
15200 learn why we don't like what their relay was doing. Resolves
15203 o Minor features (testing):
15204 - Let backtrace tests work correctly under AddressSanitizer. Fixes
15205 part of bug 18934; bugfix on 0.2.5.2-alpha.
15206 - Move the test-network.sh script to chutney, and modify tor's test-
15207 network.sh to call the (newer) chutney version when available.
15208 Resolves ticket 19116. Patch by teor.
15209 - Use the lcov convention for marking lines as unreachable, so that
15210 we don't count them when we're generating test coverage data.
15211 Update our coverage tools to understand this convention. Closes
15214 o Minor bugfixes (bootstrap):
15215 - Remember the directory we fetched the consensus or previous
15216 certificates from, and use it to fetch future authority
15217 certificates. This change improves bootstrapping performance.
15218 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
15220 o Minor bugfixes (build):
15221 - The test-stem and test-network makefile targets now depend only on
15222 the tor binary that they are testing. Previously, they depended on
15223 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
15224 patch from "cypherpunks".
15226 o Minor bugfixes (circuits):
15227 - Make sure extend_info_from_router() is only called on servers.
15228 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
15230 o Minor bugfixes (compilation):
15231 - When building with Clang, use a full set of GCC warnings.
15232 (Previously, we included only a subset, because of the way we
15233 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
15235 o Minor bugfixes (directory authority):
15236 - Authorities now sort the "package" lines in their votes, for ease
15237 of debugging. (They are already sorted in consensus documents.)
15238 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
15239 - When parsing a detached signature, make sure we use the length of
15240 the digest algorithm instead of an hardcoded DIGEST256_LEN in
15241 order to avoid comparing bytes out-of-bounds with a smaller digest
15242 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
15244 o Minor bugfixes (documentation):
15245 - Document the --passphrase-fd option in the tor manpage. Fixes bug
15246 19504; bugfix on 0.2.7.3-rc.
15247 - Fix the description of the --passphrase-fd option in the
15248 tor-gencert manpage. The option is used to pass the number of a
15249 file descriptor to read the passphrase from, not to read the file
15250 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
15252 o Minor bugfixes (ephemeral hidden service):
15253 - When deleting an ephemeral hidden service, close its intro points
15254 even if they are not completely open. Fixes bug 18604; bugfix
15257 o Minor bugfixes (guard selection):
15258 - Use a single entry guard even if the NumEntryGuards consensus
15259 parameter is not provided. Fixes bug 17688; bugfix
15261 - Don't mark guards as unreachable if connection_connect() fails.
15262 That function fails for local reasons, so it shouldn't reveal
15263 anything about the status of the guard. Fixes bug 14334; bugfix
15266 o Minor bugfixes (hidden service client):
15267 - Increase the minimum number of internal circuits we preemptively
15268 build from 2 to 3, so a circuit is available when a client
15269 connects to another onion service. Fixes bug 13239; bugfix
15272 o Minor bugfixes (logging):
15273 - When logging a directory ownership mismatch, log the owning
15274 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
15276 o Minor bugfixes (memory leaks):
15277 - Fix a small, uncommon memory leak that could occur when reading a
15278 truncated ed25519 key file. Fixes bug 18956; bugfix
15281 o Minor bugfixes (testing):
15282 - Allow clients to retry HSDirs much faster in test networks. Fixes
15283 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
15284 - Disable ASAN's detection of segmentation faults while running
15285 test_bt.sh, so that we can make sure that our own backtrace
15286 generation code works. Fixes another aspect of bug 18934; bugfix
15287 on 0.2.5.2-alpha. Patch from "cypherpunks".
15288 - Fix the test-network-all target on out-of-tree builds by using the
15289 correct path to the test driver script. Fixes bug 19421; bugfix
15292 o Minor bugfixes (time):
15293 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
15294 bugfix on all released tor versions.
15295 - When computing the difference between two times in milliseconds,
15296 we now round to the nearest millisecond correctly. Previously, we
15297 could sometimes round in the wrong direction. Fixes bug 19428;
15298 bugfix on 0.2.2.2-alpha.
15300 o Minor bugfixes (user interface):
15301 - Display a more accurate number of suppressed messages in the log
15302 rate-limiter. Previously, there was a potential integer overflow
15303 in the counter. Now, if the number of messages hits a maximum, the
15304 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
15306 - Fix a typo in the passphrase prompt for the ed25519 identity key.
15307 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
15309 o Code simplification and refactoring:
15310 - Remove redundant declarations of the MIN macro. Closes
15312 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
15313 Closes ticket 18462; patch from "icanhasaccount".
15314 - Split the 600-line directory_handle_command_get function into
15315 separate functions for different URL types. Closes ticket 16698.
15318 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
15319 ticket 19153. Patch from "U+039b".
15321 o Removed features:
15322 - Remove support for "GET /tor/bytes.txt" DirPort request, and
15323 "GETINFO dir-usage" controller request, which were only available
15324 via a compile-time option in Tor anyway. Feature was added in
15325 0.2.2.1-alpha. Resolves ticket 19035.
15326 - There is no longer a compile-time option to disable support for
15327 TransPort. (If you don't want TransPort; just don't use it.) Patch
15328 from "U+039b". Closes ticket 19449.
15331 - Run more workqueue tests as part of "make check". These had
15332 previously been implemented, but you needed to know special
15333 command-line options to enable them.
15334 - We now have unit tests for our code to reject zlib "compression
15335 bombs". (Fortunately, the code works fine.)
15338 Changes in version 0.2.8.6 - 2016-08-02
15340 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
15342 The Tor 0.2.8 series improves client bootstrapping performance,
15343 completes the authority-side implementation of improved identity
15344 keys for relays, and includes numerous bugfixes and performance
15345 improvements throughout the program. This release continues to
15346 improve the coverage of Tor's test suite. For a full list of
15347 changes since Tor 0.2.7, see the ReleaseNotes file.
15349 Changes since 0.2.8.5-rc:
15351 o Minor features (geoip):
15352 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
15355 o Minor bugfixes (compilation):
15356 - Fix a compilation warning in the unit tests on systems where char
15357 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
15359 o Minor bugfixes (fallback directories):
15360 - Remove 1 fallback that was on the hardcoded list, then opted-out,
15361 leaving 89 of the 100 fallbacks originally introduced in Tor
15362 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
15364 o Minor bugfixes (Linux seccomp2 sandbox):
15365 - Allow more syscalls when running with "Sandbox 1" enabled:
15366 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
15367 some systems, these are required for Tor to start. Fixes bug
15368 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
15369 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
15370 so that get_interface_address6_via_udp_socket_hack() can work.
15371 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
15374 Changes in version 0.2.8.5-rc - 2016-07-07
15375 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
15376 series. If we find no new bugs or regressions here, the first stable
15377 0.2.8 release will be identical to it. It has a few small bugfixes
15378 against previous versions.
15380 o Directory authority changes:
15381 - Urras is no longer a directory authority. Closes ticket 19271.
15383 o Major bugfixes (heartbeat):
15384 - Fix a regression that would crash Tor when the periodic
15385 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
15386 0.2.8.1-alpha. Reported by "kubaku".
15388 o Minor features (build):
15389 - Tor now again builds with the recent OpenSSL 1.1 development
15390 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
15391 - When building manual pages, set the timezone to "UTC", so that the
15392 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
15393 Patch from intrigeri.
15395 o Minor bugfixes (fallback directory selection):
15396 - Avoid errors during fallback selection if there are no eligible
15397 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
15400 o Minor bugfixes (IPv6, microdescriptors):
15401 - Don't check node addresses when we only have a routerstatus. This
15402 allows IPv6-only clients to bootstrap by fetching microdescriptors
15403 from fallback directory mirrors. (The microdescriptor consensus
15404 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
15407 o Minor bugfixes (logging):
15408 - Reduce pointlessly verbose log messages when directory servers
15409 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
15410 0.2.8.1-alpha. Patch by teor.
15411 - When a fallback directory changes its fingerprint from the hard-
15412 coded fingerprint, log a less severe, more explanatory log
15413 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
15415 o Minor bugfixes (Linux seccomp2 sandboxing):
15416 - Allow statistics to be written to disk when "Sandbox 1" is
15417 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
15418 0.2.6.1-alpha respectively.
15420 o Minor bugfixes (user interface):
15421 - Remove a warning message "Service [scrubbed] not found after
15422 descriptor upload". This message appears when one uses HSPOST
15423 control command to upload a service descriptor. Since there is
15424 only a descriptor and no service, showing this message is
15425 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
15427 o Fallback directory list:
15428 - Add a comment to the generated fallback directory list that
15429 explains how to comment out unsuitable fallbacks in a way that's
15430 compatible with the stem fallback parser.
15431 - Update fallback whitelist and blacklist based on relay operator
15432 emails. Blacklist unsuitable (non-working, over-volatile)
15433 fallbacks. Resolves ticket 19071. Patch by teor.
15434 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
15435 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
15436 ticket 19071; patch by teor.
15439 Changes in version 0.2.8.4-rc - 2016-06-15
15440 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
15441 If we find no new bugs or regressions here, the first stable 0.2.8
15442 release will be identical to it. It has a few small bugfixes against
15445 o Major bugfixes (user interface):
15446 - Correctly give a warning in the cases where a relay is specified
15447 by nickname, and one such relay is found, but it is not officially
15448 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
15450 o Minor features (build):
15451 - Tor now builds once again with the recent OpenSSL 1.1 development
15452 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
15454 o Minor features (geoip):
15455 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
15458 o Minor bugfixes (compilation):
15459 - Cause the unit tests to compile correctly on mingw64 versions that
15460 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
15462 o Minor bugfixes (downloading):
15463 - Predict more correctly whether we'll be downloading over HTTP when
15464 we determine the maximum length of a URL. This should avoid a
15465 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
15469 Changes in version 0.2.8.3-alpha - 2016-05-26
15470 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
15471 the course of the 0.2.8 development cycle. It improves the behavior of
15472 directory clients, fixes several crash bugs, fixes a gap in compiler
15473 hardening, and allows the full integration test suite to run on
15476 o Major bugfixes (security, client, DNS proxy):
15477 - Stop a crash that could occur when a client running with DNSPort
15478 received a query with multiple address types, and the first
15479 address type was not supported. Found and fixed by Scott Dial.
15480 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
15482 o Major bugfixes (security, compilation):
15483 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
15484 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
15485 cause a compiler warning, thereby making other checks fail, and
15486 needlessly disabling compiler-hardening support. Fixes one case of
15487 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
15489 o Major bugfixes (security, directory authorities):
15490 - Fix a crash and out-of-bounds write during authority voting, when
15491 the list of relays includes duplicate ed25519 identity keys. Fixes
15492 bug 19032; bugfix on 0.2.8.2-alpha.
15494 o Major bugfixes (client, bootstrapping):
15495 - Check if bootstrap consensus downloads are still needed when the
15496 linked connection attaches. This prevents tor making unnecessary
15497 begindir-style connections, which are the only directory
15498 connections tor clients make since the fix for 18483 was merged.
15499 - Fix some edge cases where consensus download connections may not
15500 have been closed, even though they were not needed. Related to fix
15502 - Make relays retry consensus downloads the correct number of times,
15503 rather than the more aggressive client retry count. Fixes part of
15505 - Stop downloading consensuses when we have a consensus, even if we
15506 don't have all the certificates for it yet. Fixes bug 18809;
15507 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
15509 o Major bugfixes (directory mirrors):
15510 - Decide whether to advertise begindir support in the the same way
15511 we decide whether to advertise our DirPort. Allowing these
15512 decisions to become out-of-sync led to surprising behavior like
15513 advertising begindir support when hibernation made us not
15514 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
15517 o Major bugfixes (IPv6 bridges, client):
15518 - Actually use IPv6 addresses when selecting directory addresses for
15519 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
15522 o Major bugfixes (key management):
15523 - If OpenSSL fails to generate an RSA key, do not retain a dangling
15524 pointer to the previous (uninitialized) key value. The impact here
15525 should be limited to a difficult-to-trigger crash, if OpenSSL is
15526 running an engine that makes key generation failures possible, or
15527 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
15528 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
15531 o Major bugfixes (testing):
15532 - Fix a bug that would block 'make test-network-all' on systems where
15533 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
15534 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
15535 bugfix on 0.2.8.1-alpha.
15537 o Minor features (clients):
15538 - Make clients, onion services, and bridge relays always use an
15539 encrypted begindir connection for directory requests. Resolves
15540 ticket 18483. Patch by "teor".
15542 o Minor features (fallback directory mirrors):
15543 - Give each fallback the same weight for client selection; restrict
15544 fallbacks to one per operator; report fallback directory detail
15545 changes when rebuilding list; add new fallback directory mirrors
15546 to the whitelist; and many other minor simplifications and fixes.
15547 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
15548 0.2.8.1-alpha; patch by "teor".
15549 - Replace the 21 fallbacks generated in January 2016 and included in
15550 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
15551 2016. Closes task 17158; patch by "teor".
15553 o Minor features (geoip):
15554 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
15557 o Minor bugfixes (assert, portability):
15558 - Fix an assertion failure in memarea.c on systems where "long" is
15559 shorter than the size of a pointer. Fixes bug 18716; bugfix
15562 o Minor bugfixes (bootstrap):
15563 - Consistently use the consensus download schedule for authority
15564 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
15566 o Minor bugfixes (build):
15567 - Remove a pair of redundant AM_CONDITIONAL declarations from
15568 configure.ac. Fixes one final case of bug 17744; bugfix
15570 - Resolve warnings when building on systems that are concerned with
15571 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
15573 - When libscrypt.h is found, but no libscrypt library can be linked,
15574 treat libscrypt as absent. Fixes bug 19161; bugfix
15577 o Minor bugfixes (client):
15578 - Turn all TestingClientBootstrap* into non-testing torrc options.
15579 This changes simply renames them by removing "Testing" in front of
15580 them and they do not require TestingTorNetwork to be enabled
15581 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
15582 - Make directory node selection more reliable, mainly for IPv6-only
15583 clients and clients with few reachable addresses. Fixes bug 18929;
15584 bugfix on 0.2.8.1-alpha. Patch by "teor".
15586 o Minor bugfixes (controller, microdescriptors):
15587 - Make GETINFO dir/status-vote/current/consensus conform to the
15588 control specification by returning "551 Could not open cached
15589 consensus..." when not caching consensuses. Fixes bug 18920;
15590 bugfix on 0.2.2.6-alpha.
15592 o Minor bugfixes (crypto, portability):
15593 - The SHA3 and SHAKE routines now produce the correct output on Big
15594 Endian systems. No code calls either algorithm yet, so this is
15595 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
15596 - Tor now builds again with the recent OpenSSL 1.1 development
15597 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
15600 o Minor bugfixes (directories):
15601 - When fetching extrainfo documents, compare their SHA256 digests
15602 and Ed25519 signing key certificates with the routerinfo that led
15603 us to fetch them, rather than with the most recent routerinfo.
15604 Otherwise we generate many spurious warnings about mismatches.
15605 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
15607 o Minor bugfixes (logging):
15608 - When we can't generate a signing key because OfflineMasterKey is
15609 set, do not imply that we should have been able to load it. Fixes
15610 bug 18133; bugfix on 0.2.7.2-alpha.
15611 - Stop periodic_event_dispatch() from blasting twelve lines per
15612 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
15613 - When rejecting a misformed INTRODUCE2 cell, only log at
15614 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
15616 o Minor bugfixes (pluggable transports):
15617 - Avoid reporting a spurious error when we decide that we don't need
15618 to terminate a pluggable transport because it has already exited.
15619 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
15621 o Minor bugfixes (pointer arithmetic):
15622 - Fix a bug in memarea_alloc() that could have resulted in remote
15623 heap write access, if Tor had ever passed an unchecked size to
15624 memarea_alloc(). Fortunately, all the sizes we pass to
15625 memarea_alloc() are pre-checked to be less than 128 kilobytes.
15626 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
15629 o Minor bugfixes (relays):
15630 - Consider more config options when relays decide whether to
15631 regenerate their descriptor. Fixes more of bug 12538; bugfix
15633 - Resolve some edge cases where we might launch an ORPort
15634 reachability check even when DisableNetwork is set. Noticed while
15635 fixing bug 18616; bugfix on 0.2.3.9-alpha.
15637 o Minor bugfixes (statistics):
15638 - We now include consensus downloads via IPv6 in our directory-
15639 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
15641 o Minor bugfixes (testing):
15642 - Allow directories in small networks to bootstrap by skipping
15643 DirPort checks when the consensus has no exits. Fixes bug 19003;
15644 bugfix on 0.2.8.1-alpha. Patch by teor.
15645 - Fix a small memory leak that would occur when the
15646 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
15647 bugfix on 0.2.5.2-alpha.
15649 o Minor bugfixes (time handling):
15650 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
15651 field. Otherwise, our unit tests crash on Windows. Fixes bug
15652 18977; bugfix on 0.2.2.25-alpha.
15655 - Document the contents of the 'datadir/keys' subdirectory in the
15656 manual page. Closes ticket 17621.
15657 - Stop recommending use of nicknames to identify relays in our
15658 MapAddress documentation. Closes ticket 18312.
15661 Changes in version 0.2.8.2-alpha - 2016-03-28
15662 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
15663 bugs in earlier versions of Tor, including some that prevented
15664 authorities using Tor 0.2.7.x from running correctly. IPv6 and
15665 directory support should also be much improved.
15667 o New system requirements:
15668 - Tor no longer supports versions of OpenSSL with a broken
15669 implementation of counter mode. (This bug was present in OpenSSL
15670 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
15671 longer runs with, these versions.
15672 - Tor no longer attempts to support platforms where the "time_t"
15673 type is unsigned. (To the best of our knowledge, only OpenVMS does
15674 this, and Tor has never actually built on OpenVMS.) Closes
15676 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
15677 later (released in 2008 and 2009 respectively). If you are
15678 building Tor from the git repository instead of from the source
15679 distribution, and your tools are older than this, you will need to
15680 upgrade. Closes ticket 17732.
15682 o Major bugfixes (security, pointers):
15683 - Avoid a difficult-to-trigger heap corruption attack when extending
15684 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
15685 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
15686 Reported by Guido Vranken.
15688 o Major bugfixes (bridges, pluggable transports):
15689 - Modify the check for OR connections to private addresses. Allow
15690 bridges on private addresses, including pluggable transports that
15691 ignore the (potentially private) address in the bridge line. Fixes
15692 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
15694 o Major bugfixes (compilation):
15695 - Repair hardened builds under the clang compiler. Previously, our
15696 use of _FORTIFY_SOURCE would conflict with clang's address
15697 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
15699 o Major bugfixes (crash on shutdown):
15700 - Correctly handle detaching circuits from muxes when shutting down.
15701 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
15702 - Fix an assert-on-exit bug related to counting memory usage in
15703 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
15705 o Major bugfixes (crash on startup):
15706 - Fix a segfault during startup: If a Unix domain socket was
15707 configured as listener (such as a ControlSocket or a SocksPort
15708 "unix:" socket), and tor was started as root but not configured to
15709 switch to another user, tor would segfault while trying to string
15710 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
15713 o Major bugfixes (dns proxy mode, crash):
15714 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
15715 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
15717 o Major bugfixes (relays, bridge clients):
15718 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
15719 bridge clients use the address configured in the bridge line.
15720 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
15723 o Major bugfixes (voting):
15724 - Actually enable support for authorities to match routers by their
15725 Ed25519 identities. Previously, the code had been written, but
15726 some debugging code that had accidentally been left in the
15727 codebase made it stay turned off. Fixes bug 17702; bugfix
15729 - When collating votes by Ed25519 identities, authorities now
15730 include a "NoEdConsensus" flag if the ed25519 value (or lack
15731 thereof) for a server does not reflect the majority consensus.
15732 Related to bug 17668; bugfix on 0.2.7.2-alpha.
15733 - When generating a vote with keypinning disabled, never include two
15734 entries for the same ed25519 identity. This bug was causing
15735 authorities to generate votes that they could not parse when a
15736 router violated key pinning by changing its RSA identity but
15737 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
15738 18318. Bugfix on 0.2.7.2-alpha.
15740 o Minor features (security, win32):
15741 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
15742 attack. Fixes bug 18123; bugfix on all tor versions. Patch
15745 o Minor features (bug-resistance):
15746 - Make Tor survive errors involving connections without a
15747 corresponding event object. Previously we'd fail with an
15748 assertion; now we produce a log message. Related to bug 16248.
15750 o Minor features (build):
15751 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
15752 as having possible IPFW support. Closes ticket 18448. Patch from
15753 Steven Chamberlain.
15755 o Minor features (code hardening):
15756 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
15757 level code, to harden against accidental failures to NUL-
15758 terminate. Part of ticket 17852. Patch from jsturgix. Found
15761 o Minor features (crypto):
15762 - Validate the hard-coded Diffie-Hellman parameters and ensure that
15763 p is a safe prime, and g is a suitable generator. Closes
15766 o Minor features (geoip):
15767 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
15770 o Minor features (hidden service directory):
15771 - Streamline relay-side hsdir handling: when relays consider whether
15772 to accept an uploaded hidden service descriptor, they no longer
15773 check whether they are one of the relays in the network that is
15774 "supposed" to handle that descriptor. Implements ticket 18332.
15776 o Minor features (IPv6):
15777 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
15778 to 1, tor prefers IPv6 directory addresses.
15779 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
15780 avoids using IPv4 for client OR and directory connections.
15781 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
15782 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
15783 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
15785 o Minor features (linux seccomp2 sandbox):
15786 - Reject attempts to change our Address with "Sandbox 1" enabled.
15787 Changing Address with Sandbox turned on would never actually work,
15788 but previously it would fail in strange and confusing ways. Found
15789 while fixing 18548.
15791 o Minor features (robustness):
15792 - Exit immediately with an error message if the code attempts to use
15793 Libevent without having initialized it. This should resolve some
15794 frequently-made mistakes in our unit tests. Closes ticket 18241.
15796 o Minor features (unix domain sockets):
15797 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
15798 Unix domain sockets without checking the permissions on the parent
15799 directory. (Tor checks permissions by default because some
15800 operating systems only check permissions on the parent directory.
15801 However, some operating systems do look at permissions on the
15802 socket, and tor's default check is unneeded.) Closes ticket 18458.
15805 o Minor bugfixes (exit policies, security):
15806 - Refresh an exit relay's exit policy when interface addresses
15807 change. Previously, tor only refreshed the exit policy when the
15808 configured external address changed. Fixes bug 18208; bugfix on
15809 0.2.7.3-rc. Patch by teor.
15811 o Minor bugfixes (security, hidden services):
15812 - Prevent hidden services connecting to client-supplied rendezvous
15813 addresses that are reserved as internal or multicast. Fixes bug
15814 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
15816 o Minor bugfixes (build):
15817 - Do not link the unit tests against both the testing and non-
15818 testing versions of the static libraries. Fixes bug 18490; bugfix
15820 - Avoid spurious failures from configure files related to calling
15821 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
15822 0.2.0.1-alpha. Patch from "cypherpunks".
15823 - Silence spurious clang-scan warnings in the ed25519_donna code by
15824 explicitly initializing some objects. Fixes bug 18384; bugfix on
15825 0.2.7.2-alpha. Patch by teor.
15827 o Minor bugfixes (client, bootstrap):
15828 - Count receipt of new microdescriptors as progress towards
15829 bootstrapping. Previously, with EntryNodes set, Tor might not
15830 successfully repopulate the guard set on bootstrapping. Fixes bug
15831 16825; bugfix on 0.2.3.1-alpha.
15833 o Minor bugfixes (code correctness):
15834 - Update to the latest version of Trunnel, which tries harder to
15835 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
15836 by clang address sanitizer. Fixes bug 18373; bugfix
15839 o Minor bugfixes (configuration):
15840 - Fix a tiny memory leak when parsing a port configuration ending in
15841 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
15843 o Minor bugfixes (containers):
15844 - If we somehow attempt to construct a heap with more than
15845 1073741822 elements, avoid an integer overflow when maintaining
15846 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
15848 o Minor bugfixes (correctness):
15849 - Fix a bad memory handling bug that would occur if we had queued a
15850 cell on a channel's incoming queue. Fortunately, we can't actually
15851 queue a cell like that as our code is constructed today, but it's
15852 best to avoid this kind of error, even if there isn't any code
15853 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
15855 o Minor bugfixes (directory):
15856 - When generating a URL for a directory server on an IPv6 address,
15857 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
15858 on 0.2.3.9-alpha. Patch from Malek.
15860 o Minor bugfixes (fallback directory mirrors):
15861 - When requesting extrainfo descriptors from a trusted directory
15862 server, check whether it is an authority or a fallback directory
15863 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
15864 0.2.4.7-alpha. Reported by atagar, patch by teor.
15866 o Minor bugfixes (hidden service, client):
15867 - Handle the case where the user makes several fast consecutive
15868 requests to the same .onion address. Previously, the first six
15869 requests would each trigger a descriptor fetch, each picking a
15870 directory (there are 6 overall) and the seventh one would fail
15871 because no directories were left, thereby triggering a close on
15872 all current directory connections asking for the hidden service.
15873 The solution here is to not close the connections if we have
15874 pending directory fetches. Fixes bug 15937; bugfix
15877 o Minor bugfixes (hidden service, control port):
15878 - Add the onion address to the HS_DESC event for the UPLOADED action
15879 both on success or failure. It was previously hardcoded with
15880 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
15882 o Minor bugfixes (hidden service, directory):
15883 - Bridges now refuse "rendezvous2" (hidden service descriptor)
15884 publish attempts. Suggested by ticket 18332.
15886 o Minor bugfixes (linux seccomp2 sandbox):
15887 - Allow the setrlimit syscall, and the prlimit and prlimit64
15888 syscalls, which some libc implementations use under the hood.
15889 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
15890 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
15891 enabled and no DNS resolvers configured. This should help TAILS
15892 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
15893 - Fix the sandbox's interoperability with unix domain sockets under
15894 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
15896 o Minor bugfixes (logging):
15897 - When logging information about an unparsable networkstatus vote or
15898 consensus, do not say "vote" when we mean consensus. Fixes bug
15899 18368; bugfix on 0.2.0.8-alpha.
15900 - Scrub service name in "unrecognized service ID" log messages.
15901 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
15902 - Downgrade logs and backtraces about IP versions to info-level.
15903 Only log backtraces once each time tor runs. Assists in diagnosing
15904 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
15905 Christian, patch by teor.
15907 o Minor bugfixes (memory safety):
15908 - Avoid freeing an uninitialized pointer when opening a socket fails
15909 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
15910 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
15912 - Correctly duplicate addresses in get_interface_address6_list().
15913 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
15914 patch by "cypherpunks".
15915 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
15917 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
15918 18672; bugfix on 0.2.5.1-alpha.
15920 o Minor bugfixes (private directory):
15921 - Prevent a race condition when creating private directories. Fixes
15922 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
15923 Patch from jsturgix. Found with Flawfinder.
15925 o Minor bugfixes (test networks, IPv6):
15926 - Allow internal IPv6 addresses in descriptors in test networks.
15927 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
15930 o Minor bugfixes (testing):
15931 - We no longer disable assertions in the unit tests when coverage is
15932 enabled. Instead, we require you to say --disable-asserts-in-tests
15933 to the configure script if you need assertions disabled in the
15934 unit tests (for example, if you want to perform branch coverage).
15935 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
15937 o Minor bugfixes (time parsing):
15938 - Avoid overflow in tor_timegm when parsing dates in and after 2038
15939 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
15940 0.0.2pre14. Patch by teor.
15942 o Minor bugfixes (tor-gencert):
15943 - Correctly handle the case where an authority operator enters a
15944 passphrase but sends an EOF before sending a newline. Fixes bug
15945 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
15947 o Code simplification and refactoring:
15948 - Quote all the string interpolations in configure.ac -- even those
15949 which we are pretty sure can't contain spaces. Closes ticket
15950 17744. Patch from zerosion.
15951 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
15952 inplace, so there's no need to have a separate implementation for
15953 the non-inplace code. Closes ticket 18258. Patch from Malek.
15954 - Simplify return types for some crypto functions that can't
15955 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
15958 - Change build messages to refer to "Fedora" instead of "Fedora
15959 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
15960 Patches from "icanhasaccount" and "cypherpunks".
15962 o Removed features:
15963 - We no longer maintain an internal freelist in memarea.c.
15964 Allocators should be good enough to make this code unnecessary,
15965 and it's doubtful that it ever had any performance benefit.
15968 - Fix several warnings from clang's address sanitizer produced in
15970 - Treat backtrace test failures as expected on FreeBSD until we
15971 solve bug 17808. Closes ticket 18204.
15974 Changes in version 0.2.8.1-alpha - 2016-02-04
15975 Tor 0.2.8.1-alpha is the first alpha release in its series. It
15976 includes numerous small features and bugfixes against previous Tor
15977 versions, and numerous small infrastructure improvements. The most
15978 notable features are a set of improvements to the directory subsystem.
15980 o Major features (security, Linux):
15981 - When Tor starts as root on Linux and is told to switch user ID, it
15982 can now retain the capability to bind to low ports. By default,
15983 Tor will do this only when it's switching user ID and some low
15984 ports have been configured. You can change this behavior with the
15985 new option KeepBindCapabilities. Closes ticket 8195.
15987 o Major features (directory system):
15988 - When bootstrapping multiple consensus downloads at a time, use the
15989 first one that starts downloading, and close the rest. This
15990 reduces failures when authorities or fallback directories are slow
15991 or down. Together with the code for feature 15775, this feature
15992 should reduces failures due to fallback churn. Implements ticket
15993 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
15994 "mikeperry" and "teor".
15995 - Include a trial list of 21 default fallback directories, generated
15996 in January 2016, based on an opt-in survey of suitable relays.
15997 Doing this should make clients bootstrap more quickly and reliably,
15998 and reduce the load on the directory authorities. Closes ticket
15999 15775. Patch by "teor".
16000 Candidates identified using an OnionOO script by "weasel", "teor",
16001 "gsathya", and "karsten".
16002 - Previously only relays that explicitly opened a directory port
16003 (DirPort) accepted directory requests from clients. Now all
16004 relays, with and without a DirPort, accept and serve tunneled
16005 directory requests that they receive through their ORPort. You can
16006 disable this behavior using the new DirCache option. Closes
16009 o Major key updates:
16010 - Update the V3 identity key for the dannenberg directory authority:
16011 it was changed on 18 November 2015. Closes task 17906. Patch
16014 o Minor features (security, clock):
16015 - Warn when the system clock appears to move back in time (when the
16016 state file was last written in the future). Tor doesn't know that
16017 consensuses have expired if the clock is in the past. Patch by
16018 "teor". Implements ticket 17188.
16020 o Minor features (security, exit policies):
16021 - ExitPolicyRejectPrivate now rejects more private addresses by
16022 default. Specifically, it now rejects the relay's outbound bind
16023 addresses (if configured), and the relay's configured port
16024 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
16025 0.2.0.11-alpha. Patch by "teor".
16027 o Minor features (security, memory erasure):
16028 - Set the unused entries in a smartlist to NULL. This helped catch
16029 a (harmless) bug, and shouldn't affect performance too much.
16030 Implements ticket 17026.
16031 - Use SecureMemoryWipe() function to securely clean memory on
16032 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
16033 Implements feature 17986.
16034 - Use explicit_bzero or memset_s when present. Previously, we'd use
16035 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
16036 from <logan@hackers.mu> and <selven@hackers.mu>.
16037 - Make memwipe() do nothing when passed a NULL pointer or buffer of
16038 zero size. Check size argument to memwipe() for underflow. Fixes
16039 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
16042 o Minor features (security, RNG):
16043 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
16044 positively are not allowed to fail. Previously we depended on
16045 internal details of OpenSSL's behavior. Closes ticket 17686.
16046 - Never use the system entropy output directly for anything besides
16047 seeding the PRNG. When we want to generate important keys, instead
16048 of using system entropy directly, we now hash it with the PRNG
16049 stream. This may help resist certain attacks based on broken OS
16050 entropy implementations. Closes part of ticket 17694.
16051 - Use modern system calls (like getentropy() or getrandom()) to
16052 generate strong entropy on platforms that have them. Closes
16055 o Minor features (accounting):
16056 - Added two modes to the AccountingRule option: One for limiting
16057 only the number of bytes sent ("AccountingRule out"), and one for
16058 limiting only the number of bytes received ("AccountingRule in").
16059 Closes ticket 15989; patch from "unixninja92".
16061 o Minor features (build):
16062 - Since our build process now uses "make distcheck", we no longer
16063 force "make dist" to depend on "make check". Closes ticket 17893;
16064 patch from "cypherpunks."
16065 - Tor now builds successfully with the recent OpenSSL 1.1
16066 development branch, and with the latest LibreSSL. Closes tickets
16067 17549, 17921, and 17984.
16069 o Minor features (controller):
16070 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
16071 tickets 16774 and 17817. Patch by George Tankersley.
16072 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
16073 service descriptor from a service's local hidden service
16074 descriptor cache. Closes ticket 14846.
16075 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
16076 controllers can examine the the reject rules added by
16077 ExitPolicyRejectPrivate. This makes it easier for stem to display
16080 o Minor features (crypto):
16081 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
16083 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
16084 - When allocating a digest state object, allocate no more space than
16085 we actually need. Previously, we would allocate as much space as
16086 the state for the largest algorithm would need. This change saves
16087 up to 672 bytes per circuit. Closes ticket 17796.
16088 - Improve performance when hashing non-multiple of 8 sized buffers,
16089 based on Andrew Moon's public domain SipHash-2-4 implementation.
16090 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
16092 o Minor features (directory downloads):
16093 - Wait for busy authorities and fallback directories to become non-
16094 busy when bootstrapping. (A similar change was made in 6c443e987d
16095 for directory caches chosen from the consensus.) Closes ticket
16096 17864; patch by "teor".
16097 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
16098 directory mirrors. The default is 1; set it to 0 to disable
16099 fallbacks. Implements ticket 17576. Patch by "teor".
16101 o Minor features (geoip):
16102 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
16105 o Minor features (IPv6):
16106 - Add an argument 'ipv6=address:orport' to the DirAuthority and
16107 FallbackDir torrc options, to specify an IPv6 address for an
16108 authority or fallback directory. Add hard-coded ipv6 addresses for
16109 directory authorities that have them. Closes ticket 17327; patch
16110 from Nick Mathewson and "teor".
16111 - Add address policy assume_action support for IPv6 addresses.
16112 - Limit IPv6 mask bits to 128.
16113 - Warn when comparing against an AF_UNSPEC address in a policy, it's
16114 almost always a bug. Closes ticket 17863; patch by "teor".
16115 - Allow users to configure directory authorities and fallback
16116 directory servers with IPv6 addresses and ORPorts. Resolves
16118 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
16119 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
16120 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
16121 17638; bugfix on 0.0.2pre8. Patch by "teor".
16123 o Minor features (logging):
16124 - When logging to syslog, allow a tag to be added to the syslog
16125 identity (the string prepended to every log message). The tag can
16126 be configured with SyslogIdentityTag and defaults to none. Setting
16127 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
16130 o Minor features (portability):
16131 - Use timingsafe_memcmp() where available. Closes ticket 17944;
16132 patch from <logan@hackers.mu>.
16134 o Minor features (relay, address discovery):
16135 - Add a family argument to get_interface_addresses_raw() and
16136 subfunctions to make network interface address interogation more
16137 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
16138 types of interfaces from the operating system. Resolves
16140 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
16141 fails to enumerate interface addresses using the platform-specific
16142 API, have it rely on the UDP socket fallback technique to try and
16143 find out what IP addresses (both IPv4 and IPv6) our machine has.
16144 Resolves ticket 17951.
16146 o Minor features (replay cache):
16147 - The replay cache now uses SHA256 instead of SHA1. Implements
16148 feature 8961. Patch by "teor", issue reported by "rransom".
16150 o Minor features (unix file permissions):
16151 - Defer creation of Unix sockets until after setuid. This avoids
16152 needing CAP_CHOWN and CAP_FOWNER when using systemd's
16153 CapabilityBoundingSet, or chown and fowner when using SELinux.
16154 Implements part of ticket 17562. Patch from Jamie Nguyen.
16155 - If any directory created by Tor is marked as group readable, the
16156 filesystem group is allowed to be either the default GID or the
16157 root user. Allowing root to read the DataDirectory prevents the
16158 need for CAP_READ_SEARCH when using systemd's
16159 CapabilityBoundingSet, or dac_read_search when using SELinux.
16160 Implements part of ticket 17562. Patch from Jamie Nguyen.
16161 - Introduce a new DataDirectoryGroupReadable option. If it is set to
16162 1, the DataDirectory will be made readable by the default GID.
16163 Implements part of ticket 17562. Patch from Jamie Nguyen.
16165 o Minor bugfixes (accounting):
16166 - The max bandwidth when using 'AccountRule sum' is now correctly
16167 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
16168 from "unixninja92".
16170 o Minor bugfixes (code correctness):
16171 - When closing an entry connection, generate a warning if we should
16172 have sent an end cell for it but we haven't. Fixes bug 17876;
16173 bugfix on 0.2.3.2-alpha.
16174 - Assert that allocated memory held by the reputation code is freed
16175 according to its internal counters. Fixes bug 17753; bugfix
16177 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
16180 o Minor bugfixes (compilation):
16181 - Mark all object files that include micro-revision.i as depending
16182 on it, so as to make parallel builds more reliable. Fixes bug
16183 17826; bugfix on 0.2.5.1-alpha.
16184 - Don't try to use the pthread_condattr_setclock() function unless
16185 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
16186 17819; bugfix on 0.2.6.3-alpha.
16187 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
16189 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
16190 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
16191 - Fix search for libevent libraries on OpenBSD (and other systems
16192 that install libevent 1 and libevent 2 in parallel). Fixes bug
16193 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
16194 - Isolate environment variables meant for tests from the rest of the
16195 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
16196 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
16198 - Remove config.log only from make distclean, not from make clean.
16199 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
16201 o Minor bugfixes (crypto):
16202 - Check the return value of HMAC() and assert on failure. Fixes bug
16203 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
16205 o Minor bugfixes (fallback directories):
16206 - Mark fallbacks as "too busy" when they return a 503 response,
16207 rather than just marking authorities. Fixes bug 17572; bugfix on
16208 0.2.4.7-alpha. Patch by "teor".
16210 o Minor bugfixes (IPv6):
16211 - Update the limits in max_dl_per_request for IPv6 address length.
16212 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
16214 o Minor bugfixes (linux seccomp2 sandbox):
16215 - Fix a crash when using offline master ed25519 keys with the Linux
16216 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
16218 o Minor bugfixes (logging):
16219 - In log messages that include a function name, use __FUNCTION__
16220 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
16221 with clang __PRETTY_FUNCTION__ has extra information we don't
16222 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
16224 - Remove needless quotes from a log message about unparseable
16225 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
16227 o Minor bugfixes (portability):
16228 - Remove an #endif from configure.ac so that we correctly detect the
16229 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
16232 o Minor bugfixes (relays):
16233 - Check that both the ORPort and DirPort (if present) are reachable
16234 before publishing a relay descriptor. Otherwise, relays publish a
16235 descriptor with DirPort 0 when the DirPort reachability test takes
16236 longer than the ORPort reachability test. Fixes bug 18050; bugfix
16237 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
16239 o Minor bugfixes (relays, hidden services):
16240 - Refuse connection requests to private OR addresses unless
16241 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
16242 then refuse to send any cells to a private address. Fixes bugs
16243 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
16245 o Minor bugfixes (safe logging):
16246 - When logging a malformed hostname received through socks4, scrub
16247 it if SafeLogging says we should. Fixes bug 17419; bugfix
16250 o Minor bugfixes (statistics code):
16251 - Consistently check for overflow in round_*_to_next_multiple_of
16252 functions, and add unit tests with additional and maximal values.
16253 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
16254 - Handle edge cases in the laplace functions: avoid division by
16255 zero, avoid taking the log of zero, and silence clang type
16256 conversion warnings using round and trunc. Add unit tests for edge
16257 cases with maximal values. Fixes part of bug 13192; bugfix
16260 o Minor bugfixes (testing):
16261 - The test for log_heartbeat was incorrectly failing in timezones
16262 with non-integer offsets. Instead of comparing the end of the time
16263 string against a constant, compare it to the output of
16264 format_local_iso_time when given the correct input. Fixes bug
16265 18039; bugfix on 0.2.5.4-alpha.
16266 - Make unit tests pass on IPv6-only systems, and systems without
16267 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
16268 bugfix on 0.2.7.3-rc. Patch by "teor".
16269 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
16271 - Check the full results of SHA256 and SHA512 digests in the unit
16272 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
16274 o Code simplification and refactoring:
16275 - Move logging of redundant policy entries in
16276 policies_parse_exit_policy_internal into its own function. Closes
16277 ticket 17608; patch from "juce".
16278 - Extract the more complicated parts of circuit_mark_for_close()
16279 into a new function that we run periodically before circuits are
16280 freed. This change removes more than half of the functions
16281 currently in the "blob". Closes ticket 17218.
16282 - Clean up a little duplicated code in
16283 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
16285 - Decouple the list of streams waiting to be attached to circuits
16286 from the overall connection list. This change makes it possible to
16287 attach streams quickly while simplifying Tor's callgraph and
16288 avoiding O(N) scans of the entire connection list. Closes
16290 - When a direct directory request fails immediately on launch,
16291 instead of relaunching that request from inside the code that
16292 launches it, instead mark the connection for teardown. This change
16293 simplifies Tor's callback and prevents the directory-request
16294 launching code from invoking itself recursively. Closes
16296 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
16297 use them. Closes ticket 17926.
16300 - Add a description of the correct use of the '--keygen' command-
16301 line option. Closes ticket 17583; based on text by 's7r'.
16302 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
16303 - Explain actual minima for BandwidthRate. Closes ticket 16382.
16304 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
16305 - Mention torspec URL in the manpage and point the reader to it
16306 whenever we mention a document that belongs in torspce. Fixes
16309 o Removed features:
16310 - Remove client-side support for connecting to Tor relays running
16311 versions of Tor before 0.2.3.6-alpha. These relays didn't support
16312 the v3 TLS handshake protocol, and are no longer allowed on the
16313 Tor network. Implements the client side of ticket 11150. Based on
16314 patches by Tom van der Woerdt.
16317 - Add unit tests to check for common RNG failure modes, such as
16318 returning all zeroes, identical values, or incrementing values
16319 (OpenSSL's rand_predictable feature). Patch by "teor".
16320 - Log more information when the backtrace tests fail. Closes ticket
16321 17892. Patch from "cypherpunks."
16322 - Always test both ed25519 backends, so that we can be sure that our
16323 batch-open replacement code works. Part of ticket 16794.
16324 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
16325 portion of ticket 16831.
16326 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
16327 util_format.c, directory.c, and options_validate.c. Closes tickets
16328 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
16330 - Unit tests for directory_handle_command_get. Closes ticket 17004.
16331 Patch from Reinaldo de Souza Jr.
16334 Changes in version 0.2.7.6 - 2015-12-10
16335 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
16336 well as a minor bug in hidden service reliability.
16338 o Major bugfixes (guard selection):
16339 - Actually look at the Guard flag when selecting a new directory
16340 guard. When we implemented the directory guard design, we
16341 accidentally started treating all relays as if they have the Guard
16342 flag during guard selection, leading to weaker anonymity and worse
16343 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
16346 o Minor features (geoip):
16347 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
16350 o Minor bugfixes (compilation):
16351 - When checking for net/pfvar.h, include netinet/in.h if possible.
16352 This fixes transparent proxy detection on OpenBSD. Fixes bug
16353 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
16354 - Fix a compilation warning with Clang 3.6: Do not check the
16355 presence of an address which can never be NULL. Fixes bug 17781.
16357 o Minor bugfixes (correctness):
16358 - When displaying an IPv6 exit policy, include the mask bits
16359 correctly even when the number is greater than 31. Fixes bug
16360 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
16361 - The wrong list was used when looking up expired intro points in a
16362 rend service object, causing what we think could be reachability
16363 issues for hidden services, and triggering a BUG log. Fixes bug
16364 16702; bugfix on 0.2.7.2-alpha.
16365 - Fix undefined behavior in the tor_cert_checksig function. Fixes
16366 bug 17722; bugfix on 0.2.7.2-alpha.
16369 Changes in version 0.2.7.5 - 2015-11-20
16370 The Tor 0.2.7 release series is dedicated to the memory of Tor user
16371 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
16372 tirelessly to advocate human rights regardless of national borders,
16373 and oppose the encroachments of mass surveillance. He opposed national
16374 exceptionalism, he brought clarity to legal and policy debates, he
16375 understood and predicted the impact of mass surveillance on the world,
16376 and he laid the groundwork for resisting it. While serving on the Tor
16377 Project's board of directors, he brought us his uncompromising focus
16378 on technical excellence in the service of humankind. Caspar was an
16379 inimitable force for good and a wonderful friend. He was kind,
16380 humorous, generous, gallant, and believed we should protect one
16381 another without exception. We honor him here for his ideals, his
16382 efforts, and his accomplishments. Please honor his memory with works
16383 that would make him proud.
16385 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
16387 The 0.2.7 series adds a more secure identity key type for relays,
16388 improves cryptography performance, resolves several longstanding
16389 hidden-service performance issues, improves controller support for
16390 hidden services, and includes small bugfixes and performance
16391 improvements throughout the program. This release series also includes
16392 more tests than before, and significant simplifications to which parts
16393 of Tor invoke which others.
16395 (This release contains no code changes since 0.2.7.4-rc.)
16398 Changes in version 0.2.7.4-rc - 2015-10-21
16399 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
16400 fixes some important memory leaks, and a scary-looking (but mostly
16401 harmless in practice) invalid-read bug. It also has a few small
16402 bugfixes, notably fixes for compilation and portability on different
16403 platforms. If no further significant bounds are found, the next
16404 release will the the official stable release.
16406 o Major bugfixes (security, correctness):
16407 - Fix an error that could cause us to read 4 bytes before the
16408 beginning of an openssl string. This bug could be used to cause
16409 Tor to crash on systems with unusual malloc implementations, or
16410 systems with unusual hardening installed. Fixes bug 17404; bugfix
16413 o Major bugfixes (correctness):
16414 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
16415 bug 17401; bugfix on 0.2.7.3-rc.
16417 o Major bugfixes (memory leaks):
16418 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
16419 17398; bugfix on 0.2.6.1-alpha.
16420 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
16421 17402; bugfix on 0.2.7.3-rc.
16422 - Fix a memory leak when reading an expired signing key from disk.
16423 Fixes bug 17403; bugfix on 0.2.7.2-rc.
16425 o Minor features (geoIP):
16426 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
16429 o Minor bugfixes (compilation):
16430 - Repair compilation with the most recent (unreleased, alpha)
16431 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
16432 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
16433 17251; bugfix on 0.2.7.2-alpha.
16434 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
16435 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
16437 o Minor bugfixes (portability):
16438 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
16439 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
16442 o Minor bugfixes (sandbox):
16443 - Add the "hidserv-stats" filename to our sandbox filter for the
16444 HiddenServiceStatistics option to work properly. Fixes bug 17354;
16445 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
16447 o Minor bugfixes (testing):
16448 - Add unit tests for get_interface_address* failure cases. Fixes bug
16449 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
16450 - Fix breakage when running 'make check' with BSD make. Fixes bug
16451 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
16452 - Make the get_ifaddrs_* unit tests more tolerant of different
16453 network configurations. (Don't assume every test box has an IPv4
16454 address, and don't assume every test box has a non-localhost
16455 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
16456 - Skip backtrace tests when backtrace support is not compiled in.
16457 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
16461 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
16462 - Note that HiddenServicePorts can take a unix domain socket. Closes
16466 Changes in version 0.2.7.3-rc - 2015-09-25
16467 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
16468 contains numerous usability fixes for Ed25519 keys, safeguards against
16469 several misconfiguration problems, significant simplifications to
16470 Tor's callgraph, and numerous bugfixes and small features.
16472 This is the most tested release of Tor to date. The unit tests cover
16473 39.40% of the code, and the integration tests (accessible with "make
16474 test-full-online", requiring stem and chutney and a network
16475 connection) raise the coverage to 64.49%.
16477 o Major features (security, hidden services):
16478 - Hidden services, if using the EntryNodes option, are required to
16479 use more than one EntryNode, in order to avoid a guard discovery
16480 attack. (This would only affect people who had configured hidden
16481 services and manually specified the EntryNodes option with a
16482 single entry-node. The impact was that it would be easy to
16483 remotely identify the guard node used by such a hidden service.
16484 See ticket for more information.) Fixes ticket 14917.
16486 o Major features (Ed25519 keys, keypinning):
16487 - The key-pinning option on directory authorities is now advisory-
16488 only by default. In a future version, or when the AuthDirPinKeys
16489 option is set, pins are enforced again. Disabling key-pinning
16490 seemed like a good idea so that we can survive the fallout of any
16491 usability problems associated with Ed25519 keys. Closes
16494 o Major features (Ed25519 performance):
16495 - Improve the speed of Ed25519 operations and Curve25519 keypair
16496 generation when built targeting 32 bit x86 platforms with SSE2
16497 available. Implements ticket 16535.
16498 - Improve the runtime speed of Ed25519 signature verification by
16499 using Ed25519-donna's batch verification support. Implements
16502 o Major features (performance testing):
16503 - The test-network.sh script now supports performance testing.
16504 Requires corresponding chutney performance testing changes. Patch
16505 by "teor". Closes ticket 14175.
16507 o Major features (relay, Ed25519):
16508 - Significant usability improvements for Ed25519 key management. Log
16509 messages are better, and the code can recover from far more
16510 failure conditions. Thanks to "s7r" for reporting and diagnosing
16512 - Add a new OfflineMasterKey option to tell Tor never to try loading
16513 or generating a secret Ed25519 identity key. You can use this in
16514 combination with tor --keygen to manage offline and/or encrypted
16515 Ed25519 keys. Implements ticket 16944.
16516 - Add a --newpass option to allow changing or removing the
16517 passphrase of an encrypted key with tor --keygen. Implements part
16519 - On receiving a HUP signal, check to see whether the Ed25519
16520 signing key has changed, and reload it if so. Closes ticket 16790.
16522 o Major bugfixes (relay, Ed25519):
16523 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
16524 0.2.7.2-alpha. Reported by "s7r".
16525 - Improve handling of expired signing keys with offline master keys.
16526 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
16528 o Minor features (client-side privacy):
16529 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
16530 lifespan when IsolateSOCKSAuth and streams with SOCKS
16531 authentication are attached to the circuit. This allows
16532 applications like TorBrowser to manage circuit lifetime on their
16533 own. Implements feature 15482.
16534 - When logging malformed hostnames from SOCKS5 requests, respect
16535 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
16537 o Minor features (compilation):
16538 - Give a warning as early as possible when trying to build with an
16539 unsupported OpenSSL version. Closes ticket 16901.
16540 - Fail during configure if we're trying to build against an OpenSSL
16541 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
16542 which started requiring ECC.
16544 o Minor features (geoip):
16545 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
16548 o Minor features (hidden services):
16549 - Relays need to have the Fast flag to get the HSDir flag. As this
16550 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
16551 drop. This change should make some attacks against the hidden
16552 service directory system harder. Fixes ticket 15963.
16553 - Turn on hidden service statistics collection by setting the torrc
16554 option HiddenServiceStatistics to "1" by default. (This keeps
16555 track only of the fraction of traffic used by hidden services, and
16556 the total number of hidden services in existence.) Closes
16558 - Client now uses an introduction point failure cache to know when
16559 to fetch or keep a descriptor in their cache. Previously, failures
16560 were recorded implicitly, but not explicitly remembered. Closes
16563 o Minor features (testing, authorities, documentation):
16564 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
16565 explicitly manage consensus flags in testing networks. Patch by
16566 "robgjansen", modified by "teor". Implements part of ticket 14882.
16568 o Minor bugfixes (security, exit policies):
16569 - ExitPolicyRejectPrivate now also rejects the relay's published
16570 IPv6 address (if any), and any publicly routable IPv4 or IPv6
16571 addresses on any local interfaces. ticket 17027. Patch by "teor".
16572 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
16574 o Minor bug fixes (torrc exit policies):
16575 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
16576 produce IPv6 wildcard addresses. Previously they would produce
16577 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
16578 of bug 16069; bugfix on 0.2.4.7-alpha.
16579 - When parsing torrc ExitPolicies, we now warn for a number of cases
16580 where the user's intent is likely to differ from Tor's actual
16581 behavior. These include: using an IPv4 address with an accept6 or
16582 reject6 line; using "private" on an accept6 or reject6 line; and
16583 including any ExitPolicy lines after accept *:* or reject *:*.
16584 Related to ticket 16069.
16585 - When parsing torrc ExitPolicies, we now issue an info-level
16586 message when expanding an "accept/reject *" line to include both
16587 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
16588 - In each instance above, usage advice is provided to avoid the
16589 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
16590 16069; bugfix on 0.2.4.7-alpha.
16592 o Minor bugfixes (authority):
16593 - Don't assign "HSDir" to a router if it isn't Valid and Running.
16594 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
16595 - Downgrade log messages about Ed25519 key issues if they are in old
16596 cached router descriptors. Fixes part of bug 16286; bugfix
16598 - When we find an Ed25519 key issue in a cached descriptor, stop
16599 saying the descriptor was just "uploaded". Fixes another part of
16600 bug 16286; bugfix on 0.2.7.2-alpha.
16602 o Minor bugfixes (control port):
16603 - Repair a warning and a spurious result when getting the maximum
16604 number of file descriptors from the controller. Fixes bug 16697;
16605 bugfix on 0.2.7.2-alpha.
16607 o Minor bugfixes (correctness):
16608 - When calling channel_free_list(), avoid calling smartlist_remove()
16609 while inside a FOREACH loop. This partially reverts commit
16610 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
16611 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
16613 o Minor bugfixes (documentation):
16614 - Advise users on how to configure separate IPv4 and IPv6 exit
16615 policies in the manpage and sample torrcs. Related to ticket 16069.
16616 - Fix the usage message of tor-resolve(1) so that it no longer lists
16617 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
16618 - Fix an error in the manual page and comments for
16619 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
16620 required "ORPort connectivity". While this is true, it is in no
16621 way unique to the HSDir flag. Of all the flags, only HSDirs need a
16622 DirPort configured in order for the authorities to assign that
16623 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
16626 o Minor bugfixes (Ed25519):
16627 - Fix a memory leak when reading router descriptors with expired
16628 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
16630 o Minor bugfixes (linux seccomp2 sandbox):
16631 - Allow bridge authorities to run correctly under the seccomp2
16632 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
16633 - Allow routers with ed25519 keys to run correctly under the
16634 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
16636 o Minor bugfixes (open file limit):
16637 - Fix set_max_file_descriptors() to set by default the max open file
16638 limit to the current limit when setrlimit() fails. Fixes bug
16639 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
16641 o Minor bugfixes (portability):
16642 - Try harder to normalize the exit status of the Tor process to the
16643 standard-provided range. Fixes bug 16975; bugfix on every version
16645 - Check correctly for Windows socket errors in the workqueue
16646 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
16647 - Fix the behavior of crypto_rand_time_range() when told to consider
16648 times before 1970. (These times were possible when running in a
16649 simulated network environment where time()'s output starts at
16650 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
16651 - Restore correct operation of TLS client-cipher detection on
16652 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
16654 o Minor bugfixes (relay):
16655 - Ensure that worker threads actually exit when a fatal error or
16656 shutdown is indicated. This fix doesn't currently affect the
16657 behavior of Tor, because Tor workers never indicates fatal error
16658 or shutdown except in the unit tests. Fixes bug 16868; bugfix
16660 - Unblock threads before releasing the work queue mutex to ensure
16661 predictable scheduling behavior. Fixes bug 16644; bugfix
16664 o Code simplification and refactoring:
16665 - Change the function that's called when we need to retry all
16666 downloads so that it only reschedules the downloads to happen
16667 immediately, rather than launching them all at once itself. This
16668 further simplifies Tor's callgraph.
16669 - Move some format-parsing functions out of crypto.c and
16670 crypto_curve25519.c into crypto_format.c and/or util_format.c.
16671 - Move the client-only parts of init_keys() into a separate
16672 function. Closes ticket 16763.
16673 - Simplify the microdesc_free() implementation so that it no longer
16674 appears (to code analysis tools) to potentially invoke a huge
16675 suite of other microdesc functions.
16676 - Simply the control graph further by deferring the inner body of
16677 directory_all_unreachable() into a callback. Closes ticket 16762.
16678 - Treat the loss of an owning controller as equivalent to a SIGTERM
16679 signal. This removes a tiny amount of duplicated code, and
16680 simplifies our callgraph. Closes ticket 16788.
16681 - When generating an event to send to the controller, we no longer
16682 put the event over the network immediately. Instead, we queue
16683 these events, and use a Libevent callback to deliver them. This
16684 change simplifies Tor's callgraph by reducing the number of
16685 functions from which all other Tor functions are reachable. Closes
16687 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
16688 that try to scan or compile every file on Unix won't decide that
16690 - Remove the unused "nulterminate" argument from buf_pullup().
16693 - Recommend a 40 GB example AccountingMax in torrc.sample rather
16694 than a 4 GB max. Closes ticket 16742.
16695 - Include the TUNING document in our source tarball. It is referred
16696 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
16700 - The internal pure-C tor-fw-helper tool is now removed from the Tor
16701 distribution, in favor of the pure-Go clone available from
16702 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
16703 used by the C tor-fw-helper are not, in our opinion, very
16704 confidence- inspiring in their secure-programming techniques.
16705 Closes ticket 13338.
16706 - Remove the code that would try to aggressively flush controller
16707 connections while writing to them. This code was introduced in
16708 0.1.2.7-alpha, in order to keep output buffers from exceeding
16709 their limits. But there is no longer a maximum output buffer size,
16710 and flushing data in this way caused some undesirable recursions
16711 in our call graph. Closes ticket 16480.
16714 - Make "bridges+hs" the default test network. This tests almost all
16715 tor functionality during make test-network, while allowing tests
16716 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
16717 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
16718 (chutney). Patches by "teor".
16719 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
16720 by-side in the same parent directory. Closes ticket 16903. Patch
16722 - Use environment variables rather than autoconf substitutions to
16723 send variables from the build system to the test scripts. This
16724 change should be easier to maintain, and cause 'make distcheck' to
16725 work better than before. Fixes bug 17148.
16726 - Add a new set of callgraph analysis scripts that use clang to
16727 produce a list of which Tor functions are reachable from which
16728 other Tor functions. We're planning to use these to help simplify
16729 our code structure by identifying illogical dependencies.
16730 - Add new 'test-full' and 'test-full-online' targets to run all
16731 tests, including integration tests with stem and chutney.
16732 - Make the test-workqueue test work on Windows by initializing the
16733 network before we begin.
16734 - New make target (make test-network-all) to run multiple applicable
16735 chutney test cases. Patch from Teor; closes 16953.
16736 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
16737 functions in dns.c. Implements a portion of ticket 16831.
16738 - When building Tor with testing coverage enabled, run Chutney tests
16739 (if any) using the 'tor-cov' coverage binary.
16740 - When running test-network or test-stem, check for the absence of
16741 stem/chutney before doing any build operations.
16744 Changes in version 0.2.7.2-alpha - 2015-07-27
16745 This, the second alpha in the Tor 0.2.7 series, has a number of new
16746 features, including a way to manually pick the number of introduction
16747 points for hidden services, and the much stronger Ed25519 signing key
16748 algorithm for regular Tor relays (including support for encrypted
16749 offline identity keys in the new algorithm).
16751 Support for Ed25519 on relays is currently limited to signing router
16752 descriptors; later alphas in this series will extend Ed25519 key
16753 support to more parts of the Tor protocol.
16755 o Major features (Ed25519 identity keys, Proposal 220):
16756 - All relays now maintain a stronger identity key, using the Ed25519
16757 elliptic curve signature format. This master key is designed so
16758 that it can be kept offline. Relays also generate an online
16759 signing key, and a set of other Ed25519 keys and certificates.
16760 These are all automatically regenerated and rotated as needed.
16761 Implements part of ticket 12498.
16762 - Directory authorities now vote on Ed25519 identity keys along with
16763 RSA1024 keys. Implements part of ticket 12498.
16764 - Directory authorities track which Ed25519 identity keys have been
16765 used with which RSA1024 identity keys, and do not allow them to
16766 vary freely. Implements part of ticket 12498.
16767 - Microdescriptors now include Ed25519 identity keys. Implements
16768 part of ticket 12498.
16769 - Add support for offline encrypted Ed25519 master keys. To use this
16770 feature on your tor relay, run "tor --keygen" to make a new master
16771 key (or to make a new signing key if you already have a master
16772 key). Closes ticket 13642.
16774 o Major features (Hidden services):
16775 - Add the torrc option HiddenServiceNumIntroductionPoints, to
16776 specify a fixed number of introduction points. Its maximum value
16777 is 10 and default is 3. Using this option can increase a hidden
16778 service's reliability under load, at the cost of making it more
16779 visible that the hidden service is facing extra load. Closes
16781 - Remove the adaptive algorithm for choosing the number of
16782 introduction points, which used to change the number of
16783 introduction points (poorly) depending on the number of
16784 connections the HS sees. Closes ticket 4862.
16786 o Major features (onion key cross-certification):
16787 - Relay descriptors now include signatures of their own identity
16788 keys, made using the TAP and ntor onion keys. These signatures
16789 allow relays to prove ownership of their own onion keys. Because
16790 of this change, microdescriptors will no longer need to include
16791 RSA identity keys. Implements proposal 228; closes ticket 12499.
16793 o Major features (performance):
16794 - Improve the runtime speed of Ed25519 operations by using the
16795 public-domain Ed25519-donna by Andrew M. ("floodyberry").
16796 Implements ticket 16467.
16797 - Improve the runtime speed of the ntor handshake by using an
16798 optimized curve25519 basepoint scalarmult implementation from the
16799 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
16800 ideas by Adam Langley. Implements ticket 9663.
16802 o Major bugfixes (client-side privacy, also in 0.2.6.9):
16803 - Properly separate out each SOCKSPort when applying stream
16804 isolation. The error occurred because each port's session group
16805 was being overwritten by a default value when the listener
16806 connection was initialized. Fixes bug 16247; bugfix on
16807 0.2.6.3-alpha. Patch by "jojelino".
16809 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
16810 - Stop refusing to store updated hidden service descriptors on a
16811 client. This reverts commit 9407040c59218 (which indeed fixed bug
16812 14219, but introduced a major hidden service reachability
16813 regression detailed in bug 16381). This is a temporary fix since
16814 we can live with the minor issue in bug 14219 (it just results in
16815 some load on the network) but the regression of 16381 is too much
16816 of a setback. First-round fix for bug 16381; bugfix
16819 o Major bugfixes (hidden services):
16820 - When cannibalizing a circuit for an introduction point, always
16821 extend to the chosen exit node (creating a 4 hop circuit).
16822 Previously Tor would use the current circuit exit node, which
16823 changed the original choice of introduction point, and could cause
16824 the hidden service to skip excluded introduction points or
16825 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
16828 o Major bugfixes (open file limit):
16829 - The open file limit wasn't checked before calling
16830 tor_accept_socket_nonblocking(), which would make Tor exceed the
16831 limit. Now, before opening a new socket, Tor validates the open
16832 file limit just before, and if the max has been reached, return an
16833 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
16835 o Major bugfixes (stability, also in 0.2.6.10):
16836 - Stop crashing with an assertion failure when parsing certain kinds
16837 of malformed or truncated microdescriptors. Fixes bug 16400;
16838 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
16839 by "cypherpunks_backup".
16840 - Stop random client-side assertion failures that could occur when
16841 connecting to a busy hidden service, or connecting to a hidden
16842 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
16845 o Minor features (directory authorities, security, also in 0.2.6.9):
16846 - The HSDir flag given by authorities now requires the Stable flag.
16847 For the current network, this results in going from 2887 to 2806
16848 HSDirs. Also, it makes it harder for an attacker to launch a sybil
16849 attack by raising the effort for a relay to become Stable to
16850 require at the very least 7 days, while maintaining the 96 hours
16851 uptime requirement for HSDir. Implements ticket 8243.
16853 o Minor features (client):
16854 - Relax the validation of hostnames in SOCKS5 requests, allowing the
16855 character '_' to appear, in order to cope with domains observed in
16856 the wild that are serving non-RFC compliant records. Resolves
16858 - Relax the validation done to hostnames in SOCKS5 requests, and
16859 allow a single trailing '.' to cope with clients that pass FQDNs
16860 using that syntax to explicitly indicate that the domain name is
16861 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
16862 - Add GroupWritable and WorldWritable options to unix-socket based
16863 SocksPort and ControlPort options. These options apply to a single
16864 socket, and override {Control,Socks}SocketsGroupWritable. Closes
16867 o Minor features (control protocol):
16868 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
16869 the control protocol. Resolves ticket 15358.
16871 o Minor features (directory authorities):
16872 - Directory authorities no longer vote against the "Fast", "Stable",
16873 and "HSDir" flags just because they were going to vote against
16874 "Running": if the consensus turns out to be that the router was
16875 running, then the authority's vote should count. Patch from Peter
16876 Retzlaff; closes issue 8712.
16878 o Minor features (geoip, also in 0.2.6.10):
16879 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
16880 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
16882 o Minor features (hidden services):
16883 - Add the new options "HiddenServiceMaxStreams" and
16884 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
16885 limit the maximum number of simultaneous streams per circuit, and
16886 optionally tear down the circuit when the limit is exceeded. Part
16889 o Minor features (portability):
16890 - Use C99 variadic macros when the compiler is not GCC. This avoids
16891 failing compilations on MSVC, and fixes a log-file-based race
16892 condition in our old workarounds. Original patch from Gisle Vanem.
16894 o Minor bugfixes (compilation, also in 0.2.6.9):
16895 - Build with --enable-systemd correctly when libsystemd is
16896 installed, but systemd is not. Fixes bug 16164; bugfix on
16897 0.2.6.3-alpha. Patch from Peter Palfrader.
16899 o Minor bugfixes (controller):
16900 - Add the descriptor ID in each HS_DESC control event. It was
16901 missing, but specified in control-spec.txt. Fixes bug 15881;
16902 bugfix on 0.2.5.2-alpha.
16904 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
16905 - Check for failures from crypto_early_init, and refuse to continue.
16906 A previous typo meant that we could keep going with an
16907 uninitialized crypto library, and would have OpenSSL initialize
16908 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
16909 when implementing ticket 4900. Patch by "teor".
16911 o Minor bugfixes (hidden services):
16912 - Fix a crash when reloading configuration while at least one
16913 configured and one ephemeral hidden service exists. Fixes bug
16914 16060; bugfix on 0.2.7.1-alpha.
16915 - Avoid crashing with a double-free bug when we create an ephemeral
16916 hidden service but adding it fails for some reason. Fixes bug
16917 16228; bugfix on 0.2.7.1-alpha.
16919 o Minor bugfixes (Linux seccomp2 sandbox):
16920 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
16921 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
16923 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
16924 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
16925 these when eventfd2() support is missing. Fixes bug 16363; bugfix
16926 on 0.2.6.3-alpha. Patch from "teor".
16928 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
16929 - Fix sandboxing to work when running as a relay, by allowing the
16930 renaming of secret_id_key, and allowing the eventfd2 and futex
16931 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
16933 - Allow systemd connections to work with the Linux seccomp2 sandbox
16934 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
16937 o Minor bugfixes (relay):
16938 - Fix a rarely-encountered memory leak when failing to initialize
16939 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
16940 from "cypherpunks".
16942 o Minor bugfixes (systemd):
16943 - Fix an accidental formatting error that broke the systemd
16944 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
16945 - Tor's systemd unit file no longer contains extraneous spaces.
16946 These spaces would sometimes confuse tools like deb-systemd-
16947 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
16949 o Minor bugfixes (tests):
16950 - Use the configured Python executable when running test-stem-full.
16951 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
16953 o Minor bugfixes (tests, also in 0.2.6.9):
16954 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
16955 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
16957 o Minor bugfixes (threads, comments):
16958 - Always initialize return value in compute_desc_id in rendcommon.c
16959 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
16960 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
16961 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
16962 - Remove undefined directive-in-macro in test_util_writepid clang
16963 3.7 complains that using a preprocessor directive inside a macro
16964 invocation in test_util_writepid in test_util.c is undefined.
16965 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
16967 o Code simplification and refactoring:
16968 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
16969 to ensure they remain consistent and visible everywhere.
16970 - Remove some vestigial workarounds for the MSVC6 compiler. We
16971 haven't supported that in ages.
16972 - The link authentication code has been refactored for better
16973 testability and reliability. It now uses code generated with the
16974 "trunnel" binary encoding generator, to reduce the risk of bugs
16975 due to programmer error. Done as part of ticket 12498.
16978 - Include a specific and (hopefully) accurate documentation of the
16979 torrc file's meta-format in doc/torrc_format.txt. This is mainly
16980 of interest to people writing programs to parse or generate torrc
16981 files. This document is not a commitment to long-term
16982 compatibility; some aspects of the current format are a bit
16983 ridiculous. Closes ticket 2325.
16985 o Removed features:
16986 - Tor no longer supports copies of OpenSSL that are missing support
16987 for Elliptic Curve Cryptography. (We began using ECC when
16988 available in 0.2.4.8-alpha, for more safe and efficient key
16989 negotiation.) In particular, support for at least one of P256 or
16990 P224 is now required, with manual configuration needed if only
16991 P224 is available. Resolves ticket 16140.
16992 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
16993 on an operating system that has not upgraded to OpenSSL 1.0 or
16994 later, and you compile Tor from source, you will need to install a
16995 more recent OpenSSL to link Tor against.) These versions of
16996 OpenSSL are still supported by the OpenSSL, but the numerous
16997 cryptographic improvements in later OpenSSL releases makes them a
16998 clear choice. Resolves ticket 16034.
16999 - Remove the HidServDirectoryV2 option. Now all relays offer to
17000 store hidden service descriptors. Related to 16543.
17001 - Remove the VoteOnHidServDirectoriesV2 option, since all
17002 authorities have long set it to 1. Closes ticket 16543.
17005 - Document use of coverity, clang static analyzer, and clang dynamic
17006 undefined behavior and address sanitizers in doc/HACKING. Include
17007 detailed usage instructions in the blacklist. Patch by "teor".
17008 Closes ticket 15817.
17009 - The link authentication protocol code now has extensive tests.
17010 - The relay descriptor signature testing code now has
17012 - The test_workqueue program now runs faster, and is enabled by
17013 default as a part of "make check".
17014 - Now that OpenSSL has its own scrypt implementation, add an unit
17015 test that checks for interoperability between libscrypt_scrypt()
17016 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
17017 and rely on EVP_PBE_scrypt() whenever possible. Resolves
17021 Changes in version 0.2.6.10 - 2015-07-12
17022 Tor version 0.2.6.10 fixes some significant stability and hidden
17023 service client bugs, bulletproofs the cryptography init process, and
17024 fixes a bug when using the sandbox code with some older versions of
17025 Linux. Everyone running an older version, especially an older version
17026 of 0.2.6, should upgrade.
17028 o Major bugfixes (hidden service clients, stability):
17029 - Stop refusing to store updated hidden service descriptors on a
17030 client. This reverts commit 9407040c59218 (which indeed fixed bug
17031 14219, but introduced a major hidden service reachability
17032 regression detailed in bug 16381). This is a temporary fix since
17033 we can live with the minor issue in bug 14219 (it just results in
17034 some load on the network) but the regression of 16381 is too much
17035 of a setback. First-round fix for bug 16381; bugfix
17038 o Major bugfixes (stability):
17039 - Stop crashing with an assertion failure when parsing certain kinds
17040 of malformed or truncated microdescriptors. Fixes bug 16400;
17041 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
17042 by "cypherpunks_backup".
17043 - Stop random client-side assertion failures that could occur when
17044 connecting to a busy hidden service, or connecting to a hidden
17045 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
17048 o Minor features (geoip):
17049 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
17050 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
17052 o Minor bugfixes (crypto error-handling):
17053 - Check for failures from crypto_early_init, and refuse to continue.
17054 A previous typo meant that we could keep going with an
17055 uninitialized crypto library, and would have OpenSSL initialize
17056 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
17057 when implementing ticket 4900. Patch by "teor".
17059 o Minor bugfixes (Linux seccomp2 sandbox):
17060 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
17061 these when eventfd2() support is missing. Fixes bug 16363; bugfix
17062 on 0.2.6.3-alpha. Patch from "teor".
17065 Changes in version 0.2.6.9 - 2015-06-11
17066 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
17067 requirements for receiving an HSDir flag, and addresses some other small
17068 bugs in the systemd and sandbox code. Clients using circuit isolation
17069 should upgrade; all directory authorities should upgrade.
17071 o Major bugfixes (client-side privacy):
17072 - Properly separate out each SOCKSPort when applying stream
17073 isolation. The error occurred because each port's session group was
17074 being overwritten by a default value when the listener connection
17075 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
17078 o Minor feature (directory authorities, security):
17079 - The HSDir flag given by authorities now requires the Stable flag.
17080 For the current network, this results in going from 2887 to 2806
17081 HSDirs. Also, it makes it harder for an attacker to launch a sybil
17082 attack by raising the effort for a relay to become Stable which
17083 takes at the very least 7 days to do so and by keeping the 96
17084 hours uptime requirement for HSDir. Implements ticket 8243.
17086 o Minor bugfixes (compilation):
17087 - Build with --enable-systemd correctly when libsystemd is
17088 installed, but systemd is not. Fixes bug 16164; bugfix on
17089 0.2.6.3-alpha. Patch from Peter Palfrader.
17091 o Minor bugfixes (Linux seccomp2 sandbox):
17092 - Fix sandboxing to work when running as a relaymby renaming of
17093 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
17094 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
17095 - Allow systemd connections to work with the Linux seccomp2 sandbox
17096 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
17099 o Minor bugfixes (tests):
17100 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
17101 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
17104 Changes in version 0.2.6.8 - 2015-05-21
17105 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
17106 fixes an authority-side bug in assigning the HSDir flag. All directory
17107 authorities should upgrade.
17109 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
17110 - Revert commit that made directory authorities assign the HSDir
17111 flag to relays without a DirPort; this was bad because such relays
17112 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
17115 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
17116 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
17117 a client authorized hidden service. Fixes bug 15823; bugfix
17120 o Minor features (geoip):
17121 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
17122 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
17126 Changes in version 0.2.7.1-alpha - 2015-05-12
17127 Tor 0.2.7.1-alpha is the first alpha release in its series. It
17128 includes numerous small features and bugfixes against previous Tor
17129 versions, and numerous small infrastructure improvements. The most
17130 notable features are several new ways for controllers to interact with
17131 the hidden services subsystem.
17133 o New system requirements:
17134 - Tor no longer includes workarounds to support Libevent versions
17135 before 1.3e. Libevent 2.0 or later is recommended. Closes
17138 o Major features (controller):
17139 - Add the ADD_ONION and DEL_ONION commands that allow the creation
17140 and management of hidden services via the controller. Closes
17142 - New "GETINFO onions/current" and "GETINFO onions/detached"
17143 commands to get information about hidden services created via the
17144 controller. Part of ticket 6411.
17145 - New HSFETCH command to launch a request for a hidden service
17146 descriptor. Closes ticket 14847.
17147 - New HSPOST command to upload a hidden service descriptor. Closes
17148 ticket 3523. Patch by "DonnchaC".
17150 o Major bugfixes (hidden services):
17151 - Revert commit that made directory authorities assign the HSDir
17152 flag to relays without a DirPort; this was bad because such relays
17153 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
17156 o Minor features (clock-jump tolerance):
17157 - Recover better when our clock jumps back many hours, like might
17158 happen for Tails or Whonix users who start with a very wrong
17159 hardware clock, use Tor to discover a more accurate time, and then
17160 fix their clock. Resolves part of ticket 8766.
17162 o Minor features (command-line interface):
17163 - Make --hash-password imply --hush to prevent unnecessary noise.
17164 Closes ticket 15542. Patch from "cypherpunks".
17165 - Print a warning whenever we find a relative file path being used
17166 as torrc option. Resolves issue 14018.
17168 o Minor features (controller):
17169 - Add DirAuthority lines for default directory authorities to the
17170 output of the "GETINFO config/defaults" command if not already
17171 present. Implements ticket 14840.
17172 - Controllers can now use "GETINFO hs/client/desc/id/..." to
17173 retrieve items from the client's hidden service descriptor cache.
17174 Closes ticket 14845.
17175 - Implement a new controller command "GETINFO status/fresh-relay-
17176 descs" to fetch a descriptor/extrainfo pair that was generated on
17177 demand just for the controller's use. Implements ticket 14784.
17179 o Minor features (DoS-resistance):
17180 - Make it harder for attackers to overload hidden services with
17181 introductions, by blocking multiple introduction requests on the
17182 same circuit. Resolves ticket 15515.
17184 o Minor features (geoip):
17185 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
17186 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
17189 o Minor features (HS popularity countermeasure):
17190 - To avoid leaking HS popularity, don't cycle the introduction point
17191 when we've handled a fixed number of INTRODUCE2 cells but instead
17192 cycle it when a random number of introductions is reached, thus
17193 making it more difficult for an attacker to find out the amount of
17194 clients that have used the introduction point for a specific HS.
17195 Closes ticket 15745.
17197 o Minor features (logging):
17198 - Include the Tor version in all LD_BUG log messages, since people
17199 tend to cut and paste those into the bugtracker. Implements
17202 o Minor features (pluggable transports):
17203 - When launching managed pluggable transports on Linux systems,
17204 attempt to have the kernel deliver a SIGTERM on tor exit if the
17205 pluggable transport process is still running. Resolves
17207 - When launching managed pluggable transports, setup a valid open
17208 stdin in the child process that can be used to detect if tor has
17209 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
17210 can be used by implementations to detect this new behavior.
17211 Resolves ticket 15435.
17213 o Minor features (testing):
17214 - Add a test to verify that the compiler does not eliminate our
17215 memwipe() implementation. Closes ticket 15377.
17216 - Add make rule `check-changes` to verify the format of changes
17217 files. Closes ticket 15180.
17218 - Add unit tests for control_event_is_interesting(). Add a compile-
17219 time check that the number of events doesn't exceed the capacity
17220 of control_event_t.event_mask. Closes ticket 15431, checks for
17221 bugs similar to 13085. Patch by "teor".
17222 - Command-line argument tests moved to Stem. Resolves ticket 14806.
17223 - Integrate the ntor, backtrace, and zero-length keys tests into the
17224 automake test suite. Closes ticket 15344.
17225 - Remove assertions during builds to determine Tor's test coverage.
17226 We don't want to trigger these even in assertions, so including
17227 them artificially makes our branch coverage look worse than it is.
17228 This patch provides the new test-stem-full and coverage-html-full
17229 configure options. Implements ticket 15400.
17231 o Minor bugfixes (build):
17232 - Improve out-of-tree builds by making non-standard rules work and
17233 clean up additional files and directories. Fixes bug 15053; bugfix
17236 o Minor bugfixes (command-line interface):
17237 - When "--quiet" is provided along with "--validate-config", do not
17238 write anything to stdout on success. Fixes bug 14994; bugfix
17240 - When complaining about bad arguments to "--dump-config", use
17241 stderr, not stdout.
17243 o Minor bugfixes (configuration, unit tests):
17244 - Only add the default fallback directories when the DirAuthorities,
17245 AlternateDirAuthority, and FallbackDir directory config options
17246 are set to their defaults. The default fallback directory list is
17247 currently empty, this fix will only change tor's behavior when it
17248 has default fallback directories. Includes unit tests for
17249 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
17250 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
17252 o Minor bugfixes (correctness):
17253 - For correctness, avoid modifying a constant string in
17254 handle_control_postdescriptor. Fixes bug 15546; bugfix
17256 - Remove side-effects from tor_assert() calls. This was harmless,
17257 because we never disable assertions, but it is bad style and
17258 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
17261 o Minor bugfixes (hidden service):
17262 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
17263 a client authorized hidden service. Fixes bug 15823; bugfix
17265 - Remove an extraneous newline character from the end of hidden
17266 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
17268 o Minor bugfixes (interface):
17269 - Print usage information for --dump-config when it is used without
17270 an argument. Also, fix the error message to use different wording
17271 and add newline at the end. Fixes bug 15541; bugfix
17274 o Minor bugfixes (logs):
17275 - When building Tor under Clang, do not include an extra set of
17276 parentheses in log messages that include function names. Fixes bug
17277 15269; bugfix on every released version of Tor when compiled with
17278 recent enough Clang.
17280 o Minor bugfixes (network):
17281 - When attempting to use fallback technique for network interface
17282 lookup, disregard loopback and multicast addresses since they are
17283 unsuitable for public communications.
17285 o Minor bugfixes (statistics):
17286 - Disregard the ConnDirectionStatistics torrc options when Tor is
17287 not a relay since in that mode of operation no sensible data is
17288 being collected and because Tor might run into measurement hiccups
17289 when running as a client for some time, then becoming a relay.
17290 Fixes bug 15604; bugfix on 0.2.2.35.
17292 o Minor bugfixes (test networks):
17293 - When self-testing reachability, use ExtendAllowPrivateAddresses to
17294 determine if local/private addresses imply reachability. The
17295 previous fix used TestingTorNetwork, which implies
17296 ExtendAllowPrivateAddresses, but this excluded rare configurations
17297 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
17298 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
17299 issue discovered by CJ Ess.
17301 o Minor bugfixes (testing):
17302 - Check for matching value in server response in ntor_ref.py. Fixes
17303 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
17305 - Set the severity correctly when testing
17306 get_interface_addresses_ifaddrs() and
17307 get_interface_addresses_win32(), so that the tests fail gracefully
17308 instead of triggering an assertion. Fixes bug 15759; bugfix on
17309 0.2.6.3-alpha. Reported by Nicolas Derive.
17311 o Code simplification and refactoring:
17312 - Move the hacky fallback code out of get_interface_address6() into
17313 separate function and get it covered with unit-tests. Resolves
17315 - Refactor hidden service client-side cache lookup to intelligently
17316 report its various failure cases, and disentangle failure cases
17317 involving a lack of introduction points. Closes ticket 14391.
17318 - Use our own Base64 encoder instead of OpenSSL's, to allow more
17319 control over the output. Part of ticket 15652.
17322 - Improve the descriptions of statistics-related torrc options in
17323 the manpage to describe rationale and possible uses cases. Fixes
17325 - Improve the layout and formatting of ./configure --help messages.
17326 Closes ticket 15024. Patch from "cypherpunks".
17327 - Standardize on the term "server descriptor" in the manual page.
17328 Previously, we had used "router descriptor", "server descriptor",
17329 and "relay descriptor" interchangeably. Part of ticket 14987.
17332 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
17333 and always use the internal Base64 decoder. The internal decoder
17334 has been part of tor since 0.2.0.10-alpha, and no one should
17335 be using the OpenSSL one. Part of ticket 15652.
17336 - Remove the 'tor_strclear()' function; use memwipe() instead.
17337 Closes ticket 14922.
17339 o Removed features:
17340 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
17341 fingerprinting we now recommend pluggable transports; for forward-
17342 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
17343 - Remove the undocumented "--digests" command-line option. It
17344 complicated our build process, caused subtle build issues on
17345 multiple platforms, and is now redundant since we started
17346 including git version identifiers. Closes ticket 14742.
17347 - Tor no longer contains checks for ancient directory cache versions
17348 that didn't know about microdescriptors.
17349 - Tor no longer contains workarounds for stat files generated by
17350 super-old versions of Tor that didn't choose guards sensibly.
17353 Changes in version 0.2.4.27 - 2015-04-06
17354 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
17355 could be used by an attacker to crash hidden services, or crash clients
17356 visiting hidden services. Hidden services should upgrade as soon as
17357 possible; clients should upgrade whenever packages become available.
17359 This release also backports a simple improvement to make hidden
17360 services a bit less vulnerable to denial-of-service attacks.
17362 o Major bugfixes (security, hidden service):
17363 - Fix an issue that would allow a malicious client to trigger an
17364 assertion failure and halt a hidden service. Fixes bug 15600;
17365 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
17366 - Fix a bug that could cause a client to crash with an assertion
17367 failure when parsing a malformed hidden service descriptor. Fixes
17368 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
17370 o Minor features (DoS-resistance, hidden service):
17371 - Introduction points no longer allow multiple INTRODUCE1 cells to
17372 arrive on the same circuit. This should make it more expensive for
17373 attackers to overwhelm hidden services with introductions.
17374 Resolves ticket 15515.
17377 Changes in version 0.2.5.12 - 2015-04-06
17378 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
17379 could be used by an attacker to crash hidden services, or crash clients
17380 visiting hidden services. Hidden services should upgrade as soon as
17381 possible; clients should upgrade whenever packages become available.
17383 This release also backports a simple improvement to make hidden
17384 services a bit less vulnerable to denial-of-service attacks.
17386 o Major bugfixes (security, hidden service):
17387 - Fix an issue that would allow a malicious client to trigger an
17388 assertion failure and halt a hidden service. Fixes bug 15600;
17389 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
17390 - Fix a bug that could cause a client to crash with an assertion
17391 failure when parsing a malformed hidden service descriptor. Fixes
17392 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
17394 o Minor features (DoS-resistance, hidden service):
17395 - Introduction points no longer allow multiple INTRODUCE1 cells to
17396 arrive on the same circuit. This should make it more expensive for
17397 attackers to overwhelm hidden services with introductions.
17398 Resolves ticket 15515.
17401 Changes in version 0.2.6.7 - 2015-04-06
17402 Tor 0.2.6.7 fixes two security issues that could be used by an
17403 attacker to crash hidden services, or crash clients visiting hidden
17404 services. Hidden services should upgrade as soon as possible; clients
17405 should upgrade whenever packages become available.
17407 This release also contains two simple improvements to make hidden
17408 services a bit less vulnerable to denial-of-service attacks.
17410 o Major bugfixes (security, hidden service):
17411 - Fix an issue that would allow a malicious client to trigger an
17412 assertion failure and halt a hidden service. Fixes bug 15600;
17413 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
17414 - Fix a bug that could cause a client to crash with an assertion
17415 failure when parsing a malformed hidden service descriptor. Fixes
17416 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
17418 o Minor features (DoS-resistance, hidden service):
17419 - Introduction points no longer allow multiple INTRODUCE1 cells to
17420 arrive on the same circuit. This should make it more expensive for
17421 attackers to overwhelm hidden services with introductions.
17422 Resolves ticket 15515.
17423 - Decrease the amount of reattempts that a hidden service performs
17424 when its rendezvous circuits fail. This reduces the computational
17425 cost for running a hidden service under heavy load. Resolves
17429 Changes in version 0.2.6.6 - 2015-03-24
17430 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
17432 It adds numerous safety, security, correctness, and performance
17433 improvements. Client programs can be configured to use more kinds of
17434 sockets, AutomapHosts works better, the multithreading backend is
17435 improved, cell transmission is refactored, test coverage is much
17436 higher, more denial-of-service attacks are handled, guard selection is
17437 improved to handle long-term guards better, pluggable transports
17438 should work a bit better, and some annoying hidden service performance
17439 bugs should be addressed.
17441 o Minor bugfixes (portability):
17442 - Use the correct datatype in the SipHash-2-4 function to prevent
17443 compilers from assuming any sort of alignment. Fixes bug 15436;
17444 bugfix on 0.2.5.3-alpha.
17446 Changes in version 0.2.6.5-rc - 2015-03-18
17447 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
17448 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
17450 o Major bugfixes (client):
17451 - Avoid crashing when making certain configuration option changes on
17452 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
17455 o Major bugfixes (pluggable transports):
17456 - Initialize the extended OR Port authentication cookie before
17457 launching pluggable transports. This prevents a race condition
17458 that occurred when server-side pluggable transports would cache the
17459 authentication cookie before it has been (re)generated. Fixes bug
17460 15240; bugfix on 0.2.5.1-alpha.
17462 o Major bugfixes (portability):
17463 - Do not crash on startup when running on Solaris. Fixes a bug
17464 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
17467 o Minor features (heartbeat):
17468 - On relays, report how many connections we negotiated using each
17469 version of the Tor link protocols. This information will let us
17470 know if removing support for very old versions of the Tor
17471 protocols is harming the network. Closes ticket 15212.
17473 o Code simplification and refactoring:
17474 - Refactor main loop to extract the 'loop' part. This makes it
17475 easier to run Tor under Shadow. Closes ticket 15176.
17478 Changes in version 0.2.5.11 - 2015-03-17
17479 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
17481 It backports several bugfixes from the 0.2.6 branch, including a
17482 couple of medium-level security fixes for relays and exit nodes.
17483 It also updates the list of directory authorities.
17485 o Directory authority changes:
17486 - Remove turtles as a directory authority.
17487 - Add longclaw as a new (v3) directory authority. This implements
17488 ticket 13296. This keeps the directory authority count at 9.
17489 - The directory authority Faravahar has a new IP address. This
17490 closes ticket 14487.
17492 o Major bugfixes (crash, OSX, security):
17493 - Fix a remote denial-of-service opportunity caused by a bug in
17494 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
17497 o Major bugfixes (relay, stability, possible security):
17498 - Fix a bug that could lead to a relay crashing with an assertion
17499 failure if a buffer of exactly the wrong layout was passed to
17500 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
17501 0.2.0.10-alpha. Patch from 'cypherpunks'.
17502 - Do not assert if the 'data' pointer on a buffer is advanced to the
17503 very end of the buffer; log a BUG message instead. Only assert if
17504 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
17506 o Major bugfixes (exit node stability):
17507 - Fix an assertion failure that could occur under high DNS load.
17508 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
17509 diagnosed and fixed by "cypherpunks".
17511 o Major bugfixes (Linux seccomp2 sandbox):
17512 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
17513 crash during attempts to call wait4. Fixes bug 15088; bugfix on
17514 0.2.5.1-alpha. Patch from "sanic".
17516 o Minor features (controller):
17517 - New "GETINFO bw-event-cache" to get information about recent
17518 bandwidth events. Closes ticket 14128. Useful for controllers to
17519 get recent bandwidth history after the fix for ticket 13988.
17521 o Minor features (geoip):
17522 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
17523 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
17526 o Minor bugfixes (client, automapping):
17527 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
17528 no value follows the option. Fixes bug 14142; bugfix on
17529 0.2.4.7-alpha. Patch by "teor".
17530 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
17531 14195; bugfix on 0.1.0.1-rc.
17533 o Minor bugfixes (compilation):
17534 - Build without warnings with the stock OpenSSL srtp.h header, which
17535 has a duplicate declaration of SSL_get_selected_srtp_profile().
17536 Fixes bug 14220; this is OpenSSL's bug, not ours.
17538 o Minor bugfixes (directory authority):
17539 - Allow directory authorities to fetch more data from one another if
17540 they find themselves missing lots of votes. Previously, they had
17541 been bumping against the 10 MB queued data limit. Fixes bug 14261;
17542 bugfix on 0.1.2.5-alpha.
17543 - Enlarge the buffer to read bwauth generated files to avoid an
17544 issue when parsing the file in dirserv_read_measured_bandwidths().
17545 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
17547 o Minor bugfixes (statistics):
17548 - Increase period over which bandwidth observations are aggregated
17549 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
17551 o Minor bugfixes (preventative security, C safety):
17552 - When reading a hexadecimal, base-32, or base-64 encoded value from
17553 a string, always overwrite the whole output buffer. This prevents
17554 some bugs where we would look at (but fortunately, not reveal)
17555 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
17559 Changes in version 0.2.4.26 - 2015-03-17
17560 Tor 0.2.4.26 includes an updated list of directory authorities. It
17561 also backports a couple of stability and security bugfixes from 0.2.5
17564 o Directory authority changes:
17565 - Remove turtles as a directory authority.
17566 - Add longclaw as a new (v3) directory authority. This implements
17567 ticket 13296. This keeps the directory authority count at 9.
17568 - The directory authority Faravahar has a new IP address. This
17569 closes ticket 14487.
17571 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
17572 - Fix an assertion failure that could occur under high DNS load.
17573 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
17574 diagnosed and fixed by "cypherpunks".
17576 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
17577 - Fix a bug that could lead to a relay crashing with an assertion
17578 failure if a buffer of exactly the wrong layout was passed to
17579 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
17580 0.2.0.10-alpha. Patch from 'cypherpunks'.
17581 - Do not assert if the 'data' pointer on a buffer is advanced to the
17582 very end of the buffer; log a BUG message instead. Only assert if
17583 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
17585 o Minor features (geoip):
17586 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
17587 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
17590 Changes in version 0.2.6.4-rc - 2015-03-09
17591 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
17592 attacker might be able to use in order to crash certain Tor
17593 directories. It also resolves some minor issues left over from, or
17594 introduced in, Tor 0.2.6.3-alpha or earlier.
17596 o Major bugfixes (crash, OSX, security):
17597 - Fix a remote denial-of-service opportunity caused by a bug in
17598 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
17601 o Major bugfixes (relay, stability, possible security):
17602 - Fix a bug that could lead to a relay crashing with an assertion
17603 failure if a buffer of exactly the wrong layout is passed to
17604 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
17605 0.2.0.10-alpha. Patch from "cypherpunks".
17606 - Do not assert if the 'data' pointer on a buffer is advanced to the
17607 very end of the buffer; log a BUG message instead. Only assert if
17608 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
17610 o Major bugfixes (FreeBSD IPFW transparent proxy):
17611 - Fix address detection with FreeBSD transparent proxies, when
17612 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
17615 o Major bugfixes (Linux seccomp2 sandbox):
17616 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
17617 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
17619 - Allow AF_UNIX hidden services to be used with the seccomp2
17620 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
17621 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
17622 crash during attempts to call wait4. Fixes bug 15088; bugfix on
17623 0.2.5.1-alpha. Patch from "sanic".
17625 o Minor features (controller):
17626 - Messages about problems in the bootstrap process now include
17627 information about the server we were trying to connect to when we
17628 noticed the problem. Closes ticket 15006.
17630 o Minor features (geoip):
17631 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
17632 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
17635 o Minor features (logs):
17636 - Quiet some log messages in the heartbeat and at startup. Closes
17639 o Minor bugfixes (certificate handling):
17640 - If an authority operator accidentally makes a signing certificate
17641 with a future publication time, do not discard its real signing
17642 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
17643 - Remove any old authority certificates that have been superseded
17644 for at least two days. Previously, we would keep superseded
17645 certificates until they expired, if they were published close in
17646 time to the certificate that superseded them. Fixes bug 11454;
17647 bugfix on 0.2.1.8-alpha.
17649 o Minor bugfixes (compilation):
17650 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
17652 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
17655 o Minor bugfixes (testing):
17656 - Fix endianness issues in unit test for resolve_my_address() to
17657 have it pass on big endian systems. Fixes bug 14980; bugfix on
17659 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
17660 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
17661 - When running the new 'make test-stem' target, use the configured
17662 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
17663 from "cypherpunks".
17664 - When running the zero-length-keys tests, do not use the default
17665 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
17668 o Directory authority IP change:
17669 - The directory authority Faravahar has a new IP address. This
17670 closes ticket 14487.
17673 - Remove some lingering dead code that once supported mempools.
17674 Mempools were disabled by default in 0.2.5, and removed entirely
17675 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
17679 Changes in version 0.2.6.3-alpha - 2015-02-19
17680 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
17681 the 0.2.6.x series. It introduces support for more kinds of sockets,
17682 makes it harder to accidentally run an exit, improves our
17683 multithreading backend, incorporates several fixes for the
17684 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
17686 If no major regressions or security holes are found in this version,
17687 the next version will be a release candidate.
17689 o Deprecated versions:
17690 - Tor relays older than 0.2.4.18-rc are no longer allowed to
17691 advertise themselves on the network. Closes ticket 13555.
17693 o Major features (security, unix domain sockets):
17694 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
17695 applications can reach Tor without having to create AF_INET or
17696 AF_INET6 sockets, meaning they can completely disable their
17697 ability to make non-Tor network connections. To create a socket of
17698 this type, use "SocksPort unix:/path/to/socket". Implements
17700 - Support mapping hidden service virtual ports to AF_UNIX sockets.
17701 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
17702 Implements ticket 11485.
17704 o Major features (changed defaults):
17705 - Prevent relay operators from unintentionally running exits: When a
17706 relay is configured as an exit node, we now warn the user unless
17707 the "ExitRelay" option is set to 1. We warn even more loudly if
17708 the relay is configured with the default exit policy, since this
17709 can indicate accidental misconfiguration. Setting "ExitRelay 0"
17710 stops Tor from running as an exit relay. Closes ticket 10067.
17712 o Major features (directory system):
17713 - When downloading server- or microdescriptors from a directory
17714 server, we no longer launch multiple simultaneous requests to the
17715 same server. This reduces load on the directory servers,
17716 especially when directory guards are in use. Closes ticket 9969.
17717 - When downloading server- or microdescriptors over a tunneled
17718 connection, do not limit the length of our requests to what the
17719 Squid proxy is willing to handle. Part of ticket 9969.
17720 - Authorities can now vote on the correct digests and latest
17721 versions for different software packages. This allows packages
17722 that include Tor to use the Tor authority system as a way to get
17723 notified of updates and their correct digests. Implements proposal
17724 227. Closes ticket 10395.
17726 o Major features (guards):
17727 - Introduce the Guardfraction feature to improves load balancing on
17728 guard nodes. Specifically, it aims to reduce the traffic gap that
17729 guard nodes experience when they first get the Guard flag. This is
17730 a required step if we want to increase the guard lifetime to 9
17731 months or greater. Closes ticket 9321.
17733 o Major features (performance):
17734 - Make the CPU worker implementation more efficient by avoiding the
17735 kernel and lengthening pipelines. The original implementation used
17736 sockets to transfer data from the main thread to the workers, and
17737 didn't allow any thread to be assigned more than a single piece of
17738 work at once. The new implementation avoids communications
17739 overhead by making requests in shared memory, avoiding kernel IO
17740 where possible, and keeping more requests in flight at once.
17741 Implements ticket 9682.
17743 o Major features (relay):
17744 - Raise the minimum acceptable configured bandwidth rate for bridges
17745 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
17746 20 KiB/sec.) Closes ticket 13822.
17748 o Major bugfixes (exit node stability):
17749 - Fix an assertion failure that could occur under high DNS load.
17750 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
17751 diagnosed and fixed by "cypherpunks".
17753 o Major bugfixes (mixed relay-client operation):
17754 - When running as a relay and client at the same time (not
17755 recommended), if we decide not to use a new guard because we want
17756 to retry older guards, only close the locally-originating circuits
17757 passing through that guard. Previously we would close all the
17758 circuits through that guard. Fixes bug 9819; bugfix on
17759 0.2.1.1-alpha. Reported by "skruffy".
17761 o Minor features (build):
17762 - New --disable-system-torrc compile-time option to prevent Tor from
17763 looking for the system-wide torrc or torrc-defaults files.
17764 Resolves ticket 13037.
17766 o Minor features (controller):
17767 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
17768 events so controllers can observe circuit isolation inputs. Closes
17770 - ControlPort now supports the unix:/path/to/socket syntax as an
17771 alternative to the ControlSocket option, for consistency with
17772 SocksPort and HiddenServicePort. Closes ticket 14451.
17773 - New "GETINFO bw-event-cache" to get information about recent
17774 bandwidth events. Closes ticket 14128. Useful for controllers to
17775 get recent bandwidth history after the fix for ticket 13988.
17777 o Minor features (Denial of service resistance):
17778 - Count the total number of bytes used storing hidden service
17779 descriptors against the value of MaxMemInQueues. If we're low on
17780 memory, and more than 20% of our memory is used holding hidden
17781 service descriptors, free them until no more than 10% of our
17782 memory holds hidden service descriptors. Free the least recently
17783 fetched descriptors first. Resolves ticket 13806.
17784 - When we have recently been under memory pressure (over 3/4 of
17785 MaxMemInQueues is allocated), then allocate smaller zlib objects
17786 for small requests. Closes ticket 11791.
17788 o Minor features (geoip):
17789 - Update geoip and geoip6 files to the January 7 2015 Maxmind
17790 GeoLite2 Country database.
17792 o Minor features (guard nodes):
17793 - Reduce the time delay before saving guard status to disk from 10
17794 minutes to 30 seconds (or from one hour to 10 minutes if
17795 AvoidDiskWrites is set). Closes ticket 12485.
17797 o Minor features (hidden service):
17798 - Make Sybil attacks against hidden services harder by changing the
17799 minimum time required to get the HSDir flag from 25 hours up to 96
17800 hours. Addresses ticket 14149.
17801 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
17802 services to disable the anti-scanning feature introduced in
17803 0.2.6.2-alpha. With this option not set, a connection to an
17804 unlisted port closes the circuit. With this option set, only a
17805 RELAY_DONE cell is sent. Closes ticket 14084.
17807 o Minor features (interface):
17808 - Implement "-f -" command-line option to read torrc configuration
17809 from standard input, if you don't want to store the torrc file in
17810 the file system. Implements feature 13865.
17812 o Minor features (logging):
17813 - Add a count of unique clients to the bridge heartbeat message.
17814 Resolves ticket 6852.
17815 - Suppress "router info incompatible with extra info" message when
17816 reading extrainfo documents from cache. (This message got loud
17817 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
17819 - Elevate hidden service authorized-client message from DEBUG to
17820 INFO. Closes ticket 14015.
17822 o Minor features (stability):
17823 - Add assertions in our hash-table iteration code to check for
17824 corrupted values that could cause infinite loops. Closes
17827 o Minor features (systemd):
17828 - Various improvements and modernizations in systemd hardening
17829 support. Closes ticket 13805. Patch from Craig Andrews.
17831 o Minor features (testing networks):
17832 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
17833 and the default on a testing network to 2 minutes. Drop the
17834 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
17835 keep the default on a testing network at 30 seconds. This reduces
17836 HS bootstrap time to around 25 seconds. Also, change the default
17837 time in test-network.sh to match. Closes ticket 13401. Patch
17839 - Create TestingDirAuthVoteHSDir to correspond to
17840 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
17841 HSDir flag for the listed relays regardless of uptime or ORPort
17842 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
17843 Partial implementation for ticket 14067. Patch by "teor".
17845 o Minor features (tor2web mode):
17846 - Introduce the config option Tor2webRendezvousPoints, which allows
17847 clients in Tor2webMode to select a specific Rendezvous Point to be
17848 used in HS circuits. This might allow better performance for
17849 Tor2Web nodes. Implements ticket 12844.
17851 o Minor bugfixes (client DNS):
17852 - Report the correct cached DNS expiration times on SOCKS port or in
17853 DNS replies. Previously, we would report everything as "never
17854 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
17855 - Avoid a small memory leak when we find a cached answer for a
17856 reverse DNS lookup in a client-side DNS cache. (Remember, client-
17857 side DNS caching is off by default, and is not recommended.) Fixes
17858 bug 14259; bugfix on 0.2.0.1-alpha.
17860 o Minor bugfixes (client, automapping):
17861 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
17862 no value follows the option. Fixes bug 14142; bugfix on
17863 0.2.4.7-alpha. Patch by "teor".
17864 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
17865 14195; bugfix on 0.1.0.1-rc.
17866 - Prevent changes to other options from removing the wildcard value
17867 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
17869 - Allow MapAddress and AutomapHostsOnResolve to work together when
17870 an address is mapped into another address type (like .onion) that
17871 must be automapped at resolve time. Fixes bug 7555; bugfix
17874 o Minor bugfixes (client, bridges):
17875 - When we are using bridges and we had a network connectivity
17876 problem, only retry connecting to our currently configured
17877 bridges, not all bridges we know about and remember using. Fixes
17878 bug 14216; bugfix on 0.2.2.17-alpha.
17880 o Minor bugfixes (client, IPv6):
17881 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
17882 flag is not set; and not because the NoIPv4Traffic flag was set.
17883 Previously we'd looked at the NoIPv4Traffic flag for both types of
17884 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
17886 o Minor bugfixes (compilation):
17887 - The address of an array in the middle of a structure will always
17888 be non-NULL. clang recognises this and complains. Disable the
17889 tautologous and redundant check to silence this warning. Fixes bug
17890 14001; bugfix on 0.2.1.2-alpha.
17891 - Avoid warnings when building with systemd 209 or later. Fixes bug
17892 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
17893 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
17894 Addresses ticket 14188.
17895 - Build without warnings with the stock OpenSSL srtp.h header, which
17896 has a duplicate declaration of SSL_get_selected_srtp_profile().
17897 Fixes bug 14220; this is OpenSSL's bug, not ours.
17898 - Do not compile any code related to Tor2Web mode when Tor2Web mode
17899 is not enabled at compile time. Previously, this code was included
17900 in a disabled state. See discussion on ticket 12844.
17901 - Remove the --disable-threads configure option again. It was
17902 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
17903 14819; bugfix on 0.2.6.2-alpha.
17905 o Minor bugfixes (controller):
17906 - Report "down" in response to the "GETINFO entry-guards" command
17907 when relays are down with an unreachable_since value. Previously,
17908 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
17909 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
17910 14116; bugfix on 0.2.2.9-alpha.
17911 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
17912 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
17914 o Minor bugfixes (directory authority):
17915 - Allow directory authorities to fetch more data from one another if
17916 they find themselves missing lots of votes. Previously, they had
17917 been bumping against the 10 MB queued data limit. Fixes bug 14261;
17918 bugfix on 0.1.2.5-alpha.
17919 - Do not attempt to download extrainfo documents which we will be
17920 unable to validate with a matching server descriptor. Fixes bug
17921 13762; bugfix on 0.2.0.1-alpha.
17922 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
17923 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
17924 - Enlarge the buffer to read bwauth generated files to avoid an
17925 issue when parsing the file in dirserv_read_measured_bandwidths().
17926 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
17928 o Minor bugfixes (file handling):
17929 - Stop failing when key files are zero-length. Instead, generate new
17930 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
17931 on all versions of Tor. Patch by "teor".
17932 - Stop generating a fresh .old RSA onion key file when the .old file
17933 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
17934 - Avoid overwriting .old key files with empty key files.
17935 - Skip loading zero-length extrainfo store, router store, stats,
17936 state, and key files.
17937 - Avoid crashing when trying to reload a torrc specified as a
17938 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
17941 o Minor bugfixes (hidden services):
17942 - Close the introduction circuit when we have no more usable intro
17943 points, instead of waiting for it to time out. This also ensures
17944 that no follow-up HS descriptor fetch is triggered when the
17945 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
17946 - When fetching a hidden service descriptor for a down service that
17947 was recently up, do not keep refetching until we try the same
17948 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
17949 - Successfully launch Tor with a nonexistent hidden service
17950 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
17951 14106; bugfix on 0.2.6.2-alpha.
17953 o Minor bugfixes (logging):
17954 - Avoid crashing when there are more log domains than entries in
17955 domain_list. Bugfix on 0.2.3.1-alpha.
17956 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
17958 - Don't log messages to stdout twice when starting up. Fixes bug
17959 13993; bugfix on 0.2.6.1-alpha.
17961 o Minor bugfixes (parsing):
17962 - Stop accepting milliseconds (or other junk) at the end of
17963 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
17964 - Support two-number and three-number version numbers correctly, in
17965 case we change the Tor versioning system in the future. Fixes bug
17966 13661; bugfix on 0.0.8pre1.
17968 o Minor bugfixes (path counting):
17969 - When deciding whether the consensus lists any exit nodes, count
17970 the number listed in the consensus, not the number we have
17971 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
17972 - When deciding whether we have any exit nodes, only examine
17973 ExitNodes when the ExitNodes option is actually set. Fixes part of
17974 bug 14918; bugfix on 0.2.6.2-alpha.
17975 - Get rid of redundant and possibly scary warnings that we are
17976 missing directory information while we bootstrap. Fixes part of
17977 bug 14918; bugfix on 0.2.6.2-alpha.
17979 o Minor bugfixes (portability):
17980 - Fix the ioctl()-based network interface lookup code so that it
17981 will work on systems that have variable-length struct ifreq, for
17983 - Fix scheduler compilation on targets where char is unsigned. Fixes
17984 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
17986 o Minor bugfixes (sandbox):
17987 - Allow glibc fatal errors to be sent to stderr before Tor exits.
17988 Previously, glibc would try to write them to /dev/tty, and the
17989 sandbox would trap the call and make Tor exit prematurely. Fixes
17990 bug 14759; bugfix on 0.2.5.1-alpha.
17992 o Minor bugfixes (shutdown):
17993 - When shutting down, always call event_del() on lingering read or
17994 write events before freeing them. Otherwise, we risk double-frees
17995 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
17998 o Minor bugfixes (small memory leaks):
17999 - Avoid leaking memory when using IPv6 virtual address mappings.
18000 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
18003 o Minor bugfixes (statistics):
18004 - Increase period over which bandwidth observations are aggregated
18005 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
18007 o Minor bugfixes (systemd support):
18008 - Fix detection and operation of systemd watchdog. Fixes part of bug
18009 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
18010 - Run correctly under systemd with the RunAsDaemon option set. Fixes
18011 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
18012 - Inform the systemd supervisor about more changes in the Tor
18013 process status. Implements part of ticket 14141. Patch from
18015 - Cause the "--disable-systemd" option to actually disable systemd
18016 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
18019 o Minor bugfixes (TLS):
18020 - Check more thoroughly throughout the TLS code for possible
18021 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
18023 o Minor bugfixes (transparent proxy):
18024 - Use getsockname, not getsockopt, to retrieve the address for a
18025 TPROXY-redirected connection. Fixes bug 13796; bugfix
18028 o Code simplification and refactoring:
18029 - Move fields related to isolating and configuring client ports into
18030 a shared structure. Previously, they were duplicated across
18031 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
18032 to copy them correctly had been the cause of at least one bug in
18033 the past. Closes ticket 8546.
18034 - Refactor the get_interface_addresses_raw() doom-function into
18035 multiple smaller and simpler subfunctions. Cover the resulting
18036 subfunctions with unit-tests. Fixes a significant portion of
18038 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
18039 only for version <= 0.2.2.24 which is now deprecated. Closes
18041 - Remove a test for a long-defunct broken version-one
18045 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
18046 for writing the OpenBSD-specific tips. Resolves ticket 13702.
18047 - Make the tor-resolve documentation match its help string and its
18048 options. Resolves part of ticket 14325.
18049 - Log a more useful error message from tor-resolve when failing to
18050 look up a hidden service address. Resolves part of ticket 14325.
18052 o Downgraded warnings:
18053 - Don't warn when we've attempted to contact a relay using the wrong
18054 ntor onion key. Closes ticket 9635.
18056 o Removed features:
18057 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
18058 longer silently accepted as an alias for "ExitNodes".
18059 - The --enable-mempool and --enable-buf-freelists options, which
18060 were originally created to work around bad malloc implementations,
18061 no longer exist. They were off-by-default in 0.2.5. Closes
18065 - Make the checkdir/perms test complete successfully even if the
18066 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
18067 - Test that tor does not fail when key files are zero-length. Check
18068 that tor generates new keys, and overwrites the empty key files.
18069 - Test that tor generates new keys when keys are missing
18070 (existing behavior).
18071 - Test that tor does not overwrite key files that already contain
18072 data (existing behavior). Tests bug 13111. Patch by "teor".
18073 - New "make test-stem" target to run stem integration tests.
18074 Requires that the "STEM_SOURCE_DIR" environment variable be set.
18075 Closes ticket 14107.
18076 - Make the test_cmdline_args.py script work correctly on Windows.
18077 Patch from Gisle Vanem.
18078 - Move the slower unit tests into a new "./src/test/test-slow"
18079 binary that can be run independently of the other tests. Closes
18081 - Avoid undefined behavior when sampling huge values from the
18082 Laplace distribution. This made unittests fail on Raspberry Pi.
18083 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
18086 Changes in version 0.2.6.2-alpha - 2014-12-31
18087 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
18088 It introduces a major new backend for deciding when to send cells on
18089 channels, which should lead down the road to big performance
18090 increases. It contains security and statistics features for better
18091 work on hidden services, and numerous bugfixes.
18093 This release contains many new unit tests, along with major
18094 performance improvements for running testing networks using Chutney.
18095 Thanks to a series of patches contributed by "teor", testing networks
18096 should now bootstrap in seconds, rather than minutes.
18098 o Major features (relay, infrastructure):
18099 - Complete revision of the code that relays use to decide which cell
18100 to send next. Formerly, we selected the best circuit to write on
18101 each channel, but we didn't select among channels in any
18102 sophisticated way. Now, we choose the best circuits globally from
18103 among those whose channels are ready to deliver traffic.
18105 This patch implements a new inter-cmux comparison API, a global
18106 high/low watermark mechanism and a global scheduler loop for
18107 transmission prioritization across all channels as well as among
18108 circuits on one channel. This schedule is currently tuned to
18109 (tolerantly) avoid making changes in network performance, but it
18110 should form the basis for major circuit performance increases in
18111 the future. Code by Andrea; tuning by Rob Jansen; implements
18114 o Major features (hidden services):
18115 - Make HS port scanning more difficult by immediately closing the
18116 circuit when a user attempts to connect to a nonexistent port.
18117 Closes ticket 13667.
18118 - Add a HiddenServiceStatistics option that allows Tor relays to
18119 gather and publish statistics about the overall size and volume of
18120 hidden service usage. Specifically, when this option is turned on,
18121 an HSDir will publish an approximate number of hidden services
18122 that have published descriptors to it the past 24 hours. Also, if
18123 a relay has acted as a hidden service rendezvous point, it will
18124 publish the approximate amount of rendezvous cells it has relayed
18125 the past 24 hours. The statistics themselves are obfuscated so
18126 that the exact values cannot be derived. For more details see
18127 proposal 238, "Better hidden service stats from Tor relays". This
18128 feature is currently disabled by default. Implements feature 13192.
18130 o Major bugfixes (client, automap):
18131 - Repair automapping with IPv6 addresses. This automapping should
18132 have worked previously, but one piece of debugging code that we
18133 inserted to detect a regression actually caused the regression to
18134 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
18135 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
18138 o Major bugfixes (hidden services):
18139 - When closing an introduction circuit that was opened in parallel
18140 with others, don't mark the introduction point as unreachable.
18141 Previously, the first successful connection to an introduction
18142 point would make the other introduction points get marked as
18143 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
18145 o Directory authority changes:
18146 - Remove turtles as a directory authority.
18147 - Add longclaw as a new (v3) directory authority. This implements
18148 ticket 13296. This keeps the directory authority count at 9.
18150 o Major removed features:
18151 - Tor clients no longer support connecting to hidden services
18152 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
18153 option has been removed. (There shouldn't be any hidden services
18154 running these versions on the network.) Closes ticket 7803.
18156 o Minor features (client):
18157 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
18158 is enabled, reject requests with IP addresses as hostnames.
18159 Resolves ticket 13315.
18161 o Minor features (controller):
18162 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
18163 write an unscheduled heartbeat message to the log. Implements
18166 o Minor features (geoip):
18167 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
18170 o Minor features (hidden services):
18171 - When re-enabling the network, don't try to build introduction
18172 circuits until we have successfully built a circuit. This makes
18173 hidden services come up faster when the network is re-enabled.
18174 Patch from "akwizgran". Closes ticket 13447.
18175 - When we fail to retrieve a hidden service descriptor, send the
18176 controller an "HS_DESC FAILED" controller event. Implements
18178 - New HiddenServiceDirGroupReadable option to cause hidden service
18179 directories and hostname files to be created group-readable. Patch
18180 from "anon", David Stainton, and "meejah". Closes ticket 11291.
18182 o Minor features (systemd):
18183 - Where supported, when running with systemd, report successful
18184 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
18185 - When running with systemd, support systemd watchdog messages. Part
18186 of ticket 11016. Patch by Michael Scherer.
18188 o Minor features (transparent proxy):
18189 - Update the transparent proxy option checks to allow for both ipfw
18190 and pf on OS X. Closes ticket 14002.
18191 - Use the correct option when using IPv6 with transparent proxy
18192 support on Linux. Resolves 13808. Patch by Francisco Blas
18195 o Minor bugfixes (preventative security, C safety):
18196 - When reading a hexadecimal, base-32, or base-64 encoded value from
18197 a string, always overwrite the whole output buffer. This prevents
18198 some bugs where we would look at (but fortunately, not reveal)
18199 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
18201 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
18202 just the part that's used. This makes it harder for data leak bugs
18203 to occur in the event of other programming failures. Resolves
18206 o Minor bugfixes (client, microdescriptors):
18207 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
18208 computing which microdescriptors to download. This keeps us from
18209 erroneous download behavior if two microdescriptor digests ever
18210 have the same first 160 bits. Fixes part of bug 13399; bugfix
18212 - Reset a router's status if its microdescriptor digest changes,
18213 even if the first 160 bits remain the same. Fixes part of bug
18214 13399; bugfix on 0.2.3.1-alpha.
18216 o Minor bugfixes (compilation):
18217 - Silence clang warnings under --enable-expensive-hardening,
18218 including implicit truncation of 64 bit values to 32 bit, const
18219 char assignment to self, tautological compare, and additional
18220 parentheses around equality tests. Fixes bug 13577; bugfix
18222 - Fix a clang warning about checking whether an address in the
18223 middle of a structure is NULL. Fixes bug 14001; bugfix
18226 o Minor bugfixes (hidden services):
18227 - Correctly send a controller event when we find that a rendezvous
18228 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
18229 - Pre-check directory permissions for new hidden-services to avoid
18230 at least one case of "Bug: Acting on config options left us in a
18231 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
18232 - When adding a new hidden service (for example, via SETCONF), Tor
18233 no longer congratulates the user for running a relay. Fixes bug
18234 13941; bugfix on 0.2.6.1-alpha.
18235 - When fetching hidden service descriptors, we now check not only
18236 for whether we got the hidden service we had in mind, but also
18237 whether we got the particular descriptors we wanted. This prevents
18238 a class of inefficient but annoying DoS attacks by hidden service
18239 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
18242 o Minor bugfixes (Linux seccomp2 sandbox):
18243 - Make transparent proxy support work along with the seccomp2
18244 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
18245 by Francisco Blas Izquierdo Riera.
18246 - Fix a memory leak in tor-resolve when running with the sandbox
18247 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
18249 o Minor bugfixes (logging):
18250 - Downgrade warnings about RSA signature failures to info log level.
18251 Emit a warning when an extra info document is found incompatible
18252 with a corresponding router descriptor. Fixes bug 9812; bugfix
18254 - Make connection_ap_handshake_attach_circuit() log the circuit ID
18255 correctly. Fixes bug 13701; bugfix on 0.0.6.
18257 o Minor bugfixes (misc):
18258 - Stop allowing invalid address patterns like "*/24" that contain
18259 both a wildcard address and a bit prefix length. This affects all
18260 our address-range parsing code. Fixes bug 7484; bugfix
18263 o Minor bugfixes (testing networks, fast startup):
18264 - Allow Tor to build circuits using a consensus with no exits. If
18265 the consensus has no exits (typical of a bootstrapping test
18266 network), allow Tor to build circuits once enough descriptors have
18267 been downloaded. This assists in bootstrapping a testing Tor
18268 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
18270 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
18271 header to directory servers. This allows us to obtain consensuses
18272 promptly when the consensus interval is very short. This assists
18273 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
18274 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
18275 - Stop assuming that private addresses are local when checking
18276 reachability in a TestingTorNetwork. Instead, when testing, assume
18277 all OR connections are remote. (This is necessary due to many test
18278 scenarios running all relays on localhost.) This assists in
18279 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
18280 0.1.0.1-rc. Patch by "teor".
18281 - Avoid building exit circuits from a consensus with no exits. Now
18282 thanks to our fix for 13718, we accept a no-exit network as not
18283 wholly lost, but we need to remember not to try to build exit
18284 circuits on it. Closes ticket 13814; patch by "teor".
18285 - Stop requiring exits to have non-zero bandwithcapacity in a
18286 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
18287 ignore exit bandwidthcapacity. This assists in bootstrapping a
18288 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
18289 on 0.2.0.3-alpha. Patch by "teor".
18290 - Add "internal" to some bootstrap statuses when no exits are
18291 available. If the consensus does not contain Exits, Tor will only
18292 build internal circuits. In this case, relevant statuses will
18293 contain the word "internal" as indicated in the Tor control-
18294 spec.txt. When bootstrap completes, Tor will be ready to build
18295 internal circuits. If a future consensus contains Exits, exit
18296 circuits may become available. Fixes part of bug 13718; bugfix on
18297 0.2.4.10-alpha. Patch by "teor".
18298 - Decrease minimum consensus interval to 10 seconds when
18299 TestingTorNetwork is set, or 5 seconds for the first consensus.
18300 Fix assumptions throughout the code that assume larger intervals.
18301 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
18303 - Avoid excluding guards from path building in minimal test
18304 networks, when we're in a test network and excluding guards would
18305 exclude all relays. This typically occurs in incredibly small tor
18306 networks, and those using "TestingAuthVoteGuard *". Fixes part of
18307 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
18309 o Code simplification and refactoring:
18310 - Stop using can_complete_circuits as a global variable; access it
18311 with a function instead.
18312 - Avoid using operators directly as macro arguments: this lets us
18313 apply coccinelle transformations to our codebase more directly.
18314 Closes ticket 13172.
18315 - Combine the functions used to parse ClientTransportPlugin and
18316 ServerTransportPlugin into a single function. Closes ticket 6456.
18317 - Add inline functions and convenience macros for inspecting channel
18318 state. Refactor the code to use convenience macros instead of
18319 checking channel state directly. Fixes issue 7356.
18320 - Document all members of was_router_added_t and rename
18321 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
18322 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
18323 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
18324 constant instead of hardcoded value. Fixes issue 13840.
18325 - Refactor our generic strmap and digestmap types into a single
18326 implementation, so that we can add a new digest256map
18330 - Document the bridge-authority-only 'networkstatus-bridges' file.
18331 Closes ticket 13713; patch from "tom".
18332 - Fix typo in PredictedPortsRelevanceTime option description in
18333 manpage. Resolves issue 13707.
18334 - Stop suggesting that users specify relays by nickname: it isn't a
18335 good idea. Also, properly cross-reference how to specify relays in
18336 all parts of manual documenting options that take a list of
18337 relays. Closes ticket 13381.
18338 - Clarify the HiddenServiceDir option description in manpage to make
18339 it clear that relative paths are taken with respect to the current
18340 working directory. Also clarify that this behavior is not
18341 guaranteed to remain indefinitely. Fixes issue 13913.
18344 - New tests for many parts of channel, relay, and circuitmux
18345 functionality. Code by Andrea; part of 9262.
18346 - New tests for parse_transport_line(). Part of ticket 6456.
18347 - In the unit tests, use chgrp() to change the group of the unit
18348 test temporary directory to the current user, so that the sticky
18349 bit doesn't interfere with tests that check directory groups.
18351 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
18355 Changes in version 0.2.6.1-alpha - 2014-10-30
18356 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
18357 includes numerous code cleanups and new tests, and fixes a large
18358 number of annoying bugs. Out-of-memory conditions are handled better
18359 than in 0.2.5, pluggable transports have improved proxy support, and
18360 clients now use optimistic data for contacting hidden services. Also,
18361 we are now more robust to changes in what we consider a parseable
18362 directory object, so that tightening restrictions does not have a risk
18363 of introducing infinite download loops.
18365 This is the first alpha release in a new series, so expect there to be
18366 bugs. Users who would rather test out a more stable branch should stay
18367 with 0.2.5.x for now.
18369 o New compiler and system requirements:
18370 - Tor 0.2.6.x requires that your compiler support more of the C99
18371 language standard than before. The 'configure' script now detects
18372 whether your compiler supports C99 mid-block declarations and
18373 designated initializers. If it does not, Tor will not compile.
18375 We may revisit this requirement if it turns out that a significant
18376 number of people need to build Tor with compilers that don't
18377 bother implementing a 15-year-old standard. Closes ticket 13233.
18378 - Tor no longer supports systems without threading support. When we
18379 began working on Tor, there were several systems that didn't have
18380 threads, or where the thread support wasn't able to run the
18381 threads of a single process on multiple CPUs. That no longer
18382 holds: every system where Tor needs to run well now has threading
18383 support. Resolves ticket 12439.
18385 o Removed platform support:
18386 - We no longer include special code to build on Windows CE; as far
18387 as we know, nobody has used Tor on Windows CE in a very long time.
18388 Closes ticket 11446.
18390 o Major features (bridges):
18391 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
18392 transports if they are configured via the "TOR_PT_PROXY"
18393 environment variable. Implements proposal 232. Resolves
18396 o Major features (client performance, hidden services):
18397 - Allow clients to use optimistic data when connecting to a hidden
18398 service, which should remove a round-trip from hidden service
18399 initialization. See proposal 181 for details. Implements
18402 o Major features (directory system):
18403 - Upon receiving an unparseable directory object, if its digest
18404 matches what we expected, then don't try to download it again.
18405 Previously, when we got a descriptor we didn't like, we would keep
18406 trying to download it over and over. Closes ticket 11243.
18408 o Major features (sample torrc):
18409 - Add a new, infrequently-changed "torrc.minimal". This file is
18410 similar to torrc.sample, but it will change as infrequently as
18411 possible, for the benefit of users whose systems prompt them for
18412 intervention whenever a default configuration file is changed.
18413 Making this change allows us to update torrc.sample to be a more
18414 generally useful "sample torrc".
18416 o Major bugfixes (directory authorities):
18417 - Do not assign the HSDir flag to relays if they are not Valid, or
18418 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
18420 o Major bugfixes (directory bandwidth performance):
18421 - Don't flush the zlib buffer aggressively when compressing
18422 directory information for clients. This should save about 7% of
18423 the bandwidth currently used for compressed descriptors and
18424 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
18426 o Minor features (security, memory wiping):
18427 - Ensure we securely wipe keys from memory after
18428 crypto_digest_get_digest and init_curve25519_keypair_from_file
18429 have finished using them. Resolves ticket 13477.
18431 o Minor features (security, out-of-memory handling):
18432 - When handling an out-of-memory condition, allocate less memory for
18433 temporary data structures. Fixes issue 10115.
18434 - When handling an out-of-memory condition, consider more types of
18435 buffers, including those on directory connections, and zlib
18436 buffers. Resolves ticket 11792.
18439 - When identity keypair is generated for first time, log a
18440 congratulatory message that links to the new relay lifecycle
18441 document. Implements feature 10427.
18443 o Minor features (client):
18444 - Clients are now willing to send optimistic data (before they
18445 receive a 'connected' cell) to relays of any version. (Relays
18446 without support for optimistic data are no longer supported on the
18447 Tor network.) Resolves ticket 13153.
18449 o Minor features (directory authorities):
18450 - Don't list relays with a bandwidth estimate of 0 in the consensus.
18451 Implements a feature proposed during discussion of bug 13000.
18452 - In tor-gencert, report an error if the user provides the same
18453 argument more than once.
18454 - If a directory authority can't find a best consensus method in the
18455 votes that it holds, it now falls back to its favorite consensus
18456 method. Previously, it fell back to method 1. Neither of these is
18457 likely to get enough signatures, but "fall back to favorite"
18458 doesn't require us to maintain support an obsolete consensus
18459 method. Implements part of proposal 215.
18461 o Minor features (logging):
18462 - On Unix-like systems, you can now use named pipes as the target of
18463 the Log option, and other options that try to append to files.
18464 Closes ticket 12061. Patch from "carlo von lynX".
18465 - When opening a log file at startup, send it every log message that
18466 we generated between startup and opening it. Previously, log
18467 messages that were generated before opening the log file were only
18468 logged to stdout. Closes ticket 6938.
18469 - Add a TruncateLogFile option to overwrite logs instead of
18470 appending to them. Closes ticket 5583.
18472 o Minor features (portability, Solaris):
18473 - Threads are no longer disabled by default on Solaris; we believe
18474 that the versions of Solaris with broken threading support are all
18475 obsolete by now. Resolves ticket 9495.
18477 o Minor features (relay):
18478 - Re-check our address after we detect a changed IP address from
18479 getsockname(). This ensures that the controller command "GETINFO
18480 address" will report the correct value. Resolves ticket 11582.
18482 - A new AccountingRule option lets Relays set whether they'd like
18483 AccountingMax to be applied separately to inbound and outbound
18484 traffic, or applied to the sum of inbound and outbound traffic.
18485 Resolves ticket 961. Patch by "chobe".
18487 o Minor features (testing networks):
18488 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
18489 the "Exit" flag regardless of their uptime, bandwidth, or exit
18490 policy. TestingTorNetwork must be set for this option to have any
18491 effect. Previously, authorities would take up to 35 minutes to
18492 give nodes the Exit flag in a test network. Partially implements
18495 o Minor features (validation):
18496 - Check all date/time values passed to tor_timegm and
18497 parse_rfc1123_time for validity, taking leap years into account.
18498 Improves HTTP header validation. Implemented with bug 13476.
18499 - In correct_tm(), limit the range of values returned by system
18500 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
18501 This means we don't have to deal with negative or too large dates,
18502 even if a clock is wrong. Otherwise we might fail to read a file
18503 written by us which includes such a date. Fixes bug 13476.
18505 o Minor bugfixes (bridge clients):
18506 - When configured to use a bridge without an identity digest (not
18507 recommended), avoid launching an extra channel to it when
18508 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
18510 o Minor bugfixes (bridges):
18511 - When DisableNetwork is set, do not launch pluggable transport
18512 plugins, and if any are running, terminate them. Fixes bug 13213;
18513 bugfix on 0.2.3.6-alpha.
18515 o Minor bugfixes (C correctness):
18516 - Fix several instances of possible integer overflow/underflow/NaN.
18517 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
18519 - In circuit_build_times_calculate_timeout() in circuitstats.c,
18520 avoid dividing by zero in the pareto calculations. This traps
18521 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
18523 - Fix an integer overflow in format_time_interval(). Fixes bug
18524 13393; bugfix on 0.2.0.10-alpha.
18525 - Set the correct day of year value when the system's localtime(_r)
18526 or gmtime(_r) functions fail to set struct tm. Not externally
18527 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
18528 - Avoid unlikely signed integer overflow in tor_timegm on systems
18529 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
18531 o Minor bugfixes (client):
18532 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
18533 BadExit flag are not considered worthy candidates. Fixes bug
18534 13066; bugfix on 0.1.2.3-alpha.
18535 - Use the consensus schedule for downloading consensuses, and not
18536 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
18537 - Handle unsupported or malformed SOCKS5 requests properly by
18538 responding with the appropriate error message before closing the
18539 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
18541 o Minor bugfixes (client, torrc):
18542 - Stop modifying the value of our DirReqStatistics torrc option just
18543 because we're not a bridge or relay. This bug was causing Tor
18544 Browser users to write "DirReqStatistics 0" in their torrc files
18545 as if they had chosen to change the config. Fixes bug 4244; bugfix
18547 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
18548 that our options have changed every time we SIGHUP. Fixes bug
18549 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
18551 o Minor bugfixes (controller):
18552 - Return an error when the second or later arguments of the
18553 "setevents" controller command are invalid events. Previously we
18554 would return success while silently skipping invalid events. Fixes
18555 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
18557 o Minor bugfixes (directory system):
18558 - Always believe that v3 directory authorities serve extra-info
18559 documents, whether they advertise "caches-extra-info" or not.
18560 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
18561 - When running as a v3 directory authority, advertise that you serve
18562 extra-info documents so that clients who want them can find them
18563 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
18564 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
18565 Previously, directories offering BRIDGE_DIRINFO and some other
18566 flag (i.e. microdescriptors or extrainfo) would be ignored when
18567 looking for bridges. Partially fixes bug 13163; bugfix
18570 o Minor bugfixes (networking):
18571 - Check for orconns and use connection_or_close_for_error() rather
18572 than connection_mark_for_close() directly in the getsockopt()
18573 failure case of connection_handle_write_impl(). Fixes bug 11302;
18574 bugfix on 0.2.4.4-alpha.
18576 o Minor bugfixes (relay):
18577 - When generating our family list, remove spaces from around the
18578 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
18579 - If our previous bandwidth estimate was 0 bytes, allow publishing a
18580 new relay descriptor immediately. Fixes bug 13000; bugfix
18583 o Minor bugfixes (testing networks):
18584 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
18585 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
18586 - Stop using the default authorities in networks which provide both
18587 AlternateDirAuthority and AlternateBridgeAuthority. Partially
18588 fixes bug 13163; bugfix on 0.2.0.13-alpha.
18590 o Minor bugfixes (testing):
18591 - Stop spawn test failures due to a race condition between the
18592 SIGCHLD handler updating the process status, and the test reading
18593 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
18595 o Minor bugfixes (testing, Windows):
18596 - Avoid passing an extra backslash when creating a temporary
18597 directory for running the unit tests on Windows. Fixes bug 12392;
18598 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
18600 o Minor bugfixes (windows):
18601 - Remove code to special-case handling of NTE_BAD_KEYSET when
18602 acquiring windows CryptoAPI context. This error can't actually
18603 occur for the parameters we're providing. Fixes bug 10816; bugfix
18606 o Minor bugfixes (zlib):
18607 - Avoid truncating a zlib stream when trying to finalize it with an
18608 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
18611 - Allow our configure script to build correctly with autoconf 2.62
18612 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
18613 - Improve the error message from ./configure to make it clear that
18614 when asciidoc has not been found, the user will have to either add
18615 --disable-asciidoc argument or install asciidoc. Resolves
18618 o Code simplification and refactoring:
18619 - Change the entry_is_live() function to take named bitfield
18620 elements instead of an unnamed list of booleans. Closes
18622 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
18623 Resolves ticket 12205.
18624 - Use calloc and reallocarray functions instead of multiply-
18625 then-malloc. This makes it less likely for us to fall victim to an
18626 integer overflow attack when allocating. Resolves ticket 12855.
18627 - Use the standard macro name SIZE_MAX, instead of our
18629 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
18630 functions which take them as arguments. Replace 0 with NO_DIRINFO
18631 in a function call for clarity. Seeks to prevent future issues
18633 - Avoid 4 null pointer errors under clang static analysis by using
18634 tor_assert() to prove that the pointers aren't null. Fixes
18636 - Rework the API of policies_parse_exit_policy() to use a bitmask to
18637 represent parsing options, instead of a confusing mess of
18638 booleans. Resolves ticket 8197.
18639 - Introduce a helper function to parse ExitPolicy in
18640 or_options_t structure.
18643 - Add a doc/TUNING document with tips for handling large numbers of
18644 TCP connections when running busy Tor relay. Update the warning
18645 message to point to this file when running out of sockets
18646 operating system is allowing to use simultaneously. Resolves
18649 o Removed features:
18650 - We no longer remind the user about configuration options that have
18651 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
18652 - Remove our old, non-weighted bandwidth-based node selection code.
18653 Previously, we used it as a fallback when we couldn't perform
18654 weighted bandwidth-based node selection. But that would only
18655 happen in the cases where we had no consensus, or when we had a
18656 consensus generated by buggy or ancient directory authorities. In
18657 either case, it's better to use the more modern, better maintained
18658 algorithm, with reasonable defaults for the weights. Closes
18660 - Remove the --disable-curve25519 configure option. Relays and
18661 clients now are required to support curve25519 and the
18663 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
18664 used to be deprecated synonyms for "StrictNodes", are now marked
18665 obsolete. Resolves ticket 12226.
18666 - Clients don't understand the BadDirectory flag in the consensus
18667 anymore, and ignore it.
18670 - Refactor the function that chooses guard nodes so that it can more
18671 easily be tested; write some tests for it.
18672 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
18673 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
18674 - Create unit tests for format_time_interval(). With bug 13393.
18675 - Add unit tests for tor_timegm signed overflow, tor_timegm and
18676 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
18677 tests (visible) fixes in bug 13476.
18678 - Add a "coverage-html" make target to generate HTML-visualized
18679 coverage results when building with --enable-coverage. (Requires
18680 lcov.) Patch from Kevin Murray.
18681 - Enable the backtrace handler (where supported) when running the
18683 - Revise all unit tests that used the legacy test_* macros to
18684 instead use the recommended tt_* macros. This patch was generated
18685 with coccinelle, to avoid manual errors. Closes ticket 13119.
18687 o Distribution (systemd):
18688 - systemd unit file: only allow tor to write to /var/lib/tor and
18689 /var/log/tor. The rest of the filesystem is accessible for reading
18690 only. Patch by intrigeri; resolves ticket 12751.
18691 - systemd unit file: ensure that the process and all its children
18692 can never gain new privileges. Patch by intrigeri; resolves
18694 - systemd unit file: set up /var/run/tor as writable for the Tor
18695 service. Patch by intrigeri; resolves ticket 13196.
18697 o Removed features (directory authorities):
18698 - Remove code that prevented authorities from listing Tor relays
18699 affected by CVE-2011-2769 as guards. These relays are already
18700 rejected altogether due to the minimum version requirement of
18701 0.2.3.16-alpha. Closes ticket 13152.
18702 - The "AuthDirRejectUnlisted" option no longer has any effect, as
18703 the fingerprints file (approved-routers) has been deprecated.
18704 - Directory authorities do not support being Naming dirauths anymore.
18705 The "NamingAuthoritativeDir" config option is now obsolete.
18706 - Directory authorities do not support giving out the BadDirectory
18708 - Directory authorities no longer advertise or support consensus
18709 methods 1 through 12 inclusive. These consensus methods were
18710 obsolete and/or insecure: maintaining the ability to support them
18711 served no good purpose. Implements part of proposal 215; closes
18714 o Testing (test-network.sh):
18715 - Stop using "echo -n", as some shells' built-in echo doesn't
18716 support "-n". Instead, use "/bin/echo -n". Partially fixes
18718 - Stop an apparent test-network hang when used with make -j2. Fixes
18720 - Add a --delay option to test-network.sh, which configures the
18721 delay before the chutney network tests for data transmission.
18722 Partially implements ticket 13161.
18725 Changes in version 0.2.5.10 - 2014-10-24
18726 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
18728 It adds several new security features, including improved
18729 denial-of-service resistance for relays, new compiler hardening
18730 options, and a system-call sandbox for hardened installations on Linux
18731 (requires seccomp2). The controller protocol has several new features,
18732 resolving IPv6 addresses should work better than before, and relays
18733 should be a little more CPU-efficient. We've added support for more
18734 OpenBSD and FreeBSD transparent proxy types. We've improved the build
18735 system and testing infrastructure to allow unit testing of more parts
18736 of the Tor codebase. Finally, we've addressed several nagging pluggable
18737 transport usability issues, and included numerous other small bugfixes
18738 and features mentioned below.
18740 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
18741 have accumulated many known flaws; everyone should upgrade.
18743 o Deprecated versions:
18744 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
18745 attention for some while.
18748 Changes in version 0.2.5.9-rc - 2014-10-20
18749 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
18750 series. It disables SSL3 in response to the recent "POODLE" attack
18751 (even though POODLE does not affect Tor). It also works around a crash
18752 bug caused by some operating systems' response to the "POODLE" attack
18753 (which does affect Tor). It also contains a few miscellaneous fixes.
18755 o Major security fixes:
18756 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
18757 today support TLS 1.0 or later, so we can safely turn off support
18758 for this old (and insecure) protocol. Fixes bug 13426.
18760 o Major bugfixes (openssl bug workaround):
18761 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
18762 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
18763 13471. This is a workaround for an OpenSSL bug.
18766 - Disable the sandbox name resolver cache when running tor-resolve:
18767 tor-resolve doesn't use the sandbox code, and turning it on was
18768 breaking attempts to do tor-resolve on a non-default server on
18769 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
18771 o Compilation fixes:
18772 - Build and run correctly on systems like OpenBSD-current that have
18773 patched OpenSSL to remove get_cipher_by_char and/or its
18774 implementations. Fixes issue 13325.
18776 o Downgraded warnings:
18777 - Downgrade the severity of the 'unexpected sendme cell from client'
18778 from 'warn' to 'protocol warning'. Closes ticket 8093.
18781 Changes in version 0.2.4.25 - 2014-10-20
18782 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
18783 (even though POODLE does not affect Tor). It also works around a crash
18784 bug caused by some operating systems' response to the "POODLE" attack
18785 (which does affect Tor).
18787 o Major security fixes (also in 0.2.5.9-rc):
18788 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
18789 today support TLS 1.0 or later, so we can safely turn off support
18790 for this old (and insecure) protocol. Fixes bug 13426.
18792 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
18793 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
18794 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
18795 13471. This is a workaround for an OpenSSL bug.
18798 Changes in version 0.2.5.8-rc - 2014-09-22
18799 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
18800 series. It fixes a bug that affects consistency and speed when
18801 connecting to hidden services, and it updates the location of one of
18802 the directory authorities.
18805 - Clients now send the correct address for their chosen rendezvous
18806 point when trying to access a hidden service. They used to send
18807 the wrong address, which would still work some of the time because
18808 they also sent the identity digest of the rendezvous point, and if
18809 the hidden service happened to try connecting to the rendezvous
18810 point from a relay that already had a connection open to it,
18811 the relay would reuse that connection. Now connections to hidden
18812 services should be more robust and faster. Also, this bug meant
18813 that clients were leaking to the hidden service whether they were
18814 on a little-endian (common) or big-endian (rare) system, which for
18815 some users might have reduced their anonymity. Fixes bug 13151;
18816 bugfix on 0.2.1.5-alpha.
18818 o Directory authority changes:
18819 - Change IP address for gabelmoo (v3 directory authority).
18822 Changes in version 0.2.4.24 - 2014-09-22
18823 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
18824 connecting to hidden services, and it updates the location of one of
18825 the directory authorities.
18828 - Clients now send the correct address for their chosen rendezvous
18829 point when trying to access a hidden service. They used to send
18830 the wrong address, which would still work some of the time because
18831 they also sent the identity digest of the rendezvous point, and if
18832 the hidden service happened to try connecting to the rendezvous
18833 point from a relay that already had a connection open to it,
18834 the relay would reuse that connection. Now connections to hidden
18835 services should be more robust and faster. Also, this bug meant
18836 that clients were leaking to the hidden service whether they were
18837 on a little-endian (common) or big-endian (rare) system, which for
18838 some users might have reduced their anonymity. Fixes bug 13151;
18839 bugfix on 0.2.1.5-alpha.
18841 o Directory authority changes:
18842 - Change IP address for gabelmoo (v3 directory authority).
18844 o Minor features (geoip):
18845 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
18849 Changes in version 0.2.5.7-rc - 2014-09-11
18850 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
18851 release series, and some long-standing bugs related to ORPort reachability
18852 testing and failure to send CREATE cells. It is the first release
18853 candidate for the Tor 0.2.5.x series.
18855 o Major bugfixes (client, startup):
18856 - Start making circuits as soon as DisabledNetwork is turned off.
18857 When Tor started with DisabledNetwork set, it would correctly
18858 conclude that it shouldn't build circuits, but it would mistakenly
18859 cache this conclusion, and continue believing it even when
18860 DisableNetwork is set to 0. Fixes the bug introduced by the fix
18861 for bug 11200; bugfix on 0.2.5.4-alpha.
18862 - Resume expanding abbreviations for command-line options. The fix
18863 for bug 4647 accidentally removed our hack from bug 586 that
18864 rewrote HashedControlPassword to __HashedControlSessionPassword
18865 when it appears on the commandline (which allowed the user to set
18866 her own HashedControlPassword in the torrc file while the
18867 controller generates a fresh session password for each run). Fixes
18868 bug 12948; bugfix on 0.2.5.1-alpha.
18869 - Warn about attempts to run hidden services and relays in the same
18870 process: that's probably not a good idea. Closes ticket 12908.
18872 o Major bugfixes (relay):
18873 - Avoid queuing or sending destroy cells for circuit ID zero when we
18874 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
18875 Found and fixed by "cypherpunks".
18876 - Fix ORPort reachability detection on relays running behind a
18877 proxy, by correctly updating the "local" mark on the controlling
18878 channel when changing the address of an or_connection_t after the
18879 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
18881 o Minor features (bridge):
18882 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
18883 cookie file for the ExtORPort g+r by default.
18885 o Minor features (geoip):
18886 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
18889 o Minor bugfixes (logging):
18890 - Reduce the log severity of the "Pluggable transport proxy does not
18891 provide any needed transports and will not be launched." message,
18892 since Tor Browser includes several ClientTransportPlugin lines in
18893 its torrc-defaults file, leading every Tor Browser user who looks
18894 at her logs to see these notices and wonder if they're dangerous.
18895 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
18896 - Downgrade "Unexpected onionskin length after decryption" warning
18897 to a protocol-warn, since there's nothing relay operators can do
18898 about a client that sends them a malformed create cell. Resolves
18899 bug 12996; bugfix on 0.0.6rc1.
18900 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
18901 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
18902 - When logging information about an EXTEND2 or EXTENDED2 cell, log
18903 their names correctly. Fixes part of bug 12700; bugfix
18905 - When logging information about a relay cell whose command we don't
18906 recognize, log its command as an integer. Fixes part of bug 12700;
18907 bugfix on 0.2.1.10-alpha.
18908 - Escape all strings from the directory connection before logging
18909 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
18911 o Minor bugfixes (controller):
18912 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
18913 bug 12864; bugfix on 0.2.5.1-alpha.
18914 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
18915 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
18918 o Minor bugfixes (compilation):
18919 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
18920 bugfix on 0.2.5.5-alpha.
18921 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
18922 0.2.5.1-alpha. Patch from "NewEraCracker".
18923 - In routerlist_assert_ok(), don't take the address of a
18924 routerinfo's cache_info member unless that routerinfo is non-NULL.
18925 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
18926 - Fix a large number of false positive warnings from the clang
18927 analyzer static analysis tool. This should make real warnings
18928 easier for clang analyzer to find. Patch from "teor". Closes
18931 o Distribution (systemd):
18932 - Verify configuration file via ExecStartPre in the systemd unit
18933 file. Patch from intrigeri; resolves ticket 12730.
18934 - Explicitly disable RunAsDaemon in the systemd unit file. Our
18935 current systemd unit uses "Type = simple", so systemd does not
18936 expect tor to fork. If the user has "RunAsDaemon 1" in their
18937 torrc, then things won't work as expected. This is e.g. the case
18938 on Debian (and derivatives), since there we pass "--defaults-torrc
18939 /usr/share/tor/tor-service-defaults-torrc" (that contains
18940 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
18944 - Adjust the URLs in the README to refer to the new locations of
18945 several documents on the website. Fixes bug 12830. Patch from
18947 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
18951 Changes in version 0.2.5.6-alpha - 2014-07-28
18952 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
18953 risk from guard rotation, and fixes a variety of other issues to get
18954 us closer to a release candidate.
18956 o Major features (also in 0.2.4.23):
18957 - Make the number of entry guards configurable via a new
18958 NumEntryGuards consensus parameter, and the number of directory
18959 guards configurable via a new NumDirectoryGuards consensus
18960 parameter. Implements ticket 12688.
18962 o Major bugfixes (also in 0.2.4.23):
18963 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
18964 implementation that caused incorrect results on 32-bit
18965 implementations when certain malformed inputs were used along with
18966 a small class of private ntor keys. This bug does not currently
18967 appear to allow an attacker to learn private keys or impersonate a
18968 Tor server, but it could provide a means to distinguish 32-bit Tor
18969 implementations from 64-bit Tor implementations. Fixes bug 12694;
18970 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
18974 - Perform circuit cleanup operations even when circuit
18975 construction operations are disabled (because the network is
18976 disabled, or because there isn't enough directory information).
18977 Previously, when we were not building predictive circuits, we
18978 were not closing expired circuits either. Fixes bug 8387; bugfix on
18979 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
18980 became more strict about when we have "enough directory information
18981 to build circuits".
18984 - Authorities now assign the Guard flag to the fastest 25% of the
18985 network (it used to be the fastest 50%). Also raise the consensus
18986 weight that guarantees the Guard flag from 250 to 2000. For the
18987 current network, this results in about 1100 guards, down from 2500.
18988 This step paves the way for moving the number of entry guards
18989 down to 1 (proposal 236) while still providing reasonable expected
18990 performance for most users. Implements ticket 12690.
18991 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
18993 - Slightly enhance the diagnostic message for bug 12184.
18995 o Minor bugfixes (also in 0.2.4.23):
18996 - Warn and drop the circuit if we receive an inbound 'relay early'
18997 cell. Those used to be normal to receive on hidden service circuits
18998 due to bug 1038, but the buggy Tor versions are long gone from
18999 the network so we can afford to resume watching for them. Resolves
19000 the rest of bug 1038; bugfix on 0.2.1.19.
19001 - Correct a confusing error message when trying to extend a circuit
19002 via the control protocol but we don't know a descriptor or
19003 microdescriptor for one of the specified relays. Fixes bug 12718;
19004 bugfix on 0.2.3.1-alpha.
19007 - Fix compilation when building with bufferevents enabled. (This
19008 configuration is still not expected to work, however.)
19009 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
19010 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
19012 - Compile correctly with builds and forks of OpenSSL (such as
19013 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
19014 0.2.1.1-alpha. Patch from "dhill".
19017 Changes in version 0.2.4.23 - 2014-07-28
19018 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
19019 guard rotation, and also backports several important fixes from the
19020 Tor 0.2.5 alpha release series.
19023 - Clients now look at the "usecreatefast" consensus parameter to
19024 decide whether to use CREATE_FAST or CREATE cells for the first hop
19025 of their circuit. This approach can improve security on connections
19026 where Tor's circuit handshake is stronger than the available TLS
19027 connection security levels, but the tradeoff is more computational
19028 load on guard relays. Implements proposal 221. Resolves ticket 9386.
19029 - Make the number of entry guards configurable via a new
19030 NumEntryGuards consensus parameter, and the number of directory
19031 guards configurable via a new NumDirectoryGuards consensus
19032 parameter. Implements ticket 12688.
19035 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
19036 implementation that caused incorrect results on 32-bit
19037 implementations when certain malformed inputs were used along with
19038 a small class of private ntor keys. This bug does not currently
19039 appear to allow an attacker to learn private keys or impersonate a
19040 Tor server, but it could provide a means to distinguish 32-bit Tor
19041 implementations from 64-bit Tor implementations. Fixes bug 12694;
19042 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
19046 - Warn and drop the circuit if we receive an inbound 'relay early'
19047 cell. Those used to be normal to receive on hidden service circuits
19048 due to bug 1038, but the buggy Tor versions are long gone from
19049 the network so we can afford to resume watching for them. Resolves
19050 the rest of bug 1038; bugfix on 0.2.1.19.
19051 - Correct a confusing error message when trying to extend a circuit
19052 via the control protocol but we don't know a descriptor or
19053 microdescriptor for one of the specified relays. Fixes bug 12718;
19054 bugfix on 0.2.3.1-alpha.
19055 - Avoid an illegal read from stack when initializing the TLS
19056 module using a version of OpenSSL without all of the ciphers
19057 used by the v2 link handshake. Fixes bug 12227; bugfix on
19058 0.2.4.8-alpha. Found by "starlight".
19061 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
19065 Changes in version 0.2.5.5-alpha - 2014-06-18
19066 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
19067 0.2.5.x release series, including a couple of DoS issues, some
19068 performance regressions, a large number of bugs affecting the Linux
19069 seccomp2 sandbox code, and various other bugfixes. It also adds
19070 diagnostic bugfixes for a few tricky issues that we're trying to
19073 o Major features (security, traffic analysis resistance):
19074 - Several major improvements to the algorithm used to decide when to
19075 close TLS connections. Previous versions of Tor closed connections
19076 at a fixed interval after the last time a non-padding cell was
19077 sent over the connection, regardless of the target of the
19078 connection. Now, we randomize the intervals by adding up to 50% of
19079 their base value, we measure the length of time since connection
19080 last had at least one circuit, and we allow connections to known
19081 ORs to remain open a little longer (15 minutes instead of 3
19082 minutes minimum). These changes should improve Tor's resistance
19083 against some kinds of traffic analysis, and lower some overhead
19084 from needlessly closed connections. Fixes ticket 6799.
19085 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
19087 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
19088 - Fix a memory leak that could occur if a microdescriptor parse
19089 fails during the tokenizing step. This bug could enable a memory
19090 exhaustion attack by directory servers. Fixes bug 11649; bugfix
19093 o Major bugfixes (security, directory authorities):
19094 - Directory authorities now include a digest of each relay's
19095 identity key as a part of its microdescriptor.
19097 This is a workaround for bug 11743 (reported by "cypherpunks"),
19098 where Tor clients do not support receiving multiple
19099 microdescriptors with the same SHA256 digest in the same
19100 consensus. When clients receive a consensus like this, they only
19101 use one of the relays. Without this fix, a hostile relay could
19102 selectively disable some client use of target relays by
19103 constructing a router descriptor with a different identity and the
19104 same microdescriptor parameters and getting the authorities to
19105 list it in a microdescriptor consensus. This fix prevents an
19106 attacker from causing a microdescriptor collision, because the
19107 router's identity is not forgeable.
19109 o Major bugfixes (relay):
19110 - Use a direct dirport connection when uploading non-anonymous
19111 descriptors to the directory authorities. Previously, relays would
19112 incorrectly use tunnel connections under a fairly wide variety of
19113 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
19114 - When a circuit accidentally has the same circuit ID for its
19115 forward and reverse direction, correctly detect the direction of
19116 cells using that circuit. Previously, this bug made roughly one
19117 circuit in a million non-functional. Fixes bug 12195; this is a
19118 bugfix on every version of Tor.
19120 o Major bugfixes (client, pluggable transports):
19121 - When managing pluggable transports, use OS notification facilities
19122 to learn if they have crashed, and don't attempt to kill any
19123 process that has already exited. Fixes bug 8746; bugfix
19126 o Minor features (diagnostic):
19127 - When logging a warning because of bug 7164, additionally check the
19128 hash table for consistency (as proposed on ticket 11737). This may
19129 help diagnose bug 7164.
19130 - When we log a heartbeat, log how many one-hop circuits we have
19131 that are at least 30 minutes old, and log status information about
19132 a few of them. This is an attempt to track down bug 8387.
19133 - When encountering an unexpected CR while writing text to a file on
19134 Windows, log the name of the file. Should help diagnosing
19136 - Give more specific warnings when a client notices that an onion
19137 handshake has failed. Fixes ticket 9635.
19138 - Add significant new logging code to attempt to diagnose bug 12184,
19139 where relays seem to run out of available circuit IDs.
19140 - Improve the diagnostic log message for bug 8387 even further to
19141 try to improve our odds of figuring out why one-hop directory
19142 circuits sometimes do not get closed.
19144 o Minor features (security, memory management):
19145 - Memory allocation tricks (mempools and buffer freelists) are now
19146 disabled by default. You can turn them back on with
19147 --enable-mempools and --enable-buf-freelists respectively. We're
19148 disabling these features because malloc performance is good enough
19149 on most platforms, and a similar feature in OpenSSL exacerbated
19150 exploitation of the Heartbleed attack. Resolves ticket 11476.
19152 o Minor features (security):
19153 - Apply the secure SipHash-2-4 function to the hash table mapping
19154 circuit IDs and channels to circuits. We missed this one when we
19155 were converting all the other hash functions to use SipHash back
19156 in 0.2.5.3-alpha. Resolves ticket 11750.
19158 o Minor features (build):
19159 - The configure script has a --disable-seccomp option to turn off
19160 support for libseccomp on systems that have it, in case it (or
19161 Tor's use of it) is broken. Resolves ticket 11628.
19163 o Minor features (other):
19164 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
19167 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
19168 - When running a hidden service, do not allow TunneledDirConns 0;
19169 this will keep the hidden service from running, and also
19170 make it publish its descriptors directly over HTTP. Fixes bug 10849;
19171 bugfix on 0.2.1.1-alpha.
19173 o Minor bugfixes (performance):
19174 - Avoid a bug where every successful connection made us recompute
19175 the flag telling us whether we have sufficient information to
19176 build circuits. Previously, we would forget our cached value
19177 whenever we successfully opened a channel (or marked a router as
19178 running or not running for any other reason), regardless of
19179 whether we had previously believed the router to be running. This
19180 forced us to run an expensive update operation far too often.
19181 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
19182 - Avoid using tor_memeq() for checking relay cell integrity. This
19183 removes a possible performance bottleneck. Fixes part of bug
19184 12169; bugfix on 0.2.1.31.
19186 o Minor bugfixes (compilation):
19187 - Fix compilation of test_status.c when building with MVSC. Bugfix
19188 on 0.2.5.4-alpha. Patch from Gisle Vanem.
19189 - Resolve GCC complaints on OpenBSD about discarding constness in
19190 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
19191 on 0.1.1.23. Patch from Dana Koch.
19192 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
19193 treatment of long and time_t as comparable types. Fixes part of
19194 bug 11633. Patch from Dana Koch.
19195 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
19196 11623; bugfix on 0.2.5.3-alpha.
19197 - When deciding whether to build the 64-bit curve25519
19198 implementation, detect platforms where we can compile 128-bit
19199 arithmetic but cannot link it. Fixes bug 11729; bugfix on
19200 0.2.4.8-alpha. Patch from "conradev".
19201 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
19202 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
19203 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
19206 o Minor bugfixes (Directory server):
19207 - When sending a compressed set of descriptors or microdescriptors,
19208 make sure to finalize the zlib stream. Previously, we would write
19209 all the compressed data, but if the last descriptor we wanted to
19210 send was missing or too old, we would not mark the stream as
19211 finished. This caused problems for decompression tools. Fixes bug
19212 11648; bugfix on 0.1.1.23.
19214 o Minor bugfixes (Linux seccomp sandbox):
19215 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
19216 11622; bugfix on 0.2.5.1-alpha.
19217 - Avoid crashing when re-opening listener ports with the seccomp
19218 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
19219 - Avoid crashing with the seccomp sandbox enabled along with
19220 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
19221 - When we receive a SIGHUP with the sandbox enabled, correctly
19222 support rotating our log files. Fixes bug 12032; bugfix
19224 - Avoid crash when running with sandboxing enabled and
19225 DirReqStatistics not disabled. Fixes bug 12035; bugfix
19227 - Fix a "BUG" warning when trying to write bridge-stats files with
19228 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
19230 - Prevent the sandbox from crashing on startup when run with the
19231 --enable-expensive-hardening configuration option. Fixes bug
19232 11477; bugfix on 0.2.5.4-alpha.
19233 - When running with DirPortFrontPage and sandboxing both enabled,
19234 reload the DirPortFrontPage correctly when restarting. Fixes bug
19235 12028; bugfix on 0.2.5.1-alpha.
19236 - Don't try to enable the sandbox when using the Tor binary to check
19237 its configuration, hash a passphrase, or so on. Doing so was
19238 crashing on startup for some users. Fixes bug 11609; bugfix
19240 - Avoid warnings when running with sandboxing and node statistics
19241 enabled at the same time. Fixes part of 12064; bugfix on
19242 0.2.5.1-alpha. Patch from Michael Wolf.
19243 - Avoid warnings when running with sandboxing enabled at the same
19244 time as cookie authentication, hidden services, or directory
19245 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
19246 - Do not allow options that require calls to exec to be enabled
19247 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
19248 bug 12043; bugfix on 0.2.5.1-alpha.
19249 - Handle failures in getpwnam()/getpwuid() when running with the
19250 User option set and the Linux syscall sandbox enabled. Fixes bug
19251 11946; bugfix on 0.2.5.1-alpha.
19252 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
19253 to avoid calling getaddrinfo() after installing the sandbox
19254 filters. Previously, it preloaded a cache with the IPv4 address
19255 for our hostname, and nothing else. Now, it loads the cache with
19256 every address that it used to initialize the Tor process. Fixes
19257 bug 11970; bugfix on 0.2.5.1-alpha.
19259 o Minor bugfixes (pluggable transports):
19260 - Enable the ExtORPortCookieAuthFile option, to allow changing the
19261 default location of the authentication token for the extended OR
19262 Port as used by sever-side pluggable transports. We had
19263 implemented this option before, but the code to make it settable
19264 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
19265 - Avoid another 60-second delay when starting Tor in a pluggable-
19266 transport-using configuration when we already have cached
19267 descriptors for our bridges. Fixes bug 11965; bugfix
19270 o Minor bugfixes (client):
19271 - Avoid "Tried to open a socket with DisableNetwork set" warnings
19272 when starting a client with bridges configured and DisableNetwork
19273 set. (Tor launcher starts Tor with DisableNetwork set the first
19274 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
19276 o Minor bugfixes (testing):
19277 - The Python parts of the test scripts now work on Python 3 as well
19278 as Python 2, so systems where '/usr/bin/python' is Python 3 will
19279 no longer have the tests break. Fixes bug 11608; bugfix
19281 - When looking for versions of python that we could run the tests
19282 with, check for "python2.7" and "python3.3"; previously we were
19283 only looking for "python", "python2", and "python3". Patch from
19284 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
19285 - Fix all valgrind warnings produced by the unit tests. There were
19286 over a thousand memory leak warnings previously, mostly produced
19287 by forgetting to free things in the unit test code. Fixes bug
19288 11618, bugfixes on many versions of Tor.
19290 o Minor bugfixes (tor-fw-helper):
19291 - Give a correct log message when tor-fw-helper fails to launch.
19292 (Previously, we would say something like "tor-fw-helper sent us a
19293 string we could not parse".) Fixes bug 9781; bugfix
19296 o Minor bugfixes (relay, threading):
19297 - Check return code on spawn_func() in cpuworker code, so that we
19298 don't think we've spawned a nonworking cpuworker and write junk to
19299 it forever. Fix related to bug 4345; bugfix on all released Tor
19300 versions. Found by "skruffy".
19301 - Use a pthread_attr to make sure that spawn_func() cannot return an
19302 error while at the same time launching a thread. Fix related to
19303 bug 4345; bugfix on all released Tor versions. Reported
19306 o Minor bugfixes (relay, oom prevention):
19307 - Correctly detect the total available system memory. We tried to do
19308 this in 0.2.5.4-alpha, but the code was set up to always return an
19309 error value, even on success. Fixes bug 11805; bugfix
19312 o Minor bugfixes (relay, other):
19313 - We now drop CREATE cells for already-existent circuit IDs and for
19314 zero-valued circuit IDs, regardless of other factors that might
19315 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
19317 - Avoid an illegal read from stack when initializing the TLS module
19318 using a version of OpenSSL without all of the ciphers used by the
19319 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
19321 - When rejecting DATA cells for stream_id zero, still count them
19322 against the circuit's deliver window so that we don't fail to send
19323 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
19325 o Minor bugfixes (logging):
19326 - Fix a misformatted log message about delayed directory fetches.
19327 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
19328 - Squelch a spurious LD_BUG message "No origin circuit for
19329 successful SOCKS stream" in certain hidden service failure cases;
19333 - Include a tor.service file in contrib/dist for use with systemd.
19334 Some distributions will be able to use this file unmodified;
19335 others will need to tweak it, or write their own. Patch from Jamie
19336 Nguyen; resolves ticket 8368.
19339 - Clean up several option names in the manpage to match their real
19340 names, add the missing documentation for a couple of testing and
19341 directory authority options, remove the documentation for a
19342 V2-directory fetching option that no longer exists. Resolves
19344 - Correct the documentation so that it lists the correct directory
19345 for the stats files. (They are in a subdirectory called "stats",
19347 - In the manpage, move more authority-only options into the
19348 directory authority section so that operators of regular directory
19349 caches don't get confused.
19352 - The contrib directory has been sorted and tidied. Before, it was
19353 an unsorted dumping ground for useful and not-so-useful things.
19354 Now, it is divided based on functionality, and the items which
19355 seemed to be nonfunctional or useless have been removed. Resolves
19356 ticket 8966; based on patches from "rl1987".
19359 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
19360 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
19361 - The TunnelDirConns and PreferTunnelledDirConns options no longer
19362 exist; tunneled directory connections have been available since
19363 0.1.2.5-alpha, and turning them off is not a good idea. This is a
19364 brute-force fix for 10849, where "TunnelDirConns 0" would break
19368 Changes in version 0.2.4.22 - 2014-05-16
19369 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
19370 alpha release series. These include blocking all authority signing
19371 keys that may have been affected by the OpenSSL "heartbleed" bug,
19372 choosing a far more secure set of TLS ciphersuites by default, closing
19373 a couple of memory leaks that could be used to run a target relay out
19374 of RAM, and several others.
19376 o Major features (security, backport from 0.2.5.4-alpha):
19377 - Block authority signing keys that were used on authorities
19378 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
19379 don't have any evidence that these keys _were_ compromised; we're
19380 doing this to be prudent.) Resolves ticket 11464.
19382 o Major bugfixes (security, OOM):
19383 - Fix a memory leak that could occur if a microdescriptor parse
19384 fails during the tokenizing step. This bug could enable a memory
19385 exhaustion attack by directory servers. Fixes bug 11649; bugfix
19388 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
19389 - The relay ciphersuite list is now generated automatically based on
19390 uniform criteria, and includes all OpenSSL ciphersuites with
19391 acceptable strength and forward secrecy. Previously, we had left
19392 some perfectly fine ciphersuites unsupported due to omission or
19393 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
19394 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
19395 - Relays now trust themselves to have a better view than clients of
19396 which TLS ciphersuites are better than others. (Thanks to bug
19397 11513, the relay list is now well-considered, whereas the client
19398 list has been chosen mainly for anti-fingerprinting purposes.)
19399 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
19400 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
19401 AES128. Resolves ticket 11528.
19402 - Clients now try to advertise the same list of ciphersuites as
19403 Firefox 28. This change enables selection of (fast) GCM
19404 ciphersuites, disables some strange old ciphers, and stops
19405 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
19406 Resolves ticket 11438.
19408 o Minor bugfixes (configuration, security):
19409 - When running a hidden service, do not allow TunneledDirConns 0:
19410 trying to set that option together with a hidden service would
19411 otherwise prevent the hidden service from running, and also make
19412 it publish its descriptors directly over HTTP. Fixes bug 10849;
19413 bugfix on 0.2.1.1-alpha.
19415 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
19416 - Avoid sending a garbage value to the controller when a circuit is
19417 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
19419 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
19420 - Stop leaking memory when we successfully resolve a PTR record.
19421 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
19423 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
19424 - Avoid 60-second delays in the bootstrapping process when Tor is
19425 launching for a second time while using bridges. Fixes bug 9229;
19426 bugfix on 0.2.0.3-alpha.
19428 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
19429 - Give the correct URL in the warning message when trying to run a
19430 relay on an ancient version of Windows. Fixes bug 9393.
19432 o Minor bugfixes (compilation):
19433 - Fix a compilation error when compiling with --disable-curve25519.
19434 Fixes bug 9700; bugfix on 0.2.4.17-rc.
19437 - Downgrade the warning severity for the the "md was still
19438 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
19439 for trying to diagnose this bug, and the current warning in
19440 earlier versions of tor achieves nothing useful. Addresses warning
19443 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
19444 - When we run out of usable circuit IDs on a channel, log only one
19445 warning for the whole channel, and describe how many circuits
19446 there were on the channel. Fixes part of ticket 11553.
19448 o Minor features (security, backport from 0.2.5.4-alpha):
19449 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
19450 leave the default at 8GBytes), to better support Raspberry Pi
19451 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
19453 o Documentation (backport from 0.2.5.4-alpha):
19454 - Correctly document that we search for a system torrc file before
19455 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
19459 Changes in version 0.2.5.4-alpha - 2014-04-25
19460 Tor 0.2.5.4-alpha includes several security and performance
19461 improvements for clients and relays, including blacklisting authority
19462 signing keys that were used while susceptible to the OpenSSL
19463 "heartbleed" bug, fixing two expensive functions on busy relays,
19464 improved TLS ciphersuite preference lists, support for run-time
19465 hardening on compilers that support AddressSanitizer, and more work on
19466 the Linux sandbox code.
19468 There are also several usability fixes for clients (especially clients
19469 that use bridges), two new TransPort protocols supported (one on
19470 OpenBSD, one on FreeBSD), and various other bugfixes.
19472 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
19473 have accumulated many known flaws; everyone should upgrade.
19475 o Major features (security):
19476 - If you don't specify MaxMemInQueues yourself, Tor now tries to
19477 pick a good value based on your total system memory. Previously,
19478 the default was always 8 GB. You can still override the default by
19479 setting MaxMemInQueues yourself. Resolves ticket 11396.
19480 - Block authority signing keys that were used on authorities
19481 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
19482 don't have any evidence that these keys _were_ compromised; we're
19483 doing this to be prudent.) Resolves ticket 11464.
19485 o Major features (relay performance):
19486 - Speed up server-side lookups of rendezvous and introduction point
19487 circuits by using hashtables instead of linear searches. These
19488 functions previously accounted between 3 and 7% of CPU usage on
19489 some busy relays. Resolves ticket 9841.
19490 - Avoid wasting CPU when extending a circuit over a channel that is
19491 nearly out of circuit IDs. Previously, we would do a linear scan
19492 over possible circuit IDs before finding one or deciding that we
19493 had exhausted our possibilities. Now, we try at most 64 random
19494 circuit IDs before deciding that we probably won't succeed. Fixes
19495 a possible root cause of ticket 11553.
19497 o Major features (seccomp2 sandbox, Linux only):
19498 - The seccomp2 sandbox can now run a test network for multiple hours
19499 without crashing. The sandbox is still experimental, and more bugs
19500 will probably turn up. To try it, enable "Sandbox 1" on a Linux
19501 host. Resolves ticket 11351.
19502 - Strengthen sandbox code: the sandbox can now test the arguments
19503 for rename(), and blocks _sysctl() entirely. Resolves another part
19505 - When the sandbox blocks a system call, it now tries to log a stack
19506 trace before exiting. Resolves ticket 11465.
19508 o Major bugfixes (TLS cipher selection):
19509 - The relay ciphersuite list is now generated automatically based on
19510 uniform criteria, and includes all OpenSSL ciphersuites with
19511 acceptable strength and forward secrecy. Previously, we had left
19512 some perfectly fine ciphersuites unsupported due to omission or
19513 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
19514 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
19515 - Relays now trust themselves to have a better view than clients of
19516 which TLS ciphersuites are better than others. (Thanks to bug
19517 11513, the relay list is now well-considered, whereas the client
19518 list has been chosen mainly for anti-fingerprinting purposes.)
19519 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
19520 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
19521 AES128. Resolves ticket 11528.
19522 - Clients now try to advertise the same list of ciphersuites as
19523 Firefox 28. This change enables selection of (fast) GCM
19524 ciphersuites, disables some strange old ciphers, and stops
19525 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
19526 Resolves ticket 11438.
19528 o Major bugfixes (bridge client):
19529 - Avoid 60-second delays in the bootstrapping process when Tor is
19530 launching for a second time while using bridges. Fixes bug 9229;
19531 bugfix on 0.2.0.3-alpha.
19533 o Minor features (transparent proxy, *BSD):
19534 - Support FreeBSD's ipfw firewall interface for TransPort ports on
19535 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
19536 10267; patch from "yurivict".
19537 - Support OpenBSD's divert-to rules with the pf firewall for
19538 transparent proxy ports. To enable it, set "TransProxyType
19539 pf-divert". This allows Tor to run a TransPort transparent proxy
19540 port on OpenBSD 4.4 or later without root privileges. See the
19541 pf.conf(5) manual page for information on configuring pf to use
19542 divert-to rules. Closes ticket 10896; patch from Dana Koch.
19544 o Minor features (security):
19545 - New --enable-expensive-hardening option to enable security
19546 hardening options that consume nontrivial amounts of CPU and
19547 memory. Right now, this includes AddressSanitizer and UbSan, which
19548 are supported in newer versions of GCC and Clang. Closes ticket
19551 o Minor features (log verbosity):
19552 - Demote the message that we give when a flushing connection times
19553 out for too long from NOTICE to INFO. It was usually meaningless.
19554 Resolves ticket 5286.
19555 - Don't log so many notice-level bootstrapping messages at startup
19556 about downloading descriptors. Previously, we'd log a notice
19557 whenever we learned about more routers. Now, we only log a notice
19558 at every 5% of progress. Fixes bug 9963.
19559 - Warn less verbosely when receiving a malformed
19560 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
19561 - When we run out of usable circuit IDs on a channel, log only one
19562 warning for the whole channel, and describe how many circuits
19563 there were on the channel. Fixes part of ticket 11553.
19565 o Minor features (relay):
19566 - If a circuit timed out for at least 3 minutes, check if we have a
19567 new external IP address, and publish a new descriptor with the new
19568 IP address if it changed. Resolves ticket 2454.
19570 o Minor features (controller):
19571 - Make the entire exit policy available from the control port via
19572 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
19574 - Because of the fix for ticket 11396, the real limit for memory
19575 usage may no longer match the configured MaxMemInQueues value. The
19576 real limit is now exposed via GETINFO limits/max-mem-in-queues.
19578 o Minor features (bridge client):
19579 - Report a more useful failure message when we can't connect to a
19580 bridge because we don't have the right pluggable transport
19581 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
19583 o Minor features (diagnostic):
19584 - Add more log messages to diagnose bug 7164, which causes
19585 intermittent "microdesc_free() called but md was still referenced"
19586 warnings. We now include more information, to figure out why we
19587 might be cleaning a microdescriptor for being too old if it's
19588 still referenced by a live node_t object.
19590 o Minor bugfixes (client, DNSPort):
19591 - When using DNSPort, try to respond to AAAA requests with AAAA
19592 answers. Previously, we hadn't looked at the request type when
19593 deciding which answer type to prefer. Fixes bug 10468; bugfix on
19595 - When receiving a DNS query for an unsupported record type, reply
19596 with no answer rather than with a NOTIMPL error. This behavior
19597 isn't correct either, but it will break fewer client programs, we
19598 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
19601 o Minor bugfixes (exit relay):
19602 - Stop leaking memory when we successfully resolve a PTR record.
19603 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
19605 o Minor bugfixes (bridge client):
19606 - Stop accepting bridge lines containing hostnames. Doing so would
19607 cause clients to perform DNS requests on the hostnames, which was
19608 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
19609 - Avoid a 60-second delay in the bootstrapping process when a Tor
19610 client with pluggable transports re-reads its configuration at
19611 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
19613 o Minor bugfixes (client, logging during bootstrap):
19614 - Warn only once if we start logging in an unsafe way. Previously,
19615 we complain as many times as we had problems. Fixes bug 9870;
19616 bugfix on 0.2.5.1-alpha.
19617 - Only report the first fatal bootstrap error on a given OR
19618 connection. This stops us from telling the controller bogus error
19619 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
19620 - Be more helpful when trying to run sandboxed on Linux without
19621 libseccomp. Instead of saying "Sandbox is not implemented on this
19622 platform", we now explain that we need to be built with
19623 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
19624 - Avoid generating spurious warnings when starting with
19625 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
19628 o Minor bugfixes (closing OR connections):
19629 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
19630 check if it's an or_connection_t and correctly call
19631 connection_or_close_for_error() rather than
19632 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
19634 - When closing all connections on setting DisableNetwork to 1, use
19635 connection_or_close_normally() rather than closing OR connections
19636 out from under the channel layer. Fixes bug 11306; bugfix on
19639 o Minor bugfixes (controller):
19640 - Avoid sending a garbage value to the controller when a circuit is
19641 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
19643 o Minor bugfixes (tor-fw-helper):
19644 - Allow tor-fw-helper to build again by adding src/ext to its
19645 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
19647 o Minor bugfixes (bridges):
19648 - Avoid potential crashes or bad behavior when launching a
19649 server-side managed proxy with ORPort or ExtORPort temporarily
19650 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
19652 o Minor bugfixes (platform-specific):
19653 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
19654 bug 11426; bugfix on 0.2.5.3-alpha.
19655 - When dumping a malformed directory object to disk, save it in
19656 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
19658 - Don't report failures from make_socket_reuseable() on incoming
19659 sockets on OSX: this can happen when incoming connections close
19660 early. Fixes bug 10081.
19662 o Minor bugfixes (trivial memory leaks):
19663 - Fix a small memory leak when signing a directory object. Fixes bug
19664 11275; bugfix on 0.2.4.13-alpha.
19665 - Free placeholder entries in our circuit table at exit; fixes a
19666 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
19667 - Don't re-initialize a second set of OpenSSL mutexes when starting
19668 up. Previously, we'd make one set of mutexes, and then immediately
19669 replace them with another. Fixes bug 11726; bugfix on
19671 - Resolve some memory leaks found by coverity in the unit tests, on
19672 exit in tor-gencert, and on a failure to compute digests for our
19673 own keys when generating a v3 networkstatus vote. These leaks
19674 should never have affected anyone in practice.
19676 o Minor bugfixes (hidden service):
19677 - Only retry attempts to connect to a chosen rendezvous point 8
19678 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
19680 o Minor bugfixes (misc code correctness):
19681 - Fix various instances of undefined behavior in channeltls.c,
19682 tor_memmem(), and eventdns.c that would cause us to construct
19683 pointers to memory outside an allocated object. (These invalid
19684 pointers were not accessed, but C does not even allow them to
19685 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
19686 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
19687 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
19688 fix some miscellaneous errors in our tests and codebase. Fixes bug
19689 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
19690 - Always check return values for unlink, munmap, UnmapViewOfFile;
19691 check strftime return values more often. In some cases all we can
19692 do is report a warning, but this may help prevent deeper bugs from
19693 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
19695 - Fix numerous warnings from the clang "scan-build" static analyzer.
19696 Some of these are programming style issues; some of them are false
19697 positives that indicated awkward code; some are undefined behavior
19698 cases related to constructing (but not using) invalid pointers;
19699 some are assumptions about API behavior; some are (harmlessly)
19700 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
19701 correct; and one or two are genuine bugs that weren't reachable
19702 from the rest of the program. Fixes bug 8793; bugfixes on many,
19706 - Build the torify.1 manpage again. Previously, we were only trying
19707 to build it when also building tor-fw-helper. That's why we didn't
19708 notice that we'd broken the ability to build it. Fixes bug 11321;
19709 bugfix on 0.2.5.1-alpha.
19710 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
19711 11061; bugfix on 0.2.4.7-alpha.
19712 - Correctly document that we search for a system torrc file before
19713 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
19715 - Resolve warnings from Doxygen.
19717 o Code simplifications and refactoring:
19718 - Remove is_internal_IP() function. Resolves ticket 4645.
19719 - Remove unused function circuit_dump_by_chan from circuitlist.c.
19720 Closes issue 9107; patch from "marek".
19721 - Change our use of the ENUM_BF macro to avoid declarations that
19724 o Deprecated versions:
19725 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
19726 attention for some while. Directory authorities no longer accept
19727 descriptors from relays running any version of Tor prior to Tor
19728 0.2.3.16-alpha. Resolves ticket 11149.
19731 - New macros in test.h to simplify writing mock-functions for unit
19732 tests. Part of ticket 11507. Patch from Dana Koch.
19733 - Complete tests for the status.c module. Resolves ticket 11507.
19734 Patch from Dana Koch.
19737 - Remove all code for the long unused v1 directory protocol.
19738 Resolves ticket 11070.
19741 Changes in version 0.2.5.3-alpha - 2014-03-22
19742 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
19743 two new anti-DoS features for Tor relays, resolves a bug that kept
19744 SOCKS5 support for IPv6 from working, fixes several annoying usability
19745 issues for bridge users, and removes more old code for unused
19748 The Tor 0.2.5.x release series is now in patch-freeze: no feature
19749 patches not already written will be considered for inclusion in 0.2.5.x.
19751 o Major features (relay security, DoS-resistance):
19752 - When deciding whether we have run out of memory and we need to
19753 close circuits, also consider memory allocated in buffers for
19754 streams attached to each circuit.
19756 This change, which extends an anti-DoS feature introduced in
19757 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
19758 better resist more memory-based DoS attacks than before. Since the
19759 MaxMemInCellQueues option now applies to all queues, it is renamed
19760 to MaxMemInQueues. This feature fixes bug 10169.
19761 - Avoid hash-flooding denial-of-service attacks by using the secure
19762 SipHash-2-4 hash function for our hashtables. Without this
19763 feature, an attacker could degrade performance of a targeted
19764 client or server by flooding their data structures with a large
19765 number of entries to be stored at the same hash table position,
19766 thereby slowing down the Tor instance. With this feature, hash
19767 table positions are derived from a randomized cryptographic key,
19768 and an attacker cannot predict which entries will collide. Closes
19770 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
19771 the default at 8GBytes), to better support Raspberry Pi users. Fixes
19772 bug 9686; bugfix on 0.2.4.14-alpha.
19774 o Minor features (bridges, pluggable transports):
19775 - Bridges now write the SHA1 digest of their identity key
19776 fingerprint (that is, a hash of a hash of their public key) to
19777 notice-level logs, and to a new hashed-fingerprint file. This
19778 information will help bridge operators look up their bridge in
19779 Globe and similar tools. Resolves ticket 10884.
19780 - Improve the message that Tor displays when running as a bridge
19781 using pluggable transports without an Extended ORPort listener.
19782 Also, log the message in the log file too. Resolves ticket 11043.
19784 o Minor features (other):
19785 - Add a new option, PredictedPortsRelevanceTime, to control how long
19786 after having received a request to connect to a given port Tor
19787 will try to keep circuits ready in anticipation of future requests
19788 for that port. Patch from "unixninja92"; implements ticket 9176.
19789 - Generate a warning if any ports are listed in the SocksPolicy,
19790 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
19791 AuthDirBadExit options. (These options only support address
19792 ranges.) Fixes part of ticket 11108.
19793 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
19796 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
19797 - Build without warnings under clang 3.4. (We have some macros that
19798 define static functions only some of which will get used later in
19799 the module. Starting with clang 3.4, these give a warning unless the
19800 unused attribute is set on them.) Resolves ticket 10904.
19801 - Fix build warnings about missing "a2x" comment when building the
19802 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
19803 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
19805 o Minor bugfixes (client):
19806 - Improve the log message when we can't connect to a hidden service
19807 because all of the hidden service directory nodes hosting its
19808 descriptor are excluded. Improves on our fix for bug 10722, which
19809 was a bugfix on 0.2.0.10-alpha.
19810 - Raise a control port warning when we fail to connect to all of
19811 our bridges. Previously, we didn't inform the controller, and
19812 the bootstrap process would stall. Fixes bug 11069; bugfix on
19814 - Exit immediately when a process-owning controller exits.
19815 Previously, tor relays would wait for a little while after their
19816 controller exited, as if they had gotten an INT signal -- but this
19817 was problematic, since there was no feedback for the user. To do a
19818 clean shutdown, controllers should send an INT signal and give Tor
19819 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
19820 - Stop attempting to connect to bridges before our pluggable
19821 transports are configured (harmless but resulted in some erroneous
19822 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
19823 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
19824 generating incorrect SOCKS5 responses, and confusing client
19825 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
19827 o Minor bugfixes (relays and bridges):
19828 - Avoid crashing on a malformed resolv.conf file when running a
19829 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
19830 - Non-exit relays no longer launch mock DNS requests to check for
19831 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
19832 non-exit relays stopped servicing DNS requests. Fixes bug 965;
19833 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
19834 - Bridges now report complete directory request statistics. Related
19835 to bug 5824; bugfix on 0.2.2.1-alpha.
19836 - Bridges now never collect statistics that were designed for
19837 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
19838 - Stop giving annoying warning messages when we decide not to launch
19839 a pluggable transport proxy that we don't need (because there are
19840 no bridges configured to use it). Resolves ticket 5018; bugfix
19842 - Give the correct URL in the warning message when trying to run a
19843 relay on an ancient version of Windows. Fixes bug 9393.
19845 o Minor bugfixes (backtrace support):
19846 - Support automatic backtraces on more platforms by using the
19847 "-fasynchronous-unwind-tables" compiler option. This option is
19848 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
19849 is on by default and table generation is not. This doesn't yet
19850 add Windows support; only Linux, OSX, and some BSDs are affected.
19851 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
19852 - Avoid strange behavior if two threads hit failed assertions at the
19853 same time and both try to log backtraces at once. (Previously, if
19854 this had happened, both threads would have stored their intermediate
19855 results in the same buffer, and generated junk outputs.) Reported by
19856 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
19857 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
19858 0.2.5.2-alpha; patch from Nick Hopper.
19860 o Minor bugfixes (unit tests):
19861 - Fix a small bug in the unit tests that might have made the tests
19862 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
19863 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
19866 - Remove all remaining code related to version-0 hidden service
19867 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
19868 the rest of bug 10841.
19871 - Document in the manpage that "KBytes" may also be written as
19872 "kilobytes" or "KB", that "Kbits" may also be written as
19873 "kilobits", and so forth. Closes ticket 9222.
19874 - Document that the ClientOnly config option overrides ORPort.
19875 Our old explanation made ClientOnly sound as though it did
19876 nothing at all. Resolves bug 9059.
19877 - Explain that SocksPolicy, DirPolicy, and similar options don't
19878 take port arguments. Fixes the other part of ticket 11108.
19879 - Fix a comment about the rend_server_descriptor_t.protocols field
19880 to more accurately describe its range. Also, make that field
19881 unsigned, to more accurately reflect its usage. Fixes bug 9099;
19882 bugfix on 0.2.1.5-alpha.
19883 - Fix the manpage's description of HiddenServiceAuthorizeClient:
19884 the maximum client name length is 16, not 19. Fixes bug 11118;
19885 bugfix on 0.2.1.6-alpha.
19887 o Code simplifications and refactoring:
19888 - Get rid of router->address, since in all cases it was just the
19889 string representation of router->addr. Resolves ticket 5528.
19891 o Test infrastructure:
19892 - Update to the latest version of tinytest.
19893 - Improve the tinytest implementation of string operation tests so
19894 that comparisons with NULL strings no longer crash the tests; they
19895 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
19898 Changes in version 0.2.4.21 - 2014-02-28
19899 Tor 0.2.4.21 further improves security against potential adversaries who
19900 find breaking 1024-bit crypto doable, and backports several stability
19901 and robustness patches from the 0.2.5 branch.
19903 o Major features (client security):
19904 - When we choose a path for a 3-hop circuit, make sure it contains
19905 at least one relay that supports the NTor circuit extension
19906 handshake. Otherwise, there is a chance that we're building
19907 a circuit that's worth attacking by an adversary who finds
19908 breaking 1024-bit crypto doable, and that chance changes the game
19909 theory. Implements ticket 9777.
19912 - Do not treat streams that fail with reason
19913 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
19914 since it could also indicate an ENETUNREACH connection error. Fixes
19915 part of bug 10777; bugfix on 0.2.4.8-alpha.
19917 o Code simplification and refactoring:
19918 - Remove data structures which were introduced to implement the
19919 CellStatistics option: they are now redundant with the new timestamp
19920 field in the regular packed_cell_t data structure, which we did
19921 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
19924 - Always clear OpenSSL bignums before freeing them -- even bignums
19925 that don't contain secrets. Resolves ticket 10793. Patch by
19927 - Build without warnings under clang 3.4. (We have some macros that
19928 define static functions only some of which will get used later in
19929 the module. Starting with clang 3.4, these give a warning unless the
19930 unused attribute is set on them.) Resolves ticket 10904.
19931 - Update geoip and geoip6 files to the February 7 2014 Maxmind
19932 GeoLite2 Country database.
19935 - Set the listen() backlog limit to the largest actually supported
19936 on the system, not to the value in a header file. Fixes bug 9716;
19937 bugfix on every released Tor.
19938 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
19939 exit node as a NOROUTE error, not an INTERNAL error, since they
19940 can apparently happen when trying to connect to the wrong sort
19941 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
19942 - Fix build warnings about missing "a2x" comment when building the
19943 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
19944 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
19945 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
19946 not entirely remove it from the connection lists. Fixes bug 9602;
19947 bugfix on 0.2.4.4-alpha.
19948 - Fix a segmentation fault in our benchmark code when running with
19949 Fedora's OpenSSL package, or any other OpenSSL that provides
19950 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
19951 - Turn "circuit handshake stats since last time" log messages into a
19952 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
19954 o Documentation fixes:
19955 - Document that all but one DirPort entry must have the NoAdvertise
19956 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
19959 Changes in version 0.2.5.2-alpha - 2014-02-13
19960 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
19961 like the "poor random number generation" fix and the "building too many
19962 circuits" fix. It also further improves security against potential
19963 adversaries who find breaking 1024-bit crypto doable, and launches
19964 pluggable transports on demand (which gets us closer to integrating
19965 pluggable transport support by default -- not to be confused with Tor
19966 bundles enabling pluggable transports and bridges by default).
19968 o Major features (client security):
19969 - When we choose a path for a 3-hop circuit, make sure it contains
19970 at least one relay that supports the NTor circuit extension
19971 handshake. Otherwise, there is a chance that we're building
19972 a circuit that's worth attacking by an adversary who finds
19973 breaking 1024-bit crypto doable, and that chance changes the game
19974 theory. Implements ticket 9777.
19975 - Clients now look at the "usecreatefast" consensus parameter to
19976 decide whether to use CREATE_FAST or CREATE cells for the first hop
19977 of their circuit. This approach can improve security on connections
19978 where Tor's circuit handshake is stronger than the available TLS
19979 connection security levels, but the tradeoff is more computational
19980 load on guard relays. Implements proposal 221. Resolves ticket 9386.
19982 o Major features (bridges):
19983 - Don't launch pluggable transport proxies if we don't have any
19984 bridges configured that would use them. Now we can list many
19985 pluggable transports, and Tor will dynamically start one when it
19986 hears a bridge address that needs it. Resolves ticket 5018.
19987 - The bridge directory authority now assigns status flags (Stable,
19988 Guard, etc) to bridges based on thresholds calculated over all
19989 Running bridges. Now bridgedb can finally make use of its features
19990 to e.g. include at least one Stable bridge in its answers. Fixes
19993 o Major features (other):
19994 - Extend ORCONN controller event to include an "ID" parameter,
19995 and add four new controller event types CONN_BW, CIRC_BW,
19996 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
19997 The new events are emitted in private Tor networks only, with the
19998 goal of being able to better track performance and load during
19999 full-network simulations. Implements proposal 218 and ticket 7359.
20000 - On some platforms (currently: recent OSX versions, glibc-based
20001 platforms that support the ELF format, and a few other
20002 Unix-like operating systems), Tor can now dump stack traces
20003 when a crash occurs or an assertion fails. By default, traces
20004 are dumped to stderr (if possible) and to any logs that are
20005 reporting errors. Implements ticket 9299.
20008 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
20009 not entirely remove it from the connection lists. Fixes bug 9602;
20010 bugfix on 0.2.4.4-alpha.
20011 - Do not treat streams that fail with reason
20012 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
20013 since it could also indicate an ENETUNREACH connection error. Fixes
20014 part of bug 10777; bugfix on 0.2.4.8-alpha.
20016 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
20017 - Do not allow OpenSSL engines to replace the PRNG, even when
20018 HardwareAccel is set. The only default builtin PRNG engine uses
20019 the Intel RDRAND instruction to replace the entire PRNG, and
20020 ignores all attempts to seed it with more entropy. That's
20021 cryptographically stupid: the right response to a new alleged
20022 entropy source is never to discard all previously used entropy
20023 sources. Fixes bug 10402; works around behavior introduced in
20024 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
20026 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
20027 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
20028 - Avoid launching spurious extra circuits when a stream is pending.
20029 This fixes a bug where any circuit that _wasn't_ unusable for new
20030 streams would be treated as if it were, causing extra circuits to
20031 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
20033 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
20034 - No longer stop reading or writing on cpuworker connections when
20035 our rate limiting buckets go empty. Now we should handle circuit
20036 handshake requests more promptly. Resolves bug 9731.
20037 - Stop trying to bootstrap all our directory information from
20038 only our first guard. Discovered while fixing bug 9946; bugfix
20041 o Minor features (bridges, pluggable transports):
20042 - Add threshold cutoffs to the networkstatus document created by
20043 the Bridge Authority. Fixes bug 1117.
20044 - On Windows, spawn background processes using the CREATE_NO_WINDOW
20045 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
20046 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
20047 Vidalia set this option for us.) Implements ticket 10297.
20049 o Minor features (security):
20050 - Always clear OpenSSL bignums before freeing them -- even bignums
20051 that don't contain secrets. Resolves ticket 10793. Patch by
20054 o Minor features (config options and command line):
20055 - Add an --allow-missing-torrc commandline option that tells Tor to
20056 run even if the configuration file specified by -f is not available.
20057 Implements ticket 10060.
20058 - Add support for the TPROXY transparent proxying facility on Linux.
20059 See documentation for the new TransProxyType option for more
20060 details. Implementation by "thomo". Closes ticket 10582.
20062 o Minor features (controller):
20063 - Add a new "HS_DESC" controller event that reports activities
20064 related to hidden service descriptors. Resolves ticket 8510.
20065 - New "DROPGUARDS" controller command to forget all current entry
20066 guards. Not recommended for ordinary use, since replacing guards
20067 too frequently makes several attacks easier. Resolves ticket 9934;
20070 o Minor features (build):
20071 - Assume that a user using ./configure --host wants to cross-compile,
20072 and give an error if we cannot find a properly named
20073 tool-chain. Add a --disable-tool-name-check option to proceed
20074 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
20075 - If we run ./configure and the compiler recognizes -fstack-protector
20076 but the linker rejects it, warn the user about a potentially missing
20077 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
20079 o Minor features (testing):
20080 - If Python is installed, "make check" now runs extra tests beyond
20081 the unit test scripts.
20082 - When bootstrapping a test network, sometimes very few relays get
20083 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
20084 specify a set of relays which should be voted Guard regardless of
20085 their uptime or bandwidth. Addresses ticket 9206.
20087 o Minor features (log messages):
20088 - When ServerTransportPlugin is set on a bridge, Tor can write more
20089 useful statistics about bridge use in its extrainfo descriptors,
20090 but only if the Extended ORPort ("ExtORPort") is set too. Add a
20091 log message to inform the user in this case. Resolves ticket 9651.
20092 - When receiving a new controller connection, log the origin address.
20093 Resolves ticket 9698; patch from "sigpipe".
20094 - When logging OpenSSL engine status at startup, log the status of
20095 more engines. Fixes ticket 10043; patch from Joshua Datko.
20096 - Turn "circuit handshake stats since last time" log messages into a
20097 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
20099 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
20100 - Improve the circuit queue out-of-memory handler. Previously, when
20101 we ran low on memory, we'd close whichever circuits had the most
20102 queued cells. Now, we close those that have the *oldest* queued
20103 cells, on the theory that those are most responsible for us
20104 running low on memory. Based on analysis from a forthcoming paper
20105 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
20106 - Generate bootstrapping status update events correctly when fetching
20107 microdescriptors. Fixes bug 9927.
20108 - Update to the October 2 2013 Maxmind GeoLite Country database.
20110 o Minor bugfixes (clients):
20111 - When closing a channel that has already been open, do not close
20112 pending circuits that were waiting to connect to the same relay.
20113 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
20116 o Minor bugfixes (relays):
20117 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
20118 exit node as a NOROUTE error, not an INTERNAL error, since they
20119 can apparently happen when trying to connect to the wrong sort
20120 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
20122 o Minor bugfixes (bridges):
20123 - Fix a bug where the first connection works to a bridge that uses a
20124 pluggable transport with client-side parameters, but we don't send
20125 the client-side parameters on subsequent connections. (We don't
20126 use any pluggable transports with client-side parameters yet,
20127 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
20128 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
20130 o Minor bugfixes (node selection):
20131 - If ExcludeNodes is set, consider non-excluded hidden service
20132 directory servers before excluded ones. Do not consider excluded
20133 hidden service directory servers at all if StrictNodes is
20134 set. (Previously, we would sometimes decide to connect to those
20135 servers, and then realize before we initiated a connection that
20136 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
20137 Reported by "mr-4".
20138 - If we set the ExitNodes option but it doesn't include any nodes
20139 that have the Exit flag, we would choose not to bootstrap. Now we
20140 bootstrap so long as ExitNodes includes nodes which can exit to
20141 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
20143 o Minor bugfixes (controller and command-line):
20144 - If changing a config option via "setconf" fails in a recoverable
20145 way, we used to nonetheless write our new control ports to the
20146 file described by the "ControlPortWriteToFile" option. Now we only
20147 write out that file if we successfully switch to the new config
20148 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
20149 - When a command-line option such as --version or --help that
20150 ordinarily implies --hush appears on the command line along with
20151 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
20152 only if it appeared later on the command line. Fixes bug 9578;
20153 bugfix on 0.2.5.1-alpha.
20155 o Minor bugfixes (code correctness):
20156 - Previously we used two temporary files when writing descriptors to
20157 disk; now we only use one. Fixes bug 1376.
20158 - Remove an erroneous (but impossible and thus harmless) pointer
20159 comparison that would have allowed compilers to skip a bounds
20160 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
20161 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
20162 - Fix an always-true assertion in pluggable transports code so it
20163 actually checks what it was trying to check. Fixes bug 10046;
20164 bugfix on 0.2.3.9-alpha. Found by "dcb".
20166 o Minor bugfixes (protocol correctness):
20167 - When receiving a VERSIONS cell with an odd number of bytes, close
20168 the connection immediately since the cell is malformed. Fixes bug
20169 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
20172 o Minor bugfixes (build):
20173 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
20174 turned off (that is, without support for v2 link handshakes). Fixes
20175 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
20176 - Fix compilation warnings and startup issues when running with
20177 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
20179 - Fix compilation on Solaris 9, which didn't like us having an
20180 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
20182 o Minor bugfixes (testing):
20183 - Fix a segmentation fault in our benchmark code when running with
20184 Fedora's OpenSSL package, or any other OpenSSL that provides
20185 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
20187 o Minor bugfixes (log messages):
20188 - Fix a bug where clients using bridges would report themselves
20189 as 50% bootstrapped even without a live consensus document.
20190 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
20191 - Suppress a warning where, if there's only one directory authority
20192 in the network, we would complain that votes and signatures cannot
20193 be uploaded to other directory authorities. Fixes bug 10842;
20194 bugfix on 0.2.2.26-beta.
20195 - Report bootstrapping progress correctly when we're downloading
20196 microdescriptors. We had updated our "do we have enough microdescs
20197 to begin building circuits?" logic most recently in 0.2.4.10-alpha
20198 (see bug 5956), but we left the bootstrap status event logic at
20199 "how far through getting 1/4 of them are we?" Fixes bug 9958;
20200 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
20202 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
20203 - Avoid a crash bug when starting with a corrupted microdescriptor
20204 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
20205 - If we fail to dump a previously cached microdescriptor to disk, avoid
20206 freeing duplicate data later on. Fixes bug 10423; bugfix on
20207 0.2.4.13-alpha. Spotted by "bobnomnom".
20209 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
20210 - Correctly log long IPv6 exit policies, instead of truncating them
20211 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
20212 - Our default TLS ecdhe groups were backwards: we meant to be using
20213 P224 for relays (for performance win) and P256 for bridges (since
20214 it is more common in the wild). Instead we had it backwards. After
20215 reconsideration, we decided that the default should be P256 on all
20216 hosts, since its security is probably better, and since P224 is
20217 reportedly used quite little in the wild. Found by "skruffy" on
20218 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
20219 - Free directory authority certificate download statuses on exit
20220 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
20222 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
20223 - If the guard we choose first doesn't answer, we would try the
20224 second guard, but once we connected to the second guard we would
20225 abandon it and retry the first one, slowing down bootstrapping.
20226 The fix is to treat all our initially chosen guards as acceptable
20227 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
20228 - Fix an assertion failure that would occur when disabling the
20229 ORPort setting on a running Tor process while accounting was
20230 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
20231 - When examining the list of network interfaces to find our address,
20232 do not consider non-running or disabled network interfaces. Fixes
20233 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
20234 - Avoid an off-by-one error when checking buffer boundaries when
20235 formatting the exit status of a pluggable transport helper.
20236 This is probably not an exploitable bug, but better safe than
20237 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
20240 o Removed code and features:
20241 - Clients now reject any directory authority certificates lacking
20242 a dir-key-crosscert element. These have been included since
20243 0.2.1.9-alpha, so there's no real reason for them to be optional
20244 any longer. Completes proposal 157. Resolves ticket 10162.
20245 - Remove all code that existed to support the v2 directory system,
20246 since there are no longer any v2 directory authorities. Resolves
20248 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
20249 options, which were used for designating authorities as "Hidden
20250 service authorities". There has been no use of hidden service
20251 authorities since 0.2.2.1-alpha, when we stopped uploading or
20252 downloading v0 hidden service descriptors. Fixes bug 10881; also
20253 part of a fix for bug 10841.
20255 o Code simplification and refactoring:
20256 - Remove some old fallback code designed to keep Tor clients working
20257 in a network with only two working relays. Elsewhere in the code we
20258 have long since stopped supporting such networks, so there wasn't
20259 much point in keeping it around. Addresses ticket 9926.
20260 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
20261 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
20262 - Remove data structures which were introduced to implement the
20263 CellStatistics option: they are now redundant with the addition
20264 of a timestamp to the regular packed_cell_t data structure, which
20265 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
20268 o Documentation (man page) fixes:
20269 - Update manpage to describe some of the files you can expect to
20270 find in Tor's DataDirectory. Addresses ticket 9839.
20271 - Document that all but one DirPort entry must have the NoAdvertise
20272 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
20274 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
20275 - Clarify the usage and risks of setting the ContactInfo torrc line
20276 for your relay or bridge. Resolves ticket 9854.
20277 - Add anchors to the manpage so we can link to the html version of
20278 the documentation for specific options. Resolves ticket 9866.
20279 - Replace remaining references to DirServer in man page and
20280 log entries. Resolves ticket 10124.
20283 - Make the "tor-gencert" tool used by directory authority operators
20284 create 2048-bit signing keys by default (rather than 1024-bit, since
20285 1024-bit is uncomfortably small these days). Addresses ticket 10324.
20288 Changes in version 0.2.4.20 - 2013-12-22
20289 Tor 0.2.4.20 fixes potentially poor random number generation for users
20290 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
20291 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
20292 and 4) have no state file in their DataDirectory (as would happen on
20293 first start). Users who generated relay or hidden service identity
20294 keys in such a situation should discard them and generate new ones.
20296 This release also fixes a logic error that caused Tor clients to build
20297 many more preemptive circuits than they actually need.
20300 - Do not allow OpenSSL engines to replace the PRNG, even when
20301 HardwareAccel is set. The only default builtin PRNG engine uses
20302 the Intel RDRAND instruction to replace the entire PRNG, and
20303 ignores all attempts to seed it with more entropy. That's
20304 cryptographically stupid: the right response to a new alleged
20305 entropy source is never to discard all previously used entropy
20306 sources. Fixes bug 10402; works around behavior introduced in
20307 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
20309 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
20310 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
20311 - Avoid launching spurious extra circuits when a stream is pending.
20312 This fixes a bug where any circuit that _wasn't_ unusable for new
20313 streams would be treated as if it were, causing extra circuits to
20314 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
20317 - Avoid a crash bug when starting with a corrupted microdescriptor
20318 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
20319 - If we fail to dump a previously cached microdescriptor to disk, avoid
20320 freeing duplicate data later on. Fixes bug 10423; bugfix on
20321 0.2.4.13-alpha. Spotted by "bobnomnom".
20324 Changes in version 0.2.4.19 - 2013-12-11
20325 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
20326 (1986-2013). Aaron worked on diverse projects including helping to guide
20327 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
20328 transparency to the U.S government's PACER documents, and contributing
20329 design and development for Tor and Tor2Web. Aaron was one of the latest
20330 martyrs in our collective fight for civil liberties and human rights,
20331 and his death is all the more painful because he was one of us.
20333 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
20334 a new circuit handshake and link encryption that use ECC to provide
20335 better security and efficiency; makes relays better manage circuit
20336 creation requests; uses "directory guards" to reduce client enumeration
20337 risks; makes bridges collect and report statistics about the pluggable
20338 transports they support; cleans up and improves our geoip database;
20339 gets much closer to IPv6 support for clients, bridges, and relays; makes
20340 directory authorities use measured bandwidths rather than advertised
20341 ones when computing flags and thresholds; disables client-side DNS
20342 caching to reduce tracking risks; and fixes a big bug in bridge
20343 reachability testing. This release introduces two new design
20344 abstractions in the code: a new "channel" abstraction between circuits
20345 and or_connections to allow for implementing alternate relay-to-relay
20346 transports, and a new "circuitmux" abstraction storing the queue of
20347 circuits for a channel. The release also includes many stability,
20348 security, and privacy fixes.
20351 Changes in version 0.2.4.18-rc - 2013-11-16
20352 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
20353 series. It takes a variety of fixes from the 0.2.5.x branch to improve
20354 stability, performance, and better handling of edge cases.
20357 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
20358 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
20359 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
20360 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
20361 them to solve bug 6033.)
20364 - No longer stop reading or writing on cpuworker connections when
20365 our rate limiting buckets go empty. Now we should handle circuit
20366 handshake requests more promptly. Resolves bug 9731.
20367 - If we are unable to save a microdescriptor to the journal, do not
20368 drop it from memory and then reattempt downloading it. Fixes bug
20369 9645; bugfix on 0.2.2.6-alpha.
20370 - Stop trying to bootstrap all our directory information from
20371 only our first guard. Discovered while fixing bug 9946; bugfix
20373 - The new channel code sometimes lost track of in-progress circuits,
20374 causing long-running clients to stop building new circuits. The
20375 fix is to always call circuit_n_chan_done(chan, 0) from
20376 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
20378 o Minor bugfixes (on 0.2.4.x):
20379 - Correctly log long IPv6 exit policies, instead of truncating them
20380 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
20381 - Our default TLS ecdhe groups were backwards: we meant to be using
20382 P224 for relays (for performance win) and P256 for bridges (since
20383 it is more common in the wild). Instead we had it backwards. After
20384 reconsideration, we decided that the default should be P256 on all
20385 hosts, since its security is probably better, and since P224 is
20386 reportedly used quite little in the wild. Found by "skruffy" on
20387 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
20388 - Free directory authority certificate download statuses on exit
20389 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
20391 o Minor bugfixes (on 0.2.3.x and earlier):
20392 - If the guard we choose first doesn't answer, we would try the
20393 second guard, but once we connected to the second guard we would
20394 abandon it and retry the first one, slowing down bootstrapping.
20395 The fix is to treat all our initially chosen guards as acceptable
20396 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
20397 - Fix an assertion failure that would occur when disabling the
20398 ORPort setting on a running Tor process while accounting was
20399 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
20400 - When examining the list of network interfaces to find our address,
20401 do not consider non-running or disabled network interfaces. Fixes
20402 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
20403 - Avoid an off-by-one error when checking buffer boundaries when
20404 formatting the exit status of a pluggable transport helper.
20405 This is probably not an exploitable bug, but better safe than
20406 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
20409 o Minor features (protecting client timestamps):
20410 - Clients no longer send timestamps in their NETINFO cells. These were
20411 not used for anything, and they provided one small way for clients
20412 to be distinguished from each other as they moved from network to
20413 network or behind NAT. Implements part of proposal 222.
20414 - Clients now round timestamps in INTRODUCE cells down to the nearest
20415 10 minutes. If a new Support022HiddenServices option is set to 0, or
20416 if it's set to "auto" and the feature is disabled in the consensus,
20417 the timestamp is sent as 0 instead. Implements part of proposal 222.
20418 - Stop sending timestamps in AUTHENTICATE cells. This is not such
20419 a big deal from a security point of view, but it achieves no actual
20420 good purpose, and isn't needed. Implements part of proposal 222.
20421 - Reduce down accuracy of timestamps in hidden service descriptors.
20422 Implements part of proposal 222.
20424 o Minor features (other):
20425 - Improve the circuit queue out-of-memory handler. Previously, when
20426 we ran low on memory, we'd close whichever circuits had the most
20427 queued cells. Now, we close those that have the *oldest* queued
20428 cells, on the theory that those are most responsible for us
20429 running low on memory. Based on analysis from a forthcoming paper
20430 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
20431 - Generate bootstrapping status update events correctly when fetching
20432 microdescriptors. Fixes bug 9927.
20433 - Update to the October 2 2013 Maxmind GeoLite Country database.
20435 o Documentation fixes:
20436 - Clarify the usage and risks of setting the ContactInfo torrc line
20437 for your relay or bridge. Resolves ticket 9854.
20438 - Add anchors to the manpage so we can link to the html version of
20439 the documentation for specific options. Resolves ticket 9866.
20440 - Replace remaining references to DirServer in man page and
20441 log entries. Resolves ticket 10124.
20444 Changes in version 0.2.5.1-alpha - 2013-10-02
20445 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
20446 on Linux, allows bridges that offer pluggable transports to report usage
20447 statistics, fixes many issues to make testing easier, and provides
20448 a pile of minor features and bugfixes that have been waiting for a
20449 release of the new branch.
20451 This is the first alpha release in a new series, so expect there to
20452 be bugs. Users who would rather test out a more stable branch should
20453 stay with 0.2.4.x for now.
20455 o Major features (security):
20456 - Use the seccomp2 syscall filtering facility on Linux to limit
20457 which system calls Tor can invoke. This is an experimental,
20458 Linux-only feature to provide defense-in-depth against unknown
20459 attacks. To try turning it on, set "Sandbox 1" in your torrc
20460 file. Please be ready to report bugs. We hope to add support
20461 for better sandboxing in the future, including more fine-grained
20462 filters, better division of responsibility, and support for more
20463 platforms. This work has been done by Cristian-Matei Toader for
20464 Google Summer of Code.
20465 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
20466 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
20467 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
20468 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
20469 them to solve bug 6033.)
20471 o Major features (other):
20472 - Add support for passing arguments to managed pluggable transport
20473 proxies. Implements ticket 3594.
20474 - Bridges now track GeoIP information and the number of their users
20475 even when pluggable transports are in use, and report usage
20476 statistics in their extra-info descriptors. Resolves tickets 4773
20478 - Make testing Tor networks bootstrap better: lower directory fetch
20479 retry schedules and maximum interval without directory requests,
20480 and raise maximum download tries. Implements ticket 6752.
20481 - Add make target 'test-network' to run tests on a Chutney network.
20482 Implements ticket 8530.
20483 - The ntor handshake is now on-by-default, no matter what the
20484 directory authorities recommend. Implements ticket 8561.
20487 - Instead of writing destroy cells directly to outgoing connection
20488 buffers, queue them and intersperse them with other outgoing cells.
20489 This can prevent a set of resource starvation conditions where too
20490 many pending destroy cells prevent data cells from actually getting
20491 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
20492 bugfix on 0.2.0.1-alpha.
20493 - If we are unable to save a microdescriptor to the journal, do not
20494 drop it from memory and then reattempt downloading it. Fixes bug
20495 9645; bugfix on 0.2.2.6-alpha.
20496 - The new channel code sometimes lost track of in-progress circuits,
20497 causing long-running clients to stop building new circuits. The
20498 fix is to always call circuit_n_chan_done(chan, 0) from
20499 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
20502 - Tor now builds each source file in two modes: a mode that avoids
20503 exposing identifiers needlessly, and another mode that exposes
20504 more identifiers for testing. This lets the compiler do better at
20505 optimizing the production code, while enabling us to take more
20506 radical measures to let the unit tests test things.
20507 - The production builds no longer include functions used only in
20508 the unit tests; all functions exposed from a module only for
20509 unit-testing are now static in production builds.
20510 - Add an --enable-coverage configuration option to make the unit
20511 tests (and a new src/or/tor-cov target) to build with gcov test
20515 - We now have rudimentary function mocking support that our unit
20516 tests can use to test functions in isolation. Function mocking
20517 lets the tests temporarily replace a function's dependencies with
20518 stub functions, so that the tests can check the function without
20519 invoking the other functions it calls.
20520 - Add more unit tests for the <circid,channel>->circuit map, and
20521 the destroy-cell-tracking code to fix bug 7912.
20522 - Unit tests for failing cases of the TAP onion handshake.
20523 - More unit tests for address-manipulation functions.
20525 o Minor features (protecting client timestamps):
20526 - Clients no longer send timestamps in their NETINFO cells. These were
20527 not used for anything, and they provided one small way for clients
20528 to be distinguished from each other as they moved from network to
20529 network or behind NAT. Implements part of proposal 222.
20530 - Clients now round timestamps in INTRODUCE cells down to the nearest
20531 10 minutes. If a new Support022HiddenServices option is set to 0, or
20532 if it's set to "auto" and the feature is disabled in the consensus,
20533 the timestamp is sent as 0 instead. Implements part of proposal 222.
20534 - Stop sending timestamps in AUTHENTICATE cells. This is not such
20535 a big deal from a security point of view, but it achieves no actual
20536 good purpose, and isn't needed. Implements part of proposal 222.
20537 - Reduce down accuracy of timestamps in hidden service descriptors.
20538 Implements part of proposal 222.
20540 o Minor features (config options):
20541 - Config (torrc) lines now handle fingerprints which are missing
20542 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
20543 - Support a --dump-config option to print some or all of the
20544 configured options. Mainly useful for debugging the command-line
20545 option parsing code. Helps resolve ticket 4647.
20546 - Raise awareness of safer logging: notify user of potentially
20547 unsafe config options, like logging more verbosely than severity
20548 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
20549 - Add a new configuration option TestingV3AuthVotingStartOffset
20550 that bootstraps a network faster by changing the timing for
20551 consensus votes. Addresses ticket 8532.
20552 - Add a new torrc option "ServerTransportOptions" that allows
20553 bridge operators to pass configuration parameters to their
20554 pluggable transports. Resolves ticket 8929.
20555 - The config (torrc) file now accepts bandwidth and space limits in
20556 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
20557 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
20560 o Minor features (build):
20561 - Add support for `--library-versions` flag. Implements ticket 6384.
20562 - Return the "unexpected sendme" warnings to a warn severity, but make
20563 them rate limited, to help diagnose ticket 8093.
20564 - Detect a missing asciidoc, and warn the user about it, during
20565 configure rather than at build time. Fixes issue 6506. Patch from
20568 o Minor features (other):
20569 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
20570 sockets in a single system call. Implements ticket 5129.
20571 - Log current accounting state (bytes sent and received + remaining
20572 time for the current accounting period) in the relay's heartbeat
20573 message. Implements ticket 5526; patch from Peter Retzlaff.
20574 - Implement the TRANSPORT_LAUNCHED control port event that
20575 notifies controllers about new launched pluggable
20576 transports. Resolves ticket 5609.
20577 - If we're using the pure-C 32-bit curve25519_donna implementation
20578 of curve25519, build it with the -fomit-frame-pointer option to
20579 make it go faster on register-starved hosts. This improves our
20580 handshake performance by about 6% on i386 hosts without nacl.
20581 Closes ticket 8109.
20582 - Update to the September 4 2013 Maxmind GeoLite Country database.
20585 - Set the listen() backlog limit to the largest actually supported
20586 on the system, not to the value in a header file. Fixes bug 9716;
20587 bugfix on every released Tor.
20588 - No longer accept malformed http headers when parsing urls from
20589 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
20590 bugfix on 0.0.6pre1.
20591 - In munge_extrainfo_into_routerinfo(), check the return value of
20592 memchr(). This would have been a serious issue if we ever passed
20593 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
20595 - On the chance that somebody manages to build Tor on a
20596 platform where time_t is unsigned, correct the way that
20597 microdesc_add_to_cache() handles negative time arguments.
20598 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
20599 - Reject relative control socket paths and emit a warning. Previously,
20600 single-component control socket paths would be rejected, but Tor
20601 would not log why it could not validate the config. Fixes bug 9258;
20602 bugfix on 0.2.3.16-alpha.
20604 o Minor bugfixes (command line):
20605 - Use a single command-line parser for parsing torrc options on the
20606 command line and for finding special command-line options to avoid
20607 inconsistent behavior for torrc option arguments that have the same
20608 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
20610 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
20611 9573; bugfix on 0.0.9pre5.
20613 o Minor fixes (build, auxiliary programs):
20614 - Stop preprocessing the "torify" script with autoconf, since
20615 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
20617 - The tor-fw-helper program now follows the standard convention and
20618 exits with status code "0" on success. Fixes bug 9030; bugfix on
20619 0.2.3.1-alpha. Patch by Arlo Breault.
20620 - Corrected ./configure advice for what openssl dev package you should
20621 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
20623 o Minor code improvements:
20624 - Remove constants and tests for PKCS1 padding; it's insecure and
20625 shouldn't be used for anything new. Fixes bug 8792; patch
20627 - Remove instances of strcpy() from the unit tests. They weren't
20628 hurting anything, since they were only in the unit tests, but it's
20629 embarrassing to have strcpy() in the code at all, and some analysis
20630 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
20631 0.2.3.8-alpha. Patch from Arlo Breault.
20633 o Removed features:
20634 - Remove migration code from when we renamed the "cached-routers"
20635 file to "cached-descriptors" back in 0.2.0.8-alpha. This
20636 incidentally resolves ticket 6502 by cleaning up the related code
20637 a bit. Patch from Akshay Hebbar.
20639 o Code simplification and refactoring:
20640 - Extract the common duplicated code for creating a subdirectory
20641 of the data directory and writing to a file in it. Fixes ticket
20642 4282; patch from Peter Retzlaff.
20643 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
20644 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
20645 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
20646 - Add a set of accessor functions for the circuit timeout data
20647 structure. Fixes ticket 6153; patch from "piet".
20648 - Clean up exit paths from connection_listener_new(). Closes ticket
20649 8789. Patch from Arlo Breault.
20650 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
20651 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
20652 - Use a doubly-linked list to implement the global circuit list.
20653 Resolves ticket 9108. Patch from Marek Majkowski.
20654 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
20657 Changes in version 0.2.4.17-rc - 2013-09-05
20658 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
20659 series. It adds an emergency step to help us tolerate the massive
20660 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
20661 circuit-level handshakes now effectively jump the queue compared to
20662 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
20663 big bug hindering bridge reachability tests.
20666 - Relays now process the new "NTor" circuit-level handshake requests
20667 with higher priority than the old "TAP" circuit-level handshake
20668 requests. We still process some TAP requests to not totally starve
20669 0.2.3 clients when NTor becomes popular. A new consensus parameter
20670 "NumNTorsPerTAP" lets us tune the balance later if we need to.
20671 Implements ticket 9574.
20674 - If the circuit build timeout logic is disabled (via the consensus,
20675 or because we are an authority), then don't build testing circuits.
20676 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
20677 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
20678 previously they did not, which prevented them from receiving
20679 successful connections from relays for self-test or bandwidth
20680 testing. Also, when a relay is extending a circuit to a bridge,
20681 it needs to send a NETINFO cell, even when the bridge hasn't sent
20682 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
20683 - If the time to download the next old-style networkstatus is in
20684 the future, do not decline to consider whether to download the
20685 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
20689 - Avoid double-closing the listener socket in our socketpair()
20690 replacement (used on Windows) in the case where the addresses on
20691 our opened sockets don't match what we expected. Fixes bug 9400;
20692 bugfix on 0.0.2pre7. Found by Coverity.
20694 o Minor fixes (config options):
20695 - Avoid overflows when the user sets MaxCircuitDirtiness to a
20696 ridiculously high value, by imposing a (ridiculously high) 30-day
20697 maximum on MaxCircuitDirtiness.
20698 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
20699 message is logged at notice, not at info.
20700 - Warn and fail if a server is configured not to advertise any
20701 ORPorts at all. (We need *something* to put in our descriptor,
20702 or we just won't work.)
20705 - Track how many "TAP" and "NTor" circuit handshake requests we get,
20706 and how many we complete, and log it every hour to help relay
20707 operators follow trends in network load. Addresses ticket 9658.
20708 - Update to the August 7 2013 Maxmind GeoLite Country database.
20711 Changes in version 0.2.4.16-rc - 2013-08-10
20712 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
20713 series. It fixes several crash bugs in the 0.2.4 branch.
20716 - Fix a bug in the voting algorithm that could yield incorrect results
20717 when a non-naming authority declared too many flags. Fixes bug 9200;
20718 bugfix on 0.2.0.3-alpha.
20719 - Fix an uninitialized read that could in some cases lead to a remote
20720 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
20721 Anybody running a hidden service on the experimental 0.2.4.x
20722 branch should upgrade. (This is, so far as we know, unrelated to
20724 - Avoid an assertion failure when processing DNS replies without the
20725 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
20726 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
20727 0.2.4.15-rc. Found by stem integration tests.
20730 - Fix an invalid memory read that occurred when a pluggable
20731 transport proxy failed its configuration protocol.
20732 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
20733 - When evaluating whether to use a connection that we haven't
20734 decided is canonical using a recent link protocol version,
20735 decide that it's canonical only if it used address _does_
20736 match the desired address. Fixes bug 9309; bugfix on
20737 0.2.4.4-alpha. Reported by skruffy.
20738 - Make the default behavior of NumDirectoryGuards be to track
20739 NumEntryGuards. Now a user who changes only NumEntryGuards will get
20740 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
20741 - Fix a spurious compilation warning with some older versions of
20742 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
20745 - Update to the July 3 2013 Maxmind GeoLite Country database.
20748 Changes in version 0.2.4.15-rc - 2013-07-01
20749 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
20750 series. It fixes a few smaller bugs, but generally appears stable.
20751 Please test it and let us know whether it is!
20754 - When receiving a new configuration file via the control port's
20755 LOADCONF command, do not treat the defaults file as absent.
20756 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
20759 - Issue a warning when running with the bufferevents backend enabled.
20760 It's still not stable, and people should know that they're likely
20761 to hit unexpected problems. Closes ticket 9147.
20764 Changes in version 0.2.4.14-alpha - 2013-06-18
20765 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
20766 present in 0.2.4.13-alpha.
20769 - When we have too much memory queued in circuits (according to a new
20770 MaxMemInCellQueues option), close the circuits consuming the most
20771 memory. This prevents us from running out of memory as a relay if
20772 circuits fill up faster than they can be drained. Fixes bug 9063;
20773 bugfix on the 54th commit of Tor. This bug is a further fix beyond
20774 bug 6252, whose fix was merged into 0.2.3.21-rc.
20776 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
20777 where we tried to solve this issue simply by imposing an upper limit
20778 on the number of queued cells for a single circuit. That approach
20779 proved to be problematic, since there are ways to provoke clients to
20780 send a number of cells in excess of any such reasonable limit. Fixes
20781 bug 9072; bugfix on 0.2.4.13-alpha.
20783 - Limit hidden service descriptors to at most ten introduction
20784 points, to slow one kind of guard enumeration. Fixes bug 9002;
20785 bugfix on 0.1.1.11-alpha.
20788 Changes in version 0.2.4.13-alpha - 2013-06-14
20789 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
20790 vulnerabilities, makes socks5 username/password circuit isolation
20791 actually actually work (this time for sure!), and cleans up a bunch
20792 of other issues in preparation for a release candidate.
20794 o Major bugfixes (robustness):
20795 - Close any circuit that has too many cells queued on it. Fixes
20796 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
20797 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
20798 - Prevent the get_freelists() function from running off the end of
20799 the list of freelists if it somehow gets an unrecognized
20800 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
20802 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
20803 when an exit connection with optimistic data succeeds immediately
20804 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
20806 - Fix a directory authority crash bug when building a consensus
20807 using an older consensus as its basis. Fixes bug 8833. Bugfix
20811 - Avoid a memory leak where we would leak a consensus body when we
20812 find that a consensus which we couldn't previously verify due to
20813 missing certificates is now verifiable. Fixes bug 8719; bugfix
20815 - We used to always request authority certificates by identity digest,
20816 meaning we'd get the newest one even when we wanted one with a
20817 different signing key. Then we would complain about being given
20818 a certificate we already had, and never get the one we really
20819 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
20820 resource to request the one we want. Fixes bug 5595; bugfix on
20822 - Follow the socks5 protocol when offering username/password
20823 authentication. The fix for bug 8117 exposed this bug, and it
20824 turns out real-world applications like Pidgin do care. Bugfix on
20825 0.2.3.2-alpha; fixes bug 8879.
20826 - Prevent failures on Windows Vista and later when rebuilding the
20827 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
20828 bugfix on 0.2.4.12-alpha.
20831 - Fix an impossible buffer overrun in the AES unit tests. Fixes
20832 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
20833 - If for some reason we fail to write a microdescriptor while
20834 rebuilding the cache, do not let the annotations from that
20835 microdescriptor linger in the cache file, and do not let the
20836 microdescriptor stay recorded as present in its old location.
20837 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
20838 - Fix a memory leak that would occur whenever a configuration
20839 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
20840 - Paste the description for PathBias parameters from the man
20841 page into or.h, so the code documents them too. Fixes bug 7982;
20842 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
20843 - Relays now treat a changed IPv6 ORPort as sufficient reason to
20844 publish an updated descriptor. Fixes bug 6026; bugfix on
20846 - When launching a resolve request on behalf of an AF_UNIX control
20847 socket, omit the address field of the new entry connection, used in
20848 subsequent controller events, rather than letting tor_dup_addr()
20849 set it to "<unknown address type>". Fixes bug 8639; bugfix on
20852 o Minor bugfixes (log messages):
20853 - Fix a scaling issue in the path bias accounting code that
20854 resulted in "Bug:" log messages from either
20855 pathbias_scale_close_rates() or pathbias_count_build_success().
20856 This represents a bugfix on a previous bugfix: the original fix
20857 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
20859 - Give a less useless error message when the user asks for an IPv4
20860 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
20864 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
20865 to tolerate bug 8093 for now.
20866 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
20867 in directory authority votes to describe whether they have enough
20868 measured bandwidths to ignore advertised (relay descriptor)
20869 bandwidth claims. Resolves ticket 8711.
20870 - Update to the June 5 2013 Maxmind GeoLite Country database.
20872 o Removed documentation:
20873 - Remove some of the older contents of doc/ as obsolete; move others
20874 to torspec.git. Fixes bug 8965.
20876 o Code simplification and refactoring:
20877 - Avoid using character buffers when constructing most directory
20878 objects: this approach was unwieldy and error-prone. Instead,
20879 build smartlists of strings, and concatenate them when done.
20882 Changes in version 0.2.4.12-alpha - 2013-04-18
20883 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
20884 process for lengthening the guard rotation period, makes directory
20885 authority opinions in the consensus a bit less gameable, makes socks5
20886 username/password circuit isolation actually work, and fixes a wide
20887 variety of other issues.
20890 - Raise the default time that a client keeps an entry guard from
20891 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
20892 2012 paper. (We would make it even longer, but we need better client
20893 load balancing first.) Also, make the guard lifetime controllable
20894 via a new GuardLifetime torrc option and a GuardLifetime consensus
20895 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
20896 - Directory authorities now prefer using measured bandwidths to
20897 advertised ones when computing flags and thresholds. Resolves
20899 - Directory authorities that have more than a threshold number
20900 of relays with measured bandwidths now treat relays with unmeasured
20901 bandwidths as having bandwidth 0. Resolves ticket 8435.
20903 o Major bugfixes (assert / resource use):
20904 - Avoid a bug where our response to TLS renegotiation under certain
20905 network conditions could lead to a busy-loop, with 100% CPU
20906 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
20907 - Avoid an assertion when we discover that we'd like to write a cell
20908 onto a closing connection: just discard the cell. Fixes another
20909 case of bug 7350; bugfix on 0.2.4.4-alpha.
20911 o Major bugfixes (client-side privacy):
20912 - When we mark a circuit as unusable for new circuits, have it
20913 continue to be unusable for new circuits even if MaxCircuitDirtiness
20914 is increased too much at the wrong time, or the system clock jumps
20915 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
20916 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
20917 which have resolved to internal addresses") is set, apply that
20918 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
20919 - When an exit relay rejects a stream with reason "exit policy", but
20920 we only know an exit policy summary (e.g. from the microdesc
20921 consensus) for it, do not mark the relay as useless for all exiting.
20922 Instead, mark just the circuit as unsuitable for that particular
20923 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
20924 - Allow applications to get proper stream isolation with
20925 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
20926 username/password authentication also offer "no authentication". Tor
20927 had previously preferred "no authentication", so the applications
20928 never actually sent Tor their auth details. Now Tor selects
20929 username/password authentication if it's offered. You can disable
20930 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
20931 bug 8117; bugfix on 0.2.3.3-alpha.
20933 o Major bugfixes (other):
20934 - When unable to find any working directory nodes to use as a
20935 directory guard, give up rather than adding the same non-working
20936 nodes to the directory guard list over and over. Fixes bug 8231;
20937 bugfix on 0.2.4.8-alpha.
20940 - Reject as invalid most directory objects containing a NUL.
20941 Belt-and-suspender fix for bug 8037.
20942 - In our testsuite, create temporary directories with a bit more
20943 entropy in their name to make name collisions less likely. Fixes
20945 - Add CACHED keyword to ADDRMAP events in the control protocol
20946 to indicate whether a DNS result will be cached or not. Resolves
20948 - Update to the April 3 2013 Maxmind GeoLite Country database.
20950 o Minor features (build):
20951 - Detect and reject attempts to build Tor with threading support
20952 when OpenSSL has been compiled without threading support.
20954 - Clarify that when autoconf is checking for nacl, it is checking
20955 specifically for nacl with a fast curve25519 implementation.
20957 - Warn if building on a platform with an unsigned time_t: there
20958 are too many places where Tor currently assumes that time_t can
20959 hold negative values. We'd like to fix them all, but probably
20962 o Minor bugfixes (build):
20963 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
20964 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
20965 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
20966 - Add the old src/or/micro-revision.i filename to CLEANFILES.
20967 On the off chance that somebody has one, it will go away as soon
20968 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
20969 - Build Tor correctly on 32-bit platforms where the compiler can build
20970 but not run code using the "uint128_t" construction. Fixes bug 8587;
20971 bugfix on 0.2.4.8-alpha.
20972 - Fix compilation warning with some versions of clang that would
20973 prefer the -Wswitch-enum compiler flag to warn about switch
20974 statements with missing enum values, even if those switch
20975 statements have a "default:" statement. Fixes bug 8598; bugfix
20978 o Minor bugfixes (protocol):
20979 - Fix the handling of a TRUNCATE cell when it arrives while the
20980 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
20981 - Fix a misframing issue when reading the version numbers in a
20982 VERSIONS cell. Previously we would recognize [00 01 00 02] as
20983 'version 1, version 2, and version 0x100', when it should have
20984 only included versions 1 and 2. Fixes bug 8059; bugfix on
20985 0.2.0.10-alpha. Reported pseudonymously.
20986 - Make the format and order of STREAM events for DNS lookups
20987 consistent among the various ways to launch DNS lookups. Fixes
20988 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
20989 - Correct our check for which versions of Tor support the EXTEND2
20990 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
20991 later, when support was really added in version 0.2.4.8-alpha.
20992 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
20994 o Minor bugfixes (other):
20995 - Correctly store microdescriptors and extrainfo descriptors with
20996 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
20997 Bug reported by "cypherpunks".
20998 - Increase the width of the field used to remember a connection's
20999 link protocol version to two bytes. Harmless for now, since the
21000 only currently recognized versions are one byte long. Reported
21001 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
21002 - If the state file's path bias counts are invalid (presumably from a
21003 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
21004 additional checks and log messages to the scaling of Path Bias
21005 counts, in case there still are remaining issues with scaling.
21006 Should help resolve bug 8235.
21007 - Eliminate several instances where we use "Nickname=ID" to refer to
21008 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
21009 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
21010 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
21012 o Minor bugfixes (syscalls):
21013 - Always check the return values of functions fcntl() and
21014 setsockopt(). We don't believe these are ever actually failing in
21015 practice, but better safe than sorry. Also, checking these return
21016 values should please analysis tools like Coverity. Patch from
21017 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
21018 - Use direct writes rather than stdio when building microdescriptor
21019 caches, in an attempt to mitigate bug 8031, or at least make it
21022 o Minor bugfixes (config):
21023 - When rejecting a configuration because we were unable to parse a
21024 quoted string, log an actual error message. Fixes bug 7950; bugfix
21026 - Behave correctly when the user disables LearnCircuitBuildTimeout
21027 but doesn't tell us what they would like the timeout to be. Fixes
21028 bug 6304; bugfix on 0.2.2.14-alpha.
21029 - When autodetecting the number of CPUs, use the number of available
21030 CPUs in preference to the number of configured CPUs. Inform the
21031 user if this reduces the number of available CPUs. Fixes bug 8002;
21032 bugfix on 0.2.3.1-alpha.
21033 - Make it an error when you set EntryNodes but disable UseGuardNodes,
21034 since it will (surprisingly to some users) ignore EntryNodes. Fixes
21035 bug 8180; bugfix on 0.2.3.11-alpha.
21036 - Allow TestingTorNetworks to override the 4096-byte minimum for
21037 the Fast threshold. Otherwise they can't bootstrap until they've
21038 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
21039 - Fix some logic errors when the user manually overrides the
21040 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
21043 o Minor bugfixes (log messages to help diagnose bugs):
21044 - If we fail to free a microdescriptor because of bug 7164, log
21045 the filename and line number from which we tried to free it.
21046 - Add another diagnostic to the heartbeat message: track and log
21047 overhead that TLS is adding to the data we write. If this is
21048 high, we are sending too little data to SSL_write at a time.
21049 Diagnostic for bug 7707.
21050 - Add more detail to a log message about relaxed timeouts, to help
21052 - Warn more aggressively when flushing microdescriptors to a
21053 microdescriptor cache fails, in an attempt to mitigate bug 8031,
21054 or at least make it more diagnosable.
21055 - Improve debugging output to help track down bug 8185 ("Bug:
21056 outgoing relay cell has n_chan==NULL. Dropping.")
21057 - Log the purpose of a path-bias testing circuit correctly.
21058 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
21060 o Minor bugfixes (0.2.4.x log messages that were too noisy):
21061 - Don't attempt to relax the timeout of already opened 1-hop circuits.
21062 They might never timeout. This should eliminate some/all cases of
21063 the relaxed timeout log message.
21064 - Use circuit creation time for network liveness evaluation. This
21065 should eliminate warning log messages about liveness caused
21066 by changes in timeout evaluation. Fixes bug 6572; bugfix on
21068 - Reduce a path bias length check from notice to info. The message
21069 is triggered when creating controller circuits. Fixes bug 8196;
21070 bugfix on 0.2.4.8-alpha.
21071 - Fix a path state issue that triggered a notice during relay startup.
21072 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
21073 - Reduce occurrences of warns about circuit purpose in
21074 connection_ap_expire_building(). Fixes bug 8477; bugfix on
21077 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
21078 - If we encounter a write failure on a SOCKS connection before we
21079 finish our SOCKS handshake, don't warn that we closed the
21080 connection before we could send a SOCKS reply. Fixes bug 8427;
21081 bugfix on 0.1.0.1-rc.
21082 - Correctly recognize that [::1] is a loopback address. Fixes
21083 bug 8377; bugfix on 0.2.1.3-alpha.
21084 - Fix a directory authority warn caused when we have a large amount
21085 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
21086 - Don't log inappropriate heartbeat messages when hibernating: a
21087 hibernating node is _expected_ to drop out of the consensus,
21088 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
21089 bugfix on 0.2.3.1-alpha.
21090 - Don't complain about bootstrapping problems while hibernating.
21091 These complaints reflect a general code problem, but not one
21092 with any problematic effects (no connections are actually
21093 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
21095 o Documentation fixes:
21096 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
21097 names match. Fixes bug 7768.
21098 - Make the torify manpage no longer refer to tsocks; torify hasn't
21099 supported tsocks since 0.2.3.14-alpha.
21100 - Make the tor manpage no longer reference tsocks.
21101 - Fix the GeoIPExcludeUnknown documentation to refer to
21102 ExcludeExitNodes rather than the currently nonexistent
21103 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
21106 - The tor-tsocks.conf is no longer distributed or installed. We
21107 recommend that tsocks users use torsocks instead. Resolves
21111 Changes in version 0.2.4.11-alpha - 2013-03-11
21112 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
21113 more robust, makes hidden service authentication work again, and
21114 resolves a DPI fingerprint for Tor's SSL transport.
21116 o Major features (directory authorities):
21117 - Directory authorities now support a new consensus method (17)
21118 where they cap the published bandwidth of servers for which
21119 insufficient bandwidth measurements exist. Fixes part of bug 2286.
21120 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
21121 serve any v2 directory information. Now we can test disabling the
21122 old deprecated v2 directory format, and see whether doing so has
21123 any effect on network load. Begins to fix bug 6783.
21124 - Directory authorities now include inside each vote a statement of
21125 the performance thresholds they used when assigning flags.
21126 Implements ticket 8151.
21128 o Major bugfixes (directory authorities):
21129 - Stop marking every relay as having been down for one hour every
21130 time we restart a directory authority. These artificial downtimes
21131 were messing with our Stable and Guard flag calculations. Fixes
21132 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
21134 o Major bugfixes (hidden services):
21135 - Allow hidden service authentication to succeed again. When we
21136 refactored the hidden service introduction code back
21137 in 0.2.4.1-alpha, we didn't update the code that checks
21138 whether authentication information is present, causing all
21139 authentication checks to return "false". Fix for bug 8207; bugfix
21140 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
21142 o Minor features (relays, bridges):
21143 - Make bridge relays check once a minute for whether their IP
21144 address has changed, rather than only every 15 minutes. Resolves
21145 bugs 1913 and 1992.
21146 - Refactor resolve_my_address() so it returns the method by which we
21147 decided our public IP address (explicitly configured, resolved from
21148 explicit hostname, guessed from interfaces, learned by gethostname).
21149 Now we can provide more helpful log messages when a relay guesses
21150 its IP address incorrectly (e.g. due to unexpected lines in
21151 /etc/hosts). Resolves ticket 2267.
21152 - Teach bridge-using clients to avoid 0.2.2 bridges when making
21153 microdescriptor-related dir requests, and only fall back to normal
21154 descriptors if none of their bridges can handle microdescriptors
21155 (as opposed to the fix in ticket 4013, which caused them to fall
21156 back to normal descriptors if *any* of their bridges preferred
21157 them). Resolves ticket 4994.
21158 - Randomize the lifetime of our SSL link certificate, so censors can't
21159 use the static value for filtering Tor flows. Resolves ticket 8443;
21160 related to ticket 4014 which was included in 0.2.2.33.
21161 - Support a new version of the link protocol that allows 4-byte circuit
21162 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
21163 a possible resource exhaustion issue. Closes ticket 7351; implements
21166 o Minor features (portability):
21167 - Tweak the curve25519-donna*.c implementations to tolerate systems
21168 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
21169 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
21170 the signs of types during autoconf. This is better than our old
21171 approach, which didn't work when cross-compiling.
21172 - Detect the sign of enum values, rather than assuming that MSC is the
21173 only compiler where enum types are all signed. Fixes bug 7727;
21174 bugfix on 0.2.4.10-alpha.
21176 o Minor features (other):
21177 - Say "KBytes" rather than "KB" in the man page (for various values
21178 of K), to further reduce confusion about whether Tor counts in
21179 units of memory or fractions of units of memory. Resolves ticket 7054.
21180 - Clear the high bit on curve25519 public keys before passing them to
21181 our backend, in case we ever wind up using a backend that doesn't do
21182 so itself. If we used such a backend, and *didn't* clear the high bit,
21183 we could wind up in a situation where users with such backends would
21184 be distinguishable from users without. Fixes bug 8121; bugfix on
21186 - Update to the March 6 2013 Maxmind GeoLite Country database.
21188 o Minor bugfixes (clients):
21189 - When we receive a RELAY_END cell with the reason DONE, or with no
21190 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
21191 status as "connection refused". Previously we reported these cases
21192 as success but then immediately closed the connection. Fixes bug
21193 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
21194 - Downgrade an assertion in connection_ap_expire_beginning to an
21195 LD_BUG message. The fix for bug 8024 should prevent this message
21196 from displaying, but just in case, a warn that we can diagnose
21197 is better than more assert crashes. Fixes bug 8065; bugfix on
21199 - Lower path use bias thresholds to .80 for notice and .60 for warn.
21200 Also make the rate limiting flags for the path use bias log messages
21201 independent from the original path bias flags. Fixes bug 8161;
21202 bugfix on 0.2.4.10-alpha.
21204 o Minor bugfixes (relays):
21205 - Stop trying to resolve our hostname so often (e.g. every time we
21206 think about doing a directory fetch). Now we reuse the cached
21207 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
21208 and 2410 (bugfix on 0.1.2.2-alpha).
21209 - Stop sending a stray "(null)" in some cases for the server status
21210 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
21212 - When choosing which stream on a formerly stalled circuit to wake
21213 first, make better use of the platform's weak RNG. Previously,
21214 we had been using the % ("modulo") operator to try to generate a
21215 1/N chance of picking each stream, but this behaves badly with
21216 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
21218 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
21219 Irix's random() only return 15 bits; Solaris's random() returns more
21220 bits but its RAND_MAX says it only returns 15, and so on. Motivated
21221 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
21223 o Minor bugfixes (directory authorities):
21224 - Directory authorities now use less space when formatting identical
21225 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
21228 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
21229 - Avoid leaking memory if we fail to compute a consensus signature
21230 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
21231 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
21233 - Fix a memory leak during safe-cookie controller authentication.
21234 Bugfix on 0.2.3.13-alpha.
21235 - Avoid memory leak of IPv6 policy content if we fail to format it into
21236 a router descriptor. Bugfix on 0.2.4.7-alpha.
21238 o Minor bugfixes (other code correctness issues):
21239 - Avoid a crash if we fail to generate an extrainfo descriptor.
21240 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
21241 this is CID 718634.
21242 - When detecting the largest possible file descriptor (in order to
21243 close all file descriptors when launching a new program), actually
21244 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
21245 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
21247 - Fix a copy-and-paste error when adding a missing A1 to a routerset
21248 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
21249 Bugfix on 0.2.4.10-alpha.
21250 - Fix an impossible-to-trigger integer overflow when estimating how
21251 long our onionskin queue would take. (This overflow would require us
21252 to accept 4 million onionskins before processing 100 of them.) Fixes
21253 bug 8210; bugfix on 0.2.4.10-alpha.
21255 o Code simplification and refactoring:
21256 - Add a wrapper function for the common "log a message with a
21260 Changes in version 0.2.4.10-alpha - 2013-02-04
21261 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
21262 certain attacks that flood the network with relays; changes the queue
21263 for circuit create requests from a sized-based limit to a time-based
21264 limit; resumes building with MSVC on Windows; and fixes a wide variety
21267 o Major bugfixes (directory authority):
21268 - When computing directory thresholds, ignore any rejected-as-sybil
21269 nodes during the computation so that they can't influence Fast,
21270 Guard, etc. (We should have done this for proposal 109.) Fixes
21272 - When marking a node as a likely sybil, reset its uptime metrics
21273 to zero, so that it cannot time towards getting marked as Guard,
21274 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
21278 - When a TLS write is partially successful but incomplete, remember
21279 that the flushed part has been flushed, and notice that bytes were
21280 actually written. Reported and fixed pseudonymously. Fixes bug
21281 7708; bugfix on Tor 0.1.0.5-rc.
21282 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
21283 ID: these could be used to create unexpected streams and circuits
21284 which would count as "present" to some parts of Tor but "absent"
21285 to others, leading to zombie circuits and streams or to a bandwidth
21286 denial-of-service. Fixes bug 7889; bugfix on every released version
21287 of Tor. Reported by "oftc_must_be_destroyed".
21288 - Rename all macros in our local copy of queue.h to begin with "TOR_".
21289 This change seems the only good way to permanently prevent conflicts
21290 with queue.h on various operating systems. Fixes bug 8107; bugfix
21293 o Major features (relay):
21294 - Instead of limiting the number of queued onionskins (aka circuit
21295 create requests) to a fixed, hard-to-configure number, we limit
21296 the size of the queue based on how many we expect to be able to
21297 process in a given amount of time. We estimate the time it will
21298 take to process an onionskin based on average processing time
21299 of previous onionskins. Closes ticket 7291. You'll never have to
21300 configure MaxOnionsPending again.
21302 o Major features (portability):
21303 - Resume building correctly with MSVC and Makefile.nmake. This patch
21304 resolves numerous bugs and fixes reported by ultramage, including
21305 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
21306 - Make the ntor and curve25519 code build correctly with MSVC.
21307 Fix on 0.2.4.8-alpha.
21310 - When directory authorities are computing thresholds for flags,
21311 never let the threshold for the Fast flag fall below 4096
21312 bytes. Also, do not consider nodes with extremely low bandwidths
21313 when deciding thresholds for various directory flags. This change
21314 should raise our threshold for Fast relays, possibly in turn
21315 improving overall network performance; see ticket 1854. Resolves
21317 - The Tor client now ignores sub-domain components of a .onion
21318 address. This change makes HTTP "virtual" hosting
21319 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
21320 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
21321 hosted on the same hidden service. Implements proposal 204.
21322 - We compute the overhead from passing onionskins back and forth to
21323 cpuworkers, and report it when dumping statistics in response to
21324 SIGUSR1. Supports ticket 7291.
21326 o Minor features (path selection):
21327 - When deciding whether we have enough descriptors to build circuits,
21328 instead of looking at raw relay counts, look at which fraction
21329 of (bandwidth-weighted) paths we're able to build. This approach
21330 keeps clients from building circuits if their paths are likely to
21331 stand out statistically. The default fraction of paths needed is
21332 taken from the consensus directory; you can override it with the
21333 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
21334 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
21335 and we have GeoIP information, also exclude all nodes with unknown
21336 countries "??" and "A1". This behavior is controlled by the
21337 new GeoIPExcludeUnknown option: you can make such nodes always
21338 excluded with "GeoIPExcludeUnknown 1", and disable the feature
21339 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
21340 gets you the default behavior. Implements feature 7706.
21341 - Path Use Bias: Perform separate accounting for successful circuit
21342 use. Keep separate statistics on stream attempt rates versus stream
21343 success rates for each guard. Provide configurable thresholds to
21344 determine when to emit log messages or disable use of guards that
21345 fail too many stream attempts. Resolves ticket 7802.
21347 o Minor features (log messages):
21348 - When learning a fingerprint for a bridge, log its corresponding
21349 transport type. Implements ticket 7896.
21350 - Improve the log message when "Bug/attack: unexpected sendme cell
21351 from client" occurs, to help us track bug 8093.
21354 - Remove a couple of extraneous semicolons that were upsetting the
21355 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
21356 bugfix on 0.2.2.1-alpha.
21357 - Remove a source of rounding error during path bias count scaling;
21358 don't count cannibalized circuits as used for path bias until we
21359 actually try to use them; and fix a circuit_package_relay_cell()
21360 warning message about n_chan==NULL. Fixes bug 7802.
21361 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
21362 actually link against nacl when we're configured to use it. Fixes
21363 bug 7972; bugfix on 0.2.4.8-alpha.
21364 - Compile correctly with the --disable-curve25519 option. Fixes
21365 bug 8153; bugfix on 0.2.4.8-alpha.
21367 o Build improvements:
21368 - Do not report status verbosely from autogen.sh unless the -v flag
21369 is specified. Fixes issue 4664. Patch from Onizuka.
21370 - Replace all calls to snprintf() outside of src/ext with
21371 tor_snprintf(). Also remove the #define to replace snprintf with
21372 _snprintf on Windows; they have different semantics, and all of
21373 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
21374 - Try to detect if we are ever building on a platform where
21375 memset(...,0,...) does not set the value of a double to 0.0. Such
21376 platforms are permitted by the C standard, though in practice
21377 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
21378 currently support them, but it's better to detect them and fail
21379 than to perform erroneously.
21381 o Removed features:
21382 - Stop exporting estimates of v2 and v3 directory traffic shares
21383 in extrainfo documents. They were unneeded and sometimes inaccurate.
21384 Also stop exporting any v2 directory request statistics. Resolves
21386 - Drop support for detecting and warning about versions of Libevent
21387 before 1.3e. Nothing reasonable ships with them any longer;
21388 warning the user about them shouldn't be needed. Resolves ticket
21391 o Code simplifications and refactoring:
21392 - Rename "isin" functions to "contains", for grammar. Resolves
21394 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
21395 with the natural logarithm function from the system libm. Resolves
21399 Changes in version 0.2.4.9-alpha - 2013-01-15
21400 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
21401 work more robustly.
21404 - Fix backward compatibility logic when receiving an embedded ntor
21405 handshake tunneled in a CREATE cell. This clears up the "Bug:
21406 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
21410 Changes in version 0.2.4.8-alpha - 2013-01-14
21411 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
21412 risks, adds a new stronger and faster circuit handshake, and offers
21413 stronger and faster link encryption when both sides support it.
21416 - Preliminary support for directory guards (proposal 207): when
21417 possible, clients now use their entry guards for non-anonymous
21418 directory requests. This can help prevent client enumeration. Note
21419 that this behavior only works when we have a usable consensus
21420 directory, and when options about what to download are more or less
21421 standard. In the future we should re-bootstrap from our guards,
21422 rather than re-bootstrapping from the preconfigured list of
21423 directory sources that ships with Tor. Resolves ticket 6526.
21424 - Tor relays and clients now support a better CREATE/EXTEND cell
21425 format, allowing the sender to specify multiple address, identity,
21426 and handshake types. Implements Robert Ransom's proposal 200;
21427 closes ticket 7199.
21429 o Major features (new circuit handshake):
21430 - Tor now supports a new circuit extension handshake designed by Ian
21431 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
21432 circuit extension handshake, later called "TAP", was a bit slow
21433 (especially on the relay side), had a fragile security proof, and
21434 used weaker keys than we'd now prefer. The new circuit handshake
21435 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
21436 function, making it significantly more secure than the older
21437 handshake, and significantly faster. Tor can use one of two built-in
21438 pure-C curve25519-donna implementations by Adam Langley, or it
21439 can link against the "nacl" library for a tuned version if present.
21441 The built-in version is very fast for 64-bit systems when building
21442 with GCC. The built-in 32-bit version is still faster than the
21443 old TAP protocol, but using libnacl is better on most such hosts.
21445 Clients don't currently use this protocol by default, since
21446 comparatively few clients support it so far. To try it, set
21447 UseNTorHandshake to 1.
21449 Implements proposal 216; closes ticket 7202.
21451 o Major features (better link encryption):
21452 - Relays can now enable the ECDHE TLS ciphersuites when available
21453 and appropriate. These ciphersuites let us negotiate forward-secure
21454 TLS secret keys more safely and more efficiently than with our
21455 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
21456 public relays prefer the (faster) P224 group, and bridges prefer
21457 the (more common) P256 group; you can override this with the
21460 Enabling these ciphers was a little tricky, since for a long time,
21461 clients had been claiming to support them without actually doing
21462 so, in order to foil fingerprinting. But with the client-side
21463 implementation of proposal 198 in 0.2.3.17-beta, clients can now
21464 match the ciphers from recent Firefox versions *and* list the
21465 ciphers they actually mean, so relays can believe such clients
21466 when they advertise ECDHE support in their TLS ClientHello messages.
21468 This feature requires clients running 0.2.3.17-beta or later,
21469 and requires both sides to be running OpenSSL 1.0.0 or later
21470 with ECC support. OpenSSL 1.0.1, with the compile-time option
21471 "enable-ec_nistp_64_gcc_128", is highly recommended.
21473 Implements the relay side of proposal 198; closes ticket 7200.
21476 - Avoid crashing when, as a relay without IPv6-exit support, a
21477 client insists on getting an IPv6 address or nothing. Fixes bug
21478 7814; bugfix on 0.2.4.7-alpha.
21481 - Improve circuit build timeout handling for hidden services.
21482 In particular: adjust build timeouts more accurately depending
21483 upon the number of hop-RTTs that a particular circuit type
21484 undergoes. Additionally, launch intro circuits in parallel
21485 if they timeout, and take the first one to reply as valid.
21486 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
21487 separate error codes; or at least, don't break for that reason.
21488 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
21489 - Update to the January 2 2013 Maxmind GeoLite Country database.
21491 o Minor features (testing):
21492 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
21493 (P-256) Diffie-Hellman handshakes to src/or/bench.
21494 - Add benchmark functions to test onion handshake performance.
21496 o Minor features (path bias detection):
21497 - Alter the Path Bias log messages to be more descriptive in terms
21498 of reporting timeouts and other statistics.
21499 - Create three levels of Path Bias log messages, as opposed to just
21500 two. These are configurable via consensus as well as via the torrc
21501 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
21502 The default values are 0.70, 0.50, and 0.30 respectively.
21503 - Separate the log message levels from the decision to drop guards,
21504 which also is available via torrc option PathBiasDropGuards.
21505 PathBiasDropGuards still defaults to 0 (off).
21506 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
21507 in combination with PathBiasExtremeRate.
21508 - Increase the default values for PathBiasScaleThreshold and
21509 PathBiasCircThreshold from (200, 20) to (300, 150).
21510 - Add in circuit usage accounting to path bias. If we try to use a
21511 built circuit but fail for any reason, it counts as path bias.
21512 Certain classes of circuits where the adversary gets to pick your
21513 destination node are exempt from this accounting. Usage accounting
21514 can be specifically disabled via consensus parameter or torrc.
21515 - Convert all internal path bias state to double-precision floating
21516 point, to avoid roundoff error and other issues.
21517 - Only record path bias information for circuits that have completed
21518 *two* hops. Assuming end-to-end tagging is the attack vector, this
21519 makes us more resilient to ambient circuit failure without any
21520 detection capability loss.
21522 o Minor bugfixes (log messages):
21523 - Rate-limit the "No circuits are opened. Relaxed timeout for a
21524 circuit with channel state open..." message to once per hour to
21525 keep it from filling the notice logs. Mitigates bug 7799 but does
21526 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
21527 - Avoid spurious warnings when configuring multiple client ports of
21528 which only some are nonlocal. Previously, we had claimed that some
21529 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
21532 o Code simplifications and refactoring:
21533 - Get rid of a couple of harmless clang warnings, where we compared
21534 enums to ints. These warnings are newly introduced in clang 3.2.
21535 - Split the onion.c file into separate modules for the onion queue
21536 and the different handshakes it supports.
21537 - Remove the marshalling/unmarshalling code for sending requests to
21538 cpuworkers over a socket, and instead just send structs. The
21539 recipient will always be the same Tor binary as the sender, so
21540 any encoding is overkill.
21543 Changes in version 0.2.4.7-alpha - 2012-12-24
21544 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
21545 directory mirrors for more robust bootstrapping; fixes more issues where
21546 clients with changing network conditions refuse to make any circuits;
21547 adds initial support for exiting to IPv6 addresses; resumes being able
21548 to update our GeoIP database, and includes the geoip6 file this time;
21549 turns off the client-side DNS cache by default due to privacy risks;
21550 and fixes a variety of other issues.
21552 o Major features (client resilience):
21553 - Add a new "FallbackDir" torrc option to use when we can't use
21554 a directory mirror from the consensus (either because we lack a
21555 consensus, or because they're all down). Currently, all authorities
21556 are fallbacks by default, and there are no other default fallbacks,
21557 but that will change. This option will allow us to give clients a
21558 longer list of servers to try to get a consensus from when first
21559 connecting to the Tor network, and thereby reduce load on the
21560 directory authorities. Implements proposal 206, "Preconfigured
21561 directory sources for bootstrapping". We also removed the old
21562 "FallbackNetworkstatus" option, since we never got it working well
21563 enough to use it. Closes bug 572.
21564 - If we have no circuits open, use a relaxed timeout (the
21565 95-percentile cutoff) until a circuit succeeds. This heuristic
21566 should allow Tor to succeed at building circuits even when the
21567 network connection drastically changes. Should help with bug 3443.
21569 o Major features (IPv6):
21570 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
21571 connectivity, then set the IPv6Exit flag to 1. Also make sure your
21572 exit policy reads as you would like: the address * applies to all
21573 address families, whereas *4 is IPv4 address only, and *6 is IPv6
21574 addresses only. On the client side, you'll need to wait until the
21575 authorities have upgraded, wait for enough exits to support IPv6,
21576 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
21577 ticket 5547, implements proposal 117 as revised in proposal 208.
21579 We DO NOT recommend that clients with actual anonymity needs start
21580 using IPv6 over Tor yet, since not enough exits support it yet.
21582 o Major features (geoip database):
21583 - Maxmind began labelling Tor relays as being in country "A1",
21584 which breaks by-country node selection inside Tor. Now we use a
21585 script to replace "A1" ("Anonymous Proxy") entries in our geoip
21586 file with real country codes. This script fixes about 90% of "A1"
21587 entries automatically and uses manual country code assignments to
21588 fix the remaining 10%. See src/config/README.geoip for details.
21589 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
21590 Country database, as modified above.
21592 o Major bugfixes (client-side DNS):
21593 - Turn off the client-side DNS cache by default. Updating and using
21594 the DNS cache is now configurable on a per-client-port
21595 level. SOCKSPort, DNSPort, etc lines may now contain
21596 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
21597 cache these types of DNS answers when we receive them from an
21598 exit node in response to an application request on this port, and
21599 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
21600 cached DNS answers of these types, we shouldn't use them. It's
21601 potentially risky to use cached DNS answers at the client, since
21602 doing so can indicate to one exit what answers we've gotten
21603 for DNS lookups in the past. With IPv6, this becomes especially
21604 problematic. Using cached DNS answers for requests on the same
21605 circuit would present less linkability risk, since all traffic
21606 on a circuit is already linkable, but it would also provide
21607 little performance benefit: the exit node caches DNS replies
21608 too. Implements a simplified version of Proposal 205. Implements
21611 o Major bugfixes (other):
21612 - Alter circuit build timeout measurement to start at the point
21613 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
21614 initialization). This should make our timeout measurements more
21615 uniform. Previously, we were sometimes including ORconn setup time
21616 in our circuit build time measurements. Should resolve bug 3443.
21617 - Fix an assertion that could trigger in hibernate_go_dormant() when
21618 closing an or_connection_t: call channel_mark_for_close() rather
21619 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
21621 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
21622 7655; bugfix on 0.2.4.6-alpha.
21625 - Add a new torrc option "ServerTransportListenAddr" to let bridge
21626 operators select the address where their pluggable transports will
21627 listen for connections. Resolves ticket 7013.
21628 - Allow an optional $ before the node identity digest in the
21629 controller command GETINFO ns/id/<identity>, for consistency with
21630 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
21631 - Log packaged cell fullness as part of the heartbeat message.
21632 Diagnosis to try to determine the extent of bug 7743.
21634 o Minor features (IPv6):
21635 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
21636 prefer to hand out virtual IPv6 addresses, since there are more of
21637 them and we can't run out. To override this behavior and make IPv4
21638 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
21639 or DNSPort you're using for resolving. Implements ticket 7571.
21640 - AutomapHostsOnResolve responses are now randomized, to avoid
21641 annoying situations where Tor is restarted and applications
21642 connect to the wrong addresses.
21643 - Never try more than 1000 times to pick a new virtual address when
21644 AutomapHostsOnResolve is set. That's good enough so long as we
21645 aren't close to handing out our entire virtual address space;
21646 if you're getting there, it's best to switch to IPv6 virtual
21650 - The ADDRMAP command can no longer generate an ill-formed error
21651 code on a failed MAPADDRESS. It now says "internal" rather than
21652 an English sentence fragment with spaces in the middle. Bugfix on
21653 Tor 0.2.0.19-alpha.
21654 - Fix log messages and comments to avoid saying "GMT" when we mean
21655 "UTC". Fixes bug 6113.
21656 - Compile on win64 using mingw64. Fixes bug 7260; patches from
21658 - Fix a crash when debugging unit tests on Windows: deallocate a
21659 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
21660 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
21663 - The DirServer option is now DirAuthority, for consistency with
21664 current naming patterns. You can still use the old DirServer form.
21666 o Code simplification and refactoring:
21667 - Move the client-side address-map/virtual-address/DNS-cache code
21668 out of connection_edge.c into a new addressmap.c module.
21669 - Remove unused code for parsing v1 directories and "running routers"
21670 documents. Fixes bug 6887.
21673 Changes in version 0.2.3.25 - 2012-11-19
21674 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
21675 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
21676 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
21677 programmer, and friend. Unstinting in his dedication to the cause of
21678 freedom, he inspired and helped many of us as we began our work on
21679 anonymity, and inspires us still. Please honor his memory by writing
21680 software to protect people's freedoms, and by helping others to do so.
21682 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
21683 significantly reduced directory overhead (via microdescriptors),
21684 enormous crypto performance improvements for fast relays on new
21685 enough hardware, a new v3 TLS handshake protocol that can better
21686 resist fingerprinting, support for protocol obfuscation plugins (aka
21687 pluggable transports), better scalability for hidden services, IPv6
21688 support for bridges, performance improvements like allowing clients
21689 to skip the first round-trip on the circuit ("optimistic data") and
21690 refilling token buckets more often, a new "stream isolation" design
21691 to isolate different applications on different circuits, and many
21692 stability, security, and privacy fixes.
21695 - Tor tries to wipe potentially sensitive data after using it, so
21696 that if some subsequent security failure exposes Tor's memory,
21697 the damage will be limited. But we had a bug where the compiler
21698 was eliminating these wipe operations when it decided that the
21699 memory was no longer visible to a (correctly running) program,
21700 hence defeating our attempt at defense in depth. We fix that
21701 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
21702 is unlikely to optimize away. Future versions of Tor may use
21703 a less ridiculously heavy approach for this. Fixes bug 7352.
21704 Reported in an article by Andrey Karpov.
21707 - Fix a harmless bug when opting against publishing a relay descriptor
21708 because DisableNetwork is set. Fixes bug 7464; bugfix on
21712 Changes in version 0.2.4.6-alpha - 2012-11-13
21713 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
21714 makes our defense-in-depth memory wiping more reliable, and begins to
21715 count IPv6 addresses in bridge statistics,
21718 - Fix an assertion failure that could occur when closing a connection
21719 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
21721 - Tor tries to wipe potentially sensitive data after using it, so
21722 that if some subsequent security failure exposes Tor's memory,
21723 the damage will be limited. But we had a bug where the compiler
21724 was eliminating these wipe operations when it decided that the
21725 memory was no longer visible to a (correctly running) program,
21726 hence defeating our attempt at defense in depth. We fix that
21727 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
21728 is unlikely to optimize away. Future versions of Tor may use
21729 a less ridiculously heavy approach for this. Fixes bug 7352.
21730 Reported in an article by Andrey Karpov.
21733 - Add GeoIP database for IPv6 addresses. The new config option
21735 - Bridge statistics now count bridge clients connecting over IPv6:
21736 bridge statistics files now list "bridge-ip-versions" and
21737 extra-info documents list "geoip6-db-digest". The control protocol
21738 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
21739 implementation by "shkoo", addressing ticket 5055.
21742 - Warn when we are binding low ports when hibernation is enabled;
21743 previously we had warned when we were _advertising_ low ports with
21744 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
21745 - Fix a harmless bug when opting against publishing a relay descriptor
21746 because DisableNetwork is set. Fixes bug 7464; bugfix on
21748 - Add warning message when a managed proxy dies during configuration.
21749 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
21750 - Fix a linking error when building tor-fw-helper without miniupnp.
21751 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
21752 - Check for closing an or_connection_t without going through correct
21753 channel functions; emit a warning and then call
21754 connection_or_close_for_error() so we don't assert as in bugs 7212
21756 - Compile correctly on compilers without C99 designated initializer
21757 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
21758 - Avoid a possible assert that can occur when channel_send_destroy() is
21759 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
21760 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
21761 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
21762 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
21763 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
21765 o Code simplification and refactoring:
21766 - Start using OpenBSD's implementation of queue.h, so that we don't
21767 need to hand-roll our own pointer and list structures whenever we
21768 need them. (We can't rely on a sys/queue.h, since some operating
21769 systems don't have them, and the ones that do have them don't all
21770 present the same extensions.)
21773 Changes in version 0.2.4.5-alpha - 2012-10-25
21774 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
21775 two important security vulnerabilities that could lead to remotely
21776 triggerable relay crashes, fix a major bug that was preventing clients
21777 from choosing suitable exit nodes, and refactor some of our code.
21779 o Major bugfixes (security, also in 0.2.3.24-rc):
21780 - Fix a group of remotely triggerable assertion failures related to
21781 incorrect link protocol negotiation. Found, diagnosed, and fixed
21782 by "some guy from France". Fix for CVE-2012-2250; bugfix on
21784 - Fix a denial of service attack by which any directory authority
21785 could crash all the others, or by which a single v2 directory
21786 authority could crash everybody downloading v2 directory
21787 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
21789 o Major bugfixes (also in 0.2.3.24-rc):
21790 - When parsing exit policy summaries from microdescriptors, we had
21791 previously been ignoring the last character in each one, so that
21792 "accept 80,443,8080" would be treated by clients as indicating
21793 a node that allows access to ports 80, 443, and 808. That would
21794 lead to clients attempting connections that could never work,
21795 and ignoring exit nodes that would support their connections. Now
21796 clients parse these exit policy summaries correctly. Fixes bug 7192;
21797 bugfix on 0.2.3.1-alpha.
21799 o Minor bugfixes (also in 0.2.3.24-rc):
21800 - Clients now consider the ClientRejectInternalAddresses config option
21801 when using a microdescriptor consensus stanza to decide whether
21802 an exit relay would allow exiting to an internal address. Fixes
21803 bug 7190; bugfix on 0.2.3.1-alpha.
21806 - Only disable TLS session ticket support when running as a TLS
21807 server. Now clients will blend better with regular Firefox
21808 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
21810 o Code simplification and refactoring:
21811 - Start using OpenBSD's implementation of queue.h (originally by
21813 - Move the entry node code from circuitbuild.c to its own file.
21814 - Move the circuit build timeout tracking code from circuitbuild.c
21818 Changes in version 0.2.3.24-rc - 2012-10-25
21819 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
21820 could lead to remotely triggerable relay crashes, and fixes
21821 a major bug that was preventing clients from choosing suitable exit
21824 o Major bugfixes (security):
21825 - Fix a group of remotely triggerable assertion failures related to
21826 incorrect link protocol negotiation. Found, diagnosed, and fixed
21827 by "some guy from France". Fix for CVE-2012-2250; bugfix on
21829 - Fix a denial of service attack by which any directory authority
21830 could crash all the others, or by which a single v2 directory
21831 authority could crash everybody downloading v2 directory
21832 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
21835 - When parsing exit policy summaries from microdescriptors, we had
21836 previously been ignoring the last character in each one, so that
21837 "accept 80,443,8080" would be treated by clients as indicating
21838 a node that allows access to ports 80, 443, and 808. That would
21839 lead to clients attempting connections that could never work,
21840 and ignoring exit nodes that would support their connections. Now
21841 clients parse these exit policy summaries correctly. Fixes bug 7192;
21842 bugfix on 0.2.3.1-alpha.
21845 - Clients now consider the ClientRejectInternalAddresses config option
21846 when using a microdescriptor consensus stanza to decide whether
21847 an exit relay would allow exiting to an internal address. Fixes
21848 bug 7190; bugfix on 0.2.3.1-alpha.
21851 Changes in version 0.2.4.4-alpha - 2012-10-20
21852 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
21853 vulnerability introduced by a change in OpenSSL, fixes a remotely
21854 triggerable assert, and adds new channel_t and circuitmux_t abstractions
21855 that will make it easier to test new connection transport and cell
21856 scheduling algorithms.
21858 o New directory authorities (also in 0.2.3.23-rc):
21859 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
21860 authority. Closes ticket 5749.
21862 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
21863 - Disable TLS session tickets. OpenSSL's implementation was giving
21864 our TLS session keys the lifetime of our TLS context objects, when
21865 perfect forward secrecy would want us to discard anything that
21866 could decrypt a link connection as soon as the link connection
21867 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
21868 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
21869 - Discard extraneous renegotiation attempts once the V3 link
21870 protocol has been initiated. Failure to do so left us open to
21871 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
21872 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
21874 o Internal abstraction features:
21875 - Introduce new channel_t abstraction between circuits and
21876 or_connection_t to allow for implementing alternate OR-to-OR
21877 transports. A channel_t is an abstract object which can either be a
21878 cell-bearing channel, which is responsible for authenticating and
21879 handshaking with the remote OR and transmitting cells to and from
21880 it, or a listening channel, which spawns new cell-bearing channels
21881 at the request of remote ORs. Implements part of ticket 6465.
21882 - Also new is the channel_tls_t subclass of channel_t, adapting it
21883 to the existing or_connection_t code. The V2/V3 protocol handshaking
21884 code which formerly resided in command.c has been moved below the
21885 channel_t abstraction layer and may be found in channeltls.c now.
21886 Implements the rest of ticket 6465.
21887 - Introduce new circuitmux_t storing the queue of circuits for
21888 a channel; this encapsulates and abstracts the queue logic and
21889 circuit selection policy, and allows the latter to be overridden
21890 easily by switching out a policy object. The existing EWMA behavior
21891 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
21893 o Required libraries:
21894 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
21895 strongly recommended.
21898 - Warn users who run hidden services on a Tor client with
21899 UseEntryGuards disabled that their hidden services will be
21900 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
21901 attack which motivated Tor to support entry guards in the first
21902 place). Resolves ticket 6889.
21903 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
21904 dhill. Resolves ticket 6982.
21905 - Option OutboundBindAddress can be specified multiple times and
21906 accepts IPv6 addresses. Resolves ticket 6876.
21908 o Minor bugfixes (also in 0.2.3.23-rc):
21909 - Don't serve or accept v2 hidden service descriptors over a
21910 relay's DirPort. It's never correct to do so, and disabling it
21911 might make it more annoying to exploit any bugs that turn up in the
21912 descriptor-parsing code. Fixes bug 7149.
21913 - Fix two cases in src/or/transports.c where we were calling
21914 fmt_addr() twice in a parameter list. Bug found by David
21915 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
21916 - Fix memory leaks whenever we logged any message about the "path
21917 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
21918 - When relays refuse a "create" cell because their queue of pending
21919 create cells is too big (typically because their cpu can't keep up
21920 with the arrival rate), send back reason "resource limit" rather
21921 than reason "internal", so network measurement scripts can get a
21922 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
21925 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
21926 - Free some more still-in-use memory at exit, to make hunting for
21927 memory leaks easier. Resolves bug 7029.
21928 - When a Tor client gets a "truncated" relay cell, the first byte of
21929 its payload specifies why the circuit was truncated. We were
21930 ignoring this 'reason' byte when tearing down the circuit, resulting
21931 in the controller not being told why the circuit closed. Now we
21932 pass the reason from the truncated cell to the controller. Bugfix
21933 on 0.1.2.3-alpha; fixes bug 7039.
21934 - Downgrade "Failed to hand off onionskin" messages to "debug"
21935 severity, since they're typically redundant with the "Your computer
21936 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
21937 - Make clients running with IPv6 bridges connect over IPv6 again,
21938 even without setting new config options ClientUseIPv6 and
21939 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
21940 - Use square brackets around IPv6 addresses in numerous places
21941 that needed them, including log messages, HTTPS CONNECT proxy
21942 requests, TransportProxy statefile entries, and pluggable transport
21943 extra-info lines. Fixes bug 7011; patch by David Fifield.
21945 o Code refactoring and cleanup:
21946 - Source files taken from other packages now reside in src/ext;
21947 previously they were scattered around the rest of Tor.
21948 - Avoid use of reserved identifiers in our C code. The C standard
21949 doesn't like us declaring anything that starts with an
21950 underscore, so let's knock it off before we get in trouble. Fix
21951 for bug 1031; bugfix on the first Tor commit.
21954 Changes in version 0.2.3.23-rc - 2012-10-20
21955 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
21956 vulnerability introduced by a change in OpenSSL, and fixes a variety
21957 of smaller bugs in preparation for the release.
21959 o New directory authorities:
21960 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
21961 authority. Closes ticket 5749.
21963 o Major bugfixes (security/privacy):
21964 - Disable TLS session tickets. OpenSSL's implementation was giving
21965 our TLS session keys the lifetime of our TLS context objects, when
21966 perfect forward secrecy would want us to discard anything that
21967 could decrypt a link connection as soon as the link connection
21968 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
21969 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
21970 - Discard extraneous renegotiation attempts once the V3 link
21971 protocol has been initiated. Failure to do so left us open to
21972 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
21973 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
21976 - Fix a possible crash bug when checking for deactivated circuits
21977 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
21978 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
21980 o Minor bugfixes (on 0.2.3.x):
21981 - Fix two cases in src/or/transports.c where we were calling
21982 fmt_addr() twice in a parameter list. Bug found by David
21983 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
21984 - Convert an assert in the pathbias code to a log message. The assert
21985 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
21986 bugfix on 0.2.3.17-beta.
21987 - Fix memory leaks whenever we logged any message about the "path
21988 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
21990 o Minor bugfixes (on 0.2.2.x and earlier):
21991 - Don't serve or accept v2 hidden service descriptors over a relay's
21992 DirPort. It's never correct to do so, and disabling it might
21993 make it more annoying to exploit any bugs that turn up in the
21994 descriptor-parsing code. Fixes bug 7149.
21995 - When relays refuse a "create" cell because their queue of pending
21996 create cells is too big (typically because their cpu can't keep up
21997 with the arrival rate), send back reason "resource limit" rather
21998 than reason "internal", so network measurement scripts can get a
21999 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
22000 - Correct file sizes when reading binary files on Cygwin, to avoid
22001 a bug where Tor would fail to read its state file. Fixes bug 6844;
22002 bugfix on 0.1.2.7-alpha.
22003 - Avoid undefined behavior when parsing the list of supported
22004 rendezvous/introduction protocols in a hidden service descriptor.
22005 Previously, Tor would have confused (as-yet-unused) protocol version
22006 numbers greater than 32 with lower ones on many platforms. Fixes
22007 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
22009 o Documentation fixes:
22010 - Clarify that hidden services are TCP only. Fixes bug 6024.
22013 Changes in version 0.2.4.3-alpha - 2012-09-22
22014 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
22015 assertion, resumes letting relays test reachability of their DirPort,
22016 and cleans up a bunch of smaller bugs.
22019 - Fix an assertion failure in tor_timegm() that could be triggered
22020 by a badly formatted directory object. Bug found by fuzzing with
22021 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
22024 - Fix a possible crash bug when checking for deactivated circuits
22025 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
22026 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
22027 - Allow routers to detect that their own DirPorts are running. When
22028 we removed support for versions_supports_begindir, we also
22029 accidentally removed the mechanism we used to self-test our
22030 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
22031 bugfix on 0.2.4.2-alpha.
22033 o Security features:
22034 - Switch to a completely time-invariant approach for picking nodes
22035 weighted by bandwidth. Our old approach would run through the
22036 part of the loop after it had made its choice slightly slower
22037 than it ran through the part of the loop before it had made its
22038 choice. Addresses ticket 6538.
22039 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
22040 by tor2web clients allows hidden services to identify tor2web
22041 clients through their repeated selection of the same rendezvous
22042 and introduction point circuit endpoints (their guards). Resolves
22046 - Enable Tor to read configuration, state, and key information from
22047 a FIFO. Previously Tor would only read from files with a positive
22048 stat.st_size. Code from meejah; fixes bug 6044.
22051 - Correct file sizes when reading binary files on Cygwin, to avoid
22052 a bug where Tor would fail to read its state file. Fixes bug 6844;
22053 bugfix on 0.1.2.7-alpha.
22054 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
22055 bugfix on 0.2.0.3-alpha.
22056 - When complaining about a client port on a public address, log
22057 which address we're complaining about. Fixes bug 4020; bugfix on
22058 0.2.3.3-alpha. Patch by Tom Fitzhenry.
22059 - Convert an assert in the pathbias code to a log message. The assert
22060 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
22061 bugfix on 0.2.3.17-beta.
22062 - Our new buildsystem was overzealous about rebuilding manpages: it
22063 would rebuild them all whenever any one of them changed. Now our
22064 dependency checking should be correct. Fixes bug 6843; bugfix on
22066 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
22067 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
22068 - Correct log printout about which address family is preferred
22069 when connecting to a bridge with both an IPv4 and IPv6 OR port.
22070 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
22072 o Minor bugfixes (code cleanliness):
22073 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
22074 with large values. This situation was untriggered, but nevertheless
22075 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
22076 - Reject consensus votes with more than 64 known-flags. We aren't even
22077 close to that limit yet, and our code doesn't handle it correctly.
22078 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
22079 - Avoid undefined behavior when parsing the list of supported
22080 rendezvous/introduction protocols in a hidden service descriptor.
22081 Previously, Tor would have confused (as-yet-unused) protocol version
22082 numbers greater than 32 with lower ones on many platforms. Fixes
22083 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
22084 - Fix handling of rendezvous client authorization types over 8.
22085 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
22086 - Fix building with older versions of GCC (2.95, for one) that don't
22087 like preprocessor directives inside macro arguments. Found by
22088 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
22089 - Switch weighted node selection rule from using a list of doubles
22090 to using a list of int64_t. This change should make the process
22091 slightly easier to debug and maintain. Needed to finish ticket 6538.
22093 o Code simplification and refactoring:
22094 - Move the generic "config" code into a new file, and have "config.c"
22095 hold only torrc- and state-related code. Resolves ticket 6823.
22096 - Move the core of our "choose a weighted element at random" logic
22097 into its own function, and give it unit tests. Now the logic is
22098 testable, and a little less fragile too.
22099 - Removed the testing_since field of node_t, which hasn't been used
22100 for anything since 0.2.0.9-alpha.
22102 o Documentation fixes:
22103 - Clarify that hidden services are TCP only. Fixes bug 6024.
22104 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
22108 Changes in version 0.2.3.22-rc - 2012-09-11
22109 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
22113 - Fix an assertion failure in tor_timegm() that could be triggered
22114 by a badly formatted directory object. Bug found by fuzzing with
22115 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
22118 - Avoid segfault when starting up having run with an extremely old
22119 version of Tor and parsing its state file. Fixes bug 6801; bugfix
22123 Changes in version 0.2.2.39 - 2012-09-11
22124 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
22128 - Fix an assertion failure in tor_timegm() that could be triggered
22129 by a badly formatted directory object. Bug found by fuzzing with
22130 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
22131 - Do not crash when comparing an address with port value 0 to an
22132 address policy. This bug could have been used to cause a remote
22133 assertion failure by or against directory authorities, or to
22134 allow some applications to crash clients. Fixes bug 6690; bugfix
22138 Changes in version 0.2.4.2-alpha - 2012-09-10
22139 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
22140 raises the default rate limiting even more, and makes the bootstrapping
22141 log messages less noisy.
22144 - Automatically forward the TCP ports of pluggable transport
22145 proxies using tor-fw-helper if PortForwarding is enabled. Implements
22149 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
22150 to 1GB/1GB. The previous defaults were intended to be "basically
22151 infinite", but it turns out they're now limiting our 100mbit+
22152 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
22153 last time we raised it).
22156 - Detect when we're running with a version of OpenSSL other than the
22157 one we compiled with. This has occasionally given people hard-to-
22159 - Log fewer lines at level "notice" about our OpenSSL and Libevent
22160 versions and capabilities when everything is going right. Resolves
22161 part of ticket 6736.
22162 - Directory authorities no long accept descriptors for any version of
22163 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
22164 These versions are insecure, unsupported, or both. Implements
22168 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
22169 to start with a triple-underscore so the controller won't touch it.
22170 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
22171 - Avoid segfault when starting up having run with an extremely old
22172 version of Tor and parsing its state file. Fixes bug 6801; bugfix
22174 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
22175 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
22176 - Don't follow the NULL pointer if microdescriptor generation fails.
22177 (This does not appear to be triggerable, but it's best to be safe.)
22178 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
22179 - Fix mis-declared dependencies on src/common/crypto.c and
22180 src/or/tor_main.c that could break out-of-tree builds under some
22181 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
22182 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
22183 6778; bugfix on 0.2.4.1-alpha.
22184 - Fix a harmless (in this case) build warning for implicitly
22185 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
22187 o Removed features:
22188 - Now that all versions before 0.2.2.x are disallowed, we no longer
22189 need to work around their missing features. Thus we can remove a
22190 bunch of compatibility code.
22192 o Code refactoring:
22193 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
22194 TCP ports to forward. In the past it only accepted two ports:
22195 the ORPort and the DirPort.
22198 Changes in version 0.2.4.1-alpha - 2012-09-05
22199 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
22200 bridgedb; lets relays use IPv6 addresses and directory authorities
22201 advertise them; and switches to a cleaner build interface.
22203 This is the first alpha release in a new series, so expect there to
22204 be bugs. Users who would rather test out a more stable branch should
22205 stay with 0.2.3.x for now.
22207 o Major features (bridges):
22208 - Bridges now report the pluggable transports they support to the
22209 bridge authority, so it can pass the supported transports on to
22210 bridgedb and/or eventually do reachability testing. Implements
22213 o Major features (IPv6):
22214 - Bridge authorities now accept IPv6 bridge addresses and include
22215 them in network status documents. Implements ticket 5534.
22216 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
22217 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
22218 to happen. Implements ticket 5535.
22219 - All kind of relays, not just bridges, can now advertise an IPv6
22220 OR port. Implements ticket 6362.
22221 - Directory authorities vote on IPv6 OR ports using the new consensus
22222 method 14. Implements ticket 6363.
22224 o Major features (build):
22225 - Switch to a nonrecursive Makefile structure. Now instead of each
22226 Makefile.am invoking other Makefile.am's, there is a master
22227 Makefile.am that includes the others. This change makes our build
22228 process slightly more maintainable, and improves parallelism for
22229 building with make -j. Original patch by Stewart Smith; various
22230 fixes by Jim Meyering.
22231 - Where available, we now use automake's "silent" make rules by
22232 default, so that warnings are easier to spot. You can get the old
22233 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
22235 o Minor features (code security and spec conformance):
22236 - Clear keys and key-derived material left on the stack in
22237 rendservice.c and rendclient.c. Check return value of
22238 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
22239 These fixes should make us more forward-secure against cold-boot
22240 attacks and the like. Fixes bug 2385.
22241 - Reject EXTEND cells sent to nonexistent streams. According to the
22242 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
22243 we were only checking for stream IDs that were currently in use.
22244 Found while hunting for more instances of bug 6271. Bugfix on
22245 0.0.2pre8, which introduced incremental circuit construction.
22247 o Minor features (streamlining);
22248 - No longer include the "opt" prefix when generating routerinfos
22249 or v2 directories: it has been needless since Tor 0.1.2. Closes
22251 - Remove some now-needless code that tried to aggressively flush
22252 OR connections as data was added to them. Since 0.2.0.1-alpha, our
22253 cell queue logic has saved us from the failure mode that this code
22254 was supposed to prevent. Removing this code will limit the number
22255 of baroque control flow paths through Tor's network logic. Reported
22256 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
22258 o Minor features (controller):
22259 - Add a "GETINFO signal/names" control port command. Implements
22261 - Provide default values for all options via "GETINFO config/defaults".
22262 Implements ticket 4971.
22264 o Minor features (IPv6):
22265 - New config option "AuthDirHasIPv6Connectivity 1" that directory
22266 authorities should set if they have IPv6 connectivity and want to
22267 do reachability tests for IPv6 relays. Implements feature 5974.
22268 - A relay with an IPv6 OR port now sends that address in NETINFO
22269 cells (in addition to its other address). Implements ticket 6364.
22271 o Minor features (log messages):
22272 - Omit the first heartbeat log message, because it never has anything
22273 useful to say, and it clutters up the bootstrapping messages.
22274 Resolves ticket 6758.
22275 - Don't log about reloading the microdescriptor cache at startup. Our
22276 bootstrap warnings are supposed to tell the user when there's a
22277 problem, and our bootstrap notices say when there isn't. Resolves
22278 ticket 6759; bugfix on 0.2.2.6-alpha.
22279 - Don't log "I learned some more directory information" when we're
22280 reading cached directory information. Reserve it for when new
22281 directory information arrives in response to a fetch. Resolves
22283 - Prevent rounding error in path bias counts when scaling
22284 them down, and use the correct scale factor default. Also demote
22285 some path bias related log messages down a level and make others
22286 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
22287 - We no longer warn so much when generating manpages from their
22290 o Code simplifications and refactoring:
22291 - Enhance our internal sscanf replacement so that we can eliminate
22292 the last remaining uses of the system sscanf. (Though those uses
22293 of sscanf were safe, sscanf itself is generally error prone, so
22294 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
22296 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
22297 - Move last_reachable and testing_since from routerinfo_t to node_t.
22298 Implements ticket 5529.
22299 - Add replaycache_t structure, functions and unit tests, then refactor
22300 rend_service_introduce() to be more clear to read, improve, debug,
22301 and test. Resolves bug 6177.
22302 - Finally remove support for malloc_good_size and malloc_usable_size.
22303 We had hoped that these functions would let us eke a little more
22304 memory out of our malloc implementation. Unfortunately, the only
22305 implementations that provided these functions are also ones that
22306 are already efficient about not overallocation: they never got us
22307 more than 7 or so bytes per allocation. Removing them saves us a
22308 little code complexity and a nontrivial amount of build complexity.
22310 o New requirements:
22311 - Tor maintainers now require Automake version 1.9 or later to build
22312 Tor from the Git repository. (Automake is not required when building
22313 from a source distribution.)
22316 Changes in version 0.2.3.21-rc - 2012-09-05
22317 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
22318 series. It fixes a trio of potential security bugs, fixes a bug where
22319 we were leaving some of the fast relays out of the microdescriptor
22320 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
22321 and cleans up other smaller issues.
22323 o Major bugfixes (security):
22324 - Tear down the circuit if we get an unexpected SENDME cell. Clients
22325 could use this trick to make their circuits receive cells faster
22326 than our flow control would have allowed, or to gum up the network,
22327 or possibly to do targeted memory denial-of-service attacks on
22328 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
22329 from July 2002, before the release of Tor 0.0.0. We had committed
22330 this patch previously, but we had to revert it because of bug 6271.
22331 Now that 6271 is fixed, this patch appears to work.
22332 - Reject any attempt to extend to an internal address. Without
22333 this fix, a router could be used to probe addresses on an internal
22334 network to see whether they were accepting connections. Fixes bug
22335 6710; bugfix on 0.0.8pre1.
22336 - Do not crash when comparing an address with port value 0 to an
22337 address policy. This bug could have been used to cause a remote
22338 assertion failure by or against directory authorities, or to
22339 allow some applications to crash clients. Fixes bug 6690; bugfix
22343 - Remove the upper bound on microdescriptor length. We were hitting
22344 the limit for routers with complex exit policies or family
22345 declarations, causing clients to not use them. Fixes the first
22346 piece of bug 6404; fix on 0.2.2.6-alpha.
22347 - Detect "ORPort 0" as meaning, uniformly, that we're not running
22348 as a relay. Previously, some of our code would treat the presence
22349 of any ORPort line as meaning that we should act like a relay,
22350 even though our new listener code would correctly not open any
22351 ORPorts for ORPort 0. Similar bugs in other Port options are also
22352 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
22355 - Avoid a pair of double-free and use-after-mark bugs that can
22356 occur with certain timings in canceled and re-received DNS
22357 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
22358 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
22359 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
22360 - Allow one-hop directory fetching circuits the full "circuit build
22361 timeout" period, rather than just half of it, before failing them
22362 and marking the relay down. This fix should help reduce cases where
22363 clients declare relays (or worse, bridges) unreachable because
22364 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
22365 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
22367 - Authorities no longer include any router in their microdescriptor
22368 consensuses for which they couldn't generate or agree on a
22369 microdescriptor. Fixes the second piece of bug 6404; fix on
22371 - Detect and reject attempts to specify both "FooPort" and
22372 "FooPort 0" in the same configuration domain. (It's still okay
22373 to have a FooPort in your configuration file, and use "FooPort 0"
22374 on the command line to disable it.) Fixes the second half of bug
22375 6507; bugfix on 0.2.3.3-alpha.
22376 - Make wildcarded addresses (that is, ones beginning with "*.") work
22377 when provided via the controller's MapAddress command. Previously,
22378 they were accepted, but we never actually noticed that they were
22379 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
22380 - Avoid crashing on a malformed state file where EntryGuardPathBias
22381 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
22382 - Add a (probably redundant) memory clear between iterations of
22383 the router status voting loop, to prevent future coding errors
22384 where data might leak between iterations of the loop. Resolves
22387 o Minor bugfixes (log messages):
22388 - Downgrade "set buildtimeout to low value" messages to "info"
22389 severity; they were never an actual problem, there was never
22390 anything reasonable to do about them, and they tended to spam logs
22391 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
22392 - Downgrade path-bias warning messages to "info". We'll try to get
22393 them working better in 0.2.4. Add internal circuit construction
22394 state to protect against the noisy warn message "Unexpectedly high
22395 circuit_successes". Also add some additional rate-limited notice
22396 messages to help determine the root cause of the warn. Fixes bug
22397 6475. Bugfix against 0.2.3.17-beta.
22398 - Move log message when unable to find a microdesc in a routerstatus
22399 entry to parse time. Previously we'd spam this warning every time
22400 we tried to figure out which microdescriptors to download. Fixes
22401 the third piece of bug 6404; fix on 0.2.3.18-rc.
22404 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
22405 change when the authority is deciding whether to accept a newly
22406 uploaded descriptor. Implements ticket 6423.
22407 - Add missing documentation for consensus and microdesc files.
22408 Resolves ticket 6732.
22411 Changes in version 0.2.2.38 - 2012-08-12
22412 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
22413 attack that could in theory leak path information.
22416 - Avoid an uninitialized memory read when reading a vote or consensus
22417 document that has an unrecognized flavor name. This read could
22418 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
22419 - Try to leak less information about what relays a client is
22420 choosing to a side-channel attacker. Previously, a Tor client would
22421 stop iterating through the list of available relays as soon as it
22422 had chosen one, thus finishing a little earlier when it picked
22423 a router earlier in the list. If an attacker can recover this
22424 timing information (nontrivial but not proven to be impossible),
22425 they could learn some coarse-grained information about which relays
22426 a client was picking (middle nodes in particular are likelier to
22427 be affected than exits). The timing attack might be mitigated by
22428 other factors (see bug 6537 for some discussion), but it's best
22429 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
22432 Changes in version 0.2.3.20-rc - 2012-08-05
22433 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
22434 series. It fixes a pair of code security bugs and a potential anonymity
22435 issue, updates our RPM spec files, and cleans up other smaller issues.
22438 - Avoid read-from-freed-memory and double-free bugs that could occur
22439 when a DNS request fails while launching it. Fixes bug 6480;
22440 bugfix on 0.2.0.1-alpha.
22441 - Avoid an uninitialized memory read when reading a vote or consensus
22442 document that has an unrecognized flavor name. This read could
22443 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
22444 - Try to leak less information about what relays a client is
22445 choosing to a side-channel attacker. Previously, a Tor client would
22446 stop iterating through the list of available relays as soon as it
22447 had chosen one, thus finishing a little earlier when it picked
22448 a router earlier in the list. If an attacker can recover this
22449 timing information (nontrivial but not proven to be impossible),
22450 they could learn some coarse-grained information about which relays
22451 a client was picking (middle nodes in particular are likelier to
22452 be affected than exits). The timing attack might be mitigated by
22453 other factors (see bug 6537 for some discussion), but it's best
22454 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
22457 - Try to make the warning when giving an obsolete SOCKSListenAddress
22458 a little more useful.
22459 - Terminate active server managed proxies if Tor stops being a
22460 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
22461 - Provide a better error message about possible OSX Asciidoc failure
22462 reasons. Fixes bug 6436.
22463 - Warn when Tor is configured to use accounting in a way that can
22464 link a hidden service to some other hidden service or public
22465 address. Resolves ticket 6490.
22468 - Check return value of fputs() when writing authority certificate
22469 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
22470 - Ignore ServerTransportPlugin lines when Tor is not configured as
22471 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
22472 - When disabling guards for having too high a proportion of failed
22473 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
22477 - Update our default RPM spec files to work with mock and rpmbuild
22478 on RHEL/Fedora. They have an updated set of dependencies and
22479 conflicts, a fix for an ancient typo when creating the "_tor"
22480 user, and better instructions. Thanks to Ondrej Mikle for the
22481 patch series. Fixes bug 6043.
22484 - Make it possible to set the TestingTorNetwork configuration
22485 option using AlternateDirAuthority and AlternateBridgeAuthority
22486 as an alternative to setting DirServer. Addresses ticket 6377.
22489 - Clarify the documentation for the Alternate*Authority options.
22491 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
22493 o Code simplification and refactoring:
22494 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
22495 10 lines. Also, don't nest them. Doing so in the past has
22496 led to hard-to-debug code. The new style is to use the
22497 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
22500 Changes in version 0.2.3.19-rc - 2012-07-06
22501 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
22502 series. It fixes the compile on Windows, reverts to a GeoIP database
22503 that isn't as broken, and fixes a flow control bug that has been around
22504 since the beginning of Tor.
22507 - Fix a bug handling SENDME cells on nonexistent streams that could
22508 result in bizarre window values. Report and patch contributed
22509 pseudonymously. Fixes part of bug 6271. This bug was introduced
22510 before the first Tor release, in svn commit r152.
22511 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
22512 June 2012 database, Maxmind marked many Tor relays as country "A1",
22513 which will cause risky behavior for clients that set EntryNodes
22514 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
22515 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
22516 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
22519 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
22520 bugfix on 0.2.1.10-alpha.
22523 Changes in version 0.2.3.18-rc - 2012-06-28
22524 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
22525 series. It fixes a few smaller bugs, but generally appears stable.
22526 Please test it and let us know whether it is!
22529 - Allow wildcarded mapaddress targets to be specified on the
22530 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
22531 - Make our linker option detection code more robust against linkers
22532 such as on FreeBSD 8, where a bad combination of options completes
22533 successfully but makes an unrunnable binary. Fixes bug 6173;
22534 bugfix on 0.2.3.17-beta.
22536 o Minor bugfixes (on 0.2.2.x and earlier):
22537 - Avoid a false positive in the util/threads unit test by increasing
22538 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
22539 - Replace "Sending publish request" log messages with "Launching
22540 upload", so that they no longer confusingly imply that we're
22541 sending something to a directory we might not even be connected
22542 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
22543 - Make sure to set *socket_error in all error cases in
22544 connection_connect(), so it can't produce a warning about
22545 errno being zero from errno_to_orconn_end_reason(). Bugfix on
22546 0.2.1.1-alpha; resolves ticket 6028.
22547 - Downgrade "Got a certificate, but we already have it" log messages
22548 from warning to info, except when we're a dirauth. Fixes bug 5238;
22549 bugfix on 0.2.1.7-alpha.
22550 - When checking for requested signatures on the latest consensus
22551 before serving it to a client, make sure to check the right
22552 consensus flavor. Bugfix on 0.2.2.6-alpha.
22553 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
22554 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
22556 o Minor bugfixes (on 0.2.3.x):
22557 - Make format_helper_exit_status() avoid unnecessary space padding
22558 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
22560 - Downgrade a message about cleaning the microdescriptor cache to
22561 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
22562 - Log a BUG message at severity INFO if we have a networkstatus with
22563 a missing entry for some microdescriptor. Continues on a patch
22565 - Improve the log message when a managed proxy fails to launch. Fixes
22566 bug 5099; bugfix on 0.2.3.6-alpha.
22567 - Don't do DNS lookups when parsing corrupted managed proxy protocol
22568 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
22569 - When formatting wildcarded address mappings for the controller,
22570 be sure to include "*." as appropriate. Partially fixes bug 6244;
22571 bugfix on 0.2.3.9-alpha.
22572 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
22573 Bugfix on 0.2.3.13-alpha.
22574 - Stop logging messages about running with circuit timeout learning
22575 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
22576 - Disable a spurious warning about reading on a marked and flushing
22577 connection. We shouldn't be doing that, but apparently we
22578 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
22579 - Fix a bug that stopped AllowDotExit from working on addresses
22580 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
22583 o Code simplification, refactoring, unit tests:
22584 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
22585 Libevent's notion of cached time when possible.
22586 - Remove duplicate code for invoking getrlimit() from control.c.
22587 - Add a unit test for the environment_variable_names_equal function.
22590 - Document the --defaults-torrc option, and the new (in 0.2.3)
22591 semantics for overriding, extending, and clearing lists of
22592 options. Closes bug 4748.
22595 Changes in version 0.2.3.17-beta - 2012-06-15
22596 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
22597 gets our TLS handshake back on track for being able to blend in with
22598 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
22599 with Vidalia, and otherwise continues to get us closer to a release
22603 - Enable gcc and ld hardening by default. Resolves ticket 5210.
22604 - Update TLS cipher list to match Firefox 8 and later. Resolves
22606 - Implement the client side of proposal 198: remove support for
22607 clients falsely claiming to support standard ciphersuites that
22608 they can actually provide. As of modern OpenSSL versions, it's not
22609 necessary to fake any standard ciphersuite, and doing so prevents
22610 us from using better ciphersuites in the future, since servers
22611 can't know whether an advertised ciphersuite is really supported or
22612 not. Some hosts -- notably, ones with very old versions of OpenSSL
22613 or where OpenSSL has been built with ECC disabled -- will stand
22614 out because of this change; TBB users should not be affected.
22617 - Change the default value for DynamicDHGroups (introduced in
22618 0.2.3.9-alpha) to 0. This feature can make Tor relays less
22619 identifiable by their use of the mod_ssl DH group, but at
22620 the cost of some usability (#4721) and bridge tracing (#6087)
22621 regressions. Resolves ticket 5598.
22622 - Send a CRLF at the end of each STATUS_* control protocol event. This
22623 bug tickled a bug in Vidalia which would make it freeze. Fixes
22624 bug 6094; bugfix on 0.2.3.16-alpha.
22627 - Disable writing on marked-for-close connections when they are
22628 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
22629 bug 5263; bugfix on 0.0.2pre13, where we first added a special
22630 case for flushing marked connections.
22631 - Detect SSL handshake even when the initial attempt to write the
22632 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
22633 - Change the AllowDotExit rules so they should actually work.
22634 We now enforce AllowDotExit only immediately after receiving an
22635 address via SOCKS or DNSPort: other sources are free to provide
22636 .exit addresses after the resolution occurs. Fixes bug 3940;
22637 bugfix on 0.2.2.1-alpha.
22638 - Fix a (harmless) integer overflow in cell statistics reported by
22639 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
22640 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
22641 right places and never depends on the consensus parameters or
22642 computes adaptive timeouts when it is disabled. Fixes bug 5049;
22643 bugfix on 0.2.2.14-alpha.
22644 - When building Tor on Windows with -DUNICODE (not default), ensure
22645 that error messages, filenames, and DNS server names are always
22646 NUL-terminated when we convert them to a single-byte encoding.
22647 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
22648 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
22649 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
22650 - Fix an edge case where TestingTorNetwork is set but the authorities
22651 and relays all have an uptime of zero, where the private Tor network
22652 could briefly lack support for hidden services. Fixes bug 3886;
22653 bugfix on 0.2.2.18-alpha.
22654 - Correct the manpage's descriptions for the default values of
22655 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
22657 - Fix the documentation for the --hush and --quiet command line
22658 options, which changed their behavior back in 0.2.3.3-alpha.
22659 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
22663 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
22664 more information to it, so that we can track it down in case it
22665 returns again. Mitigates bug 5235.
22666 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
22667 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
22668 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
22669 - Warn the user when HTTPProxy, but no other proxy type, is
22670 configured. This can cause surprising behavior: it doesn't send
22671 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
22672 directory traffic only. Resolves ticket 4663.
22673 - Issue a notice if a guard completes less than 40% of your circuits.
22674 Threshold is configurable by torrc option PathBiasNoticeRate and
22675 consensus parameter pb_noticepct. There is additional, off-by-
22676 default code to disable guards which fail too many circuits.
22677 Addresses ticket 5458.
22678 - Update to the June 6 2012 Maxmind GeoLite Country database.
22680 o Code simplifications and refactoring:
22681 - Remove validate_pluggable_transports_config(): its warning
22682 message is now handled by connection_or_connect().
22685 Changes in version 0.2.2.37 - 2012-06-06
22686 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
22687 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
22691 - Work around a bug in OpenSSL that broke renegotiation with TLS
22692 1.1 and TLS 1.2. Without this workaround, all attempts to speak
22693 the v2 Tor connection protocol when both sides were using OpenSSL
22694 1.0.1 would fail. Resolves ticket 6033.
22695 - When waiting for a client to renegotiate, don't allow it to add
22696 any bytes to the input buffer. This fixes a potential DoS issue.
22697 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
22698 - Fix an edge case where if we fetch or publish a hidden service
22699 descriptor, we might build a 4-hop circuit and then use that circuit
22700 for exiting afterwards -- even if the new last hop doesn't obey our
22701 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
22704 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
22705 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
22708 - Tell GCC and Clang to check for any errors in format strings passed
22709 to the tor_v*(print|scan)f functions.
22712 Changes in version 0.2.3.16-alpha - 2012-06-05
22713 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
22714 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
22715 currently). It also fixes a variety of smaller bugs and other cleanups
22716 that get us closer to a release candidate.
22718 o Major bugfixes (general):
22719 - Work around a bug in OpenSSL that broke renegotiation with TLS
22720 1.1 and TLS 1.2. Without this workaround, all attempts to speak
22721 the v2 Tor connection protocol when both sides were using OpenSSL
22722 1.0.1 would fail. Resolves ticket 6033.
22723 - When waiting for a client to renegotiate, don't allow it to add
22724 any bytes to the input buffer. This fixes a potential DoS issue.
22725 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
22726 - Pass correct OR address to managed proxies (like obfsproxy),
22727 even when ORListenAddress is used. Fixes bug 4865; bugfix on
22729 - The advertised platform of a router now includes only its operating
22730 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
22731 service pack level (for Windows) or its CPU architecture (for Unix).
22732 We also no longer include the "git-XYZ" tag in the version. Resolves
22735 o Major bugfixes (clients):
22736 - If we are unable to find any exit that supports our predicted ports,
22737 stop calling them predicted, so that we don't loop and build
22738 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
22739 which introduced predicted ports.
22740 - Fix an edge case where if we fetch or publish a hidden service
22741 descriptor, we might build a 4-hop circuit and then use that circuit
22742 for exiting afterwards -- even if the new last hop doesn't obey our
22743 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
22744 - Check at each new consensus whether our entry guards were picked
22745 long enough ago that we should rotate them. Previously, we only
22746 did this check at startup, which could lead to us holding a guard
22747 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
22748 - When fetching a bridge descriptor from a bridge authority,
22749 always do so anonymously, whether we have been able to open
22750 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
22751 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
22752 but we'll need to wait for bug 6010 before it's actually usable.
22754 o Major bugfixes (directory authorities):
22755 - When computing weight parameters, behave more robustly in the
22756 presence of a bad bwweightscale value. Previously, the authorities
22757 would crash if they agreed on a sufficiently broken weight_scale
22758 value: now, they use a reasonable default and carry on. Partial
22759 fix for 5786; bugfix on 0.2.2.17-alpha.
22760 - Check more thoroughly to prevent a rogue authority from
22761 double-voting on any consensus directory parameter. Previously,
22762 authorities would crash in this case if the total number of
22763 votes for any parameter exceeded the number of active voters,
22764 but would let it pass otherwise. Partial fix for bug 5786; bugfix
22768 - Rate-limit log messages when asked to connect anonymously to
22769 a private address. When these hit, they tended to hit fast and
22770 often. Also, don't bother trying to connect to addresses that we
22771 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
22772 reply makes us think we have been lied to, even when the address the
22773 client tried to connect to was "localhost." Resolves ticket 2822.
22774 - Allow packagers to insert an extra string in server descriptor
22775 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
22776 Resolves the rest of ticket 2988.
22777 - Raise the threshold of server descriptors needed (75%) and exit
22778 server descriptors needed (50%) before we will declare ourselves
22779 bootstrapped. This will make clients start building circuits a
22780 little later, but makes the initially constructed circuits less
22781 skewed and less in conflict with further directory fetches. Fixes
22783 - Close any connection that sends unrecognized junk before the
22784 handshake. Solves an issue noted in bug 4369.
22785 - Improve log messages about managed transports. Resolves ticket 5070.
22786 - Tag a bridge's descriptor as "never to be sent unencrypted".
22787 This shouldn't matter, since bridges don't open non-anonymous
22788 connections to the bridge authority and don't allow unencrypted
22789 directory connections from clients, but we might as well make
22790 sure. Closes bug 5139.
22791 - Expose our view of whether we have gone dormant to the controller,
22792 via a new "GETINFO dormant" value. Torbutton and other controllers
22793 can use this to avoid doing periodic requests through Tor while
22794 it's dormant (bug 4718). Fixes bug 5954.
22795 - Tell GCC and Clang to check for any errors in format strings passed
22796 to the tor_v*(print|scan)f functions.
22797 - Update to the May 1 2012 Maxmind GeoLite Country database.
22799 o Minor bugfixes (already included in 0.2.2.36):
22800 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
22801 Fixes bug 5346; bugfix on 0.0.8pre3.
22802 - Correct parsing of certain date types in parse_http_time().
22803 Without this patch, If-Modified-Since would behave
22804 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
22805 Esteban Manchado Velázques.
22806 - Make our number-parsing functions always treat too-large values
22807 as an error, even when those values exceed the width of the
22808 underlying type. Previously, if the caller provided these
22809 functions with minima or maxima set to the extreme values of the
22810 underlying integer type, these functions would return those
22811 values on overflow rather than treating overflow as an error.
22812 Fixes part of bug 5786; bugfix on 0.0.9.
22813 - If we hit the error case where routerlist_insert() replaces an
22814 existing (old) server descriptor, make sure to remove that
22815 server descriptor from the old_routers list. Fix related to bug
22816 1776. Bugfix on 0.2.2.18-alpha.
22817 - Clarify the behavior of MaxCircuitDirtiness with hidden service
22818 circuits. Fixes issue 5259.
22820 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
22821 - Prevent a null-pointer dereference when receiving a data cell
22822 for a nonexistent stream when the circuit in question has an
22823 empty deliver window. We don't believe this is triggerable,
22824 since we don't currently allow deliver windows to become empty,
22825 but the logic is tricky enough that it's better to make the code
22826 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
22827 - Fix a memory leak when trying to launch a DNS request when the
22828 network is disabled or the nameservers are unconfigurable. Fixes
22829 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
22830 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
22831 - Don't hold a Windows file handle open for every file mapping;
22832 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
22834 - Avoid O(n^2) performance characteristics when parsing a large
22835 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
22836 - Format more doubles with %f, not %lf. Patch from grarpamp to make
22837 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
22839 - Make our replacement implementation of strtok_r() compatible with
22840 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
22841 bugfix on 0.2.2.1-alpha.
22842 - Fix a NULL-pointer dereference on a badly formed
22843 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
22844 bugfix on 0.2.2.9-alpha.
22845 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
22846 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
22847 - Defensively refactor rend_mid_rendezvous() so that protocol
22848 violations and length checks happen in the beginning. Fixes
22850 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
22851 that IPv6 stuff will compile on MSVC, and compilation issues
22852 will be easier to track down. Fixes bug 5861.
22854 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
22855 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
22856 resource exhaustion, so that clients can adjust their load to
22857 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
22858 started using END_STREAM_REASON_RESOURCELIMIT.
22859 - Don't check for whether the address we're using for outbound
22860 connections has changed until after the outbound connection has
22861 completed. On Windows, getsockname() doesn't succeed until the
22862 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
22863 - If the configuration tries to set MyFamily on a bridge, refuse to
22864 do so, and warn about the security implications. Fixes bug 4657;
22865 bugfix on 0.2.0.3-alpha.
22866 - If the client fails to set a reasonable set of ciphersuites
22867 during its v2 handshake renegotiation, allow the renegotiation to
22868 continue nevertheless (i.e. send all the required certificates).
22869 Fixes bug 4591; bugfix on 0.2.0.20-rc.
22870 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
22871 option is set to 0 (which Vidalia version 0.2.16 now does when
22872 a SAVECONF attempt fails), perform other actions that SIGHUP
22873 usually causes (like reopening the logs). Fixes bug 5095; bugfix
22875 - If we fail to write a microdescriptor to the disk cache, do not
22876 continue replacing the old microdescriptor file. Fixes bug 2954;
22877 bugfix on 0.2.2.6-alpha.
22878 - Exit nodes don't need to fetch certificates for authorities that
22879 they don't recognize; only directory authorities, bridges,
22880 and caches need to do that. Fixes part of bug 2297; bugfix on
22882 - Correctly handle checking the permissions on the parent
22883 directory of a control socket in the root directory. Bug found
22884 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
22886 - When told to add a bridge with the same digest as a preexisting
22887 bridge but a different addr:port, change the addr:port as
22888 requested. Previously we would not notice the change. Fixes half
22889 of bug 5603; fix on 0.2.2.26-beta.
22890 - End AUTHCHALLENGE error messages (in the control protocol) with
22891 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
22893 o Minor bugfixes (on 0.2.3.x):
22894 - Turn an assertion (that the number of handshakes received as a
22895 server is not < 1) into a warning. Fixes bug 4873; bugfix on
22897 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
22898 we had reversed them when the answer was cached.) Fixes bug
22899 5723; bugfix on 0.2.3.1-alpha.
22900 - Work correctly on Linux systems with accept4 support advertised in
22901 their headers, but without accept4 support in the kernel. Fix
22902 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
22903 - When told to add a bridge with the same addr:port as a preexisting
22904 bridge but a different transport, change the transport as
22905 requested. Previously we would not notice the change. Fixes half
22906 of bug 5603; fix on 0.2.3.2-alpha.
22907 - Avoid a "double-reply" warning when replying to a SOCKS request
22908 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
22909 bugfix on 0.2.3.4-alpha.
22910 - Fix a bug where a bridge authority crashes if it has seen no
22911 directory requests when it's time to write statistics to disk.
22912 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
22914 - Don't try to open non-control listeners when DisableNetwork is set.
22915 Previously, we'd open all listeners, then immediately close them.
22916 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
22917 - Don't abort the managed proxy protocol if the managed proxy
22918 sends us an unrecognized line; ignore it instead. Fixes bug
22919 5910; bugfix on 0.2.3.9-alpha.
22920 - Fix a compile warning in crypto.c when compiling with clang 3.1.
22921 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
22922 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
22923 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
22924 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
22925 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
22926 - Resolve numerous small warnings and build issues with MSVC. Resolves
22929 o Documentation fixes:
22930 - Improve the manual's documentation for the NT Service command-line
22931 options. Addresses ticket 3964.
22932 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
22933 - Document the changes to the ORPort and DirPort options, and the
22934 fact that {OR/Dir}ListenAddress is now unnecessary (and
22935 therefore deprecated). Resolves ticket 5597.
22938 - Remove the torrc.bridge file: we don't use it for anything, and
22939 it had become badly desynchronized from torrc.sample. Resolves
22943 Changes in version 0.2.2.36 - 2012-05-24
22944 Tor 0.2.2.36 updates the addresses for two of the eight directory
22945 authorities, fixes some potential anonymity and security issues,
22946 and fixes several crash bugs.
22948 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
22949 known flaws, and nobody should be using them. You should upgrade. If
22950 you're using a Linux or BSD and its packages are obsolete, stop using
22951 those packages and upgrade anyway.
22953 o Directory authority changes:
22954 - Change IP address for maatuska (v3 directory authority).
22955 - Change IP address for ides (v3 directory authority), and rename
22959 - When building or running with any version of OpenSSL earlier
22960 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
22961 versions have a bug (CVE-2011-4576) in which their block cipher
22962 padding includes uninitialized data, potentially leaking sensitive
22963 information to any peer with whom they make a SSLv3 connection. Tor
22964 does not use SSL v3 by default, but a hostile client or server
22965 could force an SSLv3 connection in order to gain information that
22966 they shouldn't have been able to get. The best solution here is to
22967 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
22968 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
22969 to make sure that the bug can't happen.
22970 - Never use a bridge or a controller-supplied node as an exit, even
22971 if its exit policy allows it. Found by wanoskarnet. Fixes bug
22972 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
22973 and 0.2.0.3-alpha (for bridge-purpose descriptors).
22974 - Only build circuits if we have a sufficient threshold of the total
22975 descriptors that are marked in the consensus with the "Exit"
22976 flag. This mitigates an attack proposed by wanoskarnet, in which
22977 all of a client's bridges collude to restrict the exit nodes that
22978 the client knows about. Fixes bug 5343.
22979 - Provide controllers with a safer way to implement the cookie
22980 authentication mechanism. With the old method, if another locally
22981 running program could convince a controller that it was the Tor
22982 process, then that program could trick the controller into telling
22983 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
22984 authentication method uses a challenge-response approach to prevent
22985 this attack. Fixes bug 5185; implements proposal 193.
22988 - Avoid logging uninitialized data when unable to decode a hidden
22989 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
22990 - Avoid a client-side assertion failure when receiving an INTRODUCE2
22991 cell on a general purpose circuit. Fixes bug 5644; bugfix on
22993 - Fix builds when the path to sed, openssl, or sha1sum contains
22994 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
22996 - Correct our replacements for the timeradd() and timersub() functions
22997 on platforms that lack them (for example, Windows). The timersub()
22998 function is used when expiring circuits, while timeradd() is
22999 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
23000 bugfix on 0.2.2.24-alpha.
23001 - Fix the SOCKET_OK test that we use to tell when socket
23002 creation fails so that it works on Win64. Fixes part of bug 4533;
23003 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
23006 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
23007 Fixes bug 5346; bugfix on 0.0.8pre3.
23008 - Make our number-parsing functions always treat too-large values
23009 as an error, even when those values exceed the width of the
23010 underlying type. Previously, if the caller provided these
23011 functions with minima or maxima set to the extreme values of the
23012 underlying integer type, these functions would return those
23013 values on overflow rather than treating overflow as an error.
23014 Fixes part of bug 5786; bugfix on 0.0.9.
23015 - Older Linux kernels erroneously respond to strange nmap behavior
23016 by having accept() return successfully with a zero-length
23017 socket. When this happens, just close the connection. Previously,
23018 we would try harder to learn the remote address: but there was
23019 no such remote address to learn, and our method for trying to
23020 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
23021 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
23022 - Correct parsing of certain date types in parse_http_time().
23023 Without this patch, If-Modified-Since would behave
23024 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
23025 Esteban Manchado Velázques.
23026 - Change the BridgePassword feature (part of the "bridge community"
23027 design, which is not yet implemented) to use a time-independent
23028 comparison. The old behavior might have allowed an adversary
23029 to use timing to guess the BridgePassword value. Fixes bug 5543;
23030 bugfix on 0.2.0.14-alpha.
23031 - Detect and reject certain misformed escape sequences in
23032 configuration values. Previously, these values would cause us
23033 to crash if received in a torrc file or over an authenticated
23034 control port. Bug found by Esteban Manchado Velázquez, and
23035 independently by Robert Connolly from Matta Consulting who further
23036 noted that it allows a post-authentication heap overflow. Patch
23037 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
23038 bugfix on 0.2.0.16-alpha.
23039 - Fix a compile warning when using the --enable-openbsd-malloc
23040 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
23041 - During configure, detect when we're building with clang version
23042 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
23043 CFLAGS. clang doesn't support them yet.
23044 - When sending an HTTP/1.1 proxy request, include a Host header.
23045 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
23046 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
23047 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
23048 - If we hit the error case where routerlist_insert() replaces an
23049 existing (old) server descriptor, make sure to remove that
23050 server descriptor from the old_routers list. Fix related to bug
23051 1776. Bugfix on 0.2.2.18-alpha.
23053 o Minor bugfixes (documentation and log messages):
23054 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
23055 Fixes bug 4856; bugfix on Tor 0.0.6.
23056 - Update "ClientOnly" man page entry to explain that there isn't
23057 really any point to messing with it. Resolves ticket 5005.
23058 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
23059 directory authority option (introduced in Tor 0.2.2.34).
23060 - Downgrade the "We're missing a certificate" message from notice
23061 to info: people kept mistaking it for a real problem, whereas it
23062 is seldom the problem even when we are failing to bootstrap. Fixes
23063 bug 5067; bugfix on 0.2.0.10-alpha.
23064 - Correctly spell "connect" in a log message on failure to create a
23065 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
23066 - Clarify the behavior of MaxCircuitDirtiness with hidden service
23067 circuits. Fixes issue 5259.
23070 - Directory authorities now reject versions of Tor older than
23071 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
23072 inclusive. These versions accounted for only a small fraction of
23073 the Tor network, and have numerous known security issues. Resolves
23075 - Update to the May 1 2012 Maxmind GeoLite Country database.
23078 - When sending or relaying a RELAY_EARLY cell, we used to convert
23079 it to a RELAY cell if the connection was using the v1 link
23080 protocol. This was a workaround for older versions of Tor, which
23081 didn't handle RELAY_EARLY cells properly. Now that all supported
23082 versions can handle RELAY_EARLY cells, and now that we're enforcing
23083 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
23084 remove this workaround. Addresses bug 4786.
23087 Changes in version 0.2.3.15-alpha - 2012-04-30
23088 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
23089 the development branch build on Windows again.
23091 o Minor bugfixes (on 0.2.2.x and earlier):
23092 - Make sure that there are no unhandled pending TLS errors before
23093 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
23094 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
23095 Bugfix on 0.1.0.5-rc; fixes bug 4528.
23096 - Fix an assert that directory authorities could trigger on sighup
23097 during some configuration state transitions. We now don't treat
23098 it as a fatal error when the new descriptor we just generated in
23099 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
23100 - After we pick a directory mirror, we would refuse to use it if
23101 it's in our ExcludeExitNodes list, resulting in mysterious failures
23102 to bootstrap for people who just wanted to avoid exiting from
23103 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
23104 - When building with --enable-static-tor on OpenBSD, do not
23105 erroneously attempt to link -lrt. Fixes bug 5103.
23107 o Minor bugfixes (on 0.2.3.x):
23108 - When Tor is built with kernel headers from a recent (last few
23109 years) Linux kernel, do not fail to run on older (pre-2.6.28
23110 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
23111 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
23112 and 0.2.3.12-alpha.
23113 - Fix compilation with miniupnpc version 1.6; patch from
23114 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
23115 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
23116 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
23117 - Fix compilation on platforms without unistd.h, or where environ
23118 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
23121 - Directory authorities are now a little more lenient at accepting
23122 older router descriptors, or newer router descriptors that don't
23123 make big changes. This should help ameliorate past and future
23124 issues where routers think they have uploaded valid descriptors,
23125 but the authorities don't think so. Fix for ticket 2479.
23126 - Make the code that clients use to detect an address change be
23127 IPv6-aware, so that it won't fill clients' logs with error
23128 messages when trying to get the IPv4 address of an IPv6
23129 connection. Implements ticket 5537.
23131 o Removed features:
23132 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
23133 authorities needed to use it for a while to keep the network working
23134 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
23135 that was six months ago. As of now, it should no longer be needed
23139 Changes in version 0.2.3.14-alpha - 2012-04-23
23140 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
23141 candidate. It also dramatically speeds up AES: fast relays should
23142 consider switching to the newer OpenSSL library.
23144 o Directory authority changes:
23145 - Change IP address for ides (v3 directory authority), and rename
23149 - Avoid logging uninitialized data when unable to decode a hidden
23150 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
23151 - Avoid a client-side assertion failure when receiving an INTRODUCE2
23152 cell on a general purpose circuit. Fixes bug 5644; bugfix on
23154 - If authorities are unable to get a v2 consensus document from other
23155 directory authorities, they no longer fall back to fetching
23156 them from regular directory caches. Fixes bug 5635; bugfix on
23157 0.2.2.26-beta, where routers stopped downloading v2 consensus
23158 documents entirely.
23159 - When we start a Tor client with a normal consensus already cached,
23160 be willing to download a microdescriptor consensus. Fixes bug 4011;
23161 fix on 0.2.3.1-alpha.
23163 o Major features (performance):
23164 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
23165 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
23166 vectorized AES implementations as appropriate. These can be much,
23167 much faster than other AES implementations.
23169 o Minor bugfixes (0.2.2.x and earlier):
23170 - Don't launch more than 10 service-side introduction-point circuits
23171 for a hidden service in five minutes. Previously, we would consider
23172 launching more introduction-point circuits if at least one second
23173 had passed without any introduction-point circuits failing. Fixes
23174 bug 4607; bugfix on 0.0.7pre1.
23175 - Change the BridgePassword feature (part of the "bridge community"
23176 design, which is not yet implemented) to use a time-independent
23177 comparison. The old behavior might have allowed an adversary
23178 to use timing to guess the BridgePassword value. Fixes bug 5543;
23179 bugfix on 0.2.0.14-alpha.
23180 - Enforce correct return behavior of tor_vsscanf() when the '%%'
23181 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
23182 - When sending an HTTP/1.1 proxy request, include a Host header.
23183 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
23184 - Don't log that we have "decided to publish new relay descriptor"
23185 unless we are actually publishing a descriptor. Fixes bug 3942;
23186 bugfix on 0.2.2.28-beta.
23188 o Minor bugfixes (0.2.3.x):
23189 - Fix a bug where a bridge authority crashes (on a failed assert)
23190 if it has seen no directory requests when it's time to write
23191 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
23192 - Fix bug stomping on ORPort option NoListen and ignoring option
23193 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
23194 - In the testsuite, provide a large enough buffer in the tor_sscanf
23195 unit test. Otherwise we'd overrun that buffer and crash during
23196 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
23198 - Make sure we create the keys directory if it doesn't exist and we're
23199 about to store the dynamic Diffie-Hellman parameters. Fixes bug
23200 5572; bugfix on 0.2.3.13-alpha.
23201 - Fix a small memory leak when trying to decode incorrect base16
23202 authenticator during SAFECOOKIE authentication. Found by
23203 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
23206 - Add more information to a log statement that might help track down
23207 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
23208 non-IP address" messages (or any Bug messages, for that matter!),
23209 please let us know about it.
23210 - Relays now understand an IPv6 address when they get one from a
23211 directory server. Resolves ticket 4875.
23212 - Resolve IPv6 addresses in bridge and entry statistics to country
23213 code "??" which means we at least count them. Resolves ticket 5053;
23214 improves on 0.2.3.9-alpha.
23215 - Update to the April 3 2012 Maxmind GeoLite Country database.
23216 - Begin a doc/state-contents.txt file to explain the contents of
23217 the Tor state file. Fixes bug 2987.
23219 o Default torrc changes:
23220 - Stop listing "socksport 9050" in torrc.sample. We open a socks
23221 port on 9050 by default anyway, so this should not change anything
23223 - Stop mentioning the deprecated *ListenAddress options in
23224 torrc.sample. Fixes bug 5438.
23225 - Document unit of bandwidth related options in sample torrc.
23228 o Removed features:
23229 - The "torify" script no longer supports the "tsocks" socksifier
23230 tool, since tsocks doesn't support DNS and UDP right for Tor.
23231 Everyone should be using torsocks instead. Fixes bugs 3530 and
23232 5180. Based on a patch by "ugh".
23234 o Code refactoring:
23235 - Change the symmetric cipher interface so that creating and
23236 initializing a stream cipher are no longer separate functions.
23237 - Remove all internal support for unpadded RSA. We never used it, and
23238 it would be a bad idea to start.
23241 Changes in version 0.2.3.13-alpha - 2012-03-26
23242 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
23243 in managed pluggable transports, as well as providing other cleanups
23244 that get us closer to a release candidate.
23246 o Directory authority changes:
23247 - Change IP address for maatuska (v3 directory authority).
23250 - Provide controllers with a safer way to implement the cookie
23251 authentication mechanism. With the old method, if another locally
23252 running program could convince a controller that it was the Tor
23253 process, then that program could trick the controller into telling
23254 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
23255 authentication method uses a challenge-response approach to prevent
23256 this attack. Fixes bug 5185, implements proposal 193.
23257 - Never use a bridge or a controller-supplied node as an exit, even
23258 if its exit policy allows it. Found by wanoskarnet. Fixes bug
23259 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
23260 and 0.2.0.3-alpha (for bridge-purpose descriptors).
23261 - Only build circuits if we have a sufficient threshold of the total
23262 descriptors that are marked in the consensus with the "Exit"
23263 flag. This mitigates an attack proposed by wanoskarnet, in which
23264 all of a client's bridges collude to restrict the exit nodes that
23265 the client knows about. Fixes bug 5343.
23267 o Major bugfixes (on Tor 0.2.3.x):
23268 - Avoid an assert when managed proxies like obfsproxy are configured,
23269 and we receive HUP signals or setconf attempts too rapidly. This
23270 situation happens most commonly when Vidalia tries to attach to
23271 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
23272 bugfix on 0.2.3.6-alpha.
23273 - Fix a relay-side pluggable transports bug where managed proxies were
23274 unreachable from the Internet, because Tor asked them to bind on
23275 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
23276 - Stop discarding command-line arguments when TestingTorNetwork
23277 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
23278 0.2.3.9-alpha, where task 4552 added support for two layers of
23280 - Resume allowing the unit tests to run in gdb. This was accidentally
23281 made impossible when the DisableDebuggerAttachment option was
23282 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
23283 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
23284 0.2.3.11-alpha. Reported by Anthony G. Basile.
23286 o Minor bugfixes (on 0.2.2.x and earlier):
23287 - Ensure we don't cannibalize circuits that are longer than three hops
23288 already, so we don't end up making circuits with 5 or more
23289 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
23290 0.1.0.1-rc which introduced cannibalization.
23291 - Detect and reject certain misformed escape sequences in
23292 configuration values. Previously, these values would cause us
23293 to crash if received in a torrc file or over an authenticated
23294 control port. Bug found by Esteban Manchado Velázquez, and
23295 independently by Robert Connolly from Matta Consulting who further
23296 noted that it allows a post-authentication heap overflow. Patch
23297 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
23298 bugfix on 0.2.0.16-alpha.
23299 - Fix a compile warning when using the --enable-openbsd-malloc
23300 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
23301 - Directory caches no longer refuse to clean out descriptors because
23302 of missing v2 networkstatus documents, unless they're configured
23303 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
23304 0.2.2.26-beta. Patch by Daniel Bryg.
23305 - Update to the latest version of the tinytest unit testing framework.
23306 This includes a couple of bugfixes that can be relevant for
23307 running forked unit tests on Windows, and removes all reserved
23310 o Minor bugfixes (on 0.2.3.x):
23311 - On a failed pipe() call, don't leak file descriptors. Fixes bug
23312 4296; bugfix on 0.2.3.1-alpha.
23313 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
23314 until after we have received a CERTS cell. Fixes bug 4361; bugfix
23315 on 0.2.3.6-alpha. Patch by "frosty".
23316 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
23317 option, so that the IP stack doesn't decide to use it for IPv4
23318 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
23319 - Ensure that variables set in Tor's environment cannot override
23320 environment variables that Tor passes to a managed
23321 pluggable-transport proxy. Previously, Tor would pass every
23322 variable in its environment to managed proxies along with the new
23323 ones, in such a way that on many operating systems, the inherited
23324 environment variables would override those which Tor tried to
23325 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
23326 bugfix on 0.2.3.9-alpha for Windows.
23329 - A wide variety of new unit tests by Esteban Manchado Velázquez.
23330 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
23331 - Update to the March 6 2012 Maxmind GeoLite Country database.
23334 Changes in version 0.2.3.12-alpha - 2012-02-13
23335 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
23336 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
23337 when Tor is configured to use a pluggable transport like obfsproxy.
23340 - Fix builds when the path to sed, openssl, or sha1sum contains
23341 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
23343 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
23344 connections. This change should allow busy exit relays to stop
23345 running out of available sockets as quickly. Fixes bug 4950;
23346 bugfix on 0.2.2.26-beta.
23347 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
23348 would ask the bridge for microdescriptors, which are only supported
23349 in 0.2.3.x, and then fail to bootstrap when it didn't get the
23350 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
23351 - Properly set up obfsproxy's environment when in managed mode. The
23352 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
23353 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
23354 5076 and 5082; bugfix on 0.2.3.6-alpha.
23357 - Use the dead_strip option when building Tor on OS X. This reduces
23358 binary size by almost 19% when linking openssl and libevent
23359 statically, which we do for Tor Browser Bundle.
23360 - Fix broken URLs in the sample torrc file, and tell readers about
23361 the OutboundBindAddress, ExitPolicyRejectPrivate, and
23362 PublishServerDescriptor options. Addresses bug 4652.
23363 - Update to the February 7 2012 Maxmind GeoLite Country database.
23366 - Downgrade the "We're missing a certificate" message from notice
23367 to info: people kept mistaking it for a real problem, whereas it
23368 is seldom the problem even when we are failing to bootstrap. Fixes
23369 bug 5067; bugfix on 0.2.0.10-alpha.
23370 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
23371 managed pluggable transport server proxy's environment.
23372 Previously, we would put it there, even though Tor doesn't
23373 implement an 'extended server port' yet, and even though Tor
23374 almost certainly isn't listening at that address. For now, we set
23375 it to an empty string to avoid crashing older obfsproxies. Bugfix
23377 - Log the heartbeat message every HeartbeatPeriod seconds, not every
23378 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
23379 0.2.3.1-alpha. Bug reported by Scott Bennett.
23380 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
23381 bugfix on 0.2.3.11-alpha.
23382 - Update "ClientOnly" man page entry to explain that there isn't
23383 really any point to messing with it. Resolves ticket 5005.
23384 - Use the correct CVE number for CVE-2011-4576 in our comments and
23385 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
23388 o Code simplifications and refactoring:
23389 - Use the _WIN32 macro throughout our code to detect Windows.
23390 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
23394 Changes in version 0.2.3.11-alpha - 2012-01-22
23395 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
23396 the last step of the plan to limit maximum circuit length, includes
23397 a wide variety of hidden service performance and correctness fixes,
23398 works around an OpenSSL security flaw if your distro is too stubborn
23399 to upgrade, and fixes a bunch of smaller issues.
23402 - Now that Tor 0.2.0.x is completely deprecated, enable the final
23403 part of "Proposal 110: Avoiding infinite length circuits" by
23404 refusing all circuit-extend requests that do not use a relay_early
23405 cell. This change helps Tor resist a class of denial-of-service
23406 attacks by limiting the maximum circuit length.
23407 - Adjust the number of introduction points that a hidden service
23408 will try to maintain based on how long its introduction points
23409 remain in use and how many introductions they handle. Fixes
23411 - Try to use system facilities for enumerating local interface
23412 addresses, before falling back to our old approach (which was
23413 binding a UDP socket, and calling getsockname() on it). That
23414 approach was scaring OS X users whose draconian firewall
23415 software warned about binding to UDP sockets, regardless of
23416 whether packets were sent. Now we try to use getifaddrs(),
23417 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
23418 system supports. Resolves ticket 1827.
23420 o Major security workaround:
23421 - When building or running with any version of OpenSSL earlier
23422 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
23423 versions have a bug (CVE-2011-4576) in which their block cipher
23424 padding includes uninitialized data, potentially leaking sensitive
23425 information to any peer with whom they make a SSLv3 connection. Tor
23426 does not use SSL v3 by default, but a hostile client or server
23427 could force an SSLv3 connection in order to gain information that
23428 they shouldn't have been able to get. The best solution here is to
23429 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
23430 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
23431 to make sure that the bug can't happen.
23434 - Fix the SOCKET_OK test that we use to tell when socket
23435 creation fails so that it works on Win64. Fixes part of bug 4533;
23436 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
23437 - Correct our replacements for the timeradd() and timersub() functions
23438 on platforms that lack them (for example, Windows). The timersub()
23439 function is used when expiring circuits, while timeradd() is
23440 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
23441 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
23442 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
23443 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
23444 bug at runtime, not compile time, because some distributions hack
23445 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
23446 on 0.2.3.9-alpha. Found by Pascal.
23448 o Minor features (controller):
23449 - Use absolute path names when reporting the torrc filename in the
23450 control protocol, so a controller can more easily find the torrc
23451 file. Resolves bug 1101.
23452 - Extend the control protocol to report flags that control a circuit's
23453 path selection in CIRC events and in replies to 'GETINFO
23454 circuit-status'. Implements part of ticket 2411.
23455 - Extend the control protocol to report the hidden service address
23456 and current state of a hidden-service-related circuit in CIRC
23457 events and in replies to 'GETINFO circuit-status'. Implements part
23459 - When reporting the path to the cookie file to the controller,
23460 give an absolute path. Resolves ticket 4881.
23461 - Allow controllers to request an event notification whenever a
23462 circuit is cannibalized or its purpose is changed. Implements
23463 part of ticket 3457.
23464 - Include the creation time of a circuit in CIRC and CIRC2
23465 control-port events and the list produced by the 'GETINFO
23466 circuit-status' control-port command.
23468 o Minor features (directory authorities):
23469 - Directory authorities now reject versions of Tor older than
23470 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
23471 inclusive. These versions accounted for only a small fraction of
23472 the Tor network, and have numerous known security issues. Resolves
23474 - Authority operators can now vote for all relays in a given
23475 set of countries to be BadDir/BadExit/Invalid/Rejected.
23476 - Provide two consensus parameters (FastFlagMinThreshold and
23477 FastFlagMaxThreshold) to control the range of allowable bandwidths
23478 for the Fast directory flag. These allow authorities to run
23479 experiments on appropriate requirements for being a "Fast" node.
23480 The AuthDirFastGuarantee config value still applies. Implements
23482 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
23483 directory authority option (introduced in Tor 0.2.2.34).
23485 o Minor features (other):
23486 - Don't disable the DirPort when we cannot exceed our AccountingMax
23487 limit during this interval because the effective bandwidthrate is
23488 low enough. This is useful in a situation where AccountMax is only
23489 used as an additional safeguard or to provide statistics.
23490 - Prepend an informative header to generated dynamic_dh_params files.
23491 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
23492 EntryNodes will have no effect. Resolves issue 2571.
23493 - Log more useful messages when we fail to disable debugger
23495 - Log which authority we're missing votes from when we go to fetch
23496 them from the other auths.
23497 - Log (at debug level) whenever a circuit's purpose is changed.
23498 - Add missing documentation for the MaxClientCircuitsPending,
23499 UseMicrodescriptors, UserspaceIOCPBuffers, and
23500 _UseFilteringSSLBufferevents options, all introduced during
23501 the 0.2.3.x series.
23502 - Update to the January 3 2012 Maxmind GeoLite Country database.
23504 o Minor bugfixes (hidden services):
23505 - Don't close hidden service client circuits which have almost
23506 finished connecting to their destination when they reach
23507 the normal circuit-build timeout. Previously, we would close
23508 introduction circuits which are waiting for an acknowledgement
23509 from the introduction point, and rendezvous circuits which have
23510 been specified in an INTRODUCE1 cell sent to a hidden service,
23511 after the normal CBT. Now, we mark them as 'timed out', and launch
23512 another rendezvous attempt in parallel. This behavior change can
23513 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
23514 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
23515 - Don't close hidden-service-side rendezvous circuits when they
23516 reach the normal circuit-build timeout. This behavior change can
23517 be disabled using the new
23518 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
23519 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
23520 - Make sure we never mark the wrong rendezvous circuit as having
23521 had its introduction cell acknowledged by the introduction-point
23522 relay. Previously, when we received an INTRODUCE_ACK cell on a
23523 client-side hidden-service introduction circuit, we might have
23524 marked a rendezvous circuit other than the one we specified in
23525 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
23526 a warning message and interfered with the hidden service
23527 connection-establishment process. Fixes bug 4759; bugfix on
23528 0.2.3.3-alpha, when we added the stream-isolation feature which
23529 might cause Tor to open multiple rendezvous circuits for the same
23531 - Don't trigger an assertion failure when we mark a new client-side
23532 hidden-service introduction circuit for close during the process
23533 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
23536 o Minor bugfixes (log messages):
23537 - Correctly spell "connect" in a log message on failure to create a
23538 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
23540 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
23541 Fixes bug 4856; bugfix on Tor 0.0.6.
23542 - Fix the log message describing how we work around discovering
23543 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
23544 4837; bugfix on 0.2.2.9-alpha.
23545 - When logging about a disallowed .exit name, do not also call it
23546 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
23548 o Minor bugfixes (build fixes):
23549 - During configure, detect when we're building with clang version
23550 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
23551 CFLAGS. clang doesn't support them yet.
23552 - During configure, search for library containing cos function as
23553 libm lives in libcore on some platforms (BeOS/Haiku). Linking
23554 against libm was hard-coded before. Fixes the first part of bug
23555 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
23557 - Detect attempts to build Tor on (as yet hypothetical) versions
23558 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
23559 fix for bug 4533. Bugfix on 0.2.2.28-beta.
23560 - Preprocessor directives should not be put inside the arguments
23561 of a macro. This would break compilation with GCC releases prior
23562 to version 3.3. We would never recommend such an old GCC version,
23563 but it is apparently required for binary compatibility on some
23564 platforms (namely, certain builds of Haiku). Fixes the other part
23565 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
23568 o Minor bugfixes (other):
23569 - Older Linux kernels erroneously respond to strange nmap behavior
23570 by having accept() return successfully with a zero-length
23571 socket. When this happens, just close the connection. Previously,
23572 we would try harder to learn the remote address: but there was
23573 no such remote address to learn, and our method for trying to
23574 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
23575 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
23576 - Fix null-pointer access that could occur if TLS allocation failed.
23577 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
23578 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
23579 accidentally been reverted.
23580 - Fix our implementation of crypto_random_hostname() so it can't
23581 overflow on ridiculously large inputs. (No Tor version has ever
23582 provided this kind of bad inputs, but let's be correct in depth.)
23583 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
23584 - Find more places in the code that should have been testing for
23585 invalid sockets using the SOCKET_OK macro. Required for a fix
23586 for bug 4533. Bugfix on 0.2.2.28-beta.
23587 - Fix an assertion failure when, while running with bufferevents, a
23588 connection finishes connecting after it is marked for close, but
23589 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
23590 - test_util_spawn_background_ok() hardcoded the expected value
23591 for ENOENT to 2. This isn't portable as error numbers are
23592 platform specific, and particularly the hurd has ENOENT at
23593 0x40000002. Construct expected string at runtime, using the correct
23594 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
23595 - Reject attempts to disable DisableDebuggerAttachment while Tor is
23596 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
23597 - Use an appropriate-width type for sockets in tor-fw-helper on
23598 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
23601 - When sending or relaying a RELAY_EARLY cell, we used to convert
23602 it to a RELAY cell if the connection was using the v1 link
23603 protocol. This was a workaround for older versions of Tor, which
23604 didn't handle RELAY_EARLY cells properly. Now that all supported
23605 versions can handle RELAY_EARLY cells, and now that we're enforcing
23606 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
23607 remove this workaround. Addresses bug 4786.
23609 o Code simplifications and refactoring:
23610 - Use OpenSSL's built-in SSL_state_string_long() instead of our
23611 own homebrewed ssl_state_to_string() replacement. Patch from
23612 Emile Snyder. Fixes bug 4653.
23613 - Use macros to indicate OpenSSL versions, so we don't need to worry
23614 about accidental hexadecimal bit shifts.
23615 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
23617 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
23618 - Use the smartlist_add_asprintf() alias more consistently.
23619 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
23620 invalid value, rather than just -1.
23621 - Rename a handful of old identifiers, mostly related to crypto
23622 structures and crypto functions. By convention, our "create an
23623 object" functions are called "type_new()", our "free an object"
23624 functions are called "type_free()", and our types indicate that
23625 they are types only with a final "_t". But a handful of older
23626 types and functions broke these rules, with function names like
23627 "type_create" or "subsystem_op_type", or with type names like
23631 Changes in version 0.2.3.10-alpha - 2011-12-16
23632 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
23633 Tor's buffers code. Absolutely everybody should upgrade.
23635 The bug relied on an incorrect calculation when making data continuous
23636 in one of our IO buffers, if the first chunk of the buffer was
23637 misaligned by just the wrong amount. The miscalculation would allow an
23638 attacker to overflow a piece of heap-allocated memory. To mount this
23639 attack, the attacker would need to either open a SOCKS connection to
23640 Tor's SocksPort (usually restricted to localhost), or target a Tor
23641 instance configured to make its connections through a SOCKS proxy
23642 (which Tor does not do by default).
23644 Good security practice requires that all heap-overflow bugs should be
23645 presumed to be exploitable until proven otherwise, so we are treating
23646 this as a potential code execution attack. Please upgrade immediately!
23647 This bug does not affect bufferevents-based builds of Tor. Special
23648 thanks to "Vektor" for reporting this issue to us!
23650 This release also contains a few minor bugfixes for issues discovered
23654 - Fix a heap overflow bug that could occur when trying to pull
23655 data into the first chunk of a buffer, when that chunk had
23656 already had some data drained from it. Fixes CVE-2011-2778;
23657 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
23660 - If we can't attach streams to a rendezvous circuit when we
23661 finish connecting to a hidden service, clear the rendezvous
23662 circuit's stream-isolation state and try to attach streams
23663 again. Previously, we cleared rendezvous circuits' isolation
23664 state either too early (if they were freshly built) or not at all
23665 (if they had been built earlier and were cannibalized). Bugfix on
23666 0.2.3.3-alpha; fixes bug 4655.
23667 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
23668 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
23669 - Fix an assertion failure when a relay with accounting enabled
23670 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
23673 - Update to the December 6 2011 Maxmind GeoLite Country database.
23676 Changes in version 0.2.2.35 - 2011-12-16
23677 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
23678 buffers code. Absolutely everybody should upgrade.
23680 The bug relied on an incorrect calculation when making data continuous
23681 in one of our IO buffers, if the first chunk of the buffer was
23682 misaligned by just the wrong amount. The miscalculation would allow an
23683 attacker to overflow a piece of heap-allocated memory. To mount this
23684 attack, the attacker would need to either open a SOCKS connection to
23685 Tor's SocksPort (usually restricted to localhost), or target a Tor
23686 instance configured to make its connections through a SOCKS proxy
23687 (which Tor does not do by default).
23689 Good security practice requires that all heap-overflow bugs should be
23690 presumed to be exploitable until proven otherwise, so we are treating
23691 this as a potential code execution attack. Please upgrade immediately!
23692 This bug does not affect bufferevents-based builds of Tor. Special
23693 thanks to "Vektor" for reporting this issue to us!
23695 Tor 0.2.2.35 also fixes several bugs in previous versions, including
23696 crash bugs for unusual configurations, and a long-term bug that
23697 would prevent Tor from starting on Windows machines with draconian
23700 With this release, we remind everyone that 0.2.0.x has reached its
23701 formal end-of-life. Those Tor versions have many known flaws, and
23702 nobody should be using them. You should upgrade -- ideally to the
23703 0.2.2.x series. If you're using a Linux or BSD and its packages are
23704 obsolete, stop using those packages and upgrade anyway.
23706 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
23707 longer receive support after some time in early 2012.
23710 - Fix a heap overflow bug that could occur when trying to pull
23711 data into the first chunk of a buffer, when that chunk had
23712 already had some data drained from it. Fixes CVE-2011-2778;
23713 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
23714 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
23715 that it doesn't attempt to allocate a socketpair. This could cause
23716 some problems on Windows systems with overzealous firewalls. Fix for
23717 bug 4457; workaround for Libevent versions 2.0.1-alpha through
23719 - If we mark an OR connection for close based on a cell we process,
23720 don't process any further cells on it. We already avoid further
23721 reads on marked-for-close connections, but now we also discard the
23722 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
23723 which was the first version where we might mark a connection for
23724 close based on processing a cell on it.
23725 - Correctly sanity-check that we don't underflow on a memory
23726 allocation (and then assert) for hidden service introduction
23727 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
23728 bugfix on 0.2.1.5-alpha.
23729 - Fix a memory leak when we check whether a hidden service
23730 descriptor has any usable introduction points left. Fixes bug
23731 4424. Bugfix on 0.2.2.25-alpha.
23732 - Don't crash when we're running as a relay and don't have a GeoIP
23733 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
23734 we've had in the 0.2.3.x branch already.
23735 - When running as a client, do not print a misleading (and plain
23736 wrong) log message that we're collecting "directory request"
23737 statistics: clients don't collect statistics. Also don't create a
23738 useless (because empty) stats file in the stats/ directory. Fixes
23739 bug 4353; bugfix on 0.2.2.34.
23742 - Detect failure to initialize Libevent. This fix provides better
23743 detection for future instances of bug 4457.
23744 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
23745 function. This was eating up hideously large amounts of time on some
23746 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
23747 - Resolve an integer overflow bug in smartlist_ensure_capacity().
23748 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
23750 - Don't warn about unused log_mutex in log.c when building with
23751 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
23752 0.1.0.6-rc which introduced --disable-threads.
23753 - When configuring, starting, or stopping an NT service, stop
23754 immediately after the service configuration attempt has succeeded
23755 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
23756 - When sending a NETINFO cell, include the original address
23757 received for the other side, not its canonical address. Found
23758 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
23759 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
23760 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
23761 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
23762 occurred when a client tried to fetch a descriptor for a bridge
23763 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
23764 - Backport fixes for a pair of compilation warnings on Windows.
23765 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
23766 - If we had ever tried to call tor_addr_to_str on an address of
23767 unknown type, we would have done a strdup on an uninitialized
23768 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
23769 Reported by "troll_un".
23770 - Correctly detect and handle transient lookup failures from
23771 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
23772 Reported by "troll_un".
23773 - Fix null-pointer access that could occur if TLS allocation failed.
23774 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
23775 - Use tor_socket_t type for listener argument to accept(). Fixes bug
23776 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
23779 - Add two new config options for directory authorities:
23780 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
23781 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
23782 that is always sufficient to satisfy the bandwidth requirement for
23783 the Guard flag. Now it will be easier for researchers to simulate
23784 Tor networks with different values. Resolves ticket 4484.
23785 - When Tor ignores a hidden service specified in its configuration,
23786 include the hidden service's directory in the warning message.
23787 Previously, we would only tell the user that some hidden service
23788 was ignored. Bugfix on 0.0.6; fixes bug 4426.
23789 - Update to the December 6 2011 Maxmind GeoLite Country database.
23791 o Packaging changes:
23792 - Make it easier to automate expert package builds on Windows,
23793 by removing an absolute path from makensis.exe command.
23796 Changes in version 0.2.1.32 - 2011-12-16
23797 Tor 0.2.1.32 backports important security and privacy fixes for
23798 oldstable. This release is intended only for package maintainers and
23799 others who cannot use the 0.2.2 stable series. All others should be
23800 using Tor 0.2.2.x or newer.
23802 The Tor 0.2.1.x series will reach formal end-of-life some time in
23803 early 2012; we will stop releasing patches for it then.
23805 o Major bugfixes (also included in 0.2.2.x):
23806 - Correctly sanity-check that we don't underflow on a memory
23807 allocation (and then assert) for hidden service introduction
23808 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
23809 bugfix on 0.2.1.5-alpha.
23810 - Fix a heap overflow bug that could occur when trying to pull
23811 data into the first chunk of a buffer, when that chunk had
23812 already had some data drained from it. Fixes CVE-2011-2778;
23813 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
23816 - Update to the December 6 2011 Maxmind GeoLite Country database.
23819 Changes in version 0.2.3.9-alpha - 2011-12-08
23820 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
23821 a "DisableNetwork" security feature that bundles can use to avoid
23822 touching the network until bridges are configured, moves forward on
23823 the pluggable transport design, fixes a flaw in the hidden service
23824 design that unnecessarily prevented clients with wrong clocks from
23825 reaching hidden services, and fixes a wide variety of other issues.
23828 - Clients can now connect to private bridges over IPv6. Bridges
23829 still need at least one IPv4 address in order to connect to
23830 other relays. Note that we don't yet handle the case where the
23831 user has two bridge lines for the same bridge (one IPv4, one
23832 IPv6). Implements parts of proposal 186.
23833 - New "DisableNetwork" config option to prevent Tor from launching any
23834 connections or accepting any connections except on a control port.
23835 Bundles and controllers can set this option before letting Tor talk
23836 to the rest of the network, for example to prevent any connections
23837 to a non-bridge address. Packages like Orbot can also use this
23838 option to instruct Tor to save power when the network is off.
23839 - Clients and bridges can now be configured to use a separate
23840 "transport" proxy. This approach makes the censorship arms race
23841 easier by allowing bridges to use protocol obfuscation plugins. It
23842 implements the "managed proxy" part of proposal 180 (ticket 3472).
23843 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
23844 implementation. It makes AES_CTR about 7% faster than our old one
23845 (which was about 10% faster than the one OpenSSL used to provide).
23846 Resolves ticket 4526.
23847 - Add a "tor2web mode" for clients that want to connect to hidden
23848 services non-anonymously (and possibly more quickly). As a safety
23849 measure to try to keep users from turning this on without knowing
23850 what they are doing, tor2web mode must be explicitly enabled at
23851 compile time, and a copy of Tor compiled to run in tor2web mode
23852 cannot be used as a normal Tor client. Implements feature 2553.
23853 - Add experimental support for running on Windows with IOCP and no
23854 kernel-space socket buffers. This feature is controlled by a new
23855 "UserspaceIOCPBuffers" config option (off by default), which has
23856 no effect unless Tor has been built with support for bufferevents,
23857 is running on Windows, and has enabled IOCP. This may, in the long
23858 run, help solve or mitigate bug 98.
23859 - Use a more secure consensus parameter voting algorithm. Now at
23860 least three directory authorities or a majority of them must
23861 vote on a given parameter before it will be included in the
23862 consensus. Implements proposal 178.
23865 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
23866 They used to check that the timestamp was within 30 minutes
23867 of their system clock, so they could cap the size of their
23868 replay-detection cache, but that approach unnecessarily refused
23869 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
23870 the v3 intro-point protocol (the first one which sent a timestamp
23871 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
23872 - Only use the EVP interface when AES acceleration is enabled,
23873 to avoid a 5-7% performance regression. Resolves issue 4525;
23874 bugfix on 0.2.3.8-alpha.
23876 o Privacy/anonymity features (bridge detection):
23877 - Make bridge SSL certificates a bit more stealthy by using random
23878 serial numbers, in the same fashion as OpenSSL when generating
23879 self-signed certificates. Implements ticket 4584.
23880 - Introduce a new config option "DynamicDHGroups", enabled by
23881 default, which provides each bridge with a unique prime DH modulus
23882 to be used during SSL handshakes. This option attempts to help
23883 against censors who might use the Apache DH modulus as a static
23884 identifier for bridges. Addresses ticket 4548.
23886 o Minor features (new/different config options):
23887 - New configuration option "DisableDebuggerAttachment" (on by default)
23888 to prevent basic debugging attachment attempts by other processes.
23889 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
23890 - Allow MapAddress directives to specify matches against super-domains,
23891 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
23892 Implements issue 933.
23893 - Slightly change behavior of "list" options (that is, config
23894 options that can appear more than once) when they appear both in
23895 torrc and on the command line. Previously, the command-line options
23896 would be appended to the ones from torrc. Now, the command-line
23897 options override the torrc options entirely. This new behavior
23898 allows the user to override list options (like exit policies and
23899 ports to listen on) from the command line, rather than simply
23900 appending to the list.
23901 - You can get the old (appending) command-line behavior for "list"
23902 options by prefixing the option name with a "+".
23903 - You can remove all the values for a "list" option from the command
23904 line without adding any new ones by prefixing the option name
23906 - Add experimental support for a "defaults" torrc file to be parsed
23907 before the regular torrc. Torrc options override the defaults file's
23908 options in the same way that the command line overrides the torrc.
23909 The SAVECONF controller command saves only those options which
23910 differ between the current configuration and the defaults file. HUP
23911 reloads both files. (Note: This is an experimental feature; its
23912 behavior will probably be refined in future 0.2.3.x-alpha versions
23913 to better meet packagers' needs.) Implements task 4552.
23916 - Try to make the introductory warning message that Tor prints on
23917 startup more useful for actually finding help and information.
23918 Resolves ticket 2474.
23919 - Running "make version" now displays the version of Tor that
23920 we're about to build. Idea from katmagic; resolves issue 4400.
23921 - Expire old or over-used hidden service introduction points.
23922 Required by fix for bug 3460.
23923 - Move the replay-detection cache for the RSA-encrypted parts of
23924 INTRODUCE2 cells to the introduction point data structures.
23925 Previously, we would use one replay-detection cache per hidden
23926 service. Required by fix for bug 3460.
23927 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
23928 public key replay-detection cache from 60 minutes to 5 minutes. This
23929 replay-detection cache is now used only to detect multiple
23930 INTRODUCE2 cells specifying the same rendezvous point, so we can
23931 avoid launching multiple simultaneous attempts to connect to it.
23933 o Minor bugfixes (on Tor 0.2.2.x and earlier):
23934 - Resolve an integer overflow bug in smartlist_ensure_capacity().
23935 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
23937 - Fix a minor formatting issue in one of tor-gencert's error messages.
23939 - Prevent a false positive from the check-spaces script, by disabling
23940 the "whitespace between function name and (" check for functions
23942 - Fix a log message suggesting that people contact a non-existent
23943 email address. Fixes bug 3448.
23944 - Fix null-pointer access that could occur if TLS allocation failed.
23945 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
23946 - Report a real bootstrap problem to the controller on router
23947 identity mismatch. Previously we just said "foo", which probably
23948 made a lot of sense at the time. Fixes bug 4169; bugfix on
23950 - If we had ever tried to call tor_addr_to_str() on an address of
23951 unknown type, we would have done a strdup() on an uninitialized
23952 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
23953 Reported by "troll_un".
23954 - Correctly detect and handle transient lookup failures from
23955 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
23956 Reported by "troll_un".
23957 - Use tor_socket_t type for listener argument to accept(). Fixes bug
23958 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
23959 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
23960 bug 4532; found by "troll_un".
23962 o Minor bugfixes (on Tor 0.2.3.x):
23963 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
23965 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
23966 circuit for use as a hidden service client's rendezvous point.
23967 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
23968 with help from wanoskarnet.
23969 - Restore behavior of overriding SocksPort, ORPort, and similar
23970 options from the command line. Bugfix on 0.2.3.3-alpha.
23973 - Properly handle the case where the build-tree is not the same
23974 as the source tree when generating src/common/common_sha1.i,
23975 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
23976 bugfix on 0.2.0.1-alpha.
23978 o Code simplifications, cleanups, and refactorings:
23979 - Remove the pure attribute from all functions that used it
23980 previously. In many cases we assigned it incorrectly, because the
23981 functions might assert or call impure functions, and we don't have
23982 evidence that keeping the pure attribute is worthwhile. Implements
23983 changes suggested in ticket 4421.
23984 - Remove some dead code spotted by coverity. Fixes cid 432.
23985 Bugfix on 0.2.3.1-alpha, closes bug 4637.
23988 Changes in version 0.2.3.8-alpha - 2011-11-22
23989 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
23990 socketpair-related bug that has been bothering Windows users. It adds
23991 support to serve microdescriptors to controllers, so Vidalia's network
23992 map can resume listing relays (once Vidalia implements its side),
23993 and adds better support for hardware AES acceleration. Finally, it
23994 starts the process of adjusting the bandwidth cutoff for getting the
23995 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
23996 that tiny relays harm performance more than they help network capacity.
23999 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
24000 that it doesn't attempt to allocate a socketpair. This could cause
24001 some problems on Windows systems with overzealous firewalls. Fix for
24002 bug 4457; workaround for Libevent versions 2.0.1-alpha through
24004 - Correctly sanity-check that we don't underflow on a memory
24005 allocation (and then assert) for hidden service introduction
24006 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
24007 bugfix on 0.2.1.5-alpha.
24008 - Remove the artificially low cutoff of 20KB to guarantee the Fast
24009 flag. In the past few years the average relay speed has picked
24010 up, and while the "top 7/8 of the network get the Fast flag" and
24011 "all relays with 20KB or more of capacity get the Fast flag" rules
24012 used to have the same result, now the top 7/8 of the network has
24013 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
24014 - Fix a rare assertion failure when checking whether a v0 hidden
24015 service descriptor has any usable introduction points left, and
24016 we don't have enough information to build a circuit to the first
24017 intro point named in the descriptor. The HS client code in
24018 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
24019 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
24020 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
24021 - Make bridge authorities not crash when they are asked for their own
24022 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
24023 - When running as a client, do not print a misleading (and plain
24024 wrong) log message that we're collecting "directory request"
24025 statistics: clients don't collect statistics. Also don't create a
24026 useless (because empty) stats file in the stats/ directory. Fixes
24027 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
24030 - Allow Tor controllers like Vidalia to obtain the microdescriptor
24031 for a relay by identity digest or nickname. Previously,
24032 microdescriptors were only available by their own digests, so a
24033 controller would have to ask for and parse the whole microdescriptor
24034 consensus in order to look up a single relay's microdesc. Fixes
24035 bug 3832; bugfix on 0.2.3.1-alpha.
24036 - Use OpenSSL's EVP interface for AES encryption, so that all AES
24037 operations can use hardware acceleration (if present). Resolves
24040 o Minor bugfixes (on 0.2.2.x and earlier):
24041 - Detect failure to initialize Libevent. This fix provides better
24042 detection for future instances of bug 4457.
24043 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
24044 function. This was eating up hideously large amounts of time on some
24045 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
24046 - Don't warn about unused log_mutex in log.c when building with
24047 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
24048 0.1.0.6-rc which introduced --disable-threads.
24049 - Allow manual 'authenticate' commands to the controller interface
24050 from netcat (nc) as well as telnet. We were rejecting them because
24051 they didn't come with the expected whitespace at the end of the
24052 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
24053 - Fix some (not actually triggerable) buffer size checks in usage of
24054 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
24056 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
24057 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
24058 - When configuring, starting, or stopping an NT service, stop
24059 immediately after the service configuration attempt has succeeded
24060 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
24061 - When sending a NETINFO cell, include the original address
24062 received for the other side, not its canonical address. Found
24063 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
24064 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
24065 can pick them up when the tests aren't disabled. Bugfix on
24066 0.2.2.4-alpha which introduced tinytest.
24067 - Fix a memory leak when we check whether a hidden service
24068 descriptor has any usable introduction points left. Fixes bug
24069 4424. Bugfix on 0.2.2.25-alpha.
24070 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
24071 occurred when a client tried to fetch a descriptor for a bridge
24072 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
24074 o Minor bugfixes (on 0.2.3.x):
24075 - Make util unit tests build correctly with MSVC. Bugfix on
24076 0.2.3.3-alpha. Patch by Gisle Vanem.
24077 - Successfully detect AUTH_CHALLENGE cells with no recognized
24078 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
24079 Found by frosty_un.
24080 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
24081 it should still send a NETINFO cell to allow the connection to
24082 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
24084 - Log less loudly when we get an invalid authentication certificate
24085 from a source other than a directory authority: it's not unusual
24086 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
24088 - Tolerate servers with more clock skew in their authentication
24089 certificates than previously. Fixes bug 4371; bugfix on
24091 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
24092 on 0.2.3.4-alpha and 0.2.3.6-alpha.
24095 - Add two new config options for directory authorities:
24096 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
24097 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
24098 that is always sufficient to satisfy the bandwidth requirement for
24099 the Guard flag. Now it will be easier for researchers to simulate
24100 Tor networks with different values. Resolves ticket 4484.
24101 - When Tor ignores a hidden service specified in its configuration,
24102 include the hidden service's directory in the warning message.
24103 Previously, we would only tell the user that some hidden service
24104 was ignored. Bugfix on 0.0.6; fixes bug 4426.
24105 - When we fail to initialize Libevent, retry with IOCP disabled so we
24106 don't need to turn on multi-threading support in Libevent, which in
24107 turn requires a working socketpair(). This is a workaround for bug
24108 4457, which affects Libevent versions from 2.0.1-alpha through
24110 - Detect when we try to build on a platform that doesn't define
24111 AF_UNSPEC to 0. We don't work there, so refuse to compile.
24112 - Update to the November 1 2011 Maxmind GeoLite Country database.
24114 o Packaging changes:
24115 - Make it easier to automate expert package builds on Windows,
24116 by removing an absolute path from makensis.exe command.
24118 o Code simplifications and refactoring:
24119 - Remove some redundant #include directives throughout the code.
24120 Patch from Andrea Gelmini.
24121 - Unconditionally use OpenSSL's AES implementation instead of our
24122 old built-in one. OpenSSL's AES has been better for a while, and
24123 relatively few servers should still be on any version of OpenSSL
24124 that doesn't have good optimized assembly AES.
24125 - Use the name "CERTS" consistently to refer to the new cell type;
24126 we were calling it CERT in some places and CERTS in others.
24129 - Numerous new unit tests for functions in util.c and address.c by
24131 - The long-disabled benchmark tests are now split into their own
24132 ./src/test/bench binary.
24133 - The benchmark tests can now use more accurate timers than
24134 gettimeofday() when such timers are available.
24137 Changes in version 0.2.3.7-alpha - 2011-10-30
24138 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
24139 the new v3 handshake. It also resolves yet another bridge address
24143 - If we mark an OR connection for close based on a cell we process,
24144 don't process any further cells on it. We already avoid further
24145 reads on marked-for-close connections, but now we also discard the
24146 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
24147 which was the first version where we might mark a connection for
24148 close based on processing a cell on it.
24149 - Fix a double-free bug that would occur when we received an invalid
24150 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
24151 bugfix on 0.2.3.6-alpha.
24152 - Bridges no longer include their address in NETINFO cells on outgoing
24153 OR connections, to allow them to blend in better with clients.
24154 Removes another avenue for enumerating bridges. Reported by
24155 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
24156 cells were introduced.
24159 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
24160 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
24163 Changes in version 0.2.3.6-alpha - 2011-10-26
24164 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
24165 anonymity vulnerability where an attacker can deanonymize Tor
24166 users. Everybody should upgrade.
24168 This release also features support for a new v3 connection handshake
24169 protocol, and fixes to make hidden service connections more robust.
24172 - Implement a new handshake protocol (v3) for authenticating Tors to
24173 each other over TLS. It should be more resistant to fingerprinting
24174 than previous protocols, and should require less TLS hacking for
24175 future Tor implementations. Implements proposal 176.
24176 - Allow variable-length padding cells to disguise the length of
24177 Tor's TLS records. Implements part of proposal 184.
24179 o Privacy/anonymity fixes (clients):
24180 - Clients and bridges no longer send TLS certificate chains on
24181 outgoing OR connections. Previously, each client or bridge would
24182 use the same cert chain for all outgoing OR connections until
24183 its IP address changes, which allowed any relay that the client
24184 or bridge contacted to determine which entry guards it is using.
24185 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
24186 - If a relay receives a CREATE_FAST cell on a TLS connection, it
24187 no longer considers that connection as suitable for satisfying a
24188 circuit EXTEND request. Now relays can protect clients from the
24189 CVE-2011-2768 issue even if the clients haven't upgraded yet.
24190 - Directory authorities no longer assign the Guard flag to relays
24191 that haven't upgraded to the above "refuse EXTEND requests
24192 to client connections" fix. Now directory authorities can
24193 protect clients from the CVE-2011-2768 issue even if neither
24194 the clients nor the relays have upgraded yet. There's a new
24195 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
24196 to let us transition smoothly, else tomorrow there would be no
24199 o Major bugfixes (hidden services):
24200 - Improve hidden service robustness: when an attempt to connect to
24201 a hidden service ends, be willing to refetch its hidden service
24202 descriptors from each of the HSDir relays responsible for them
24203 immediately. Previously, we would not consider refetching the
24204 service's descriptors from each HSDir for 15 minutes after the last
24205 fetch, which was inconvenient if the hidden service was not running
24206 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
24207 - When one of a hidden service's introduction points appears to be
24208 unreachable, stop trying it. Previously, we would keep trying
24209 to build circuits to the introduction point until we lost the
24210 descriptor, usually because the user gave up and restarted Tor.
24211 Partly fixes bug 3825.
24212 - Don't launch a useless circuit after failing to use one of a
24213 hidden service's introduction points. Previously, we would
24214 launch a new introduction circuit, but not set the hidden service
24215 which that circuit was intended to connect to, so it would never
24216 actually be used. A different piece of code would then create a
24217 new introduction circuit correctly. Bug reported by katmagic and
24218 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
24220 o Major bugfixes (other):
24221 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
24222 that they initiated. Relays could distinguish incoming bridge
24223 connections from client connections, creating another avenue for
24224 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
24225 Found by "frosty_un".
24226 - Don't update the AccountingSoftLimitHitAt state file entry whenever
24227 tor gets started. This prevents a wrong average bandwidth
24228 estimate, which would cause relays to always start a new accounting
24229 interval at the earliest possible moment. Fixes bug 2003; bugfix
24230 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
24231 immensely in tracking this bug down.
24232 - Fix a crash bug when changing node restrictions while a DNS lookup
24233 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
24236 o Minor bugfixes (on 0.2.2.x and earlier):
24237 - When a hidden service turns an extra service-side introduction
24238 circuit into a general-purpose circuit, free the rend_data and
24239 intro_key fields first, so we won't leak memory if the circuit
24240 is cannibalized for use as another service-side introduction
24241 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
24242 - Rephrase the log message emitted if the TestSocks check is
24243 successful. Patch from Fabian Keil; fixes bug 4094.
24244 - Bridges now skip DNS self-tests, to act a little more stealthily.
24245 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
24246 bridges. Patch by "warms0x".
24247 - Remove a confusing dollar sign from the example fingerprint in the
24248 man page, and also make the example fingerprint a valid one. Fixes
24249 bug 4309; bugfix on 0.2.1.3-alpha.
24250 - Fix internal bug-checking logic that was supposed to catch
24251 failures in digest generation so that it will fail more robustly
24252 if we ask for a nonexistent algorithm. Found by Coverity Scan.
24253 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
24254 - Report any failure in init_keys() calls launched because our
24255 IP address has changed. Spotted by Coverity Scan. Bugfix on
24256 0.1.1.4-alpha; fixes CID 484.
24258 o Minor bugfixes (on 0.2.3.x):
24259 - Fix a bug in configure.in that kept it from building a configure
24260 script with autoconf versions earlier than 2.61. Fixes bug 2430;
24261 bugfix on 0.2.3.1-alpha.
24262 - Don't warn users that they are exposing a client port to the
24263 Internet if they have specified an RFC1918 address. Previously,
24264 we would warn if the user had specified any non-loopback
24265 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
24266 - Fix memory leaks in the failing cases of the new SocksPort and
24267 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
24268 fixes coverity CIDs 485, 486, and 487.
24271 - When a hidden service's introduction point times out, consider
24272 trying it again during the next attempt to connect to the
24273 HS. Previously, we would not try it again unless a newly fetched
24274 descriptor contained it. Required by fixes for bugs 1297 and 3825.
24275 - The next version of Windows will be called Windows 8, and it has
24276 a major version of 6, minor version of 2. Correctly identify that
24277 version instead of calling it "Very recent version". Resolves
24278 ticket 4153; reported by funkstar.
24279 - The Bridge Authority now writes statistics on how many bridge
24280 descriptors it gave out in total, and how many unique descriptors
24281 it gave out. It also lists how often the most and least commonly
24282 fetched descriptors were given out, as well as the median and
24283 25th/75th percentile. Implements tickets 4200 and 4294.
24284 - Update to the October 4 2011 Maxmind GeoLite Country database.
24286 o Code simplifications and refactoring:
24287 - Remove some old code to remember statistics about which descriptors
24288 we've served as a directory mirror. The feature wasn't used and
24289 is outdated now that microdescriptors are around.
24290 - Rename Tor functions that turn strings into addresses, so that
24291 "parse" indicates that no hostname resolution occurs, and
24292 "lookup" indicates that hostname resolution may occur. This
24293 should help prevent mistakes in the future. Fixes bug 3512.
24296 Changes in version 0.2.2.34 - 2011-10-26
24297 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
24298 can deanonymize Tor users. Everybody should upgrade.
24300 The attack relies on four components: 1) Clients reuse their TLS cert
24301 when talking to different relays, so relays can recognize a user by
24302 the identity key in her cert. 2) An attacker who knows the client's
24303 identity key can probe each guard relay to see if that identity key
24304 is connected to that guard relay right now. 3) A variety of active
24305 attacks in the literature (starting from "Low-Cost Traffic Analysis
24306 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
24307 discover the guard relays that a Tor user visiting the website is using.
24308 4) Clients typically pick three guards at random, so the set of guards
24309 for a given user could well be a unique fingerprint for her. This
24310 release fixes components #1 and #2, which is enough to block the attack;
24311 the other two remain as open research problems. Special thanks to
24312 "frosty_un" for reporting the issue to us!
24314 Clients should upgrade so they are no longer recognizable by the TLS
24315 certs they present. Relays should upgrade so they no longer allow a
24316 remote attacker to probe them to test whether unpatched clients are
24317 currently connected to them.
24319 This release also fixes several vulnerabilities that allow an attacker
24320 to enumerate bridge relays. Some bridge enumeration attacks still
24321 remain; see for example proposal 188.
24323 o Privacy/anonymity fixes (clients):
24324 - Clients and bridges no longer send TLS certificate chains on
24325 outgoing OR connections. Previously, each client or bridge would
24326 use the same cert chain for all outgoing OR connections until
24327 its IP address changes, which allowed any relay that the client
24328 or bridge contacted to determine which entry guards it is using.
24329 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
24330 - If a relay receives a CREATE_FAST cell on a TLS connection, it
24331 no longer considers that connection as suitable for satisfying a
24332 circuit EXTEND request. Now relays can protect clients from the
24333 CVE-2011-2768 issue even if the clients haven't upgraded yet.
24334 - Directory authorities no longer assign the Guard flag to relays
24335 that haven't upgraded to the above "refuse EXTEND requests
24336 to client connections" fix. Now directory authorities can
24337 protect clients from the CVE-2011-2768 issue even if neither
24338 the clients nor the relays have upgraded yet. There's a new
24339 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
24340 to let us transition smoothly, else tomorrow there would be no
24343 o Privacy/anonymity fixes (bridge enumeration):
24344 - Bridge relays now do their directory fetches inside Tor TLS
24345 connections, like all the other clients do, rather than connecting
24346 directly to the DirPort like public relays do. Removes another
24347 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
24348 - Bridges relays now build circuits for themselves in a more similar
24349 way to how clients build them. Removes another avenue for
24350 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
24351 when bridges were introduced.
24352 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
24353 that they initiated. Relays could distinguish incoming bridge
24354 connections from client connections, creating another avenue for
24355 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
24356 Found by "frosty_un".
24359 - Fix a crash bug when changing node restrictions while a DNS lookup
24360 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
24362 - Don't launch a useless circuit after failing to use one of a
24363 hidden service's introduction points. Previously, we would
24364 launch a new introduction circuit, but not set the hidden service
24365 which that circuit was intended to connect to, so it would never
24366 actually be used. A different piece of code would then create a
24367 new introduction circuit correctly. Bug reported by katmagic and
24368 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
24371 - Change an integer overflow check in the OpenBSD_Malloc code so
24372 that GCC is less likely to eliminate it as impossible. Patch
24373 from Mansour Moufid. Fixes bug 4059.
24374 - When a hidden service turns an extra service-side introduction
24375 circuit into a general-purpose circuit, free the rend_data and
24376 intro_key fields first, so we won't leak memory if the circuit
24377 is cannibalized for use as another service-side introduction
24378 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
24379 - Bridges now skip DNS self-tests, to act a little more stealthily.
24380 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
24381 bridges. Patch by "warms0x".
24382 - Fix internal bug-checking logic that was supposed to catch
24383 failures in digest generation so that it will fail more robustly
24384 if we ask for a nonexistent algorithm. Found by Coverity Scan.
24385 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
24386 - Report any failure in init_keys() calls launched because our
24387 IP address has changed. Spotted by Coverity Scan. Bugfix on
24388 0.1.1.4-alpha; fixes CID 484.
24390 o Minor bugfixes (log messages and documentation):
24391 - Remove a confusing dollar sign from the example fingerprint in the
24392 man page, and also make the example fingerprint a valid one. Fixes
24393 bug 4309; bugfix on 0.2.1.3-alpha.
24394 - The next version of Windows will be called Windows 8, and it has
24395 a major version of 6, minor version of 2. Correctly identify that
24396 version instead of calling it "Very recent version". Resolves
24397 ticket 4153; reported by funkstar.
24398 - Downgrade log messages about circuit timeout calibration from
24399 "notice" to "info": they don't require or suggest any human
24400 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
24401 bugfix on 0.2.2.14-alpha.
24404 - Turn on directory request statistics by default and include them in
24405 extra-info descriptors. Don't break if we have no GeoIP database.
24406 Backported from 0.2.3.1-alpha; implements ticket 3951.
24407 - Update to the October 4 2011 Maxmind GeoLite Country database.
24410 Changes in version 0.2.1.31 - 2011-10-26
24411 Tor 0.2.1.31 backports important security and privacy fixes for
24412 oldstable. This release is intended only for package maintainers and
24413 others who cannot use the 0.2.2 stable series. All others should be
24414 using Tor 0.2.2.x or newer.
24416 o Security fixes (also included in 0.2.2.x):
24417 - Replace all potentially sensitive memory comparison operations
24418 with versions whose runtime does not depend on the data being
24419 compared. This will help resist a class of attacks where an
24420 adversary can use variations in timing information to learn
24421 sensitive data. Fix for one case of bug 3122. (Safe memcmp
24422 implementation by Robert Ransom based partially on code by DJB.)
24423 - Fix an assert in parsing router descriptors containing IPv6
24424 addresses. This one took down the directory authorities when
24425 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
24427 o Privacy/anonymity fixes (also included in 0.2.2.x):
24428 - Clients and bridges no longer send TLS certificate chains on
24429 outgoing OR connections. Previously, each client or bridge would
24430 use the same cert chain for all outgoing OR connections until
24431 its IP address changes, which allowed any relay that the client
24432 or bridge contacted to determine which entry guards it is using.
24433 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
24434 - If a relay receives a CREATE_FAST cell on a TLS connection, it
24435 no longer considers that connection as suitable for satisfying a
24436 circuit EXTEND request. Now relays can protect clients from the
24437 CVE-2011-2768 issue even if the clients haven't upgraded yet.
24438 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
24439 that they initiated. Relays could distinguish incoming bridge
24440 connections from client connections, creating another avenue for
24441 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
24442 Found by "frosty_un".
24443 - When receiving a hidden service descriptor, check that it is for
24444 the hidden service we wanted. Previously, Tor would store any
24445 hidden service descriptors that a directory gave it, whether it
24446 wanted them or not. This wouldn't have let an attacker impersonate
24447 a hidden service, but it did let directories pre-seed a client
24448 with descriptors that it didn't want. Bugfix on 0.0.6.
24449 - Avoid linkability based on cached hidden service descriptors: forget
24450 all hidden service descriptors cached as a client when processing a
24451 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
24452 - Make the bridge directory authority refuse to answer directory
24453 requests for "all" descriptors. It used to include bridge
24454 descriptors in its answer, which was a major information leak.
24455 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
24456 - Don't attach new streams to old rendezvous circuits after SIGNAL
24457 NEWNYM. Previously, we would keep using an existing rendezvous
24458 circuit if it remained open (i.e. if it were kept open by a
24459 long-lived stream, or if a new stream were attached to it before
24460 Tor could notice that it was old and no longer in use). Bugfix on
24461 0.1.1.15-rc; fixes bug 3375.
24463 o Minor bugfixes (also included in 0.2.2.x):
24464 - When we restart our relay, we might get a successful connection
24465 from the outside before we've started our reachability tests,
24466 triggering a warning: "ORPort found reachable, but I have no
24467 routerinfo yet. Failing to inform controller of success." This
24468 bug was harmless unless Tor is running under a controller
24469 like Vidalia, in which case the controller would never get a
24470 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
24472 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
24473 enabled. Fixes bug 1526.
24474 - Remove undocumented option "-F" from tor-resolve: it hasn't done
24475 anything since 0.2.1.16-rc.
24476 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
24477 None of the cases where we did this before were wrong, but by making
24478 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
24479 - Fix a rare crash bug that could occur when a client was configured
24480 with a large number of bridges. Fixes bug 2629; bugfix on
24481 0.2.1.2-alpha. Bugfix by trac user "shitlei".
24482 - Correct the warning displayed when a rendezvous descriptor exceeds
24483 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
24485 - Fix an uncommon assertion failure when running with DNSPort under
24486 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
24487 - When warning about missing zlib development packages during compile,
24488 give the correct package names. Bugfix on 0.2.0.1-alpha.
24489 - Require that introduction point keys and onion keys have public
24490 exponent 65537. Bugfix on 0.2.0.10-alpha.
24491 - Do not crash when our configuration file becomes unreadable, for
24492 example due to a permissions change, between when we start up
24493 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
24495 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
24497 - Always NUL-terminate the sun_path field of a sockaddr_un before
24498 passing it to the kernel. (Not a security issue: kernels are
24499 smart enough to reject bad sockaddr_uns.) Found by Coverity;
24500 CID #428. Bugfix on Tor 0.2.0.3-alpha.
24501 - Don't stack-allocate the list of supplementary GIDs when we're
24502 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
24503 could take up to 256K, which is way too much stack. Found by
24504 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
24506 o Minor bugfixes (only in 0.2.1.x):
24507 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
24508 rely on them. Bugfix on 0.2.1.30.
24509 - Use git revisions instead of svn revisions when generating our
24510 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
24512 o Minor features (also included in 0.2.2.x):
24513 - Adjust the expiration time on our SSL session certificates to
24514 better match SSL certs seen in the wild. Resolves ticket 4014.
24515 - Allow nameservers with IPv6 address. Resolves bug 2574.
24516 - Update to the October 4 2011 Maxmind GeoLite Country database.
24519 Changes in version 0.2.3.5-alpha - 2011-09-28
24520 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
24521 bridge relays; fixes an assertion error that many users started hitting
24522 today; and adds the ability to refill token buckets more often than
24523 once per second, allowing significant performance improvements.
24526 - Bridge relays now do their directory fetches inside Tor TLS
24527 connections, like all the other clients do, rather than connecting
24528 directly to the DirPort like public relays do. Removes another
24529 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
24530 - Bridges relays now build circuits for themselves in a more similar
24531 way to how clients build them. Removes another avenue for
24532 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
24533 when bridges were introduced.
24536 - Fix an "Assertion md->held_by_node == 1 failed" error that could
24537 occur when the same microdescriptor was referenced by two node_t
24538 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
24540 o Major features (networking):
24541 - Add a new TokenBucketRefillInterval option to refill token buckets
24542 more frequently than once per second. This should improve network
24543 performance, alleviate queueing problems, and make traffic less
24544 bursty. Implements proposal 183; closes ticket 3630. Design by
24545 Florian Tschorsch and Björn Scheuermann; implementation by
24549 - Change an integer overflow check in the OpenBSD_Malloc code so
24550 that GCC is less likely to eliminate it as impossible. Patch
24551 from Mansour Moufid. Fixes bug 4059.
24553 o Minor bugfixes (usability):
24554 - Downgrade log messages about circuit timeout calibration from
24555 "notice" to "info": they don't require or suggest any human
24556 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
24557 bugfix on 0.2.2.14-alpha.
24559 o Minor features (diagnostics):
24560 - When the system call to create a listener socket fails, log the
24561 error message explaining why. This may help diagnose bug 4027.
24564 Changes in version 0.2.3.4-alpha - 2011-09-13
24565 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
24566 tweak to Tor's TLS handshake that makes relays and bridges that run
24567 this new version reachable from Iran again. It also fixes a few new
24568 bugs in 0.2.3.x, and teaches relays to recognize when they're not
24569 listed in the network consensus and republish.
24571 o Major bugfixes (also part of 0.2.2.33):
24572 - Avoid an assertion failure when reloading a configuration with
24573 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
24574 3923; bugfix on 0.2.2.25-alpha.
24576 o Minor features (security, also part of 0.2.2.33):
24577 - Check for replays of the public-key encrypted portion of an
24578 INTRODUCE1 cell, in addition to the current check for replays of
24579 the g^x value. This prevents a possible class of active attacks
24580 by an attacker who controls both an introduction point and a
24581 rendezvous point, and who uses the malleability of AES-CTR to
24582 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
24583 that these attacks are infeasible (requiring the attacker to send
24584 on the order of zettabytes of altered cells in a short interval),
24585 but we'd rather block them off in case there are any classes of
24586 this attack that we missed. Reported by Willem Pinckaers.
24588 o Minor features (also part of 0.2.2.33):
24589 - Adjust the expiration time on our SSL session certificates to
24590 better match SSL certs seen in the wild. Resolves ticket 4014.
24591 - Change the default required uptime for a relay to be accepted as
24592 a HSDir (hidden service directory) from 24 hours to 25 hours.
24593 Improves on 0.2.0.10-alpha; resolves ticket 2649.
24594 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
24595 authorities to abstain from voting on assignment of the HSDir
24596 consensus flag. Related to bug 2649.
24597 - Update to the September 6 2011 Maxmind GeoLite Country database.
24599 o Minor bugfixes (also part of 0.2.2.33):
24600 - Demote the 'replay detected' log message emitted when a hidden
24601 service receives the same Diffie-Hellman public key in two different
24602 INTRODUCE2 cells to info level. A normal Tor client can cause that
24603 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
24604 fixes part of bug 2442.
24605 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
24606 level. There is nothing that a hidden service's operator can do
24607 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
24609 - Clarify a log message specifying the characters permitted in
24610 HiddenServiceAuthorizeClient client names. Previously, the log
24611 message said that "[A-Za-z0-9+-_]" were permitted; that could have
24612 given the impression that every ASCII character between "+" and "_"
24613 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
24615 o Build fixes (also part of 0.2.2.33):
24616 - Clean up some code issues that prevented Tor from building on older
24617 BSDs. Fixes bug 3894; reported by "grarpamp".
24618 - Search for a platform-specific version of "ar" when cross-compiling.
24619 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
24622 - Fix a bug where the SocksPort option (for example) would get
24623 ignored and replaced by the default if a SocksListenAddress
24624 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
24628 - Relays now try regenerating and uploading their descriptor more
24629 frequently if they are not listed in the consensus, or if the
24630 version of their descriptor listed in the consensus is too
24631 old. This fix should prevent situations where a server declines
24632 to re-publish itself because it has done so too recently, even
24633 though the authorities decided not to list its recent-enough
24634 descriptor. Fix for bug 3327.
24637 - Relays now include a reason for regenerating their descriptors
24638 in an HTTP header when uploading to the authorities. This will
24639 make it easier to debug descriptor-upload issues in the future.
24640 - When starting as root and then changing our UID via the User
24641 control option, and we have a ControlSocket configured, make sure
24642 that the ControlSocket is owned by the same account that Tor will
24643 run under. Implements ticket 3421; fix by Jérémy Bobbio.
24646 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
24647 utility function used in the control-port code). This shouldn't
24648 ever happen unless Tor is completely out of memory, but if it did
24649 happen and Tor somehow recovered from it, Tor could have sent a log
24650 message to a control port in the middle of a reply to a controller
24651 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
24652 - Make 'FetchUselessDescriptors' cause all descriptor types and
24653 all consensus types (including microdescriptors) to get fetched.
24654 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
24656 o Code refactoring:
24657 - Make a new "entry connection" struct as an internal subtype of "edge
24658 connection", to simplify the code and make exit connections smaller.
24661 Changes in version 0.2.2.33 - 2011-09-13
24662 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
24663 TLS handshake that makes relays and bridges that run this new version
24664 reachable from Iran again.
24667 - Avoid an assertion failure when reloading a configuration with
24668 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
24669 3923; bugfix on 0.2.2.25-alpha.
24671 o Minor features (security):
24672 - Check for replays of the public-key encrypted portion of an
24673 INTRODUCE1 cell, in addition to the current check for replays of
24674 the g^x value. This prevents a possible class of active attacks
24675 by an attacker who controls both an introduction point and a
24676 rendezvous point, and who uses the malleability of AES-CTR to
24677 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
24678 that these attacks are infeasible (requiring the attacker to send
24679 on the order of zettabytes of altered cells in a short interval),
24680 but we'd rather block them off in case there are any classes of
24681 this attack that we missed. Reported by Willem Pinckaers.
24684 - Adjust the expiration time on our SSL session certificates to
24685 better match SSL certs seen in the wild. Resolves ticket 4014.
24686 - Change the default required uptime for a relay to be accepted as
24687 a HSDir (hidden service directory) from 24 hours to 25 hours.
24688 Improves on 0.2.0.10-alpha; resolves ticket 2649.
24689 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
24690 authorities to abstain from voting on assignment of the HSDir
24691 consensus flag. Related to bug 2649.
24692 - Update to the September 6 2011 Maxmind GeoLite Country database.
24694 o Minor bugfixes (documentation and log messages):
24695 - Correct the man page to explain that HashedControlPassword and
24696 CookieAuthentication can both be set, in which case either method
24697 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
24698 when we decided to allow these config options to both be set. Issue
24699 raised by bug 3898.
24700 - Demote the 'replay detected' log message emitted when a hidden
24701 service receives the same Diffie-Hellman public key in two different
24702 INTRODUCE2 cells to info level. A normal Tor client can cause that
24703 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
24704 fixes part of bug 2442.
24705 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
24706 level. There is nothing that a hidden service's operator can do
24707 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
24709 - Clarify a log message specifying the characters permitted in
24710 HiddenServiceAuthorizeClient client names. Previously, the log
24711 message said that "[A-Za-z0-9+-_]" were permitted; that could have
24712 given the impression that every ASCII character between "+" and "_"
24713 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
24716 - Provide a substitute implementation of lround() for MSVC, which
24717 apparently lacks it. Patch from Gisle Vanem.
24718 - Clean up some code issues that prevented Tor from building on older
24719 BSDs. Fixes bug 3894; reported by "grarpamp".
24720 - Search for a platform-specific version of "ar" when cross-compiling.
24721 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
24724 Changes in version 0.2.3.3-alpha - 2011-09-01
24725 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
24726 security, and provides client-side support for the microdescriptor
24727 and optimistic data features introduced earlier in the 0.2.3.x
24728 series. It also includes numerous critical bugfixes in the (optional)
24729 bufferevent-based networking backend.
24731 o Major features (stream isolation):
24732 - You can now configure Tor so that streams from different
24733 applications are isolated on different circuits, to prevent an
24734 attacker who sees your streams as they leave an exit node from
24735 linking your sessions to one another. To do this, choose some way
24736 to distinguish the applications: have them connect to different
24737 SocksPorts, or have one of them use SOCKS4 while the other uses
24738 SOCKS5, or have them pass different authentication strings to the
24739 SOCKS proxy. Then, use the new SocksPort syntax to configure the
24740 degree of isolation you need. This implements Proposal 171.
24741 - There's a new syntax for specifying multiple client ports (such as
24742 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
24743 multiple *Port entries with full addr:port syntax on each.
24744 The old *ListenAddress format is still supported, but you can't
24745 mix it with the new *Port syntax.
24747 o Major features (other):
24748 - Enable microdescriptor fetching by default for clients. This allows
24749 clients to download a much smaller amount of directory information.
24750 To disable it (and go back to the old-style consensus and
24751 descriptors), set "UseMicrodescriptors 0" in your torrc file.
24752 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
24753 "PortForwarding" config option), now supports Windows.
24754 - When using an exit relay running 0.2.3.x, clients can now
24755 "optimistically" send data before the exit relay reports that
24756 the stream has opened. This saves a round trip when starting
24757 connections where the client speaks first (such as web browsing).
24758 This behavior is controlled by a consensus parameter (currently
24759 disabled). To turn it on or off manually, use the "OptimisticData"
24760 torrc option. Implements proposal 181; code by Ian Goldberg.
24762 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
24763 - When using IOCP on Windows, we need to enable Libevent windows
24765 - The IOCP backend now works even when the user has not specified
24766 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
24767 Fixes part of bug 3752.
24768 - Correctly record the bytes we've read and written when using
24769 bufferevents, so that we can include them in our bandwidth history
24770 and advertised bandwidth. Fixes bug 3803.
24771 - Apply rate-limiting only at the bottom of a chain of filtering
24772 bufferevents. This prevents us from filling up internal read
24773 buffers and violating rate-limits when filtering bufferevents
24774 are enabled. Fixes part of bug 3804.
24775 - Add high-watermarks to the output buffers for filtered
24776 bufferevents. This prevents us from filling up internal write
24777 buffers and wasting CPU cycles when filtering bufferevents are
24778 enabled. Fixes part of bug 3804.
24779 - Correctly notice when data has been written from a bufferevent
24780 without flushing it completely. Fixes bug 3805.
24781 - Fix a bug where server-side tunneled bufferevent-based directory
24782 streams would get closed prematurely. Fixes bug 3814.
24783 - Fix a use-after-free error with per-connection rate-limiting
24784 buckets. Fixes bug 3888.
24786 o Major bugfixes (also part of 0.2.2.31-rc):
24787 - If we're configured to write our ControlPorts to disk, only write
24788 them after switching UID and creating the data directory. This way,
24789 we don't fail when starting up with a nonexistent DataDirectory
24790 and a ControlPortWriteToFile setting based on that directory. Fixes
24791 bug 3747; bugfix on Tor 0.2.2.26-beta.
24794 - Added a new CONF_CHANGED event so that controllers can be notified
24795 of any configuration changes made by other controllers, or by the
24796 user. Implements ticket 1692.
24797 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
24798 leak when using bufferevents, and lets Libevent worry about how to
24799 best copy data out of a buffer.
24800 - Replace files in stats/ rather than appending to them. Now that we
24801 include statistics in extra-info descriptors, it makes no sense to
24802 keep old statistics forever. Implements ticket 2930.
24804 o Minor features (build compatibility):
24805 - Limited, experimental support for building with nmake and MSVC.
24806 - Provide a substitute implementation of lround() for MSVC, which
24807 apparently lacks it. Patch from Gisle Vanem.
24809 o Minor features (also part of 0.2.2.31-rc):
24810 - Update to the August 2 2011 Maxmind GeoLite Country database.
24812 o Minor bugfixes (on 0.2.3.x-alpha):
24813 - Fix a spurious warning when parsing SOCKS requests with
24814 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
24815 - Get rid of a harmless warning that could happen on relays running
24816 with bufferevents. The warning was caused by someone doing an http
24817 request to a relay's orport. Also don't warn for a few related
24818 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
24820 o Minor bugfixes (on 2.2.x and earlier):
24821 - Correct the man page to explain that HashedControlPassword and
24822 CookieAuthentication can both be set, in which case either method
24823 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
24824 when we decided to allow these config options to both be set. Issue
24825 raised by bug 3898.
24826 - The "--quiet" and "--hush" options now apply not only to Tor's
24827 behavior before logs are configured, but also to Tor's behavior in
24828 the absence of configured logs. Fixes bug 3550; bugfix on
24831 o Minor bugfixes (also part of 0.2.2.31-rc):
24832 - Write several files in text mode, on OSes that distinguish text
24833 mode from binary mode (namely, Windows). These files are:
24834 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
24835 that collect those statistics; 'client_keys' and 'hostname' for
24836 hidden services that use authentication; and (in the tor-gencert
24837 utility) newly generated identity and signing keys. Previously,
24838 we wouldn't specify text mode or binary mode, leading to an
24839 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
24840 the DirRecordUsageByCountry option which would have triggered
24841 the assertion failure was added), although this assertion failure
24842 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
24843 - Selectively disable deprecation warnings on OS X because Lion
24844 started deprecating the shipped copy of openssl. Fixes bug 3643.
24845 - Remove an extra pair of quotation marks around the error
24846 message in control-port STATUS_GENERAL BUG events. Bugfix on
24847 0.1.2.6-alpha; fixes bug 3732.
24848 - When unable to format an address as a string, report its value
24849 as "???" rather than reusing the last formatted address. Bugfix
24852 o Code simplifications and refactoring:
24853 - Rewrite the listener-selection logic so that parsing which ports
24854 we want to listen on is now separate from binding to the ports
24858 - Building Tor with bufferevent support now requires Libevent
24859 2.0.13-stable or later. Previous versions of Libevent had bugs in
24860 SSL-related bufferevents and related issues that would make Tor
24861 work badly with bufferevents. Requiring 2.0.13-stable also allows
24862 Tor with bufferevents to take advantage of Libevent APIs
24863 introduced after 2.0.8-rc.
24866 Changes in version 0.2.2.32 - 2011-08-27
24867 The Tor 0.2.2 release series is dedicated to the memory of Andreas
24868 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
24869 a founder of the PETS community, a leader in our field, a mentor,
24870 and a friend. He left us with these words: "I had the possibility
24871 to contribute to this world that is not as it should be. I hope I
24872 could help in some areas to make the world a better place, and that
24873 I could also encourage other people to be engaged in improving the
24874 world. Please, stay engaged. This world needs you, your love, your
24875 initiative -- now I cannot be part of that anymore."
24877 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
24878 ready. More than two years in the making, this release features improved
24879 client performance and hidden service reliability, better compatibility
24880 for Android, correct behavior for bridges that listen on more than
24881 one address, more extensible and flexible directory object handling,
24882 better reporting of network statistics, improved code security, and
24883 many many other features and bugfixes.
24886 Changes in version 0.2.2.31-rc - 2011-08-17
24887 Tor 0.2.2.31-rc is the second and hopefully final release candidate
24888 for the Tor 0.2.2.x series.
24891 - Remove an extra pair of quotation marks around the error
24892 message in control-port STATUS_GENERAL BUG events. Bugfix on
24893 0.1.2.6-alpha; fixes bug 3732.
24894 - If we're configured to write our ControlPorts to disk, only write
24895 them after switching UID and creating the data directory. This way,
24896 we don't fail when starting up with a nonexistent DataDirectory
24897 and a ControlPortWriteToFile setting based on that directory. Fixes
24898 bug 3747; bugfix on Tor 0.2.2.26-beta.
24901 - Update to the August 2 2011 Maxmind GeoLite Country database.
24904 - Allow GETINFO fingerprint to return a fingerprint even when
24905 we have not yet built a router descriptor. Fixes bug 3577;
24906 bugfix on 0.2.0.1-alpha.
24907 - Write several files in text mode, on OSes that distinguish text
24908 mode from binary mode (namely, Windows). These files are:
24909 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
24910 that collect those statistics; 'client_keys' and 'hostname' for
24911 hidden services that use authentication; and (in the tor-gencert
24912 utility) newly generated identity and signing keys. Previously,
24913 we wouldn't specify text mode or binary mode, leading to an
24914 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
24915 the DirRecordUsageByCountry option which would have triggered
24916 the assertion failure was added), although this assertion failure
24917 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
24918 - Selectively disable deprecation warnings on OS X because Lion
24919 started deprecating the shipped copy of openssl. Fixes bug 3643.
24920 - When unable to format an address as a string, report its value
24921 as "???" rather than reusing the last formatted address. Bugfix
24925 Changes in version 0.2.3.2-alpha - 2011-07-18
24926 Tor 0.2.3.2-alpha introduces two new experimental features:
24927 microdescriptors and pluggable transports. It also continues cleaning
24928 up a variety of recently introduced features.
24931 - Clients can now use microdescriptors instead of regular descriptors
24932 to build circuits. Microdescriptors are authority-generated
24933 summaries of regular descriptors' contents, designed to change
24934 very rarely (see proposal 158 for details). This feature is
24935 designed to save bandwidth, especially for clients on slow internet
24936 connections. It's off by default for now, since nearly no caches
24937 support it, but it will be on-by-default for clients in a future
24938 version. You can use the UseMicrodescriptors option to turn it on.
24939 - Tor clients using bridges can now be configured to use a separate
24940 'transport' proxy for each bridge. This approach helps to resist
24941 censorship by allowing bridges to use protocol obfuscation
24942 plugins. It implements part of proposal 180. Implements ticket 2841.
24943 - While we're trying to bootstrap, record how many TLS connections
24944 fail in each state, and report which states saw the most failures
24945 in response to any bootstrap failures. This feature may speed up
24946 diagnosis of censorship events. Implements ticket 3116.
24948 o Major bugfixes (on 0.2.3.1-alpha):
24949 - When configuring a large set of nodes in EntryNodes (as with
24950 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
24951 random subset to be guards, and choose them in random
24952 order. Fixes bug 2798.
24953 - Tor could crash when remembering a consensus in a non-used consensus
24954 flavor without having a current consensus set. Fixes bug 3361.
24955 - Comparing an unknown address to a microdescriptor's shortened exit
24956 policy would always give a "rejected" result. Fixes bug 3599.
24957 - Using microdescriptors as a client no longer prevents Tor from
24958 uploading and downloading hidden service descriptors. Fixes
24962 - Allow nameservers with IPv6 address. Resolves bug 2574.
24963 - Accept attempts to include a password authenticator in the
24964 handshake, as supported by SOCKS5. This handles SOCKS clients that
24965 don't know how to omit a password when authenticating. Resolves
24967 - When configuring a large set of nodes in EntryNodes, and there are
24968 enough of them listed as Guard so that we don't need to consider
24969 the non-guard entries, prefer the ones listed with the Guard flag.
24970 - Check for and recover from inconsistency in the microdescriptor
24971 cache. This will make it harder for us to accidentally free a
24972 microdescriptor without removing it from the appropriate data
24973 structures. Fixes issue 3135; issue noted by "wanoskarnet".
24974 - Log SSL state transitions at log level DEBUG, log domain
24975 HANDSHAKE. This can be useful for debugging censorship events.
24976 Implements ticket 3264.
24977 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
24978 implements ticket 3439.
24980 o Minor bugfixes (on 0.2.3.1-alpha):
24981 - Do not free all general-purpose regular descriptors just
24982 because microdescriptor use is enabled. Fixes bug 3113.
24983 - Correctly link libevent_openssl when --enable-static-libevent
24984 is passed to configure. Fixes bug 3118.
24985 - Bridges should not complain during their heartbeat log messages that
24986 they are unlisted in the consensus: that's more or less the point
24987 of being a bridge. Fixes bug 3183.
24988 - Report a SIGNAL event to controllers when acting on a delayed
24989 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
24990 event to the controller if we acted on a SIGNAL NEWNYM command
24991 immediately, and otherwise not report a SIGNAL event for the
24992 command at all. Fixes bug 3349.
24993 - Fix a crash when handling the SIGNAL controller command or
24994 reporting ERR-level status events with bufferevents enabled. Found
24995 by Robert Ransom. Fixes bug 3367.
24996 - Always ship the tor-fw-helper manpage in our release tarballs.
24997 Fixes bug 3389. Reported by Stephen Walker.
24998 - Fix a class of double-mark-for-close bugs when bufferevents
24999 are enabled. Fixes bug 3403.
25000 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
25001 - Add SIGNAL to the list returned by the 'GETINFO events/names'
25002 control-port command. Fixes part of bug 3465.
25003 - Prevent using negative indices during unit test runs when read_all()
25004 fails. Spotted by coverity.
25005 - Fix a rare memory leak when checking the nodelist without it being
25006 present. Found by coverity.
25007 - Only try to download a microdescriptor-flavored consensus from
25008 a directory cache that provides them.
25010 o Minor bugfixes (on 0.2.2.x and earlier):
25011 - Assert that hidden-service-related operations are not performed
25012 using single-hop circuits. Previously, Tor would assert that
25013 client-side streams are not attached to single-hop circuits,
25014 but not that other sensitive operations on the client and service
25015 side are not performed using single-hop circuits. Fixes bug 3332;
25017 - Don't publish a new relay descriptor when we reload our onion key,
25018 unless the onion key has actually changed. Fixes bug 3263 and
25019 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
25020 - Allow GETINFO fingerprint to return a fingerprint even when
25021 we have not yet built a router descriptor. Fixes bug 3577;
25022 bugfix on 0.2.0.1-alpha.
25023 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
25024 on 0.2.2.4-alpha; fixes bug 3427.
25026 o Code simplification and refactoring:
25027 - Use tor_sscanf() in place of scanf() in more places through the
25028 code. This makes us a little more locale-independent, and
25029 should help shut up code-analysis tools that can't tell
25030 a safe sscanf string from a dangerous one.
25031 - Use tt_assert(), not tor_assert(), for checking for test failures.
25032 This makes the unit tests more able to go on in the event that
25034 - Split connection_about_to_close() into separate functions for each
25038 - On Windows, we now define the _WIN32_WINNT macros only if they
25039 are not already defined. This lets the person building Tor decide,
25040 if they want, to require a later version of Windows.
25043 Changes in version 0.2.2.30-rc - 2011-07-07
25044 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
25045 series. It fixes a few smaller bugs, but generally appears stable.
25046 Please test it and let us know whether it is!
25049 - Send a SUCCEEDED stream event to the controller when a reverse
25050 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
25051 discovered by katmagic.
25052 - Always NUL-terminate the sun_path field of a sockaddr_un before
25053 passing it to the kernel. (Not a security issue: kernels are
25054 smart enough to reject bad sockaddr_uns.) Found by Coverity;
25055 CID #428. Bugfix on Tor 0.2.0.3-alpha.
25056 - Don't stack-allocate the list of supplementary GIDs when we're
25057 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
25058 could take up to 256K, which is way too much stack. Found by
25059 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
25060 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
25061 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
25062 fixes part of bug 3465.
25063 - Fix a memory leak when receiving a descriptor for a hidden
25064 service we didn't ask for. Found by Coverity; CID #30. Bugfix
25068 - Update to the July 1 2011 Maxmind GeoLite Country database.
25071 Changes in version 0.2.2.29-beta - 2011-06-20
25072 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
25073 have bridge lines in their torrc but don't want to use them; gets
25074 us closer to having the control socket feature working on Debian;
25075 and fixes a variety of smaller bugs.
25078 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
25079 When we changed the default behavior to "use bridges if any
25080 are listed in the torrc", we surprised users who had bridges
25081 in their torrc files but who didn't actually want to use them.
25082 Partial resolution for bug 3354.
25085 - Don't attach new streams to old rendezvous circuits after SIGNAL
25086 NEWNYM. Previously, we would keep using an existing rendezvous
25087 circuit if it remained open (i.e. if it were kept open by a
25088 long-lived stream, or if a new stream were attached to it before
25089 Tor could notice that it was old and no longer in use). Bugfix on
25090 0.1.1.15-rc; fixes bug 3375.
25093 - Fix a bug when using ControlSocketsGroupWritable with User. The
25094 directory's group would be checked against the current group, not
25095 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
25096 bugfix on 0.2.2.26-beta.
25097 - Make connection_printf_to_buf()'s behavior sane. Its callers
25098 expect it to emit a CRLF iff the format string ends with CRLF;
25099 it actually emitted a CRLF iff (a) the format string ended with
25100 CRLF or (b) the resulting string was over 1023 characters long or
25101 (c) the format string did not end with CRLF *and* the resulting
25102 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
25103 fixes part of bug 3407.
25104 - Make send_control_event_impl()'s behavior sane. Its callers
25105 expect it to always emit a CRLF at the end of the string; it
25106 might have emitted extra control characters as well. Bugfix on
25107 0.1.1.9-alpha; fixes another part of bug 3407.
25108 - Make crypto_rand_int() check the value of its input correctly.
25109 Previously, it accepted values up to UINT_MAX, but could return a
25110 negative number if given a value above INT_MAX+1. Found by George
25111 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
25112 - Avoid a segfault when reading a malformed circuit build state
25113 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
25115 - When asked about a DNS record type we don't support via a
25116 client DNSPort, reply with NOTIMPL rather than an empty
25117 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
25118 - Fix a rare memory leak during stats writing. Found by coverity.
25121 - Update to the June 1 2011 Maxmind GeoLite Country database.
25123 o Code simplifications and refactoring:
25124 - Remove some dead code as indicated by coverity.
25125 - Remove a few dead assignments during router parsing. Found by
25127 - Add some forgotten return value checks during unit tests. Found
25129 - Don't use 1-bit wide signed bit fields. Found by coverity.
25132 Changes in version 0.2.2.28-beta - 2011-06-04
25133 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
25134 fixed a big bug in whether relays stay in the consensus consistently,
25135 we moved closer to handling bridges and hidden services correctly,
25136 and we started the process of better handling the dreaded "my Vidalia
25137 died, and now my Tor demands a password when I try to reconnect to it"
25141 - Don't decide to make a new descriptor when receiving a HUP signal.
25142 This bug has caused a lot of 0.2.2.x relays to disappear from the
25143 consensus periodically. Fixes the most common case of triggering
25144 bug 1810; bugfix on 0.2.2.7-alpha.
25145 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
25146 - Don't try to build descriptors if "ORPort auto" is set and we
25147 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
25149 - Resolve a crash that occurred when setting BridgeRelay to 1 with
25150 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
25151 - Apply circuit timeouts to opened hidden-service-related circuits
25152 based on the correct start time. Previously, we would apply the
25153 circuit build timeout based on time since the circuit's creation;
25154 it was supposed to be applied based on time since the circuit
25155 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
25156 - Use the same circuit timeout for client-side introduction
25157 circuits as for other four-hop circuits, rather than the timeout
25158 for single-hop directory-fetch circuits; the shorter timeout may
25159 have been appropriate with the static circuit build timeout in
25160 0.2.1.x and earlier, but caused many hidden service access attempts
25161 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
25162 on 0.2.2.2-alpha; fixes another part of bug 1297.
25163 - In ticket 2511 we fixed a case where you could use an unconfigured
25164 bridge if you had configured it as a bridge the last time you ran
25165 Tor. Now fix another edge case: if you had configured it as a bridge
25166 but then switched to a different bridge via the controller, you
25167 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
25171 - Add an __OwningControllerProcess configuration option and a
25172 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
25173 that when it exits, Tor will shut down. Implements feature 3049.
25174 - If "UseBridges 1" is set and no bridges are configured, Tor will
25175 now refuse to build any circuits until some bridges are set.
25176 If "UseBridges auto" is set, Tor will use bridges if they are
25177 configured and we are not running as a server, but otherwise will
25178 make circuits as usual. The new default is "auto". Patch by anonym,
25179 so the Tails LiveCD can stop automatically revealing you as a Tor
25183 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
25184 - Remove a trailing asterisk from "exit-policy/default" in the
25185 output of the control port command "GETINFO info/names". Bugfix
25187 - Use a wide type to hold sockets when built for 64-bit Windows builds.
25189 - Warn when the user configures two HiddenServiceDir lines that point
25190 to the same directory. Bugfix on 0.0.6 (the version introducing
25191 HiddenServiceDir); fixes bug 3289.
25192 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
25193 part of bug 2748; bugfix on 0.2.0.10-alpha.
25194 - Log malformed requests for rendezvous descriptors as protocol
25195 warnings, not warnings. Also, use a more informative log message
25196 in case someone sees it at log level warning without prior
25197 info-level messages. Fixes the other part of bug 2748; bugfix
25199 - Clear the table recording the time of the last request for each
25200 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
25201 Previously, we would clear our HS descriptor cache on SIGNAL
25202 NEWNYM, but if we had previously retrieved a descriptor (or tried
25203 to) from every directory responsible for it, we would refuse to
25204 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
25206 - Fix a log message that said "bits" while displaying a value in
25207 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
25209 - When checking for 1024-bit keys, check for 1024 bits, not 128
25210 bytes. This allows Tor to correctly discard keys of length 1017
25211 through 1023. Bugfix on 0.0.9pre5.
25214 - Relays now log the reason for publishing a new relay descriptor,
25215 so we have a better chance of hunting down instances of bug 1810.
25216 Resolves ticket 3252.
25217 - Revise most log messages that refer to nodes by nickname to
25218 instead use the "$key=nickname at address" format. This should be
25219 more useful, especially since nicknames are less and less likely
25220 to be unique. Resolves ticket 3045.
25221 - Log (at info level) when purging pieces of hidden-service-client
25222 state because of SIGNAL NEWNYM.
25225 - Remove undocumented option "-F" from tor-resolve: it hasn't done
25226 anything since 0.2.1.16-rc.
25229 Changes in version 0.2.2.27-beta - 2011-05-18
25230 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
25231 release, and also adds a few more general bugfixes.
25234 - Fix a crash bug when changing bridges in a running Tor process.
25235 Fixes bug 3213; bugfix on 0.2.2.26-beta.
25236 - When the controller configures a new bridge, don't wait 10 to 60
25237 seconds before trying to fetch its descriptor. Bugfix on
25238 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
25241 - Require that onion keys have exponent 65537 in microdescriptors too.
25242 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
25243 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
25244 Changed the limit to 512 characters by removing base64 newlines.
25245 Fixes bug 2752. Fix by Michael Yakubovich.
25246 - When a client starts or stops using bridges, never use a circuit
25247 that was built before the configuration change. This behavior could
25248 put at risk a user who uses bridges to ensure that her traffic
25249 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
25253 Changes in version 0.2.2.26-beta - 2011-05-17
25254 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
25255 also introduces a new "socksport auto" approach that should make it
25256 easier to run multiple Tors on the same system, and does a lot of
25257 cleanup to get us closer to a release candidate.
25259 o Security/privacy fixes:
25260 - Replace all potentially sensitive memory comparison operations
25261 with versions whose runtime does not depend on the data being
25262 compared. This will help resist a class of attacks where an
25263 adversary can use variations in timing information to learn
25264 sensitive data. Fix for one case of bug 3122. (Safe memcmp
25265 implementation by Robert Ransom based partially on code by DJB.)
25266 - When receiving a hidden service descriptor, check that it is for
25267 the hidden service we wanted. Previously, Tor would store any
25268 hidden service descriptors that a directory gave it, whether it
25269 wanted them or not. This wouldn't have let an attacker impersonate
25270 a hidden service, but it did let directories pre-seed a client
25271 with descriptors that it didn't want. Bugfix on 0.0.6.
25272 - On SIGHUP, do not clear out all TrackHostExits mappings, client
25273 DNS cache entries, and virtual address mappings: that's what
25274 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
25277 - The options SocksPort, ControlPort, and so on now all accept a
25278 value "auto" that opens a socket on an OS-selected port. A
25279 new ControlPortWriteToFile option tells Tor to write its
25280 actual control port or ports to a chosen file. If the option
25281 ControlPortFileGroupReadable is set, the file is created as
25282 group-readable. Now users can run two Tor clients on the same
25283 system without needing to manually mess with parameters. Resolves
25284 part of ticket 3076.
25285 - Set SO_REUSEADDR on all sockets, not just listeners. This should
25286 help busy exit nodes avoid running out of useable ports just
25287 because all the ports have been used in the near past. Resolves
25291 - New "GETINFO net/listeners/(type)" controller command to return
25292 a list of addresses and ports that are bound for listeners for a
25293 given connection type. This is useful when the user has configured
25294 "SocksPort auto" and the controller needs to know which port got
25295 chosen. Resolves another part of ticket 3076.
25296 - Add a new ControlSocketsGroupWritable configuration option: when
25297 it is turned on, ControlSockets are group-writeable by the default
25298 group of the current user. Patch by Jérémy Bobbio; implements
25300 - Tor now refuses to create a ControlSocket in a directory that is
25301 world-readable (or group-readable if ControlSocketsGroupWritable
25302 is 0). This is necessary because some operating systems do not
25303 enforce permissions on an AF_UNIX sockets. Permissions on the
25304 directory holding the socket, however, seems to work everywhere.
25305 - Rate-limit a warning about failures to download v2 networkstatus
25306 documents. Resolves part of bug 1352.
25307 - Backport code from 0.2.3.x that allows directory authorities to
25308 clean their microdescriptor caches. Needed to resolve bug 2230.
25309 - When an HTTPS proxy reports "403 Forbidden", we now explain
25310 what it means rather than calling it an unexpected status code.
25311 Closes bug 2503. Patch from Michael Yakubovich.
25312 - Update to the May 1 2011 Maxmind GeoLite Country database.
25315 - Authorities now clean their microdesc cache periodically and when
25316 reading from disk initially, not only when adding new descriptors.
25317 This prevents a bug where we could lose microdescriptors. Bugfix
25318 on 0.2.2.6-alpha. Fixes bug 2230.
25319 - Do not crash when our configuration file becomes unreadable, for
25320 example due to a permissions change, between when we start up
25321 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
25323 - Avoid a bug that would keep us from replacing a microdescriptor
25324 cache on Windows. (We would try to replace the file while still
25325 holding it open. That's fine on Unix, but Windows doesn't let us
25326 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
25327 - Add missing explanations for the authority-related torrc options
25328 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
25329 man page. Resolves issue 2379.
25330 - As an authority, do not upload our own vote or signature set to
25331 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
25332 it would get flagged as a duplicate. Resolves bug 3026.
25333 - Accept hidden service descriptors if we think we might be a hidden
25334 service directory, regardless of what our consensus says. This
25335 helps robustness, since clients and hidden services can sometimes
25336 have a more up-to-date view of the network consensus than we do,
25337 and if they think that the directory authorities list us a HSDir,
25338 we might actually be one. Related to bug 2732; bugfix on
25340 - When a controller changes TrackHostExits, remove mappings for
25341 hosts that should no longer have their exits tracked. Bugfix on
25343 - When a controller changes VirtualAddrNetwork, remove any mappings
25344 for hosts that were automapped to the old network. Bugfix on
25346 - When a controller changes one of the AutomapHosts* options, remove
25347 any mappings for hosts that should no longer be automapped. Bugfix
25349 - Do not reset the bridge descriptor download status every time we
25350 re-parse our configuration or get a configuration change. Fixes
25351 bug 3019; bugfix on 0.2.0.3-alpha.
25353 o Minor bugfixes (code cleanup):
25354 - When loading the microdesc journal, remember its current size.
25355 In 0.2.2, this helps prevent the microdesc journal from growing
25356 without limit on authorities (who are the only ones to use it in
25357 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
25358 Fix posted by "cypherpunks."
25359 - The microdesc journal is supposed to get rebuilt only if it is
25360 at least _half_ the length of the store, not _twice_ the length
25361 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
25362 - Fix a potential null-pointer dereference while computing a
25363 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
25365 - Avoid a possible null-pointer dereference when rebuilding the mdesc
25366 cache without actually having any descriptors to cache. Bugfix on
25367 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
25368 - If we fail to compute the identity digest of a v3 legacy keypair,
25369 warn, and don't use a buffer-full of junk instead. Bugfix on
25370 0.2.1.1-alpha; fixes bug 3106.
25371 - Resolve an untriggerable issue in smartlist_string_num_isin(),
25372 where if the function had ever in the future been used to check
25373 for the presence of a too-large number, it would have given an
25374 incorrect result. (Fortunately, we only used it for 16-bit
25375 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
25376 - Require that introduction point keys and onion handshake keys
25377 have a public exponent of 65537. Starts to fix bug 3207; bugfix
25380 o Removed features:
25381 - Caches no longer download and serve v2 networkstatus documents
25382 unless FetchV2Networkstatus flag is set: these documents haven't
25383 haven't been used by clients or relays since 0.2.0.x. Resolves
25387 Changes in version 0.2.3.1-alpha - 2011-05-05
25388 Tor 0.2.3.1-alpha adds some new experimental features, including support
25389 for an improved network IO backend, IOCP networking on Windows,
25390 microdescriptor caching, "fast-start" support for streams, and automatic
25391 home router configuration. There are also numerous internal improvements
25392 to try to make the code easier for developers to work with.
25394 This is the first alpha release in a new series, so expect there to be
25395 bugs. Users who would rather test out a more stable branch should
25396 stay with 0.2.2.x for now.
25399 - Tor can now optionally build with the "bufferevents" buffered IO
25400 backend provided by Libevent 2. To use this feature, make sure you
25401 have the latest possible version of Libevent, and pass the
25402 --enable-bufferevents flag to configure when building Tor from
25403 source. This feature will make our networking code more flexible,
25404 let us stack layers on each other, and let us use more efficient
25405 zero-copy transports where available.
25406 - As an experimental feature, Tor can use IOCP for networking on Windows.
25407 Once this code is tuned and optimized, it promises much better
25408 performance than the select-based backend we've used in the past. To
25409 try this feature, you must build Tor with Libevent 2, configure Tor
25410 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
25411 your torrc. There are known bugs here: only try this if you can help
25412 debug it as it breaks.
25413 - The EntryNodes option can now include country codes like {de} or IP
25414 addresses or network masks. Previously we had disallowed these options
25415 because we didn't have an efficient way to keep the list up to
25416 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
25417 - Exit nodes now accept and queue data on not-yet-connected streams.
25418 Previously, the client wasn't allowed to send data until the stream was
25419 connected, which slowed down all connections. This change will enable
25420 clients to perform a "fast-start" on streams and send data without
25421 having to wait for a confirmation that the stream has opened. (Patch
25422 from Ian Goldberg; implements the server side of Proposal 174.)
25423 - Tor now has initial support for automatic port mapping on the many
25424 home routers that support NAT-PMP or UPnP. (Not yet supported on
25425 Windows). To build the support code, you'll need to have libnatpnp
25426 library and/or the libminiupnpc library, and you'll need to enable the
25427 feature specifically by passing "--enable-upnp" and/or
25428 "--enable-natpnp" to configure. To turn it on, use the new
25429 PortForwarding option.
25430 - Caches now download, cache, and serve multiple "flavors" of the
25431 consensus, including a flavor that describes microdescriptors.
25432 - Caches now download, cache, and serve microdescriptors -- small
25433 summaries of router descriptors that are authenticated by all of the
25434 directory authorities. Once enough caches are running this code,
25435 clients will be able to save significant amounts of directory bandwidth
25436 by downloading microdescriptors instead of router descriptors.
25439 - Make logging resolution configurable with a new LogTimeGranularity
25440 option, and change the default from 1 millisecond to 1 second.
25441 Implements enhancement 1668.
25442 - We log which torrc file we're using on startup. Implements ticket
25444 - Ordinarily, Tor does not count traffic from private addresses (like
25445 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
25446 There is now a new option, CountPrivateBandwidth, to disable this
25447 behavior. Patch from Daniel Cagara.
25448 - New --enable-static-tor configure option for building Tor as
25449 statically as possible. Idea, general hackery and thoughts from
25450 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
25452 - If you set the NumCPUs option to 0, Tor will now try to detect how
25453 many CPUs you have. This is the new default behavior.
25454 - Turn on directory request statistics by default and include them in
25455 extra-info descriptors. Don't break if we have no GeoIP database.
25456 - Relays that set "ConnDirectionStatistics 1" write statistics on the
25457 bidirectional use of connections to disk every 24 hours.
25458 - Add a GeoIP file digest to the extra-info descriptor. Implements
25460 - The NodeFamily option -- which let you declare that you want to
25461 consider nodes to be part of a family whether they list themselves
25462 that way or not -- now allows IP address ranges and country codes.
25463 - Add a new 'Heartbeat' log message type to periodically log a message
25464 describing Tor's status at level Notice. This feature is meant for
25465 operators who log at notice, and want to make sure that their Tor
25466 server is still working. Implementation by George Kadianakis.
25468 o Minor bugfixes (on 0.2.2.25-alpha):
25469 - When loading the microdesc journal, remember its current size.
25470 In 0.2.2, this helps prevent the microdesc journal from growing
25471 without limit on authorities (who are the only ones to use it in
25472 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
25473 Fix posted by "cypherpunks."
25474 - The microdesc journal is supposed to get rebuilt only if it is
25475 at least _half_ the length of the store, not _twice_ the length
25476 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
25477 - If as an authority we fail to compute the identity digest of a v3
25478 legacy keypair, warn, and don't use a buffer-full of junk instead.
25479 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
25480 - Authorities now clean their microdesc cache periodically and when
25481 reading from disk initially, not only when adding new descriptors.
25482 This prevents a bug where we could lose microdescriptors. Bugfix
25485 o Minor features (controller):
25486 - Add a new SIGNAL event to the controller interface so that
25487 controllers can be notified when Tor handles a signal. Resolves
25488 issue 1955. Patch by John Brooks.
25489 - Add a new GETINFO option to get total bytes read and written. Patch
25490 from pipe, revised by atagar. Resolves ticket 2345.
25491 - Implement some GETINFO controller fields to provide information about
25492 the Tor process's pid, euid, username, and resource limits.
25495 - Our build system requires automake 1.6 or later to create the
25496 Makefile.in files. Previously, you could have used 1.4.
25497 This only affects developers and people building Tor from git;
25498 people who build Tor from the source distribution without changing
25499 the Makefile.am files should be fine.
25500 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
25501 so on. This is more robust against some of the failure modes
25502 associated with running the autotools pieces on their own.
25504 o Minor packaging issues:
25505 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
25506 already created. Patch from Andreas Stieger. Fixes bug 2573.
25508 o Code simplifications and refactoring:
25509 - A major revision to our internal node-selecting and listing logic.
25510 Tor already had at least two major ways to look at the question of
25511 "which Tor servers do we know about": a list of router descriptors,
25512 and a list of entries in the current consensus. With
25513 microdescriptors, we're adding a third. Having so many systems
25514 without an abstraction layer over them was hurting the codebase.
25515 Now, we have a new "node_t" abstraction that presents a consistent
25516 interface to a client's view of a Tor node, and holds (nearly) all
25517 of the mutable state formerly in routerinfo_t and routerstatus_t.
25518 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
25519 no longer link against Libevent: they never used it, but
25520 our library structure used to force them to link it.
25522 o Removed features:
25523 - Remove some old code to work around even older versions of Tor that
25524 used forked processes to handle DNS requests. Such versions of Tor
25525 are no longer in use as servers.
25527 o Documentation fixes:
25528 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
25529 - Add missing documentation for the authority-related torrc options
25530 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
25534 Changes in version 0.2.2.25-alpha - 2011-04-29
25535 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
25536 robust, routers no longer overreport their bandwidth, Win7 should crash
25537 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
25538 now prevents hidden service-related activity from being linkable. It
25539 provides more information to Vidalia so you can see if your bridge is
25540 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
25541 StrictNodes configuration options to make them more reliable, more
25542 understandable, and more regularly applied. If you use those options,
25543 please see the revised documentation for them in the manual page.
25546 - Relays were publishing grossly inflated bandwidth values because
25547 they were writing their state files wrong--now they write the
25548 correct value. Also, resume reading bandwidth history from the
25549 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
25550 - Improve hidden service robustness: When we find that we have
25551 extended a hidden service's introduction circuit to a relay not
25552 listed as an introduction point in the HS descriptor we currently
25553 have, retry with an introduction point from the current
25554 descriptor. Previously we would just give up. Fixes bugs 1024 and
25555 1930; bugfix on 0.2.0.10-alpha.
25556 - Clients now stop trying to use an exit node associated with a given
25557 destination by TrackHostExits if they fail to reach that exit node.
25558 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
25559 - Fix crash bug on platforms where gmtime and localtime can return
25560 NULL. Windows 7 users were running into this one. Fixes part of bug
25561 2077. Bugfix on all versions of Tor. Found by boboper.
25563 o Security and stability fixes:
25564 - Don't double-free a parsable, but invalid, microdescriptor, even if
25565 it is followed in the blob we're parsing by an unparsable
25566 microdescriptor. Fixes an issue reported in a comment on bug 2954.
25567 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
25568 - If the Nickname configuration option isn't given, Tor would pick a
25569 nickname based on the local hostname as the nickname for a relay.
25570 Because nicknames are not very important in today's Tor and the
25571 "Unnamed" nickname has been implemented, this is now problematic
25572 behavior: It leaks information about the hostname without being
25573 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
25574 introduced the Unnamed nickname. Reported by tagnaq.
25575 - Fix an uncommon assertion failure when running with DNSPort under
25576 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
25577 - Avoid linkability based on cached hidden service descriptors: forget
25578 all hidden service descriptors cached as a client when processing a
25579 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
25582 - Export GeoIP information on bridge usage to controllers even if we
25583 have not yet been running for 24 hours. Now Vidalia bridge operators
25584 can get more accurate and immediate feedback about their
25585 contributions to the network.
25587 o Major features and bugfixes (node selection):
25588 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
25589 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
25590 options. Previously, we had been ambiguous in describing what
25591 counted as an "exit" node, and what operations exactly "StrictNodes
25592 0" would permit. This created confusion when people saw nodes built
25593 through unexpected circuits, and made it hard to tell real bugs from
25594 surprises. Now the intended behavior is:
25595 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
25596 a node that delivers user traffic outside the Tor network.
25597 . "Entry", in the context of EntryNodes, means a node used as the
25598 first hop of a multihop circuit. It doesn't include direct
25599 connections to directory servers.
25600 . "ExcludeNodes" applies to all nodes.
25601 . "StrictNodes" changes the behavior of ExcludeNodes only. When
25602 StrictNodes is set, Tor should avoid all nodes listed in
25603 ExcludeNodes, even when it will make user requests fail. When
25604 StrictNodes is *not* set, then Tor should follow ExcludeNodes
25605 whenever it can, except when it must use an excluded node to
25606 perform self-tests, connect to a hidden service, provide a
25607 hidden service, fulfill a .exit request, upload directory
25608 information, or fetch directory information.
25609 Collectively, the changes to implement the behavior fix bug 1090.
25610 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
25611 a node is listed in both, it's treated as excluded.
25612 - ExcludeNodes now applies to directory nodes -- as a preference if
25613 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
25614 Don't exclude all the directory authorities and set StrictNodes to 1
25615 unless you really want your Tor to break.
25616 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
25617 - ExcludeExitNodes now overrides .exit requests.
25618 - We don't use bridges listed in ExcludeNodes.
25619 - When StrictNodes is 1:
25620 . We now apply ExcludeNodes to hidden service introduction points
25621 and to rendezvous points selected by hidden service users. This
25622 can make your hidden service less reliable: use it with caution!
25623 . If we have used ExcludeNodes on ourself, do not try relay
25624 reachability self-tests.
25625 . If we have excluded all the directory authorities, we will not
25626 even try to upload our descriptor if we're a relay.
25627 . Do not honor .exit requests to an excluded node.
25628 - Remove a misfeature that caused us to ignore the Fast/Stable flags
25629 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
25630 - When the set of permitted nodes changes, we now remove any mappings
25631 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
25633 - We never cannibalize a circuit that had excluded nodes on it, even
25634 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
25635 - Revert a change where we would be laxer about attaching streams to
25636 circuits than when building the circuits. This was meant to prevent
25637 a set of bugs where streams were never attachable, but our improved
25638 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
25639 - Keep track of how many times we launch a new circuit to handle a
25640 given stream. Too many launches could indicate an inconsistency
25641 between our "launch a circuit to handle this stream" logic and our
25642 "attach this stream to one of the available circuits" logic.
25643 - Improve log messages related to excluded nodes.
25646 - Fix a spurious warning when moving from a short month to a long
25647 month on relays with month-based BandwidthAccounting. Bugfix on
25648 0.2.2.17-alpha; fixes bug 3020.
25649 - When a client finds that an origin circuit has run out of 16-bit
25650 stream IDs, we now mark it as unusable for new streams. Previously,
25651 we would try to close the entire circuit. Bugfix on 0.0.6.
25652 - Add a forgotten cast that caused a compile warning on OS X 10.6.
25653 Bugfix on 0.2.2.24-alpha.
25654 - Be more careful about reporting the correct error from a failed
25655 connect() system call. Under some circumstances, it was possible to
25656 look at an incorrect value for errno when sending the end reason.
25657 Bugfix on 0.1.0.1-rc.
25658 - Correctly handle an "impossible" overflow cases in connection byte
25659 counting, where we write or read more than 4GB on an edge connection
25660 in a single second. Bugfix on 0.1.2.8-beta.
25661 - Correct the warning displayed when a rendezvous descriptor exceeds
25662 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
25664 - Clients and hidden services now use HSDir-flagged relays for hidden
25665 service descriptor downloads and uploads even if the relays have no
25666 DirPort set and the client has disabled TunnelDirConns. This will
25667 eventually allow us to give the HSDir flag to relays with no
25668 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
25669 - Downgrade "no current certificates known for authority" message from
25670 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
25671 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
25672 2917. Bugfix on 0.1.1.1-alpha.
25673 - Only limit the lengths of single HS descriptors, even when multiple
25674 HS descriptors are published to an HSDir relay in a single POST
25675 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
25676 - Write the current time into the LastWritten line in our state file,
25677 rather than the time from the previous write attempt. Also, stop
25678 trying to use a time of -1 in our log statements. Fixes bug 3039;
25679 bugfix on 0.2.2.14-alpha.
25680 - Be more consistent in our treatment of file system paths. "~" should
25681 get expanded to the user's home directory in the Log config option.
25682 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
25683 feature for the -f and --DataDirectory options.
25686 - Make sure every relay writes a state file at least every 12 hours.
25687 Previously, a relay could go for weeks without writing its state
25688 file, and on a crash could lose its bandwidth history, capacity
25689 estimates, client country statistics, and so on. Addresses bug 3012.
25690 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
25691 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
25692 clients are already deprecated because of security bugs.
25693 - Don't allow v0 hidden service authorities to act as clients.
25694 Required by fix for bug 3000.
25695 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
25696 by fix for bug 3000.
25697 - Ensure that no empty [dirreq-](read|write)-history lines are added
25698 to an extrainfo document. Implements ticket 2497.
25700 o Code simplification and refactoring:
25701 - Remove workaround code to handle directory responses from servers
25702 that had bug 539 (they would send HTTP status 503 responses _and_
25703 send a body too). Since only server versions before
25704 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
25705 keep the workaround in place.
25706 - Remove the old 'fuzzy time' logic. It was supposed to be used for
25707 handling calculations where we have a known amount of clock skew and
25708 an allowed amount of unknown skew. But we only used it in three
25709 places, and we never adjusted the known/unknown skew values. This is
25710 still something we might want to do someday, but if we do, we'll
25711 want to do it differently.
25712 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
25713 None of the cases where we did this before were wrong, but by making
25714 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
25715 - Use GetTempDir to find the proper temporary directory location on
25716 Windows when generating temporary files for the unit tests. Patch by
25720 Changes in version 0.2.2.24-alpha - 2011-04-08
25721 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
25722 prevented Tor clients from effectively using "multihomed" bridges,
25723 that is, bridges that listen on multiple ports or IP addresses so users
25724 can continue to use some of their addresses even if others get blocked.
25727 - Fix a bug where bridge users who configure the non-canonical
25728 address of a bridge automatically switch to its canonical
25729 address. If a bridge listens at more than one address, it should be
25730 able to advertise those addresses independently and any non-blocked
25731 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
25733 - If you configured Tor to use bridge A, and then quit and
25734 configured Tor to use bridge B instead, it would happily continue
25735 to use bridge A if it's still reachable. While this behavior is
25736 a feature if your goal is connectivity, in some scenarios it's a
25737 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
25738 - Directory authorities now use data collected from their own
25739 uptime observations when choosing whether to assign the HSDir flag
25740 to relays, instead of trusting the uptime value the relay reports in
25741 its descriptor. This change helps prevent an attack where a small
25742 set of nodes with frequently-changing identity keys can blackhole
25743 a hidden service. (Only authorities need upgrade; others will be
25744 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
25747 - When we restart our relay, we might get a successful connection
25748 from the outside before we've started our reachability tests,
25749 triggering a warning: "ORPort found reachable, but I have no
25750 routerinfo yet. Failing to inform controller of success." This
25751 bug was harmless unless Tor is running under a controller
25752 like Vidalia, in which case the controller would never get a
25753 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
25755 - Make directory authorities more accurate at recording when
25756 relays that have failed several reachability tests became
25757 unreachable, so we can provide more accuracy at assigning Stable,
25758 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
25759 - Fix an issue that prevented static linking of libevent on
25760 some platforms (notably Linux). Fixes bug 2698; bugfix on
25761 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
25762 the --with-static-libevent configure option).
25763 - We now ask the other side of a stream (the client or the exit)
25764 for more data on that stream when the amount of queued data on
25765 that stream dips low enough. Previously, we wouldn't ask the
25766 other side for more data until either it sent us more data (which
25767 it wasn't supposed to do if it had exhausted its window!) or we
25768 had completely flushed all our queued data. This flow control fix
25769 should improve throughput. Fixes bug 2756; bugfix on the earliest
25770 released versions of Tor (svn commit r152).
25771 - Avoid a double-mark-for-free warning when failing to attach a
25772 transparent proxy connection. (We thought we had fixed this in
25773 0.2.2.23-alpha, but it turns out our fix was checking the wrong
25774 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
25775 bug) and 0.2.2.23-alpha (the incorrect fix).
25776 - When warning about missing zlib development packages during compile,
25777 give the correct package names. Bugfix on 0.2.0.1-alpha.
25780 - Directory authorities now log the source of a rejected POSTed v3
25781 networkstatus vote.
25782 - Make compilation with clang possible when using
25783 --enable-gcc-warnings by removing two warning options that clang
25784 hasn't implemented yet and by fixing a few warnings. Implements
25786 - When expiring circuits, use microsecond timers rather than
25787 one-second timers. This can avoid an unpleasant situation where a
25788 circuit is launched near the end of one second and expired right
25789 near the beginning of the next, and prevent fluctuations in circuit
25791 - Use computed circuit-build timeouts to decide when to launch
25792 parallel introduction circuits for hidden services. (Previously,
25793 we would retry after 15 seconds.)
25794 - Update to the April 1 2011 Maxmind GeoLite Country database.
25797 - Create the /var/run/tor directory on startup on OpenSUSE if it is
25798 not already created. Patch from Andreas Stieger. Fixes bug 2573.
25800 o Documentation changes:
25801 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
25802 - Resolve all doxygen warnings except those for missing documentation.
25804 - Add doxygen documentation for more functions, fields, and types.
25807 Changes in version 0.2.2.23-alpha - 2011-03-08
25808 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
25809 they restart they don't lose their bandwidth capacity estimate. This
25810 release also fixes a diverse set of user-facing bugs, ranging from
25811 relays overrunning their rate limiting to clients falsely warning about
25812 clock skew to bridge descriptor leaks by our bridge directory authority.
25815 - Stop sending a CLOCK_SKEW controller status event whenever
25816 we fetch directory information from a relay that has a wrong clock.
25817 Instead, only inform the controller when it's a trusted authority
25818 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
25819 the rest of bug 1074.
25820 - Fix an assert in parsing router descriptors containing IPv6
25821 addresses. This one took down the directory authorities when
25822 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
25823 - Make the bridge directory authority refuse to answer directory
25824 requests for "all" descriptors. It used to include bridge
25825 descriptors in its answer, which was a major information leak.
25826 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
25827 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
25828 Tor would ignore their RelayBandwidthBurst setting,
25829 potentially using more bandwidth than expected. Bugfix on
25830 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
25831 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
25832 hidserv" in her torrc. The 'hidserv' argument never controlled
25833 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
25836 - Relays now save observed peak bandwidth throughput rates to their
25837 state file (along with total usage, which was already saved)
25838 so that they can determine their correct estimated bandwidth on
25839 restart. Resolves bug 1863, where Tor relays would reset their
25840 estimated bandwidth to 0 after restarting.
25841 - Directory authorities now take changes in router IP address and
25842 ORPort into account when determining router stability. Previously,
25843 if a router changed its IP or ORPort, the authorities would not
25844 treat it as having any downtime for the purposes of stability
25845 calculation, whereas clients would experience downtime since the
25846 change could take a while to propagate to them. Resolves issue 1035.
25847 - Enable Address Space Layout Randomization (ASLR) and Data Execution
25848 Prevention (DEP) by default on Windows to make it harder for
25849 attackers to exploit vulnerabilities. Patch from John Brooks.
25851 o Minor bugfixes (on 0.2.1.x and earlier):
25852 - Fix a rare crash bug that could occur when a client was configured
25853 with a large number of bridges. Fixes bug 2629; bugfix on
25854 0.2.1.2-alpha. Bugfix by trac user "shitlei".
25855 - Avoid a double mark-for-free warning when failing to attach a
25856 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
25858 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
25859 found by "cypherpunks". This bug was introduced before the first
25860 Tor release, in svn commit r110.
25861 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
25862 don't mention them in the manpage. Fixes bug 2450; issue
25863 spotted by keb and G-Lo.
25864 - Fix a bug in bandwidth history state parsing that could have been
25865 triggered if a future version of Tor ever changed the timing
25866 granularity at which bandwidth history is measured. Bugfix on
25867 Tor 0.1.1.11-alpha.
25868 - When a relay decides that its DNS is too broken for it to serve
25869 as an exit server, it advertised itself as a non-exit, but
25870 continued to act as an exit. This could create accidental
25871 partitioning opportunities for users. Instead, if a relay is
25872 going to advertise reject *:* as its exit policy, it should
25873 really act with exit policy "reject *:*". Fixes bug 2366.
25874 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
25875 - In the special case where you configure a public exit relay as your
25876 bridge, Tor would be willing to use that exit relay as the last
25877 hop in your circuit as well. Now we fail that circuit instead.
25878 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
25879 - Fix a bug with our locking implementation on Windows that couldn't
25880 correctly detect when a file was already locked. Fixes bug 2504,
25881 bugfix on 0.2.1.6-alpha.
25882 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
25883 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
25885 - Set target port in get_interface_address6() correctly. Bugfix
25886 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
25887 - Directory authorities are now more robust to hops back in time
25888 when calculating router stability. Previously, if a run of uptime
25889 or downtime appeared to be negative, the calculation could give
25890 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
25892 - Fix an assert that got triggered when using the TestingTorNetwork
25893 configuration option and then issuing a GETINFO config-text control
25894 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
25896 o Minor bugfixes (on 0.2.2.x):
25897 - Clients should not weight BadExit nodes as Exits in their node
25898 selection. Similarly, directory authorities should not count BadExit
25899 bandwidth as Exit bandwidth when computing bandwidth-weights.
25900 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
25901 - Correctly clear our dir_read/dir_write history when there is an
25902 error parsing any bw history value from the state file. Bugfix on
25903 Tor 0.2.2.15-alpha.
25904 - Resolve a bug in verifying signatures of directory objects
25905 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
25906 Fixes bug 2409. Found by "piebeer".
25907 - Bridge authorities no longer crash on SIGHUP when they try to
25908 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
25912 - Log less aggressively about circuit timeout changes, and improve
25913 some other circuit timeout messages. Resolves bug 2004.
25914 - Log a little more clearly about the times at which we're no longer
25915 accepting new connections. Resolves bug 2181.
25916 - Reject attempts at the client side to open connections to private
25917 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
25918 a randomly chosen exit node. Attempts to do so are always
25919 ill-defined, generally prevented by exit policies, and usually
25920 in error. This will also help to detect loops in transparent
25921 proxy configurations. You can disable this feature by setting
25922 "ClientRejectInternalAddresses 0" in your torrc.
25923 - Always treat failure to allocate an RSA key as an unrecoverable
25925 - Update to the March 1 2011 Maxmind GeoLite Country database.
25927 o Minor features (log subsystem):
25928 - Add documentation for configuring logging at different severities in
25929 different log domains. We've had this feature since 0.2.1.1-alpha,
25930 but for some reason it never made it into the manpage. Fixes
25932 - Make it simpler to specify "All log domains except for A and B".
25933 Previously you needed to say "[*,~A,~B]". Now you can just say
25935 - Add a "LogMessageDomains 1" option to include the domains of log
25936 messages along with the messages. Without this, there's no way
25937 to use log domains without reading the source or doing a lot
25940 o Packaging changes:
25941 - Stop shipping the Tor specs files and development proposal documents
25942 in the tarball. They are now in a separate git repository at
25943 git://git.torproject.org/torspec.git
25946 Changes in version 0.2.1.30 - 2011-02-23
25947 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
25948 change is a slight tweak to Tor's TLS handshake that makes relays
25949 and bridges that run this new version reachable from Iran again.
25950 We don't expect this tweak will win the arms race long-term, but it
25951 buys us time until we roll out a better solution.
25954 - Stop sending a CLOCK_SKEW controller status event whenever
25955 we fetch directory information from a relay that has a wrong clock.
25956 Instead, only inform the controller when it's a trusted authority
25957 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
25958 the rest of bug 1074.
25959 - Fix a bounds-checking error that could allow an attacker to
25960 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
25961 Found by "piebeer".
25962 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
25963 Tor would ignore their RelayBandwidthBurst setting,
25964 potentially using more bandwidth than expected. Bugfix on
25965 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
25966 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
25967 hidserv" in her torrc. The 'hidserv' argument never controlled
25968 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
25971 - Adjust our TLS Diffie-Hellman parameters to match those used by
25973 - Update to the February 1 2011 Maxmind GeoLite Country database.
25976 - Check for and reject overly long directory certificates and
25977 directory tokens before they have a chance to hit any assertions.
25978 Bugfix on 0.2.1.28. Found by "doorss".
25979 - Bring the logic that gathers routerinfos and assesses the
25980 acceptability of circuits into line. This prevents a Tor OP from
25981 getting locked in a cycle of choosing its local OR as an exit for a
25982 path (due to a .exit request) and then rejecting the circuit because
25983 its OR is not listed yet. It also prevents Tor clients from using an
25984 OR running in the same instance as an exit (due to a .exit request)
25985 if the OR does not meet the same requirements expected of an OR
25986 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
25988 o Packaging changes:
25989 - Stop shipping the Tor specs files and development proposal documents
25990 in the tarball. They are now in a separate git repository at
25991 git://git.torproject.org/torspec.git
25992 - Do not include Git version tags as though they are SVN tags when
25993 generating a tarball from inside a repository that has switched
25994 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
25997 Changes in version 0.2.2.22-alpha - 2011-01-25
25998 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
25999 main other change is a slight tweak to Tor's TLS handshake that makes
26000 relays and bridges that run this new version reachable from Iran again.
26001 We don't expect this tweak will win the arms race long-term, but it
26002 will buy us a bit more time until we roll out a better solution.
26005 - Fix a bounds-checking error that could allow an attacker to
26006 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
26007 Found by "piebeer".
26008 - Don't assert when changing from bridge to relay or vice versa
26009 via the controller. The assert happened because we didn't properly
26010 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
26011 bug 2433. Reported by bastik.
26014 - Adjust our TLS Diffie-Hellman parameters to match those used by
26016 - Provide a log message stating which geoip file we're parsing
26017 instead of just stating that we're parsing the geoip file.
26018 Implements ticket 2432.
26021 - Check for and reject overly long directory certificates and
26022 directory tokens before they have a chance to hit any assertions.
26023 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
26026 Changes in version 0.2.2.21-alpha - 2011-01-15
26027 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
26028 continues our recent code security audit work. The main fix resolves
26029 a remote heap overflow vulnerability that can allow remote code
26030 execution (CVE-2011-0427). Other fixes address a variety of assert
26031 and crash bugs, most of which we think are hard to exploit remotely.
26033 o Major bugfixes (security), also included in 0.2.1.29:
26034 - Fix a heap overflow bug where an adversary could cause heap
26035 corruption. This bug probably allows remote code execution
26036 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
26038 - Prevent a denial-of-service attack by disallowing any
26039 zlib-compressed data whose compression factor is implausibly
26040 high. Fixes part of bug 2324; reported by "doorss".
26041 - Zero out a few more keys in memory before freeing them. Fixes
26042 bug 2384 and part of bug 2385. These key instances found by
26043 "cypherpunks", based on Andrew Case's report about being able
26044 to find sensitive data in Tor's memory space if you have enough
26045 permissions. Bugfix on 0.0.2pre9.
26047 o Major bugfixes (crashes), also included in 0.2.1.29:
26048 - Prevent calls to Libevent from inside Libevent log handlers.
26049 This had potential to cause a nasty set of crashes, especially
26050 if running Libevent with debug logging enabled, and running
26051 Tor with a controller watching for low-severity log messages.
26052 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
26053 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
26054 underflow errors there too. Fixes the other part of bug 2324.
26055 - Fix a bug where we would assert if we ever had a
26056 cached-descriptors.new file (or another file read directly into
26057 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
26058 on 0.2.1.25. Found by doorss.
26059 - Fix some potential asserts and parsing issues with grossly
26060 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
26063 o Minor bugfixes (other), also included in 0.2.1.29:
26064 - Fix a bug with handling misformed replies to reverse DNS lookup
26065 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
26066 bug reported by doorss.
26067 - Fix compilation on mingw when a pthreads compatibility library
26068 has been installed. (We don't want to use it, so we shouldn't
26069 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
26070 - Fix a bug where we would declare that we had run out of virtual
26071 addresses when the address space was only half-exhausted. Bugfix
26073 - Correctly handle the case where AutomapHostsOnResolve is set but
26074 no virtual addresses are available. Fixes bug 2328; bugfix on
26075 0.1.2.1-alpha. Bug found by doorss.
26076 - Correctly handle wrapping around when we run out of virtual
26077 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
26079 o Minor features, also included in 0.2.1.29:
26080 - Update to the January 1 2011 Maxmind GeoLite Country database.
26081 - Introduce output size checks on all of our decryption functions.
26083 o Build changes, also included in 0.2.1.29:
26084 - Tor does not build packages correctly with Automake 1.6 and earlier;
26085 added a check to Makefile.am to make sure that we're building with
26086 Automake 1.7 or later.
26087 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
26088 because we built it with a too-old version of automake. Thus that
26089 release broke ./configure --enable-openbsd-malloc, which is popular
26090 among really fast exit relays on Linux.
26092 o Major bugfixes, new in 0.2.2.21-alpha:
26093 - Prevent crash/heap corruption when the cbtnummodes consensus
26094 parameter is set to 0 or large values. Fixes bug 2317; bugfix
26097 o Major features, new in 0.2.2.21-alpha:
26098 - Introduce minimum/maximum values that clients will believe
26099 from the consensus. Now we'll have a better chance to avoid crashes
26100 or worse when a consensus param has a weird value.
26102 o Minor features, new in 0.2.2.21-alpha:
26103 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
26104 used on bridges, and it makes bridge scanning somewhat easier.
26105 - If writing the state file to disk fails, wait up to an hour before
26106 retrying again, rather than trying again each second. Fixes bug
26107 2346; bugfix on Tor 0.1.1.3-alpha.
26108 - Make Libevent log messages get delivered to controllers later,
26109 and not from inside the Libevent log handler. This prevents unsafe
26110 reentrant Libevent calls while still letting the log messages
26112 - Detect platforms that brokenly use a signed size_t, and refuse to
26113 build there. Found and analyzed by doorss and rransom.
26114 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
26117 o Minor bugfixes, new in 0.2.2.21-alpha:
26118 - Handle SOCKS messages longer than 128 bytes long correctly, rather
26119 than waiting forever for them to finish. Fixes bug 2330; bugfix
26120 on 0.2.0.16-alpha. Found by doorss.
26121 - Add assertions to check for overflow in arguments to
26122 base32_encode() and base32_decode(); fix a signed-unsigned
26123 comparison there too. These bugs are not actually reachable in Tor,
26124 but it's good to prevent future errors too. Found by doorss.
26125 - Correctly detect failures to create DNS requests when using Libevent
26126 versions before v2. (Before Libevent 2, we used our own evdns
26127 implementation. Its return values for Libevent's evdns_resolve_*()
26128 functions are not consistent with those from Libevent.) Fixes bug
26129 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
26131 o Documentation, new in 0.2.2.21-alpha:
26132 - Document the default socks host and port (127.0.0.1:9050) for
26136 Changes in version 0.2.1.29 - 2011-01-15
26137 Tor 0.2.1.29 continues our recent code security audit work. The main
26138 fix resolves a remote heap overflow vulnerability that can allow remote
26139 code execution. Other fixes address a variety of assert and crash bugs,
26140 most of which we think are hard to exploit remotely.
26142 o Major bugfixes (security):
26143 - Fix a heap overflow bug where an adversary could cause heap
26144 corruption. This bug probably allows remote code execution
26145 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
26147 - Prevent a denial-of-service attack by disallowing any
26148 zlib-compressed data whose compression factor is implausibly
26149 high. Fixes part of bug 2324; reported by "doorss".
26150 - Zero out a few more keys in memory before freeing them. Fixes
26151 bug 2384 and part of bug 2385. These key instances found by
26152 "cypherpunks", based on Andrew Case's report about being able
26153 to find sensitive data in Tor's memory space if you have enough
26154 permissions. Bugfix on 0.0.2pre9.
26156 o Major bugfixes (crashes):
26157 - Prevent calls to Libevent from inside Libevent log handlers.
26158 This had potential to cause a nasty set of crashes, especially
26159 if running Libevent with debug logging enabled, and running
26160 Tor with a controller watching for low-severity log messages.
26161 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
26162 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
26163 underflow errors there too. Fixes the other part of bug 2324.
26164 - Fix a bug where we would assert if we ever had a
26165 cached-descriptors.new file (or another file read directly into
26166 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
26167 on 0.2.1.25. Found by doorss.
26168 - Fix some potential asserts and parsing issues with grossly
26169 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
26172 o Minor bugfixes (other):
26173 - Fix a bug with handling misformed replies to reverse DNS lookup
26174 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
26175 bug reported by doorss.
26176 - Fix compilation on mingw when a pthreads compatibility library
26177 has been installed. (We don't want to use it, so we shouldn't
26178 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
26179 - Fix a bug where we would declare that we had run out of virtual
26180 addresses when the address space was only half-exhausted. Bugfix
26182 - Correctly handle the case where AutomapHostsOnResolve is set but
26183 no virtual addresses are available. Fixes bug 2328; bugfix on
26184 0.1.2.1-alpha. Bug found by doorss.
26185 - Correctly handle wrapping around to when we run out of virtual
26186 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
26187 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
26188 because we built it with a too-old version of automake. Thus that
26189 release broke ./configure --enable-openbsd-malloc, which is popular
26190 among really fast exit relays on Linux.
26193 - Update to the January 1 2011 Maxmind GeoLite Country database.
26194 - Introduce output size checks on all of our decryption functions.
26197 - Tor does not build packages correctly with Automake 1.6 and earlier;
26198 added a check to Makefile.am to make sure that we're building with
26199 Automake 1.7 or later.
26202 Changes in version 0.2.2.20-alpha - 2010-12-17
26203 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
26204 exploitable bugs. We also fix a variety of other significant bugs,
26205 change the IP address for one of our directory authorities, and update
26206 the minimum version that Tor relays must run to join the network.
26209 - Fix a remotely exploitable bug that could be used to crash instances
26210 of Tor remotely by overflowing on the heap. Remote-code execution
26211 hasn't been confirmed, but can't be ruled out. Everyone should
26212 upgrade. Bugfix on the 0.1.1 series and later.
26213 - Fix a bug that could break accounting on 64-bit systems with large
26214 time_t values, making them hibernate for impossibly long intervals.
26215 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
26216 - Fix a logic error in directory_fetches_from_authorities() that
26217 would cause all _non_-exits refusing single-hop-like circuits
26218 to fetch from authorities, when we wanted to have _exits_ fetch
26219 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
26221 - Fix a stream fairness bug that would cause newer streams on a given
26222 circuit to get preference when reading bytes from the origin or
26223 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
26224 introduced before the first Tor release, in svn revision r152.
26226 o Directory authority changes:
26227 - Change IP address and ports for gabelmoo (v3 directory authority).
26230 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
26231 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
26232 - Fix an off-by-one error in calculating some controller command
26233 argument lengths. Fortunately, this mistake is harmless since
26234 the controller code does redundant NUL termination too. Found by
26235 boboper. Bugfix on 0.1.1.1-alpha.
26236 - Do not dereference NULL if a bridge fails to build its
26237 extra-info descriptor. Found by an anonymous commenter on
26238 Trac. Bugfix on 0.2.2.19-alpha.
26241 - Update to the December 1 2010 Maxmind GeoLite Country database.
26242 - Directory authorities now reject relays running any versions of
26243 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
26244 known bugs that keep RELAY_EARLY cells from working on rendezvous
26245 circuits. Followup to fix for bug 2081.
26246 - Directory authorities now reject relays running any version of Tor
26247 older than 0.2.0.26-rc. That version is the earliest that fetches
26248 current directory information correctly. Fixes bug 2156.
26249 - Report only the top 10 ports in exit-port stats in order not to
26250 exceed the maximum extra-info descriptor length of 50 KB. Implements
26254 Changes in version 0.2.1.28 - 2010-12-17
26255 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
26256 exploitable bugs. We also took this opportunity to change the IP address
26257 for one of our directory authorities, and to update the geoip database
26261 - Fix a remotely exploitable bug that could be used to crash instances
26262 of Tor remotely by overflowing on the heap. Remote-code execution
26263 hasn't been confirmed, but can't be ruled out. Everyone should
26264 upgrade. Bugfix on the 0.1.1 series and later.
26266 o Directory authority changes:
26267 - Change IP address and ports for gabelmoo (v3 directory authority).
26270 - Update to the December 1 2010 Maxmind GeoLite Country database.
26273 Changes in version 0.2.1.27 - 2010-11-23
26274 Yet another OpenSSL security patch broke its compatibility with Tor:
26275 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
26276 also took this opportunity to fix several crash bugs, integrate a new
26277 directory authority, and update the bundled GeoIP database.
26280 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
26281 No longer set the tlsext_host_name extension on server SSL objects;
26282 but continue to set it on client SSL objects. Our goal in setting
26283 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
26284 bugfix on 0.2.1.1-alpha.
26285 - Do not log messages to the controller while shrinking buffer
26286 freelists. Doing so would sometimes make the controller connection
26287 try to allocate a buffer chunk, which would mess up the internals
26288 of the freelist and cause an assertion failure. Fixes bug 1125;
26289 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
26290 - Learn our external IP address when we're a relay or bridge, even if
26291 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
26292 where we introduced bridge relays that don't need to publish to
26293 be useful. Fixes bug 2050.
26294 - Do even more to reject (and not just ignore) annotations on
26295 router descriptors received anywhere but from the cache. Previously
26296 we would ignore such annotations at first, but cache them to disk
26297 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
26298 - When you're using bridges and your network goes away and your
26299 bridges get marked as down, recover when you attempt a new socks
26300 connection (if the network is back), rather than waiting up to an
26301 hour to try fetching new descriptors for your bridges. Bugfix on
26302 0.2.0.3-alpha; fixes bug 1981.
26305 - Move to the November 2010 Maxmind GeoLite country db (rather
26306 than the June 2009 ip-to-country GeoIP db) for our statistics that
26307 count how many users relays are seeing from each country. Now we'll
26308 have more accurate data, especially for many African countries.
26310 o New directory authorities:
26311 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
26315 - Fix an assertion failure that could occur in directory caches or
26316 bridge users when using a very short voting interval on a testing
26317 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
26319 - Enforce multiplicity rules when parsing annotations. Bugfix on
26320 0.2.0.8-alpha. Found by piebeer.
26321 - Allow handshaking OR connections to take a full KeepalivePeriod
26322 seconds to handshake. Previously, we would close them after
26323 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
26324 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
26326 - When building with --enable-gcc-warnings on OpenBSD, disable
26327 warnings in system headers. This makes --enable-gcc-warnings
26328 pass on OpenBSD 4.8.
26331 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
26332 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
26333 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
26334 Servers can start sending this code when enough clients recognize
26335 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
26336 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
26337 Patch from mingw-san.
26340 - Remove the old debian/ directory from the main Tor distribution.
26341 The official Tor-for-debian git repository lives at the URL
26342 https://git.torproject.org/debian/tor.git
26343 - Stop shipping the old doc/website/ directory in the tarball. We
26344 changed the website format in late 2010, and what we shipped in
26345 0.2.1.26 really wasn't that useful anyway.
26348 Changes in version 0.2.2.19-alpha - 2010-11-22
26349 Yet another OpenSSL security patch broke its compatibility with Tor:
26350 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
26353 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
26354 No longer set the tlsext_host_name extension on server SSL objects;
26355 but continue to set it on client SSL objects. Our goal in setting
26356 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
26357 bugfix on 0.2.1.1-alpha.
26360 - Try harder not to exceed the maximum length of 50 KB when writing
26361 statistics to extra-info descriptors. This bug was triggered by very
26362 fast relays reporting exit-port, entry, and dirreq statistics.
26363 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
26364 - Publish a router descriptor even if generating an extra-info
26365 descriptor fails. Previously we would not publish a router
26366 descriptor without an extra-info descriptor; this can cause fast
26367 exit relays collecting exit-port statistics to drop from the
26368 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
26371 Changes in version 0.2.2.18-alpha - 2010-11-16
26372 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
26373 us lately, makes unpublished bridge relays able to detect their IP
26374 address, and fixes a wide variety of other bugs to get us much closer
26375 to a stable release.
26378 - Do even more to reject (and not just ignore) annotations on
26379 router descriptors received anywhere but from the cache. Previously
26380 we would ignore such annotations at first, but cache them to disk
26381 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
26382 - Do not log messages to the controller while shrinking buffer
26383 freelists. Doing so would sometimes make the controller connection
26384 try to allocate a buffer chunk, which would mess up the internals
26385 of the freelist and cause an assertion failure. Fixes bug 1125;
26386 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
26387 - Learn our external IP address when we're a relay or bridge, even if
26388 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
26389 where we introduced bridge relays that don't need to publish to
26390 be useful. Fixes bug 2050.
26391 - Maintain separate TLS contexts and certificates for incoming and
26392 outgoing connections in bridge relays. Previously we would use the
26393 same TLS contexts and certs for incoming and outgoing connections.
26394 Bugfix on 0.2.0.3-alpha; addresses bug 988.
26395 - Maintain separate identity keys for incoming and outgoing TLS
26396 contexts in bridge relays. Previously we would use the same
26397 identity keys for incoming and outgoing TLS contexts. Bugfix on
26398 0.2.0.3-alpha; addresses the other half of bug 988.
26399 - Avoid an assertion failure when we as an authority receive a
26400 duplicate upload of a router descriptor that we already have,
26401 but which we previously considered an obsolete descriptor.
26402 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
26403 - Avoid a crash bug triggered by looking at a dangling pointer while
26404 setting the network status consensus. Found by Robert Ransom.
26405 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
26406 - Fix a logic error where servers that _didn't_ act as exits would
26407 try to keep their server lists more aggressively up to date than
26408 exits, when it was supposed to be the other way around. Bugfix
26411 o Minor bugfixes (on Tor 0.2.1.x and earlier):
26412 - When we're trying to guess whether we know our IP address as
26413 a relay, we would log various ways that we failed to guess
26414 our address, but never log that we ended up guessing it
26415 successfully. Now add a log line to help confused and anxious
26416 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
26417 - Bring the logic that gathers routerinfos and assesses the
26418 acceptability of circuits into line. This prevents a Tor OP from
26419 getting locked in a cycle of choosing its local OR as an exit for a
26420 path (due to a .exit request) and then rejecting the circuit because
26421 its OR is not listed yet. It also prevents Tor clients from using an
26422 OR running in the same instance as an exit (due to a .exit request)
26423 if the OR does not meet the same requirements expected of an OR
26424 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
26425 - Correctly describe errors that occur when generating a TLS object.
26426 Previously we would attribute them to a failure while generating a
26427 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
26429 - Enforce multiplicity rules when parsing annotations. Bugfix on
26430 0.2.0.8-alpha. Found by piebeer.
26431 - Fix warnings that newer versions of autoconf produced during
26432 ./autogen.sh. These warnings appear to be harmless in our case,
26433 but they were extremely verbose. Fixes bug 2020.
26435 o Minor bugfixes (on Tor 0.2.2.x):
26436 - Enable protection of small arrays whenever we build with gcc
26437 hardening features, not only when also building with warnings
26438 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
26441 - Make hidden services work better in private Tor networks by not
26442 requiring any uptime to join the hidden service descriptor
26443 DHT. Implements ticket 2088.
26444 - Rate-limit the "your application is giving Tor only an IP address"
26445 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
26446 - When AllowSingleHopExits is set, print a warning to explain to the
26447 relay operator why most clients are avoiding her relay.
26448 - Update to the November 1 2010 Maxmind GeoLite Country database.
26450 o Code simplifications and refactoring:
26451 - When we fixed bug 1038 we had to put in a restriction not to send
26452 RELAY_EARLY cells on rend circuits. This was necessary as long
26453 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
26454 active. Now remove this obsolete check. Resolves bug 2081.
26455 - Some options used different conventions for uppercasing of acronyms
26456 when comparing manpage and source. Fix those in favor of the
26457 manpage, as it makes sense to capitalize acronyms.
26458 - Remove the torrc.complete file. It hasn't been kept up to date
26459 and users will have better luck checking out the manpage.
26460 - Remove the obsolete "NoPublish" option; it has been flagged
26461 as obsolete and has produced a warning since 0.1.1.18-rc.
26462 - Remove everything related to building the expert bundle for OS X.
26463 It has confused many users, doesn't work right on OS X 10.6,
26464 and is hard to get rid of once installed. Resolves bug 1274.
26467 Changes in version 0.2.2.17-alpha - 2010-09-30
26468 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
26469 to use one-hop circuits (which can put the exit relays at higher risk,
26470 plus unbalance the network); fixes a big bug in bandwidth accounting
26471 for relays that want to limit their monthly bandwidth use; fixes a
26472 big pile of bugs in how clients tolerate temporary network failure;
26473 and makes our adaptive circuit build timeout feature (which improves
26474 client performance if your network is fast while not breaking things
26475 if your network is slow) better handle bad networks.
26478 - Exit relays now try harder to block exit attempts from unknown
26479 relays, to make it harder for people to use them as one-hop proxies
26480 a la tortunnel. Controlled by the refuseunknownexits consensus
26481 parameter (currently enabled), or you can override it on your
26482 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
26484 o Major bugfixes (0.2.1.x and earlier):
26485 - Fix a bug in bandwidth accounting that could make us use twice
26486 the intended bandwidth when our interval start changes due to
26487 daylight saving time. Now we tolerate skew in stored vs computed
26488 interval starts: if the start of the period changes by no more than
26489 50% of the period's duration, we remember bytes that we transferred
26490 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
26491 - Always search the Windows system directory for system DLLs, and
26492 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
26493 - When you're using bridges and your network goes away and your
26494 bridges get marked as down, recover when you attempt a new socks
26495 connection (if the network is back), rather than waiting up to an
26496 hour to try fetching new descriptors for your bridges. Bugfix on
26497 0.2.0.3-alpha; fixes bug 1981.
26499 o Major bugfixes (on 0.2.2.x):
26500 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
26502 - Fix a segfault that could happen when operating a bridge relay with
26503 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
26504 - The consensus bandwidth-weights (used by clients to choose fast
26505 relays) entered an unexpected edge case in September where
26506 Exits were much scarcer than Guards, resulting in bad weight
26507 recommendations. Now we compute them using new constraints that
26508 should succeed in all cases. Also alter directory authorities to
26509 not include the bandwidth-weights line if they fail to produce
26510 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
26511 - When weighting bridges during path selection, we used to trust
26512 the bandwidths they provided in their descriptor, only capping them
26513 at 10MB/s. This turned out to be problematic for two reasons:
26514 Bridges could claim to handle a lot more traffic then they
26515 actually would, thus making more clients pick them and have a
26516 pretty effective DoS attack. The other issue is that new bridges
26517 that might not have a good estimate for their bw capacity yet
26518 would not get used at all unless no other bridges are available
26519 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
26521 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
26522 - Ignore cannibalized circuits when recording circuit build times.
26523 This should provide for a minor performance improvement for hidden
26524 service users using 0.2.2.14-alpha, and should remove two spurious
26525 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
26526 - Simplify the logic that causes us to decide if the network is
26527 unavailable for purposes of recording circuit build times. If we
26528 receive no cells whatsoever for the entire duration of a circuit's
26529 full measured lifetime, the network is probably down. Also ignore
26530 one-hop directory fetching circuit timeouts when calculating our
26531 circuit build times. These changes should hopefully reduce the
26532 cases where we see ridiculous circuit build timeouts for people
26533 with spotty wireless connections. Fixes part of bug 1772; bugfix
26535 - Prevent the circuit build timeout from becoming larger than
26536 the maximum build time we have ever seen. Also, prevent the time
26537 period for measurement circuits from becoming larger than twice that
26538 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
26541 - When we run out of directory information such that we can't build
26542 circuits, but then get enough that we can build circuits, log when
26543 we actually construct a circuit, so the user has a better chance of
26544 knowing what's going on. Fixes bug 1362.
26545 - Be more generous with how much bandwidth we'd use up (with
26546 accounting enabled) before entering "soft hibernation". Previously,
26547 we'd refuse new connections and circuits once we'd used up 95% of
26548 our allotment. Now, we use up 95% of our allotment, AND make sure
26549 that we have no more than 500MB (or 3 hours of expected traffic,
26550 whichever is lower) remaining before we enter soft hibernation.
26551 - If we've configured EntryNodes and our network goes away and/or all
26552 our entrynodes get marked down, optimistically retry them all when
26553 a new socks application request appears. Fixes bug 1882.
26554 - Add some more defensive programming for architectures that can't
26555 handle unaligned integer accesses. We don't know of any actual bugs
26556 right now, but that's the best time to fix them. Fixes bug 1943.
26557 - Support line continuations in the torrc config file. If a line
26558 ends with a single backslash character, the newline is ignored, and
26559 the configuration value is treated as continuing on the next line.
26562 o Minor bugfixes (on 0.2.1.x and earlier):
26563 - For bandwidth accounting, calculate our expected bandwidth rate
26564 based on the time during which we were active and not in
26565 soft-hibernation during the last interval. Previously, we were
26566 also considering the time spent in soft-hibernation. If this
26567 was a long time, we would wind up underestimating our bandwidth
26568 by a lot, and skewing our wakeup time towards the start of the
26569 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
26571 o Minor bugfixes (on 0.2.2.x):
26572 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
26573 which were disabled by the circuit build timeout changes in
26574 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
26575 - Make sure we don't warn about missing bandwidth weights when
26576 choosing bridges or other relays not in the consensus. Bugfix on
26577 0.2.2.10-alpha; fixes bug 1805.
26578 - In our logs, do not double-report signatures from unrecognized
26579 authorities both as "from unknown authority" and "not
26580 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
26583 Changes in version 0.2.2.16-alpha - 2010-09-17
26584 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
26585 evident at exit relays), and also continues to resolve all the little
26586 bugs that have been filling up trac lately.
26588 o Major bugfixes (stream-level fairness):
26589 - When receiving a circuit-level SENDME for a blocked circuit, try
26590 to package cells fairly from all the streams that had previously
26591 been blocked on that circuit. Previously, we had started with the
26592 oldest stream, and allowed each stream to potentially exhaust
26593 the circuit's package window. This gave older streams on any
26594 given circuit priority over newer ones. Fixes bug 1937. Detected
26595 originally by Camilo Viecco. This bug was introduced before the
26596 first Tor release, in svn commit r152: it is the new winner of
26597 the longest-lived bug prize.
26598 - When the exit relay got a circuit-level sendme cell, it started
26599 reading on the exit streams, even if had 500 cells queued in the
26600 circuit queue already, so the circuit queue just grew and grew in
26601 some cases. We fix this by not re-enabling reading on receipt of a
26602 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
26603 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
26605 - Newly created streams were allowed to read cells onto circuits,
26606 even if the circuit's cell queue was blocked and waiting to drain.
26607 This created potential unfairness, as older streams would be
26608 blocked, but newer streams would gladly fill the queue completely.
26609 We add code to detect this situation and prevent any stream from
26610 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
26614 - Update to the September 1 2010 Maxmind GeoLite Country database.
26615 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
26616 not. This would lead to a cookie that is still not group readable.
26617 Closes bug 1843. Suggested by katmagic.
26618 - When logging a rate-limited warning, we now mention how many messages
26619 got suppressed since the last warning.
26620 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
26621 do individual connection-level rate limiting of clients. The torrc
26622 config options with the same names trump the consensus params, if
26623 both are present. Replaces the old "bwconnrate" and "bwconnburst"
26624 consensus params which were broken from 0.2.2.7-alpha through
26625 0.2.2.14-alpha. Closes bug 1947.
26626 - When a router changes IP address or port, authorities now launch
26627 a new reachability test for it. Implements ticket 1899.
26628 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
26629 2 no signature, 4 required" messages about consensus signatures
26630 easier to read, and make sure they get logged at the same severity
26631 as the messages explaining which keys are which. Fixes bug 1290.
26632 - Don't warn when we have a consensus that we can't verify because
26633 of missing certificates, unless those certificates are ones
26634 that we have been trying and failing to download. Fixes bug 1145.
26635 - If you configure your bridge with a known identity fingerprint,
26636 and the bridge authority is unreachable (as it is in at least
26637 one country now), fall back to directly requesting the descriptor
26638 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
26640 - When building with --enable-gcc-warnings on OpenBSD, disable
26641 warnings in system headers. This makes --enable-gcc-warnings
26642 pass on OpenBSD 4.8.
26644 o Minor bugfixes (on 0.2.1.x and earlier):
26645 - Authorities will now attempt to download consensuses if their
26646 own efforts to make a live consensus have failed. This change
26647 means authorities that restart will fetch a valid consensus, and
26648 it means authorities that didn't agree with the current consensus
26649 will still fetch and serve it if it has enough signatures. Bugfix
26650 on 0.2.0.9-alpha; fixes bug 1300.
26651 - Ensure DNS requests launched by "RESOLVE" commands from the
26652 controller respect the __LeaveStreamsUnattached setconf options. The
26653 same goes for requests launched via DNSPort or transparent
26654 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
26655 - Allow handshaking OR connections to take a full KeepalivePeriod
26656 seconds to handshake. Previously, we would close them after
26657 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
26658 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
26660 - Rate-limit "Failed to hand off onionskin" warnings.
26661 - Never relay a cell for a circuit we have already destroyed.
26662 Between marking a circuit as closeable and finally closing it,
26663 it may have been possible for a few queued cells to get relayed,
26664 even though they would have been immediately dropped by the next
26665 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
26666 - Never queue a cell for a circuit that's already been marked
26668 - Never vote for a server as "Running" if we have a descriptor for
26669 it claiming to be hibernating, and that descriptor was published
26670 more recently than our last contact with the server. Bugfix on
26671 0.2.0.3-alpha; fixes bug 911.
26672 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
26675 o Minor bugfixes (on 0.2.2.x):
26676 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
26677 down if a directory fetch fails and you've configured either
26678 bridges or EntryNodes. The intent was to mark the relay as down
26679 _unless_ you're using bridges or EntryNodes, since if you are
26680 then you could quickly run out of entry points.
26681 - Fix the Windows directory-listing code. A bug introduced in
26682 0.2.2.14-alpha could make Windows directory servers forget to load
26683 some of their cached v2 networkstatus files.
26684 - Really allow clients to use relays as bridges. Fixes bug 1776;
26685 bugfix on 0.2.2.15-alpha.
26686 - Demote a warn to info that happens when the CellStatistics option
26687 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
26688 Reported by Moritz Bartl.
26689 - On Windows, build correctly either with or without Unicode support.
26690 This is necessary so that Tor can support fringe platforms like
26691 Windows 98 (which has no Unicode), or Windows CE (which has no
26692 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
26695 - Add a unit test for cross-platform directory-listing code.
26698 Changes in version 0.2.2.15-alpha - 2010-08-18
26699 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
26700 fixes a variety of other bugs that were preventing performance
26701 experiments from moving forward, fixes several bothersome memory leaks,
26702 and generally closes a lot of smaller bugs that have been filling up
26706 - Stop assigning the HSDir flag to relays that disable their
26707 DirPort (and thus will refuse to answer directory requests). This
26708 fix should dramatically improve the reachability of hidden services:
26709 hidden services and hidden service clients pick six HSDir relays
26710 to store and retrieve the hidden service descriptor, and currently
26711 about half of the HSDir relays will refuse to work. Bugfix on
26712 0.2.0.10-alpha; fixes part of bug 1693.
26713 - The PerConnBWRate and Burst config options, along with the
26714 bwconnrate and bwconnburst consensus params, initialized each conn's
26715 token bucket values only when the connection is established. Now we
26716 update them if the config options change, and update them every time
26717 we get a new consensus. Otherwise we can encounter an ugly edge
26718 case where we initialize an OR conn to client-level bandwidth,
26719 but then later the relay joins the consensus and we leave it
26720 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
26721 - Fix a regression that caused Tor to rebind its ports if it receives
26722 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
26725 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
26726 should give us approximately 40-50% more Guard-flagged nodes,
26727 improving the anonymity the Tor network can provide and also
26728 decreasing the dropoff in throughput that relays experience when
26729 they first get the Guard flag.
26730 - Allow enabling or disabling the *Statistics config options while
26734 - Update to the August 1 2010 Maxmind GeoLite Country database.
26735 - Have the controller interface give a more useful message than
26736 "Internal Error" in response to failed GETINFO requests.
26737 - Warn when the same option is provided more than once in a torrc
26738 file, on the command line, or in a single SETCONF statement, and
26739 the option is one that only accepts a single line. Closes bug 1384.
26740 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
26741 Patch from mingw-san.
26742 - Add support for the country code "{??}" in torrc options like
26743 ExcludeNodes, to indicate all routers of unknown country. Closes
26745 - Relays report the number of bytes spent on answering directory
26746 requests in extra-info descriptors similar to {read,write}-history.
26747 Implements enhancement 1790.
26749 o Minor bugfixes (on 0.2.1.x and earlier):
26750 - Complain if PublishServerDescriptor is given multiple arguments that
26751 include 0 or 1. This configuration will be rejected in the future.
26752 Bugfix on 0.2.0.1-alpha; closes bug 1107.
26753 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
26754 Bugfix on 0.2.0.13-alpha; closes bug 928.
26755 - Change "Application request when we're believed to be offline."
26756 notice to "Application request when we haven't used client
26757 functionality lately.", to clarify that it's not an error. Bugfix
26758 on 0.0.9.3; fixes bug 1222.
26759 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
26760 would return "551 Internal error" rather than "552 Unrecognized key
26761 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
26762 - Users can't configure a regular relay to be their bridge. It didn't
26763 work because when Tor fetched the bridge descriptor, it found
26764 that it already had it, and didn't realize that the purpose of the
26765 descriptor had changed. Now we replace routers with a purpose other
26766 than bridge with bridge descriptors when fetching them. Bugfix on
26767 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
26768 refetch the descriptor with router purpose 'general', disabling
26770 - Fix a rare bug in rend_fn unit tests: we would fail a test when
26771 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
26772 on 0.2.0.10-alpha; fixes bug 1808.
26773 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
26774 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
26775 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
26776 Servers can start sending this code when enough clients recognize
26777 it. Also update the spec to reflect this new reason. Bugfix on
26778 0.1.0.1-rc; fixes part of bug 1793.
26779 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
26780 when we switch from being a public relay to a bridge. Otherwise
26781 there will still be clients that see the relay in their consensus,
26782 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
26784 - Instead of giving an assertion failure on an internal mismatch
26785 on estimated freelist size, just log a BUG warning and try later.
26786 Mitigates but does not fix bug 1125.
26787 - Fix an assertion failure that could occur in caches or bridge users
26788 when using a very short voting interval on a testing network.
26789 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
26791 o Minor bugfixes (on 0.2.2.x):
26792 - Alter directory authorities to always consider Exit-flagged nodes
26793 as potential Guard nodes in their votes. The actual decision to
26794 use Exits as Guards is done in the consensus bandwidth weights.
26795 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
26796 - When the controller is reporting the purpose of circuits that
26797 didn't finish building before the circuit build timeout, it was
26798 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
26799 - Our libevent version parsing code couldn't handle versions like
26800 1.4.14b-stable and incorrectly warned the user about using an
26801 old and broken version of libevent. Treat 1.4.14b-stable like
26802 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
26804 - Don't use substitution references like $(VAR:MOD) when
26805 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
26806 '$(:x)' to 'x' rather than the empty string. This bites us in
26807 doc/ when configured with --disable-asciidoc. Bugfix on
26808 0.2.2.9-alpha; fixes bug 1773.
26809 - Remove a spurious hidden service server-side log notice about
26810 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
26812 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
26814 - Correctly report written bytes on linked connections. Found while
26815 implementing 1790. Bugfix on 0.2.2.4-alpha.
26816 - Fix three memory leaks: one in circuit_build_times_parse_state(),
26817 one in dirvote_add_signatures_to_pending_consensus(), and one every
26818 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
26819 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
26821 o Code simplifications and refactoring:
26822 - Take a first step towards making or.h smaller by splitting out
26823 function definitions for all source files in src/or/. Leave
26824 structures and defines in or.h for now.
26825 - Remove a bunch of unused function declarations as well as a block of
26826 #if 0'd code from the unit tests. Closes bug 1824.
26827 - New unit tests for exit-port history statistics; refactored exit
26828 statistics code to be more easily tested.
26829 - Remove the old debian/ directory from the main Tor distribution.
26830 The official Tor-for-debian git repository lives at the URL
26831 https://git.torproject.org/debian/tor.git
26834 Changes in version 0.2.2.14-alpha - 2010-07-12
26835 Tor 0.2.2.14-alpha greatly improves client-side handling of
26836 circuit build timeouts, which are used to estimate speed and improve
26837 performance. We also move to a much better GeoIP database, port Tor to
26838 Windows CE, introduce new compile flags that improve code security,
26839 add an eighth v3 directory authority, and address a lot of more
26843 - Tor directory authorities no longer crash when started with a
26844 cached-microdesc-consensus file in their data directory. Bugfix
26845 on 0.2.2.6-alpha; fixes bug 1532.
26846 - Treat an unset $HOME like an empty $HOME rather than triggering an
26847 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
26848 - Ignore negative and large circuit build timeout values that can
26849 happen during a suspend or hibernate. These values caused various
26850 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
26851 - Alter calculation of Pareto distribution parameter 'Xm' for
26852 Circuit Build Timeout learning to use the weighted average of the
26853 top N=3 modes (because we have three entry guards). Considering
26854 multiple modes should improve the timeout calculation in some cases,
26855 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
26857 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
26858 right censored distribution model. This approach improves over the
26859 synthetic timeout generation approach that was producing insanely
26860 high timeout values. Now we calculate build timeouts using truncated
26861 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
26862 - Do not close circuits that are under construction when they reach
26863 the circuit build timeout. Instead, leave them building (but do not
26864 use them) for up until the time corresponding to the 95th percentile
26865 on the Pareto CDF or 60 seconds, whichever is greater. This is done
26866 to provide better data for the new Pareto model. This percentile
26867 can be controlled by the consensus.
26870 - Move to the June 2010 Maxmind GeoLite country db (rather than the
26871 June 2009 ip-to-country GeoIP db) for our statistics that count
26872 how many users relays are seeing from each country. Now we have
26873 more accurate data for many African countries.
26874 - Port Tor to build and run correctly on Windows CE systems, using
26875 the wcecompat library. Contributed by Valerio Lupi.
26876 - New "--enable-gcc-hardening" ./configure flag (off by default)
26877 to turn on gcc compile time hardening options. It ensures
26878 that signed ints have defined behavior (-fwrapv), enables
26879 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
26880 with canaries (-fstack-protector-all), turns on ASLR protection if
26881 supported by the kernel (-fPIE, -pie), and adds additional security
26882 related warnings. Verified to work on Mac OS X and Debian Lenny.
26883 - New "--enable-linker-hardening" ./configure flag (off by default)
26884 to turn on ELF specific hardening features (relro, now). This does
26885 not work with Mac OS X or any other non-ELF binary format.
26887 o New directory authorities:
26888 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
26892 - New config option "WarnUnsafeSocks 0" disables the warning that
26893 occurs whenever Tor receives a socks handshake using a version of
26894 the socks protocol that can only provide an IP address (rather
26895 than a hostname). Setups that do DNS locally over Tor are fine,
26896 and we shouldn't spam the logs in that case.
26897 - Convert the HACKING file to asciidoc, and add a few new sections
26898 to it, explaining how we use Git, how we make changelogs, and
26899 what should go in a patch.
26900 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
26901 event, to give information on the current rate of circuit timeouts
26902 over our stored history.
26903 - Add ability to disable circuit build time learning via consensus
26904 parameter and via a LearnCircuitBuildTimeout config option. Also
26905 automatically disable circuit build time calculation if we are
26906 either a AuthoritativeDirectory, or if we fail to write our state
26907 file. Fixes bug 1296.
26908 - More gracefully handle corrupt state files, removing asserts
26909 in favor of saving a backup and resetting state.
26910 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
26914 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
26916 - When a2x fails, mention that the user could disable manpages instead
26917 of trying to fix their asciidoc installation.
26918 - Where available, use Libevent 2.0's periodic timers so that our
26919 once-per-second cleanup code gets called even more closely to
26920 once per second than it would otherwise. Fixes bug 943.
26921 - If you run a bridge that listens on multiple IP addresses, and
26922 some user configures a bridge address that uses a different IP
26923 address than your bridge writes in its router descriptor, and the
26924 user doesn't specify an identity key, their Tor would discard the
26925 descriptor because "it isn't one of our configured bridges", and
26926 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
26927 Bugfix on 0.2.0.3-alpha.
26928 - If OpenSSL fails to make a duplicate of a private or public key, log
26929 an error message and try to exit cleanly. May help with debugging
26930 if bug 1209 ever remanifests.
26931 - Save a couple bytes in memory allocation every time we escape
26932 certain characters in a string. Patch from Florian Zumbiehl.
26933 - Make it explicit that we don't cannibalize one-hop circuits. This
26934 happens in the wild, but doesn't turn out to be a problem because
26935 we fortunately don't use those circuits. Many thanks to outofwords
26936 for the initial analysis and to swissknife who confirmed that
26937 two-hop circuits are actually created.
26938 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
26939 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
26940 - Eliminate a case where a circuit build time warning was displayed
26941 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
26944 Changes in version 0.2.1.26 - 2010-05-02
26945 Tor 0.2.1.26 addresses the recent connection and memory overload
26946 problems we've been seeing on relays, especially relays with their
26947 DirPort open. If your relay has been crashing, or you turned it off
26948 because it used too many resources, give this release a try.
26950 This release also fixes yet another instance of broken OpenSSL libraries
26951 that was causing some relays to drop out of the consensus.
26954 - Teach relays to defend themselves from connection overload. Relays
26955 now close idle circuits early if it looks like they were intended
26956 for directory fetches. Relays are also more aggressive about closing
26957 TLS connections that have no circuits on them. Such circuits are
26958 unlikely to be re-used, and tens of thousands of them were piling
26959 up at the fast relays, causing the relays to run out of sockets
26960 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
26961 their directory fetches over TLS).
26962 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
26963 that claim to be earlier than 0.9.8m, but which have in reality
26964 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
26965 behavior. Possible fix for some cases of bug 1346.
26966 - Directory mirrors were fetching relay descriptors only from v2
26967 directory authorities, rather than v3 authorities like they should.
26968 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
26969 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
26972 - Finally get rid of the deprecated and now harmful notion of "clique
26973 mode", where directory authorities maintain TLS connections to
26977 - In the util/threads test, no longer free the test_mutex before all
26978 worker threads have finished. Bugfix on 0.2.1.6-alpha.
26979 - The master thread could starve the worker threads quite badly on
26980 certain systems, causing them to run only partially in the allowed
26981 window. This resulted in test failures. Now the master thread sleeps
26982 occasionally for a few microseconds while the two worker-threads
26983 compete for the mutex. Bugfix on 0.2.0.1-alpha.
26986 Changes in version 0.2.2.13-alpha - 2010-04-24
26987 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
26988 problems we've been seeing on relays, especially relays with their
26989 DirPort open. If your relay has been crashing, or you turned it off
26990 because it used too many resources, give this release a try.
26993 - Teach relays to defend themselves from connection overload. Relays
26994 now close idle circuits early if it looks like they were intended
26995 for directory fetches. Relays are also more aggressive about closing
26996 TLS connections that have no circuits on them. Such circuits are
26997 unlikely to be re-used, and tens of thousands of them were piling
26998 up at the fast relays, causing the relays to run out of sockets
26999 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
27000 their directory fetches over TLS).
27003 - Finally get rid of the deprecated and now harmful notion of "clique
27004 mode", where directory authorities maintain TLS connections to
27006 - Directory authorities now do an immediate reachability check as soon
27007 as they hear about a new relay. This change should slightly reduce
27008 the time between setting up a relay and getting listed as running
27009 in the consensus. It should also improve the time between setting
27010 up a bridge and seeing use by bridge users.
27011 - Directory authorities no longer launch a TLS connection to every
27012 relay as they startup. Now that we have 2k+ descriptors cached,
27013 the resulting network hiccup is becoming a burden. Besides,
27014 authorities already avoid voting about Running for the first half
27015 hour of their uptime.
27018 Changes in version 0.2.2.12-alpha - 2010-04-20
27019 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
27020 handle and vote on descriptors. It was causing relays to drop out of
27024 - Many relays have been falling out of the consensus lately because
27025 not enough authorities know about their descriptor for them to get
27026 a majority of votes. When we deprecated the v2 directory protocol,
27027 we got rid of the only way that v3 authorities can hear from each
27028 other about other descriptors. Now authorities examine every v3
27029 vote for new descriptors, and fetch them from that authority. Bugfix
27031 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
27032 and a warning in or.h related to bandwidth_weight_rule_t that
27033 prevented clean compile on OS X. Fixes bug 1363; bugfix on
27035 - Fix a segfault on relays when DirReqStatistics is enabled
27036 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
27040 - Demote a confusing TLS warning that relay operators might get when
27041 someone tries to talk to their OrPort. It is neither the operator's
27042 fault nor can they do anything about it. Fixes bug 1364; bugfix
27046 Changes in version 0.2.2.11-alpha - 2010-04-15
27047 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
27048 libraries that was causing some relays to drop out of the consensus.
27051 - Directory mirrors were fetching relay descriptors only from v2
27052 directory authorities, rather than v3 authorities like they should.
27053 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
27054 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
27055 - Fix a parsing error that made every possible value of
27056 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
27057 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
27058 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
27059 about the option without breaking older ones.
27060 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
27061 that claim to be earlier than 0.9.8m, but which have in reality
27062 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
27063 behavior. Possible fix for some cases of bug 1346.
27066 - Experiment with a more aggressive approach to preventing clients
27067 from making one-hop exit streams. Exit relays who want to try it
27068 out can set "RefuseUnknownExits 1" in their torrc, and then look
27069 for "Attempt by %s to open a stream" log messages. Let us know
27071 - Add support for statically linking zlib by specifying
27072 --enable-static-zlib, to go with our support for statically linking
27073 openssl and libevent. Resolves bug 1358.
27076 - Fix a segfault that happens whenever a Tor client that is using
27077 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
27079 - When we cleaned up the contrib/tor-exit-notice.html file, we left
27080 out the first line. Fixes bug 1295.
27081 - When building the manpage from a tarball, we required asciidoc, but
27082 the asciidoc -> roff/html conversion was already done for the
27083 tarball. Make 'make' complain only when we need asciidoc (either
27084 because we're compiling directly from git, or because we altered
27085 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
27086 - When none of the directory authorities vote on any params, Tor
27087 segfaulted when trying to make the consensus from the votes. We
27088 didn't trigger the bug in practice, because authorities do include
27089 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
27092 - In the util/threads test, no longer free the test_mutex before all
27093 worker threads have finished. Bugfix on 0.2.1.6-alpha.
27094 - The master thread could starve the worker threads quite badly on
27095 certain systems, causing them to run only partially in the allowed
27096 window. This resulted in test failures. Now the master thread sleeps
27097 occasionally for a few microseconds while the two worker-threads
27098 compete for the mutex. Bugfix on 0.2.0.1-alpha.
27101 Changes in version 0.2.2.10-alpha - 2010-03-07
27102 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
27103 could prevent relays from guessing their IP address correctly. It also
27104 starts the groundwork for another client-side performance boost, since
27105 currently we're not making efficient use of relays that have both the
27106 Guard flag and the Exit flag.
27109 - Fix a regression from our patch for bug 1244 that caused relays
27110 to guess their IP address incorrectly if they didn't set Address
27111 in their torrc and/or their address fails to resolve. Bugfix on
27112 0.2.2.9-alpha; fixes bug 1269.
27114 o Major features (performance):
27115 - Directory authorities now compute consensus weightings that instruct
27116 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
27117 and no flag. Clients that use these weightings will distribute
27118 network load more evenly across these different relay types. The
27119 weightings are in the consensus so we can change them globally in
27120 the future. Extra thanks to "outofwords" for finding some nasty
27121 security bugs in the first implementation of this feature.
27123 o Minor features (performance):
27124 - Always perform router selections using weighted relay bandwidth,
27125 even if we don't need a high capacity circuit at the time. Non-fast
27126 circuits now only differ from fast ones in that they can use relays
27127 not marked with the Fast flag. This "feature" could turn out to
27128 be a horrible bug; we should investigate more before it goes into
27132 - Allow disabling building of the manpages. Skipping the manpage
27133 speeds up the build considerably.
27135 o Minor bugfixes (on 0.2.2.x):
27136 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
27137 Bugfix on 0.2.2.9-alpha.
27138 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
27139 config option. Bugfix on 0.2.2.7-alpha.
27140 - Ship the asciidoc-helper file in the tarball, so that people can
27141 build from source if they want to, and touching the .1.txt files
27142 doesn't break the build. Bugfix on 0.2.2.9-alpha.
27144 o Minor bugfixes (on 0.2.1.x or earlier):
27145 - Fix a dereference-then-NULL-check sequence when publishing
27146 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
27148 - Fix another dereference-then-NULL-check sequence. Bugfix on
27149 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
27150 - Make sure we treat potentially not NUL-terminated strings correctly.
27151 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
27153 o Code simplifications and refactoring:
27154 - Fix some urls in the exit notice file and make it XHTML1.1 strict
27155 compliant. Based on a patch from Christian Kujau.
27156 - Don't use sed in asciidoc-helper anymore.
27157 - Make the build process fail if asciidoc cannot be found and
27158 building with asciidoc isn't disabled.
27161 Changes in version 0.2.2.9-alpha - 2010-02-22
27162 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
27163 location of a directory authority, and cleans up a bunch of small bugs.
27165 o Directory authority changes:
27166 - Change IP address for dannenberg (v3 directory authority), and
27167 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
27168 service directory authority) from the list.
27171 - Make Tor work again on the latest OS X: when deciding whether to
27172 use strange flags to turn TLS renegotiation on, detect the OpenSSL
27173 version at run-time, not compile time. We need to do this because
27174 Apple doesn't update its dev-tools headers when it updates its
27175 libraries in a security patch.
27176 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
27177 that could happen on 32-bit platforms with 64-bit time_t. Also fix
27178 a memory leak when requesting a hidden service descriptor we've
27179 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
27181 - Authorities could be tricked into giving out the Exit flag to relays
27182 that didn't allow exiting to any ports. This bug could screw
27183 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
27184 1238. Bug discovered by Martin Kowalczyk.
27185 - When freeing a session key, zero it out completely. We only zeroed
27186 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
27187 patched by ekir. Fixes bug 1254.
27190 - Fix static compilation by listing the openssl libraries in the right
27191 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
27192 - Resume handling .exit hostnames in a special way: originally we
27193 stripped the .exit part and used the requested exit relay. In
27194 0.2.2.1-alpha we stopped treating them in any special way, meaning
27195 if you use a .exit address then Tor will pass it on to the exit
27196 relay. Now we reject the .exit stream outright, since that behavior
27197 might be more expected by the user. Found and diagnosed by Scott
27198 Bennett and Downie on or-talk.
27199 - Don't spam the controller with events when we have no file
27200 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
27201 for log messages was already solved from bug 748.)
27202 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
27204 - Make the DNSPort option work with libevent 2.x. Don't alter the
27205 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
27206 - Emit a GUARD DROPPED controller event for a case we missed.
27207 - Make more fields in the controller protocol case-insensitive, since
27208 control-spec.txt said they were.
27209 - Refactor resolve_my_address() to not use gethostbyname() anymore.
27210 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
27211 - Fix a spec conformance issue: the network-status-version token
27212 must be the first token in a v3 consensus or vote. Discovered by
27213 parakeep. Bugfix on 0.2.0.3-alpha.
27215 o Code simplifications and refactoring:
27216 - Generate our manpage and HTML documentation using Asciidoc. This
27217 change should make it easier to maintain the documentation, and
27218 produce nicer HTML.
27219 - Remove the --enable-iphone option. According to reports from Marco
27220 Bonetti, Tor builds fine without any special tweaking on recent
27221 iPhone SDK versions.
27222 - Removed some unnecessary files from the source distribution. The
27223 AUTHORS file has now been merged into the people page on the
27224 website. The roadmaps and design doc can now be found in the
27225 projects directory in svn.
27226 - Enabled various circuit build timeout constants to be controlled
27227 by consensus parameters. Also set better defaults for these
27228 parameters based on experimentation on broadband and simulated
27229 high latency links.
27232 - The 'EXTENDCIRCUIT' control port command can now be used with
27233 a circ id of 0 and no path. This feature will cause Tor to build
27234 a new 'fast' general purpose circuit using its own path selection
27236 - Added a BUILDTIMEOUT_SET controller event to describe changes
27237 to the circuit build timeout.
27238 - Future-proof the controller protocol a bit by ignoring keyword
27239 arguments we do not recognize.
27240 - Expand homedirs passed to tor-checkkey. This should silence a
27241 coverity complaint about passing a user-supplied string into
27242 open() without checking it.
27245 Changes in version 0.2.1.25 - 2010-03-16
27246 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
27247 prevent relays from guessing their IP address correctly. It also fixes
27248 several minor potential security bugs.
27251 - Fix a regression from our patch for bug 1244 that caused relays
27252 to guess their IP address incorrectly if they didn't set Address
27253 in their torrc and/or their address fails to resolve. Bugfix on
27254 0.2.1.23; fixes bug 1269.
27255 - When freeing a session key, zero it out completely. We only zeroed
27256 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
27257 patched by ekir. Fixes bug 1254.
27260 - Fix a dereference-then-NULL-check sequence when publishing
27261 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
27263 - Fix another dereference-then-NULL-check sequence. Bugfix on
27264 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
27265 - Make sure we treat potentially not NUL-terminated strings correctly.
27266 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
27270 Changes in version 0.2.1.24 - 2010-02-21
27271 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
27275 - Work correctly out-of-the-box with even more vendor-patched versions
27276 of OpenSSL. In particular, make it so Debian and OS X don't need
27277 customized patches to run/build.
27280 Changes in version 0.2.1.23 - 2010-02-13
27281 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
27282 again on the latest OS X, and updates the location of a directory
27285 o Major bugfixes (performance):
27286 - We were selecting our guards uniformly at random, and then weighting
27287 which of our guards we'd use uniformly at random. This imbalance
27288 meant that Tor clients were severely limited on throughput (and
27289 probably latency too) by the first hop in their circuit. Now we
27290 select guards weighted by currently advertised bandwidth. We also
27291 automatically discard guards picked using the old algorithm. Fixes
27292 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
27295 - Make Tor work again on the latest OS X: when deciding whether to
27296 use strange flags to turn TLS renegotiation on, detect the OpenSSL
27297 version at run-time, not compile time. We need to do this because
27298 Apple doesn't update its dev-tools headers when it updates its
27299 libraries in a security patch.
27300 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
27301 that could happen on 32-bit platforms with 64-bit time_t. Also fix
27302 a memory leak when requesting a hidden service descriptor we've
27303 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
27306 o Directory authority changes:
27307 - Change IP address for dannenberg (v3 directory authority), and
27308 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
27309 service directory authority) from the list.
27312 - Refactor resolve_my_address() to not use gethostbyname() anymore.
27313 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
27316 - Avoid a mad rush at the beginning of each month when each client
27317 rotates half of its guards. Instead we spread the rotation out
27318 throughout the month, but we still avoid leaving a precise timestamp
27319 in the state file about when we first picked the guard. Improves
27320 over the behavior introduced in 0.1.2.17.
27323 Changes in version 0.2.2.8-alpha - 2010-01-26
27324 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
27325 causing bridge relays to disappear. If you're running a bridge,
27329 - Fix a memory corruption bug on bridges that occurred during the
27330 inclusion of stats data in extra-info descriptors. Also fix the
27331 interface for geoip_get_bridge_stats* to prevent similar bugs in
27332 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
27333 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
27336 - Ignore OutboundBindAddress when connecting to localhost.
27337 Connections to localhost need to come _from_ localhost, or else
27338 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
27342 Changes in version 0.2.2.7-alpha - 2010-01-19
27343 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
27344 as laying the groundwork for further relay-side performance fixes. It
27345 also starts cleaning up client behavior with respect to the EntryNodes,
27346 ExitNodes, and StrictNodes config options.
27348 This release also rotates two directory authority keys, due to a
27349 security breach of some of the Torproject servers.
27351 o Directory authority changes:
27352 - Rotate keys (both v3 identity and relay identity) for moria1
27355 o Major features (performance):
27356 - We were selecting our guards uniformly at random, and then weighting
27357 which of our guards we'd use uniformly at random. This imbalance
27358 meant that Tor clients were severely limited on throughput (and
27359 probably latency too) by the first hop in their circuit. Now we
27360 select guards weighted by currently advertised bandwidth. We also
27361 automatically discard guards picked using the old algorithm. Fixes
27362 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
27363 - When choosing which cells to relay first, relays can now favor
27364 circuits that have been quiet recently, to provide lower latency
27365 for low-volume circuits. By default, relays enable or disable this
27366 feature based on a setting in the consensus. You can override
27367 this default by using the new "CircuitPriorityHalflife" config
27368 option. Design and code by Ian Goldberg, Can Tang, and Chris
27370 - Add separate per-conn write limiting to go with the per-conn read
27371 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
27372 but never per-conn write limits.
27373 - New consensus params "bwconnrate" and "bwconnburst" to let us
27374 rate-limit client connections as they enter the network. It's
27375 controlled in the consensus so we can turn it on and off for
27376 experiments. It's starting out off. Based on proposal 163.
27378 o Major features (relay selection options):
27379 - Switch to a StrictNodes config option, rather than the previous
27380 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
27381 "StrictExcludeNodes" option.
27382 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
27383 change during a config reload, mark and discard all our origin
27384 circuits. This fix should address edge cases where we change the
27385 config options and but then choose a circuit that we created before
27387 - If EntryNodes or ExitNodes are set, be more willing to use an
27388 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
27390 - Make EntryNodes config option much more aggressive even when
27391 StrictNodes is not set. Before it would prepend your requested
27392 entrynodes to your list of guard nodes, but feel free to use others
27393 after that. Now it chooses only from your EntryNodes if any of
27394 those are available, and only falls back to others if a) they're
27395 all down and b) StrictNodes is not set.
27396 - Now we refresh your entry guards from EntryNodes at each consensus
27397 fetch -- rather than just at startup and then they slowly rot as
27398 the network changes.
27401 - Stop bridge directory authorities from answering dbg-stability.txt
27402 directory queries, which would let people fetch a list of all
27403 bridge identities they track. Bugfix on 0.2.1.6-alpha.
27406 - Log a notice when we get a new control connection. Now it's easier
27407 for security-conscious users to recognize when a local application
27408 is knocking on their controller door. Suggested by bug 1196.
27409 - New config option "CircuitStreamTimeout" to override our internal
27410 timeout schedule for how many seconds until we detach a stream from
27411 a circuit and try a new circuit. If your network is particularly
27412 slow, you might want to set this to a number like 60.
27413 - New controller command "getinfo config-text". It returns the
27414 contents that Tor would write if you send it a SAVECONF command,
27415 so the controller can write the file to disk itself.
27416 - New options for SafeLogging to allow scrubbing only log messages
27417 generated while acting as a relay.
27418 - Ship the bridges spec file in the tarball too.
27419 - Avoid a mad rush at the beginning of each month when each client
27420 rotates half of its guards. Instead we spread the rotation out
27421 throughout the month, but we still avoid leaving a precise timestamp
27422 in the state file about when we first picked the guard. Improves
27423 over the behavior introduced in 0.1.2.17.
27425 o Minor bugfixes (compiling):
27426 - Fix compilation on OS X 10.3, which has a stub mlockall() but
27427 hides it. Bugfix on 0.2.2.6-alpha.
27428 - Fix compilation on Solaris by removing support for the
27429 DisableAllSwap config option. Solaris doesn't have an rlimit for
27430 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
27433 o Minor bugfixes (crashes):
27434 - Do not segfault when writing buffer stats when we haven't observed
27435 a single circuit to report about. Found by Fabian Lanze. Bugfix on
27437 - If we're in the pathological case where there's no exit bandwidth
27438 but there is non-exit bandwidth, or no guard bandwidth but there
27439 is non-guard bandwidth, don't crash during path selection. Bugfix
27441 - Fix an impossible-to-actually-trigger buffer overflow in relay
27442 descriptor generation. Bugfix on 0.1.0.15.
27444 o Minor bugfixes (privacy):
27445 - Fix an instance where a Tor directory mirror might accidentally
27446 log the IP address of a misbehaving Tor client. Bugfix on
27448 - Don't list Windows capabilities in relay descriptors. We never made
27449 use of them, and maybe it's a bad idea to publish them. Bugfix
27452 o Minor bugfixes (other):
27453 - Resolve an edge case in path weighting that could make us misweight
27454 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
27455 - Fix statistics on client numbers by country as seen by bridges that
27456 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
27457 intervals instead of variable 12-to-48-hour intervals.
27458 - After we free an internal connection structure, overwrite it
27459 with a different memory value than we use for overwriting a freed
27460 internal circuit structure. Should help with debugging. Suggested
27462 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
27465 o Removed features:
27466 - Remove the HSAuthorityRecordStats option that version 0 hidden
27467 service authorities could have used to track statistics of overall
27468 hidden service usage.
27471 Changes in version 0.2.1.22 - 2010-01-19
27472 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
27473 authorities -- it would tell you its whole history of bridge descriptors
27474 if you make the right directory request. This stable update also
27475 rotates two of the seven v3 directory authority keys and locations.
27477 o Directory authority changes:
27478 - Rotate keys (both v3 identity and relay identity) for moria1
27482 - Stop bridge directory authorities from answering dbg-stability.txt
27483 directory queries, which would let people fetch a list of all
27484 bridge identities they track. Bugfix on 0.2.1.6-alpha.
27487 Changes in version 0.2.1.21 - 2009-12-21
27488 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
27489 library. If you use Tor on Linux / Unix and you're getting SSL
27490 renegotiation errors, upgrading should help. We also recommend an
27491 upgrade if you're an exit relay.
27494 - Work around a security feature in OpenSSL 0.9.8l that prevents our
27495 handshake from working unless we explicitly tell OpenSSL that we
27496 are using SSL renegotiation safely. We are, of course, but OpenSSL
27497 0.9.8l won't work unless we say we are.
27498 - Avoid crashing if the client is trying to upload many bytes and the
27499 circuit gets torn down at the same time, or if the flip side
27500 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
27503 - Do not refuse to learn about authority certs and v2 networkstatus
27504 documents that are older than the latest consensus. This bug might
27505 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
27506 Spotted and fixed by xmux.
27507 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
27508 trigger platform-specific option misparsing case found by Coverity
27510 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
27511 trigger assert. Fixes bug 1173.
27514 Changes in version 0.2.2.6-alpha - 2009-11-19
27515 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
27516 support for the new lower-footprint "microdescriptor" directory design,
27517 future-proofing our consensus format against new hash functions or
27518 other changes, and an Android port. It also makes Tor compatible with
27519 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
27522 - Directory authorities can now create, vote on, and serve multiple
27523 parallel formats of directory data as part of their voting process.
27524 Partially implements Proposal 162: "Publish the consensus in
27526 - Directory authorities can now agree on and publish small summaries
27527 of router information that clients can use in place of regular
27528 server descriptors. This transition will eventually allow clients
27529 to use far less bandwidth for downloading information about the
27530 network. Begins the implementation of Proposal 158: "Clients
27531 download consensus + microdescriptors".
27532 - The directory voting system is now extensible to use multiple hash
27533 algorithms for signatures and resource selection. Newer formats
27534 are signed with SHA256, with a possibility for moving to a better
27535 hash algorithm in the future.
27536 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
27537 current and future memory pages via mlockall(). On supported
27538 platforms (modern Linux and probably BSD but not Windows or OS X),
27539 this should effectively disable any and all attempts to page out
27540 memory. This option requires that you start your Tor as root --
27541 if you use DisableAllSwap, please consider using the User option
27542 to properly reduce the privileges of your Tor.
27543 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
27544 to help Tor build correctly for Android phones.
27547 - Work around a security feature in OpenSSL 0.9.8l that prevents our
27548 handshake from working unless we explicitly tell OpenSSL that we
27549 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
27550 won't work unless we say we are.
27553 - Fix a crash bug when trying to initialize the evdns module in
27554 Libevent 2. Bugfix on 0.2.1.16-rc.
27555 - Stop logging at severity 'warn' when some other Tor client tries
27556 to establish a circuit with us using weak DH keys. It's a protocol
27557 violation, but that doesn't mean ordinary users need to hear about
27558 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
27559 - Do not refuse to learn about authority certs and v2 networkstatus
27560 documents that are older than the latest consensus. This bug might
27561 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
27562 Spotted and fixed by xmux.
27563 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
27564 - If all authorities restart at once right before a consensus vote,
27565 nobody will vote about "Running", and clients will get a consensus
27566 with no usable relays. Instead, authorities refuse to build a
27567 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
27568 - If your relay can't keep up with the number of incoming create
27569 cells, it would log one warning per failure into your logs. Limit
27570 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
27571 - Bridges now use "reject *:*" as their default exit policy. Bugfix
27572 on 0.2.0.3-alpha; fixes bug 1113.
27573 - Fix a memory leak on directory authorities during voting that was
27574 introduced in 0.2.2.1-alpha. Found via valgrind.
27577 Changes in version 0.2.1.20 - 2009-10-15
27578 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
27579 services at once, prepares for more performance improvements, and
27580 fixes a bunch of smaller bugs.
27582 The Windows and OS X bundles also include a more recent Vidalia,
27583 and switch from Privoxy to Polipo.
27585 The OS X installers are now drag and drop. It's best to un-install
27586 Tor/Vidalia and then install this new bundle, rather than upgrade. If
27587 you want to upgrade, you'll need to update the paths for Tor and Polipo
27588 in the Vidalia Settings window.
27591 - Send circuit or stream sendme cells when our window has decreased
27592 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
27593 by Karsten when testing the "reduce circuit window" performance
27594 patch. Bugfix on the 54th commit on Tor -- from July 2002,
27595 before the release of Tor 0.0.0. This is the new winner of the
27597 - Fix a remotely triggerable memory leak when a consensus document
27598 contains more than one signature from the same voter. Bugfix on
27600 - Avoid segfault in rare cases when finishing an introduction circuit
27601 as a client and finding out that we don't have an introduction key
27602 for it. Fixes bug 1073. Reported by Aaron Swartz.
27605 - Tor now reads the "circwindow" parameter out of the consensus,
27606 and uses that value for its circuit package window rather than the
27607 default of 1000 cells. Begins the implementation of proposal 168.
27609 o New directory authorities:
27610 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
27612 - Move moria1 and tonga to alternate IP addresses.
27615 - Fix a signed/unsigned compile warning in 0.2.1.19.
27616 - Fix possible segmentation fault on directory authorities. Bugfix on
27618 - Fix an extremely rare infinite recursion bug that could occur if
27619 we tried to log a message after shutting down the log subsystem.
27620 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
27621 - Fix an obscure bug where hidden services on 64-bit big-endian
27622 systems might mis-read the timestamp in v3 introduce cells, and
27623 refuse to connect back to the client. Discovered by "rotor".
27624 Bugfix on 0.2.1.6-alpha.
27625 - We were triggering a CLOCK_SKEW controller status event whenever
27626 we connect via the v2 connection protocol to any relay that has
27627 a wrong clock. Instead, we should only inform the controller when
27628 it's a trusted authority that claims our clock is wrong. Bugfix
27629 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
27630 - We were telling the controller about CHECKING_REACHABILITY and
27631 REACHABILITY_FAILED status events whenever we launch a testing
27632 circuit or notice that one has failed. Instead, only tell the
27633 controller when we want to inform the user of overall success or
27634 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
27636 - Don't warn when we're using a circuit that ends with a node
27637 excluded in ExcludeExitNodes, but the circuit is not used to access
27638 the outside world. This should help fix bug 1090. Bugfix on
27640 - Work around a small memory leak in some versions of OpenSSL that
27641 stopped the memory used by the hostname TLS extension from being
27645 - Add a "getinfo status/accepted-server-descriptor" controller
27646 command, which is the recommended way for controllers to learn
27647 whether our server descriptor has been successfully received by at
27648 least on directory authority. Un-recommend good-server-descriptor
27649 getinfo and status events until we have a better design for them.
27652 Changes in version 0.2.2.5-alpha - 2009-10-11
27653 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
27656 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
27658 o Directory authorities:
27659 - Temporarily (just for this release) move dizum to an alternate
27663 Changes in version 0.2.2.4-alpha - 2009-10-10
27664 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
27665 introduces a new unit test framework, shifts directry authority
27666 addresses around to reduce the impact from recent blocking events,
27667 and fixes a few smaller bugs.
27670 - Fix several more asserts in the circuit_build_times code, for
27671 example one that causes Tor to fail to start once we have
27672 accumulated 5000 build times in the state file. Bugfixes on
27673 0.2.2.2-alpha; fixes bug 1108.
27675 o New directory authorities:
27676 - Move moria1 and Tonga to alternate IP addresses.
27679 - Log SSL state transitions at debug level during handshake, and
27680 include SSL states in error messages. This may help debug future
27681 SSL handshake issues.
27682 - Add a new "Handshake" log domain for activities that happen
27683 during the TLS handshake.
27684 - Revert to the "June 3 2009" ip-to-country file. The September one
27685 seems to have removed most US IP addresses.
27686 - Directory authorities now reject Tor relays with versions less than
27687 0.1.2.14. This step cuts out four relays from the current network,
27688 none of which are very big.
27691 - Fix a couple of smaller issues with gathering statistics. Bugfixes
27693 - Fix two memory leaks in the error case of
27694 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
27695 - Don't count one-hop circuits when we're estimating how long it
27696 takes circuits to build on average. Otherwise we'll set our circuit
27697 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
27698 - Directory authorities no longer change their opinion of, or vote on,
27699 whether a router is Running, unless they have themselves been
27700 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
27703 o Code simplifications and refactoring:
27704 - Revise our unit tests to use the "tinytest" framework, so we
27705 can run tests in their own processes, have smarter setup/teardown
27706 code, and so on. The unit test code has moved to its own
27707 subdirectory, and has been split into multiple modules.
27710 Changes in version 0.2.2.3-alpha - 2009-09-23
27711 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
27714 - Fix an overzealous assert in our new circuit build timeout code.
27715 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
27718 - If the networkstatus consensus tells us that we should use a
27719 negative circuit package window, ignore it. Otherwise we'll
27720 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
27723 Changes in version 0.2.2.2-alpha - 2009-09-21
27724 Tor 0.2.2.2-alpha introduces our latest performance improvement for
27725 clients: Tor tracks the average time it takes to build a circuit, and
27726 avoids using circuits that take too long to build. For fast connections,
27727 this feature can cut your expected latency in half. For slow or flaky
27728 connections, it could ruin your Tor experience. Let us know if it does!
27731 - Tor now tracks how long it takes to build client-side circuits
27732 over time, and adapts its timeout to local network performance.
27733 Since a circuit that takes a long time to build will also provide
27734 bad performance, we get significant latency improvements by
27735 discarding the slowest 20% of circuits. Specifically, Tor creates
27736 circuits more aggressively than usual until it has enough data
27737 points for a good timeout estimate. Implements proposal 151.
27738 We are especially looking for reports (good and bad) from users with
27739 both EDGE and broadband connections that can move from broadband
27740 to EDGE and find out if the build-time data in the .tor/state gets
27741 reset without loss of Tor usability. You should also see a notice
27742 log message telling you that Tor has reset its timeout.
27743 - Directory authorities can now vote on arbitrary integer values as
27744 part of the consensus process. This is designed to help set
27745 network-wide parameters. Implements proposal 167.
27746 - Tor now reads the "circwindow" parameter out of the consensus,
27747 and uses that value for its circuit package window rather than the
27748 default of 1000 cells. Begins the implementation of proposal 168.
27751 - Fix a remotely triggerable memory leak when a consensus document
27752 contains more than one signature from the same voter. Bugfix on
27756 - Fix an extremely rare infinite recursion bug that could occur if
27757 we tried to log a message after shutting down the log subsystem.
27758 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
27759 - Fix parsing for memory or time units given without a space between
27760 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
27761 - A networkstatus vote must contain exactly one signature. Spec
27762 conformance issue. Bugfix on 0.2.0.3-alpha.
27763 - Fix an obscure bug where hidden services on 64-bit big-endian
27764 systems might mis-read the timestamp in v3 introduce cells, and
27765 refuse to connect back to the client. Discovered by "rotor".
27766 Bugfix on 0.2.1.6-alpha.
27767 - We were triggering a CLOCK_SKEW controller status event whenever
27768 we connect via the v2 connection protocol to any relay that has
27769 a wrong clock. Instead, we should only inform the controller when
27770 it's a trusted authority that claims our clock is wrong. Bugfix
27771 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
27772 - We were telling the controller about CHECKING_REACHABILITY and
27773 REACHABILITY_FAILED status events whenever we launch a testing
27774 circuit or notice that one has failed. Instead, only tell the
27775 controller when we want to inform the user of overall success or
27776 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
27778 - Don't warn when we're using a circuit that ends with a node
27779 excluded in ExcludeExitNodes, but the circuit is not used to access
27780 the outside world. This should help fix bug 1090, but more problems
27781 remain. Bugfix on 0.2.1.6-alpha.
27782 - Work around a small memory leak in some versions of OpenSSL that
27783 stopped the memory used by the hostname TLS extension from being
27785 - Make our 'torify' script more portable; if we have only one of
27786 'torsocks' or 'tsocks' installed, don't complain to the user;
27787 and explain our warning about tsocks better.
27790 - Add a "getinfo status/accepted-server-descriptor" controller
27791 command, which is the recommended way for controllers to learn
27792 whether our server descriptor has been successfully received by at
27793 least on directory authority. Un-recommend good-server-descriptor
27794 getinfo and status events until we have a better design for them.
27795 - Update to the "September 4 2009" ip-to-country file.
27798 Changes in version 0.2.2.1-alpha - 2009-08-26
27799 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
27800 Tor clients to bootstrap on networks where only port 80 is reachable,
27801 makes it more straightforward to support hardware crypto accelerators,
27802 and starts the groundwork for gathering stats safely at relays.
27805 - Start the process of disabling ".exit" address notation, since it
27806 can be used for a variety of esoteric application-level attacks
27807 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
27810 o New directory authorities:
27811 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
27815 - New AccelName and AccelDir options add support for dynamic OpenSSL
27816 hardware crypto acceleration engines.
27817 - Tor now supports tunneling all of its outgoing connections over
27818 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
27819 configuration options. Code by Christopher Davis.
27822 - Send circuit or stream sendme cells when our window has decreased
27823 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
27824 by Karsten when testing the "reduce circuit window" performance
27825 patch. Bugfix on the 54th commit on Tor -- from July 2002,
27826 before the release of Tor 0.0.0. This is the new winner of the
27829 o New options for gathering stats safely:
27830 - Directory mirrors that set "DirReqStatistics 1" write statistics
27831 about directory requests to disk every 24 hours. As compared to the
27832 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
27833 1) stats are written to disk exactly every 24 hours; 2) estimated
27834 shares of v2 and v3 requests are determined as mean values, not at
27835 the end of a measurement period; 3) unresolved requests are listed
27836 with country code '??'; 4) directories also measure download times.
27837 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
27838 number of exit streams and transferred bytes per port to disk every
27840 - Relays that set "CellStatistics 1" write statistics on how long
27841 cells spend in their circuit queues to disk every 24 hours.
27842 - Entry nodes that set "EntryStatistics 1" write statistics on the
27843 rough number and origins of connecting clients to disk every 24
27845 - Relays that write any of the above statistics to disk and set
27846 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
27847 their extra-info documents.
27850 - New --digests command-line switch to output the digests of the
27851 source files Tor was built with.
27852 - The "torify" script now uses torsocks where available.
27853 - The memarea code now uses a sentinel value at the end of each area
27854 to make sure nothing writes beyond the end of an area. This might
27855 help debug some conceivable causes of bug 930.
27856 - Time and memory units in the configuration file can now be set to
27857 fractional units. For example, "2.5 GB" is now a valid value for
27859 - Certain Tor clients (such as those behind check.torproject.org) may
27860 want to fetch the consensus in an extra early manner. To enable this
27861 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
27862 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
27863 as only certain clients who must have this information sooner should
27865 - Instead of adding the svn revision to the Tor version string, report
27866 the git commit (when we're building from a git checkout).
27869 - If any of the v3 certs we download are unparseable, we should
27870 actually notice the failure so we don't retry indefinitely. Bugfix
27871 on 0.2.0.x; reported by "rotator".
27872 - If the cached cert file is unparseable, warn but don't exit.
27873 - Fix possible segmentation fault on directory authorities. Bugfix on
27875 - When Tor fails to parse a descriptor of any kind, dump it to disk.
27876 Might help diagnosing bug 1051.
27878 o Deprecated and removed features:
27879 - The controller no longer accepts the old obsolete "addr-mappings/"
27880 or "unregistered-servers-" GETINFO values.
27881 - Hidden services no longer publish version 0 descriptors, and clients
27882 do not request or use version 0 descriptors. However, the old hidden
27883 service authorities still accept and serve version 0 descriptors
27884 when contacted by older hidden services/clients.
27885 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
27886 always on; using them is necessary for correct forward-compatible
27888 - Remove support for .noconnect style addresses. Nobody was using
27889 them, and they provided another avenue for detecting Tor users
27890 via application-level web tricks.
27892 o Packaging changes:
27893 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
27894 installer bundles. See
27895 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
27896 for details of what's new in Vidalia 0.2.3.
27897 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
27898 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
27899 configuration file, rather than the old Privoxy.
27900 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
27901 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
27902 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
27903 better compatibility with OS X 10.6, aka Snow Leopard.
27904 - OS X Vidalia Bundle: The multi-package installer is now replaced
27905 by a simple drag and drop to the /Applications folder. This change
27906 occurred with the upgrade to Vidalia 0.2.3.
27909 Changes in version 0.2.1.19 - 2009-07-28
27910 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
27911 services on Tor 0.2.1.3-alpha through 0.2.1.18.
27914 - Make accessing hidden services on 0.2.1.x work right again.
27915 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
27916 part of patch provided by "optimist".
27919 - When a relay/bridge is writing out its identity key fingerprint to
27920 the "fingerprint" file and to its logs, write it without spaces. Now
27921 it will look like the fingerprints in our bridges documentation,
27922 and confuse fewer users.
27925 - Relays no longer publish a new server descriptor if they change
27926 their MaxAdvertisedBandwidth config option but it doesn't end up
27927 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
27928 fixes bug 1026. Patch from Sebastian.
27929 - Avoid leaking memory every time we get a create cell but we have
27930 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
27931 fixes bug 1034. Reported by BarkerJr.
27934 Changes in version 0.2.1.18 - 2009-07-24
27935 Tor 0.2.1.18 lays the foundations for performance improvements,
27936 adds status events to help users diagnose bootstrap problems, adds
27937 optional authentication/authorization for hidden services, fixes a
27938 variety of potential anonymity problems, and includes a huge pile of
27939 other features and bug fixes.
27942 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
27945 Changes in version 0.2.1.17-rc - 2009-07-07
27946 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
27947 candidate for the 0.2.1.x series. It lays the groundwork for further
27948 client performance improvements, and also fixes a big bug with directory
27949 authorities that were causing them to assign Guard and Stable flags
27952 The Windows bundles also finally include the geoip database that we
27953 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
27954 should actually install Torbutton rather than giving you a cryptic
27955 failure message (oops).
27958 - Clients now use the bandwidth values in the consensus, rather than
27959 the bandwidth values in each relay descriptor. This approach opens
27960 the door to more accurate bandwidth estimates once the directory
27961 authorities start doing active measurements. Implements more of
27965 - When Tor clients restart after 1-5 days, they discard all their
27966 cached descriptors as too old, but they still use the cached
27967 consensus document. This approach is good for robustness, but
27968 bad for performance: since they don't know any bandwidths, they
27969 end up choosing at random rather than weighting their choice by
27970 speed. Fixed by the above feature of putting bandwidths in the
27971 consensus. Bugfix on 0.2.0.x.
27972 - Directory authorities were neglecting to mark relays down in their
27973 internal histories if the relays fall off the routerlist without
27974 ever being found unreachable. So there were relays in the histories
27975 that haven't been seen for eight months, and are listed as being
27976 up for eight months. This wreaked havoc on the "median wfu"
27977 and "median mtbf" calculations, in turn making Guard and Stable
27978 flags very wrong, hurting network performance. Fixes bugs 696 and
27979 969. Bugfix on 0.2.0.6-alpha.
27982 - Serve the DirPortFrontPage page even when we have been approaching
27983 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
27984 - The control port would close the connection before flushing long
27985 replies, such as the network consensus, if a QUIT command was issued
27986 before the reply had completed. Now, the control port flushes all
27987 pending replies before closing the connection. Also fixed a spurious
27988 warning when a QUIT command is issued after a malformed or rejected
27989 AUTHENTICATE command, but before the connection was closed. Patch
27990 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
27991 - When we can't find an intro key for a v2 hidden service descriptor,
27992 fall back to the v0 hidden service descriptor and log a bug message.
27993 Workaround for bug 1024.
27994 - Fix a log message that did not respect the SafeLogging option.
27998 - If we're a relay and we change our IP address, be more verbose
27999 about the reason that made us change. Should help track down
28000 further bugs for relays on dynamic IP addresses.
28003 Changes in version 0.2.0.35 - 2009-06-24
28005 - Avoid crashing in the presence of certain malformed descriptors.
28006 Found by lark, and by automated fuzzing.
28007 - Fix an edge case where a malicious exit relay could convince a
28008 controller that the client's DNS question resolves to an internal IP
28009 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
28012 - Finally fix the bug where dynamic-IP relays disappear when their
28013 IP address changes: directory mirrors were mistakenly telling
28014 them their old address if they asked via begin_dir, so they
28015 never got an accurate answer about their new address, so they
28016 just vanished after a day. For belt-and-suspenders, relays that
28017 don't set Address in their config now avoid using begin_dir for
28018 all direct connections. Should fix bugs 827, 883, and 900.
28019 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
28020 that would occur on some exit nodes when DNS failures and timeouts
28021 occurred in certain patterns. Fix for bug 957.
28024 - When starting with a cache over a few days old, do not leak
28025 memory for the obsolete router descriptors in it. Bugfix on
28026 0.2.0.33; fixes bug 672.
28027 - Hidden service clients didn't use a cached service descriptor that
28028 was older than 15 minutes, but wouldn't fetch a new one either,
28029 because there was already one in the cache. Now, fetch a v2
28030 descriptor unless the same descriptor was added to the cache within
28031 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
28034 Changes in version 0.2.1.16-rc - 2009-06-20
28035 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
28036 a bunch of minor bugs.
28039 - Fix an edge case where a malicious exit relay could convince a
28040 controller that the client's DNS question resolves to an internal IP
28041 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
28043 o Major performance improvements (on 0.2.0.x):
28044 - Disable and refactor some debugging checks that forced a linear scan
28045 over the whole server-side DNS cache. These accounted for over 50%
28046 of CPU time on a relatively busy exit node's gprof profile. Found
28048 - Disable some debugging checks that appeared in exit node profile
28052 - Update to the "June 3 2009" ip-to-country file.
28053 - Do not have tor-resolve automatically refuse all .onion addresses;
28054 if AutomapHostsOnResolve is set in your torrc, this will work fine.
28056 o Minor bugfixes (on 0.2.0.x):
28057 - Log correct error messages for DNS-related network errors on
28059 - Fix a race condition that could cause crashes or memory corruption
28060 when running as a server with a controller listening for log
28062 - Avoid crashing when we have a policy specified in a DirPolicy or
28063 SocksPolicy or ReachableAddresses option with ports set on it,
28064 and we re-load the policy. May fix bug 996.
28065 - Hidden service clients didn't use a cached service descriptor that
28066 was older than 15 minutes, but wouldn't fetch a new one either,
28067 because there was already one in the cache. Now, fetch a v2
28068 descriptor unless the same descriptor was added to the cache within
28069 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
28071 o Minor bugfixes (on 0.2.1.x):
28072 - Don't warn users about low port and hibernation mix when they
28073 provide a *ListenAddress directive to fix that. Bugfix on
28075 - When switching back and forth between bridge mode, do not start
28076 gathering GeoIP data until two hours have passed.
28077 - Do not complain that the user has requested an excluded node as
28078 an exit when the node is not really an exit. This could happen
28079 because the circuit was for testing, or an introduction point.
28083 Changes in version 0.2.1.15-rc - 2009-05-25
28084 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
28085 series. It fixes a major bug on fast exit relays, as well as a variety
28086 of more minor bugs.
28088 o Major bugfixes (on 0.2.0.x):
28089 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
28090 that would occur on some exit nodes when DNS failures and timeouts
28091 occurred in certain patterns. Fix for bug 957.
28093 o Minor bugfixes (on 0.2.0.x):
28094 - Actually return -1 in the error case for read_bandwidth_usage().
28095 Harmless bug, since we currently don't care about the return value
28096 anywhere. Bugfix on 0.2.0.9-alpha.
28097 - Provide a more useful log message if bug 977 (related to buffer
28098 freelists) ever reappears, and do not crash right away.
28099 - Fix an assertion failure on 64-bit platforms when we allocated
28100 memory right up to the end of a memarea, then realigned the memory
28101 one step beyond the end. Fixes a possible cause of bug 930.
28102 - Protect the count of open sockets with a mutex, so we can't
28103 corrupt it when two threads are closing or opening sockets at once.
28104 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
28105 - Don't allow a bridge to publish its router descriptor to a
28106 non-bridge directory authority. Fixes part of bug 932.
28107 - When we change to or from being a bridge, reset our counts of
28108 client usage by country. Fixes bug 932.
28109 - Fix a bug that made stream bandwidth get misreported to the
28111 - Stop using malloc_usable_size() to use more area than we had
28112 actually allocated: it was safe, but made valgrind really unhappy.
28113 - Fix a memory leak when v3 directory authorities load their keys
28114 and cert from disk. Bugfix on 0.2.0.1-alpha.
28116 o Minor bugfixes (on 0.2.1.x):
28117 - Fix use of freed memory when deciding to mark a non-addable
28118 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
28121 Changes in version 0.2.1.14-rc - 2009-04-12
28122 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
28123 series. It begins fixing some major performance problems, and also
28124 finally addresses the bug that was causing relays on dynamic IP
28125 addresses to fall out of the directory.
28128 - Clients replace entry guards that were chosen more than a few months
28129 ago. This change should significantly improve client performance,
28130 especially once more people upgrade, since relays that have been
28131 a guard for a long time are currently overloaded.
28133 o Major bugfixes (on 0.2.0):
28134 - Finally fix the bug where dynamic-IP relays disappear when their
28135 IP address changes: directory mirrors were mistakenly telling
28136 them their old address if they asked via begin_dir, so they
28137 never got an accurate answer about their new address, so they
28138 just vanished after a day. For belt-and-suspenders, relays that
28139 don't set Address in their config now avoid using begin_dir for
28140 all direct connections. Should fix bugs 827, 883, and 900.
28141 - Relays were falling out of the networkstatus consensus for
28142 part of a day if they changed their local config but the
28143 authorities discarded their new descriptor as "not sufficiently
28144 different". Now directory authorities accept a descriptor as changed
28145 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
28146 patch by Sebastian.
28147 - Avoid crashing in the presence of certain malformed descriptors.
28148 Found by lark, and by automated fuzzing.
28151 - When generating circuit events with verbose nicknames for
28152 controllers, try harder to look up nicknames for routers on a
28153 circuit. (Previously, we would look in the router descriptors we had
28154 for nicknames, but not in the consensus.) Partial fix for bug 941.
28155 - If the bridge config line doesn't specify a port, assume 443.
28156 This makes bridge lines a bit smaller and easier for users to
28158 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
28159 bytes (aka 20KB/s), to match our documentation. Also update
28160 directory authorities so they always assign the Fast flag to relays
28161 with 20KB/s of capacity. Now people running relays won't suddenly
28162 find themselves not seeing any use, if the network gets faster
28164 - Update to the "April 3 2009" ip-to-country file.
28167 - Avoid trying to print raw memory to the logs when we decide to
28168 give up on downloading a given relay descriptor. Bugfix on
28170 - In tor-resolve, when the Tor client to use is specified by
28171 <hostname>:<port>, actually use the specified port rather than
28172 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
28173 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
28174 - When starting with a cache over a few days old, do not leak
28175 memory for the obsolete router descriptors in it. Bugfix on
28177 - Avoid double-free on list of successfully uploaded hidden
28178 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
28179 - Change memarea_strndup() implementation to work even when
28180 duplicating a string at the end of a page. This bug was
28181 harmless for now, but could have meant crashes later. Fix by
28182 lark. Bugfix on 0.2.1.1-alpha.
28183 - Limit uploaded directory documents to be 16M rather than 500K.
28184 The directory authorities were refusing v3 consensus votes from
28185 other authorities, since the votes are now 504K. Fixes bug 959;
28186 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
28187 - Directory authorities should never send a 503 "busy" response to
28188 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
28192 Changes in version 0.2.1.13-alpha - 2009-03-09
28193 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
28194 cleanups. We're finally getting close to a release candidate.
28197 - Correctly update the list of which countries we exclude as
28198 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
28199 lark. Bugfix on 0.2.1.6-alpha.
28201 o Minor bugfixes (on 0.2.0.x and earlier):
28202 - Automatically detect MacOSX versions earlier than 10.4.0, and
28203 disable kqueue from inside Tor when running with these versions.
28204 We previously did this from the startup script, but that was no
28205 help to people who didn't use the startup script. Resolves bug 863.
28206 - When we had picked an exit node for a connection, but marked it as
28207 "optional", and it turned out we had no onion key for the exit,
28208 stop wanting that exit and try again. This situation may not
28209 be possible now, but will probably become feasible with proposal
28210 158. Spotted by rovv. Fixes another case of bug 752.
28211 - Clients no longer cache certificates for authorities they do not
28212 recognize. Bugfix on 0.2.0.9-alpha.
28213 - When we can't transmit a DNS request due to a network error, retry
28214 it after a while, and eventually transmit a failing response to
28215 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
28216 - If the controller claimed responsibility for a stream, but that
28217 stream never finished making its connection, it would live
28218 forever in circuit_wait state. Now we close it after SocksTimeout
28219 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
28220 - Drop begin cells to a hidden service if they come from the middle
28221 of a circuit. Patch from lark.
28222 - When we erroneously receive two EXTEND cells for the same circuit
28223 ID on the same connection, drop the second. Patch from lark.
28224 - Fix a crash that occurs on exit nodes when a nameserver request
28225 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
28226 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
28228 - Do not assume that a stack-allocated character array will be
28229 64-bit aligned on platforms that demand that uint64_t access is
28230 aligned. Possible fix for bug 604.
28231 - Parse dates and IPv4 addresses in a locale- and libc-independent
28232 manner, to avoid platform-dependent behavior on malformed input.
28233 - Build correctly when configured to build outside the main source
28234 path. Patch from Michael Gold.
28235 - We were already rejecting relay begin cells with destination port
28236 of 0. Now also reject extend cells with destination port or address
28237 of 0. Suggested by lark.
28239 o Minor bugfixes (on 0.2.1.x):
28240 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
28241 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
28242 - If we're an exit node, scrub the IP address to which we are exiting
28243 in the logs. Bugfix on 0.2.1.8-alpha.
28246 - On Linux, use the prctl call to re-enable core dumps when the user
28248 - New controller event NEWCONSENSUS that lists the networkstatus
28249 lines for every recommended relay. Now controllers like Torflow
28250 can keep up-to-date on which relays they should be using.
28251 - Update to the "February 26 2009" ip-to-country file.
28254 Changes in version 0.2.0.34 - 2009-02-08
28255 Tor 0.2.0.34 features several more security-related fixes. You should
28256 upgrade, especially if you run an exit relay (remote crash) or a
28257 directory authority (remote infinite loop), or you're on an older
28258 (pre-XP) or not-recently-patched Windows (remote exploit).
28260 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
28261 have many known flaws, and nobody should be using them. You should
28262 upgrade. If you're using a Linux or BSD and its packages are obsolete,
28263 stop using those packages and upgrade anyway.
28266 - Fix an infinite-loop bug on handling corrupt votes under certain
28267 circumstances. Bugfix on 0.2.0.8-alpha.
28268 - Fix a temporary DoS vulnerability that could be performed by
28269 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
28270 - Avoid a potential crash on exit nodes when processing malformed
28271 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
28272 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
28273 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
28276 - Fix compilation on systems where time_t is a 64-bit integer.
28277 Patch from Matthias Drochner.
28278 - Don't consider expiring already-closed client connections. Fixes
28279 bug 893. Bugfix on 0.0.2pre20.
28282 Changes in version 0.2.1.12-alpha - 2009-02-08
28283 Tor 0.2.1.12-alpha features several more security-related fixes. You
28284 should upgrade, especially if you run an exit relay (remote crash) or
28285 a directory authority (remote infinite loop), or you're on an older
28286 (pre-XP) or not-recently-patched Windows (remote exploit). It also
28287 includes a big pile of minor bugfixes and cleanups.
28290 - Fix an infinite-loop bug on handling corrupt votes under certain
28291 circumstances. Bugfix on 0.2.0.8-alpha.
28292 - Fix a temporary DoS vulnerability that could be performed by
28293 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
28294 - Avoid a potential crash on exit nodes when processing malformed
28295 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
28298 - Let controllers actually ask for the "clients_seen" event for
28299 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
28300 reported by Matt Edman.
28301 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
28303 - Fix a bug in address parsing that was preventing bridges or hidden
28304 service targets from being at IPv6 addresses.
28305 - Solve a bug that kept hardware crypto acceleration from getting
28306 enabled when accounting was turned on. Fixes bug 907. Bugfix on
28308 - Remove a bash-ism from configure.in to build properly on non-Linux
28309 platforms. Bugfix on 0.2.1.1-alpha.
28310 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
28311 headers. Bugfix on 0.2.0.10-alpha.
28312 - Don't consider expiring already-closed client connections. Fixes
28313 bug 893. Bugfix on 0.0.2pre20.
28314 - Fix another interesting corner-case of bug 891 spotted by rovv:
28315 Previously, if two hosts had different amounts of clock drift, and
28316 one of them created a new connection with just the wrong timing,
28317 the other might decide to deprecate the new connection erroneously.
28318 Bugfix on 0.1.1.13-alpha.
28319 - Resolve a very rare crash bug that could occur when the user forced
28320 a nameserver reconfiguration during the middle of a nameserver
28321 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
28322 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
28323 Bugfix on 0.2.1.7-alpha.
28324 - If we're using bridges and our network goes away, be more willing
28325 to forgive our bridges and try again when we get an application
28326 request. Bugfix on 0.2.0.x.
28329 - Support platforms where time_t is 64 bits long. (Congratulations,
28330 NetBSD!) Patch from Matthias Drochner.
28331 - Add a 'getinfo status/clients-seen' controller command, in case
28332 controllers want to hear clients_seen events but connect late.
28335 - Disable GCC's strict alias optimization by default, to avoid the
28336 likelihood of its introducing subtle bugs whenever our code violates
28337 the letter of C99's alias rules.
28340 Changes in version 0.2.0.33 - 2009-01-21
28341 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
28342 useful to users. It also finally fixes a bug where a relay or client
28343 that's been off for many days would take a long time to bootstrap.
28345 This update also fixes an important security-related bug reported by
28346 Ilja van Sprundel. You should upgrade. (We'll send out more details
28347 about the bug once people have had some time to upgrade.)
28350 - Fix a heap-corruption bug that may be remotely triggerable on
28351 some platforms. Reported by Ilja van Sprundel.
28354 - When a stream at an exit relay is in state "resolving" or
28355 "connecting" and it receives an "end" relay cell, the exit relay
28356 would silently ignore the end cell and not close the stream. If
28357 the client never closes the circuit, then the exit relay never
28358 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
28359 reported by "wood".
28360 - When sending CREATED cells back for a given circuit, use a 64-bit
28361 connection ID to find the right connection, rather than an addr:port
28362 combination. Now that we can have multiple OR connections between
28363 the same ORs, it is no longer possible to use addr:port to uniquely
28364 identify a connection.
28365 - Bridge relays that had DirPort set to 0 would stop fetching
28366 descriptors shortly after startup, and then briefly resume
28367 after a new bandwidth test and/or after publishing a new bridge
28368 descriptor. Bridge users that try to bootstrap from them would
28369 get a recent networkstatus but would get descriptors from up to
28370 18 hours earlier, meaning most of the descriptors were obsolete
28371 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
28372 - Prevent bridge relays from serving their 'extrainfo' document
28373 to anybody who asks, now that extrainfo docs include potentially
28374 sensitive aggregated client geoip summaries. Bugfix on
28376 - If the cached networkstatus consensus is more than five days old,
28377 discard it rather than trying to use it. In theory it could be
28378 useful because it lists alternate directory mirrors, but in practice
28379 it just means we spend many minutes trying directory mirrors that
28380 are long gone from the network. Also discard router descriptors as
28381 we load them if they are more than five days old, since the onion
28382 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
28385 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
28386 could make gcc generate non-functional binary search code. Bugfix
28388 - Build correctly on platforms without socklen_t.
28389 - Compile without warnings on solaris.
28390 - Avoid potential crash on internal error during signature collection.
28391 Fixes bug 864. Patch from rovv.
28392 - Correct handling of possible malformed authority signing key
28393 certificates with internal signature types. Fixes bug 880.
28394 Bugfix on 0.2.0.3-alpha.
28395 - Fix a hard-to-trigger resource leak when logging credential status.
28397 - When we can't initialize DNS because the network is down, do not
28398 automatically stop Tor from starting. Instead, we retry failed
28399 dns_init() every 10 minutes, and change the exit policy to reject
28400 *:* until one succeeds. Fixes bug 691.
28401 - Use 64 bits instead of 32 bits for connection identifiers used with
28402 the controller protocol, to greatly reduce risk of identifier reuse.
28403 - When we're choosing an exit node for a circuit, and we have
28404 no pending streams, choose a good general exit rather than one that
28405 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
28406 - Fix another case of assuming, when a specific exit is requested,
28407 that we know more than the user about what hosts it allows.
28408 Fixes one case of bug 752. Patch from rovv.
28409 - Clip the MaxCircuitDirtiness config option to a minimum of 10
28410 seconds. Warn the user if lower values are given in the
28411 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
28412 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
28413 user if lower values are given in the configuration. Bugfix on
28414 0.1.1.17-rc. Patch by Sebastian.
28415 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
28416 the cache because we already had a v0 descriptor with the same ID.
28417 Bugfix on 0.2.0.18-alpha.
28418 - Fix a race condition when freeing keys shared between main thread
28419 and CPU workers that could result in a memory leak. Bugfix on
28420 0.1.0.1-rc. Fixes bug 889.
28421 - Send a valid END cell back when a client tries to connect to a
28422 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
28423 840. Patch from rovv.
28424 - Check which hops rendezvous stream cells are associated with to
28425 prevent possible guess-the-streamid injection attacks from
28426 intermediate hops. Fixes another case of bug 446. Based on patch
28428 - If a broken client asks a non-exit router to connect somewhere,
28429 do not even do the DNS lookup before rejecting the connection.
28430 Fixes another case of bug 619. Patch from rovv.
28431 - When a relay gets a create cell it can't decrypt (e.g. because it's
28432 using the wrong onion key), we were dropping it and letting the
28433 client time out. Now actually answer with a destroy cell. Fixes
28434 bug 904. Bugfix on 0.0.2pre8.
28436 o Minor bugfixes (hidden services):
28437 - Do not throw away existing introduction points on SIGHUP. Bugfix on
28438 0.0.6pre1. Patch by Karsten. Fixes bug 874.
28441 - Report the case where all signatures in a detached set are rejected
28442 differently than the case where there is an error handling the
28444 - When we realize that another process has modified our cached
28445 descriptors, print out a more useful error message rather than
28446 triggering an assertion. Fixes bug 885. Patch from Karsten.
28447 - Implement the 0x20 hack to better resist DNS poisoning: set the
28448 case on outgoing DNS requests randomly, and reject responses that do
28449 not match the case correctly. This logic can be disabled with the
28450 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
28451 of servers that do not reliably preserve case in replies. See
28452 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
28454 - Check DNS replies for more matching fields to better resist DNS
28456 - Never use OpenSSL compression: it wastes RAM and CPU trying to
28457 compress cells, which are basically all encrypted, compressed, or
28461 Changes in version 0.2.1.11-alpha - 2009-01-20
28462 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
28463 week it will take a long time to bootstrap again" bug. It also fixes
28464 an important security-related bug reported by Ilja van Sprundel. You
28465 should upgrade. (We'll send out more details about the bug once people
28466 have had some time to upgrade.)
28469 - Fix a heap-corruption bug that may be remotely triggerable on
28470 some platforms. Reported by Ilja van Sprundel.
28473 - Discard router descriptors as we load them if they are more than
28474 five days old. Otherwise if Tor is off for a long time and then
28475 starts with cached descriptors, it will try to use the onion
28476 keys in those obsolete descriptors when building circuits. Bugfix
28477 on 0.2.0.x. Fixes bug 887.
28480 - Try to make sure that the version of Libevent we're running with
28481 is binary-compatible with the one we built with. May address bug
28483 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
28484 for bug 905. Bugfix on 0.2.1.7-alpha.
28485 - Add a new --enable-local-appdata configuration switch to change
28486 the default location of the datadir on win32 from APPDATA to
28487 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
28488 entirely. Patch from coderman.
28491 - Make outbound DNS packets respect the OutboundBindAddress setting.
28492 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
28493 - When our circuit fails at the first hop (e.g. we get a destroy
28494 cell back), avoid using that OR connection anymore, and also
28495 tell all the one-hop directory requests waiting for it that they
28496 should fail. Bugfix on 0.2.1.3-alpha.
28497 - In the torify(1) manpage, mention that tsocks will leak your
28501 Changes in version 0.2.1.10-alpha - 2009-01-06
28502 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
28503 would make the bridge relay not so useful if it had DirPort set to 0,
28504 and one that could let an attacker learn a little bit of information
28505 about the bridge's users), and a bug that would cause your Tor relay
28506 to ignore a circuit create request it can't decrypt (rather than reply
28507 with an error). It also fixes a wide variety of other bugs.
28510 - If the cached networkstatus consensus is more than five days old,
28511 discard it rather than trying to use it. In theory it could
28512 be useful because it lists alternate directory mirrors, but in
28513 practice it just means we spend many minutes trying directory
28514 mirrors that are long gone from the network. Helps bug 887 a bit;
28516 - Bridge relays that had DirPort set to 0 would stop fetching
28517 descriptors shortly after startup, and then briefly resume
28518 after a new bandwidth test and/or after publishing a new bridge
28519 descriptor. Bridge users that try to bootstrap from them would
28520 get a recent networkstatus but would get descriptors from up to
28521 18 hours earlier, meaning most of the descriptors were obsolete
28522 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
28523 - Prevent bridge relays from serving their 'extrainfo' document
28524 to anybody who asks, now that extrainfo docs include potentially
28525 sensitive aggregated client geoip summaries. Bugfix on
28529 - New controller event "clients_seen" to report a geoip-based summary
28530 of which countries we've seen clients from recently. Now controllers
28531 like Vidalia can show bridge operators that they're actually making
28533 - Build correctly against versions of OpenSSL 0.9.8 or later built
28534 without support for deprecated functions.
28535 - Update to the "December 19 2008" ip-to-country file.
28537 o Minor bugfixes (on 0.2.0.x):
28538 - Authorities now vote for the Stable flag for any router whose
28539 weighted MTBF is at least 5 days, regardless of the mean MTBF.
28540 - Do not remove routers as too old if we do not have any consensus
28541 document. Bugfix on 0.2.0.7-alpha.
28542 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
28543 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
28544 - When an exit relay resolves a stream address to a local IP address,
28545 do not just keep retrying that same exit relay over and
28546 over. Instead, just close the stream. Addresses bug 872. Bugfix
28547 on 0.2.0.32. Patch from rovv.
28548 - If a hidden service sends us an END cell, do not consider
28549 retrying the connection; just close it. Patch from rovv.
28550 - When we made bridge authorities stop serving bridge descriptors over
28551 unencrypted links, we also broke DirPort reachability testing for
28552 bridges. So bridges with a non-zero DirPort were printing spurious
28553 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
28554 - When a relay gets a create cell it can't decrypt (e.g. because it's
28555 using the wrong onion key), we were dropping it and letting the
28556 client time out. Now actually answer with a destroy cell. Fixes
28557 bug 904. Bugfix on 0.0.2pre8.
28558 - Squeeze 2-5% out of client performance (according to oprofile) by
28559 improving the implementation of some policy-manipulation functions.
28561 o Minor bugfixes (on 0.2.1.x):
28562 - Make get_interface_address() function work properly again; stop
28563 guessing the wrong parts of our address as our address.
28564 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
28565 send on that circuit. Otherwise we might violate the proposal-110
28566 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
28568 - When we're sending non-EXTEND cells to the first hop in a circuit,
28569 for example to use an encrypted directory connection, we don't need
28570 to use RELAY_EARLY cells: the first hop knows what kind of cell
28571 it is, and nobody else can even see the cell type. Conserving
28572 RELAY_EARLY cells makes it easier to cannibalize circuits like
28574 - Stop logging nameserver addresses in reverse order.
28575 - If we are retrying a directory download slowly over and over, do
28576 not automatically give up after the 254th failure. Bugfix on
28578 - Resume reporting accurate "stream end" reasons to the local control
28579 port. They were lost in the changes for Proposal 148. Bugfix on
28582 o Deprecated and removed features:
28583 - The old "tor --version --version" command, which would print out
28584 the subversion "Id" of most of the source files, is now removed. It
28585 turned out to be less useful than we'd expected, and harder to
28588 o Code simplifications and refactoring:
28589 - Change our header file guard macros to be less likely to conflict
28590 with system headers. Adam Langley noticed that we were conflicting
28591 with log.h on Android.
28592 - Tool-assisted documentation cleanup. Nearly every function or
28593 static variable in Tor should have its own documentation now.
28596 Changes in version 0.2.1.9-alpha - 2008-12-25
28597 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
28599 o New directory authorities:
28600 - gabelmoo (the authority run by Karsten Loesing) now has a new
28604 - Never use a connection with a mismatched address to extend a
28605 circuit, unless that connection is canonical. A canonical
28606 connection is one whose address is authenticated by the router's
28607 identity key, either in a NETINFO cell or in a router descriptor.
28608 - Avoid a possible memory corruption bug when receiving hidden service
28609 descriptors. Bugfix on 0.2.1.6-alpha.
28612 - Fix a logic error that would automatically reject all but the first
28613 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
28614 part of bug 813/868. Bug spotted by coderman.
28615 - When a stream at an exit relay is in state "resolving" or
28616 "connecting" and it receives an "end" relay cell, the exit relay
28617 would silently ignore the end cell and not close the stream. If
28618 the client never closes the circuit, then the exit relay never
28619 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
28620 reported by "wood".
28621 - When we can't initialize DNS because the network is down, do not
28622 automatically stop Tor from starting. Instead, retry failed
28623 dns_init() every 10 minutes, and change the exit policy to reject
28624 *:* until one succeeds. Fixes bug 691.
28627 - Give a better error message when an overzealous init script says
28628 "sudo -u username tor --user username". Makes Bug 882 easier for
28630 - When a directory authority gives us a new guess for our IP address,
28631 log which authority we used. Hopefully this will help us debug
28632 the recent complaints about bad IP address guesses.
28633 - Detect svn revision properly when we're using git-svn.
28634 - Try not to open more than one descriptor-downloading connection
28635 to an authority at once. This should reduce load on directory
28636 authorities. Fixes bug 366.
28637 - Add cross-certification to newly generated certificates, so that
28638 a signing key is enough information to look up a certificate.
28639 Partial implementation of proposal 157.
28640 - Start serving certificates by <identity digest, signing key digest>
28641 pairs. Partial implementation of proposal 157.
28642 - Clients now never report any stream end reason except 'MISC'.
28643 Implements proposal 148.
28644 - On platforms with a maximum syslog string length, truncate syslog
28645 messages to that length ourselves, rather than relying on the
28646 system to do it for us.
28647 - Optimize out calls to time(NULL) that occur for every IO operation,
28648 or for every cell. On systems where time() is a slow syscall,
28649 this fix will be slightly helpful.
28650 - Exit servers can now answer resolve requests for ip6.arpa addresses.
28651 - When we download a descriptor that we then immediately (as
28652 a directory authority) reject, do not retry downloading it right
28653 away. Should save some bandwidth on authorities. Fix for bug
28654 888. Patch by Sebastian Hahn.
28655 - When a download gets us zero good descriptors, do not notify
28656 Tor that new directory information has arrived.
28657 - Avoid some nasty corner cases in the logic for marking connections
28658 as too old or obsolete or noncanonical for circuits. Partial
28661 o Minor features (controller):
28662 - New CONSENSUS_ARRIVED event to note when a new consensus has
28663 been fetched and validated.
28664 - When we realize that another process has modified our cached
28665 descriptors file, print out a more useful error message rather
28666 than triggering an assertion. Fixes bug 885. Patch from Karsten.
28667 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
28668 controllers to prevent SIGHUP from reloading the
28669 configuration. Fixes bug 856.
28672 - Resume using the correct "REASON=" stream when telling the
28673 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
28674 - When a canonical connection appears later in our internal list
28675 than a noncanonical one for a given OR ID, always use the
28676 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
28678 - Clip the MaxCircuitDirtiness config option to a minimum of 10
28679 seconds. Warn the user if lower values are given in the
28680 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
28681 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
28682 user if lower values are given in the configuration. Bugfix on
28683 0.1.1.17-rc. Patch by Sebastian.
28684 - Fix a race condition when freeing keys shared between main thread
28685 and CPU workers that could result in a memory leak. Bugfix on
28686 0.1.0.1-rc. Fixes bug 889.
28688 o Minor bugfixes (hidden services):
28689 - Do not throw away existing introduction points on SIGHUP (bugfix on
28690 0.0.6pre1); also, do not stall hidden services because we're
28691 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
28692 by John Brooks. Patch by Karsten. Fixes bug 874.
28693 - Fix a memory leak when we decline to add a v2 rendezvous
28694 descriptor to the cache because we already had a v0 descriptor
28695 with the same ID. Bugfix on 0.2.0.18-alpha.
28697 o Deprecated and removed features:
28698 - RedirectExits has been removed. It was deprecated since
28700 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
28701 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
28702 - Cell pools are now always enabled; --disable-cell-pools is ignored.
28704 o Code simplifications and refactoring:
28705 - Rename the confusing or_is_obsolete field to the more appropriate
28706 is_bad_for_new_circs, and move it to or_connection_t where it
28708 - Move edge-only flags from connection_t to edge_connection_t: not
28709 only is this better coding, but on machines of plausible alignment,
28710 it should save 4-8 bytes per connection_t. "Every little bit helps."
28711 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
28712 for consistency; keep old option working for backward compatibility.
28713 - Simplify the code for finding connections to use for a circuit.
28716 Changes in version 0.2.1.8-alpha - 2008-12-08
28717 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
28718 builds better on unusual platforms like Solaris and old OS X, and
28719 fixes a variety of other issues.
28722 - New DirPortFrontPage option that takes an html file and publishes
28723 it as "/" on the DirPort. Now relay operators can provide a
28724 disclaimer without needing to set up a separate webserver. There's
28725 a sample disclaimer in contrib/tor-exit-notice.html.
28728 - When the client is choosing entry guards, now it selects at most
28729 one guard from a given relay family. Otherwise we could end up with
28730 all of our entry points into the network run by the same operator.
28731 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
28734 - Fix a DOS opportunity during the voting signature collection process
28735 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
28736 - Fix a possible segfault when establishing an exit connection. Bugfix
28740 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
28742 - Made Tor a little less aggressive about deleting expired
28743 certificates. Partial fix for bug 854.
28744 - Stop doing unaligned memory access that generated bus errors on
28745 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
28746 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
28747 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
28748 - Make USR2 log-level switch take effect immediately. Bugfix on
28750 - If one win32 nameserver fails to get added, continue adding the
28751 rest, and don't automatically fail.
28752 - Use fcntl() for locking when flock() is not available. Should fix
28753 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
28754 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
28755 could make gcc generate non-functional binary search code. Bugfix
28757 - Build correctly on platforms without socklen_t.
28758 - Avoid potential crash on internal error during signature collection.
28759 Fixes bug 864. Patch from rovv.
28760 - Do not use C's stdio library for writing to log files. This will
28761 improve logging performance by a minute amount, and will stop
28762 leaking fds when our disk is full. Fixes bug 861.
28763 - Stop erroneous use of O_APPEND in cases where we did not in fact
28764 want to re-seek to the end of a file before every last write().
28765 - Correct handling of possible malformed authority signing key
28766 certificates with internal signature types. Fixes bug 880. Bugfix
28768 - Fix a hard-to-trigger resource leak when logging credential status.
28772 - Directory mirrors no longer fetch the v1 directory or
28773 running-routers files. They are obsolete, and nobody asks for them
28774 anymore. This is the first step to making v1 authorities obsolete.
28776 o Minor features (controller):
28777 - Return circuit purposes in response to GETINFO circuit-status. Fixes
28781 Changes in version 0.2.0.32 - 2008-11-20
28782 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
28783 packages (and maybe other packages) noticed by Theo de Raadt, fixes
28784 a smaller security flaw that might allow an attacker to access local
28785 services, further improves hidden service performance, and fixes a
28786 variety of other issues.
28789 - The "User" and "Group" config options did not clear the
28790 supplementary group entries for the Tor process. The "User" option
28791 is now more robust, and we now set the groups to the specified
28792 user's primary group. The "Group" option is now ignored. For more
28793 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
28794 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
28795 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
28796 - The "ClientDNSRejectInternalAddresses" config option wasn't being
28797 consistently obeyed: if an exit relay refuses a stream because its
28798 exit policy doesn't allow it, we would remember what IP address
28799 the relay said the destination address resolves to, even if it's
28800 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
28803 - Fix a DOS opportunity during the voting signature collection process
28804 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
28806 o Major bugfixes (hidden services):
28807 - When fetching v0 and v2 rendezvous service descriptors in parallel,
28808 we were failing the whole hidden service request when the v0
28809 descriptor fetch fails, even if the v2 fetch is still pending and
28810 might succeed. Similarly, if the last v2 fetch fails, we were
28811 failing the whole hidden service request even if a v0 fetch is
28812 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
28813 - When extending a circuit to a hidden service directory to upload a
28814 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
28815 requests failed, because the router descriptor has not been
28816 downloaded yet. In these cases, do not attempt to upload the
28817 rendezvous descriptor, but wait until the router descriptor is
28818 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
28819 descriptor from a hidden service directory for which the router
28820 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
28824 - Fix several infrequent memory leaks spotted by Coverity.
28825 - When testing for libevent functions, set the LDFLAGS variable
28826 correctly. Found by Riastradh.
28827 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
28828 bootstrapping with tunneled directory connections. Bugfix on
28829 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
28830 - When asked to connect to A.B.exit:80, if we don't know the IP for A
28831 and we know that server B rejects most-but-not all connections to
28832 port 80, we would previously reject the connection. Now, we assume
28833 the user knows what they were asking for. Fixes bug 752. Bugfix
28834 on 0.0.9rc5. Diagnosed by BarkerJr.
28835 - If we overrun our per-second write limits a little, count this as
28836 having used up our write allocation for the second, and choke
28837 outgoing directory writes. Previously, we had only counted this when
28838 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
28839 Bugfix on 0.2.0.x (??).
28840 - Remove the old v2 directory authority 'lefkada' from the default
28841 list. It has been gone for many months.
28842 - Stop doing unaligned memory access that generated bus errors on
28843 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
28844 - Make USR2 log-level switch take effect immediately. Bugfix on
28847 o Minor bugfixes (controller):
28848 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
28849 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
28852 Changes in version 0.2.1.7-alpha - 2008-11-08
28853 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
28854 packages (and maybe other packages) noticed by Theo de Raadt, fixes
28855 a smaller security flaw that might allow an attacker to access local
28856 services, adds better defense against DNS poisoning attacks on exit
28857 relays, further improves hidden service performance, and fixes a
28858 variety of other issues.
28861 - The "ClientDNSRejectInternalAddresses" config option wasn't being
28862 consistently obeyed: if an exit relay refuses a stream because its
28863 exit policy doesn't allow it, we would remember what IP address
28864 the relay said the destination address resolves to, even if it's
28865 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
28866 - The "User" and "Group" config options did not clear the
28867 supplementary group entries for the Tor process. The "User" option
28868 is now more robust, and we now set the groups to the specified
28869 user's primary group. The "Group" option is now ignored. For more
28870 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
28871 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
28872 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
28873 - Do not use or believe expired v3 authority certificates. Patch
28874 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
28877 - Now NodeFamily and MyFamily config options allow spaces in
28878 identity fingerprints, so it's easier to paste them in.
28879 Suggested by Lucky Green.
28880 - Implement the 0x20 hack to better resist DNS poisoning: set the
28881 case on outgoing DNS requests randomly, and reject responses that do
28882 not match the case correctly. This logic can be disabled with the
28883 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
28884 of servers that do not reliably preserve case in replies. See
28885 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
28887 - Preserve case in replies to DNSPort requests in order to support
28888 the 0x20 hack for resisting DNS poisoning attacks.
28890 o Hidden service performance improvements:
28891 - When the client launches an introduction circuit, retry with a
28892 new circuit after 30 seconds rather than 60 seconds.
28893 - Launch a second client-side introduction circuit in parallel
28894 after a delay of 15 seconds (based on work by Christian Wilms).
28895 - Hidden services start out building five intro circuits rather
28896 than three, and when the first three finish they publish a service
28897 descriptor using those. Now we publish our service descriptor much
28898 faster after restart.
28901 - Minor fix in the warning messages when you're having problems
28902 bootstrapping; also, be more forgiving of bootstrap problems when
28903 we're still making incremental progress on a given bootstrap phase.
28904 - When we're choosing an exit node for a circuit, and we have
28905 no pending streams, choose a good general exit rather than one that
28906 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
28907 - Send a valid END cell back when a client tries to connect to a
28908 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
28909 840. Patch from rovv.
28910 - If a broken client asks a non-exit router to connect somewhere,
28911 do not even do the DNS lookup before rejecting the connection.
28912 Fixes another case of bug 619. Patch from rovv.
28913 - Fix another case of assuming, when a specific exit is requested,
28914 that we know more than the user about what hosts it allows.
28915 Fixes another case of bug 752. Patch from rovv.
28916 - Check which hops rendezvous stream cells are associated with to
28917 prevent possible guess-the-streamid injection attacks from
28918 intermediate hops. Fixes another case of bug 446. Based on patch
28920 - Avoid using a negative right-shift when comparing 32-bit
28921 addresses. Possible fix for bug 845 and bug 811.
28922 - Make the assert_circuit_ok() function work correctly on circuits that
28923 have already been marked for close.
28924 - Fix read-off-the-end-of-string error in unit tests when decoding
28925 introduction points.
28926 - Fix uninitialized size field for memory area allocation: may improve
28927 memory performance during directory parsing.
28928 - Treat duplicate certificate fetches as failures, so that we do
28929 not try to re-fetch an expired certificate over and over and over.
28930 - Do not say we're fetching a certificate when we'll in fact skip it
28931 because of a pending download.
28934 Changes in version 0.2.1.6-alpha - 2008-09-30
28935 Tor 0.2.1.6-alpha further improves performance and robustness of
28936 hidden services, starts work on supporting per-country relay selection,
28937 and fixes a variety of smaller issues.
28940 - Implement proposal 121: make it possible to build hidden services
28941 that only certain clients are allowed to connect to. This is
28942 enforced at several points, so that unauthorized clients are unable
28943 to send INTRODUCE cells to the service, or even (depending on the
28944 type of authentication) to learn introduction points. This feature
28945 raises the bar for certain kinds of active attacks against hidden
28946 services. Code by Karsten Loesing.
28947 - Relays now store and serve v2 hidden service descriptors by default,
28948 i.e., the new default value for HidServDirectoryV2 is 1. This is
28949 the last step in proposal 114, which aims to make hidden service
28950 lookups more reliable.
28951 - Start work to allow node restrictions to include country codes. The
28952 syntax to exclude nodes in a country with country code XX is
28953 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
28954 refinement to decide what config options should take priority if
28955 you ask to both use a particular node and exclude it.
28956 - Allow ExitNodes list to include IP ranges and country codes, just
28957 like the Exclude*Nodes lists. Patch from Robert Hogan.
28960 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
28961 Tor to fail to start if you had it configured to use a bridge
28962 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
28963 - When extending a circuit to a hidden service directory to upload a
28964 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
28965 requests failed, because the router descriptor had not been
28966 downloaded yet. In these cases, we now wait until the router
28967 descriptor is downloaded, and then retry. Likewise, clients
28968 now skip over a hidden service directory if they don't yet have
28969 its router descriptor, rather than futilely requesting it and
28970 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
28972 - When fetching v0 and v2 rendezvous service descriptors in parallel,
28973 we were failing the whole hidden service request when the v0
28974 descriptor fetch fails, even if the v2 fetch is still pending and
28975 might succeed. Similarly, if the last v2 fetch fails, we were
28976 failing the whole hidden service request even if a v0 fetch is
28977 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
28978 - DNS replies need to have names matching their requests, but
28979 these names should be in the questions section, not necessarily
28980 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
28983 - Update to the "September 1 2008" ip-to-country file.
28984 - Allow ports 465 and 587 in the default exit policy again. We had
28985 rejected them in 0.1.0.15, because back in 2005 they were commonly
28986 misconfigured and ended up as spam targets. We hear they are better
28987 locked down these days.
28988 - Use a lockfile to make sure that two Tor processes are not
28989 simultaneously running with the same datadir.
28990 - Serve the latest v3 networkstatus consensus via the control
28991 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
28992 - Better logging about stability/reliability calculations on directory
28994 - Drop the requirement to have an open dir port for storing and
28995 serving v2 hidden service descriptors.
28996 - Directory authorities now serve a /tor/dbg-stability.txt URL to
28997 help debug WFU and MTBF calculations.
28998 - Implement most of Proposal 152: allow specialized servers to permit
28999 single-hop circuits, and clients to use those servers to build
29000 single-hop circuits when using a specialized controller. Patch
29001 from Josh Albrecht. Resolves feature request 768.
29002 - Add a -p option to tor-resolve for specifying the SOCKS port: some
29003 people find host:port too confusing.
29004 - Make TrackHostExit mappings expire a while after their last use, not
29005 after their creation. Patch from Robert Hogan.
29006 - Provide circuit purposes along with circuit events to the controller.
29009 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
29011 - Fixed some memory leaks -- some quite frequent, some almost
29012 impossible to trigger -- based on results from Coverity.
29013 - When testing for libevent functions, set the LDFLAGS variable
29014 correctly. Found by Riastradh.
29015 - Fix an assertion bug in parsing policy-related options; possible fix
29017 - Catch and report a few more bootstrapping failure cases when Tor
29018 fails to establish a TCP connection. Cleanup on 0.2.1.x.
29019 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
29020 bootstrapping with tunneled directory connections. Bugfix on
29021 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
29022 - When asked to connect to A.B.exit:80, if we don't know the IP for A
29023 and we know that server B rejects most-but-not all connections to
29024 port 80, we would previously reject the connection. Now, we assume
29025 the user knows what they were asking for. Fixes bug 752. Bugfix
29026 on 0.0.9rc5. Diagnosed by BarkerJr.
29027 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
29028 service directories if they have no advertised dir port. Bugfix
29030 - If we overrun our per-second write limits a little, count this as
29031 having used up our write allocation for the second, and choke
29032 outgoing directory writes. Previously, we had only counted this when
29033 we had met our limits precisely. Fixes bug 824. Patch by rovv.
29034 Bugfix on 0.2.0.x (??).
29035 - Avoid a "0 divided by 0" calculation when calculating router uptime
29036 at directory authorities. Bugfix on 0.2.0.8-alpha.
29037 - Make DNS resolved controller events into "CLOSED", not
29038 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
29040 - Fix a bug where an unreachable relay would establish enough
29041 reachability testing circuits to do a bandwidth test -- if
29042 we already have a connection to the middle hop of the testing
29043 circuit, then it could establish the last hop by using the existing
29044 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
29045 circuits no longer use entry guards in 0.2.1.3-alpha.
29046 - If we have correct permissions on $datadir, we complain to stdout
29047 and fail to start. But dangerous permissions on
29048 $datadir/cached-status/ would cause us to open a log and complain
29049 there. Now complain to stdout and fail to start in both cases. Fixes
29050 bug 820, reported by seeess.
29051 - Remove the old v2 directory authority 'lefkada' from the default
29052 list. It has been gone for many months.
29054 o Code simplifications and refactoring:
29055 - Revise the connection_new functions so that a more typesafe variant
29056 exists. This will work better with Coverity, and let us find any
29057 actual mistakes we're making here.
29058 - Refactor unit testing logic so that dmalloc can be used sensibly
29059 with unit tests to check for memory leaks.
29060 - Move all hidden-service related fields from connection and circuit
29061 structure to substructures: this way they won't eat so much memory.
29064 Changes in version 0.2.0.31 - 2008-09-03
29065 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
29066 a big bug we're seeing where in rare cases traffic from one Tor stream
29067 gets mixed into another stream, and fixes a variety of smaller issues.
29070 - Make sure that two circuits can never exist on the same connection
29071 with the same circuit ID, even if one is marked for close. This
29072 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
29073 - Relays now reject risky extend cells: if the extend cell includes
29074 a digest of all zeroes, or asks to extend back to the relay that
29075 sent the extend cell, tear down the circuit. Ideas suggested
29077 - If not enough of our entry guards are available so we add a new
29078 one, we might use the new one even if it overlapped with the
29079 current circuit's exit relay (or its family). Anonymity bugfix
29080 pointed out by rovv.
29083 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
29084 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
29085 - Correctly detect the presence of the linux/netfilter_ipv4.h header
29086 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
29087 - Pick size of default geoip filename string correctly on windows.
29088 Fixes bug 806. Bugfix on 0.2.0.30.
29089 - Make the autoconf script accept the obsolete --with-ssl-dir
29090 option as an alias for the actually-working --with-openssl-dir
29091 option. Fix the help documentation to recommend --with-openssl-dir.
29092 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
29093 - When using the TransPort option on OpenBSD, and using the User
29094 option to change UID and drop privileges, make sure to open
29095 /dev/pf before dropping privileges. Fixes bug 782. Patch from
29096 Christopher Davis. Bugfix on 0.1.2.1-alpha.
29097 - Try to attach connections immediately upon receiving a RENDEZVOUS2
29098 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
29099 on the client side when connecting to a hidden service. Bugfix
29100 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
29101 - When closing an application-side connection because its circuit is
29102 getting torn down, generate the stream event correctly. Bugfix on
29103 0.1.2.x. Anonymous patch.
29106 Changes in version 0.2.1.5-alpha - 2008-08-31
29107 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
29108 in a lot of the infrastructure for adding authorization to hidden
29109 services, lays the groundwork for having clients read their load
29110 balancing information out of the networkstatus consensus rather than
29111 the individual router descriptors, addresses two potential anonymity
29112 issues, and fixes a variety of smaller issues.
29115 - Convert many internal address representations to optionally hold
29117 - Generate and accept IPv6 addresses in many protocol elements.
29118 - Make resolver code handle nameservers located at ipv6 addresses.
29119 - Begin implementation of proposal 121 ("Client authorization for
29120 hidden services"): configure hidden services with client
29121 authorization, publish descriptors for them, and configure
29122 authorization data for hidden services at clients. The next
29123 step is to actually access hidden services that perform client
29125 - More progress toward proposal 141: Network status consensus
29126 documents and votes now contain bandwidth information for each
29127 router and a summary of that router's exit policy. Eventually this
29128 will be used by clients so that they do not have to download every
29129 known descriptor before building circuits.
29131 o Major bugfixes (on 0.2.0.x and before):
29132 - When sending CREATED cells back for a given circuit, use a 64-bit
29133 connection ID to find the right connection, rather than an addr:port
29134 combination. Now that we can have multiple OR connections between
29135 the same ORs, it is no longer possible to use addr:port to uniquely
29136 identify a connection.
29137 - Relays now reject risky extend cells: if the extend cell includes
29138 a digest of all zeroes, or asks to extend back to the relay that
29139 sent the extend cell, tear down the circuit. Ideas suggested
29141 - If not enough of our entry guards are available so we add a new
29142 one, we might use the new one even if it overlapped with the
29143 current circuit's exit relay (or its family). Anonymity bugfix
29144 pointed out by rovv.
29147 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
29148 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
29149 - When using the TransPort option on OpenBSD, and using the User
29150 option to change UID and drop privileges, make sure to open /dev/pf
29151 before dropping privileges. Fixes bug 782. Patch from Christopher
29152 Davis. Bugfix on 0.1.2.1-alpha.
29153 - Correctly detect the presence of the linux/netfilter_ipv4.h header
29154 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
29155 - Add a missing safe_str() call for a debug log message.
29156 - Use 64 bits instead of 32 bits for connection identifiers used with
29157 the controller protocol, to greatly reduce risk of identifier reuse.
29158 - Make the autoconf script accept the obsolete --with-ssl-dir
29159 option as an alias for the actually-working --with-openssl-dir
29160 option. Fix the help documentation to recommend --with-openssl-dir.
29161 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
29164 - Rate-limit too-many-sockets messages: when they happen, they happen
29165 a lot. Resolves bug 748.
29166 - Resist DNS poisoning a little better by making sure that names in
29167 answer sections match.
29168 - Print the SOCKS5 error message string as well as the error code
29169 when a tor-resolve request fails. Patch from Jacob.
29172 Changes in version 0.2.1.4-alpha - 2008-08-04
29173 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
29176 - The address part of exit policies was not correctly written
29177 to router descriptors. This generated router descriptors that failed
29178 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
29180 - Tor triggered a false assert when extending a circuit to a relay
29181 but we already have a connection open to that relay. Noticed by
29182 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
29185 - Fix a hidden service logging bug: in some edge cases, the router
29186 descriptor of a previously picked introduction point becomes
29187 obsolete and we need to give up on it rather than continually
29188 complaining that it has become obsolete. Observed by xiando. Bugfix
29191 o Removed features:
29192 - Take out the TestVia config option, since it was a workaround for
29193 a bug that was fixed in Tor 0.1.1.21.
29196 Changes in version 0.2.1.3-alpha - 2008-08-03
29197 Tor 0.2.1.3-alpha implements most of the pieces to prevent
29198 infinite-length circuit attacks (see proposal 110); fixes a bug that
29199 might cause exit relays to corrupt streams they send back; allows
29200 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
29201 ExcludeExitNodes config options; and fixes a big pile of bugs.
29203 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
29204 - Send a bootstrap problem "warn" event on the first problem if the
29205 reason is NO_ROUTE (that is, our network is down).
29208 - Implement most of proposal 110: The first K cells to be sent
29209 along a circuit are marked as special "early" cells; only K "early"
29210 cells will be allowed. Once this code is universal, we can block
29211 certain kinds of DOS attack by requiring that EXTEND commands must
29212 be sent using an "early" cell.
29215 - Try to attach connections immediately upon receiving a RENDEZVOUS2
29216 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
29217 on the client side when connecting to a hidden service. Bugfix
29218 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
29219 - Ensure that two circuits can never exist on the same connection
29220 with the same circuit ID, even if one is marked for close. This
29221 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
29224 - When relays do their initial bandwidth measurement, don't limit
29225 to just our entry guards for the test circuits. Otherwise we tend
29226 to have multiple test circuits going through a single entry guard,
29227 which makes our bandwidth test less accurate. Fixes part of bug 654;
29228 patch contributed by Josh Albrecht.
29229 - Add an ExcludeExitNodes option so users can list a set of nodes
29230 that should be be excluded from the exit node position, but
29231 allowed elsewhere. Implements proposal 151.
29232 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
29233 ExcludeNodes and ExcludeExitNodes lists.
29234 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
29235 be more efficient. Formerly it was quadratic in the number of
29236 servers; now it should be linear. Fixes bug 509.
29237 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
29238 and n_conn_id_digest fields into a separate structure that's
29239 only needed when the circuit has not yet attached to an n_conn.
29242 - Change the contrib/tor.logrotate script so it makes the new
29243 logs as "_tor:_tor" rather than the default, which is generally
29244 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
29245 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
29246 warnings (occasionally), but it can also cause the compiler to
29247 eliminate error-checking code. Suggested by Peter Gutmann.
29248 - When a hidden service is giving up on an introduction point candidate
29249 that was not included in the last published rendezvous descriptor,
29250 don't reschedule publication of the next descriptor. Fixes bug 763.
29252 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
29253 HiddenServiceExcludeNodes as obsolete: they never worked properly,
29254 and nobody claims to be using them. Fixes bug 754. Bugfix on
29255 0.1.0.1-rc. Patch from Christian Wilms.
29256 - Fix a small alignment and memory-wasting bug on buffer chunks.
29259 o Minor bugfixes (controller):
29260 - When closing an application-side connection because its circuit
29261 is getting torn down, generate the stream event correctly.
29262 Bugfix on 0.1.2.x. Anonymous patch.
29264 o Removed features:
29265 - Remove all backward-compatibility code to support relays running
29266 versions of Tor so old that they no longer work at all on the
29270 Changes in version 0.2.0.30 - 2008-07-15
29272 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
29273 warnings (occasionally), but it can also cause the compiler to
29274 eliminate error-checking code. Suggested by Peter Gutmann.
29277 Changes in version 0.2.0.29-rc - 2008-07-08
29278 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
29279 hidden-service performance bugs, and fixes a bunch of smaller bugs.
29282 - If you have more than one bridge but don't know their keys,
29283 you would only launch a request for the descriptor of the first one
29284 on your list. (Tor considered launching requests for the others, but
29285 found that it already had a connection on the way for $0000...0000
29286 so it didn't open another.) Bugfix on 0.2.0.x.
29287 - If you have more than one bridge but don't know their keys, and the
29288 connection to one of the bridges failed, you would cancel all
29289 pending bridge connections. (After all, they all have the same
29290 digest.) Bugfix on 0.2.0.x.
29291 - When a hidden service was trying to establish an introduction point,
29292 and Tor had built circuits preemptively for such purposes, we
29293 were ignoring all the preemptive circuits and launching a new one
29294 instead. Bugfix on 0.2.0.14-alpha.
29295 - When a hidden service was trying to establish an introduction point,
29296 and Tor *did* manage to reuse one of the preemptively built
29297 circuits, it didn't correctly remember which one it used,
29298 so it asked for another one soon after, until there were no
29299 more preemptive circuits, at which point it launched one from
29300 scratch. Bugfix on 0.0.9.x.
29301 - Make directory servers include the X-Your-Address-Is: http header in
29302 their responses even for begin_dir conns. Now clients who only
29303 ever use begin_dir connections still have a way to learn their IP
29304 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
29307 - Fix a macro/CPP interaction that was confusing some compilers:
29308 some GCCs don't like #if/#endif pairs inside macro arguments.
29310 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
29311 Fixes bug 704; fix from Steven Murdoch.
29312 - When opening /dev/null in finish_daemonize(), do not pass the
29313 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
29314 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
29315 - Correctly detect transparent proxy support on Linux hosts that
29316 require in.h to be included before netfilter_ipv4.h. Patch
29318 - Disallow session resumption attempts during the renegotiation
29319 stage of the v2 handshake protocol. Clients should never be trying
29320 session resumption at this point, but apparently some did, in
29321 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
29322 found by Geoff Goodell.
29325 Changes in version 0.2.1.2-alpha - 2008-06-20
29326 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
29327 make it easier to set up your own private Tor network; fixes several
29328 big bugs with using more than one bridge relay; fixes a big bug with
29329 offering hidden services quickly after Tor starts; and uses a better
29330 API for reporting potential bootstrapping problems to the controller.
29333 - New TestingTorNetwork config option to allow adjustment of
29334 previously constant values that, while reasonable, could slow
29335 bootstrapping. Implements proposal 135. Patch from Karsten.
29338 - If you have more than one bridge but don't know their digests,
29339 you would only learn a request for the descriptor of the first one
29340 on your list. (Tor considered launching requests for the others, but
29341 found that it already had a connection on the way for $0000...0000
29342 so it didn't open another.) Bugfix on 0.2.0.x.
29343 - If you have more than one bridge but don't know their digests,
29344 and the connection to one of the bridges failed, you would cancel
29345 all pending bridge connections. (After all, they all have the
29346 same digest.) Bugfix on 0.2.0.x.
29347 - When establishing a hidden service, introduction points that
29348 originate from cannibalized circuits are completely ignored and not
29349 included in rendezvous service descriptors. This might be another
29350 reason for delay in making a hidden service available. Bugfix
29351 from long ago (0.0.9.x?)
29354 - Allow OpenSSL to use dynamic locks if it wants.
29355 - When building a consensus, do not include routers that are down.
29356 This will cut down 30% to 40% on consensus size. Implements
29358 - In directory authorities' approved-routers files, allow
29359 fingerprints with or without space.
29360 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
29361 controller can query our current bootstrap state in case it attaches
29362 partway through and wants to catch up.
29363 - Send an initial "Starting" bootstrap status event, so we have a
29364 state to start out in.
29367 - Asking for a conditional consensus at .../consensus/<fingerprints>
29368 would crash a dirserver if it did not already have a
29369 consensus. Bugfix on 0.2.1.1-alpha.
29370 - Clean up some macro/CPP interactions: some GCC versions don't like
29371 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
29374 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
29375 - Directory authorities shouldn't complain about bootstrapping
29376 problems just because they do a lot of reachability testing and
29377 some of the connection attempts fail.
29378 - Start sending "count" and "recommendation" key/value pairs in
29379 bootstrap problem status events, so the controller can hear about
29380 problems even before Tor decides they're worth reporting for sure.
29381 - If you're using bridges, generate "bootstrap problem" warnings
29382 as soon as you run out of working bridges, rather than waiting
29383 for ten failures -- which will never happen if you have less than
29385 - If we close our OR connection because there's been a circuit
29386 pending on it for too long, we were telling our bootstrap status
29387 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
29390 Changes in version 0.2.1.1-alpha - 2008-06-13
29391 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
29392 were making the Tor process bloat especially on Linux; makes our TLS
29393 handshake blend in better; sends "bootstrap phase" status events to
29394 the controller, so it can keep the user informed of progress (and
29395 problems) fetching directory information and establishing circuits;
29396 and adds a variety of smaller features.
29399 - More work on making our TLS handshake blend in: modify the list
29400 of ciphers advertised by OpenSSL in client mode to even more
29401 closely resemble a common web browser. We cheat a little so that
29402 we can advertise ciphers that the locally installed OpenSSL doesn't
29404 - Start sending "bootstrap phase" status events to the controller,
29405 so it can keep the user informed of progress fetching directory
29406 information and establishing circuits. Also inform the controller
29407 if we think we're stuck at a particular bootstrap phase. Implements
29409 - Resume using OpenSSL's RAND_poll() for better (and more portable)
29410 cross-platform entropy collection again. We used to use it, then
29411 stopped using it because of a bug that could crash systems that
29412 called RAND_poll when they had a lot of fds open. It looks like the
29413 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
29414 at startup, and to call RAND_poll() when we reseed later only if
29415 we have a non-buggy OpenSSL version.
29418 - When we choose to abandon a new entry guard because we think our
29419 older ones might be better, close any circuits pending on that
29420 new entry guard connection. This fix should make us recover much
29421 faster when our network is down and then comes back. Bugfix on
29422 0.1.2.8-beta; found by lodger.
29424 o Memory fixes and improvements:
29425 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
29426 to avoid unused RAM in buffer chunks and memory pools.
29427 - Speed up parsing and cut down on memory fragmentation by using
29428 stack-style allocations for parsing directory objects. Previously,
29429 this accounted for over 40% of allocations from within Tor's code
29430 on a typical directory cache.
29431 - Use a Bloom filter rather than a digest-based set to track which
29432 descriptors we need to keep around when we're cleaning out old
29433 router descriptors. This speeds up the computation significantly,
29434 and may reduce fragmentation.
29435 - Reduce the default smartlist size from 32 to 16; it turns out that
29436 most smartlists hold around 8-12 elements tops.
29437 - Make dumpstats() log the fullness and size of openssl-internal
29439 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
29440 patch to their OpenSSL, turn it on to save memory on servers. This
29441 patch will (with any luck) get included in a mainline distribution
29443 - Never use OpenSSL compression: it wastes RAM and CPU trying to
29444 compress cells, which are basically all encrypted, compressed,
29448 - Stop reloading the router list from disk for no reason when we
29449 run out of reachable directory mirrors. Once upon a time reloading
29450 it would set the 'is_running' flag back to 1 for them. It hasn't
29451 done that for a long time.
29452 - In very rare situations new hidden service descriptors were
29453 published earlier than 30 seconds after the last change to the
29454 service. (We currently think that a hidden service descriptor
29455 that's been stable for 30 seconds is worth publishing.)
29458 - Allow separate log levels to be configured for different logging
29459 domains. For example, this allows one to log all notices, warnings,
29460 or errors, plus all memory management messages of level debug or
29461 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
29462 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
29463 and stop using a warning that had become unfixably verbose under
29465 - New --hush command-line option similar to --quiet. While --quiet
29466 disables all logging to the console on startup, --hush limits the
29467 output to messages of warning and error severity.
29468 - Servers support a new URL scheme for consensus downloads that
29469 allows the client to specify which authorities are trusted.
29470 The server then only sends the consensus if the client will trust
29471 it. Otherwise a 404 error is sent back. Clients use this
29472 new scheme when the server supports it (meaning it's running
29473 0.2.1.1-alpha or later). Implements proposal 134.
29474 - New configure/torrc options (--enable-geoip-stats,
29475 DirRecordUsageByCountry) to record how many IPs we've served
29476 directory info to in each country code, how many status documents
29477 total we've sent to each country code, and what share of the total
29478 directory requests we should expect to see.
29479 - Use the TLS1 hostname extension to more closely resemble browser
29481 - Lots of new unit tests.
29482 - Add a macro to implement the common pattern of iterating through
29483 two parallel lists in lockstep.
29486 Changes in version 0.2.0.28-rc - 2008-06-13
29487 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
29488 performance bug, and fixes a bunch of smaller bugs.
29491 - Fix a bug where, when we were choosing the 'end stream reason' to
29492 put in our relay end cell that we send to the exit relay, Tor
29493 clients on Windows were sometimes sending the wrong 'reason'. The
29494 anonymity problem is that exit relays may be able to guess whether
29495 the client is running Windows, thus helping partition the anonymity
29496 set. Down the road we should stop sending reasons to exit relays,
29497 or otherwise prevent future versions of this bug.
29500 - While setting up a hidden service, some valid introduction circuits
29501 were overlooked and abandoned. This might be the reason for
29502 the long delay in making a hidden service available. Bugfix on
29506 - Update to the "June 9 2008" ip-to-country file.
29507 - Run 'make test' as part of 'make dist', so we stop releasing so
29508 many development snapshots that fail their unit tests.
29511 - When we're checking if we have enough dir info for each relay
29512 to begin establishing circuits, make sure that we actually have
29513 the descriptor listed in the consensus, not just any descriptor.
29515 - Bridge relays no longer print "xx=0" in their extrainfo document
29516 for every single country code in the geoip db. Bugfix on
29518 - Only warn when we fail to load the geoip file if we were planning to
29519 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
29520 - If we change our MaxAdvertisedBandwidth and then reload torrc,
29521 Tor won't realize it should publish a new relay descriptor. Fixes
29522 bug 688, reported by mfr. Bugfix on 0.1.2.x.
29523 - When we haven't had any application requests lately, don't bother
29524 logging that we have expired a bunch of descriptors. Bugfix
29526 - Make relay cells written on a connection count as non-padding when
29527 tracking how long a connection has been in use. Bugfix on
29528 0.2.0.1-alpha. Spotted by lodger.
29529 - Fix unit tests in 0.2.0.27-rc.
29530 - Fix compile on Windows.
29533 Changes in version 0.2.0.27-rc - 2008-06-03
29534 Tor 0.2.0.27-rc adds a few features we left out of the earlier
29535 release candidates. In particular, we now include an IP-to-country
29536 GeoIP database, so controllers can easily look up what country a
29537 given relay is in, and so bridge relays can give us some sanitized
29538 summaries about which countries are making use of bridges. (See proposal
29539 126-geoip-fetching.txt for details.)
29542 - Include an IP-to-country GeoIP file in the tarball, so bridge
29543 relays can report sanitized summaries of the usage they're seeing.
29546 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
29547 Robert Hogan. Fixes the first part of bug 681.
29548 - Make bridge authorities never serve extrainfo docs.
29549 - Add support to detect Libevent versions in the 1.4.x series
29551 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
29552 - Include a new contrib/tor-exit-notice.html file that exit relay
29553 operators can put on their website to help reduce abuse queries.
29556 - When tunneling an encrypted directory connection, and its first
29557 circuit fails, do not leave it unattached and ask the controller
29558 to deal. Fixes the second part of bug 681.
29559 - Make bridge authorities correctly expire old extrainfo documents
29563 Changes in version 0.2.0.26-rc - 2008-05-13
29564 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
29565 in Debian's OpenSSL packages. All users running any 0.2.0.x version
29566 should upgrade, whether they're running Debian or not.
29568 o Major security fixes:
29569 - Use new V3 directory authority keys on the tor26, gabelmoo, and
29570 moria1 V3 directory authorities. The old keys were generated with
29571 a vulnerable version of Debian's OpenSSL package, and must be
29572 considered compromised. Other authorities' keys were not generated
29573 with an affected version of OpenSSL.
29576 - List authority signatures as "unrecognized" based on DirServer
29577 lines, not on cert cache. Bugfix on 0.2.0.x.
29580 - Add a new V3AuthUseLegacyKey option to make it easier for
29581 authorities to change their identity keys if they have to.
29584 Changes in version 0.2.0.25-rc - 2008-04-23
29585 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
29588 - Remember to initialize threading before initializing logging.
29589 Otherwise, many BSD-family implementations will crash hard on
29590 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
29593 - Authorities correctly free policies on bad servers on
29594 exit. Fixes bug 672. Bugfix on 0.2.0.x.
29597 Changes in version 0.2.0.24-rc - 2008-04-22
29598 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
29599 v3 directory authority, makes relays with dynamic IP addresses and no
29600 DirPort notice more quickly when their IP address changes, fixes a few
29601 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
29603 o New directory authorities:
29604 - Take lefkada out of the list of v3 directory authorities, since
29605 it has been down for months.
29606 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
29610 - Detect address changes more quickly on non-directory mirror
29611 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
29613 o Minor features (security):
29614 - Reject requests for reverse-dns lookup of names that are in
29615 a private address space. Patch from lodger.
29616 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
29619 o Minor bugfixes (crashes):
29620 - Avoid a rare assert that can trigger when Tor doesn't have much
29621 directory information yet and it tries to fetch a v2 hidden
29622 service descriptor. Fixes bug 651, reported by nwf.
29623 - Initialize log mutex before initializing dmalloc. Otherwise,
29624 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
29625 - Use recursive pthread mutexes in order to avoid deadlock when
29626 logging debug-level messages to a controller. Bug spotted by nwf,
29627 bugfix on 0.2.0.16-alpha.
29629 o Minor bugfixes (resource management):
29630 - Keep address policies from leaking memory: start their refcount
29631 at 1, not 2. Bugfix on 0.2.0.16-alpha.
29632 - Free authority certificates on exit, so they don't look like memory
29633 leaks. Bugfix on 0.2.0.19-alpha.
29634 - Free static hashtables for policy maps and for TLS connections on
29635 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
29636 - Avoid allocating extra space when computing consensuses on 64-bit
29637 platforms. Bug spotted by aakova.
29639 o Minor bugfixes (misc):
29640 - Do not read the configuration file when we've only been told to
29641 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
29642 based on patch from Sebastian Hahn.
29643 - Exit relays that are used as a client can now reach themselves
29644 using the .exit notation, rather than just launching an infinite
29645 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
29646 - When attempting to open a logfile fails, tell us why.
29647 - Fix a dumb bug that was preventing us from knowing that we should
29648 preemptively build circuits to handle expected directory requests.
29649 Fixes bug 660. Bugfix on 0.1.2.x.
29650 - Warn less verbosely about clock skew from netinfo cells from
29651 untrusted sources. Fixes bug 663.
29652 - Make controller stream events for DNS requests more consistent,
29653 by adding "new stream" events for DNS requests, and removing
29654 spurious "stream closed" events" for cached reverse resolves.
29655 Patch from mwenge. Fixes bug 646.
29656 - Correctly notify one-hop connections when a circuit build has
29657 failed. Possible fix for bug 669. Found by lodger.
29660 Changes in version 0.2.0.23-rc - 2008-03-24
29661 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
29662 makes bootstrapping faster if the first directory mirror you contact
29663 is down. The bundles also include the new Vidalia 0.1.2 release.
29666 - When a tunneled directory request is made to a directory server
29667 that's down, notice after 30 seconds rather than 120 seconds. Also,
29668 fail any begindir streams that are pending on it, so they can
29669 retry elsewhere. This was causing multi-minute delays on bootstrap.
29672 Changes in version 0.2.0.22-rc - 2008-03-18
29673 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
29674 enables encrypted directory connections by default for non-relays, fixes
29675 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
29676 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
29679 - Enable encrypted directory connections by default for non-relays,
29680 so censor tools that block Tor directory connections based on their
29681 plaintext patterns will no longer work. This means Tor works in
29682 certain censored countries by default again.
29685 - Make sure servers always request certificates from clients during
29686 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
29687 - Do not enter a CPU-eating loop when a connection is closed in
29688 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
29689 diagnosed by lodger; bugfix on 0.2.0.20-rc.
29690 - Fix assertion failure that could occur when a blocked circuit
29691 became unblocked, and it had pending client DNS requests. Bugfix
29692 on 0.2.0.1-alpha. Fixes bug 632.
29694 o Minor bugfixes (on 0.1.2.x):
29695 - Generate "STATUS_SERVER" events rather than misspelled
29696 "STATUS_SEVER" events. Caught by mwenge.
29697 - When counting the number of bytes written on a TLS connection,
29698 look at the BIO actually used for writing to the network, not
29699 at the BIO used (sometimes) to buffer data for the network.
29700 Looking at different BIOs could result in write counts on the
29701 order of ULONG_MAX. Fixes bug 614.
29702 - On Windows, correctly detect errors when listing the contents of
29703 a directory. Fix from lodger.
29705 o Minor bugfixes (on 0.2.0.x):
29706 - Downgrade "sslv3 alert handshake failure" message to INFO.
29707 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
29708 left BandwidthRate and BandwidthBurst at the default, we would be
29709 silently limited by those defaults. Now raise them to match the
29710 RelayBandwidth* values.
29711 - Fix the SVK version detection logic to work correctly on a branch.
29712 - Make --enable-openbsd-malloc work correctly on Linux with alpha
29713 CPUs. Fixes bug 625.
29714 - Logging functions now check that the passed severity is sane.
29715 - Use proper log levels in the testsuite call of
29716 get_interface_address6().
29717 - When using a nonstandard malloc, do not use the platform values for
29718 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
29719 - Make the openbsd malloc code use 8k pages on alpha CPUs and
29721 - Detect mismatched page sizes when using --enable-openbsd-malloc.
29722 - Avoid double-marked-for-close warning when certain kinds of invalid
29723 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
29724 for bug 617. Bugfix on 0.2.0.1-alpha.
29725 - Make sure that the "NULL-means-reject *:*" convention is followed by
29726 all the policy manipulation functions, avoiding some possible crash
29727 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
29728 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
29729 actually works, and doesn't warn about every single reverse lookup.
29730 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
29733 - Only log guard node status when guard node status has changed.
29734 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
29735 make "INFO" 75% less verbose.
29738 Changes in version 0.2.0.21-rc - 2008-03-02
29739 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
29740 makes Tor work well with Vidalia again, fixes a rare assert bug,
29741 and fixes a pair of more minor bugs. The bundles also include Vidalia
29742 0.1.0 and Torbutton 1.1.16.
29745 - The control port should declare that it requires password auth
29746 when HashedControlSessionPassword is set too. Patch from Matt Edman;
29747 bugfix on 0.2.0.20-rc. Fixes bug 615.
29748 - Downgrade assert in connection_buckets_decrement() to a log message.
29749 This may help us solve bug 614, and in any case will make its
29750 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
29751 - We were sometimes miscounting the number of bytes read from the
29752 network, causing our rate limiting to not be followed exactly.
29753 Bugfix on 0.2.0.16-alpha. Reported by lodger.
29756 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
29757 OpenSSL versions should have been working fine. Diagnosis and patch
29758 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
29759 Bugfix on 0.2.0.20-rc.
29762 Changes in version 0.2.0.20-rc - 2008-02-24
29763 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
29764 makes more progress towards normalizing Tor's TLS handshake, makes
29765 hidden services work better again, helps relays bootstrap if they don't
29766 know their IP address, adds optional support for linking in openbsd's
29767 allocator or tcmalloc, allows really fast relays to scale past 15000
29768 sockets, and fixes a bunch of minor bugs reported by Veracode.
29771 - Enable the revised TLS handshake based on the one designed by
29772 Steven Murdoch in proposal 124, as revised in proposal 130. It
29773 includes version negotiation for OR connections as described in
29774 proposal 105. The new handshake is meant to be harder for censors
29775 to fingerprint, and it adds the ability to detect certain kinds of
29776 man-in-the-middle traffic analysis attacks. The version negotiation
29777 feature will allow us to improve Tor's link protocol more safely
29779 - Choose which bridge to use proportional to its advertised bandwidth,
29780 rather than uniformly at random. This should speed up Tor for
29781 bridge users. Also do this for people who set StrictEntryNodes.
29782 - When a TrackHostExits-chosen exit fails too many times in a row,
29783 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
29786 - Resolved problems with (re-)fetching hidden service descriptors.
29787 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
29788 and 0.2.0.19-alpha.
29789 - If we only ever used Tor for hidden service lookups or posts, we
29790 would stop building circuits and start refusing connections after
29791 24 hours, since we falsely believed that Tor was dormant. Reported
29792 by nwf; bugfix on 0.1.2.x.
29793 - Servers that don't know their own IP address should go to the
29794 authorities for their first directory fetch, even if their DirPort
29795 is off or if they don't know they're reachable yet. This will help
29796 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
29797 - When counting the number of open sockets, count not only the number
29798 of sockets we have received from the socket() call, but also
29799 the number we've gotten from accept() and socketpair(). This bug
29800 made us fail to count all sockets that we were using for incoming
29801 connections. Bugfix on 0.2.0.x.
29802 - Fix code used to find strings within buffers, when those strings
29803 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
29804 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
29805 - Add a new __HashedControlSessionPassword option for controllers
29806 to use for one-off session password hashes that shouldn't get
29807 saved to disk by SAVECONF --- Vidalia users were accumulating a
29808 pile of HashedControlPassword lines in their torrc files, one for
29809 each time they had restarted Tor and then clicked Save. Make Tor
29810 automatically convert "HashedControlPassword" to this new option but
29811 only when it's given on the command line. Partial fix for bug 586.
29813 o Minor features (performance):
29814 - Tune parameters for cell pool allocation to minimize amount of
29816 - Add OpenBSD malloc code from phk as an optional malloc
29817 replacement on Linux: some glibc libraries do very poorly
29818 with Tor's memory allocation patterns. Pass
29819 --enable-openbsd-malloc to get the replacement malloc code.
29820 - Add a --with-tcmalloc option to the configure script to link
29821 against tcmalloc (if present). Does not yet search for
29822 non-system include paths.
29823 - Stop imposing an arbitrary maximum on the number of file descriptors
29824 used for busy servers. Bug reported by Olaf Selke; patch from
29827 o Minor features (other):
29828 - When SafeLogging is disabled, log addresses along with all TLS
29830 - When building with --enable-gcc-warnings, check for whether Apple's
29831 warning "-Wshorten-64-to-32" is available.
29832 - Add a --passphrase-fd argument to the tor-gencert command for
29835 o Minor bugfixes (memory leaks and code problems):
29836 - We were leaking a file descriptor if Tor started with a zero-length
29837 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
29838 - Detect size overflow in zlib code. Reported by Justin Ferguson and
29840 - We were comparing the raw BridgePassword entry with a base64'ed
29841 version of it, when handling a "/tor/networkstatus-bridges"
29842 directory request. Now compare correctly. Noticed by Veracode.
29843 - Recover from bad tracked-since value in MTBF-history file.
29844 Should fix bug 537.
29845 - Alter the code that tries to recover from unhandled write
29846 errors, to not try to flush onto a socket that's given us
29847 unhandled errors. Bugfix on 0.1.2.x.
29848 - Make Unix controlsockets work correctly on OpenBSD. Patch from
29849 tup. Bugfix on 0.2.0.3-alpha.
29851 o Minor bugfixes (other):
29852 - If we have an extra-info document for our server, always make
29853 it available on the control port, even if we haven't gotten
29854 a copy of it from an authority yet. Patch from mwenge.
29855 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
29856 - Directory mirrors no longer include a guess at the client's IP
29857 address if the connection appears to be coming from the same /24
29858 network; it was producing too many wrong guesses.
29859 - Make the new hidden service code respect the SafeLogging setting.
29860 Bugfix on 0.2.0.x. Patch from Karsten.
29861 - When starting as an authority, do not overwrite all certificates
29862 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
29863 - If we're trying to flush the last bytes on a connection (for
29864 example, when answering a directory request), reset the
29865 time-to-give-up timeout every time we manage to write something
29866 on the socket. Bugfix on 0.1.2.x.
29867 - Change the behavior of "getinfo status/good-server-descriptor"
29868 so it doesn't return failure when any authority disappears.
29869 - Even though the man page said that "TrackHostExits ." should
29870 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
29871 - Report TLS "zero return" case as a "clean close" and "IO error"
29872 as a "close". Stop calling closes "unexpected closes": existing
29873 Tors don't use SSL_close(), so having a connection close without
29874 the TLS shutdown handshake is hardly unexpected.
29875 - Send NAMESERVER_STATUS messages for a single failed nameserver
29878 o Code simplifications and refactoring:
29879 - Remove the tor_strpartition function: its logic was confused,
29880 and it was only used for one thing that could be implemented far
29884 Changes in version 0.2.0.19-alpha - 2008-02-09
29885 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
29886 handshake, makes path selection for relays more secure and IP address
29887 guessing more robust, and generally fixes a lot of bugs in preparation
29888 for calling the 0.2.0 branch stable.
29891 - Do not include recognizeable strings in the commonname part of
29892 Tor's x509 certificates.
29895 - If we're a relay, avoid picking ourselves as an introduction point,
29896 a rendezvous point, or as the final hop for internal circuits. Bug
29897 reported by taranis and lodger. Bugfix on 0.1.2.x.
29898 - Patch from "Andrew S. Lists" to catch when we contact a directory
29899 mirror at IP address X and he says we look like we're coming from
29900 IP address X. Bugfix on 0.1.2.x.
29902 o Minor features (security):
29903 - Be more paranoid about overwriting sensitive memory on free(),
29904 as a defensive programming tactic to ensure forward secrecy.
29906 o Minor features (directory authority):
29907 - Actually validate the options passed to AuthDirReject,
29908 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
29909 - Reject router descriptors with out-of-range bandwidthcapacity or
29910 bandwidthburst values.
29912 o Minor features (controller):
29913 - Reject controller commands over 1MB in length. This keeps rogue
29914 processes from running us out of memory.
29916 o Minor features (misc):
29917 - Give more descriptive well-formedness errors for out-of-range
29918 hidden service descriptor/protocol versions.
29919 - Make memory debugging information describe more about history
29920 of cell allocation, so we can help reduce our memory use.
29922 o Deprecated features (controller):
29923 - The status/version/num-versioning and status/version/num-concurring
29924 GETINFO options are no longer useful in the v3 directory protocol:
29925 treat them as deprecated, and warn when they're used.
29928 - When our consensus networkstatus has been expired for a while, stop
29929 being willing to build circuits using it. Fixes bug 401. Bugfix
29931 - Directory caches now fetch certificates from all authorities
29932 listed in a networkstatus consensus, even when they do not
29933 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
29934 - When connecting to a bridge without specifying its key, insert
29935 the connection into the identity-to-connection map as soon as
29936 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
29937 - Detect versions of OS X where malloc_good_size() is present in the
29938 library but never actually declared. Resolves bug 587. Bugfix
29940 - Stop incorrectly truncating zlib responses to directory authority
29941 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
29942 - Stop recommending that every server operator send mail to tor-ops.
29943 Resolves bug 597. Bugfix on 0.1.2.x.
29944 - Don't trigger an assert if we start a directory authority with a
29945 private IP address (like 127.0.0.1).
29946 - Avoid possible failures when generating a directory with routers
29947 with over-long versions strings, or too many flags set. Bugfix
29949 - If an attempt to launch a DNS resolve request over the control
29950 port fails because we have overrun the limit on the number of
29951 connections, tell the controller that the request has failed.
29952 - Avoid using too little bandwidth when our clock skips a few
29953 seconds. Bugfix on 0.1.2.x.
29954 - Fix shell error when warning about missing packages in configure
29955 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
29956 - Do not become confused when receiving a spurious VERSIONS-like
29957 cell from a confused v1 client. Bugfix on 0.2.0.x.
29958 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
29959 introduction points for a hidden service have failed. Patch from
29960 Karsten Loesing. Bugfix on 0.2.0.x.
29962 o Code simplifications and refactoring:
29963 - Remove some needless generality from cpuworker code, for improved
29965 - Stop overloading the circuit_t.onionskin field for both "onionskin
29966 from a CREATE cell that we are waiting for a cpuworker to be
29967 assigned" and "onionskin from an EXTEND cell that we are going to
29968 send to an OR as soon as we are connected". Might help with bug 600.
29969 - Add an in-place version of aes_crypt() so that we can avoid doing a
29970 needless memcpy() call on each cell payload.
29973 Changes in version 0.2.0.18-alpha - 2008-01-25
29974 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
29975 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
29976 that can warn or reject connections to ports generally associated with
29977 vulnerable-plaintext protocols.
29979 o New directory authorities:
29980 - Set up dannenberg (run by CCC) as the sixth v3 directory
29984 - Fix a major memory leak when attempting to use the v2 TLS
29985 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
29986 - We accidentally enabled the under-development v2 TLS handshake
29987 code, which was causing log entries like "TLS error while
29988 renegotiating handshake". Disable it again. Resolves bug 590.
29989 - We were computing the wrong Content-Length: header for directory
29990 responses that need to be compressed on the fly, causing clients
29991 asking for those items to always fail. Bugfix on 0.2.0.x; partially
29995 - Avoid going directly to the directory authorities even if you're a
29996 relay, if you haven't found yourself reachable yet or if you've
29997 decided not to advertise your dirport yet. Addresses bug 556.
29998 - If we've gone 12 hours since our last bandwidth check, and we
29999 estimate we have less than 50KB bandwidth capacity but we could
30000 handle more, do another bandwidth test.
30001 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
30002 Tor can warn and/or refuse connections to ports commonly used with
30003 vulnerable-plaintext protocols. Currently we warn on ports 23,
30004 109, 110, and 143, but we don't reject any.
30007 - When we setconf ClientOnly to 1, close any current OR and Dir
30008 listeners. Reported by mwenge.
30009 - When we get a consensus that's been signed by more people than
30010 we expect, don't log about it; it's not a big deal. Reported
30014 - Don't answer "/tor/networkstatus-bridges" directory requests if
30015 the request isn't encrypted.
30016 - Make "ClientOnly 1" config option disable directory ports too.
30017 - Patches from Karsten Loesing to make v2 hidden services more
30018 robust: work even when there aren't enough HSDir relays available;
30019 retry when a v2 rend desc fetch fails; but don't retry if we
30020 already have a usable v0 rend desc.
30023 Changes in version 0.2.0.17-alpha - 2008-01-17
30024 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
30027 - Make the tor-gencert man page get included correctly in the tarball.
30030 Changes in version 0.2.0.16-alpha - 2008-01-17
30031 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
30032 Loesing, and generally cleans up a lot of features and minor bugs.
30034 o New directory authorities:
30035 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
30038 o Major performance improvements:
30039 - Switch our old ring buffer implementation for one more like that
30040 used by free Unix kernels. The wasted space in a buffer with 1mb
30041 of data will now be more like 8k than 1mb. The new implementation
30042 also avoids realloc();realloc(); patterns that can contribute to
30043 memory fragmentation.
30046 - Configuration files now accept C-style strings as values. This
30047 helps encode characters not allowed in the current configuration
30048 file format, such as newline or #. Addresses bug 557.
30049 - Although we fixed bug 539 (where servers would send HTTP status 503
30050 responses _and_ send a body too), there are still servers out
30051 there that haven't upgraded. Therefore, make clients parse such
30052 bodies when they receive them.
30053 - When we're not serving v2 directory information, there is no reason
30054 to actually keep any around. Remove the obsolete files and directory
30055 on startup if they are very old and we aren't going to serve them.
30057 o Minor performance improvements:
30058 - Reference-count and share copies of address policy entries; only 5%
30059 of them were actually distinct.
30060 - Never walk through the list of logs if we know that no log is
30061 interested in a given message.
30064 - When an authority has not signed a consensus, do not try to
30065 download a nonexistent "certificate with key 00000000". Bugfix
30066 on 0.2.0.x. Fixes bug 569.
30067 - Fix a rare assert error when we're closing one of our threads:
30068 use a mutex to protect the list of logs, so we never write to the
30069 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
30070 bug 575, which is kind of the revenge of bug 222.
30071 - Patch from Karsten Loesing to complain less at both the client
30072 and the relay when a relay used to have the HSDir flag but doesn't
30073 anymore, and we try to upload a hidden service descriptor.
30074 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
30076 - Do not try to download missing certificates until we have tried
30077 to check our fallback consensus. Fixes bug 583.
30078 - Make bridges round reported GeoIP stats info up to the nearest
30079 estimate, not down. Now we can distinguish between "0 people from
30080 this country" and "1 person from this country".
30081 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
30082 - Avoid possible segfault if key generation fails in
30083 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
30084 - Avoid segfault in the case where a badly behaved v2 versioning
30085 directory sends a signed networkstatus with missing client-versions.
30087 - Avoid segfaults on certain complex invocations of
30088 router_get_by_hexdigest(). Bugfix on 0.1.2.
30089 - Correct bad index on array access in parse_http_time(). Bugfix
30091 - Fix possible bug in vote generation when server versions are present
30092 but client versions are not.
30093 - Fix rare bug on REDIRECTSTREAM control command when called with no
30094 port set: it could erroneously report an error when none had
30096 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
30097 compressing large objects and find ourselves with more than 4k
30098 left over. Bugfix on 0.2.0.
30099 - Fix a small memory leak when setting up a hidden service.
30100 - Fix a few memory leaks that could in theory happen under bizarre
30102 - Fix an assert if we post a general-purpose descriptor via the
30103 control port but that descriptor isn't mentioned in our current
30104 network consensus. Bug reported by Jon McLachlan; bugfix on
30107 o Minor features (controller):
30108 - Get NS events working again. Patch from tup.
30109 - The GETCONF command now escapes and quotes configuration values
30110 that don't otherwise fit into the torrc file.
30111 - The SETCONF command now handles quoted values correctly.
30113 o Minor features (directory authorities):
30114 - New configuration options to override default maximum number of
30115 servers allowed on a single IP address. This is important for
30116 running a test network on a single host.
30117 - Actually implement the -s option to tor-gencert.
30118 - Add a manual page for tor-gencert.
30120 o Minor features (bridges):
30121 - Bridge authorities no longer serve bridge descriptors over
30122 unencrypted connections.
30124 o Minor features (other):
30125 - Add hidden services and DNSPorts to the list of things that make
30126 Tor accept that it has running ports. Change starting Tor with no
30127 ports from a fatal error to a warning; we might change it back if
30128 this turns out to confuse anybody. Fixes bug 579.
30131 Changes in version 0.1.2.19 - 2008-01-17
30132 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
30133 exit policy a little bit more conservative so it's safer to run an
30134 exit relay on a home system, and fixes a variety of smaller issues.
30137 - Exit policies now reject connections that are addressed to a
30138 relay's public (external) IP address too, unless
30139 ExitPolicyRejectPrivate is turned off. We do this because too
30140 many relays are running nearby to services that trust them based
30141 on network address.
30144 - When the clock jumps forward a lot, do not allow the bandwidth
30145 buckets to become negative. Fixes bug 544.
30146 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
30147 on every successful resolve. Reported by Mike Perry.
30148 - Purge old entries from the "rephist" database and the hidden
30149 service descriptor database even when DirPort is zero.
30150 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
30151 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
30152 crashing or mis-answering these requests.
30153 - When we decide to send a 503 response to a request for servers, do
30154 not then also send the server descriptors: this defeats the whole
30155 purpose. Fixes bug 539.
30158 - Changing the ExitPolicyRejectPrivate setting should cause us to
30159 rebuild our server descriptor.
30160 - Fix handling of hex nicknames when answering controller requests for
30161 networkstatus by name, or when deciding whether to warn about
30162 unknown routers in a config option. (Patch from mwenge.)
30163 - Fix a couple of hard-to-trigger autoconf problems that could result
30164 in really weird results on platforms whose sys/types.h files define
30165 nonstandard integer types.
30166 - Don't try to create the datadir when running --verify-config or
30167 --hash-password. Resolves bug 540.
30168 - If we were having problems getting a particular descriptor from the
30169 directory caches, and then we learned about a new descriptor for
30170 that router, we weren't resetting our failure count. Reported
30172 - Although we fixed bug 539 (where servers would send HTTP status 503
30173 responses _and_ send a body too), there are still servers out there
30174 that haven't upgraded. Therefore, make clients parse such bodies
30175 when they receive them.
30176 - Run correctly on systems where rlim_t is larger than unsigned long.
30177 This includes some 64-bit systems.
30178 - Run correctly on platforms (like some versions of OS X 10.5) where
30179 the real limit for number of open files is OPEN_FILES, not rlim_max
30180 from getrlimit(RLIMIT_NOFILES).
30181 - Avoid a spurious free on base64 failure.
30182 - Avoid segfaults on certain complex invocations of
30183 router_get_by_hexdigest().
30184 - Fix rare bug on REDIRECTSTREAM control command when called with no
30185 port set: it could erroneously report an error when none had
30189 Changes in version 0.2.0.15-alpha - 2007-12-25
30190 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
30191 features added in 0.2.0.13-alpha.
30194 - Fix several remotely triggerable asserts based on DirPort requests
30195 for a v2 or v3 networkstatus object before we were prepared. This
30196 was particularly bad for 0.2.0.13 and later bridge relays, who
30197 would never have a v2 networkstatus and would thus always crash
30198 when used. Bugfixes on 0.2.0.x.
30199 - Estimate the v3 networkstatus size more accurately, rather than
30200 estimating it at zero bytes and giving it artificially high priority
30201 compared to other directory requests. Bugfix on 0.2.0.x.
30204 - Fix configure.in logic for cross-compilation.
30205 - When we load a bridge descriptor from the cache, and it was
30206 previously unreachable, mark it as retriable so we won't just
30207 ignore it. Also, try fetching a new copy immediately. Bugfixes
30209 - The bridge GeoIP stats were counting other relays, for example
30210 self-reachability and authority-reachability tests.
30213 - Support compilation to target iPhone; patch from cjacker huang.
30214 To build for iPhone, pass the --enable-iphone option to configure.
30217 Changes in version 0.2.0.14-alpha - 2007-12-23
30219 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
30220 without a datadirectory from a previous Tor install. Reported
30222 - Fix a crash when we fetch a descriptor that turns out to be
30223 unexpected (it used to be in our networkstatus when we started
30224 fetching it, but it isn't in our current networkstatus), and we
30225 aren't using bridges. Bugfix on 0.2.0.x.
30226 - Fix a crash when accessing hidden services: it would work the first
30227 time you use a given introduction point for your service, but
30228 on subsequent requests we'd be using garbage memory. Fixed by
30229 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
30230 - Fix a crash when we load a bridge descriptor from disk but we don't
30231 currently have a Bridge line for it in our torrc. Bugfix on
30235 - If bridge authorities set BridgePassword, they will serve a
30236 snapshot of known bridge routerstatuses from their DirPort to
30237 anybody who knows that password. Unset by default.
30240 - Make the unit tests build again.
30241 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
30242 - Make PublishServerDescriptor default to 1, so the default doesn't
30243 have to change as we invent new directory protocol versions.
30244 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
30245 be included unless sys/time.h is already included. Fixes
30246 bug 553. Bugfix on 0.2.0.x.
30247 - If we receive a general-purpose descriptor and then receive an
30248 identical bridge-purpose descriptor soon after, don't discard
30249 the next one as a duplicate.
30252 - If BridgeRelay is set to 1, then the default for
30253 PublishServerDescriptor is now "bridge" rather than "v2,v3".
30254 - If the user sets RelayBandwidthRate but doesn't set
30255 RelayBandwidthBurst, then make them equal rather than erroring out.
30258 Changes in version 0.2.0.13-alpha - 2007-12-21
30259 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
30260 Goodell, fixes many more bugs, and adds a lot of infrastructure for
30263 o New directory authorities:
30264 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
30268 - Only update guard status (usable / not usable) once we have
30269 enough directory information. This was causing us to always pick
30270 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
30271 causing us to discard all our guards on startup if we hadn't been
30272 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
30273 - Purge old entries from the "rephist" database and the hidden
30274 service descriptor databases even when DirPort is zero. Bugfix
30276 - We were ignoring our RelayBandwidthRate for the first 30 seconds
30277 after opening a circuit -- even a relayed circuit. Bugfix on
30279 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
30280 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
30281 crashing or mis-answering these types of requests.
30282 - Relays were publishing their server descriptor to v1 and v2
30283 directory authorities, but they didn't try publishing to v3-only
30284 authorities. Fix this; and also stop publishing to v1 authorities.
30286 - When we were reading router descriptors from cache, we were ignoring
30287 the annotations -- so for example we were reading in bridge-purpose
30288 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
30289 - When we decided to send a 503 response to a request for servers, we
30290 were then also sending the server descriptors: this defeats the
30291 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
30294 - Bridge relays now behave like clients with respect to time
30295 intervals for downloading new consensus documents -- otherwise they
30296 stand out. Bridge users now wait until the end of the interval,
30297 so their bridge relay will be sure to have a new consensus document.
30298 - Three new config options (AlternateDirAuthority,
30299 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
30300 user selectively replace the default directory authorities by type,
30301 rather than the all-or-nothing replacement that DirServer offers.
30302 - Tor can now be configured to read a GeoIP file from disk in one
30303 of two formats. This can be used by controllers to map IP addresses
30304 to countries. Eventually, it may support exit-by-country.
30305 - When possible, bridge relays remember which countries users
30306 are coming from, and report aggregate information in their
30307 extra-info documents, so that the bridge authorities can learn
30308 where Tor is blocked.
30309 - Bridge directory authorities now do reachability testing on the
30310 bridges they know. They provide router status summaries to the
30311 controller via "getinfo ns/purpose/bridge", and also dump summaries
30312 to a file periodically.
30313 - Stop fetching directory info so aggressively if your DirPort is
30314 on but your ORPort is off; stop fetching v2 dir info entirely.
30315 You can override these choices with the new FetchDirInfoEarly
30319 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
30320 consensus documents when there are too many relays at a single
30321 IP address. Now clear it in v2 network status documents too, and
30322 also clear it in routerinfo_t when the relay is no longer listed
30323 in the relevant networkstatus document.
30324 - Don't crash if we get an unexpected value for the
30325 PublishServerDescriptor config option. Reported by Matt Edman;
30326 bugfix on 0.2.0.9-alpha.
30327 - Our new v2 hidden service descriptor format allows descriptors
30328 that have no introduction points. But Tor crashed when we tried
30329 to build a descriptor with no intro points (and it would have
30330 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
30331 by Karsten Loesing.
30332 - Fix building with dmalloc 5.5.2 with glibc.
30333 - Reject uploaded descriptors and extrainfo documents if they're
30334 huge. Otherwise we'll cache them all over the network and it'll
30335 clog everything up. Reported by Aljosha Judmayer.
30336 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
30337 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
30338 - When the DANGEROUS_VERSION controller status event told us we're
30339 running an obsolete version, it used the string "OLD" to describe
30340 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
30341 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
30342 - If we can't expand our list of entry guards (e.g. because we're
30343 using bridges or we have StrictEntryNodes set), don't mark relays
30344 down when they fail a directory request. Otherwise we're too quick
30345 to mark all our entry points down. Bugfix on 0.1.2.x.
30346 - Fix handling of hex nicknames when answering controller requests for
30347 networkstatus by name, or when deciding whether to warn about unknown
30348 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
30349 - Fix a couple of hard-to-trigger autoconf problems that could result
30350 in really weird results on platforms whose sys/types.h files define
30351 nonstandard integer types. Bugfix on 0.1.2.x.
30352 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
30353 - Don't crash on name lookup when we have no current consensus. Fixes
30354 bug 538; bugfix on 0.2.0.x.
30355 - Only Tors that want to mirror the v2 directory info should
30356 create the "cached-status" directory in their datadir. (All Tors
30357 used to create it.) Bugfix on 0.2.0.9-alpha.
30358 - Directory authorities should only automatically download Extra Info
30359 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
30362 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
30363 consumers. (We already do this on HUP.)
30364 - Authorities and caches fetch the v2 networkstatus documents
30365 less often, now that v3 is encouraged.
30366 - Add a new config option BridgeRelay that specifies you want to
30367 be a bridge relay. Right now the only difference is that it makes
30368 you answer begin_dir requests, and it makes you cache dir info,
30369 even if your DirPort isn't on.
30370 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
30371 ask about source, timestamp of arrival, purpose, etc. We need
30372 something like this to help Vidalia not do GeoIP lookups on bridge
30374 - Allow multiple HashedControlPassword config lines, to support
30375 multiple controller passwords.
30376 - Authorities now decide whether they're authoritative for a given
30377 router based on the router's purpose.
30378 - New config options AuthDirBadDir and AuthDirListBadDirs for
30379 authorities to mark certain relays as "bad directories" in the
30380 networkstatus documents. Also supports the "!baddir" directive in
30381 the approved-routers file.
30384 Changes in version 0.2.0.12-alpha - 2007-11-16
30385 This twelfth development snapshot fixes some more build problems as
30386 well as a few minor bugs.
30389 - Make it build on OpenBSD again. Patch from tup.
30390 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
30391 package-building for Red Hat, OS X, etc.
30393 o Minor bugfixes (on 0.1.2.x):
30394 - Changing the ExitPolicyRejectPrivate setting should cause us to
30395 rebuild our server descriptor.
30397 o Minor bugfixes (on 0.2.0.x):
30398 - When we're lacking a consensus, don't try to perform rendezvous
30399 operations. Reported by Karsten Loesing.
30400 - Fix a small memory leak whenever we decide against using a
30401 newly picked entry guard. Reported by Mike Perry.
30402 - When authorities detected more than two relays running on the same
30403 IP address, they were clearing all the status flags but forgetting
30404 to clear the "hsdir" flag. So clients were being told that a
30405 given relay was the right choice for a v2 hsdir lookup, yet they
30406 never had its descriptor because it was marked as 'not running'
30408 - If we're trying to fetch a bridge descriptor and there's no way
30409 the bridge authority could help us (for example, we don't know
30410 a digest, or there is no bridge authority), don't be so eager to
30411 fall back to asking the bridge authority.
30412 - If we're using bridges or have strictentrynodes set, and our
30413 chosen exit is in the same family as all our bridges/entry guards,
30414 then be flexible about families.
30417 - When we negotiate a v2 link-layer connection (not yet implemented),
30418 accept RELAY_EARLY cells and turn them into RELAY cells if we've
30419 negotiated a v1 connection for their next step. Initial code for
30423 Changes in version 0.2.0.11-alpha - 2007-11-12
30424 This eleventh development snapshot fixes some build problems with
30425 the previous snapshot. It also includes a more secure-by-default exit
30426 policy for relays, fixes an enormous memory leak for exit relays, and
30427 fixes another bug where servers were falling out of the directory list.
30430 - Exit policies now reject connections that are addressed to a
30431 relay's public (external) IP address too, unless
30432 ExitPolicyRejectPrivate is turned off. We do this because too
30433 many relays are running nearby to services that trust them based
30434 on network address. Bugfix on 0.1.2.x.
30437 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
30438 on every successful resolve. Reported by Mike Perry; bugfix
30440 - On authorities, never downgrade to old router descriptors simply
30441 because they're listed in the consensus. This created a catch-22
30442 where we wouldn't list a new descriptor because there was an
30443 old one in the consensus, and we couldn't get the new one in the
30444 consensus because we wouldn't list it. Possible fix for bug 548.
30445 Also, this might cause bug 543 to appear on authorities; if so,
30446 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
30448 o Packaging fixes on 0.2.0.10-alpha:
30449 - We were including instructions about what to do with the
30450 src/config/fallback-consensus file, but we weren't actually
30451 including it in the tarball. Disable all of that for now.
30454 - Allow people to say PreferTunnelledDirConns rather than
30455 PreferTunneledDirConns, for those alternate-spellers out there.
30458 - Don't reevaluate all the information from our consensus document
30459 just because we've downloaded a v2 networkstatus that we intend
30460 to cache. Fixes bug 545; bugfix on 0.2.0.x.
30463 Changes in version 0.2.0.10-alpha - 2007-11-10
30464 This tenth development snapshot adds a third v3 directory authority
30465 run by Mike Perry, adds most of Karsten Loesing's new hidden service
30466 descriptor format, fixes a bad crash bug and new bridge bugs introduced
30467 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
30468 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
30469 addresses many more minor issues.
30471 o New directory authorities:
30472 - Set up ides (run by Mike Perry) as the third v3 directory authority.
30475 - Allow tunnelled directory connections to ask for an encrypted
30476 "begin_dir" connection or an anonymized "uses a full Tor circuit"
30477 connection independently. Now we can make anonymized begin_dir
30478 connections for (e.g.) more secure hidden service posting and
30480 - More progress on proposal 114: code from Karsten Loesing to
30481 implement new hidden service descriptor format.
30482 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
30483 accommodate the growing number of servers that use the default
30484 and are reaching it.
30485 - Directory authorities use a new formula for selecting which nodes
30486 to advertise as Guards: they must be in the top 7/8 in terms of
30487 how long we have known about them, and above the median of those
30488 nodes in terms of weighted fractional uptime.
30489 - Make "not enough dir info yet" warnings describe *why* Tor feels
30490 it doesn't have enough directory info yet.
30493 - Stop servers from crashing if they set a Family option (or
30494 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
30496 - Make bridge users work again -- the move to v3 directories in
30497 0.2.0.9-alpha had introduced a number of bugs that made bridges
30498 no longer work for clients.
30499 - When the clock jumps forward a lot, do not allow the bandwidth
30500 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
30502 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
30503 - When the consensus lists a router descriptor that we previously were
30504 mirroring, but that we considered non-canonical, reload the
30505 descriptor as canonical. This fixes bug 543 where Tor servers
30506 would start complaining after a few days that they don't have
30507 enough directory information to build a circuit.
30508 - Consider replacing the current consensus when certificates arrive
30509 that make the pending consensus valid. Previously, we were only
30510 considering replacement when the new certs _didn't_ help.
30511 - Fix an assert error on startup if we didn't already have the
30512 consensus and certs cached in our datadirectory: we were caching
30513 the consensus in consensus_waiting_for_certs but then free'ing it
30515 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
30516 Request) if we need more v3 certs but we've already got pending
30517 requests for all of them.
30518 - Correctly back off from failing certificate downloads. Fixes
30520 - Authorities don't vote on the Running flag if they have been running
30521 for less than 30 minutes themselves. Fixes bug 547, where a newly
30522 started authority would vote that everyone was down.
30524 o New requirements:
30525 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
30526 it, it had no AES, and it hasn't seen any security patches since
30530 - Clients now hold circuitless TLS connections open for 1.5 times
30531 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
30532 rebuild a new circuit over them within that timeframe. Previously,
30533 they held them open only for KeepalivePeriod (5 minutes).
30534 - Use "If-Modified-Since" to avoid retrieving consensus
30535 networkstatuses that we already have.
30536 - When we have no consensus, check FallbackNetworkstatusFile (defaults
30537 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
30538 we start knowing some directory caches.
30539 - When we receive a consensus from the future, warn about skew.
30540 - Improve skew reporting: try to give the user a better log message
30541 about how skewed they are, and how much this matters.
30542 - When we have a certificate for an authority, believe that
30543 certificate's claims about the authority's IP address.
30544 - New --quiet command-line option to suppress the default console log.
30545 Good in combination with --hash-password.
30546 - Authorities send back an X-Descriptor-Not-New header in response to
30547 an accepted-but-discarded descriptor upload. Partially implements
30549 - Make the log message for "tls error. breaking." more useful.
30550 - Better log messages about certificate downloads, to attempt to
30551 track down the second incarnation of bug 546.
30553 o Minor features (bridges):
30554 - If bridge users set UpdateBridgesFromAuthority, but the digest
30555 they ask for is a 404 from the bridge authority, they now fall
30556 back to trying the bridge directly.
30557 - Bridges now use begin_dir to publish their server descriptor to
30558 the bridge authority, even when they haven't set TunnelDirConns.
30560 o Minor features (controller):
30561 - When reporting clock skew, and we know that the clock is _at least
30562 as skewed_ as some value, but we don't know the actual value,
30563 report the value as a "minimum skew."
30566 - Update linux-tor-prio.sh script to allow QoS based on the uid of
30567 the Tor process. Patch from Marco Bonetti with tweaks from Mike
30571 - Refuse to start if both ORPort and UseBridges are set. Bugfix
30572 on 0.2.0.x, suggested by Matt Edman.
30573 - Don't stop fetching descriptors when FetchUselessDescriptors is
30574 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
30575 reported by tup and ioerror.
30576 - Better log message on vote from unknown authority.
30577 - Don't log "Launching 0 request for 0 router" message.
30579 o Minor bugfixes (memory leaks):
30580 - Stop leaking memory every time we parse a v3 certificate. Bugfix
30582 - Stop leaking memory every time we load a v3 certificate. Bugfix
30583 on 0.2.0.1-alpha. Fixes bug 536.
30584 - Stop leaking a cached networkstatus on exit. Bugfix on
30586 - Stop leaking voter information every time we free a consensus.
30587 Bugfix on 0.2.0.3-alpha.
30588 - Stop leaking signed data every time we check a voter signature.
30589 Bugfix on 0.2.0.3-alpha.
30590 - Stop leaking a signature every time we fail to parse a consensus or
30591 a vote. Bugfix on 0.2.0.3-alpha.
30592 - Stop leaking v2_download_status_map on shutdown. Bugfix on
30594 - Stop leaking conn->nickname every time we make a connection to a
30595 Tor relay without knowing its expected identity digest (e.g. when
30596 using bridges). Bugfix on 0.2.0.3-alpha.
30598 - Minor bugfixes (portability):
30599 - Run correctly on platforms where rlim_t is larger than unsigned
30600 long, and/or where the real limit for number of open files is
30601 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
30602 particular, these may be needed for OS X 10.5.
30605 Changes in version 0.1.2.18 - 2007-10-28
30606 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
30607 hidden service introduction that were causing huge delays, and a big
30608 bug that was causing some servers to disappear from the network status
30609 lists for a few hours each day.
30611 o Major bugfixes (crashes):
30612 - If a connection is shut down abruptly because of something that
30613 happened inside connection_flushed_some(), do not call
30614 connection_finished_flushing(). Should fix bug 451:
30615 "connection_stop_writing: Assertion conn->write_event failed"
30616 Bugfix on 0.1.2.7-alpha.
30617 - Fix possible segfaults in functions called from
30618 rend_process_relay_cell().
30620 o Major bugfixes (hidden services):
30621 - Hidden services were choosing introduction points uniquely by
30622 hexdigest, but when constructing the hidden service descriptor
30623 they merely wrote the (potentially ambiguous) nickname.
30624 - Clients now use the v2 intro format for hidden service
30625 connections: they specify their chosen rendezvous point by identity
30626 digest rather than by (potentially ambiguous) nickname. These
30627 changes could speed up hidden service connections dramatically.
30629 o Major bugfixes (other):
30630 - Stop publishing a new server descriptor just because we get a
30631 HUP signal. This led (in a roundabout way) to some servers getting
30632 dropped from the networkstatus lists for a few hours each day.
30633 - When looking for a circuit to cannibalize, consider family as well
30634 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
30635 circuit cannibalization).
30636 - When a router wasn't listed in a new networkstatus, we were leaving
30637 the flags for that router alone -- meaning it remained Named,
30638 Running, etc -- even though absence from the networkstatus means
30639 that it shouldn't be considered to exist at all anymore. Now we
30640 clear all the flags for routers that fall out of the networkstatus
30641 consensus. Fixes bug 529.
30644 - Don't try to access (or alter) the state file when running
30645 --list-fingerprint or --verify-config or --hash-password. Resolves
30647 - When generating information telling us how to extend to a given
30648 router, do not try to include the nickname if it is
30649 absent. Resolves bug 467.
30650 - Fix a user-triggerable segfault in expand_filename(). (There isn't
30651 a way to trigger this remotely.)
30652 - When sending a status event to the controller telling it that an
30653 OR address is reachable, set the port correctly. (Previously we
30654 were reporting the dir port.)
30655 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
30656 command. Bugfix on 0.1.2.17.
30657 - When loading bandwidth history, do not believe any information in
30658 the future. Fixes bug 434.
30659 - When loading entry guard information, do not believe any information
30661 - When we have our clock set far in the future and generate an
30662 onion key, then re-set our clock to be correct, we should not stop
30663 the onion key from getting rotated.
30664 - On some platforms, accept() can return a broken address. Detect
30665 this more quietly, and deal accordingly. Fixes bug 483.
30666 - It's not actually an error to find a non-pending entry in the DNS
30667 cache when canceling a pending resolve. Don't log unless stuff
30668 is fishy. Resolves bug 463.
30669 - Don't reset trusted dir server list when we set a configuration
30670 option. Patch from Robert Hogan.
30671 - Don't try to create the datadir when running --verify-config or
30672 --hash-password. Resolves bug 540.
30675 Changes in version 0.2.0.9-alpha - 2007-10-24
30676 This ninth development snapshot switches clients to the new v3 directory
30677 system; allows servers to be listed in the network status even when they
30678 have the same nickname as a registered server; and fixes many other
30679 bugs including a big one that was causing some servers to disappear
30680 from the network status lists for a few hours each day.
30682 o Major features (directory system):
30683 - Clients now download v3 consensus networkstatus documents instead
30684 of v2 networkstatus documents. Clients and caches now base their
30685 opinions about routers on these consensus documents. Clients only
30686 download router descriptors listed in the consensus.
30687 - Authorities now list servers who have the same nickname as
30688 a different named server, but list them with a new flag,
30689 "Unnamed". Now we can list servers that happen to pick the same
30690 nickname as a server that registered two years ago and then
30691 disappeared. Partially implements proposal 122.
30692 - If the consensus lists a router as "Unnamed", the name is assigned
30693 to a different router: do not identify the router by that name.
30694 Partially implements proposal 122.
30695 - Authorities can now come to a consensus on which method to use to
30696 compute the consensus. This gives us forward compatibility.
30699 - Stop publishing a new server descriptor just because we HUP or
30700 when we find our DirPort to be reachable but won't actually publish
30701 it. New descriptors without any real changes are dropped by the
30702 authorities, and can screw up our "publish every 18 hours" schedule.
30704 - When a router wasn't listed in a new networkstatus, we were leaving
30705 the flags for that router alone -- meaning it remained Named,
30706 Running, etc -- even though absence from the networkstatus means
30707 that it shouldn't be considered to exist at all anymore. Now we
30708 clear all the flags for routers that fall out of the networkstatus
30709 consensus. Fixes bug 529; bugfix on 0.1.2.x.
30710 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
30711 extrainfo documents and then discard them immediately for not
30712 matching the latest router. Bugfix on 0.2.0.1-alpha.
30714 o Minor features (v3 directory protocol):
30715 - Allow tor-gencert to generate a new certificate without replacing
30717 - Allow certificates to include an address.
30718 - When we change our directory-cache settings, reschedule all voting
30719 and download operations.
30720 - Reattempt certificate downloads immediately on failure, as long as
30721 we haven't failed a threshold number of times yet.
30722 - Delay retrying consensus downloads while we're downloading
30723 certificates to verify the one we just got. Also, count getting a
30724 consensus that we already have (or one that isn't valid) as a failure,
30725 and count failing to get the certificates after 20 minutes as a
30727 - Build circuits and download descriptors even if our consensus is a
30728 little expired. (This feature will go away once authorities are
30731 o Minor features (router descriptor cache):
30732 - If we find a cached-routers file that's been sitting around for more
30733 than 28 days unmodified, then most likely it's a leftover from
30734 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
30736 - When we (as a cache) download a descriptor because it was listed
30737 in a consensus, remember when the consensus was supposed to expire,
30738 and don't expire the descriptor until then.
30740 o Minor features (performance):
30741 - Call routerlist_remove_old_routers() much less often. This should
30742 speed startup, especially on directory caches.
30743 - Don't try to launch new descriptor downloads quite so often when we
30744 already have enough directory information to build circuits.
30745 - Base64 decoding was actually showing up on our profile when parsing
30746 the initial descriptor file; switch to an in-process all-at-once
30747 implementation that's about 3.5x times faster than calling out to
30750 o Minor features (compilation):
30751 - Detect non-ASCII platforms (if any still exist) and refuse to
30752 build there: some of our code assumes that 'A' is 65 and so on.
30754 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
30755 - Make the "next period" votes into "current period" votes immediately
30756 after publishing the consensus; avoid a heisenbug that made them
30757 stick around indefinitely.
30758 - When we discard a vote as a duplicate, do not report this as
30760 - Treat missing v3 keys or certificates as an error when running as a
30761 v3 directory authority.
30762 - When we're configured to be a v3 authority, but we're only listed
30763 as a non-v3 authority in our DirServer line for ourself, correct
30765 - If an authority doesn't have a qualified hostname, just put
30766 its address in the vote. This fixes the problem where we referred to
30767 "moria on moria:9031."
30768 - Distinguish between detached signatures for the wrong period, and
30769 detached signatures for a divergent vote.
30770 - Fix a small memory leak when computing a consensus.
30771 - When there's no consensus, we were forming a vote every 30
30772 minutes, but writing the "valid-after" line in our vote based
30773 on our configured V3AuthVotingInterval: so unless the intervals
30774 matched up, we immediately rejected our own vote because it didn't
30775 start at the voting interval that caused us to construct a vote.
30777 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
30778 - Delete unverified-consensus when the real consensus is set.
30779 - Consider retrying a consensus networkstatus fetch immediately
30780 after one fails: don't wait 60 seconds to notice.
30781 - When fetching a consensus as a cache, wait until a newer consensus
30782 should exist before trying to replace the current one.
30783 - Use a more forgiving schedule for retrying failed consensus
30784 downloads than for other types.
30786 o Minor bugfixes (other directory issues):
30787 - Correct the implementation of "download votes by digest." Bugfix on
30789 - Authorities no longer send back "400 you're unreachable please fix
30790 it" errors to Tor servers that aren't online all the time. We're
30791 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
30793 o Minor bugfixes (controller):
30794 - Don't reset trusted dir server list when we set a configuration
30795 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
30796 - Respond to INT and TERM SIGNAL commands before we execute the
30797 signal, in case the signal shuts us down. We had a patch in
30798 0.1.2.1-alpha that tried to do this by queueing the response on
30799 the connection's buffer before shutting down, but that really
30800 isn't the same thing at all. Bug located by Matt Edman.
30802 o Minor bugfixes (misc):
30803 - Correctly check for bad options to the "PublishServerDescriptor"
30804 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
30805 - Stop leaking memory on failing case of base32_decode, and make
30806 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
30807 - Don't try to download extrainfo documents when we're trying to
30808 fetch enough directory info to build a circuit: having enough
30809 info should get priority. Bugfix on 0.2.0.x.
30810 - Don't complain that "your server has not managed to confirm that its
30811 ports are reachable" if we haven't been able to build any circuits
30812 yet. Bug found by spending four hours without a v3 consensus. Bugfix
30814 - Detect the reason for failing to mmap a descriptor file we just
30815 wrote, and give a more useful log message. Fixes bug 533. Bugfix
30818 o Code simplifications and refactoring:
30819 - Remove support for the old bw_accounting file: we've been storing
30820 bandwidth accounting information in the state file since
30821 0.1.2.5-alpha. This may result in bandwidth accounting errors
30822 if you try to upgrade from 0.1.1.x or earlier, or if you try to
30823 downgrade to 0.1.1.x or earlier.
30824 - New convenience code to locate a file within the DataDirectory.
30825 - Move non-authority functionality out of dirvote.c.
30826 - Refactor the arguments for router_pick_{directory_|trusteddir}server
30827 so that they all take the same named flags.
30830 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
30831 Unix users an easy way to script their Tor process (e.g. by
30832 adjusting bandwidth based on the time of the day).
30835 Changes in version 0.2.0.8-alpha - 2007-10-12
30836 This eighth development snapshot fixes a crash bug that's been bothering
30837 us since February 2007, lets bridge authorities store a list of bridge
30838 descriptors they've seen, gets v3 directory voting closer to working,
30839 starts caching v3 directory consensus documents on directory mirrors,
30840 and fixes a variety of smaller issues including some minor memory leaks.
30842 o Major features (router descriptor cache):
30843 - Store routers in a file called cached-descriptors instead of in
30844 cached-routers. Initialize cached-descriptors from cached-routers
30845 if the old format is around. The new format allows us to store
30846 annotations along with descriptors.
30847 - Use annotations to record the time we received each descriptor, its
30848 source, and its purpose.
30849 - Disable the SETROUTERPURPOSE controller command: it is now
30851 - Controllers should now specify cache=no or cache=yes when using
30852 the +POSTDESCRIPTOR command.
30853 - Bridge authorities now write bridge descriptors to disk, meaning
30854 we can export them to other programs and begin distributing them
30857 o Major features (directory authorities):
30858 - When a v3 authority is missing votes or signatures, it now tries
30860 - Directory authorities track weighted fractional uptime as well as
30861 weighted mean-time-between failures. WFU is suitable for deciding
30862 whether a node is "usually up", while MTBF is suitable for deciding
30863 whether a node is "likely to stay up." We need both, because
30864 "usually up" is a good requirement for guards, while "likely to
30865 stay up" is a good requirement for long-lived connections.
30867 o Major features (v3 directory system):
30868 - Caches now download v3 network status documents as needed,
30869 and download the descriptors listed in them.
30870 - All hosts now attempt to download and keep fresh v3 authority
30871 certificates, and re-attempt after failures.
30872 - More internal-consistency checks for vote parsing.
30874 o Major bugfixes (crashes):
30875 - If a connection is shut down abruptly because of something that
30876 happened inside connection_flushed_some(), do not call
30877 connection_finished_flushing(). Should fix bug 451. Bugfix on
30880 o Major bugfixes (performance):
30881 - Fix really bad O(n^2) performance when parsing a long list of
30882 routers: Instead of searching the entire list for an "extra-info "
30883 string which usually wasn't there, once for every routerinfo
30884 we read, just scan lines forward until we find one we like.
30886 - When we add data to a write buffer in response to the data on that
30887 write buffer getting low because of a flush, do not consider the
30888 newly added data as a candidate for immediate flushing, but rather
30889 make it wait until the next round of writing. Otherwise, we flush
30890 and refill recursively, and a single greedy TLS connection can
30891 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
30893 o Minor features (v3 authority system):
30894 - Add more ways for tools to download the votes that lead to the
30896 - Send a 503 when low on bandwidth and a vote, consensus, or
30897 certificate is requested.
30898 - If-modified-since is now implemented properly for all kinds of
30899 certificate requests.
30901 o Minor bugfixes (network statuses):
30902 - Tweak the implementation of proposal 109 slightly: allow at most
30903 two Tor servers on the same IP address, except if it's the location
30904 of a directory authority, in which case allow five. Bugfix on
30907 o Minor bugfixes (controller):
30908 - When sending a status event to the controller telling it that an
30909 OR address is reachable, set the port correctly. (Previously we
30910 were reporting the dir port.) Bugfix on 0.1.2.x.
30912 o Minor bugfixes (v3 directory system):
30913 - Fix logic to look up a cert by its signing key digest. Bugfix on
30915 - Only change the reply to a vote to "OK" if it's not already
30916 set. This gets rid of annoying "400 OK" log messages, which may
30917 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
30918 - When we get a valid consensus, recompute the voting schedule.
30919 - Base the valid-after time of a vote on the consensus voting
30920 schedule, not on our preferred schedule.
30921 - Make the return values and messages from signature uploads and
30922 downloads more sensible.
30923 - Fix a memory leak when serving votes and consensus documents, and
30924 another when serving certificates.
30926 o Minor bugfixes (performance):
30927 - Use a slightly simpler string hashing algorithm (copying Python's
30928 instead of Java's) and optimize our digest hashing algorithm to take
30929 advantage of 64-bit platforms and to remove some possibly-costly
30931 - Fix a minor memory leak whenever we parse guards from our state
30932 file. Bugfix on 0.2.0.7-alpha.
30933 - Fix a minor memory leak whenever we write out a file. Bugfix on
30935 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
30936 command. Bugfix on 0.2.0.5-alpha.
30938 o Minor bugfixes (portability):
30939 - On some platforms, accept() can return a broken address. Detect
30940 this more quietly, and deal accordingly. Fixes bug 483.
30941 - Stop calling tor_strlower() on uninitialized memory in some cases.
30942 Bugfix in 0.2.0.7-alpha.
30944 o Minor bugfixes (usability):
30945 - Treat some 403 responses from directory servers as INFO rather than
30946 WARN-severity events.
30947 - It's not actually an error to find a non-pending entry in the DNS
30948 cache when canceling a pending resolve. Don't log unless stuff is
30949 fishy. Resolves bug 463.
30951 o Minor bugfixes (anonymity):
30952 - Never report that we've used more bandwidth than we're willing to
30953 relay: it leaks how much non-relay traffic we're using. Resolves
30955 - When looking for a circuit to cannibalize, consider family as well
30956 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
30957 circuit cannibalization).
30959 o Code simplifications and refactoring:
30960 - Make a bunch of functions static. Remove some dead code.
30961 - Pull out about a third of the really big routerlist.c; put it in a
30962 new module, networkstatus.c.
30963 - Merge the extra fields in local_routerstatus_t back into
30964 routerstatus_t: we used to need one routerstatus_t for each
30965 authority's opinion, plus a local_routerstatus_t for the locally
30966 computed consensus opinion. To save space, we put the locally
30967 modified fields into local_routerstatus_t, and only the common
30968 stuff into routerstatus_t. But once v3 directories are in use,
30969 clients and caches will no longer need to hold authority opinions;
30970 thus, the rationale for keeping the types separate is now gone.
30971 - Make the code used to reschedule and reattempt downloads more
30973 - Turn all 'Are we a directory server/mirror?' logic into a call to
30975 - Remove the code to generate the oldest (v1) directory format.
30976 The code has been disabled since 0.2.0.5-alpha.
30979 Changes in version 0.2.0.7-alpha - 2007-09-21
30980 This seventh development snapshot makes bridges work again, makes bridge
30981 authorities work for the first time, fixes two huge performance flaws
30982 in hidden services, and fixes a variety of minor issues.
30984 o New directory authorities:
30985 - Set up moria1 and tor26 as the first v3 directory authorities. See
30986 doc/spec/dir-spec.txt for details on the new directory design.
30988 o Major bugfixes (crashes):
30989 - Fix possible segfaults in functions called from
30990 rend_process_relay_cell(). Bugfix on 0.1.2.x.
30992 o Major bugfixes (bridges):
30993 - Fix a bug that made servers send a "404 Not found" in response to
30994 attempts to fetch their server descriptor. This caused Tor servers
30995 to take many minutes to establish reachability for their DirPort,
30996 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
30997 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
30998 users configure that and specify a bridge with an identity
30999 fingerprint, now they will lookup the bridge descriptor at the
31000 default bridge authority via a one-hop tunnel, but once circuits
31001 are established they will switch to a three-hop tunnel for later
31002 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
31004 o Major bugfixes (hidden services):
31005 - Hidden services were choosing introduction points uniquely by
31006 hexdigest, but when constructing the hidden service descriptor
31007 they merely wrote the (potentially ambiguous) nickname.
31008 - Clients now use the v2 intro format for hidden service
31009 connections: they specify their chosen rendezvous point by identity
31010 digest rather than by (potentially ambiguous) nickname. Both
31011 are bugfixes on 0.1.2.x, and they could speed up hidden service
31012 connections dramatically. Thanks to Karsten Loesing.
31014 o Minor features (security):
31015 - As a client, do not believe any server that tells us that an
31016 address maps to an internal address space.
31017 - Make it possible to enable HashedControlPassword and
31018 CookieAuthentication at the same time.
31020 o Minor features (guard nodes):
31021 - Tag every guard node in our state file with the version that
31022 we believe added it, or with our own version if we add it. This way,
31023 if a user temporarily runs an old version of Tor and then switches
31024 back to a new one, she doesn't automatically lose her guards.
31026 o Minor features (speed):
31027 - When implementing AES counter mode, update only the portions of the
31028 counter buffer that need to change, and don't keep separate
31029 network-order and host-order counters when they are the same (i.e.,
31030 on big-endian hosts.)
31032 o Minor features (controller):
31033 - Accept LF instead of CRLF on controller, since some software has a
31034 hard time generating real Internet newlines.
31035 - Add GETINFO values for the server status events
31036 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
31039 o Removed features:
31040 - Routers no longer include bandwidth-history lines in their
31041 descriptors; this information is already available in extra-info
31042 documents, and including it in router descriptors took up 60%
31043 (!) of compressed router descriptor downloads. Completes
31044 implementation of proposal 104.
31045 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
31046 and TorControl.py, as they use the old v0 controller protocol,
31047 and are obsoleted by TorFlow anyway.
31048 - Drop support for v1 rendezvous descriptors, since we never used
31049 them anyway, and the code has probably rotted by now. Based on
31050 patch from Karsten Loesing.
31051 - On OSX, stop warning the user that kqueue support in libevent is
31052 "experimental", since it seems to have worked fine for ages.
31055 - When generating information telling us how to extend to a given
31056 router, do not try to include the nickname if it is absent. Fixes
31057 bug 467. Bugfix on 0.2.0.3-alpha.
31058 - Fix a user-triggerable (but not remotely-triggerable) segfault
31059 in expand_filename(). Bugfix on 0.1.2.x.
31060 - Fix a memory leak when freeing incomplete requests from DNSPort.
31061 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
31062 - Don't try to access (or alter) the state file when running
31063 --list-fingerprint or --verify-config or --hash-password. (Resolves
31064 bug 499.) Bugfix on 0.1.2.x.
31065 - Servers used to decline to publish their DirPort if their
31066 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
31067 were below a threshold. Now they only look at BandwidthRate and
31068 RelayBandwidthRate. Bugfix on 0.1.2.x.
31069 - Remove an optimization in the AES counter-mode code that assumed
31070 that the counter never exceeded 2^68. When the counter can be set
31071 arbitrarily as an IV (as it is by Karsten's new hidden services
31072 code), this assumption no longer holds. Bugfix on 0.1.2.x.
31073 - Resume listing "AUTHORITY" flag for authorities in network status.
31074 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
31076 o Code simplifications and refactoring:
31077 - Revamp file-writing logic so we don't need to have the entire
31078 contents of a file in memory at once before we write to disk. Tor,
31080 - Turn "descriptor store" into a full-fledged type.
31081 - Move all NT services code into a separate source file.
31082 - Unify all code that computes medians, percentile elements, etc.
31083 - Get rid of a needless malloc when parsing address policies.
31086 Changes in version 0.1.2.17 - 2007-08-30
31087 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
31088 X bundles. Vidalia 0.0.14 makes authentication required for the
31089 ControlPort in the default configuration, which addresses important
31090 security risks. Everybody who uses Vidalia (or another controller)
31093 In addition, this Tor update fixes major load balancing problems with
31094 path selection, which should speed things up a lot once many people
31097 o Major bugfixes (security):
31098 - We removed support for the old (v0) control protocol. It has been
31099 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
31100 become more of a headache than it's worth.
31102 o Major bugfixes (load balancing):
31103 - When choosing nodes for non-guard positions, weight guards
31104 proportionally less, since they already have enough load. Patch
31106 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
31107 will allow fast Tor servers to get more attention.
31108 - When we're upgrading from an old Tor version, forget our current
31109 guards and pick new ones according to the new weightings. These
31110 three load balancing patches could raise effective network capacity
31111 by a factor of four. Thanks to Mike Perry for measurements.
31113 o Major bugfixes (stream expiration):
31114 - Expire not-yet-successful application streams in all cases if
31115 they've been around longer than SocksTimeout. Right now there are
31116 some cases where the stream will live forever, demanding a new
31117 circuit every 15 seconds. Fixes bug 454; reported by lodger.
31119 o Minor features (controller):
31120 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
31121 is valid before any authentication has been received. It tells
31122 a controller what kind of authentication is expected, and what
31123 protocol is spoken. Implements proposal 119.
31125 o Minor bugfixes (performance):
31126 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
31127 greatly speeding up loading cached-routers from disk on startup.
31128 - Disable sentinel-based debugging for buffer code: we squashed all
31129 the bugs that this was supposed to detect a long time ago, and now
31130 its only effect is to change our buffer sizes from nice powers of
31131 two (which platform mallocs tend to like) to values slightly over
31132 powers of two (which make some platform mallocs sad).
31134 o Minor bugfixes (misc):
31135 - If exit bandwidth ever exceeds one third of total bandwidth, then
31136 use the correct formula to weight exit nodes when choosing paths.
31137 Based on patch from Mike Perry.
31138 - Choose perfectly fairly among routers when choosing by bandwidth and
31139 weighting by fraction of bandwidth provided by exits. Previously, we
31140 would choose with only approximate fairness, and correct ourselves
31141 if we ran off the end of the list.
31142 - If we require CookieAuthentication but we fail to write the
31143 cookie file, we would warn but not exit, and end up in a state
31144 where no controller could authenticate. Now we exit.
31145 - If we require CookieAuthentication, stop generating a new cookie
31146 every time we change any piece of our config.
31147 - Refuse to start with certain directory authority keys, and
31148 encourage people using them to stop.
31149 - Terminate multi-line control events properly. Original patch
31151 - Fix a minor memory leak when we fail to find enough suitable
31152 servers to choose a circuit.
31153 - Stop leaking part of the descriptor when we run into a particularly
31154 unparseable piece of it.
31157 Changes in version 0.2.0.6-alpha - 2007-08-26
31158 This sixth development snapshot features a new Vidalia version in the
31159 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
31160 the ControlPort in the default configuration, which addresses important
31163 In addition, this snapshot fixes major load balancing problems
31164 with path selection, which should speed things up a lot once many
31165 people have upgraded. The directory authorities also use a new
31166 mean-time-between-failure approach to tracking which servers are stable,
31167 rather than just looking at the most recent uptime.
31169 o New directory authorities:
31170 - Set up Tonga as the default bridge directory authority.
31173 - Directory authorities now track servers by weighted
31174 mean-times-between-failures. When we have 4 or more days of data,
31175 use measured MTBF rather than declared uptime to decide whether
31176 to call a router Stable. Implements proposal 108.
31178 o Major bugfixes (load balancing):
31179 - When choosing nodes for non-guard positions, weight guards
31180 proportionally less, since they already have enough load. Patch
31182 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
31183 will allow fast Tor servers to get more attention.
31184 - When we're upgrading from an old Tor version, forget our current
31185 guards and pick new ones according to the new weightings. These
31186 three load balancing patches could raise effective network capacity
31187 by a factor of four. Thanks to Mike Perry for measurements.
31189 o Major bugfixes (descriptor parsing):
31190 - Handle unexpected whitespace better in malformed descriptors. Bug
31191 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
31194 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
31195 GETINFO for Torstat to use until it can switch to using extrainfos.
31196 - Optionally (if built with -DEXPORTMALLINFO) export the output
31197 of mallinfo via http, as tor/mallinfo.txt. Only accessible
31201 - Do not intermix bridge routers with controller-added
31202 routers. (Bugfix on 0.2.0.x)
31203 - Do not fail with an assert when accept() returns an unexpected
31204 address family. Addresses but does not wholly fix bug 483. (Bugfix
31206 - Let directory authorities startup even when they can't generate
31207 a descriptor immediately, e.g. because they don't know their
31209 - Stop putting the authentication cookie in a file called "0"
31210 in your working directory if you don't specify anything for the
31211 new CookieAuthFile option. Reported by Matt Edman.
31212 - Make it possible to read the PROTOCOLINFO response in a way that
31213 conforms to our control-spec. Reported by Matt Edman.
31214 - Fix a minor memory leak when we fail to find enough suitable
31215 servers to choose a circuit. Bugfix on 0.1.2.x.
31216 - Stop leaking part of the descriptor when we run into a particularly
31217 unparseable piece of it. Bugfix on 0.1.2.x.
31218 - Unmap the extrainfo cache file on exit.
31221 Changes in version 0.2.0.5-alpha - 2007-08-19
31222 This fifth development snapshot fixes compilation on Windows again;
31223 fixes an obnoxious client-side bug that slowed things down and put
31224 extra load on the network; gets us closer to using the v3 directory
31225 voting scheme; makes it easier for Tor controllers to use cookie-based
31226 authentication; and fixes a variety of other bugs.
31228 o Removed features:
31229 - Version 1 directories are no longer generated in full. Instead,
31230 authorities generate and serve "stub" v1 directories that list
31231 no servers. This will stop Tor versions 0.1.0.x and earlier from
31232 working, but (for security reasons) nobody should be running those
31235 o Major bugfixes (compilation, 0.2.0.x):
31236 - Try to fix Win32 compilation again: improve checking for IPv6 types.
31237 - Try to fix MSVC compilation: build correctly on platforms that do
31238 not define s6_addr16 or s6_addr32.
31239 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
31242 o Major bugfixes (stream expiration):
31243 - Expire not-yet-successful application streams in all cases if
31244 they've been around longer than SocksTimeout. Right now there are
31245 some cases where the stream will live forever, demanding a new
31246 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
31247 reported by lodger.
31249 o Minor features (directory servers):
31250 - When somebody requests a list of statuses or servers, and we have
31251 none of those, return a 404 rather than an empty 200.
31253 o Minor features (directory voting):
31254 - Store v3 consensus status consensuses on disk, and reload them
31257 o Minor features (security):
31258 - Warn about unsafe ControlPort configurations.
31259 - Refuse to start with certain directory authority keys, and
31260 encourage people using them to stop.
31262 o Minor features (controller):
31263 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
31264 is valid before any authentication has been received. It tells
31265 a controller what kind of authentication is expected, and what
31266 protocol is spoken. Implements proposal 119.
31267 - New config option CookieAuthFile to choose a new location for the
31268 cookie authentication file, and config option
31269 CookieAuthFileGroupReadable to make it group-readable.
31271 o Minor features (unit testing):
31272 - Add command-line arguments to unit-test executable so that we can
31273 invoke any chosen test from the command line rather than having
31274 to run the whole test suite at once; and so that we can turn on
31275 logging for the unit tests.
31277 o Minor bugfixes (on 0.1.2.x):
31278 - If we require CookieAuthentication but we fail to write the
31279 cookie file, we would warn but not exit, and end up in a state
31280 where no controller could authenticate. Now we exit.
31281 - If we require CookieAuthentication, stop generating a new cookie
31282 every time we change any piece of our config.
31283 - When loading bandwidth history, do not believe any information in
31284 the future. Fixes bug 434.
31285 - When loading entry guard information, do not believe any information
31287 - When we have our clock set far in the future and generate an
31288 onion key, then re-set our clock to be correct, we should not stop
31289 the onion key from getting rotated.
31290 - Clean up torrc sample config file.
31291 - Do not automatically run configure from autogen.sh. This
31292 non-standard behavior tended to annoy people who have built other
31295 o Minor bugfixes (on 0.2.0.x):
31296 - Fix a bug with AutomapHostsOnResolve that would always cause
31297 the second request to fail. Bug reported by Kate. Bugfix on
31299 - Fix a bug in ADDRMAP controller replies that would sometimes
31300 try to print a NULL. Patch from tup.
31301 - Read v3 directory authority keys from the right location.
31302 - Numerous bugfixes to directory voting code.
31305 Changes in version 0.1.2.16 - 2007-08-01
31306 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
31307 remote attacker in certain situations to rewrite the user's torrc
31308 configuration file. This can completely compromise anonymity of users
31309 in most configurations, including those running the Vidalia bundles,
31310 TorK, etc. Or worse.
31312 o Major security fixes:
31313 - Close immediately after missing authentication on control port;
31314 do not allow multiple authentication attempts.
31317 Changes in version 0.2.0.4-alpha - 2007-08-01
31318 This fourth development snapshot fixes a critical security vulnerability
31319 for most users, specifically those running Vidalia, TorK, etc. Everybody
31320 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
31322 o Major security fixes:
31323 - Close immediately after missing authentication on control port;
31324 do not allow multiple authentication attempts.
31326 o Major bugfixes (compilation):
31327 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
31330 o Minor features (performance):
31331 - Be even more aggressive about releasing RAM from small
31332 empty buffers. Thanks to our free-list code, this shouldn't be too
31333 performance-intensive.
31334 - Disable sentinel-based debugging for buffer code: we squashed all
31335 the bugs that this was supposed to detect a long time ago, and
31336 now its only effect is to change our buffer sizes from nice
31337 powers of two (which platform mallocs tend to like) to values
31338 slightly over powers of two (which make some platform mallocs sad).
31339 - Log malloc statistics from mallinfo() on platforms where it
31343 Changes in version 0.2.0.3-alpha - 2007-07-29
31344 This third development snapshot introduces new experimental
31345 blocking-resistance features and a preliminary version of the v3
31346 directory voting design, and includes many other smaller features
31350 - The first pieces of our "bridge" design for blocking-resistance
31351 are implemented. People can run bridge directory authorities;
31352 people can run bridges; and people can configure their Tor clients
31353 with a set of bridges to use as the first hop into the Tor network.
31354 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
31356 - Create listener connections before we setuid to the configured
31357 User and Group. Now non-Windows users can choose port values
31358 under 1024, start Tor as root, and have Tor bind those ports
31359 before it changes to another UID. (Windows users could already
31361 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
31362 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
31363 on "vserver" accounts. (Patch from coderman.)
31364 - Be even more aggressive about separating local traffic from relayed
31365 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
31367 o Major features (experimental):
31368 - First cut of code for "v3 dir voting": directory authorities will
31369 vote on a common network status document rather than each publishing
31370 their own opinion. This code needs more testing and more corner-case
31371 handling before it's ready for use.
31374 - Directory authorities now call routers Fast if their bandwidth is
31375 at least 100KB/s, and consider their bandwidth adequate to be a
31376 Guard if it is at least 250KB/s, no matter the medians. This fix
31377 complements proposal 107. [Bugfix on 0.1.2.x]
31378 - Directory authorities now never mark more than 3 servers per IP as
31379 Valid and Running. (Implements proposal 109, by Kevin Bauer and
31381 - Minor change to organizationName and commonName generation
31382 procedures in TLS certificates during Tor handshakes, to invalidate
31383 some earlier censorware approaches. This is not a long-term
31384 solution, but applying it will give us a bit of time to look into
31385 the epidemiology of countermeasures as they spread.
31387 o Major bugfixes (directory):
31388 - Rewrite directory tokenization code to never run off the end of
31389 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
31391 o Minor features (controller):
31392 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
31393 match requests to applications. (Patch from Robert Hogan.)
31394 - Report address and port correctly on connections to DNSPort. (Patch
31395 from Robert Hogan.)
31396 - Add a RESOLVE command to launch hostname lookups. (Original patch
31397 from Robert Hogan.)
31398 - Add GETINFO status/enough-dir-info to let controllers tell whether
31399 Tor has downloaded sufficient directory information. (Patch
31401 - You can now use the ControlSocket option to tell Tor to listen for
31402 controller connections on Unix domain sockets on systems that
31403 support them. (Patch from Peter Palfrader.)
31404 - STREAM NEW events are generated for DNSPort requests and for
31405 tunneled directory connections. (Patch from Robert Hogan.)
31406 - New "GETINFO address-mappings/*" command to get address mappings
31407 with expiry information. "addr-mappings/*" is now deprecated.
31410 o Minor features (misc):
31411 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
31413 - The tor-gencert tool for v3 directory authorities now creates all
31414 files as readable to the file creator only, and write-protects
31415 the authority identity key.
31416 - When dumping memory usage, list bytes used in buffer memory
31418 - When running with dmalloc, dump more stats on hup and on exit.
31419 - Directory authorities now fail quickly and (relatively) harmlessly
31420 if they generate a network status document that is somehow
31423 o Traffic load balancing improvements:
31424 - If exit bandwidth ever exceeds one third of total bandwidth, then
31425 use the correct formula to weight exit nodes when choosing paths.
31426 (Based on patch from Mike Perry.)
31427 - Choose perfectly fairly among routers when choosing by bandwidth and
31428 weighting by fraction of bandwidth provided by exits. Previously, we
31429 would choose with only approximate fairness, and correct ourselves
31430 if we ran off the end of the list. [Bugfix on 0.1.2.x]
31432 o Performance improvements:
31433 - Be more aggressive with freeing buffer RAM or putting it on the
31435 - Use Critical Sections rather than Mutexes for synchronizing threads
31436 on win32; Mutexes are heavier-weight, and designed for synchronizing
31439 o Deprecated and removed features:
31440 - RedirectExits is now deprecated.
31441 - Stop allowing address masks that do not correspond to bit prefixes.
31442 We have warned about these for a really long time; now it's time
31443 to reject them. (Patch from croup.)
31445 o Minor bugfixes (directory):
31446 - Fix another crash bug related to extra-info caching. (Bug found by
31447 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
31448 - Directories no longer return a "304 not modified" when they don't
31449 have the networkstatus the client asked for. Also fix a memory
31450 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
31451 - We had accidentally labelled 0.1.2.x directory servers as not
31452 suitable for begin_dir requests, and had labelled no directory
31453 servers as suitable for uploading extra-info documents. [Bugfix
31456 o Minor bugfixes (dns):
31457 - Fix a crash when DNSPort is set more than once. (Patch from Robert
31458 Hogan.) [Bugfix on 0.2.0.2-alpha]
31459 - Add DNSPort connections to the global connection list, so that we
31460 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
31462 - Fix a dangling reference that could lead to a crash when DNSPort is
31463 changed or closed (Patch from Robert Hogan.) [Bugfix on
31466 o Minor bugfixes (controller):
31467 - Provide DNS expiry times in GMT, not in local time. For backward
31468 compatibility, ADDRMAP events only provide GMT expiry in an extended
31469 field. "GETINFO address-mappings" always does the right thing.
31470 - Use CRLF line endings properly in NS events.
31471 - Terminate multi-line control events properly. (Original patch
31472 from tup.) [Bugfix on 0.1.2.x-alpha]
31473 - Do not include spaces in SOURCE_ADDR fields in STREAM
31474 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
31477 Changes in version 0.1.2.15 - 2007-07-17
31478 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
31479 problems, fixes compilation on BSD, and fixes a variety of other
31480 bugs. Everybody should upgrade.
31482 o Major bugfixes (compilation):
31483 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
31485 o Major bugfixes (crashes):
31486 - Try even harder not to dereference the first character after
31487 an mmap(). Reported by lodger.
31488 - Fix a crash bug in directory authorities when we re-number the
31489 routerlist while inserting a new router.
31490 - When the cached-routers file is an even multiple of the page size,
31491 don't run off the end and crash. (Fixes bug 455; based on idea
31493 - Fix eventdns.c behavior on Solaris: It is critical to include
31494 orconfig.h _before_ sys/types.h, so that we can get the expected
31495 definition of _FILE_OFFSET_BITS.
31497 o Major bugfixes (security):
31498 - Fix a possible buffer overrun when using BSD natd support. Bug
31500 - When sending destroy cells from a circuit's origin, don't include
31501 the reason for tearing down the circuit. The spec says we didn't,
31502 and now we actually don't. Reported by lodger.
31503 - Keep streamids from different exits on a circuit separate. This
31504 bug may have allowed other routers on a given circuit to inject
31505 cells into streams. Reported by lodger; fixes bug 446.
31506 - If there's a never-before-connected-to guard node in our list,
31507 never choose any guards past it. This way we don't expand our
31508 guard list unless we need to.
31510 o Minor bugfixes (guard nodes):
31511 - Weight guard selection by bandwidth, so that low-bandwidth nodes
31512 don't get overused as guards.
31514 o Minor bugfixes (directory):
31515 - Correctly count the number of authorities that recommend each
31516 version. Previously, we were under-counting by 1.
31517 - Fix a potential crash bug when we load many server descriptors at
31518 once and some of them make others of them obsolete. Fixes bug 458.
31520 o Minor bugfixes (hidden services):
31521 - Stop tearing down the whole circuit when the user asks for a
31522 connection to a port that the hidden service didn't configure.
31525 o Minor bugfixes (misc):
31526 - On Windows, we were preventing other processes from reading
31527 cached-routers while Tor was running. Reported by janbar.
31528 - Fix a possible (but very unlikely) bug in picking routers by
31529 bandwidth. Add a log message to confirm that it is in fact
31530 unlikely. Patch from lodger.
31531 - Backport a couple of memory leak fixes.
31532 - Backport miscellaneous cosmetic bugfixes.
31535 Changes in version 0.2.0.2-alpha - 2007-06-02
31536 o Major bugfixes on 0.2.0.1-alpha:
31537 - Fix an assertion failure related to servers without extra-info digests.
31538 Resolves bugs 441 and 442.
31540 o Minor features (directory):
31541 - Support "If-Modified-Since" when answering HTTP requests for
31542 directories, running-routers documents, and network-status documents.
31543 (There's no need to support it for router descriptors, since those
31544 are downloaded by descriptor digest.)
31546 o Minor build issues:
31547 - Clear up some MIPSPro compiler warnings.
31548 - When building from a tarball on a machine that happens to have SVK
31549 installed, report the micro-revision as whatever version existed
31550 in the tarball, not as "x".
31553 Changes in version 0.2.0.1-alpha - 2007-06-01
31554 This early development snapshot provides new features for people running
31555 Tor as both a client and a server (check out the new RelayBandwidth
31556 config options); lets Tor run as a DNS proxy; and generally moves us
31557 forward on a lot of fronts.
31559 o Major features, server usability:
31560 - New config options RelayBandwidthRate and RelayBandwidthBurst:
31561 a separate set of token buckets for relayed traffic. Right now
31562 relayed traffic is defined as answers to directory requests, and
31563 OR connections that don't have any local circuits on them.
31565 o Major features, client usability:
31566 - A client-side DNS proxy feature to replace the need for
31567 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
31568 for DNS requests on port 9999, use the Tor network to resolve them
31569 anonymously, and send the reply back like a regular DNS server.
31570 The code still only implements a subset of DNS.
31571 - Make PreferTunneledDirConns and TunnelDirConns work even when
31572 we have no cached directory info. This means Tor clients can now
31573 do all of their connections protected by TLS.
31575 o Major features, performance and efficiency:
31576 - Directory authorities accept and serve "extra info" documents for
31577 routers. These documents contain fields from router descriptors
31578 that aren't usually needed, and that use a lot of excess
31579 bandwidth. Once these fields are removed from router descriptors,
31580 the bandwidth savings should be about 60%. [Partially implements
31582 - Servers upload extra-info documents to any authority that accepts
31583 them. Authorities (and caches that have been configured to download
31584 extra-info documents) download them as needed. [Partially implements
31586 - Change the way that Tor buffers data that it is waiting to write.
31587 Instead of queueing data cells in an enormous ring buffer for each
31588 client->OR or OR->OR connection, we now queue cells on a separate
31589 queue for each circuit. This lets us use less slack memory, and
31590 will eventually let us be smarter about prioritizing different kinds
31592 - Use memory pools to allocate cells with better speed and memory
31593 efficiency, especially on platforms where malloc() is inefficient.
31594 - Stop reading on edge connections when their corresponding circuit
31595 buffers are full; start again as the circuits empty out.
31597 o Major features, other:
31598 - Add an HSAuthorityRecordStats option that hidden service authorities
31599 can use to track statistics of overall hidden service usage without
31600 logging information that would be very useful to an attacker.
31601 - Start work implementing multi-level keys for directory authorities:
31602 Add a standalone tool to generate key certificates. (Proposal 103.)
31605 - Directory authorities now call routers Stable if they have an
31606 uptime of at least 30 days, even if that's not the median uptime
31607 in the network. Implements proposal 107, suggested by Kevin Bauer
31610 o Minor fixes (resource management):
31611 - Count the number of open sockets separately from the number
31612 of active connection_t objects. This will let us avoid underusing
31613 our allocated connection limit.
31614 - We no longer use socket pairs to link an edge connection to an
31615 anonymous directory connection or a DirPort test connection.
31616 Instead, we track the link internally and transfer the data
31617 in-process. This saves two sockets per "linked" connection (at the
31618 client and at the server), and avoids the nasty Windows socketpair()
31620 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
31621 for every single inactive connection_t. Free items from the
31622 4k/16k-buffer free lists when they haven't been used for a while.
31624 o Minor features (build):
31625 - Make autoconf search for libevent, openssl, and zlib consistently.
31626 - Update deprecated macros in configure.in.
31627 - When warning about missing headers, tell the user to let us
31628 know if the compile succeeds anyway, so we can downgrade the
31630 - Include the current subversion revision as part of the version
31631 string: either fetch it directly if we're in an SVN checkout, do
31632 some magic to guess it if we're in an SVK checkout, or use
31633 the last-detected version if we're building from a .tar.gz.
31634 Use this version consistently in log messages.
31636 o Minor features (logging):
31637 - Always prepend "Bug: " to any log message about a bug.
31638 - Put a platform string (e.g. "Linux i686") in the startup log
31639 message, so when people paste just their logs, we know if it's
31640 OpenBSD or Windows or what.
31641 - When logging memory usage, break down memory used in buffers by
31644 o Minor features (directory system):
31645 - New config option V2AuthoritativeDirectory that all directory
31646 authorities should set. This will let future authorities choose
31647 not to serve V2 directory information.
31648 - Directory authorities allow multiple router descriptors and/or extra
31649 info documents to be uploaded in a single go. This will make
31650 implementing proposal 104 simpler.
31652 o Minor features (controller):
31653 - Add a new config option __DisablePredictedCircuits designed for
31654 use by the controller, when we don't want Tor to build any circuits
31656 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
31657 so we can exit from the middle of the circuit.
31658 - Implement "getinfo status/circuit-established".
31659 - Implement "getinfo status/version/..." so a controller can tell
31660 whether the current version is recommended, and whether any versions
31661 are good, and how many authorities agree. (Patch from shibz.)
31663 o Minor features (hidden services):
31664 - Allow multiple HiddenServicePort directives with the same virtual
31665 port; when they occur, the user is sent round-robin to one
31666 of the target ports chosen at random. Partially fixes bug 393 by
31667 adding limited ad-hoc round-robining.
31669 o Minor features (other):
31671 - Add a new AutomapHostsOnResolve option: when it is enabled, any
31672 resolve request for hosts matching a given pattern causes Tor to
31673 generate an internal virtual address mapping for that host. This
31674 allows DNSPort to work sensibly with hidden service users. By
31675 default, .exit and .onion addresses are remapped; the list of
31676 patterns can be reconfigured with AutomapHostsSuffixes.
31677 - Add an "-F" option to tor-resolve to force a resolve for a .onion
31678 address. Thanks to the AutomapHostsOnResolve option, this is no
31679 longer a completely silly thing to do.
31680 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
31681 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
31682 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
31683 minus 1 byte: the actual maximum declared bandwidth.
31685 o Removed features:
31686 - Removed support for the old binary "version 0" controller protocol.
31687 This has been deprecated since 0.1.1, and warnings have been issued
31688 since 0.1.2. When we encounter a v0 control message, we now send
31689 back an error and close the connection.
31690 - Remove the old "dns worker" server DNS code: it hasn't been default
31691 since 0.1.2.2-alpha, and all the servers seem to be using the new
31694 o Minor bugfixes (portability):
31695 - Even though Windows is equally happy with / and \ as path separators,
31696 try to use \ consistently on Windows and / consistently on Unix: it
31697 makes the log messages nicer.
31698 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
31699 - Read resolv.conf files correctly on platforms where read() returns
31700 partial results on small file reads.
31702 o Minor bugfixes (directory):
31703 - Correctly enforce that elements of directory objects do not appear
31704 more often than they are allowed to appear.
31705 - When we are reporting the DirServer line we just parsed, we were
31706 logging the second stanza of the key fingerprint, not the first.
31708 o Minor bugfixes (logging):
31709 - When we hit an EOF on a log (probably because we're shutting down),
31710 don't try to remove the log from the list: just mark it as
31711 unusable. (Bulletproofs against bug 222.)
31713 o Minor bugfixes (other):
31714 - In the exitlist script, only consider the most recently published
31715 server descriptor for each server. Also, when the user requests
31716 a list of servers that _reject_ connections to a given address,
31717 explicitly exclude the IPs that also have servers that accept
31718 connections to that address. (Resolves bug 405.)
31719 - Stop allowing hibernating servers to be "stable" or "fast".
31720 - On Windows, we were preventing other processes from reading
31721 cached-routers while Tor was running. (Reported by janbar)
31722 - Make the NodeFamilies config option work. (Reported by
31723 lodger -- it has never actually worked, even though we added it
31725 - Check return values from pthread_mutex functions.
31726 - Don't save non-general-purpose router descriptors to the disk cache,
31727 because we have no way of remembering what their purpose was when
31729 - Add even more asserts to hunt down bug 417.
31730 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
31731 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
31732 Add a log message to confirm that it is in fact unlikely.
31734 o Minor bugfixes (controller):
31735 - Make 'getinfo fingerprint' return a 551 error if we're not a
31736 server, so we match what the control spec claims we do. Reported
31738 - Fix a typo in an error message when extendcircuit fails that
31739 caused us to not follow the \r\n-based delimiter protocol. Reported
31742 o Code simplifications and refactoring:
31743 - Stop passing around circuit_t and crypt_path_t pointers that are
31744 implicit in other procedure arguments.
31745 - Drop the old code to choke directory connections when the
31746 corresponding OR connections got full: thanks to the cell queue
31747 feature, OR conns don't get full any more.
31748 - Make dns_resolve() handle attaching connections to circuits
31749 properly, so the caller doesn't have to.
31750 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
31751 - Keep the connection array as a dynamic smartlist_t, rather than as
31752 a fixed-sized array. This is important, as the number of connections
31753 is becoming increasingly decoupled from the number of sockets.
31756 Changes in version 0.1.2.14 - 2007-05-25
31757 Tor 0.1.2.14 changes the addresses of two directory authorities (this
31758 change especially affects those who serve or use hidden services),
31759 and fixes several other crash- and security-related bugs.
31761 o Directory authority changes:
31762 - Two directory authorities (moria1 and moria2) just moved to new
31763 IP addresses. This change will particularly affect those who serve
31764 or use hidden services.
31766 o Major bugfixes (crashes):
31767 - If a directory server runs out of space in the connection table
31768 as it's processing a begin_dir request, it will free the exit stream
31769 but leave it attached to the circuit, leading to unpredictable
31770 behavior. (Reported by seeess, fixes bug 425.)
31771 - Fix a bug in dirserv_remove_invalid() that would cause authorities
31772 to corrupt memory under some really unlikely scenarios.
31773 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
31774 - Avoid segfaults when reading from mmaped descriptor file. (Reported
31777 o Major bugfixes (security):
31778 - When choosing an entry guard for a circuit, avoid using guards
31779 that are in the same family as the chosen exit -- not just guards
31780 that are exactly the chosen exit. (Reported by lodger.)
31782 o Major bugfixes (resource management):
31783 - If a directory authority is down, skip it when deciding where to get
31784 networkstatus objects or descriptors. Otherwise we keep asking
31785 every 10 seconds forever. Fixes bug 384.
31786 - Count it as a failure if we fetch a valid network-status but we
31787 don't want to keep it. Otherwise we'll keep fetching it and keep
31788 not wanting to keep it. Fixes part of bug 422.
31789 - If all of our dirservers have given us bad or no networkstatuses
31790 lately, then stop hammering them once per minute even when we
31791 think they're failed. Fixes another part of bug 422.
31794 - Actually set the purpose correctly for descriptors inserted with
31795 purpose=controller.
31796 - When we have k non-v2 authorities in our DirServer config,
31797 we ignored the last k authorities in the list when updating our
31799 - Correctly back-off from requesting router descriptors that we are
31800 having a hard time downloading.
31801 - Read resolv.conf files correctly on platforms where read() returns
31802 partial results on small file reads.
31803 - Don't rebuild the entire router store every time we get 32K of
31804 routers: rebuild it when the journal gets very large, or when
31805 the gaps in the store get very large.
31808 - When routers publish SVN revisions in their router descriptors,
31809 authorities now include those versions correctly in networkstatus
31811 - Warn when using a version of libevent before 1.3b to run a server on
31812 OSX or BSD: these versions interact badly with userspace threads.
31815 Changes in version 0.1.2.13 - 2007-04-24
31816 This release features some major anonymity fixes, such as safer path
31817 selection; better client performance; faster bootstrapping, better
31818 address detection, and better DNS support for servers; write limiting as
31819 well as read limiting to make servers easier to run; and a huge pile of
31820 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
31822 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
31823 of the Freenode IRC network, remembering his patience and vision for
31824 free speech on the Internet.
31827 - Fix a memory leak when we ask for "all" networkstatuses and we
31828 get one we don't recognize.
31829 - Add more asserts to hunt down bug 417.
31830 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
31833 Changes in version 0.1.2.12-rc - 2007-03-16
31835 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
31836 directory information requested inside Tor connections (i.e. via
31837 begin_dir cells). It only triggered when the same connection was
31838 serving other data at the same time. Reported by seeess.
31841 - When creating a circuit via the controller, send a 'launched'
31842 event when we're done, so we follow the spec better.
31845 Changes in version 0.1.2.11-rc - 2007-03-15
31846 o Minor bugfixes (controller), reported by daejees:
31847 - Correct the control spec to match how the code actually responds
31848 to 'getinfo addr-mappings/*'.
31849 - The control spec described a GUARDS event, but the code
31850 implemented a GUARD event. Standardize on GUARD, but let people
31851 ask for GUARDS too.
31854 Changes in version 0.1.2.10-rc - 2007-03-07
31855 o Major bugfixes (Windows):
31856 - Do not load the NT services library functions (which may not exist)
31857 just to detect if we're a service trying to shut down. Now we run
31858 on Win98 and friends again.
31860 o Minor bugfixes (other):
31861 - Clarify a couple of log messages.
31862 - Fix a misleading socks5 error number.
31865 Changes in version 0.1.2.9-rc - 2007-03-02
31866 o Major bugfixes (Windows):
31867 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
31868 of the usual GCC "%llu". This prevents a bug when saving 64-bit
31869 int configuration values: the high-order 32 bits would get
31870 truncated. In particular, we were being bitten by the default
31871 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
31872 and maybe also bug 397.)
31874 o Minor bugfixes (performance):
31875 - Use OpenSSL's AES implementation on platforms where it's faster.
31876 This could save us as much as 10% CPU usage.
31878 o Minor bugfixes (server):
31879 - Do not rotate onion key immediately after setting it for the first
31882 o Minor bugfixes (directory authorities):
31883 - Stop calling servers that have been hibernating for a long time
31884 "stable". Also, stop letting hibernating or obsolete servers affect
31885 uptime and bandwidth cutoffs.
31886 - Stop listing hibernating servers in the v1 directory.
31888 o Minor bugfixes (hidden services):
31889 - Upload hidden service descriptors slightly less often, to reduce
31890 load on authorities.
31892 o Minor bugfixes (other):
31893 - Fix an assert that could trigger if a controller quickly set then
31894 cleared EntryNodes. Bug found by Udo van den Heuvel.
31895 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
31897 - Fix a potential race condition in the rpm installer. Found by
31899 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
31900 of 2 as indicating that the server is completely bad; it sometimes
31901 means that the server is just bad for the request in question. (may fix
31902 the last of bug 326.)
31903 - Disable encrypted directory connections when we don't have a server
31904 descriptor for the destination. We'll get this working again in
31908 Changes in version 0.1.2.8-beta - 2007-02-26
31909 o Major bugfixes (crashes):
31910 - Stop crashing when the controller asks us to resetconf more than
31911 one config option at once. (Vidalia 0.0.11 does this.)
31912 - Fix a crash that happened on Win98 when we're given command-line
31913 arguments: don't try to load NT service functions from advapi32.dll
31914 except when we need them. (Bug introduced in 0.1.2.7-alpha;
31916 - Fix a longstanding obscure crash bug that could occur when
31917 we run out of DNS worker processes. (Resolves bug 390.)
31919 o Major bugfixes (hidden services):
31920 - Correctly detect whether hidden service descriptor downloads are
31921 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
31923 o Major bugfixes (accounting):
31924 - When we start during an accounting interval before it's time to wake
31925 up, remember to wake up at the correct time. (May fix bug 342.)
31927 o Minor bugfixes (controller):
31928 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
31929 clear the corresponding on_circuit variable, and remember later
31930 that we don't need to send a redundant CLOSED event. Resolves part
31932 - Report events where a resolve succeeded or where we got a socks
31933 protocol error correctly, rather than calling both of them
31935 - Change reported stream target addresses to IP consistently when
31936 we finally get the IP from an exit node.
31937 - Send log messages to the controller even if they happen to be very
31940 o Minor bugfixes (other):
31941 - Display correct results when reporting which versions are
31942 recommended, and how recommended they are. (Resolves bug 383.)
31943 - Improve our estimates for directory bandwidth to be less random:
31944 guess that an unrecognized directory will have the average bandwidth
31945 from all known directories, not that it will have the average
31946 bandwidth from those directories earlier than it on the list.
31947 - If we start a server with ClientOnly 1, then set ClientOnly to 0
31948 and hup, stop triggering an assert based on an empty onion_key.
31949 - On platforms with no working mmap() equivalent, don't warn the
31950 user when cached-routers doesn't exist.
31951 - Warn the user when mmap() [or its equivalent] fails for some reason
31952 other than file-not-found.
31953 - Don't warn the user when cached-routers.new doesn't exist: that's
31954 perfectly fine when starting up for the first time.
31955 - When EntryNodes are configured, rebuild the guard list to contain,
31956 in order: the EntryNodes that were guards before; the rest of the
31957 EntryNodes; the nodes that were guards before.
31958 - Mask out all signals in sub-threads; only the libevent signal
31959 handler should be processing them. This should prevent some crashes
31960 on some machines using pthreads. (Patch from coderman.)
31961 - Fix switched arguments on memset in the implementation of
31962 tor_munmap() for systems with no mmap() call.
31963 - When Tor receives a router descriptor that it asked for, but
31964 no longer wants (because it has received fresh networkstatuses
31965 in the meantime), do not warn the user. Cache the descriptor if
31966 we're a cache; drop it if we aren't.
31967 - Make earlier entry guards _really_ get retried when the network
31969 - On a malformed DNS reply, always give an error to the corresponding
31971 - Build with recent libevents on platforms that do not define the
31972 nonstandard types "u_int8_t" and friends.
31974 o Minor features (controller):
31975 - Warn the user when an application uses the obsolete binary v0
31976 control protocol. We're planning to remove support for it during
31977 the next development series, so it's good to give people some
31979 - Add STREAM_BW events to report per-entry-stream bandwidth
31980 use. (Patch from Robert Hogan.)
31981 - Rate-limit SIGNEWNYM signals in response to controllers that
31982 impolitely generate them for every single stream. (Patch from
31983 mwenge; closes bug 394.)
31984 - Make REMAP stream events have a SOURCE (cache or exit), and
31985 make them generated in every case where we get a successful
31986 connected or resolved cell.
31988 o Minor bugfixes (performance):
31989 - Call router_have_min_dir_info half as often. (This is showing up in
31990 some profiles, but not others.)
31991 - When using GCC, make log_debug never get called at all, and its
31992 arguments never get evaluated, when no debug logs are configured.
31993 (This is showing up in some profiles, but not others.)
31996 - Remove some never-implemented options. Mark PathlenCoinWeight as
31998 - Implement proposal 106: Stop requiring clients to have well-formed
31999 certificates; stop checking nicknames in certificates. (Clients
32000 have certificates so that they can look like Tor servers, but in
32001 the future we might want to allow them to look like regular TLS
32002 clients instead. Nicknames in certificates serve no purpose other
32003 than making our protocol easier to recognize on the wire.)
32004 - Revise messages on handshake failure again to be even more clear about
32005 which are incoming connections and which are outgoing.
32006 - Discard any v1 directory info that's over 1 month old (for
32007 directories) or over 1 week old (for running-routers lists).
32008 - Do not warn when individual nodes in the configuration's EntryNodes,
32009 ExitNodes, etc are down: warn only when all possible nodes
32010 are down. (Fixes bug 348.)
32011 - Always remove expired routers and networkstatus docs before checking
32012 whether we have enough information to build circuits. (Fixes
32014 - Put a lower-bound on MaxAdvertisedBandwidth.
32017 Changes in version 0.1.2.7-alpha - 2007-02-06
32018 o Major bugfixes (rate limiting):
32019 - Servers decline directory requests much more aggressively when
32020 they're low on bandwidth. Otherwise they end up queueing more and
32021 more directory responses, which can't be good for latency.
32022 - But never refuse directory requests from local addresses.
32023 - Fix a memory leak when sending a 503 response for a networkstatus
32025 - Be willing to read or write on local connections (e.g. controller
32026 connections) even when the global rate limiting buckets are empty.
32027 - If our system clock jumps back in time, don't publish a negative
32028 uptime in the descriptor. Also, don't let the global rate limiting
32029 buckets go absurdly negative.
32030 - Flush local controller connection buffers periodically as we're
32031 writing to them, so we avoid queueing 4+ megabytes of data before
32034 o Major bugfixes (NT services):
32035 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
32036 command-line flag so that admins can override the default by saying
32037 "tor --service install --user "SomeUser"". This will not affect
32038 existing installed services. Also, warn the user that the service
32039 will look for its configuration file in the service user's
32040 %appdata% directory. (We can't do the 'hardwire the user's appdata
32041 directory' trick any more, since we may not have read access to that
32044 o Major bugfixes (other):
32045 - Previously, we would cache up to 16 old networkstatus documents
32046 indefinitely, if they came from nontrusted authorities. Now we
32047 discard them if they are more than 10 days old.
32048 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
32050 - Detect and reject malformed DNS responses containing circular
32052 - If exits are rare enough that we're not marking exits as guards,
32053 ignore exit bandwidth when we're deciding the required bandwidth
32055 - When we're handling a directory connection tunneled over Tor,
32056 don't fill up internal memory buffers with all the data we want
32057 to tunnel; instead, only add it if the OR connection that will
32058 eventually receive it has some room for it. (This can lead to
32059 slowdowns in tunneled dir connections; a better solution will have
32060 to wait for 0.2.0.)
32062 o Minor bugfixes (dns):
32063 - Add some defensive programming to eventdns.c in an attempt to catch
32064 possible memory-stomping bugs.
32065 - Detect and reject DNS replies containing IPv4 or IPv6 records with
32066 an incorrect number of bytes. (Previously, we would ignore the
32068 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
32069 in the correct order, and doesn't crash.
32070 - Free memory held in recently-completed DNS lookup attempts on exit.
32071 This was not a memory leak, but may have been hiding memory leaks.
32072 - Handle TTL values correctly on reverse DNS lookups.
32073 - Treat failure to parse resolv.conf as an error.
32075 o Minor bugfixes (other):
32076 - Fix crash with "tor --list-fingerprint" (reported by seeess).
32077 - When computing clock skew from directory HTTP headers, consider what
32078 time it was when we finished asking for the directory, not what
32080 - Expire socks connections if they spend too long waiting for the
32081 handshake to finish. Previously we would let them sit around for
32082 days, if the connecting application didn't close them either.
32083 - And if the socks handshake hasn't started, don't send a
32084 "DNS resolve socks failed" handshake reply; just close it.
32085 - Stop using C functions that OpenBSD's linker doesn't like.
32086 - Don't launch requests for descriptors unless we have networkstatuses
32087 from at least half of the authorities. This delays the first
32088 download slightly under pathological circumstances, but can prevent
32089 us from downloading a bunch of descriptors we don't need.
32090 - Do not log IPs with TLS failures for incoming TLS
32091 connections. (Fixes bug 382.)
32092 - If the user asks to use invalid exit nodes, be willing to use
32094 - Stop using the reserved ac_cv namespace in our configure script.
32095 - Call stat() slightly less often; use fstat() when possible.
32096 - Refactor the way we handle pending circuits when an OR connection
32097 completes or fails, in an attempt to fix a rare crash bug.
32098 - Only rewrite a conn's address based on X-Forwarded-For: headers
32099 if it's a parseable public IP address; and stop adding extra quotes
32100 to the resulting address.
32103 - Weight directory requests by advertised bandwidth. Now we can
32104 let servers enable write limiting but still allow most clients to
32105 succeed at their directory requests. (We still ignore weights when
32106 choosing a directory authority; I hope this is a feature.)
32109 - Create a new file ReleaseNotes which was the old ChangeLog. The
32110 new ChangeLog file now includes the summaries for all development
32112 - Check for addresses with invalid characters at the exit as well
32113 as at the client, and warn less verbosely when they fail. You can
32114 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
32115 - Adapt a patch from goodell to let the contrib/exitlist script
32116 take arguments rather than require direct editing.
32117 - Inform the server operator when we decide not to advertise a
32118 DirPort due to AccountingMax enabled or a low BandwidthRate. It
32119 was confusing Zax, so now we're hopefully more helpful.
32120 - Bring us one step closer to being able to establish an encrypted
32121 directory tunnel without knowing a descriptor first. Still not
32122 ready yet. As part of the change, now assume we can use a
32123 create_fast cell if we don't know anything about a router.
32124 - Allow exit nodes to use nameservers running on ports other than 53.
32125 - Servers now cache reverse DNS replies.
32126 - Add an --ignore-missing-torrc command-line option so that we can
32127 get the "use sensible defaults if the configuration file doesn't
32128 exist" behavior even when specifying a torrc location on the command
32131 o Minor features (controller):
32132 - Track reasons for OR connection failure; make these reasons
32133 available via the controller interface. (Patch from Mike Perry.)
32134 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
32135 can learn when clients are sending malformed hostnames to Tor.
32136 - Clean up documentation for controller status events.
32137 - Add a REMAP status to stream events to note that a stream's
32138 address has changed because of a cached address or a MapAddress
32142 Changes in version 0.1.2.6-alpha - 2007-01-09
32144 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
32145 connection handles more than 4 gigs in either direction, we crash.
32146 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
32147 advertised exit node, somebody might try to exit from us when
32148 we're bootstrapping and before we've built our descriptor yet.
32149 Refuse the connection rather than crashing.
32152 - Warn if we (as a server) find that we've resolved an address that we
32153 weren't planning to resolve.
32154 - Warn that using select() on any libevent version before 1.1 will be
32155 unnecessarily slow (even for select()).
32156 - Flush ERR-level controller status events just like we currently
32157 flush ERR-level log events, so that a Tor shutdown doesn't prevent
32158 the controller from learning about current events.
32160 o Minor features (more controller status events):
32161 - Implement EXTERNAL_ADDRESS server status event so controllers can
32162 learn when our address changes.
32163 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
32164 can learn when directories reject our descriptor.
32165 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
32166 can learn when a client application is speaking a non-socks protocol
32168 - Implement DANGEROUS_SOCKS client status event so controllers
32169 can learn when a client application is leaking DNS addresses.
32170 - Implement BUG general status event so controllers can learn when
32171 Tor is unhappy about its internal invariants.
32172 - Implement CLOCK_SKEW general status event so controllers can learn
32173 when Tor thinks the system clock is set incorrectly.
32174 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
32175 server status events so controllers can learn when their descriptors
32176 are accepted by a directory.
32177 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
32178 server status events so controllers can learn about Tor's progress in
32179 deciding whether it's reachable from the outside.
32180 - Implement BAD_LIBEVENT general status event so controllers can learn
32181 when we have a version/method combination in libevent that needs to
32183 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
32184 and DNS_USELESS server status events so controllers can learn
32185 about changes to DNS server status.
32187 o Minor features (directory):
32188 - Authorities no longer recommend exits as guards if this would shift
32189 too much load to the exit nodes.
32192 Changes in version 0.1.2.5-alpha - 2007-01-06
32194 - Enable write limiting as well as read limiting. Now we sacrifice
32195 capacity if we're pushing out lots of directory traffic, rather
32196 than overrunning the user's intended bandwidth limits.
32197 - Include TLS overhead when counting bandwidth usage; previously, we
32198 would count only the bytes sent over TLS, but not the bytes used
32200 - Support running the Tor service with a torrc not in the same
32201 directory as tor.exe and default to using the torrc located in
32202 the %appdata%\Tor\ of the user who installed the service. Patch
32204 - Servers now check for the case when common DNS requests are going to
32205 wildcarded addresses (i.e. all getting the same answer), and change
32206 their exit policy to reject *:* if it's happening.
32207 - Implement BEGIN_DIR cells, so we can connect to the directory
32208 server via TLS to do encrypted directory requests rather than
32209 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
32210 config options if you like.
32212 o Minor features (config and docs):
32213 - Start using the state file to store bandwidth accounting data:
32214 the bw_accounting file is now obsolete. We'll keep generating it
32215 for a while for people who are still using 0.1.2.4-alpha.
32216 - Try to batch changes to the state file so that we do as few
32217 disk writes as possible while still storing important things in
32219 - The state file and the bw_accounting file get saved less often when
32220 the AvoidDiskWrites config option is set.
32221 - Make PIDFile work on Windows (untested).
32222 - Add internal descriptions for a bunch of configuration options:
32223 accessible via controller interface and in comments in saved
32225 - Reject *:563 (NNTPS) in the default exit policy. We already reject
32226 NNTP by default, so this seems like a sensible addition.
32227 - Clients now reject hostnames with invalid characters. This should
32228 avoid some inadvertent info leaks. Add an option
32229 AllowNonRFC953Hostnames to disable this behavior, in case somebody
32230 is running a private network with hosts called @, !, and #.
32231 - Add a maintainer script to tell us which options are missing
32232 documentation: "make check-docs".
32233 - Add a new address-spec.txt document to describe our special-case
32234 addresses: .exit, .onion, and .noconnnect.
32236 o Minor features (DNS):
32237 - Ongoing work on eventdns infrastructure: now it has dns server
32238 and ipv6 support. One day Tor will make use of it.
32239 - Add client-side caching for reverse DNS lookups.
32240 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
32241 - When we change nameservers or IP addresses, reset and re-launch
32242 our tests for DNS hijacking.
32244 o Minor features (directory):
32245 - Authorities now specify server versions in networkstatus. This adds
32246 about 2% to the size of compressed networkstatus docs, and allows
32247 clients to tell which servers support BEGIN_DIR and which don't.
32248 The implementation is forward-compatible with a proposed future
32249 protocol version scheme not tied to Tor versions.
32250 - DirServer configuration lines now have an orport= option so
32251 clients can open encrypted tunnels to the authorities without
32252 having downloaded their descriptors yet. Enabled for moria1,
32253 moria2, tor26, and lefkada now in the default configuration.
32254 - Directory servers are more willing to send a 503 "busy" if they
32255 are near their write limit, especially for v1 directory requests.
32256 Now they can use their limited bandwidth for actual Tor traffic.
32257 - Clients track responses with status 503 from dirservers. After a
32258 dirserver has given us a 503, we try not to use it until an hour has
32259 gone by, or until we have no dirservers that haven't given us a 503.
32260 - When we get a 503 from a directory, and we're not a server, we don't
32261 count the failure against the total number of failures allowed
32262 for the thing we're trying to download.
32263 - Report X-Your-Address-Is correctly from tunneled directory
32264 connections; don't report X-Your-Address-Is when it's an internal
32265 address; and never believe reported remote addresses when they're
32267 - Protect against an unlikely DoS attack on directory servers.
32268 - Add a BadDirectory flag to network status docs so that authorities
32269 can (eventually) tell clients about caches they believe to be
32272 o Minor features (controller):
32273 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
32274 - Reimplement GETINFO so that info/names stays in sync with the
32276 - Implement "GETINFO fingerprint".
32277 - Implement "SETEVENTS GUARD" so controllers can get updates on
32278 entry guard status as it changes.
32280 o Minor features (clean up obsolete pieces):
32281 - Remove some options that have been deprecated since at least
32282 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
32283 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
32284 to set log options.
32285 - We no longer look for identity and onion keys in "identity.key" and
32286 "onion.key" -- these were replaced by secret_id_key and
32287 secret_onion_key in 0.0.8pre1.
32288 - We no longer require unrecognized directory entries to be
32291 o Major bugfixes (security):
32292 - Stop sending the HttpProxyAuthenticator string to directory
32293 servers when directory connections are tunnelled through Tor.
32294 - Clients no longer store bandwidth history in the state file.
32295 - Do not log introduction points for hidden services if SafeLogging
32297 - When generating bandwidth history, round down to the nearest
32298 1k. When storing accounting data, round up to the nearest 1k.
32299 - When we're running as a server, remember when we last rotated onion
32300 keys, so that we will rotate keys once they're a week old even if
32301 we never stay up for a week ourselves.
32303 o Major bugfixes (other):
32304 - Fix a longstanding bug in eventdns that prevented the count of
32305 timed-out resolves from ever being reset. This bug caused us to
32306 give up on a nameserver the third time it timed out, and try it
32307 10 seconds later... and to give up on it every time it timed out
32309 - Take out the '5 second' timeout from the connection retry
32310 schedule. Now the first connect attempt will wait a full 10
32311 seconds before switching to a new circuit. Perhaps this will help
32312 a lot. Based on observations from Mike Perry.
32313 - Fix a bug on the Windows implementation of tor_mmap_file() that
32314 would prevent the cached-routers file from ever loading. Reported
32318 - Fix an assert failure when a directory authority sets
32319 AuthDirRejectUnlisted and then receives a descriptor from an
32320 unlisted router. Reported by seeess.
32321 - Avoid a double-free when parsing malformed DirServer lines.
32322 - Fix a bug when a BSD-style PF socket is first used. Patch from
32324 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
32325 to resolve an address at a given exit node even when they ask for
32327 - Servers no longer ever list themselves in their "family" line,
32328 even if configured to do so. This makes it easier to configure
32329 family lists conveniently.
32330 - When running as a server, don't fall back to 127.0.0.1 when no
32331 nameservers are configured in /etc/resolv.conf; instead, make the
32332 user fix resolv.conf or specify nameservers explicitly. (Resolves
32334 - Stop accepting certain malformed ports in configured exit policies.
32335 - Don't re-write the fingerprint file every restart, unless it has
32337 - Stop warning when a single nameserver fails: only warn when _all_ of
32338 our nameservers have failed. Also, when we only have one nameserver,
32339 raise the threshold for deciding that the nameserver is dead.
32340 - Directory authorities now only decide that routers are reachable
32341 if their identity keys are as expected.
32342 - When the user uses bad syntax in the Log config line, stop
32343 suggesting other bad syntax as a replacement.
32344 - Correctly detect ipv6 DNS capability on OpenBSD.
32346 o Minor bugfixes (controller):
32347 - Report the circuit number correctly in STREAM CLOSED events. Bug
32348 reported by Mike Perry.
32349 - Do not report bizarre values for results of accounting GETINFOs
32350 when the last second's write or read exceeds the allotted bandwidth.
32351 - Report "unrecognized key" rather than an empty string when the
32352 controller tries to fetch a networkstatus that doesn't exist.
32355 Changes in version 0.1.1.26 - 2006-12-14
32356 o Security bugfixes:
32357 - Stop sending the HttpProxyAuthenticator string to directory
32358 servers when directory connections are tunnelled through Tor.
32359 - Clients no longer store bandwidth history in the state file.
32360 - Do not log introduction points for hidden services if SafeLogging
32364 - Fix an assert failure when a directory authority sets
32365 AuthDirRejectUnlisted and then receives a descriptor from an
32366 unlisted router (reported by seeess).
32369 Changes in version 0.1.2.4-alpha - 2006-12-03
32371 - Add support for using natd; this allows FreeBSDs earlier than
32372 5.1.2 to have ipfw send connections through Tor without using
32373 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
32376 - Make all connections to addresses of the form ".noconnect"
32377 immediately get closed. This lets application/controller combos
32378 successfully test whether they're talking to the same Tor by
32379 watching for STREAM events.
32380 - Make cross.sh cross-compilation script work even when autogen.sh
32381 hasn't been run. (Patch from Michael Mohr.)
32382 - Statistics dumped by -USR2 now include a breakdown of public key
32383 operations, for profiling.
32386 - Fix a major leak when directory authorities parse their
32387 approved-routers list, a minor memory leak when we fail to pick
32388 an exit node, and a few rare leaks on errors.
32389 - Handle TransPort connections even when the server sends data before
32390 the client sends data. Previously, the connection would just hang
32391 until the client sent data. (Patch from tup based on patch from
32393 - Avoid assert failure when our cached-routers file is empty on
32397 - Don't log spurious warnings when we see a circuit close reason we
32398 don't recognize; it's probably just from a newer version of Tor.
32399 - Have directory authorities allow larger amounts of drift in uptime
32400 without replacing the server descriptor: previously, a server that
32401 restarted every 30 minutes could have 48 "interesting" descriptors
32403 - Start linking to the Tor specification and Tor reference manual
32404 correctly in the Windows installer.
32405 - Add Vidalia to the OS X uninstaller script, so when we uninstall
32406 Tor/Privoxy we also uninstall Vidalia.
32407 - Resume building on Irix64, and fix a lot of warnings from its
32408 MIPSpro C compiler.
32409 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
32410 when we're running as a client.
32413 Changes in version 0.1.1.25 - 2006-11-04
32415 - When a client asks us to resolve (rather than connect to)
32416 an address, and we have a cached answer, give them the cached
32417 answer. Previously, we would give them no answer at all.
32418 - We were building exactly the wrong circuits when we predict
32419 hidden service requirements, meaning Tor would have to build all
32420 its circuits on demand.
32421 - If none of our live entry guards have a high uptime, but we
32422 require a guard with a high uptime, try adding a new guard before
32423 we give up on the requirement. This patch should make long-lived
32424 connections more stable on average.
32425 - When testing reachability of our DirPort, don't launch new
32426 tests when there's already one in progress -- unreachable
32427 servers were stacking up dozens of testing streams.
32429 o Security bugfixes:
32430 - When the user sends a NEWNYM signal, clear the client-side DNS
32431 cache too. Otherwise we continue to act on previous information.
32434 - Avoid a memory corruption bug when creating a hash table for
32436 - Avoid possibility of controller-triggered crash when misusing
32437 certain commands from a v0 controller on platforms that do not
32438 handle printf("%s",NULL) gracefully.
32439 - Avoid infinite loop on unexpected controller input.
32440 - Don't log spurious warnings when we see a circuit close reason we
32441 don't recognize; it's probably just from a newer version of Tor.
32442 - Add Vidalia to the OS X uninstaller script, so when we uninstall
32443 Tor/Privoxy we also uninstall Vidalia.
32446 Changes in version 0.1.2.3-alpha - 2006-10-29
32448 - Prepare for servers to publish descriptors less often: never
32449 discard a descriptor simply for being too old until either it is
32450 recommended by no authorities, or until we get a better one for
32451 the same router. Make caches consider retaining old recommended
32452 routers for even longer.
32453 - If most authorities set a BadExit flag for a server, clients
32454 don't think of it as a general-purpose exit. Clients only consider
32455 authorities that advertise themselves as listing bad exits.
32456 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
32457 headers for content, so that we can work better in the presence of
32458 caching HTTP proxies.
32459 - Allow authorities to list nodes as bad exits by fingerprint or by
32462 o Minor features, controller:
32463 - Add a REASON field to CIRC events; for backward compatibility, this
32464 field is sent only to controllers that have enabled the extended
32465 event format. Also, add additional reason codes to explain why
32466 a given circuit has been destroyed or truncated. (Patches from
32468 - Add a REMOTE_REASON field to extended CIRC events to tell the
32469 controller about why a remote OR told us to close a circuit.
32470 - Stream events also now have REASON and REMOTE_REASON fields,
32471 working much like those for circuit events.
32472 - There's now a GETINFO ns/... field so that controllers can ask Tor
32473 about the current status of a router.
32474 - A new event type "NS" to inform a controller when our opinion of
32475 a router's status has changed.
32476 - Add a GETINFO events/names and GETINFO features/names so controllers
32477 can tell which events and features are supported.
32478 - A new CLEARDNSCACHE signal to allow controllers to clear the
32479 client-side DNS cache without expiring circuits.
32481 o Security bugfixes:
32482 - When the user sends a NEWNYM signal, clear the client-side DNS
32483 cache too. Otherwise we continue to act on previous information.
32486 - Avoid sending junk to controllers or segfaulting when a controller
32487 uses EVENT_NEW_DESC with verbose nicknames.
32488 - Stop triggering asserts if the controller tries to extend hidden
32489 service circuits (reported by mwenge).
32490 - Avoid infinite loop on unexpected controller input.
32491 - When the controller does a "GETINFO network-status", tell it
32492 about even those routers whose descriptors are very old, and use
32493 long nicknames where appropriate.
32494 - Change NT service functions to be loaded on demand. This lets us
32495 build with MinGW without breaking Tor for Windows 98 users.
32496 - Do DirPort reachability tests less often, since a single test
32497 chews through many circuits before giving up.
32498 - In the hidden service example in torrc.sample, stop recommending
32499 esoteric and discouraged hidden service options.
32500 - When stopping an NT service, wait up to 10 sec for it to actually
32501 stop. Patch from Matt Edman; resolves bug 295.
32502 - Fix handling of verbose nicknames with ORCONN controller events:
32503 make them show up exactly when requested, rather than exactly when
32505 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
32506 printing a duplicate "$" in the keys we send (reported by mwenge).
32507 - Correctly set maximum connection limit on Cygwin. (This time
32509 - Try to detect Windows correctly when cross-compiling.
32510 - Detect the size of the routers file correctly even if it is
32511 corrupted (on systems without mmap) or not page-aligned (on systems
32512 with mmap). This bug was harmless.
32513 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
32514 to open a stream fails; now we do in more cases. This should
32515 make clients able to find a good exit faster in some cases, since
32516 unhandleable requests will now get an error rather than timing out.
32517 - Resolve two memory leaks when rebuilding the on-disk router cache
32518 (reported by fookoowa).
32519 - Clean up minor code warnings suggested by the MIPSpro C compiler,
32520 and reported by some Centos users.
32521 - Controller signals now work on non-Unix platforms that don't define
32522 SIGUSR1 and SIGUSR2 the way we expect.
32523 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
32524 values before failing, and always enables eventdns.
32525 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
32526 Try to fix this in configure.in by checking for most functions
32527 before we check for libevent.
32530 Changes in version 0.1.2.2-alpha - 2006-10-07
32532 - Make our async eventdns library on-by-default for Tor servers,
32533 and plan to deprecate the separate dnsworker threads.
32534 - Add server-side support for "reverse" DNS lookups (using PTR
32535 records so clients can determine the canonical hostname for a given
32536 IPv4 address). Only supported by servers using eventdns; servers
32537 now announce in their descriptors whether they support eventdns.
32538 - Specify and implement client-side SOCKS5 interface for reverse DNS
32539 lookups (see doc/socks-extensions.txt).
32540 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
32541 connect to directory servers through Tor. Previously, clients needed
32542 to find Tor exits to make private connections to directory servers.
32543 - Avoid choosing Exit nodes for entry or middle hops when the
32544 total bandwidth available from non-Exit nodes is much higher than
32545 the total bandwidth available from Exit nodes.
32546 - Workaround for name servers (like Earthlink's) that hijack failing
32547 DNS requests and replace the no-such-server answer with a "helpful"
32548 redirect to an advertising-driven search portal. Also work around
32549 DNS hijackers who "helpfully" decline to hijack known-invalid
32550 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
32551 lets you turn it off.
32552 - Send out a burst of long-range padding cells once we've established
32553 that we're reachable. Spread them over 4 circuits, so hopefully
32554 a few will be fast. This exercises our bandwidth and bootstraps
32555 us into the directory more quickly.
32557 o New/improved config options:
32558 - Add new config option "ResolvConf" to let the server operator
32559 choose an alternate resolve.conf file when using eventdns.
32560 - Add an "EnforceDistinctSubnets" option to control our "exclude
32561 servers on the same /16" behavior. It's still on by default; this
32562 is mostly for people who want to operate private test networks with
32563 all the machines on the same subnet.
32564 - If one of our entry guards is on the ExcludeNodes list, or the
32565 directory authorities don't think it's a good guard, treat it as
32566 if it were unlisted: stop using it as a guard, and throw it off
32567 the guards list if it stays that way for a long time.
32568 - Allow directory authorities to be marked separately as authorities
32569 for the v1 directory protocol, the v2 directory protocol, and
32570 as hidden service directories, to make it easier to retire old
32571 authorities. V1 authorities should set "HSAuthoritativeDir 1"
32572 to continue being hidden service authorities too.
32573 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
32575 o Minor features, controller:
32576 - Fix CIRC controller events so that controllers can learn the
32577 identity digests of non-Named servers used in circuit paths.
32578 - Let controllers ask for more useful identifiers for servers. Instead
32579 of learning identity digests for un-Named servers and nicknames
32580 for Named servers, the new identifiers include digest, nickname,
32581 and indication of Named status. Off by default; see control-spec.txt
32582 for more information.
32583 - Add a "getinfo address" controller command so it can display Tor's
32584 best guess to the user.
32585 - New controller event to alert the controller when our server
32586 descriptor has changed.
32587 - Give more meaningful errors on controller authentication failure.
32589 o Minor features, other:
32590 - When asked to resolve a hostname, don't use non-exit servers unless
32591 requested to do so. This allows servers with broken DNS to be
32592 useful to the network.
32593 - Divide eventdns log messages into warn and info messages.
32594 - Reserve the nickname "Unnamed" for routers that can't pick
32595 a hostname: any router can call itself Unnamed; directory
32596 authorities will never allocate Unnamed to any particular router;
32597 clients won't believe that any router is the canonical Unnamed.
32598 - Only include function names in log messages for info/debug messages.
32599 For notice/warn/err, the content of the message should be clear on
32600 its own, and printing the function name only confuses users.
32601 - Avoid some false positives during reachability testing: don't try
32602 to test via a server that's on the same /24 as us.
32603 - If we fail to build a circuit to an intended enclave, and it's
32604 not mandatory that we use that enclave, stop wanting it.
32605 - When eventdns is enabled, allow multithreaded builds on NetBSD and
32606 OpenBSD. (We had previously disabled threads on these platforms
32607 because they didn't have working thread-safe resolver functions.)
32609 o Major bugfixes, anonymity/security:
32610 - If a client asked for a server by name, and there's a named server
32611 in our network-status but we don't have its descriptor yet, we
32612 could return an unnamed server instead.
32613 - Fix NetBSD bug that could allow someone to force uninitialized RAM
32614 to be sent to a server's DNS resolver. This only affects NetBSD
32615 and other platforms that do not bounds-check tolower().
32616 - Reject (most) attempts to use Tor circuits with length one. (If
32617 many people start using Tor as a one-hop proxy, exit nodes become
32618 a more attractive target for compromise.)
32619 - Just because your DirPort is open doesn't mean people should be
32620 able to remotely teach you about hidden service descriptors. Now
32621 only accept rendezvous posts if you've got HSAuthoritativeDir set.
32623 o Major bugfixes, other:
32624 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
32625 - When a client asks the server to resolve (not connect to)
32626 an address, and it has a cached answer, give them the cached answer.
32627 Previously, the server would give them no answer at all.
32628 - Allow really slow clients to not hang up five minutes into their
32629 directory downloads (suggested by Adam J. Richter).
32630 - We were building exactly the wrong circuits when we anticipated
32631 hidden service requirements, meaning Tor would have to build all
32632 its circuits on demand.
32633 - Avoid crashing when we mmap a router cache file of size 0.
32634 - When testing reachability of our DirPort, don't launch new
32635 tests when there's already one in progress -- unreachable
32636 servers were stacking up dozens of testing streams.
32638 o Minor bugfixes, correctness:
32639 - If we're a directory mirror and we ask for "all" network status
32640 documents, we would discard status documents from authorities
32641 we don't recognize.
32642 - Avoid a memory corruption bug when creating a hash table for
32644 - Avoid controller-triggered crash when misusing certain commands
32645 from a v0 controller on platforms that do not handle
32646 printf("%s",NULL) gracefully.
32647 - Don't crash when a controller sends a third argument to an
32648 "extendcircuit" request.
32649 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
32650 response; fix error code when "getinfo dir/status/" fails.
32651 - Avoid crash when telling controller stream-status and a stream
32653 - Patch from Adam Langley to fix assert() in eventdns.c.
32654 - Fix a debug log message in eventdns to say "X resolved to Y"
32655 instead of "X resolved to X".
32656 - Make eventdns give strings for DNS errors, not just error numbers.
32657 - Track unreachable entry guards correctly: don't conflate
32658 'unreachable by us right now' with 'listed as down by the directory
32659 authorities'. With the old code, if a guard was unreachable by
32660 us but listed as running, it would clog our guard list forever.
32661 - Behave correctly in case we ever have a network with more than
32662 2GB/s total advertised capacity.
32663 - Make TrackExitHosts case-insensitive, and fix the behavior of
32664 ".suffix" TrackExitHosts items to avoid matching in the middle of
32666 - Finally fix the openssl warnings from newer gccs that believe that
32667 ignoring a return value is okay, but casting a return value and
32668 then ignoring it is a sign of madness.
32669 - Prevent the contrib/exitlist script from printing the same
32670 result more than once.
32671 - Patch from Steve Hildrey: Generate network status correctly on
32672 non-versioning dirservers.
32673 - Don't listen to the X-Your-Address-Is hint if you did the lookup
32674 via Tor; otherwise you'll think you're the exit node's IP address.
32676 o Minor bugfixes, performance:
32677 - Two small performance improvements on parsing descriptors.
32678 - Major performance improvement on inserting descriptors: change
32679 algorithm from O(n^2) to O(n).
32680 - Make the common memory allocation path faster on machines where
32681 malloc(0) returns a pointer.
32682 - Start remembering X-Your-Address-Is directory hints even if you're
32683 a client, so you can become a server more smoothly.
32684 - Avoid duplicate entries on MyFamily line in server descriptor.
32686 o Packaging, features:
32687 - Remove architecture from OS X builds. The official builds are
32688 now universal binaries.
32689 - The Debian package now uses --verify-config when (re)starting,
32690 to distinguish configuration errors from other errors.
32691 - Update RPMs to require libevent 1.1b.
32693 o Packaging, bugfixes:
32694 - Patches so Tor builds with MinGW on Windows.
32695 - Patches so Tor might run on Cygwin again.
32696 - Resume building on non-gcc compilers and ancient gcc. Resume
32697 building with the -O0 compile flag. Resume building cleanly on
32699 - Run correctly on OS X platforms with case-sensitive filesystems.
32700 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
32701 - Add autoconf checks so Tor can build on Solaris x86 again.
32704 - Documented (and renamed) ServerDNSSearchDomains and
32705 ServerDNSResolvConfFile options.
32706 - Be clearer that the *ListenAddress directives can be repeated
32710 Changes in version 0.1.1.24 - 2006-09-29
32712 - Allow really slow clients to not hang up five minutes into their
32713 directory downloads (suggested by Adam J. Richter).
32714 - Fix major performance regression from 0.1.0.x: instead of checking
32715 whether we have enough directory information every time we want to
32716 do something, only check when the directory information has changed.
32717 This should improve client CPU usage by 25-50%.
32718 - Don't crash if, after a server has been running for a while,
32719 it can't resolve its hostname.
32722 - Allow Tor to start when RunAsDaemon is set but no logs are set.
32723 - Don't crash when the controller receives a third argument to an
32724 "extendcircuit" request.
32725 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
32726 response; fix error code when "getinfo dir/status/" fails.
32727 - Fix configure.in to not produce broken configure files with
32728 more recent versions of autoconf. Thanks to Clint for his auto*
32730 - Fix security bug on NetBSD that could allow someone to force
32731 uninitialized RAM to be sent to a server's DNS resolver. This
32732 only affects NetBSD and other platforms that do not bounds-check
32734 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
32735 methods: these are known to be buggy.
32736 - If we're a directory mirror and we ask for "all" network status
32737 documents, we would discard status documents from authorities
32738 we don't recognize.
32741 Changes in version 0.1.2.1-alpha - 2006-08-27
32743 - Add "eventdns" async dns library from Adam Langley, tweaked to
32744 build on OSX and Windows. Only enabled if you pass the
32745 --enable-eventdns argument to configure.
32746 - Allow servers with no hostname or IP address to learn their
32747 IP address by asking the directory authorities. This code only
32748 kicks in when you would normally have exited with a "no address"
32749 error. Nothing's authenticated, so use with care.
32750 - Rather than waiting a fixed amount of time between retrying
32751 application connections, we wait only 5 seconds for the first,
32752 10 seconds for the second, and 15 seconds for each retry after
32753 that. Hopefully this will improve the expected user experience.
32754 - Patch from Tup to add support for transparent AP connections:
32755 this basically bundles the functionality of trans-proxy-tor
32756 into the Tor mainline. Now hosts with compliant pf/netfilter
32757 implementations can redirect TCP connections straight to Tor
32758 without diverting through SOCKS. Needs docs.
32759 - Busy directory servers save lots of memory by spooling server
32760 descriptors, v1 directories, and v2 networkstatus docs to buffers
32761 as needed rather than en masse. Also mmap the cached-routers
32762 files, so we don't need to keep the whole thing in memory too.
32763 - Automatically avoid picking more than one node from the same
32764 /16 network when constructing a circuit.
32765 - Revise and clean up the torrc.sample that we ship with; add
32766 a section for BandwidthRate and BandwidthBurst.
32769 - Split circuit_t into origin_circuit_t and or_circuit_t, and
32770 split connection_t into edge, or, dir, control, and base structs.
32771 These will save quite a bit of memory on busy servers, and they'll
32772 also help us track down bugs in the code and bugs in the spec.
32773 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
32774 or later. Log when we are doing this, so we can diagnose it when
32775 it fails. (Also, recommend libevent 1.1b for kqueue and
32776 win32 methods; deprecate libevent 1.0b harder; make libevent
32777 recommendation system saner.)
32778 - Start being able to build universal binaries on OS X (thanks
32780 - Export the default exit policy via the control port, so controllers
32781 don't need to guess what it is / will be later.
32782 - Add a man page entry for ProtocolWarnings.
32783 - Add TestVia config option to the man page.
32784 - Remove even more protocol-related warnings from Tor server logs,
32785 such as bad TLS handshakes and malformed begin cells.
32786 - Stop fetching descriptors if you're not a dir mirror and you
32787 haven't tried to establish any circuits lately. [This currently
32788 causes some dangerous behavior, because when you start up again
32789 you'll use your ancient server descriptors.]
32790 - New DirPort behavior: if you have your dirport set, you download
32791 descriptors aggressively like a directory mirror, whether or not
32792 your ORPort is set.
32793 - Get rid of the router_retry_connections notion. Now routers
32794 no longer try to rebuild long-term connections to directory
32795 authorities, and directory authorities no longer try to rebuild
32796 long-term connections to all servers. We still don't hang up
32797 connections in these two cases though -- we need to look at it
32798 more carefully to avoid flapping, and we likely need to wait til
32799 0.1.1.x is obsolete.
32800 - Drop compatibility with obsolete Tors that permit create cells
32801 to have the wrong circ_id_type.
32802 - Re-enable per-connection rate limiting. Get rid of the "OP
32803 bandwidth" concept. Lay groundwork for "bandwidth classes" --
32804 separate global buckets that apply depending on what sort of conn
32806 - Start publishing one minute or so after we find our ORPort
32807 to be reachable. This will help reduce the number of descriptors
32808 we have for ourselves floating around, since it's quite likely
32809 other things (e.g. DirPort) will change during that minute too.
32810 - Fork the v1 directory protocol into its own spec document,
32811 and mark dir-spec.txt as the currently correct (v2) spec.
32814 - When we find our DirPort to be reachable, publish a new descriptor
32815 so we'll tell the world (reported by pnx).
32816 - Publish a new descriptor after we hup/reload. This is important
32817 if our config has changed such that we'll want to start advertising
32818 our DirPort now, etc.
32819 - Allow Tor to start when RunAsDaemon is set but no logs are set.
32820 - When we have a state file we cannot parse, tell the user and
32821 move it aside. Now we avoid situations where the user starts
32822 Tor in 1904, Tor writes a state file with that timestamp in it,
32823 the user fixes her clock, and Tor refuses to start.
32824 - Fix configure.in to not produce broken configure files with
32825 more recent versions of autoconf. Thanks to Clint for his auto*
32827 - "tor --verify-config" now exits with -1(255) or 0 depending on
32828 whether the config options are bad or good.
32829 - Resolve bug 321 when using dnsworkers: append a period to every
32830 address we resolve at the exit node, so that we do not accidentally
32831 pick up local addresses, and so that failing searches are retried
32832 in the resolver search domains. (This is already solved for
32833 eventdns.) (This breaks Blossom servers for now.)
32834 - If we are using an exit enclave and we can't connect, e.g. because
32835 its webserver is misconfigured to not listen on localhost, then
32836 back off and try connecting from somewhere else before we fail.
32839 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
32840 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
32841 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
32842 when the IP address is mapped through MapAddress to a hostname.
32843 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
32844 useless IPv6 DNS resolves.
32845 - Patch suggested by Karsten Loesing: respond to SIGNAL command
32846 before we execute the signal, in case the signal shuts us down.
32847 - Clean up AllowInvalidNodes man page entry.
32848 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
32849 - Add more asserts to track down an assert error on a windows Tor
32850 server with connection_add being called with socket == -1.
32851 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
32852 - Fix misleading log messages: an entry guard that is "unlisted",
32853 as well as not known to be "down" (because we've never heard
32854 of it), is not therefore "up".
32855 - Remove code to special-case "-cvs" ending, since it has not
32856 actually mattered since 0.0.9.
32857 - Make our socks5 handling more robust to broken socks clients:
32858 throw out everything waiting on the buffer in between socks
32859 handshake phases, since they can't possibly (so the theory
32860 goes) have predicted what we plan to respond to them.
32863 Changes in version 0.1.1.23 - 2006-07-30
32865 - Fast Tor servers, especially exit nodes, were triggering asserts
32866 due to a bug in handling the list of pending DNS resolves. Some
32867 bugs still remain here; we're hunting them.
32868 - Entry guards could crash clients by sending unexpected input.
32869 - More fixes on reachability testing: if you find yourself reachable,
32870 then don't ever make any client requests (so you stop predicting
32871 circuits), then hup or have your clock jump, then later your IP
32872 changes, you won't think circuits are working, so you won't try to
32873 test reachability, so you won't publish.
32876 - Avoid a crash if the controller does a resetconf firewallports
32877 and then a setconf fascistfirewall=1.
32878 - Avoid an integer underflow when the dir authority decides whether
32879 a router is stable: we might wrongly label it stable, and compute
32880 a slightly wrong median stability, when a descriptor is published
32882 - Fix a place where we might trigger an assert if we can't build our
32883 own server descriptor yet.
32886 Changes in version 0.1.1.22 - 2006-07-05
32888 - Fix a big bug that was causing servers to not find themselves
32889 reachable if they changed IP addresses. Since only 0.1.1.22+
32890 servers can do reachability testing correctly, now we automatically
32891 make sure to test via one of these.
32892 - Fix to allow clients and mirrors to learn directory info from
32893 descriptor downloads that get cut off partway through.
32894 - Directory authorities had a bug in deciding if a newly published
32895 descriptor was novel enough to make everybody want a copy -- a few
32896 servers seem to be publishing new descriptors many times a minute.
32898 - Fix a rare bug that was causing some servers to complain about
32899 "closing wedged cpuworkers" and skip some circuit create requests.
32900 - Make the Exit flag in directory status documents actually work.
32903 Changes in version 0.1.1.21 - 2006-06-10
32904 o Crash and assert fixes from 0.1.1.20:
32905 - Fix a rare crash on Tor servers that have enabled hibernation.
32906 - Fix a seg fault on startup for Tor networks that use only one
32907 directory authority.
32908 - Fix an assert from a race condition that occurs on Tor servers
32909 while exiting, where various threads are trying to log that they're
32910 exiting, and delete the logs, at the same time.
32911 - Make our unit tests pass again on certain obscure platforms.
32914 - Add support for building SUSE RPM packages.
32915 - Speed up initial bootstrapping for clients: if we are making our
32916 first ever connection to any entry guard, then don't mark it down
32918 - When only one Tor server in the network is labelled as a guard,
32919 and we've already picked him, we would cycle endlessly picking him
32920 again, being unhappy about it, etc. Now we specifically exclude
32921 current guards when picking a new guard.
32922 - Servers send create cells more reliably after the TLS connection
32923 is established: we were sometimes forgetting to send half of them
32924 when we had more than one pending.
32925 - If we get a create cell that asks us to extend somewhere, but the
32926 Tor server there doesn't match the expected digest, we now send
32927 a destroy cell back, rather than silently doing nothing.
32928 - Make options->RedirectExit work again.
32929 - Make cookie authentication for the controller work again.
32930 - Stop being picky about unusual characters in the arguments to
32931 mapaddress. It's none of our business.
32932 - Add a new config option "TestVia" that lets you specify preferred
32933 middle hops to use for test circuits. Perhaps this will let me
32934 debug the reachability problems better.
32936 o Log / documentation fixes:
32937 - If we're a server and some peer has a broken TLS certificate, don't
32938 log about it unless ProtocolWarnings is set, i.e., we want to hear
32939 about protocol violations by others.
32940 - Fix spelling of VirtualAddrNetwork in man page.
32941 - Add a better explanation at the top of the autogenerated torrc file
32942 about what happened to our old torrc.
32945 Changes in version 0.1.1.20 - 2006-05-23
32947 - Downgrade a log severity where servers complain that they're
32949 - Avoid a compile warning on FreeBSD.
32950 - Remove string size limit on NEWDESC messages; solve bug 291.
32951 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
32952 more thoroughly when we're running on windows.
32955 Changes in version 0.1.1.19-rc - 2006-05-03
32957 - Regenerate our local descriptor if it's dirty and we try to use
32958 it locally (e.g. if it changes during reachability detection).
32959 - If we setconf our ORPort to 0, we continued to listen on the
32960 old ORPort and receive connections.
32961 - Avoid a second warning about machine/limits.h on Debian
32963 - Be willing to add our own routerinfo into the routerlist.
32964 Now authorities will include themselves in their directories
32965 and network-statuses.
32966 - Stop trying to upload rendezvous descriptors to every
32967 directory authority: only try the v1 authorities.
32968 - Servers no longer complain when they think they're not
32969 registered with the directory authorities. There were too many
32971 - Backport dist-rpm changes so rpms can be built without errors.
32974 - Implement an option, VirtualAddrMask, to set which addresses
32975 get handed out in response to mapaddress requests. This works
32976 around a bug in tsocks where 127.0.0.0/8 is never socksified.
32979 Changes in version 0.1.1.18-rc - 2006-04-10
32981 - Work harder to download live network-statuses from all the
32982 directory authorities we know about. Improve the threshold
32983 decision logic so we're more robust to edge cases.
32984 - When fetching rendezvous descriptors, we were willing to ask
32985 v2 authorities too, which would always return 404.
32988 - Stop listing down or invalid nodes in the v1 directory. This will
32989 reduce its bulk by about 1/3, and reduce load on directory
32991 - When deciding whether a router is Fast or Guard-worthy, consider
32992 his advertised BandwidthRate and not just the BandwidthCapacity.
32993 - No longer ship INSTALL and README files -- they are useless now.
32994 - Force rpmbuild to behave and honor target_cpu.
32995 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
32996 - Start to include translated versions of the tor-doc-*.html
32997 files, along with the screenshots. Still needs more work.
32998 - Start sending back 512 and 451 errors if mapaddress fails,
32999 rather than not sending anything back at all.
33000 - When we fail to bind or listen on an incoming or outgoing
33001 socket, we should close it before failing. otherwise we just
33002 leak it. (thanks to weasel for finding.)
33003 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
33004 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
33005 - Make NoPublish (even though deprecated) work again.
33006 - Fix a minor security flaw where a versioning auth dirserver
33007 could list a recommended version many times in a row to make
33008 clients more convinced that it's recommended.
33009 - Fix crash bug if there are two unregistered servers running
33010 with the same nickname, one of them is down, and you ask for
33011 them by nickname in your EntryNodes or ExitNodes. Also, try
33012 to pick the one that's running rather than an arbitrary one.
33013 - Fix an infinite loop we could hit if we go offline for too long.
33014 - Complain when we hit WSAENOBUFS on recv() or write() too.
33015 Perhaps this will help us hunt the bug.
33016 - If you're not a versioning dirserver, don't put the string
33017 "client-versions \nserver-versions \n" in your network-status.
33018 - Lower the minimum required number of file descriptors to 1000,
33019 so we can have some overhead for Valgrind on Linux, where the
33020 default ulimit -n is 1024.
33023 - Add tor.dizum.com as the fifth authoritative directory server.
33024 - Add a new config option FetchUselessDescriptors, off by default,
33025 for when you plan to run "exitlist" on your client and you want
33026 to know about even the non-running descriptors.
33029 Changes in version 0.1.1.17-rc - 2006-03-28
33031 - Clients and servers since 0.1.1.10-alpha have been expiring
33032 connections whenever they are idle for 5 minutes and they *do*
33033 have circuits on them. Oops. With this new version, clients will
33034 discard their previous entry guard choices and avoid choosing
33035 entry guards running these flawed versions.
33036 - Fix memory leak when uncompressing concatenated zlib streams. This
33037 was causing substantial leaks over time on Tor servers.
33038 - The v1 directory was including servers as much as 48 hours old,
33039 because that's how the new routerlist->routers works. Now only
33040 include them if they're 20 hours old or less.
33043 - Resume building on irix64, netbsd 2.0, etc.
33044 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
33046 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
33047 and it is confusing some users.
33048 - Mirrors stop caching the v1 directory so often.
33049 - Make the max number of old descriptors that a cache will hold
33050 rise with the number of directory authorities, so we can scale.
33051 - Change our win32 uname() hack to be more forgiving about what
33052 win32 versions it thinks it's found.
33055 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
33057 - When the controller's *setconf commands fail, collect an error
33058 message in a string and hand it back to the controller.
33059 - Make the v2 dir's "Fast" flag based on relative capacity, just
33060 like "Stable" is based on median uptime. Name everything in the
33061 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
33062 - Log server fingerprint on startup, so new server operators don't
33063 have to go hunting around their filesystem for it.
33064 - Return a robots.txt on our dirport to discourage google indexing.
33065 - Let the controller ask for GETINFO dir/status/foo so it can ask
33066 directly rather than connecting to the dir port. Only works when
33067 dirport is set for now.
33069 o New config options rather than constants in the code:
33070 - SocksTimeout: How long do we let a socks connection wait
33071 unattached before we fail it?
33072 - CircuitBuildTimeout: Cull non-open circuits that were born
33073 at least this many seconds ago.
33074 - CircuitIdleTimeout: Cull open clean circuits that were born
33075 at least this many seconds ago.
33078 Changes in version 0.1.1.16-rc - 2006-03-18
33079 o Bugfixes on 0.1.1.15-rc:
33080 - Fix assert when the controller asks to attachstream a connect-wait
33081 or resolve-wait stream.
33082 - Now do address rewriting when the controller asks us to attach
33083 to a particular circuit too. This will let Blossom specify
33084 "moria2.exit" without having to learn what moria2's IP address is.
33085 - Make the "tor --verify-config" command-line work again, so people
33086 can automatically check if their torrc will parse.
33087 - Authoritative dirservers no longer require an open connection from
33088 a server to consider him "reachable". We need this change because
33089 when we add new auth dirservers, old servers won't know not to
33091 - Let Tor build on Sun CC again.
33092 - Fix an off-by-one buffer size in dirserv.c that magically never
33093 hit our three authorities but broke sjmurdoch's own tor network.
33094 - If we as a directory mirror don't know of any v1 directory
33095 authorities, then don't try to cache any v1 directories.
33096 - Stop warning about unknown servers in our family when they are
33097 given as hex digests.
33098 - Stop complaining as quickly to the server operator that he
33099 hasn't registered his nickname/key binding.
33100 - Various cleanups so we can add new V2 Auth Dirservers.
33101 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
33102 reflect the updated flags in our v2 dir protocol.
33103 - Resume allowing non-printable characters for exit streams (both
33104 for connecting and for resolving). Now we tolerate applications
33105 that don't follow the RFCs. But continue to block malformed names
33108 o Bugfixes on 0.1.0.x:
33109 - Fix assert bug in close_logs(): when we close and delete logs,
33110 remove them all from the global "logfiles" list.
33111 - Fix minor integer overflow in calculating when we expect to use up
33112 our bandwidth allocation before hibernating.
33113 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
33114 there are multiple SSLs installed with different versions.
33115 - When we try to be a server and Address is not explicitly set and
33116 our hostname resolves to a private IP address, try to use an
33117 interface address if it has a public address. Now Windows machines
33118 that think of themselves as localhost can work by default.
33121 - Let the controller ask for GETINFO dir/server/foo so it can ask
33122 directly rather than connecting to the dir port.
33123 - Let the controller tell us about certain router descriptors
33124 that it doesn't want Tor to use in circuits. Implement
33125 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
33126 - New config option SafeSocks to reject all application connections
33127 using unsafe socks protocols. Defaults to off.
33130 Changes in version 0.1.1.15-rc - 2006-03-11
33131 o Bugfixes and cleanups:
33132 - When we're printing strings from the network, don't try to print
33133 non-printable characters. This protects us against shell escape
33134 sequence exploits, and also against attacks to fool humans into
33135 misreading their logs.
33136 - Fix a bug where Tor would fail to establish any connections if you
33137 left it off for 24 hours and then started it: we were happy with
33138 the obsolete network statuses, but they all referred to router
33139 descriptors that were too old to fetch, so we ended up with no
33140 valid router descriptors.
33141 - Fix a seg fault in the controller's "getinfo orconn-status"
33142 command while listing status on incoming handshaking connections.
33143 Introduce a status name "NEW" for these connections.
33144 - If we get a linelist or linelist_s config option from the torrc
33145 (e.g. ExitPolicy) and it has no value, warn and skip rather than
33146 silently resetting it to its default.
33147 - Don't abandon entry guards until they've been down or gone for
33149 - Cleaner and quieter log messages.
33152 - New controller signal NEWNYM that makes new application requests
33153 use clean circuits.
33154 - Add a new circuit purpose 'controller' to let the controller ask
33155 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
33156 controller command to let you specify the purpose if you're
33157 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
33158 command to let you change a circuit's purpose after it's been
33160 - Accept "private:*" in routerdesc exit policies; not generated yet
33161 because older Tors do not understand it.
33162 - Add BSD-style contributed startup script "rc.subr" from Peter
33166 Changes in version 0.1.1.14-alpha - 2006-02-20
33167 o Bugfixes on 0.1.1.x:
33168 - Don't die if we ask for a stdout or stderr log (even implicitly)
33169 and we're set to RunAsDaemon -- just warn.
33170 - We still had a few bugs in the OR connection rotation code that
33171 caused directory servers to slowly aggregate connections to other
33172 fast Tor servers. This time for sure!
33173 - Make log entries on Win32 include the name of the function again.
33174 - We were treating a pair of exit policies if they were equal even
33175 if one said accept and the other said reject -- causing us to
33176 not always publish a new descriptor since we thought nothing
33178 - Retry pending server downloads as well as pending networkstatus
33179 downloads when we unexpectedly get a socks request.
33180 - We were ignoring the IS_FAST flag in the directory status,
33181 meaning we were willing to pick trivial-bandwidth nodes for "fast"
33183 - If the controller's SAVECONF command fails (e.g. due to file
33184 permissions), let the controller know that it failed.
33187 - If we're trying to be a Tor server and running Windows 95/98/ME
33188 as a server, explain that we'll likely crash.
33189 - When we're a server, a client asks for an old-style directory,
33190 and our write bucket is empty, don't give it to him. This way
33191 small servers can continue to serve the directory *sometimes*,
33192 without getting overloaded.
33193 - Compress exit policies even more -- look for duplicate lines
33195 - Clients now honor the "guard" flag in the router status when
33196 picking entry guards, rather than looking at is_fast or is_stable.
33197 - Retain unrecognized lines in $DATADIR/state file, so that we can
33198 be forward-compatible.
33199 - Generate 18.0.0.0/8 address policy format in descs when we can;
33200 warn when the mask is not reducible to a bit-prefix.
33201 - Let the user set ControlListenAddress in the torrc. This can be
33202 dangerous, but there are some cases (like a secured LAN) where it
33204 - Split ReachableAddresses into ReachableDirAddresses and
33205 ReachableORAddresses, so we can restrict Dir conns to port 80
33206 and OR conns to port 443.
33207 - Now we can target arch and OS in rpm builds (contributed by
33208 Phobos). Also make the resulting dist-rpm filename match the
33210 - New config options to help controllers: FetchServerDescriptors
33211 and FetchHidServDescriptors for whether to fetch server
33212 info and hidserv info or let the controller do it, and
33213 PublishServerDescriptor and PublishHidServDescriptors.
33214 - Also let the controller set the __AllDirActionsPrivate config
33215 option if you want all directory fetches/publishes to happen via
33216 Tor (it assumes your controller bootstraps your circuits).
33219 Changes in version 0.1.0.17 - 2006-02-17
33220 o Crash bugfixes on 0.1.0.x:
33221 - When servers with a non-zero DirPort came out of hibernation,
33222 sometimes they would trigger an assert.
33224 o Other important bugfixes:
33225 - On platforms that don't have getrlimit (like Windows), we were
33226 artificially constraining ourselves to a max of 1024
33227 connections. Now just assume that we can handle as many as 15000
33228 connections. Hopefully this won't cause other problems.
33230 o Backported features:
33231 - When we're a server, a client asks for an old-style directory,
33232 and our write bucket is empty, don't give it to him. This way
33233 small servers can continue to serve the directory *sometimes*,
33234 without getting overloaded.
33235 - Whenever you get a 503 in response to a directory fetch, try
33236 once more. This will become important once servers start sending
33237 503's whenever they feel busy.
33238 - Fetch a new directory every 120 minutes, not every 40 minutes.
33239 Now that we have hundreds of thousands of users running the old
33240 directory algorithm, it's starting to hurt a lot.
33241 - Bump up the period for forcing a hidden service descriptor upload
33242 from 20 minutes to 1 hour.
33245 Changes in version 0.1.1.13-alpha - 2006-02-09
33246 o Crashes in 0.1.1.x:
33247 - When you tried to setconf ORPort via the controller, Tor would
33248 crash. So people using TorCP to become a server were sad.
33249 - Solve (I hope) the stack-smashing bug that we were seeing on fast
33250 servers. The problem appears to be something do with OpenSSL's
33251 random number generation, or how we call it, or something. Let me
33252 know if the crashes continue.
33253 - Turn crypto hardware acceleration off by default, until we find
33254 somebody smart who can test it for us. (It appears to produce
33255 seg faults in at least some cases.)
33256 - Fix a rare assert error when we've tried all intro points for
33257 a hidden service and we try fetching the service descriptor again:
33258 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
33261 - Fix a major load balance bug: we were round-robining in 16 KB
33262 chunks, and servers with bandwidthrate of 20 KB, while downloading
33263 a 600 KB directory, would starve their other connections. Now we
33264 try to be a bit more fair.
33265 - Dir authorities and mirrors were never expiring the newest
33266 descriptor for each server, causing memory and directory bloat.
33267 - Fix memory-bloating and connection-bloating bug on servers: We
33268 were never closing any connection that had ever had a circuit on
33269 it, because we were checking conn->n_circuits == 0, yet we had a
33270 bug that let it go negative.
33271 - Make Tor work using squid as your http proxy again -- squid
33272 returns an error if you ask for a URL that's too long, and it uses
33273 a really generic error message. Plus, many people are behind a
33274 transparent squid so they don't even realize it.
33275 - On platforms that don't have getrlimit (like Windows), we were
33276 artificially constraining ourselves to a max of 1024
33277 connections. Now just assume that we can handle as many as 15000
33278 connections. Hopefully this won't cause other problems.
33279 - Add a new config option ExitPolicyRejectPrivate which defaults to
33280 1. This means all exit policies will begin with rejecting private
33281 addresses, unless the server operator explicitly turns it off.
33284 - Clients no longer download descriptors for non-running
33286 - Before we add new directory authorities, we should make it
33287 clear that only v1 authorities should receive/publish hidden
33288 service descriptors.
33291 - As soon as we've fetched some more directory info, immediately
33292 try to download more server descriptors. This way we don't have
33293 a 10 second pause during initial bootstrapping.
33294 - Remove even more loud log messages that the server operator can't
33296 - When we're running an obsolete or un-recommended version, make
33297 the log message more clear about what the problem is and what
33298 versions *are* still recommended.
33299 - Provide a more useful warn message when our onion queue gets full:
33300 the CPU is too slow or the exit policy is too liberal.
33301 - Don't warn when we receive a 503 from a dirserver/cache -- this
33302 will pave the way for them being able to refuse if they're busy.
33303 - When we fail to bind a listener, try to provide a more useful
33304 log message: e.g., "Is Tor already running?"
33305 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
33306 Goldberg can prove things about our handshake protocol more
33308 - MaxConn has been obsolete for a while now. Document the ConnLimit
33309 config option, which is a *minimum* number of file descriptors
33310 that must be available else Tor refuses to start.
33311 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
33312 if you log to syslog and want something other than LOG_DAEMON.
33313 - Make dirservers generate a separate "guard" flag to mean,
33314 "would make a good entry guard". Make clients parse it and vote
33315 on it. Not used by clients yet.
33316 - Implement --with-libevent-dir option to ./configure. Also, improve
33317 search techniques to find libevent, and use those for openssl too.
33318 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
33319 - Only start testing reachability once we've established a
33320 circuit. This will make startup on dirservers less noisy.
33321 - Don't try to upload hidden service descriptors until we have
33322 established a circuit.
33323 - Fix the controller's "attachstream 0" command to treat conn like
33324 it just connected, doing address remapping, handling .exit and
33325 .onion idioms, and so on. Now we're more uniform in making sure
33326 that the controller hears about new and closing connections.
33329 Changes in version 0.1.1.12-alpha - 2006-01-11
33330 o Bugfixes on 0.1.1.x:
33331 - The fix to close duplicate server connections was closing all
33332 Tor client connections if they didn't establish a circuit
33333 quickly enough. Oops.
33334 - Fix minor memory issue (double-free) that happened on exit.
33336 o Bugfixes on 0.1.0.x:
33337 - Tor didn't warn when it failed to open a log file.
33340 Changes in version 0.1.1.11-alpha - 2006-01-10
33341 o Crashes in 0.1.1.x:
33342 - Include all the assert/crash fixes from 0.1.0.16.
33343 - If you start Tor and then quit very quickly, there were some
33344 races that tried to free things that weren't allocated yet.
33345 - Fix a rare memory stomp if you're running hidden services.
33346 - Fix segfault when specifying DirServer in config without nickname.
33347 - Fix a seg fault when you finish connecting to a server but at
33348 that moment you dump his server descriptor.
33349 - Extendcircuit and Attachstream controller commands would
33350 assert/crash if you don't give them enough arguments.
33351 - Fix an assert error when we're out of space in the connection_list
33352 and we try to post a hidden service descriptor (reported by weasel).
33353 - If you specify a relative torrc path and you set RunAsDaemon in
33354 your torrc, then it chdir()'s to the new directory. If you HUP,
33355 it tries to load the new torrc location, fails, and exits.
33356 The fix: no longer allow a relative path to torrc using -f.
33359 - Implement "entry guards": automatically choose a handful of entry
33360 nodes and stick with them for all circuits. Only pick new guards
33361 when the ones you have are unsuitable, and if the old guards
33362 become suitable again, switch back. This will increase security
33363 dramatically against certain end-point attacks. The EntryNodes
33364 config option now provides some hints about which entry guards you
33365 want to use most; and StrictEntryNodes means to only use those.
33366 - New directory logic: download by descriptor digest, not by
33367 fingerprint. Caches try to download all listed digests from
33368 authorities; clients try to download "best" digests from caches.
33369 This avoids partitioning and isolating attacks better.
33370 - Make the "stable" router flag in network-status be the median of
33371 the uptimes of running valid servers, and make clients pay
33372 attention to the network-status flags. Thus the cutoff adapts
33373 to the stability of the network as a whole, making IRC, IM, etc
33374 connections more reliable.
33377 - Tor servers with dynamic IP addresses were needing to wait 18
33378 hours before they could start doing reachability testing using
33379 the new IP address and ports. This is because they were using
33380 the internal descriptor to learn what to test, yet they were only
33381 rebuilding the descriptor once they decided they were reachable.
33382 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
33383 to download certain server descriptors, throw them away, and then
33384 fetch them again after 30 minutes. Now mirrors throw away these
33385 server descriptors so clients can't get them.
33386 - We were leaving duplicate connections to other ORs open for a week,
33387 rather than closing them once we detect a duplicate. This only
33388 really affected authdirservers, but it affected them a lot.
33389 - Spread the authdirservers' reachability testing over the entire
33390 testing interval, so we don't try to do 500 TLS's at once every
33394 - If the network is down, and we try to connect to a conn because
33395 we have a circuit in mind, and we timeout (30 seconds) because the
33396 network never answers, we were expiring the circuit, but we weren't
33397 obsoleting the connection or telling the entry_guards functions.
33398 - Some Tor servers process billions of cells per day. These statistics
33399 need to be uint64_t's.
33400 - Check for integer overflows in more places, when adding elements
33401 to smartlists. This could possibly prevent a buffer overflow
33402 on malicious huge inputs. I don't see any, but I haven't looked
33404 - ReachableAddresses kept growing new "reject *:*" lines on every
33406 - When you "setconf log" via the controller, it should remove all
33407 logs. We were automatically adding back in a "log notice stdout".
33408 - Newly bootstrapped Tor networks couldn't establish hidden service
33409 circuits until they had nodes with high uptime. Be more tolerant.
33410 - We were marking servers down when they could not answer every piece
33411 of the directory request we sent them. This was far too harsh.
33412 - Fix the torify (tsocks) config file to not use Tor for localhost
33414 - Directory authorities now go to the proper authority when asking for
33415 a networkstatus, even when they want a compressed one.
33416 - Fix a harmless bug that was causing Tor servers to log
33417 "Got an end because of misc error, but we're not an AP. Closing."
33418 - Authorities were treating their own descriptor changes as cosmetic,
33419 meaning the descriptor available in the network-status and the
33420 descriptor that clients downloaded were different.
33421 - The OS X installer was adding a symlink for tor_resolve but
33422 the binary was called tor-resolve (reported by Thomas Hardly).
33423 - Workaround a problem with some http proxies where they refuse GET
33424 requests that specify "Content-Length: 0" (reported by Adrian).
33425 - Fix wrong log message when you add a "HiddenServiceNodes" config
33426 line without any HiddenServiceDir line (reported by Chris Thomas).
33429 - Write the TorVersion into the state file so we have a prayer of
33430 keeping forward and backward compatibility.
33431 - Revive the FascistFirewall config option rather than eliminating it:
33432 now it's a synonym for ReachableAddresses *:80,*:443.
33433 - Clients choose directory servers from the network status lists,
33434 not from their internal list of router descriptors. Now they can
33435 go to caches directly rather than needing to go to authorities
33437 - Directory authorities ignore router descriptors that have only
33438 cosmetic differences: do this for 0.1.0.x servers now too.
33439 - Add a new flag to network-status indicating whether the server
33440 can answer v2 directory requests too.
33441 - Authdirs now stop whining so loudly about bad descriptors that
33442 they fetch from other dirservers. So when there's a log complaint,
33443 it's for sure from a freshly uploaded descriptor.
33444 - Reduce memory requirements in our structs by changing the order
33446 - There used to be two ways to specify your listening ports in a
33447 server descriptor: on the "router" line and with a separate "ports"
33448 line. Remove support for the "ports" line.
33449 - New config option "AuthDirRejectUnlisted" for auth dirservers as
33450 a panic button: if we get flooded with unusable servers we can
33451 revert to only listing servers in the approved-routers file.
33452 - Auth dir servers can now mark a fingerprint as "!reject" or
33453 "!invalid" in the approved-routers file (as its nickname), to
33454 refuse descriptors outright or include them but marked as invalid.
33455 - Servers store bandwidth history across restarts/crashes.
33456 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
33457 get a better idea of why their circuits failed. Not used yet.
33458 - Directory mirrors now cache up to 16 unrecognized network-status
33459 docs. Now we can add new authdirservers and they'll be cached too.
33460 - When picking a random directory, prefer non-authorities if any
33462 - New controller option "getinfo desc/all-recent" to fetch the
33463 latest server descriptor for every router that Tor knows about.
33466 Changes in version 0.1.0.16 - 2006-01-02
33467 o Crash bugfixes on 0.1.0.x:
33468 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
33469 corrupting the heap, losing FDs, or crashing when we need to resize
33470 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
33471 - It turns out sparc64 platforms crash on unaligned memory access
33472 too -- so detect and avoid this.
33473 - Handle truncated compressed data correctly (by detecting it and
33475 - Fix possible-but-unlikely free(NULL) in control.c.
33476 - When we were closing connections, there was a rare case that
33477 stomped on memory, triggering seg faults and asserts.
33478 - Avoid potential infinite recursion when building a descriptor. (We
33479 don't know that it ever happened, but better to fix it anyway.)
33480 - We were neglecting to unlink marked circuits from soon-to-close OR
33481 connections, which caused some rare scribbling on freed memory.
33482 - Fix a memory stomping race bug when closing the joining point of two
33483 rendezvous circuits.
33484 - Fix an assert in time parsing found by Steven Murdoch.
33486 o Other bugfixes on 0.1.0.x:
33487 - When we're doing reachability testing, provide more useful log
33488 messages so the operator knows what to expect.
33489 - Do not check whether DirPort is reachable when we are suppressing
33490 advertising it because of hibernation.
33491 - When building with -static or on Solaris, we sometimes needed -ldl.
33492 - When we're deciding whether a stream has enough circuits around
33493 that can handle it, count the freshly dirty ones and not the ones
33494 that are so dirty they won't be able to handle it.
33495 - When we're expiring old circuits, we had a logic error that caused
33496 us to close new rendezvous circuits rather than old ones.
33497 - Give a more helpful log message when you try to change ORPort via
33498 the controller: you should upgrade Tor if you want that to work.
33499 - We were failing to parse Tor versions that start with "Tor ".
33500 - Tolerate faulty streams better: when a stream fails for reason
33501 exitpolicy, stop assuming that the router is lying about his exit
33502 policy. When a stream fails for reason misc, allow it to retry just
33503 as if it was resolvefailed. When a stream has failed three times,
33504 reset its failure count so we can try again and get all three tries.
33507 Changes in version 0.1.1.10-alpha - 2005-12-11
33508 o Correctness bugfixes on 0.1.0.x:
33509 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
33510 corrupting the heap, losing FDs, or crashing when we need to resize
33511 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
33512 - Stop doing the complex voodoo overkill checking for insecure
33513 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
33514 - When we were closing connections, there was a rare case that
33515 stomped on memory, triggering seg faults and asserts.
33516 - We were neglecting to unlink marked circuits from soon-to-close OR
33517 connections, which caused some rare scribbling on freed memory.
33518 - When we're deciding whether a stream has enough circuits around
33519 that can handle it, count the freshly dirty ones and not the ones
33520 that are so dirty they won't be able to handle it.
33521 - Recover better from TCP connections to Tor servers that are
33522 broken but don't tell you (it happens!); and rotate TLS
33523 connections once a week.
33524 - When we're expiring old circuits, we had a logic error that caused
33525 us to close new rendezvous circuits rather than old ones.
33526 - Fix a scary-looking but apparently harmless bug where circuits
33527 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
33528 servers, and never switch to state CIRCUIT_STATE_OPEN.
33529 - When building with -static or on Solaris, we sometimes needed to
33531 - Give a useful message when people run Tor as the wrong user,
33532 rather than telling them to start chowning random directories.
33533 - We were failing to inform the controller about new .onion streams.
33535 o Security bugfixes on 0.1.0.x:
33536 - Refuse server descriptors if the fingerprint line doesn't match
33537 the included identity key. Tor doesn't care, but other apps (and
33538 humans) might actually be trusting the fingerprint line.
33539 - We used to kill the circuit when we receive a relay command we
33540 don't recognize. Now we just drop it.
33541 - Start obeying our firewall options more rigorously:
33542 . If we can't get to a dirserver directly, try going via Tor.
33543 . Don't ever try to connect (as a client) to a place our
33544 firewall options forbid.
33545 . If we specify a proxy and also firewall options, obey the
33546 firewall options even when we're using the proxy: some proxies
33547 can only proxy to certain destinations.
33548 - Fix a bug found by Lasse Overlier: when we were making internal
33549 circuits (intended to be cannibalized later for rendezvous and
33550 introduction circuits), we were picking them so that they had
33551 useful exit nodes. There was no need for this, and it actually
33552 aids some statistical attacks.
33553 - Start treating internal circuits and exit circuits separately.
33554 It's important to keep them separate because internal circuits
33555 have their last hops picked like middle hops, rather than like
33556 exit hops. So exiting on them will break the user's expectations.
33558 o Bugfixes on 0.1.1.x:
33559 - Take out the mis-feature where we tried to detect IP address
33560 flapping for people with DynDNS, and chose not to upload a new
33561 server descriptor sometimes.
33562 - Try to be compatible with OpenSSL 0.9.6 again.
33563 - Log fix: when the controller is logging about .onion addresses,
33564 sometimes it didn't include the ".onion" part of the address.
33565 - Don't try to modify options->DirServers internally -- if the
33566 user didn't specify any, just add the default ones directly to
33567 the trusted dirserver list. This fixes a bug where people running
33568 controllers would use SETCONF on some totally unrelated config
33569 option, and Tor would start yelling at them about changing their
33571 - Let the controller's redirectstream command specify a port, in
33572 case the controller wants to change that too.
33573 - When we requested a pile of server descriptors, we sometimes
33574 accidentally launched a duplicate request for the first one.
33575 - Bugfix for trackhostexits: write down the fingerprint of the
33576 chosen exit, not its nickname, because the chosen exit might not
33578 - When parsing foo.exit, if foo is unknown, and we are leaving
33579 circuits unattached, set the chosen_exit field and leave the
33580 address empty. This matters because controllers got confused
33582 - Directory authorities no longer try to download server
33583 descriptors that they know they will reject.
33585 o Features and updates:
33586 - Replace balanced trees with hash tables: this should make stuff
33587 significantly faster.
33588 - Resume using the AES counter-mode implementation that we ship,
33589 rather than OpenSSL's. Ours is significantly faster.
33590 - Many other CPU and memory improvements.
33591 - Add a new config option FastFirstHopPK (on by default) so clients
33592 do a trivial crypto handshake for their first hop, since TLS has
33593 already taken care of confidentiality and authentication.
33594 - Add a new config option TestSocks so people can see if their
33595 applications are using socks4, socks4a, socks5-with-ip, or
33596 socks5-with-hostname. This way they don't have to keep mucking
33597 with tcpdump and wondering if something got cached somewhere.
33598 - Warn when listening on a public address for socks. I suspect a
33599 lot of people are setting themselves up as open socks proxies,
33600 and they have no idea that jerks on the Internet are using them,
33601 since they simply proxy the traffic into the Tor network.
33602 - Add "private:*" as an alias in configuration for policies. Now
33603 you can simplify your exit policy rather than needing to list
33604 every single internal or nonroutable network space.
33605 - Add a new controller event type that allows controllers to get
33606 all server descriptors that were uploaded to a router in its role
33607 as authoritative dirserver.
33608 - Start shipping socks-extensions.txt, tor-doc-unix.html,
33609 tor-doc-server.html, and stylesheet.css in the tarball.
33610 - Stop shipping tor-doc.html in the tarball.
33613 Changes in version 0.1.1.9-alpha - 2005-11-15
33614 o Usability improvements:
33615 - Start calling it FooListenAddress rather than FooBindAddress,
33616 since few of our users know what it means to bind an address
33618 - Reduce clutter in server logs. We're going to try to make
33619 them actually usable now. New config option ProtocolWarnings that
33620 lets you hear about how _other Tors_ are breaking the protocol. Off
33622 - Divide log messages into logging domains. Once we put some sort
33623 of interface on this, it will let people looking at more verbose
33624 log levels specify the topics they want to hear more about.
33625 - Make directory servers return better http 404 error messages
33626 instead of a generic "Servers unavailable".
33627 - Check for even more Windows version flags when writing the platform
33628 string in server descriptors, and note any we don't recognize.
33629 - Clean up more of the OpenSSL memory when exiting, so we can detect
33630 memory leaks better.
33631 - Make directory authorities be non-versioning, non-naming by
33632 default. Now we can add new directory servers without requiring
33633 their operators to pay close attention.
33634 - When logging via syslog, include the pid whenever we provide
33635 a log entry. Suggested by Todd Fries.
33637 o Performance improvements:
33638 - Directory servers now silently throw away new descriptors that
33639 haven't changed much if the timestamps are similar. We do this to
33640 tolerate older Tor servers that upload a new descriptor every 15
33641 minutes. (It seemed like a good idea at the time.)
33642 - Inline bottleneck smartlist functions; use fast versions by default.
33643 - Add a "Map from digest to void*" abstraction digestmap_t so we
33644 can do less hex encoding/decoding. Use it in router_get_by_digest()
33645 to resolve a performance bottleneck.
33646 - Allow tor_gzip_uncompress to extract as much as possible from
33647 truncated compressed data. Try to extract as many
33648 descriptors as possible from truncated http responses (when
33649 DIR_PURPOSE_FETCH_ROUTERDESC).
33650 - Make circ->onionskin a pointer, not a static array. moria2 was using
33651 125000 circuit_t's after it had been up for a few weeks, which
33652 translates to 20+ megs of wasted space.
33653 - The private half of our EDH handshake keys are now chosen out
33654 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
33656 o Security improvements:
33657 - Start making directory caches retain old routerinfos, so soon
33658 clients can start asking by digest of descriptor rather than by
33659 fingerprint of server.
33660 - Add half our entropy from RAND_poll in OpenSSL. This knows how
33661 to use egd (if present), openbsd weirdness (if present), vms/os2
33662 weirdness (if we ever port there), and more in the future.
33664 o Bugfixes on 0.1.0.x:
33665 - Do round-robin writes of at most 16 kB per write. This might be
33666 more fair on loaded Tor servers, and it might resolve our Windows
33667 crash bug. It might also slow things down.
33668 - Our TLS handshakes were generating a single public/private
33669 keypair for the TLS context, rather than making a new one for
33670 each new connections. Oops. (But we were still rotating them
33671 periodically, so it's not so bad.)
33672 - When we were cannibalizing a circuit with a particular exit
33673 node in mind, we weren't checking to see if that exit node was
33674 already present earlier in the circuit. Oops.
33675 - When a Tor server's IP changes (e.g. from a dyndns address),
33676 upload a new descriptor so clients will learn too.
33677 - Really busy servers were keeping enough circuits open on stable
33678 connections that they were wrapping around the circuit_id
33679 space. (It's only two bytes.) This exposed a bug where we would
33680 feel free to reuse a circuit_id even if it still exists but has
33681 been marked for close. Try to fix this bug. Some bug remains.
33682 - If we would close a stream early (e.g. it asks for a .exit that
33683 we know would refuse it) but the LeaveStreamsUnattached config
33684 option is set by the controller, then don't close it.
33686 o Bugfixes on 0.1.1.8-alpha:
33687 - Fix a big pile of memory leaks, some of them serious.
33688 - Do not try to download a routerdesc if we would immediately reject
33690 - Resume inserting a newline between all router descriptors when
33691 generating (old style) signed directories, since our spec says
33693 - When providing content-type application/octet-stream for
33694 server descriptors using .z, we were leaving out the
33695 content-encoding header. Oops. (Everything tolerated this just
33696 fine, but that doesn't mean we need to be part of the problem.)
33697 - Fix a potential seg fault in getconf and getinfo using version 1
33698 of the controller protocol.
33699 - Avoid crash: do not check whether DirPort is reachable when we
33700 are suppressing it because of hibernation.
33701 - Make --hash-password not crash on exit.
33704 Changes in version 0.1.1.8-alpha - 2005-10-07
33705 o New features (major):
33706 - Clients don't download or use the directory anymore. Now they
33707 download and use network-statuses from the trusted dirservers,
33708 and fetch individual server descriptors as needed from mirrors.
33709 See dir-spec.txt for all the gory details.
33710 - Be more conservative about whether to advertise our DirPort.
33711 The main change is to not advertise if we're running at capacity
33712 and either a) we could hibernate or b) our capacity is low and
33713 we're using a default DirPort.
33714 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
33716 o New features (minor):
33717 - Try to be smart about when to retry network-status and
33718 server-descriptor fetches. Still needs some tuning.
33719 - Stop parsing, storing, or using running-routers output (but
33720 mirrors still cache and serve it).
33721 - Consider a threshold of versioning dirservers (dirservers who have
33722 an opinion about which Tor versions are still recommended) before
33723 deciding whether to warn the user that he's obsolete.
33724 - Dirservers can now reject/invalidate by key and IP, with the
33725 config options "AuthDirInvalid" and "AuthDirReject". This is
33726 useful since currently we automatically list servers as running
33727 and usable even if we know they're jerks.
33728 - Provide dire warnings to any users who set DirServer; move it out
33729 of torrc.sample and into torrc.complete.
33730 - Add MyFamily to torrc.sample in the server section.
33731 - Add nicknames to the DirServer line, so we can refer to them
33732 without requiring all our users to memorize their IP addresses.
33733 - When we get an EOF or a timeout on a directory connection, note
33734 how many bytes of serverdesc we are dropping. This will help
33735 us determine whether it is smart to parse incomplete serverdesc
33737 - Add a new function to "change pseudonyms" -- that is, to stop
33738 using any currently-dirty circuits for new streams, so we don't
33739 link new actions to old actions. Currently it's only called on
33740 HUP (or SIGNAL RELOAD).
33741 - On sighup, if UseHelperNodes changed to 1, use new circuits.
33742 - Start using RAND_bytes rather than RAND_pseudo_bytes from
33743 OpenSSL. Also, reseed our entropy every hour, not just at
33744 startup. And entropy in 512-bit chunks, not 160-bit chunks.
33746 o Fixes on 0.1.1.7-alpha:
33747 - Nobody ever implemented EVENT_ADDRMAP for control protocol
33748 version 0, so don't let version 0 controllers ask for it.
33749 - If you requested something with too many newlines via the
33750 v1 controller protocol, you could crash tor.
33751 - Fix a number of memory leaks, including some pretty serious ones.
33752 - Re-enable DirPort testing again, so Tor servers will be willing
33753 to advertise their DirPort if it's reachable.
33754 - On TLS handshake, only check the other router's nickname against
33755 its expected nickname if is_named is set.
33757 o Fixes forward-ported from 0.1.0.15:
33758 - Don't crash when we don't have any spare file descriptors and we
33759 try to spawn a dns or cpu worker.
33760 - Make the numbers in read-history and write-history into uint64s,
33761 so they don't overflow and publish negatives in the descriptor.
33763 o Fixes on 0.1.0.x:
33764 - For the OS X package's modified privoxy config file, comment
33765 out the "logfile" line so we don't log everything passed
33767 - We were whining about using socks4 or socks5-with-local-lookup
33768 even when it's an IP in the "virtual" range we designed exactly
33770 - We were leaking some memory every time the client changes IPs.
33771 - Never call free() on tor_malloc()d memory. This will help us
33772 use dmalloc to detect memory leaks.
33773 - Check for named servers when looking them up by nickname;
33774 warn when we'recalling a non-named server by its nickname;
33775 don't warn twice about the same name.
33776 - Try to list MyFamily elements by key, not by nickname, and warn
33777 if we've not heard of the server.
33778 - Make windows platform detection (uname equivalent) smarter.
33779 - It turns out sparc64 doesn't like unaligned access either.
33782 Changes in version 0.1.0.15 - 2005-09-23
33783 o Bugfixes on 0.1.0.x:
33784 - Reject ports 465 and 587 (spam targets) in default exit policy.
33785 - Don't crash when we don't have any spare file descriptors and we
33786 try to spawn a dns or cpu worker.
33787 - Get rid of IgnoreVersion undocumented config option, and make us
33788 only warn, never exit, when we're running an obsolete version.
33789 - Don't try to print a null string when your server finds itself to
33790 be unreachable and the Address config option is empty.
33791 - Make the numbers in read-history and write-history into uint64s,
33792 so they don't overflow and publish negatives in the descriptor.
33793 - Fix a minor memory leak in smartlist_string_remove().
33794 - We were only allowing ourselves to upload a server descriptor at
33795 most every 20 minutes, even if it changed earlier than that.
33796 - Clean up log entries that pointed to old URLs.
33799 Changes in version 0.1.1.7-alpha - 2005-09-14
33800 o Fixes on 0.1.1.6-alpha:
33801 - Exit servers were crashing when people asked them to make a
33802 connection to an address not in their exit policy.
33803 - Looking up a non-existent stream for a v1 control connection would
33805 - Fix a seg fault if we ask a dirserver for a descriptor by
33806 fingerprint but he doesn't know about him.
33807 - SETCONF was appending items to linelists, not clearing them.
33808 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
33809 out and refuse the setconf if it would fail.
33810 - Downgrade the dirserver log messages when whining about
33814 - Add Peter Palfrader's check-tor script to tor/contrib/
33815 It lets you easily check whether a given server (referenced by
33816 nickname) is reachable by you.
33817 - Numerous changes to move towards client-side v2 directories. Not
33820 o Fixes on 0.1.0.x:
33821 - If the user gave tor an odd number of command-line arguments,
33822 we were silently ignoring the last one. Now we complain and fail.
33823 [This wins the oldest-bug prize -- this bug has been present since
33824 November 2002, as released in Tor 0.0.0.]
33825 - Do not use unaligned memory access on alpha, mips, or mipsel.
33826 It *works*, but is very slow, so we treat them as if it doesn't.
33827 - Retry directory requests if we fail to get an answer we like
33828 from a given dirserver (we were retrying before, but only if
33829 we fail to connect).
33830 - When writing the RecommendedVersions line, sort them first.
33831 - When the client asked for a rendezvous port that the hidden
33832 service didn't want to provide, we were sending an IP address
33833 back along with the end cell. Fortunately, it was zero. But stop
33835 - Correct "your server is reachable" log entries to indicate that
33836 it was self-testing that told us so.
33839 Changes in version 0.1.1.6-alpha - 2005-09-09
33840 o Fixes on 0.1.1.5-alpha:
33841 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
33842 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
33843 - Fix bug with tor_memmem finding a match at the end of the string.
33844 - Make unit tests run without segfaulting.
33845 - Resolve some solaris x86 compile warnings.
33846 - Handle duplicate lines in approved-routers files without warning.
33847 - Fix bug where as soon as a server refused any requests due to his
33848 exit policy (e.g. when we ask for localhost and he tells us that's
33849 127.0.0.1 and he won't do it), we decided he wasn't obeying his
33850 exit policy using him for any exits.
33851 - Only do openssl hardware accelerator stuff if openssl version is
33854 o New controller features/fixes:
33855 - Add a "RESETCONF" command so you can set config options like
33856 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
33857 a config option in the torrc with no value, then it clears it
33858 entirely (rather than setting it to its default).
33859 - Add a "GETINFO config-file" to tell us where torrc is.
33860 - Avoid sending blank lines when GETINFO replies should be empty.
33861 - Add a QUIT command for the controller (for using it manually).
33862 - Fix a bug in SAVECONF that was adding default dirservers and
33863 other redundant entries to the torrc file.
33865 o Start on the new directory design:
33866 - Generate, publish, cache, serve new network-status format.
33867 - Publish individual descriptors (by fingerprint, by "all", and by
33869 - Publish client and server recommended versions separately.
33870 - Allow tor_gzip_uncompress() to handle multiple concatenated
33871 compressed strings. Serve compressed groups of router
33872 descriptors. The compression logic here could be more
33874 - Distinguish v1 authorities (all currently trusted directories)
33875 from v2 authorities (all trusted directories).
33876 - Change DirServers config line to note which dirs are v1 authorities.
33877 - Add configuration option "V1AuthoritativeDirectory 1" which
33878 moria1, moria2, and tor26 should set.
33879 - Remove option when getting directory cache to see whether they
33880 support running-routers; they all do now. Replace it with one
33881 to see whether caches support v2 stuff.
33884 - Dirservers now do their own external reachability testing of each
33885 Tor server, and only list them as running if they've been found to
33886 be reachable. We also send back warnings to the server's logs if
33887 it uploads a descriptor that we already believe is unreachable.
33888 - Implement exit enclaves: if we know an IP address for the
33889 destination, and there's a running Tor server at that address
33890 which allows exit to the destination, then extend the circuit to
33891 that exit first. This provides end-to-end encryption and end-to-end
33892 authentication. Also, if the user wants a .exit address or enclave,
33893 use 4 hops rather than 3, and cannibalize a general circ for it
33895 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
33896 controller. Also, rotate dns and cpu workers if the controller
33897 changes options that will affect them; and initialize the dns
33898 worker cache tree whether or not we start out as a server.
33899 - Only upload a new server descriptor when options change, 18
33900 hours have passed, uptime is reset, or bandwidth changes a lot.
33901 - Check [X-]Forwarded-For headers in HTTP requests when generating
33902 log messages. This lets people run dirservers (and caches) behind
33903 Apache but still know which IP addresses are causing warnings.
33905 o Config option changes:
33906 - Replace (Fascist)Firewall* config options with a new
33907 ReachableAddresses option that understands address policies.
33908 For example, "ReachableAddresses *:80,*:443"
33909 - Get rid of IgnoreVersion undocumented config option, and make us
33910 only warn, never exit, when we're running an obsolete version.
33911 - Make MonthlyAccountingStart config option truly obsolete now.
33913 o Fixes on 0.1.0.x:
33914 - Reject ports 465 and 587 in the default exit policy, since
33915 people have started using them for spam too.
33916 - It turns out we couldn't bootstrap a network since we added
33917 reachability detection in 0.1.0.1-rc. Good thing the Tor network
33918 has never gone down. Add an AssumeReachable config option to let
33919 servers and dirservers bootstrap. When we're trying to build a
33920 high-uptime or high-bandwidth circuit but there aren't enough
33921 suitable servers, try being less picky rather than simply failing.
33922 - Our logic to decide if the OR we connected to was the right guy
33923 was brittle and maybe open to a mitm for unverified routers.
33924 - We weren't cannibalizing circuits correctly for
33925 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
33926 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
33927 build those from scratch. This should make hidden services faster.
33928 - Predict required circuits better, with an eye toward making hidden
33929 services faster on the service end.
33930 - Retry streams if the exit node sends back a 'misc' failure. This
33931 should result in fewer random failures. Also, after failing
33932 from resolve failed or misc, reset the num failures, so we give
33933 it a fair shake next time we try.
33934 - Clean up the rendezvous warn log msgs, and downgrade some to info.
33935 - Reduce severity on logs about dns worker spawning and culling.
33936 - When we're shutting down and we do something like try to post a
33937 server descriptor or rendezvous descriptor, don't complain that
33938 we seem to be unreachable. Of course we are, we're shutting down.
33939 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
33940 We don't use them yet, but maybe one day our DNS resolver will be
33941 able to discover them.
33942 - Make ContactInfo mandatory for authoritative directory servers.
33943 - Require server descriptors to list IPv4 addresses -- hostnames
33944 are no longer allowed. This also fixes some potential security
33945 problems with people providing hostnames as their address and then
33946 preferentially resolving them to partition users.
33947 - Change log line for unreachability to explicitly suggest /etc/hosts
33948 as the culprit. Also make it clearer what IP address and ports we're
33949 testing for reachability.
33950 - Put quotes around user-supplied strings when logging so users are
33951 more likely to realize if they add bad characters (like quotes)
33953 - Let auth dir servers start without specifying an Address config
33955 - Make unit tests (and other invocations that aren't the real Tor)
33956 run without launching listeners, creating subdirectories, and so on.
33959 Changes in version 0.1.1.5-alpha - 2005-08-08
33960 o Bugfixes included in 0.1.0.14.
33962 o Bugfixes on 0.1.0.x:
33963 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
33964 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
33965 it would silently using ignore the 6668.
33968 Changes in version 0.1.0.14 - 2005-08-08
33969 o Bugfixes on 0.1.0.x:
33970 - Fix the other half of the bug with crypto handshakes
33972 - Fix an assert trigger if you send a 'signal term' via the
33973 controller when it's listening for 'event info' messages.
33976 Changes in version 0.1.1.4-alpha - 2005-08-04
33977 o Bugfixes included in 0.1.0.13.
33980 - Improve tor_gettimeofday() granularity on windows.
33981 - Make clients regenerate their keys when their IP address changes.
33982 - Implement some more GETINFO goodness: expose helper nodes, config
33983 options, getinfo keys.
33986 Changes in version 0.1.0.13 - 2005-08-04
33987 o Bugfixes on 0.1.0.x:
33988 - Fix a critical bug in the security of our crypto handshakes.
33989 - Fix a size_t underflow in smartlist_join_strings2() that made
33990 it do bad things when you hand it an empty smartlist.
33991 - Fix Windows installer to ship Tor license (thanks to Aphex for
33992 pointing out this oversight) and put a link to the doc directory
33994 - Explicitly set no-unaligned-access for sparc: it turns out the
33995 new gcc's let you compile broken code, but that doesn't make it
33999 Changes in version 0.1.1.3-alpha - 2005-07-23
34000 o Bugfixes on 0.1.1.2-alpha:
34001 - Fix a bug in handling the controller's "post descriptor"
34003 - Fix several bugs in handling the controller's "extend circuit"
34005 - Fix a bug in handling the controller's "stream status" event.
34006 - Fix an assert failure if we have a controller listening for
34007 circuit events and we go offline.
34008 - Re-allow hidden service descriptors to publish 0 intro points.
34009 - Fix a crash when generating your hidden service descriptor if
34010 you don't have enough intro points already.
34012 o New features on 0.1.1.2-alpha:
34013 - New controller function "getinfo accounting", to ask how
34014 many bytes we've used in this time period.
34015 - Experimental support for helper nodes: a lot of the risk from
34016 a small static adversary comes because users pick new random
34017 nodes every time they rebuild a circuit. Now users will try to
34018 stick to the same small set of entry nodes if they can. Not
34019 enabled by default yet.
34021 o Bugfixes on 0.1.0.12:
34022 - If you're an auth dir server, always publish your dirport,
34023 even if you haven't yet found yourself to be reachable.
34024 - Fix a size_t underflow in smartlist_join_strings2() that made
34025 it do bad things when you hand it an empty smartlist.
34028 Changes in version 0.1.0.12 - 2005-07-18
34029 o New directory servers:
34030 - tor26 has changed IP address.
34032 o Bugfixes on 0.1.0.x:
34033 - Fix a possible double-free in tor_gzip_uncompress().
34034 - When --disable-threads is set, do not search for or link against
34035 pthreads libraries.
34036 - Don't trigger an assert if an authoritative directory server
34037 claims its dirport is 0.
34038 - Fix bug with removing Tor as an NT service: some people were
34039 getting "The service did not return an error." Thanks to Matt
34043 Changes in version 0.1.1.2-alpha - 2005-07-15
34044 o New directory servers:
34045 - tor26 has changed IP address.
34047 o Bugfixes on 0.1.0.x, crashes/leaks:
34048 - Port the servers-not-obeying-their-exit-policies fix from
34050 - Fix an fd leak in start_daemon().
34051 - On Windows, you can't always reopen a port right after you've
34052 closed it. So change retry_listeners() to only close and re-open
34053 ports that have changed.
34054 - Fix a possible double-free in tor_gzip_uncompress().
34056 o Bugfixes on 0.1.0.x, usability:
34057 - When tor_socketpair() fails in Windows, give a reasonable
34058 Windows-style errno back.
34059 - Let people type "tor --install" as well as "tor -install" when
34061 want to make it an NT service.
34062 - NT service patch from Matt Edman to improve error messages.
34063 - When the controller asks for a config option with an abbreviated
34064 name, give the full name in our response.
34065 - Correct the man page entry on TrackHostExitsExpire.
34066 - Looks like we were never delivering deflated (i.e. compressed)
34067 running-routers lists, even when asked. Oops.
34068 - When --disable-threads is set, do not search for or link against
34069 pthreads libraries.
34071 o Bugfixes on 0.1.1.x:
34072 - Fix a seg fault with autodetecting which controller version is
34076 - New hidden service descriptor format: put a version in it, and
34077 let people specify introduction/rendezvous points that aren't
34078 in "the directory" (which is subjective anyway).
34079 - Allow the DEBUG controller event to work again. Mark certain log
34080 entries as "don't tell this to controllers", so we avoid cycles.
34083 Changes in version 0.1.0.11 - 2005-06-30
34084 o Bugfixes on 0.1.0.x:
34085 - Fix major security bug: servers were disregarding their
34086 exit policies if clients behaved unexpectedly.
34087 - Make OS X init script check for missing argument, so we don't
34088 confuse users who invoke it incorrectly.
34089 - Fix a seg fault in "tor --hash-password foo".
34090 - The MAPADDRESS control command was broken.
34093 Changes in version 0.1.1.1-alpha - 2005-06-29
34095 - Make OS X init script check for missing argument, so we don't
34096 confuse users who invoke it incorrectly.
34097 - Fix a seg fault in "tor --hash-password foo".
34098 - Fix a possible way to DoS dirservers.
34099 - When we complain that your exit policy implicitly allows local or
34100 private address spaces, name them explicitly so operators can
34102 - Make the log message less scary when all the dirservers are
34103 temporarily unreachable.
34104 - We were printing the number of idle dns workers incorrectly when
34108 - Revised controller protocol (version 1) that uses ascii rather
34109 than binary. Add supporting libraries in python and java so you
34110 can use the controller from your applications without caring how
34111 our protocol works.
34112 - Spiffy new support for crypto hardware accelerators. Can somebody
34116 Changes in version 0.0.9.10 - 2005-06-16
34117 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
34118 - Refuse relay cells that claim to have a length larger than the
34119 maximum allowed. This prevents a potential attack that could read
34120 arbitrary memory (e.g. keys) from an exit server's process
34124 Changes in version 0.1.0.10 - 2005-06-14
34125 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
34126 libevent before 1.1a.
34129 Changes in version 0.1.0.9-rc - 2005-06-09
34131 - Reset buf->highwater every time buf_shrink() is called, not just on
34132 a successful shrink. This was causing significant memory bloat.
34133 - Fix buffer overflow when checking hashed passwords.
34134 - Security fix: if seeding the RNG on Win32 fails, quit.
34135 - Allow seeding the RNG on Win32 even when you're not running as
34137 - Disable threading on Solaris too. Something is wonky with it,
34138 cpuworkers, and reentrant libs.
34139 - Reenable the part of the code that tries to flush as soon as an
34140 OR outbuf has a full TLS record available. Perhaps this will make
34141 OR outbufs not grow as huge except in rare cases, thus saving lots
34142 of CPU time plus memory.
34143 - Reject malformed .onion addresses rather then passing them on as
34144 normal web requests.
34145 - Adapt patch from Adam Langley: fix possible memory leak in
34146 tor_lookup_hostname().
34147 - Initialize libevent later in the startup process, so the logs are
34148 already established by the time we start logging libevent warns.
34149 - Use correct errno on win32 if libevent fails.
34150 - Check and warn about known-bad/slow libevent versions.
34151 - Pay more attention to the ClientOnly config option.
34152 - Have torctl.in/tor.sh.in check for location of su binary (needed
34154 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
34155 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
34156 HttpProxyAuthenticator
34157 - Stop warning about sigpipes in the logs. We're going to
34158 pretend that getting these occasionally is normal and fine.
34159 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
34161 installer screens; and don't put stuff into StartupItems unless
34162 the user asks you to.
34163 - Require servers that use the default dirservers to have public IP
34164 addresses. We have too many servers that are configured with private
34165 IPs and their admins never notice the log entries complaining that
34166 their descriptors are being rejected.
34167 - Add OSX uninstall instructions. An actual uninstall script will
34171 Changes in version 0.1.0.8-rc - 2005-05-23
34173 - It turns out that kqueue on OS X 10.3.9 was causing kernel
34174 panics. Disable kqueue on all OS X Tors.
34175 - Fix RPM: remove duplicate line accidentally added to the rpm
34177 - Disable threads on openbsd too, since its gethostaddr is not
34179 - Tolerate libevent 0.8 since it still works, even though it's
34181 - Enable building on Red Hat 9.0 again.
34182 - Allow the middle hop of the testing circuit to be running any
34183 version, now that most of them have the bugfix to let them connect
34184 to unknown servers. This will allow reachability testing to work
34185 even when 0.0.9.7-0.0.9.9 become obsolete.
34186 - Handle relay cells with rh.length too large. This prevents
34187 a potential attack that could read arbitrary memory (maybe even
34188 keys) from the exit server's process.
34189 - We screwed up the dirport reachability testing when we don't yet
34190 have a cached version of the directory. Hopefully now fixed.
34191 - Clean up router_load_single_router() (used by the controller),
34192 so it doesn't seg fault on error.
34193 - Fix a minor memory leak when somebody establishes an introduction
34194 point at your Tor server.
34195 - If a socks connection ends because read fails, don't warn that
34196 you're not sending a socks reply back.
34199 - Add HttpProxyAuthenticator config option too, that works like
34200 the HttpsProxyAuthenticator config option.
34201 - Encode hashed controller passwords in hex instead of base64,
34202 to make it easier to write controllers.
34205 Changes in version 0.1.0.7-rc - 2005-05-17
34207 - Fix a bug in the OS X package installer that prevented it from
34208 installing on Tiger.
34209 - Fix a script bug in the OS X package installer that made it
34210 complain during installation.
34211 - Find libevent even if it's hiding in /usr/local/ and your
34212 CFLAGS and LDFLAGS don't tell you to look there.
34213 - Be able to link with libevent as a shared library (the default
34214 after 1.0d), even if it's hiding in /usr/local/lib and even
34215 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
34216 assuming you're running gcc. Otherwise fail and give a useful
34218 - Fix a bug in the RPM packager: set home directory for _tor to
34219 something more reasonable when first installing.
34220 - Free a minor amount of memory that is still reachable on exit.
34223 Changes in version 0.1.0.6-rc - 2005-05-14
34225 - Implement --disable-threads configure option. Disable threads on
34226 netbsd by default, because it appears to have no reentrant resolver
34228 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
34229 release (1.1) detects and disables kqueue if it's broken.
34230 - Append default exit policy before checking for implicit internal
34231 addresses. Now we don't log a bunch of complaints on startup
34232 when using the default exit policy.
34233 - Some people were putting "Address " in their torrc, and they had
34234 a buggy resolver that resolved " " to 0.0.0.0. Oops.
34235 - If DataDir is ~/.tor, and that expands to /.tor, then default to
34236 LOCALSTATEDIR/tor instead.
34237 - Fix fragmented-message bug in TorControl.py.
34238 - Resolve a minor bug which would prevent unreachable dirports
34239 from getting suppressed in the published descriptor.
34240 - When the controller gave us a new descriptor, we weren't resolving
34241 it immediately, so Tor would think its address was 0.0.0.0 until
34242 we fetched a new directory.
34243 - Fix an uppercase/lowercase case error in suppressing a bogus
34244 libevent warning on some Linuxes.
34247 - Begin scrubbing sensitive strings from logs by default. Turn off
34248 the config option SafeLogging if you need to do debugging.
34249 - Switch to a new buffer management algorithm, which tries to avoid
34250 reallocing and copying quite as much. In first tests it looks like
34251 it uses *more* memory on average, but less cpu.
34252 - First cut at support for "create-fast" cells. Clients can use
34253 these when extending to their first hop, since the TLS already
34254 provides forward secrecy and authentication. Not enabled on
34256 - When dirservers refuse a router descriptor, we now log its
34257 contactinfo, platform, and the poster's IP address.
34258 - Call tor_free_all instead of connections_free_all after forking, to
34259 save memory on systems that need to fork.
34260 - Whine at you if you're a server and you don't set your contactinfo.
34261 - Implement --verify-config command-line option to check if your torrc
34262 is valid without actually launching Tor.
34263 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
34264 rather than just rejecting it.
34267 Changes in version 0.1.0.5-rc - 2005-04-27
34269 - Stop trying to print a null pointer if an OR conn fails because
34270 we didn't like its cert.
34272 - Switch our internal buffers implementation to use a ring buffer,
34273 to hopefully improve performance for fast servers a lot.
34274 - Add HttpsProxyAuthenticator support (basic auth only), based
34275 on patch from Adam Langley.
34276 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
34277 the fast servers that have been joining lately.
34278 - Give hidden service accesses extra time on the first attempt,
34279 since 60 seconds is often only barely enough. This might improve
34281 - Improve performance for dirservers: stop re-parsing the whole
34282 directory every time you regenerate it.
34283 - Add more debugging info to help us find the weird dns freebsd
34284 pthreads bug; cleaner debug messages to help track future issues.
34287 Changes in version 0.0.9.9 - 2005-04-23
34288 o Bugfixes on 0.0.9.x:
34289 - If unofficial Tor clients connect and send weird TLS certs, our
34290 Tor server triggers an assert. This release contains a minimal
34291 backport from the broader fix that we put into 0.1.0.4-rc.
34294 Changes in version 0.1.0.4-rc - 2005-04-23
34296 - If unofficial Tor clients connect and send weird TLS certs, our
34297 Tor server triggers an assert. Stop asserting, and start handling
34298 TLS errors better in other situations too.
34299 - When the controller asks us to tell it about all the debug-level
34300 logs, it turns out we were generating debug-level logs while
34301 telling it about them, which turns into a bad loop. Now keep
34302 track of whether you're sending a debug log to the controller,
34303 and don't log when you are.
34304 - Fix the "postdescriptor" feature of the controller interface: on
34305 non-complete success, only say "done" once.
34307 - Clients are now willing to load balance over up to 2mB, not 1mB,
34308 of advertised bandwidth capacity.
34309 - Add a NoPublish config option, so you can be a server (e.g. for
34310 testing running Tor servers in other Tor networks) without
34311 publishing your descriptor to the primary dirservers.
34314 Changes in version 0.1.0.3-rc - 2005-04-08
34315 o Improvements on 0.1.0.2-rc:
34316 - Client now retries when streams end early for 'hibernating' or
34317 'resource limit' reasons, rather than failing them.
34318 - More automated handling for dirserver operators:
34319 - Automatically approve nodes running 0.1.0.2-rc or later,
34320 now that the the reachability detection stuff is working.
34321 - Now we allow two unverified servers with the same nickname
34322 but different keys. But if a nickname is verified, only that
34323 nickname+key are allowed.
34324 - If you're an authdirserver connecting to an address:port,
34325 and it's not the OR you were expecting, forget about that
34326 descriptor. If he *was* the one you were expecting, then forget
34327 about all other descriptors for that address:port.
34328 - Allow servers to publish descriptors from 12 hours in the future.
34329 Corollary: only whine about clock skew from the dirserver if
34330 he's a trusted dirserver (since now even verified servers could
34331 have quite wrong clocks).
34332 - Adjust maximum skew and age for rendezvous descriptors: let skew
34333 be 48 hours rather than 90 minutes.
34334 - Efficiency improvements:
34335 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
34336 it much faster to look up a circuit for each relay cell.
34337 - Remove most calls to assert_all_pending_dns_resolves_ok(),
34338 since they're eating our cpu on exit nodes.
34339 - Stop wasting time doing a case insensitive comparison for every
34340 dns name every time we do any lookup. Canonicalize the names to
34341 lowercase and be done with it.
34342 - Start sending 'truncated' cells back rather than destroy cells,
34343 if the circuit closes in front of you. This means we won't have
34344 to abandon partially built circuits.
34345 - Only warn once per nickname from add_nickname_list_to_smartlist
34346 per failure, so an entrynode or exitnode choice that's down won't
34348 - Put a note in the torrc about abuse potential with the default
34350 - Revise control spec and implementation to allow all log messages to
34351 be sent to controller with their severities intact (suggested by
34352 Matt Edman). Update TorControl to handle new log event types.
34353 - Provide better explanation messages when controller's POSTDESCRIPTOR
34355 - Stop putting nodename in the Platform string in server descriptors.
34356 It doesn't actually help, and it is confusing/upsetting some people.
34358 o Bugfixes on 0.1.0.2-rc:
34359 - We were printing the host mask wrong in exit policies in server
34360 descriptors. This isn't a critical bug though, since we were still
34361 obeying the exit policy internally.
34362 - Fix Tor when compiled with libevent but without pthreads: move
34363 connection_unregister() from _connection_free() to
34365 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
34366 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
34367 when we look through the connection array, we'll find any of the
34368 cpu/dnsworkers. This is no good.
34370 o Bugfixes on 0.0.9.8:
34371 - Fix possible bug on threading platforms (e.g. win32) which was
34372 leaking a file descriptor whenever a cpuworker or dnsworker died.
34373 - When using preferred entry or exit nodes, ignore whether the
34374 circuit wants uptime or capacity. They asked for the nodes, they
34376 - chdir() to your datadirectory at the *end* of the daemonize process,
34377 not the beginning. This was a problem because the first time you
34378 run tor, if your datadir isn't there, and you have runasdaemon set
34379 to 1, it will try to chdir to it before it tries to create it. Oops.
34380 - Handle changed router status correctly when dirserver reloads
34381 fingerprint file. We used to be dropping all unverified descriptors
34382 right then. The bug was hidden because we would immediately
34383 fetch a directory from another dirserver, which would include the
34384 descriptors we just dropped.
34385 - When we're connecting to an OR and he's got a different nickname/key
34386 than we were expecting, only complain loudly if we're an OP or a
34387 dirserver. Complaining loudly to the OR admins just confuses them.
34388 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
34389 artificially capped at 500kB.
34392 Changes in version 0.0.9.8 - 2005-04-07
34393 o Bugfixes on 0.0.9.x:
34394 - We have a bug that I haven't found yet. Sometimes, very rarely,
34395 cpuworkers get stuck in the 'busy' state, even though the cpuworker
34396 thinks of itself as idle. This meant that no new circuits ever got
34397 established. Here's a workaround to kill any cpuworker that's been
34398 busy for more than 100 seconds.
34401 Changes in version 0.1.0.2-rc - 2005-04-01
34402 o Bugfixes on 0.1.0.1-rc:
34403 - Fixes on reachability detection:
34404 - Don't check for reachability while hibernating.
34405 - If ORPort is reachable but DirPort isn't, still publish the
34406 descriptor, but zero out DirPort until it's found reachable.
34407 - When building testing circs for ORPort testing, use only
34408 high-bandwidth nodes, so fewer circuits fail.
34409 - Complain about unreachable ORPort separately from unreachable
34410 DirPort, so the user knows what's going on.
34411 - Make sure we only conclude ORPort reachability if we didn't
34412 initiate the conn. Otherwise we could falsely conclude that
34413 we're reachable just because we connected to the guy earlier
34414 and he used that same pipe to extend to us.
34415 - Authdirservers shouldn't do ORPort reachability detection,
34416 since they're in clique mode, so it will be rare to find a
34417 server not already connected to them.
34418 - When building testing circuits, always pick middle hops running
34419 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
34420 bug. (This is a kludge; it will go away when 0.0.9.x becomes
34422 - When we decide we're reachable, actually publish our descriptor
34424 - Fix bug in redirectstream in the controller.
34425 - Fix the state descriptor strings so logs don't claim edge streams
34426 are in a different state than they actually are.
34427 - Use recent libevent features when possible (this only really affects
34428 win32 and osx right now, because the new libevent with these
34429 features hasn't been released yet). Add code to suppress spurious
34431 - Prevent possible segfault in connection_close_unattached_ap().
34432 - Fix newlines on torrc in win32.
34433 - Improve error msgs when tor-resolve fails.
34435 o Improvements on 0.0.9.x:
34436 - New experimental script tor/contrib/ExerciseServer.py (needs more
34437 work) that uses the controller interface to build circuits and
34438 fetch pages over them. This will help us bootstrap servers that
34439 have lots of capacity but haven't noticed it yet.
34440 - New experimental script tor/contrib/PathDemo.py (needs more work)
34441 that uses the controller interface to let you choose whole paths
34443 "<hostname>.<path,separated by dots>.<length of path>.path"
34444 - When we've connected to an OR and handshaked but didn't like
34445 the result, we were closing the conn without sending destroy
34446 cells back for pending circuits. Now send those destroys.
34449 Changes in version 0.0.9.7 - 2005-04-01
34450 o Bugfixes on 0.0.9.x:
34451 - Fix another race crash bug (thanks to Glenn Fink for reporting).
34452 - Compare identity to identity, not to nickname, when extending to
34453 a router not already in the directory. This was preventing us from
34454 extending to unknown routers. Oops.
34455 - Make sure to create OS X Tor user in <500 range, so we aren't
34456 creating actual system users.
34457 - Note where connection-that-hasn't-sent-end was marked, and fix
34458 a few really loud instances of this harmless bug (it's fixed more
34462 Changes in version 0.1.0.1-rc - 2005-03-28
34464 - Add reachability testing. Your Tor server will automatically try
34465 to see if its ORPort and DirPort are reachable from the outside,
34466 and it won't upload its descriptor until it decides they are.
34467 - Handle unavailable hidden services better. Handle slow or busy
34468 hidden services better.
34469 - Add support for CONNECTing through https proxies, with "HttpsProxy"
34471 - New exit policy: accept most low-numbered ports, rather than
34472 rejecting most low-numbered ports.
34473 - More Tor controller support (still experimental). See
34474 http://tor.eff.org/doc/control-spec.txt for all the new features,
34475 including signals to emulate unix signals from any platform;
34476 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
34477 closestream; closecircuit; etc.
34478 - Make nt services work and start on startup on win32 (based on
34479 patch by Matt Edman).
34480 - Add a new AddressMap config directive to rewrite incoming socks
34481 addresses. This lets you, for example, declare an implicit
34482 required exit node for certain sites.
34483 - Add a new TrackHostExits config directive to trigger addressmaps
34484 for certain incoming socks addresses -- for sites that break when
34485 your exit keeps changing (based on patch by Mike Perry).
34486 - Redo the client-side dns cache so it's just an addressmap too.
34487 - Notice when our IP changes, and reset stats/uptime/reachability.
34488 - When an application is using socks5, give him the whole variety of
34489 potential socks5 responses (connect refused, host unreachable, etc),
34490 rather than just "success" or "failure".
34491 - A more sane version numbering system. See
34492 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
34493 - New contributed script "exitlist": a simple python script to
34494 parse directories and find Tor nodes that exit to listed
34496 - New contributed script "privoxy-tor-toggle" to toggle whether
34497 Privoxy uses Tor. Seems to be configured for Debian by default.
34498 - Report HTTP reasons to client when getting a response from directory
34499 servers -- so you can actually know what went wrong.
34500 - New config option MaxAdvertisedBandwidth which lets you advertise
34501 a low bandwidthrate (to not attract as many circuits) while still
34502 allowing a higher bandwidthrate in reality.
34504 o Robustness/stability fixes:
34505 - Make Tor use Niels Provos's libevent instead of its current
34506 poll-but-sometimes-select mess. This will let us use faster async
34507 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
34509 - pthread support now too. This was forced because when we forked,
34510 we ended up wasting a lot of duplicate ram over time. Also switch
34511 to foo_r versions of some library calls to allow reentry and
34513 - Better handling for heterogeneous / unreliable nodes:
34514 - Annotate circuits w/ whether they aim to contain high uptime nodes
34515 and/or high capacity nodes. When building circuits, choose
34517 - This means that every single node in an intro rend circuit,
34518 not just the last one, will have a minimum uptime.
34519 - New config option LongLivedPorts to indicate application streams
34520 that will want high uptime circuits.
34521 - Servers reset uptime when a dir fetch entirely fails. This
34522 hopefully reflects stability of the server's network connectivity.
34523 - If somebody starts his tor server in Jan 2004 and then fixes his
34524 clock, don't make his published uptime be a year.
34525 - Reset published uptime when you wake up from hibernation.
34526 - Introduce a notion of 'internal' circs, which are chosen without
34527 regard to the exit policy of the last hop. Intro and rendezvous
34528 circs must be internal circs, to avoid leaking information. Resolve
34529 and connect streams can use internal circs if they want.
34530 - New circuit pooling algorithm: make sure to have enough circs around
34531 to satisfy any predicted ports, and also make sure to have 2 internal
34532 circs around if we've required internal circs lately (and with high
34533 uptime if we've seen that lately too).
34534 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
34535 which describes how often we retry making new circuits if current
34536 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
34537 how long we're willing to make use of an already-dirty circuit.
34538 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
34539 circ as necessary, if there are any completed ones lying around
34540 when we try to launch one.
34541 - Make hidden services try to establish a rendezvous for 30 seconds,
34542 rather than for n (where n=3) attempts to build a circuit.
34543 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
34544 "ShutdownWaitLength".
34545 - Try to be more zealous about calling connection_edge_end when
34546 things go bad with edge conns in connection.c.
34547 - Revise tor-spec to add more/better stream end reasons.
34548 - Revise all calls to connection_edge_end to avoid sending "misc",
34549 and to take errno into account where possible.
34552 - Fix a race condition that can trigger an assert, when we have a
34553 pending create cell and an OR connection fails right then.
34554 - Fix several double-mark-for-close bugs, e.g. where we were finding
34555 a conn for a cell even if that conn is already marked for close.
34556 - Make sequence of log messages when starting on win32 with no config
34557 file more reasonable.
34558 - When choosing an exit node for a new non-internal circ, don't take
34559 into account whether it'll be useful for any pending x.onion
34560 addresses -- it won't.
34561 - Turn addr_policy_compare from a tristate to a quadstate; this should
34562 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
34563 for google.com" problem.
34564 - Make "platform" string in descriptor more accurate for Win32 servers,
34565 so it's not just "unknown platform".
34566 - Fix an edge case in parsing config options (thanks weasel).
34567 If they say "--" on the commandline, it's not an option.
34568 - Reject odd-looking addresses at the client (e.g. addresses that
34569 contain a colon), rather than having the server drop them because
34571 - tor-resolve requests were ignoring .exit if there was a working circuit
34572 they could use instead.
34573 - REUSEADDR on normal platforms means you can rebind to the port
34574 right after somebody else has let it go. But REUSEADDR on win32
34575 means to let you bind to the port _even when somebody else
34576 already has it bound_! So, don't do that on Win32.
34577 - Change version parsing logic: a version is "obsolete" if it is not
34578 recommended and (1) there is a newer recommended version in the
34579 same series, or (2) there are no recommended versions in the same
34580 series, but there are some recommended versions in a newer series.
34581 A version is "new" if it is newer than any recommended version in
34583 - Stop most cases of hanging up on a socks connection without sending
34587 - Require BandwidthRate to be at least 20kB/s for servers.
34588 - When a dirserver causes you to give a warn, mention which dirserver
34590 - New config option DirAllowPrivateAddresses for authdirservers.
34591 Now by default they refuse router descriptors that have non-IP or
34592 private-IP addresses.
34593 - Stop publishing socksport in the directory, since it's not
34594 actually meant to be public. For compatibility, publish a 0 there
34596 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
34597 smart" value, that is low for servers and high for clients.
34598 - If our clock jumps forward by 100 seconds or more, assume something
34599 has gone wrong with our network and abandon all not-yet-used circs.
34600 - Warn when exit policy implicitly allows local addresses.
34601 - If we get an incredibly skewed timestamp from a dirserver mirror
34602 that isn't a verified OR, don't warn -- it's probably him that's
34604 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
34605 cookies to disk and doesn't log each web request to disk. (Thanks
34606 to Brett Carrington for pointing this out.)
34607 - When a client asks us for a dir mirror and we don't have one,
34608 launch an attempt to get a fresh one.
34609 - If we're hibernating and we get a SIGINT, exit immediately.
34610 - Add --with-dmalloc ./configure option, to track memory leaks.
34611 - And try to free all memory on closing, so we can detect what
34613 - Cache local dns resolves correctly even when they're .exit
34615 - Give a better warning when some other server advertises an
34616 ORPort that is actually an apache running ssl.
34617 - Add "opt hibernating 1" to server descriptor to make it clearer
34618 whether the server is hibernating.
34621 Changes in version 0.0.9.6 - 2005-03-24
34622 o Bugfixes on 0.0.9.x (crashes and asserts):
34623 - Add new end stream reasons to maintenance branch. Fix bug where
34624 reason (8) could trigger an assert. Prevent bug from recurring.
34625 - Apparently win32 stat wants paths to not end with a slash.
34626 - Fix assert triggers in assert_cpath_layer_ok(), where we were
34627 blowing away the circuit that conn->cpath_layer points to, then
34628 checking to see if the circ is well-formed. Backport check to make
34629 sure we dont use the cpath on a closed connection.
34630 - Prevent circuit_resume_edge_reading_helper() from trying to package
34631 inbufs for marked-for-close streams.
34632 - Don't crash on hup if your options->address has become unresolvable.
34633 - Some systems (like OS X) sometimes accept() a connection and tell
34634 you the remote host is 0.0.0.0:0. If this happens, due to some
34635 other mis-features, we get confused; so refuse the conn for now.
34637 o Bugfixes on 0.0.9.x (other):
34638 - Fix harmless but scary "Unrecognized content encoding" warn message.
34639 - Add new stream error reason: TORPROTOCOL reason means "you are not
34640 speaking a version of Tor I understand; say bye-bye to your stream."
34641 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
34642 into the future, now that we are more tolerant of skew. This
34643 resolves a bug where a Tor server would refuse to cache a directory
34644 because all the directories it gets are too far in the future;
34645 yet the Tor server never logs any complaints about clock skew.
34646 - Mac packaging magic: make man pages useable, and do not overwrite
34647 existing torrc files.
34648 - Make OS X log happily to /var/log/tor/tor.log
34651 Changes in version 0.0.9.5 - 2005-02-22
34652 o Bugfixes on 0.0.9.x:
34653 - Fix an assert race at exit nodes when resolve requests fail.
34654 - Stop picking unverified dir mirrors--it only leads to misery.
34655 - Patch from Matt Edman to make NT services work better. Service
34656 support is still not compiled into the executable by default.
34657 - Patch from Dmitri Bely so the Tor service runs better under
34658 the win32 SYSTEM account.
34659 - Make tor-resolve actually work (?) on Win32.
34660 - Fix a sign bug when getrlimit claims to have 4+ billion
34661 file descriptors available.
34662 - Stop refusing to start when bandwidthburst == bandwidthrate.
34663 - When create cells have been on the onion queue more than five
34664 seconds, just send back a destroy and take them off the list.
34667 Changes in version 0.0.9.4 - 2005-02-03
34668 o Bugfixes on 0.0.9:
34669 - Fix an assert bug that took down most of our servers: when
34670 a server claims to have 1 GB of bandwidthburst, don't
34672 - Don't crash as badly if we have spawned the max allowed number
34673 of dnsworkers, or we're out of file descriptors.
34674 - Block more file-sharing ports in the default exit policy.
34675 - MaxConn is now automatically set to the hard limit of max
34676 file descriptors we're allowed (ulimit -n), minus a few for
34678 - Give a clearer message when servers need to raise their
34679 ulimit -n when they start running out of file descriptors.
34680 - SGI Compatibility patches from Jan Schaumann.
34681 - Tolerate a corrupt cached directory better.
34682 - When a dirserver hasn't approved your server, list which one.
34683 - Go into soft hibernation after 95% of the bandwidth is used,
34684 not 99%. This is especially important for daily hibernators who
34685 have a small accounting max. Hopefully it will result in fewer
34686 cut connections when the hard hibernation starts.
34687 - Load-balance better when using servers that claim more than
34688 800kB/s of capacity.
34689 - Make NT services work (experimental, only used if compiled in).
34692 Changes in version 0.0.9.3 - 2005-01-21
34693 o Bugfixes on 0.0.9:
34694 - Backport the cpu use fixes from main branch, so busy servers won't
34695 need as much processor time.
34696 - Work better when we go offline and then come back, or when we
34697 run Tor at boot before the network is up. We do this by
34698 optimistically trying to fetch a new directory whenever an
34699 application request comes in and we think we're offline -- the
34700 human is hopefully a good measure of when the network is back.
34701 - Backport some minimal hidserv bugfixes: keep rend circuits open as
34702 long as you keep using them; actually publish hidserv descriptors
34703 shortly after they change, rather than waiting 20-40 minutes.
34704 - Enable Mac startup script by default.
34705 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
34706 - When you update AllowUnverifiedNodes or FirewallPorts via the
34707 controller's setconf feature, we were always appending, never
34709 - When you update HiddenServiceDir via setconf, it was screwing up
34710 the order of reading the lines, making it fail.
34711 - Do not rewrite a cached directory back to the cache; otherwise we
34712 will think it is recent and not fetch a newer one on startup.
34713 - Workaround for webservers that lie about Content-Encoding: Tor
34714 now tries to autodetect compressed directories and compression
34715 itself. This lets us Proxypass dir fetches through apache.
34718 Changes in version 0.0.9.2 - 2005-01-04
34719 o Bugfixes on 0.0.9 (crashes and asserts):
34720 - Fix an assert on startup when the disk is full and you're logging
34722 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
34723 style address, then we'd crash.
34724 - Fix an assert trigger when the running-routers string we get from
34725 a dirserver is broken.
34726 - Make worker threads start and run on win32. Now win32 servers
34728 - Bandaid (not actually fix, but now it doesn't crash) an assert
34729 where the dns worker dies mysteriously and the main Tor process
34730 doesn't remember anything about the address it was resolving.
34732 o Bugfixes on 0.0.9 (Win32):
34733 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
34734 name out of the warning/assert messages.
34735 - Fix a superficial "unhandled error on read" bug on win32.
34736 - The win32 installer no longer requires a click-through for our
34737 license, since our Free Software license grants rights but does not
34739 - Win32: When connecting to a dirserver fails, try another one
34740 immediately. (This was already working for non-win32 Tors.)
34741 - Stop trying to parse $HOME on win32 when hunting for default
34743 - Make tor-resolve.c work on win32 by calling network_init().
34745 o Bugfixes on 0.0.9 (other):
34746 - Make 0.0.9.x build on Solaris again.
34747 - Due to a fencepost error, we were blowing away the \n when reporting
34748 confvalue items in the controller. So asking for multiple config
34749 values at once couldn't work.
34750 - When listing circuits that are pending on an opening OR connection,
34751 if we're an OR we were listing circuits that *end* at us as
34752 being pending on every listener, dns/cpu worker, etc. Stop that.
34753 - Dirservers were failing to create 'running-routers' or 'directory'
34754 strings if we had more than some threshold of routers. Fix them so
34755 they can handle any number of routers.
34756 - Fix a superficial "Duplicate mark for close" bug.
34757 - Stop checking for clock skew for OR connections, even for servers.
34758 - Fix a fencepost error that was chopping off the last letter of any
34759 nickname that is the maximum allowed nickname length.
34760 - Update URLs in log messages so they point to the new website.
34761 - Fix a potential problem in mangling server private keys while
34762 writing to disk (not triggered yet, as far as we know).
34763 - Include the licenses for other free software we include in Tor,
34764 now that we're shipping binary distributions more regularly.
34767 Changes in version 0.0.9.1 - 2004-12-15
34768 o Bugfixes on 0.0.9:
34769 - Make hibernation actually work.
34770 - Make HashedControlPassword config option work.
34771 - When we're reporting event circuit status to a controller,
34772 don't use the stream status code.
34775 Changes in version 0.0.9 - 2004-12-12
34777 - Clean up manpage and torrc.sample file.
34778 - Clean up severities and text of log warnings.
34780 - Make servers trigger an assert when they enter hibernation.
34783 Changes in version 0.0.9rc7 - 2004-12-08
34784 o Bugfixes on 0.0.9rc:
34785 - Fix a stack-trashing crash when an exit node begins hibernating.
34786 - Avoid looking at unallocated memory while considering which
34787 ports we need to build circuits to cover.
34788 - Stop a sigpipe: when an 'end' cell races with eof from the app,
34789 we shouldn't hold-open-until-flush if the eof arrived first.
34790 - Fix a bug with init_cookie_authentication() in the controller.
34791 - When recommending new-format log lines, if the upper bound is
34792 LOG_ERR, leave it implicit.
34794 o Bugfixes on 0.0.8.1:
34795 - Fix a whole slew of memory leaks.
34796 - Fix isspace() and friends so they still make Solaris happy
34797 but also so they don't trigger asserts on win32.
34798 - Fix parse_iso_time on platforms without strptime (eg win32).
34799 - win32: tolerate extra "readable" events better.
34800 - win32: when being multithreaded, leave parent fdarray open.
34801 - Make unit tests work on win32.
34804 Changes in version 0.0.9rc6 - 2004-12-06
34805 o Bugfixes on 0.0.9pre:
34806 - Clean up some more integer underflow opportunities (not exploitable
34808 - While hibernating, hup should not regrow our listeners.
34809 - Send an end to the streams we close when we hibernate, rather
34810 than just chopping them off.
34811 - React to eof immediately on non-open edge connections.
34813 o Bugfixes on 0.0.8.1:
34814 - Calculate timeout for waiting for a connected cell from the time
34815 we sent the begin cell, not from the time the stream started. If
34816 it took a long time to establish the circuit, we would time out
34817 right after sending the begin cell.
34818 - Fix router_compare_addr_to_addr_policy: it was not treating a port
34819 of * as always matching, so we were picking reject *:* nodes as
34820 exit nodes too. Oops.
34823 - New circuit building strategy: keep a list of ports that we've
34824 used in the past 6 hours, and always try to have 2 circuits open
34825 or on the way that will handle each such port. Seed us with port
34826 80 so web users won't complain that Tor is "slow to start up".
34827 - Make kill -USR1 dump more useful stats about circuits.
34828 - When warning about retrying or giving up, print the address, so
34829 the user knows which one it's talking about.
34830 - If you haven't used a clean circuit in an hour, throw it away,
34831 just to be on the safe side. (This means after 6 hours a totally
34832 unused Tor client will have no circuits open.)
34835 Changes in version 0.0.9rc5 - 2004-12-01
34836 o Bugfixes on 0.0.8.1:
34837 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
34838 - Let resolve conns retry/expire also, rather than sticking around
34840 - If we are using select, make sure we stay within FD_SETSIZE.
34842 o Bugfixes on 0.0.9pre:
34843 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
34844 but doesn't seem to be currently; thanks to Ilja van Sprundel for
34846 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
34847 instead. Impose minima and maxima for all *Period options; impose
34848 even tighter maxima for fetching if we are a caching dirserver.
34849 Clip rather than rejecting.
34850 - Fetch cached running-routers from servers that serve it (that is,
34851 authdirservers and servers running 0.0.9rc5-cvs or later.)
34854 - Accept *:706 (silc) in default exit policy.
34855 - Implement new versioning format for post 0.1.
34856 - Support "foo.nickname.exit" addresses, to let Alice request the
34857 address "foo" as viewed by exit node "nickname". Based on a patch
34859 - Make tor --version --version dump the cvs Id of every file.
34862 Changes in version 0.0.9rc4 - 2004-11-28
34863 o Bugfixes on 0.0.8.1:
34864 - Make windows sockets actually non-blocking (oops), and handle
34865 win32 socket errors better.
34867 o Bugfixes on 0.0.9rc1:
34868 - Actually catch the -USR2 signal.
34871 Changes in version 0.0.9rc3 - 2004-11-25
34872 o Bugfixes on 0.0.8.1:
34873 - Flush the log file descriptor after we print "Tor opening log file",
34874 so we don't see those messages days later.
34876 o Bugfixes on 0.0.9rc1:
34877 - Make tor-resolve work again.
34878 - Avoid infinite loop in tor-resolve if tor hangs up on it.
34879 - Fix an assert trigger for clients/servers handling resolves.
34882 Changes in version 0.0.9rc2 - 2004-11-24
34883 o Bugfixes on 0.0.9rc1:
34884 - I broke socks5 support while fixing the eof bug.
34885 - Allow unitless bandwidths and intervals; they default to bytes
34887 - New servers don't start out hibernating; they are active until
34888 they run out of bytes, so they have a better estimate of how
34889 long it takes, and so their operators can know they're working.
34892 Changes in version 0.0.9rc1 - 2004-11-23
34893 o Bugfixes on 0.0.8.1:
34894 - Finally fix a bug that's been plaguing us for a year:
34895 With high load, circuit package window was reaching 0. Whenever
34896 we got a circuit-level sendme, we were reading a lot on each
34897 socket, but only writing out a bit. So we would eventually reach
34898 eof. This would be noticed and acted on even when there were still
34899 bytes sitting in the inbuf.
34900 - When poll() is interrupted, we shouldn't believe the revents values.
34902 o Bugfixes on 0.0.9pre6:
34903 - Fix hibernate bug that caused pre6 to be broken.
34904 - Don't keep rephist info for routers that haven't had activity for
34905 24 hours. (This matters now that clients have keys, since we track
34907 - Never call close_temp_logs while validating log options.
34908 - Fix backslash-escaping on tor.sh.in and torctl.in.
34911 - Implement weekly/monthly/daily accounting: now you specify your
34912 hibernation properties by
34913 AccountingMax N bytes|KB|MB|GB|TB
34914 AccountingStart day|week|month [day] HH:MM
34915 Defaults to "month 1 0:00".
34916 - Let bandwidth and interval config options be specified as 5 bytes,
34917 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
34918 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
34919 get back to normal.)
34920 - If your requested entry or exit node has advertised bandwidth 0,
34922 - Be more greedy about filling up relay cells -- we try reading again
34923 once we've processed the stuff we read, in case enough has arrived
34924 to fill the last cell completely.
34925 - Apply NT service patch from Osamu Fujino. Still needs more work.
34928 Changes in version 0.0.9pre6 - 2004-11-15
34929 o Bugfixes on 0.0.8.1:
34930 - Fix assert failure on malformed socks4a requests.
34931 - Use identity comparison, not nickname comparison, to choose which
34932 half of circuit-ID-space each side gets to use. This is needed
34933 because sometimes we think of a router as a nickname, and sometimes
34934 as a hex ID, and we can't predict what the other side will do.
34935 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
34936 write() call will fail and we handle it there.
34937 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
34938 and smartlist_len, which are two major profiling offenders.
34940 o Bugfixes on 0.0.9pre5:
34941 - Fix a bug in read_all that was corrupting config files on windows.
34942 - When we're raising the max number of open file descriptors to
34943 'unlimited', don't log that we just raised it to '-1'.
34944 - Include event code with events, as required by control-spec.txt.
34945 - Don't give a fingerprint when clients do --list-fingerprint:
34946 it's misleading, because it will never be the same again.
34947 - Stop using strlcpy in tor_strndup, since it was slowing us
34949 - Remove warn on startup about missing cached-directory file.
34950 - Make kill -USR1 work again.
34951 - Hibernate if we start tor during the "wait for wakeup-time" phase
34952 of an accounting interval. Log our hibernation plans better.
34953 - Authoritative dirservers now also cache their directory, so they
34954 have it on start-up.
34957 - Fetch running-routers; cache running-routers; compress
34958 running-routers; serve compressed running-routers.z
34959 - Add NSI installer script contributed by J Doe.
34960 - Commit VC6 and VC7 workspace/project files.
34961 - Commit a tor.spec for making RPM files, with help from jbash.
34962 - Add contrib/torctl.in contributed by Glenn Fink.
34963 - Implement the control-spec's SAVECONF command, to write your
34964 configuration to torrc.
34965 - Get cookie authentication for the controller closer to working.
34966 - Include control-spec.txt in the tarball.
34967 - When set_conf changes our server descriptor, upload a new copy.
34968 But don't upload it too often if there are frequent changes.
34969 - Document authentication config in man page, and document signals
34971 - Clean up confusing parts of man page and torrc.sample.
34972 - Make expand_filename handle ~ and ~username.
34973 - Use autoconf to enable largefile support where necessary. Use
34974 ftello where available, since ftell can fail at 2GB.
34975 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
34976 log more informatively.
34977 - Give a slightly more useful output for "tor -h".
34978 - Refuse application socks connections to port 0.
34979 - Check clock skew for verified servers, but allow unverified
34980 servers and clients to have any clock skew.
34981 - Break DirFetchPostPeriod into:
34982 - DirFetchPeriod for fetching full directory,
34983 - StatusFetchPeriod for fetching running-routers,
34984 - DirPostPeriod for posting server descriptor,
34985 - RendPostPeriod for posting hidden service descriptors.
34986 - Make sure the hidden service descriptors are at a random offset
34987 from each other, to hinder linkability.
34990 Changes in version 0.0.9pre5 - 2004-11-09
34991 o Bugfixes on 0.0.9pre4:
34992 - Fix a seg fault in unit tests (doesn't affect main program).
34993 - Fix an assert bug where a hidden service provider would fail if
34994 the first hop of his rendezvous circuit was down.
34995 - Hidden service operators now correctly handle version 1 style
34996 INTRODUCE1 cells (nobody generates them still, so not a critical
34998 - If do_hup fails, actually notice.
34999 - Handle more errnos from accept() without closing the listener.
35000 Some OpenBSD machines were closing their listeners because
35001 they ran out of file descriptors.
35002 - Send resolve cells to exit routers that are running a new
35003 enough version of the resolve code to work right.
35004 - Better handling of winsock includes on non-MSV win32 compilers.
35005 - Some people had wrapped their tor client/server in a script
35006 that would restart it whenever it died. This did not play well
35007 with our "shut down if your version is obsolete" code. Now people
35008 don't fetch a new directory if their local cached version is
35010 - Make our autogen.sh work on ksh as well as bash.
35013 - Hibernation: New config option "AccountingMaxKB" lets you
35014 set how many KBytes per month you want to allow your server to
35015 consume. Rather than spreading those bytes out evenly over the
35016 month, we instead hibernate for some of the month and pop up
35017 at a deterministic time, work until the bytes are consumed, then
35018 hibernate again. Config option "MonthlyAccountingStart" lets you
35019 specify which day of the month your billing cycle starts on.
35020 - Control interface: a separate program can now talk to your
35021 client/server over a socket, and get/set config options, receive
35022 notifications of circuits and streams starting/finishing/dying,
35023 bandwidth used, etc. The next step is to get some GUIs working.
35024 Let us know if you want to help out. See doc/control-spec.txt .
35025 - Ship a contrib/tor-control.py as an example script to interact
35026 with the control port.
35027 - "tor --hash-password zzyxz" will output a salted password for
35028 use in authenticating to the control interface.
35029 - New log format in config:
35030 "Log minsev[-maxsev] stdout|stderr|syslog" or
35031 "Log minsev[-maxsev] file /var/foo"
35034 - DirPolicy config option, to let people reject incoming addresses
35035 from their dirserver.
35036 - "tor --list-fingerprint" will list your identity key fingerprint
35038 - Add "pass" target for RedirectExit, to make it easier to break
35039 out of a sequence of RedirectExit rules.
35040 - Clients now generate a TLS cert too, in preparation for having
35041 them act more like real nodes.
35042 - Ship src/win32/ in the tarball, so people can use it to build.
35043 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
35045 - New "router-status" line in directory, to better bind each verified
35046 nickname to its identity key.
35047 - Deprecate unofficial config option abbreviations, and abbreviations
35048 not on the command line.
35049 - Add a pure-C tor-resolve implementation.
35050 - Use getrlimit and friends to ensure we can reach MaxConn (currently
35051 1024) file descriptors.
35053 o Code security improvements, inspired by Ilja:
35054 - Replace sprintf with snprintf. (I think they were all safe, but
35056 - Replace strcpy/strncpy with strlcpy in more places.
35057 - Avoid strcat; use snprintf or strlcat instead.
35058 - snprintf wrapper with consistent (though not C99) overflow behavior.
35061 Changes in version 0.0.9pre4 - 2004-10-17
35062 o Bugfixes on 0.0.9pre3:
35063 - If the server doesn't specify an exit policy, use the real default
35064 exit policy, not reject *:*.
35065 - Ignore fascistfirewall when uploading/downloading hidden service
35066 descriptors, since we go through Tor for those; and when using
35067 an HttpProxy, since we assume it can reach them all.
35068 - When looking for an authoritative dirserver, use only the ones
35069 configured at boot. Don't bother looking in the directory.
35070 - The rest of the fix for get_default_conf_file() on older win32.
35071 - Make 'Routerfile' config option obsolete.
35074 - New 'MyFamily nick1,...' config option for a server to
35075 specify other servers that shouldn't be used in the same circuit
35076 with it. Only believed if nick1 also specifies us.
35077 - New 'NodeFamily nick1,nick2,...' config option for a client to
35078 specify nodes that it doesn't want to use in the same circuit.
35079 - New 'Redirectexit pattern address:port' config option for a
35080 server to redirect exit connections, e.g. to a local squid.
35083 Changes in version 0.0.9pre3 - 2004-10-13
35084 o Bugfixes on 0.0.8.1:
35085 - Better torrc example lines for dirbindaddress and orbindaddress.
35086 - Improved bounds checking on parsed ints (e.g. config options and
35087 the ones we find in directories.)
35088 - Better handling of size_t vs int, so we're more robust on 64
35090 - Fix the rest of the bug where a newly started OR would appear
35091 as unverified even after we've added his fingerprint and hupped
35093 - Fix a bug from 0.0.7: when read() failed on a stream, we would
35094 close it without sending back an end. So 'connection refused'
35095 would simply be ignored and the user would get no response.
35097 o Bugfixes on 0.0.9pre2:
35098 - Serving the cached-on-disk directory to people is bad. We now
35099 provide no directory until we've fetched a fresh one.
35100 - Workaround for bug on windows where cached-directories get crlf
35102 - Make get_default_conf_file() work on older windows too.
35103 - If we write a *:* exit policy line in the descriptor, don't write
35104 any more exit policy lines.
35107 - Use only 0.0.9pre1 and later servers for resolve cells.
35108 - Make the dirservers file obsolete.
35109 - Include a dir-signing-key token in directories to tell the
35110 parsing entity which key is being used to sign.
35111 - Remove the built-in bulky default dirservers string.
35112 - New config option "Dirserver %s:%d [fingerprint]", which can be
35113 repeated as many times as needed. If no dirservers specified,
35114 default to moria1,moria2,tor26.
35115 - Make moria2 advertise a dirport of 80, so people behind firewalls
35116 will be able to get a directory.
35117 - Http proxy support
35118 - Dirservers translate requests for http://%s:%d/x to /x
35119 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
35120 be routed through this host.
35121 - Clients ask for /tor/x rather than /x for new enough dirservers.
35122 This way we can one day coexist peacefully with apache.
35123 - Clients specify a "Host: %s%d" http header, to be compatible
35124 with more proxies, and so running squid on an exit node can work.
35127 Changes in version 0.0.8.1 - 2004-10-13
35129 - Fix a seg fault that can be triggered remotely for Tor
35130 clients/servers with an open dirport.
35131 - Fix a rare assert trigger, where routerinfos for entries in
35132 our cpath would expire while we're building the path.
35133 - Fix a bug in OutboundBindAddress so it (hopefully) works.
35134 - Fix a rare seg fault for people running hidden services on
35135 intermittent connections.
35136 - Fix a bug in parsing opt keywords with objects.
35137 - Fix a stale pointer assert bug when a stream detaches and
35139 - Fix a string format vulnerability (probably not exploitable)
35140 in reporting stats locally.
35141 - Fix an assert trigger: sometimes launching circuits can fail
35142 immediately, e.g. because too many circuits have failed recently.
35143 - Fix a compile warning on 64 bit platforms.
35146 Changes in version 0.0.9pre2 - 2004-10-03
35148 - Make fetching a cached directory work for 64-bit platforms too.
35149 - Make zlib.h a required header, not an optional header.
35152 Changes in version 0.0.9pre1 - 2004-10-01
35154 - Stop using separate defaults for no-config-file and
35155 empty-config-file. Now you have to explicitly turn off SocksPort,
35156 if you don't want it open.
35157 - Fix a bug in OutboundBindAddress so it (hopefully) works.
35158 - Improve man page to mention more of the 0.0.8 features.
35159 - Fix a rare seg fault for people running hidden services on
35160 intermittent connections.
35161 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
35163 - Fix more dns related bugs: send back resolve_failed and end cells
35164 more reliably when the resolve fails, rather than closing the
35165 circuit and then trying to send the cell. Also attach dummy resolve
35166 connections to a circuit *before* calling dns_resolve(), to fix
35167 a bug where cached answers would never be sent in RESOLVED cells.
35168 - When we run out of disk space, or other log writing error, don't
35169 crash. Just stop logging to that log and continue.
35170 - We were starting to daemonize before we opened our logs, so if
35171 there were any problems opening logs, we would complain to stderr,
35172 which wouldn't work, and then mysteriously exit.
35173 - Fix a rare bug where sometimes a verified OR would connect to us
35174 before he'd uploaded his descriptor, which would cause us to
35175 assign conn->nickname as though he's unverified. Now we look through
35176 the fingerprint list to see if he's there.
35177 - Fix a rare assert trigger, where routerinfos for entries in
35178 our cpath would expire while we're building the path.
35181 - Clients can ask dirservers for /dir.z to get a compressed version
35182 of the directory. Only works for servers running 0.0.9, of course.
35183 - Make clients cache directories and use them to seed their router
35184 lists at startup. This means clients have a datadir again.
35185 - Configuration infrastructure support for warning on obsolete
35187 - Respond to content-encoding headers by trying to uncompress as
35189 - Reply with a deflated directory when a client asks for "dir.z".
35190 We could use allow-encodings instead, but allow-encodings isn't
35191 specified in HTTP 1.0.
35192 - Raise the max dns workers from 50 to 100.
35193 - Discourage people from setting their dirfetchpostperiod more often
35194 than once per minute.
35195 - Protect dirservers from overzealous descriptor uploading -- wait
35196 10 seconds after directory gets dirty, before regenerating.
35199 Changes in version 0.0.8 - 2004-08-25
35200 o Port it to SunOS 5.9 / Athena
35203 Changes in version 0.0.8rc2 - 2004-08-20
35204 o Make it compile on cygwin again.
35205 o When picking unverified routers, skip those with low uptime and/or
35206 low bandwidth, depending on what properties you care about.
35209 Changes in version 0.0.8rc1 - 2004-08-18
35210 o Changes from 0.0.7.3:
35212 - Fix assert triggers: if the other side returns an address 0.0.0.0,
35213 don't put it into the client dns cache.
35214 - If a begin failed due to exit policy, but we believe the IP address
35215 should have been allowed, switch that router to exitpolicy reject *:*
35216 until we get our next directory.
35218 - Clients choose nodes proportional to advertised bandwidth.
35219 - Avoid using nodes with low uptime as introduction points.
35220 - Handle servers with dynamic IP addresses: don't replace
35221 options->Address with the resolved one at startup, and
35222 detect our address right before we make a routerinfo each time.
35223 - 'FascistFirewall' option to pick dirservers and ORs on specific
35224 ports; plus 'FirewallPorts' config option to tell FascistFirewall
35225 which ports are open. (Defaults to 80,443)
35226 - Be more aggressive about trying to make circuits when the network
35227 has changed (e.g. when you unsuspend your laptop).
35228 - Check for time skew on http headers; report date in response to
35230 - If the entrynode config line has only one node, don't pick it as
35232 - Add strict{entry|exit}nodes config options. If set to 1, then
35233 we refuse to build circuits that don't include the specified entry
35235 - OutboundBindAddress config option, to bind to a specific
35236 IP address for outgoing connect()s.
35237 - End truncated log entries (e.g. directories) with "[truncated]".
35239 o Patches to 0.0.8preX:
35241 - Patches to compile and run on win32 again (maybe)?
35242 - Fix crash when looking for ~/.torrc with no $HOME set.
35243 - Fix a race bug in the unit tests.
35244 - Handle verified/unverified name collisions better when new
35245 routerinfo's arrive in a directory.
35246 - Sometimes routers were getting entered into the stats before
35247 we'd assigned their identity_digest. Oops.
35248 - Only pick and establish intro points after we've gotten a
35251 - AllowUnverifiedNodes config option to let circuits choose no-name
35252 routers in entry,middle,exit,introduction,rendezvous positions.
35253 Allow middle and rendezvous positions by default.
35254 - Add a man page for tor-resolve.
35257 Changes in version 0.0.7.3 - 2004-08-12
35258 o Stop dnsworkers from triggering an assert failure when you
35259 ask them to resolve the host "".
35262 Changes in version 0.0.8pre3 - 2004-08-09
35263 o Changes from 0.0.7.2:
35264 - Allow multiple ORs with same nickname in routerlist -- now when
35265 people give us one identity key for a nickname, then later
35266 another, we don't constantly complain until the first expires.
35267 - Remember used bandwidth (both in and out), and publish 15-minute
35268 snapshots for the past day into our descriptor.
35269 - You can now fetch $DIRURL/running-routers to get just the
35270 running-routers line, not the whole descriptor list. (But
35271 clients don't use this yet.)
35272 - When people mistakenly use Tor as an http proxy, point them
35273 at the tor-doc.html rather than the INSTALL.
35274 - Remove our mostly unused -- and broken -- hex_encode()
35275 function. Use base16_encode() instead. (Thanks to Timo Lindfors
35276 for pointing out this bug.)
35277 - Rotate onion keys every 12 hours, not every 2 hours, so we have
35278 fewer problems with people using the wrong key.
35279 - Change the default exit policy to reject the default edonkey,
35280 kazaa, gnutella ports.
35281 - Add replace_file() to util.[ch] to handle win32's rename().
35283 o Changes from 0.0.8preX:
35284 - Fix two bugs in saving onion keys to disk when rotating, so
35285 hopefully we'll get fewer people using old onion keys.
35286 - Fix an assert error that was making SocksPolicy not work.
35287 - Be willing to expire routers that have an open dirport -- it's
35288 just the authoritative dirservers we want to not forget.
35289 - Reject tor-resolve requests for .onion addresses early, so we
35290 don't build a whole rendezvous circuit and then fail.
35291 - When you're warning a server that he's unverified, don't cry
35292 wolf unpredictably.
35293 - Fix a race condition: don't try to extend onto a connection
35294 that's still handshaking.
35295 - For servers in clique mode, require the conn to be open before
35296 you'll choose it for your path.
35297 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
35298 end relay cell, etc.
35299 - Measure bandwidth capacity over the last 24 hours, not just 12
35300 - Bugfix: authoritative dirservers were making and signing a new
35301 directory for each client, rather than reusing the cached one.
35304 Changes in version 0.0.8pre2 - 2004-08-04
35305 o Changes from 0.0.7.2:
35307 - Check directory signature _before_ you decide whether you're
35308 you're running an obsolete version and should exit.
35309 - Check directory signature _before_ you parse the running-routers
35310 list to decide who's running or verified.
35311 - Bugfixes and features:
35312 - Check return value of fclose while writing to disk, so we don't
35313 end up with broken files when servers run out of disk space.
35314 - Log a warning if the user uses an unsafe socks variant, so people
35315 are more likely to learn about privoxy or socat.
35316 - Dirservers now include RFC1123-style dates in the HTTP headers,
35317 which one day we will use to better detect clock skew.
35319 o Changes from 0.0.8pre1:
35320 - Make it compile without warnings again on win32.
35321 - Log a warning if you're running an unverified server, to let you
35322 know you might want to get it verified.
35323 - Only pick a default nickname if you plan to be a server.
35326 Changes in version 0.0.8pre1 - 2004-07-23
35328 - Made our unit tests compile again on OpenBSD 3.5, and tor
35329 itself compile again on OpenBSD on a sparc64.
35330 - We were neglecting milliseconds when logging on win32, so
35331 everything appeared to happen at the beginning of each second.
35333 o Protocol changes:
35334 - 'Extend' relay cell payloads now include the digest of the
35335 intended next hop's identity key. Now we can verify that we're
35336 extending to the right router, and also extend to routers we
35337 hadn't heard of before.
35340 - Tor nodes can now act as relays (with an advertised ORPort)
35341 without being manually verified by the dirserver operators.
35342 - Uploaded descriptors of unverified routers are now accepted
35343 by the dirservers, and included in the directory.
35344 - Verified routers are listed by nickname in the running-routers
35345 list; unverified routers are listed as "$<fingerprint>".
35346 - We now use hash-of-identity-key in most places rather than
35347 nickname or addr:port, for improved security/flexibility.
35348 - To avoid Sybil attacks, paths still use only verified servers.
35349 But now we have a chance to play around with hybrid approaches.
35350 - Nodes track bandwidth usage to estimate capacity (not used yet).
35351 - ClientOnly option for nodes that never want to become servers.
35352 - Directory caching.
35353 - "AuthoritativeDir 1" option for the official dirservers.
35354 - Now other nodes (clients and servers) will cache the latest
35355 directory they've pulled down.
35356 - They can enable their DirPort to serve it to others.
35357 - Clients will pull down a directory from any node with an open
35358 DirPort, and check the signature/timestamp correctly.
35359 - Authoritative dirservers now fetch directories from other
35360 authdirservers, to stay better synced.
35361 - Running-routers list tells who's down also, along with noting
35362 if they're verified (listed by nickname) or unverified (listed
35364 - Allow dirservers to serve running-router list separately.
35365 This isn't used yet.
35366 - ORs connect-on-demand to other ORs
35367 - If you get an extend cell to an OR you're not connected to,
35368 connect, handshake, and forward the create cell.
35369 - The authoritative dirservers stay connected to everybody,
35370 and everybody stays connected to 0.0.7 servers, but otherwise
35371 clients/servers expire unused connections after 5 minutes.
35372 - When servers get a sigint, they delay 30 seconds (refusing new
35373 connections) then exit. A second sigint causes immediate exit.
35374 - File and name management:
35375 - Look for .torrc if no CONFDIR "torrc" is found.
35376 - If no datadir is defined, then choose, make, and secure ~/.tor
35378 - If torrc not found, exitpolicy reject *:*.
35379 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
35380 - If no nickname is defined, derive default from hostname.
35381 - Rename secret key files, e.g. identity.key -> secret_id_key,
35382 to discourage people from mailing their identity key to tor-ops.
35383 - Refuse to build a circuit before the directory has arrived --
35384 it won't work anyway, since you won't know the right onion keys
35386 - Try other dirservers immediately if the one you try is down. This
35387 should tolerate down dirservers better now.
35388 - Parse tor version numbers so we can do an is-newer-than check
35389 rather than an is-in-the-list check.
35390 - New socks command 'resolve', to let us shim gethostbyname()
35392 - A 'tor_resolve' script to access the socks resolve functionality.
35393 - A new socks-extensions.txt doc file to describe our
35394 interpretation and extensions to the socks protocols.
35395 - Add a ContactInfo option, which gets published in descriptor.
35396 - Publish OR uptime in descriptor (and thus in directory) too.
35397 - Write tor version at the top of each log file
35398 - New docs in the tarball:
35400 - Document that you should proxy your SSL traffic too.
35403 Changes in version 0.0.7.2 - 2004-07-07
35404 o A better fix for the 0.0.0.0 problem, that will hopefully
35405 eliminate the remaining related assertion failures.
35408 Changes in version 0.0.7.1 - 2004-07-04
35409 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
35410 since internally we use 0.0.0.0 to signify "not yet resolved".
35413 Changes in version 0.0.7 - 2004-06-07
35414 o Updated the man page to reflect the new features.
35417 Changes in version 0.0.7rc2 - 2004-06-06
35418 o Changes from 0.0.7rc1:
35419 - Make it build on Win32 again.
35420 o Changes from 0.0.6.2:
35421 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
35425 Changes in version 0.0.7rc1 - 2004-06-02
35427 - On sighup, we were adding another log without removing the first
35428 one. So log messages would get duplicated n times for n sighups.
35429 - Several cases of using a connection after we'd freed it. The
35430 problem was that connections that are pending resolve are in both
35431 the pending_resolve tree, and also the circuit's resolving_streams
35432 list. When you want to remove one, you must remove it from both.
35433 - Fix a double-mark-for-close where an end cell arrived for a
35434 resolving stream, and then the resolve failed.
35435 - Check directory signatures based on name of signer, not on whom
35436 we got the directory from. This will let us cache directories more
35439 - Crank up some of our constants to handle more users.
35442 Changes in version 0.0.7pre1 - 2004-06-02
35443 o Fixes for crashes and other obnoxious bugs:
35444 - Fix an epipe bug: sometimes when directory connections failed
35445 to connect, we would give them a chance to flush before closing
35447 - When we detached from a circuit because of resolvefailed, we
35448 would immediately try the same circuit twice more, and then
35449 give up on the resolve thinking we'd tried three different
35451 - Limit the number of intro circuits we'll attempt to build for a
35452 hidden service per 15-minute period.
35453 - Check recommended-software string *early*, before actually parsing
35454 the directory. Thus we can detect an obsolete version and exit,
35455 even if the new directory format doesn't parse.
35456 o Fixes for security bugs:
35457 - Remember which nodes are dirservers when you startup, and if a
35458 random OR enables his dirport, don't automatically assume he's
35459 a trusted dirserver.
35461 - Directory connections were asking the wrong poll socket to
35462 start writing, and not asking themselves to start writing.
35463 - When we detached from a circuit because we sent a begin but
35464 didn't get a connected, we would use it again the first time;
35465 but after that we would correctly switch to a different one.
35466 - Stop warning when the first onion decrypt attempt fails; they
35467 will sometimes legitimately fail now that we rotate keys.
35468 - Override unaligned-access-ok check when $host_cpu is ia64 or
35469 arm. Apparently they allow it but the kernel whines.
35470 - Dirservers try to reconnect periodically too, in case connections
35472 - Fix some memory leaks in directory servers.
35473 - Allow backslash in Win32 filenames.
35474 - Made Tor build complain-free on FreeBSD, hopefully without
35475 breaking other BSD builds. We'll see.
35477 - Doxygen markup on all functions and global variables.
35478 - Make directory functions update routerlist, not replace it. So
35479 now directory disagreements are not so critical a problem.
35480 - Remove the upper limit on number of descriptors in a dirserver's
35481 directory (not that we were anywhere close).
35482 - Allow multiple logfiles at different severity ranges.
35483 - Allow *BindAddress to specify ":port" rather than setting *Port
35484 separately. Allow multiple instances of each BindAddress config
35485 option, so you can bind to multiple interfaces if you want.
35486 - Allow multiple exit policy lines, which are processed in order.
35487 Now we don't need that huge line with all the commas in it.
35488 - Enable accept/reject policies on SOCKS connections, so you can bind
35489 to 0.0.0.0 but still control who can use your OP.
35492 Changes in version 0.0.6.2 - 2004-05-16
35493 o Our integrity-checking digest was checking only the most recent cell,
35494 not the previous cells like we'd thought.
35495 Thanks to Stefan Mark for finding the flaw!
35498 Changes in version 0.0.6.1 - 2004-05-06
35499 o Fix two bugs in our AES counter-mode implementation (this affected
35500 onion-level stream encryption, but not TLS-level). It turns
35501 out we were doing something much more akin to a 16-character
35502 polyalphabetic cipher. Oops.
35503 Thanks to Stefan Mark for finding the flaw!
35504 o Retire moria3 as a directory server, and add tor26 as a directory
35508 Changes in version 0.0.6 - 2004-05-02
35509 [version bump only]
35512 Changes in version 0.0.6rc4 - 2004-05-01
35513 o Update the built-in dirservers list to use the new directory format
35514 o Fix a rare seg fault: if a node offering a hidden service attempts
35515 to build a circuit to Alice's rendezvous point and fails before it
35516 reaches the last hop, it retries with a different circuit, but
35518 o Handle windows socket errors correctly.
35521 Changes in version 0.0.6rc3 - 2004-04-28
35522 o Don't expire non-general excess circuits (if we had enough
35523 circuits open, we were expiring rendezvous circuits -- even
35524 when they had a stream attached. oops.)
35525 o Fetch randomness from /dev/urandom better (not via fopen/fread)
35526 o Better debugging for tls errors
35527 o Some versions of openssl have an SSL_pending function that erroneously
35528 returns bytes when there is a non-application record pending.
35529 o Set Content-Type on the directory and hidserv descriptor.
35530 o Remove IVs from cipher code, since AES-ctr has none.
35531 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
35532 o We were using an array of length zero in a few places.
35533 o win32's gethostbyname can't resolve an IP to an IP.
35534 o win32's close can't close a socket.
35537 Changes in version 0.0.6rc2 - 2004-04-26
35538 o Fix a bug where we were closing tls connections intermittently.
35539 It turns out openssl keeps its errors around -- so if an error
35540 happens, and you don't ask about it, and then another openssl
35541 operation happens and succeeds, and you ask if there was an error,
35542 it tells you about the first error. Fun fun.
35543 o Fix a bug that's been lurking since 27 may 03 (!)
35544 When passing back a destroy cell, we would use the wrong circ id.
35545 'Mostly harmless', but still worth fixing.
35546 o Since we don't support truncateds much, don't bother sending them;
35547 just close the circ.
35548 o check for <machine/limits.h> so we build on NetBSD again (I hope).
35549 o don't crash if a conn that sent a begin has suddenly lost its circuit
35550 (this was quite rare).
35553 Changes in version 0.0.6rc1 - 2004-04-25
35554 o We now rotate link (tls context) keys and onion keys.
35555 o CREATE cells now include oaep padding, so you can tell
35556 if you decrypted them correctly.
35557 o Add bandwidthburst to server descriptor.
35558 o Directories now say which dirserver signed them.
35559 o Use a tor_assert macro that logs failed assertions too.
35562 Changes in version 0.0.6pre5 - 2004-04-18
35563 o changes from 0.0.6pre4:
35564 - make tor build on broken freebsd 5.2 installs
35565 - fix a failed assert when you try an intro point, get a nack, and try
35566 a second one and it works.
35567 - when alice uses a port that the hidden service doesn't accept,
35568 it now sends back an end cell (denied by exit policy). otherwise
35569 alice would just have to wait to time out.
35570 - fix another rare bug: when we had tried all the intro
35571 points for a hidden service, we fetched the descriptor
35572 again, but we left our introcirc thinking it had already
35573 sent an intro, so it kept waiting for a response...
35574 - bugfix: when you sleep your hidden-service laptop, as soon
35575 as it wakes up it tries to upload a service descriptor, but
35576 socketpair fails for some reason (localhost not up yet?).
35577 now we simply give up on that upload, and we'll try again later.
35578 i'd still like to find the bug though.
35579 - if an intro circ waiting for an ack dies before getting one, then
35581 - we were reusing stale service descriptors and refetching usable
35585 Changes in version 0.0.6pre4 - 2004-04-14
35586 o changes from 0.0.6pre3:
35587 - when bob fails to connect to the rendezvous point, and his
35588 circ didn't fail because of the rendezvous point itself, then
35589 he retries a couple of times
35590 - we expire introduction and rendezvous circs more thoroughly
35591 (sometimes they were hanging around forever)
35592 - we expire unattached rendezvous streams that have been around
35593 too long (they were sticking around forever).
35594 - fix a measly fencepost error that was crashing everybody with
35598 Changes in version 0.0.6pre3 - 2004-04-14
35599 o changes from 0.0.6pre2:
35600 - make hup work again
35601 - fix some memory leaks for dirservers
35602 - allow more skew in rendezvous descriptor timestamps, to help
35603 handle people like blanu who don't know what time it is
35604 - normal circs are 3 hops, but some rend/intro circs are 4, if
35605 the initiator doesn't get to choose the last hop
35606 - send acks for introductions, so alice can know whether to try
35608 - bob publishes intro points more correctly
35609 o changes from 0.0.5:
35610 - fix an assert trigger that's been plaguing us since the days
35611 of 0.0.2prexx (thanks weasel!)
35612 - retry stream correctly when we fail to connect because of
35613 exit-policy-reject (should try another) or can't-resolve-address
35614 (also should try another, because dns on random internet servers
35616 - when we hup a dirserver and we've *removed* a server from the
35617 approved-routers list, now we remove that server from the
35618 in-memory directories too
35621 Changes in version 0.0.6pre2 - 2004-04-08
35622 o We fixed our base32 implementation. Now it works on all architectures.
35625 Changes in version 0.0.6pre1 - 2004-04-08
35627 - Hidden services and rendezvous points are implemented. Go to
35628 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
35629 hidden services. (This only works via a socks4a proxy such as
35630 Privoxy, and currently it's quite slow.)
35633 Changes in version 0.0.5 - 2004-03-30
35634 [version bump only]
35637 Changes in version 0.0.5rc3 - 2004-03-29
35638 o Install torrc as torrc.sample -- we no longer clobber your
35640 o Re-enable recommendedversion checking (we broke it in rc2, oops)
35641 o Add in a 'notice' log level for things the operator should hear
35642 but that aren't warnings
35645 Changes in version 0.0.5rc2 - 2004-03-29
35646 o Hold socks connection open until reply is flushed (if possible)
35647 o Make exit nodes resolve IPs to IPs immediately, rather than asking
35648 the dns farm to do it.
35649 o Fix c99 aliasing warnings in rephist.c
35650 o Don't include server descriptors that are older than 24 hours in the
35652 o Give socks 'reject' replies their whole 15s to attempt to flush,
35653 rather than seeing the 60s timeout and assuming the flush had failed.
35654 o Clean automake droppings from the cvs repository
35657 Changes in version 0.0.5rc1 - 2004-03-28
35658 o Fix mangled-state bug in directory fetching (was causing sigpipes).
35659 o Only build circuits after we've fetched the directory: clients were
35660 using only the directory servers before they'd fetched a directory.
35661 This also means longer startup time; so it goes.
35662 o Fix an assert trigger where an OP would fail to handshake, and we'd
35663 expect it to have a nickname.
35664 o Work around a tsocks bug: do a socks reject when AP connection dies
35665 early, else tsocks goes into an infinite loop.
35668 Changes in version 0.0.4 - 2004-03-26
35669 o When connecting to a dirserver or OR and the network is down,
35673 Changes in version 0.0.3 - 2004-03-26
35674 o Warn and fail if server chose a nickname with illegal characters
35675 o Port to Solaris and Sparc:
35676 - include missing header fcntl.h
35677 - have autoconf find -lsocket -lnsl automatically
35678 - deal with hardware word alignment
35679 - make uname() work (solaris has a different return convention)
35680 - switch from using signal() to sigaction()
35681 o Preliminary work on reputation system:
35682 - Keep statistics on success/fail of connect attempts; they're published
35683 by kill -USR1 currently.
35684 - Add a RunTesting option to try to learn link state by creating test
35685 circuits, even when SocksPort is off.
35686 - Remove unused open circuits when there are too many.
35689 Changes in version 0.0.2 - 2004-03-19
35690 - Include strlcpy and strlcat for safer string ops
35691 - define INADDR_NONE so we compile (but still not run) on solaris
35694 Changes in version 0.0.2pre27 - 2004-03-14
35696 - Allow internal tor networks (we were rejecting internal IPs,
35697 now we allow them if they're set explicitly).
35698 - And fix a few endian issues.
35701 Changes in version 0.0.2pre26 - 2004-03-14
35703 - If a stream times out after 15s without a connected cell, don't
35704 try that circuit again: try a new one.
35705 - Retry streams at most 4 times. Then give up.
35706 - When a dirserver gets a descriptor from an unknown router, it
35707 logs its fingerprint (so the dirserver operator can choose to
35708 accept it even without mail from the server operator).
35709 - Inform unapproved servers when we reject their descriptors.
35710 - Make tor build on Windows again. It works as a client, who knows
35712 - Clearer instructions in the torrc for how to set up a server.
35713 - Be more efficient about reading fd's when our global token bucket
35714 (used for rate limiting) becomes empty.
35716 - Stop asserting that computers always go forward in time. It's
35718 - When we sent a cell (e.g. destroy) and then marked an OR connection
35719 expired, we might close it before finishing a flush if the other
35720 side isn't reading right then.
35721 - Don't allow dirservers to start if they haven't defined
35722 RecommendedVersions
35723 - We were caching transient dns failures. Oops.
35724 - Prevent servers from publishing an internal IP as their address.
35725 - Address a strcat vulnerability in circuit.c
35728 Changes in version 0.0.2pre25 - 2004-03-04
35730 - Put the OR's IP in its router descriptor, not its fqdn. That way
35731 we'll stop being stalled by gethostbyname for nodes with flaky dns,
35734 - If the user typed in an address that didn't resolve, the server
35738 Changes in version 0.0.2pre24 - 2004-03-03
35740 - Fix an assertion failure in dns.c, where we were trying to dequeue
35741 a pending dns resolve even if it wasn't pending
35742 - Fix a spurious socks5 warning about still trying to write after the
35743 connection is finished.
35744 - Hold certain marked_for_close connections open until they're finished
35745 flushing, rather than losing bytes by closing them too early.
35746 - Correctly report the reason for ending a stream
35747 - Remove some duplicate calls to connection_mark_for_close
35748 - Put switch_id and start_daemon earlier in the boot sequence, so it
35749 will actually try to chdir() to options.DataDirectory
35750 - Make 'make test' exit(1) if a test fails; fix some unit tests
35751 - Make tor fail when you use a config option it doesn't know about,
35752 rather than warn and continue.
35753 - Make --version work
35754 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
35757 Changes in version 0.0.2pre23 - 2004-02-29
35759 - Print a statement when the first circ is finished, so the user
35760 knows it's working.
35761 - If a relay cell is unrecognized at the end of the circuit,
35762 send back a destroy. (So attacks to mutate cells are more
35764 - New config option 'excludenodes' to avoid certain nodes for circuits.
35765 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
35766 so you can collect coredumps there.
35768 - Fix a bug in tls flushing where sometimes data got wedged and
35769 didn't flush until more data got sent. Hopefully this bug was
35770 a big factor in the random delays we were seeing.
35771 - Make 'connected' cells include the resolved IP, so the client
35772 dns cache actually gets populated.
35773 - Disallow changing from ORPort=0 to ORPort>0 on hup.
35774 - When we time-out on a stream and detach from the circuit, send an
35775 end cell down it first.
35776 - Only warn about an unknown router (in exitnodes, entrynodes,
35777 excludenodes) after we've fetched a directory.
35780 Changes in version 0.0.2pre22 - 2004-02-26
35782 - Servers publish less revealing uname information in descriptors.
35783 - More memory tracking and assertions, to crash more usefully when
35785 - If the default torrc isn't there, just use some default defaults.
35786 Plus provide an internal dirservers file if they don't have one.
35787 - When the user tries to use Tor as an http proxy, give them an http
35788 501 failure explaining that we're a socks proxy.
35789 - Dump a new router.desc on hup, to help confused people who change
35790 their exit policies and then wonder why router.desc doesn't reflect
35792 - Clean up the generic tor.sh init script that we ship with.
35794 - If the exit stream is pending on the resolve, and a destroy arrives,
35795 then the stream wasn't getting removed from the pending list. I
35796 think this was the one causing recent server crashes.
35797 - Use a more robust poll on OSX 10.3, since their poll is flaky.
35798 - When it couldn't resolve any dirservers, it was useless from then on.
35799 Now it reloads the RouterFile (or default dirservers) if it has no
35801 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
35802 many users don't even *have* a /usr/local/sbin/.
35805 Changes in version 0.0.2pre21 - 2004-02-18
35807 - There's a ChangeLog file that actually reflects the changelog.
35808 - There's a 'torify' wrapper script, with an accompanying
35809 tor-tsocks.conf, that simplifies the process of using tsocks for
35810 tor. It even has a man page.
35811 - The tor binary gets installed to sbin rather than bin now.
35812 - Retry streams where the connected cell hasn't arrived in 15 seconds
35813 - Clean up exit policy handling -- get the default out of the torrc,
35814 so we can update it without forcing each server operator to fix
35816 - Allow imaps and pop3s in default exit policy
35818 - Prevent picking middleman nodes as the last node in the circuit
35821 Changes in version 0.0.2pre20 - 2004-01-30
35823 - We now have a deb package, and it's in debian unstable. Go to
35824 it, apt-getters. :)
35825 - I've split the TotalBandwidth option into BandwidthRate (how many
35826 bytes per second you want to allow, long-term) and
35827 BandwidthBurst (how many bytes you will allow at once before the cap
35828 kicks in). This better token bucket approach lets you, say, set
35829 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
35830 performance while not exceeding your monthly bandwidth quota.
35831 - Push out a tls record's worth of data once you've got it, rather
35832 than waiting until you've read everything waiting to be read. This
35833 may improve performance by pipelining better. We'll see.
35834 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
35835 from failed circuits (if they haven't been connected yet) and attach
35837 - Expire old streams that haven't managed to connect. Some day we'll
35838 have them reattach to new circuits instead.
35841 - Fix several memory leaks that were causing servers to become bloated
35843 - Fix a few very rare assert triggers. A few more remain.
35844 - Setuid to User _before_ complaining about running as root.
35847 Changes in version 0.0.2pre19 - 2004-01-07
35849 - Fix deadlock condition in dns farm. We were telling a child to die by
35850 closing the parent's file descriptor to him. But newer children were
35851 inheriting the open file descriptor from the parent, and since they
35852 weren't closing it, the socket never closed, so the child never read
35853 eof, so he never knew to exit. Similarly, dns workers were holding
35854 open other sockets, leading to all sorts of chaos.
35855 - New cleaner daemon() code for forking and backgrounding.
35856 - If you log to a file, it now prints an entry at the top of the
35857 logfile so you know it's working.
35858 - The onionskin challenge length was 30 bytes longer than necessary.
35859 - Started to patch up the spec so it's not quite so out of date.
35862 Changes in version 0.0.2pre18 - 2004-01-02
35864 - Fix endian issues with the 'integrity' field in the relay header.
35865 - Fix a potential bug where connections in state
35866 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
35869 Changes in version 0.0.2pre17 - 2003-12-30
35871 - Made --debuglogfile (or any second log file, actually) work.
35872 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
35873 adversary could force us into an infinite loop.
35876 - Each onionskin handshake now includes a hash of the computed key,
35877 to prove the server's identity and help perfect forward secrecy.
35878 - Changed cell size from 256 to 512 bytes (working toward compatibility
35880 - Changed cell length to 2 bytes, and moved it to the relay header.
35881 - Implemented end-to-end integrity checking for the payloads of
35883 - Separated streamid from 'recognized' (otherwise circuits will get
35884 messed up when we try to have streams exit from the middle). We
35885 use the integrity-checking to confirm that a cell is addressed to
35887 - Randomize the initial circid and streamid values, so an adversary who
35888 breaks into a node can't learn how many circuits or streams have
35892 Changes in version 0.0.2pre16 - 2003-12-14
35894 - Fixed a bug that made HUP trigger an assert
35895 - Fixed a bug where a circuit that immediately failed wasn't being
35896 counted as a failed circuit in counting retries.
35899 - Now we close the circuit when we get a truncated cell: otherwise we're
35900 open to an anonymity attack where a bad node in the path truncates
35901 the circuit and then we open streams at him.
35902 - Add port ranges to exit policies
35903 - Add a conservative default exit policy
35904 - Warn if you're running tor as root
35905 - on HUP, retry OR connections and close/rebind listeners
35906 - options.EntryNodes: try these nodes first when picking the first node
35907 - options.ExitNodes: if your best choices happen to include any of
35908 your preferred exit nodes, you choose among just those preferred
35910 - options.ExcludedNodes: nodes that are never picked in path building
35913 Changes in version 0.0.2pre15 - 2003-12-03
35914 o Robustness and bugfixes:
35915 - Sometimes clients would cache incorrect DNS resolves, which would
35916 really screw things up.
35917 - An OP that goes offline would slowly leak all its sockets and stop
35919 - A wide variety of bugfixes in exit node selection, exit policy
35920 handling, and processing pending streams when a new circuit is
35922 - Pick nodes for a path only from those the directory says are up
35923 - Choose randomly from all running dirservers, not always the first one
35924 - Increase allowed http header size for directory fetch.
35925 - Stop writing to stderr (if we're daemonized it will be closed).
35926 - Enable -g always, so cores will be more useful to me.
35927 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
35930 - Wrote a man page. It lists commonly used options.
35933 - Change default loglevel to warn.
35934 - Make PidFile default to null rather than littering in your CWD.
35935 - OnionRouter config option is now obsolete. Instead it just checks
35937 - Moved to a single unified torrc file for both clients and servers.
35940 Changes in version 0.0.2pre14 - 2003-11-29
35941 o Robustness and bugfixes:
35942 - Force the admin to make the DataDirectory himself
35943 - to get ownership/permissions right
35944 - so clients no longer make a DataDirectory and then never use it
35945 - fix bug where a client who was offline for 45 minutes would never
35946 pull down a directory again
35947 - fix (or at least hide really well) the dns assert bug that was
35948 causing server crashes
35949 - warnings and improved robustness wrt clockskew for certs
35950 - use the native daemon(3) to daemonize, when available
35951 - exit if bind() fails
35952 - exit if neither socksport nor orport is defined
35953 - include our own tor_timegm (Win32 doesn't have its own)
35954 - bugfix for win32 with lots of connections
35955 - fix minor bias in PRNG
35956 - make dirserver more robust to corrupt cached directory
35959 - Wrote the design document (woo)
35961 o Circuit building and exit policies:
35962 - Circuits no longer try to use nodes that the directory has told them
35964 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
35965 bitcounts (18.0.0.0/8).
35966 - Make AP connections standby for a circuit if no suitable circuit
35967 exists, rather than failing
35968 - Circuits choose exit node based on addr/port, exit policies, and
35969 which AP connections are standing by
35970 - Bump min pathlen from 2 to 3
35971 - Relay end cells have a payload to describe why the stream ended.
35972 - If the stream failed because of exit policy, try again with a new
35974 - Clients have a dns cache to remember resolved addresses.
35975 - Notice more quickly when we have no working circuits
35978 - APPort is now called SocksPort
35979 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
35981 - RecommendedVersions is now a config variable rather than
35982 hardcoded (for dirservers)
35983 - Reloads config on HUP
35984 - Usage info on -h or --help
35985 - If you set User and Group config vars, it'll setu/gid to them.
35988 Changes in version 0.0.2pre13 - 2003-10-19
35989 o General stability:
35990 - SSL_write no longer fails when it returns WANTWRITE and the number
35991 of bytes in the buf has changed by the next SSL_write call.
35992 - Fix segfault fetching directory when network is down
35993 - Fix a variety of minor memory leaks
35994 - Dirservers reload the fingerprints file on HUP, so I don't have
35995 to take down the network when I approve a new router
35996 - Default server config file has explicit Address line to specify fqdn
35999 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
36000 - Make listener connections not ever alloc bufs
36002 o Autoconf improvements:
36003 - don't clobber an external CFLAGS in ./configure
36004 - Make install now works
36005 - create var/lib/tor on make install
36006 - autocreate a tor.sh initscript to help distribs
36007 - autocreate the torrc and sample-server-torrc with correct paths
36009 o Log files and Daemonizing now work:
36010 - If --DebugLogFile is specified, log to it at -l debug
36011 - If --LogFile is specified, use it instead of commandline
36012 - If --RunAsDaemon is set, tor forks and backgrounds on startup