1 This document summarizes new features and bugfixes in each stable
2 release of Tor. If you want to see more detailed descriptions of the
3 changes in each development snapshot, see the ChangeLog file.
5 Changes in version 0.4.4.9 - 2021-06-14
6 Tor 0.4.4.9 fixes several security issues, including a
7 denial-of-service attack against onion service clients, and another
8 denial-of-service attack against relays. Everybody should upgrade to
9 one of 0.3.5.15, 0.4.4.9, 0.4.5.9, or 0.4.6.5.
11 Note that the scheduled end-of-life date for the Tor 0.4.4.x series is
12 June 15. This is therefore the last release in its series. Everybody
13 still running 0.4.4.x should plan to upgrade to 0.4.5.x or later.
15 o Major bugfixes (security, backport from 0.4.6.5):
16 - Don't allow relays to spoof RELAY_END or RELAY_RESOLVED cell on
17 half-closed streams. Previously, clients failed to validate which
18 hop sent these cells: this would allow a relay on a circuit to end
19 a stream that wasn't actually built with it. Fixes bug 40389;
20 bugfix on 0.3.5.1-alpha. This issue is also tracked as TROVE-2021-
21 003 and CVE-2021-34548.
23 o Major bugfixes (security, defense-in-depth, backport from 0.4.6.5):
24 - Detect more failure conditions from the OpenSSL RNG code.
25 Previously, we would detect errors from a missing RNG
26 implementation, but not failures from the RNG code itself.
27 Fortunately, it appears those failures do not happen in practice
28 when Tor is using OpenSSL's default RNG implementation. Fixes bug
29 40390; bugfix on 0.2.8.1-alpha. This issue is also tracked as
30 TROVE-2021-004. Reported by Jann Horn at Google's Project Zero.
32 o Major bugfixes (security, denial of service, backport from 0.4.6.5):
33 - Resist a hashtable-based CPU denial-of-service attack against
34 relays. Previously we used a naive unkeyed hash function to look
35 up circuits in a circuitmux object. An attacker could exploit this
36 to construct circuits with chosen circuit IDs, to create
37 collisions and make the hash table inefficient. Now we use a
38 SipHash construction here instead. Fixes bug 40391; bugfix on
39 0.2.4.4-alpha. This issue is also tracked as TROVE-2021-005 and
40 CVE-2021-34549. Reported by Jann Horn from Google's Project Zero.
41 - Fix an out-of-bounds memory access in v3 onion service descriptor
42 parsing. An attacker could exploit this bug by crafting an onion
43 service descriptor that would crash any client that tried to visit
44 it. Fixes bug 40392; bugfix on 0.3.0.1-alpha. This issue is also
45 tracked as TROVE-2021-006 and CVE-2021-34550. Reported by Sergei
46 Glazunov from Google's Project Zero.
48 o Minor features (compatibility, backport from 0.4.6.4-rc):
49 - Remove an assertion function related to TLS renegotiation. It was
50 used nowhere outside the unit tests, and it was breaking
51 compilation with recent alpha releases of OpenSSL 3.0.0. Closes
54 o Minor features (fallback directory list, backport from 0.4.6.2-alpha):
55 - Regenerate the list of fallback directories to contain a new set
56 of 200 relays. Closes ticket 40265.
58 o Minor features (geoip data):
59 - Update the geoip files to match the IPFire Location Database, as
60 retrieved on 2021/06/10.
62 o Minor bugfixes (channel, DoS, backport from 0.4.6.2-alpha):
63 - Fix a non-fatal BUG() message due to a too-early free of a string,
64 when listing a client connection from the DoS defenses subsystem.
65 Fixes bug 40345; bugfix on 0.4.3.4-rc.
67 o Minor bugfixes (compiler warnings, backport from 0.4.6.3-rc):
68 - Fix an indentation problem that led to a warning from GCC 11.1.1.
69 Fixes bug 40380; bugfix on 0.3.0.1-alpha.
72 Changes in version 0.4.4.8 - 2021-03-16
73 Tor 0.4.4.8 backports fixes for two important denial-of-service bugs
74 in earlier versions of Tor.
76 One of these vulnerabilities (TROVE-2021-001) would allow an attacker
77 who can send directory data to a Tor instance to force that Tor
78 instance to consume huge amounts of CPU. This is easiest to exploit
79 against authorities, since anybody can upload to them, but directory
80 caches could also exploit this vulnerability against relays or clients
81 when they download. The other vulnerability (TROVE-2021-002) only
82 affects directory authorities, and would allow an attacker to remotely
83 crash the authority with an assertion failure. Patches have already
84 been provided to the authority operators, to help ensure
87 We recommend that everybody upgrade to one of the releases that fixes
88 these issues (0.3.5.14, 0.4.4.8, or 0.4.5.7) as they become available
91 This release also updates our GeoIP data source, and fixes a
94 o Major bugfixes (security, denial of service, backport from 0.4.5.7):
95 - Disable the dump_desc() function that we used to dump unparseable
96 information to disk. It was called incorrectly in several places,
97 in a way that could lead to excessive CPU usage. Fixes bug 40286;
98 bugfix on 0.2.2.1-alpha. This bug is also tracked as TROVE-2021-
99 001 and CVE-2021-28089.
100 - Fix a bug in appending detached signatures to a pending consensus
101 document that could be used to crash a directory authority. Fixes
102 bug 40316; bugfix on 0.2.2.6-alpha. Tracked as TROVE-2021-002
105 o Minor features (geoip data, backport from 0.4.5.7):
106 - We have switched geoip data sources. Previously we shipped IP-to-
107 country mappings from Maxmind's GeoLite2, but in 2019 they changed
108 their licensing terms, so we were unable to update them after that
109 point. We now ship geoip files based on the IPFire Location
110 Database instead. (See https://location.ipfire.org/ for more
111 information). This release updates our geoip files to match the
112 IPFire Location Database as retrieved on 2021/03/12. Closes
115 o Removed features (mallinfo deprecated, backport from 0.4.5.7):
116 - Remove mallinfo() usage entirely. Libc 2.33+ now deprecates it.
120 Changes in version 0.4.4.7 - 2021-02-03
121 Tor 0.4.4.7 backports numerous bugfixes from later releases,
122 including one that made v3 onion services more susceptible to
123 denial-of-service attacks, and a feature that makes some kinds of
124 DoS attacks harder to perform.
126 o Major bugfixes (onion service v3, backport from 0.4.5.3-rc):
127 - Stop requiring a live consensus for v3 clients and services, and
128 allow a "reasonably live" consensus instead. This allows v3 onion
129 services to work even if the authorities fail to generate a
130 consensus for more than 2 hours in a row. Fixes bug 40237; bugfix
133 o Major feature (exit, backport from 0.4.5.5-rc):
134 - Re-entry into the network is now denied at the Exit level to all
135 relays' ORPorts and authorities' ORPorts and DirPorts. This change
136 should help mitgate a set of denial-of-service attacks. Closes
139 o Minor feature (build system, backport from 0.4.5.4-rc):
140 - New "make lsp" command to generate the compile_commands.json file
141 used by the ccls language server. The "bear" program is needed for
142 this. Closes ticket 40227.
144 o Minor features (compilation, backport from 0.4.5.2-rc):
145 - Disable deprecation warnings when building with OpenSSL 3.0.0 or
146 later. There are a number of APIs newly deprecated in OpenSSL
147 3.0.0 that Tor still requires. (A later version of Tor will try to
148 stop depending on these APIs.) Closes ticket 40165.
150 o Minor features (crypto, backport from 0.4.5.3-rc):
151 - Fix undefined behavior on our Keccak library. The bug only
152 appeared on platforms with 32-byte CPU cache lines (e.g. armv5tel)
153 and would result in wrong digests. Fixes bug 40210; bugfix on
154 0.2.8.1-alpha. Thanks to Bernhard Übelacker, Arnd Bergmann and
155 weasel for diagnosing this.
157 o Minor bugfixes (compatibility, backport from 0.4.5.1-rc):
158 - Strip '\r' characters when reading text files on Unix platforms.
159 This should resolve an issue where a relay operator migrates a
160 relay from Windows to Unix, but does not change the line ending of
161 Tor's various state files to match the platform, and the CRLF line
162 endings from Windows end up leaking into other files such as the
163 extra-info document. Fixes bug 33781; bugfix on 0.0.9pre5.
165 o Minor bugfixes (compilation, backport from 0.4.5.3-rc):
166 - Fix a compilation warning about unreachable fallthrough
167 annotations when building with "--enable-all-bugs-are-fatal" on
168 some compilers. Fixes bug 40241; bugfix on 0.3.5.4-alpha.
170 o Minor bugfixes (SOCKS5, backport from 0.4.5.3-rc):
171 - Handle partial SOCKS5 messages correctly. Previously, our code
172 would send an incorrect error message if it got a SOCKS5 request
173 that wasn't complete. Fixes bug 40190; bugfix on 0.3.5.1-alpha.
175 o Minor bugfixes (testing, backport from 0.4.5.2-alpha):
176 - Fix the `config/parse_tcp_proxy_line` test so that it works
177 correctly on systems where the DNS provider hijacks invalid
178 queries. Fixes part of bug 40179; bugfix on 0.4.3.1-alpha.
179 - Fix our Python reference-implementation for the v3 onion service
180 handshake so that it works correctly with the version of hashlib
181 provided by Python 3.9. Fixes part of bug 40179; bugfix
183 - Fix the `tortls/openssl/log_one_error` test to work with OpenSSL
184 3.0.0. Fixes bug 40170; bugfix on 0.2.8.1-alpha.
187 Changes in version 0.4.4.6 - 2020-11-12
188 Tor 0.4.4.6 is the second stable release in the 0.4.4.x series. It
189 backports fixes from later releases, including a fix for TROVE-2020-
190 005, a security issue that could be used, under certain cases, by an
191 adversary to observe traffic patterns on a limited number of circuits
192 intended for a different relay.
194 o Major bugfixes (security, backport from 0.4.5.1-alpha):
195 - When completing a channel, relays now check more thoroughly to
196 make sure that it matches any pending circuits before attaching
197 those circuits. Previously, address correctness and Ed25519
198 identities were not checked in this case, but only when extending
199 circuits on an existing channel. Fixes bug 40080; bugfix on
200 0.2.7.2-alpha. Resolves TROVE-2020-005.
202 o Minor features (directory authorities, backport from 0.4.5.1-alpha):
203 - Authorities now list a different set of protocols as required and
204 recommended. These lists have been chosen so that only truly
205 recommended and/or required protocols are included, and so that
206 clients using 0.2.9 or later will continue to work (even though
207 they are not supported), whereas only relays running 0.3.5 or
208 later will meet the requirements. Closes ticket 40162.
209 - Make it possible to specify multiple ConsensusParams torrc lines.
210 Now directory authority operators can for example put the main
211 ConsensusParams config in one torrc file and then add to it from a
212 different torrc file. Closes ticket 40164.
214 o Minor features (subprotocol versions, backport from 0.4.5.1-alpha):
215 - Tor no longer allows subprotocol versions larger than 63.
216 Previously version numbers up to UINT32_MAX were allowed, which
217 significantly complicated our code. Implements proposal 318;
220 o Minor features (tests, v2 onion services, backport from 0.4.5.1-alpha):
221 - Fix a rendezvous cache unit test that was triggering an underflow
222 on the global rend cache allocation. Fixes bug 40125; bugfix
224 - Fix another rendezvous cache unit test that was triggering an
225 underflow on the global rend cache allocation. Fixes bug 40126;
226 bugfix on 0.2.8.1-alpha.
228 o Minor bugfixes (compilation, backport from 0.4.5.1-alpha):
229 - Fix compiler warnings that would occur when building with
230 "--enable-all-bugs-are-fatal" and "--disable-module-relay" at the
231 same time. Fixes bug 40129; bugfix on 0.4.4.1-alpha.
232 - Resolve a compilation warning that could occur in
233 test_connection.c. Fixes bug 40113; bugfix on 0.2.9.3-alpha.
235 o Minor bugfixes (logging, backport from 0.4.5.1-alpha):
236 - Remove a debug logging statement that uselessly spammed the logs.
237 Fixes bug 40135; bugfix on 0.3.5.0-alpha.
239 o Minor bugfixes (relay configuration, crash, backport from 0.4.5.1-alpha):
240 - Avoid a fatal assert() when failing to create a listener
241 connection for an address that was in use. Fixes bug 40073; bugfix
244 o Minor bugfixes (v2 onion services, backport from 0.4.5.1-alpha):
245 - For HSFETCH commands on v2 onion services addresses, check the
246 length of bytes decoded, not the base32 length. Fixes bug 34400;
247 bugfix on 0.4.1.1-alpha. Patch by Neel Chauhan.
250 Changes in version 0.4.4.5 - 2020-09-15
251 Tor 0.4.4.5 is the first stable release in the 0.4.4.x series. This
252 series improves our guard selection algorithms, adds v3 onion balance
253 support, improves the amount of code that can be disabled when running
254 without relay support, and includes numerous small bugfixes and
255 enhancements. It also lays the ground for some IPv6 features that
256 we'll be developing more in the next (0.4.5) series.
258 Per our support policy, we support each stable release series for nine
259 months after its first stable release, or three months after the first
260 stable release of the next series: whichever is longer. This means
261 that 0.4.4.x will be supported until around June 2021--or later, if
262 0.4.5.x is later than anticipated.
264 Note also that support for 0.4.2.x has just ended; support for 0.4.3
265 will continue until Feb 15, 2021. We still plan to continue supporting
266 0.3.5.x, our long-term stable series, until Feb 2022.
268 Below are the changes since 0.4.3.6-rc. For a complete list of changes
269 since 0.4.4.4-rc, see the ChangeLog file.
271 o Major features (Proposal 310, performance + security):
272 - Implements Proposal 310, "Bandaid on guard selection". Proposal
273 310 solves load-balancing issues with older versions of the guard
274 selection algorithm, and improves its security. Under this new
275 algorithm, a newly selected guard never becomes Primary unless all
276 previously sampled guards are unreachable. Implements
277 recommendation from 32088. (Proposal 310 is linked to the CLAPS
278 project researching optimal client location-aware path selections.
279 This project is a collaboration between the UCLouvain Crypto Group,
280 the U.S. Naval Research Laboratory, and Princeton University.)
282 o Major features (fallback directory list):
283 - Replace the 148 fallback directories originally included in Tor
284 0.4.1.4-rc (of which around 105 are still functional) with a list
285 of 144 fallbacks generated in July 2020. Closes ticket 40061.
287 o Major features (IPv6, relay):
288 - Consider IPv6-only EXTEND2 cells valid on relays. Log a protocol
289 warning if the IPv4 or IPv6 address is an internal address, and
290 internal addresses are not allowed. But continue to use the other
291 address, if it is valid. Closes ticket 33817.
292 - If a relay can extend over IPv4 and IPv6, and both addresses are
293 provided, it chooses between them uniformly at random. Closes
295 - Re-use existing IPv6 connections for circuit extends. Closes
297 - Relays may extend circuits over IPv6, if the relay has an IPv6
298 ORPort, and the client supplies the other relay's IPv6 ORPort in
299 the EXTEND2 cell. IPv6 extends will be used by the relay IPv6
300 ORPort self-tests in 33222. Closes ticket 33817.
302 o Major features (v3 onion services):
303 - Allow v3 onion services to act as OnionBalance backend instances,
304 by using the HiddenServiceOnionBalanceInstance torrc option.
307 o Major bugfixes (NSS):
308 - When running with NSS enabled, make sure that NSS knows to expect
309 nonblocking sockets. Previously, we set our TCP sockets as
310 nonblocking, but did not tell NSS, which in turn could lead to
311 unexpected blocking behavior. Fixes bug 40035; bugfix
314 o Major bugfixes (onion services, DoS):
315 - Correct handling of parameters for the onion service DoS defense.
316 Previously, the consensus parameters for the onion service DoS
317 defenses were overwriting the parameters set by the service
318 operator using HiddenServiceEnableIntroDoSDefense. Fixes bug
319 40109; bugfix on 0.4.2.1-alpha.
321 o Major bugfixes (stats, onion services):
322 - Fix a bug where we were undercounting the Tor network's total
323 onion service traffic, by ignoring any traffic originating from
324 clients. Now we count traffic from both clients and services.
325 Fixes bug 40117; bugfix on 0.2.6.2-alpha.
327 o Minor features (security):
328 - Channels using obsolete versions of the Tor link protocol are no
329 longer allowed to circumvent address-canonicity checks. (This is
330 only a minor issue, since such channels have no way to set ed25519
331 keys, and therefore should always be rejected for circuits that
332 specify ed25519 identities.) Closes ticket 40081.
334 o Minor features (bootstrap reporting):
335 - Report more detailed reasons for bootstrap failure when the
336 failure happens due to a TLS error. Previously we would just call
337 these errors "MISC" when they happened during read, and "DONE"
338 when they happened during any other TLS operation. Closes
341 o Minor features (client-only compilation):
342 - Disable more code related to the ext_orport protocol when
343 compiling without support for relay mode. Closes ticket 33368.
344 - Disable more of our self-testing code when support for relay mode
345 is disabled. Closes ticket 33370.
346 - Most server-side DNS code is now disabled when building without
347 support for relay mode. Closes ticket 33366.
349 o Minor features (code safety):
350 - Check for failures of tor_inet_ntop() and tor_inet_ntoa()
351 functions in DNS and IP address processing code, and adjust
352 codepaths to make them less likely to crash entire Tor instances.
353 Resolves issue 33788.
355 o Minor features (continuous integration):
356 - Run unit-test and integration test (Stem, Chutney) jobs with
357 ALL_BUGS_ARE_FATAL macro being enabled on Travis and Appveyor.
358 Resolves ticket 32143.
360 o Minor features (control port):
361 - If a ClientName was specified in ONION_CLIENT_AUTH_ADD for an
362 onion service, display it when we use ONION_CLIENT_AUTH_VIEW.
363 Closes ticket 40089. Patch by Neel Chauhan.
364 - Return a descriptive error message from the 'GETINFO status/fresh-
365 relay-descs' command on the control port. Previously, we returned
366 a generic error of "Error generating descriptor". Closes ticket
367 32873. Patch by Neel Chauhan.
369 o Minor features (defense in depth):
370 - Wipe more data from connection address fields before returning
371 them to the memory heap. Closes ticket 6198.
373 o Minor features (denial-of-service memory limiter):
374 - Allow the user to configure even lower values for the
375 MaxMemInQueues parameter. Relays now enforce a minimum of 64 MB,
376 when previously the minimum was 256 MB. On clients, there is no
377 minimum. Relays and clients will both warn if the value is set so
378 low that Tor is likely to stop working. Closes ticket 24308.
380 o Minor features (developer tooling):
381 - Add a script to help check the alphabetical ordering of option
382 names in the manual page. Closes ticket 33339.
383 - Refrain from listing all .a files that are generated by the Tor
384 build in .gitignore. Add a single wildcard *.a entry that covers
385 all of them for present and future. Closes ticket 33642.
386 - Add a script ("git-install-tools.sh") to install git hooks and
387 helper scripts. Closes ticket 33451.
389 o Minor features (directory authority):
390 - Authorities now recommend the protocol versions that are supported
391 by Tor 0.3.5 and later. (Earlier versions of Tor have been
392 deprecated since January of this year.) This recommendation will
393 cause older clients and relays to give a warning on startup, or
394 when they download a consensus directory. Closes ticket 32696.
396 o Minor features (directory authority, shared random):
397 - Refactor more authority-only parts of the shared-random scheduling
398 code to reside in the dirauth module, and to be disabled when
399 compiling with --disable-module-dirauth. Closes ticket 33436.
401 o Minor features (directory):
402 - Remember the number of bytes we have downloaded for each directory
403 purpose while bootstrapping, and while fully bootstrapped. Log
404 this information as part of the heartbeat message. Closes
407 o Minor features (entry guards):
408 - Reinstate support for GUARD NEW/UP/DOWN control port events.
411 o Minor features (IPv6 support):
412 - Adds IPv6 support to tor_addr_is_valid(). Adds tests for the above
413 changes and tor_addr_is_null(). Closes ticket 33679. Patch
415 - Allow clients and relays to send dual-stack and IPv6-only EXTEND2
416 cells. Parse dual-stack and IPv6-only EXTEND2 cells on relays.
419 o Minor features (linux seccomp2 sandbox, portability):
420 - Allow Tor to build on platforms where it doesn't know how to
421 report which syscall caused the linux seccomp2 sandbox to fail.
422 This change should make the sandbox code more portable to less
423 common Linux architectures. Closes ticket 34382.
424 - Permit the unlinkat() syscall, which some Libc implementations use
425 to implement unlink(). Closes ticket 33346.
427 o Minor features (logging):
428 - When trying to find our own address, add debug-level logging to
429 report the sources of candidate addresses. Closes ticket 32888.
431 o Minor features (onion service client, SOCKS5):
432 - Add 3 new SocksPort ExtendedErrors (F2, F3, F7) that reports back
433 new type of onion service connection failures. The semantics of
434 these error codes are documented in proposal 309. Closes
437 o Minor features (onion service v3):
438 - If a service cannot upload its descriptor(s), log why at INFO
439 level. Closes ticket 33400; bugfix on 0.3.2.1-alpha.
441 o Minor features (python scripts):
442 - Stop assuming that /usr/bin/python exists. Instead of using a
443 hardcoded path in scripts that still use Python 2, use
444 /usr/bin/env, similarly to the scripts that use Python 3. Fixes
445 bug 33192; bugfix on 0.4.2.
447 o Minor features (testing, architecture):
448 - Our test scripts now double-check that subsystem initialization
449 order is consistent with the inter-module dependencies established
450 by our .may_include files. Implements ticket 31634.
451 - Initialize all subsystems at the beginning of our unit test
452 harness, to avoid crashes due to uninitialized subsystems. Follow-
453 up from ticket 33316.
454 - Our "make check" target now runs the unit tests in 8 parallel
455 chunks. Doing this speeds up hardened CI builds by more than a
456 factor of two. Closes ticket 40098.
458 o Minor features (v3 onion services):
459 - Add v3 onion service status to the dumpstats() call which is
460 triggered by a SIGUSR1 signal. Previously, we only did v2 onion
461 services. Closes ticket 24844. Patch by Neel Chauhan.
463 o Minor features (windows):
464 - Add support for console control signals like Ctrl+C in Windows.
465 Closes ticket 34211. Patch from Damon Harris (TheDcoder).
467 o Minor bugfixes (control port, onion service):
468 - Consistently use 'address' in "Invalid v3 address" response to
469 ONION_CLIENT_AUTH commands. Previously, we would sometimes say
470 'addr'. Fixes bug 40005; bugfix on 0.4.3.1-alpha.
472 o Minor bugfixes (correctness, buffers):
473 - Fix a correctness bug that could cause an assertion failure if we
474 ever tried using the buf_move_all() function with an empty input
475 buffer. As far as we know, no released versions of Tor do this.
476 Fixes bug 40076; bugfix on 0.3.3.1-alpha.
478 o Minor bugfixes (directory authorities):
479 - Directory authorities now reject votes that arrive too late. In
480 particular, once an authority has started fetching missing votes,
481 it no longer accepts new votes posted by other authorities. This
482 change helps prevent a consensus split, where only some authorities
483 have the late vote. Fixes bug 4631; bugfix on 0.2.0.5-alpha.
485 o Minor bugfixes (git scripts):
486 - Stop executing the checked-out pre-commit hook from the pre-push
487 hook. Instead, execute the copy in the user's git directory. Fixes
488 bug 33284; bugfix on 0.4.1.1-alpha.
490 o Minor bugfixes (initialization):
491 - Initialize the subsystems in our code in an order more closely
492 corresponding to their dependencies, so that every system is
493 initialized before the ones that (theoretically) depend on it.
494 Fixes bug 33316; bugfix on 0.4.0.1-alpha.
496 o Minor bugfixes (IPv4, relay):
497 - Check for invalid zero IPv4 addresses and ports when sending and
498 receiving extend cells. Fixes bug 33900; bugfix on 0.2.4.8-alpha.
500 o Minor bugfixes (IPv6, relay):
501 - Consider IPv6 addresses when checking if a connection is
502 canonical. In 17604, relays assumed that a remote relay could
503 consider an IPv6 connection canonical, but did not set the
504 canonical flag on their side of the connection. Fixes bug 33899;
505 bugfix on 0.3.1.1-alpha.
506 - Log IPv6 addresses on connections where this relay is the
507 responder. Previously, responding relays would replace the remote
508 IPv6 address with the IPv4 address from the consensus. Fixes bug
509 33899; bugfix on 0.3.1.1-alpha.
511 o Minor bugfixes (linux seccomp2 sandbox):
512 - Fix a regression on sandboxing rules for the openat() syscall. The
513 fix for bug 25440 fixed the problem on systems with glibc >= 2.27
514 but broke with versions of glibc. We now choose a rule based on
515 the glibc version. Patch from Daniel Pinto. Fixes bug 27315;
517 - Makes the seccomp sandbox allow the correct syscall for opendir
518 according to the running glibc version. This fixes crashes when
519 reloading torrc with sandbox enabled when running on glibc 2.15 to
520 2.21 and 2.26. Patch from Daniel Pinto. Fixes bug 40020; bugfix
523 o Minor bugfixes (logging, testing):
524 - Make all of tor's assertion macros support the ALL_BUGS_ARE_FATAL
525 and DISABLE_ASSERTS_IN_UNIT_TESTS debugging modes. (IF_BUG_ONCE()
526 used to log a non-fatal warning, regardless of the debugging
527 mode.) Fixes bug 33917; bugfix on 0.2.9.1-alpha.
528 - Remove surprising empty line in the INFO-level log about circuit
529 build timeout. Fixes bug 33531; bugfix on 0.3.3.1-alpha.
531 o Minor bugfixes (mainloop):
532 - Better guard against growing a buffer past its maximum 2GB in
533 size. Fixes bug 33131; bugfix on 0.3.0.4-rc.
535 o Minor bugfixes (onion service v3 client):
536 - Remove a BUG() warning that could occur naturally. Fixes bug
537 34087; bugfix on 0.3.2.1-alpha.
539 o Minor bugfixes (onion service, logging):
540 - Fix a typo in a log message PublishHidServDescriptors is set to 0.
541 Fixes bug 33779; bugfix on 0.3.2.1-alpha.
543 o Minor bugfixes (onion services v3):
544 - Avoid a non-fatal assertion failure in certain edge-cases when
545 opening an intro circuit as a client. Fixes bug 34084; bugfix
548 o Minor bugfixes (protocol versions):
549 - Sort tor's supported protocol version lists, as recommended by the
550 tor directory specification. Fixes bug 33285; bugfix
553 o Minor bugfixes (rate limiting, bridges, pluggable transports):
554 - On a bridge, treat all connections from an ExtORPort as remote by
555 default for the purposes of rate-limiting. Previously, bridges
556 would treat the connection as local unless they explicitly
557 received a "USERADDR" command. ExtORPort connections still count
558 as local if there is a USERADDR command with an explicit local
559 address. Fixes bug 33747; bugfix on 0.2.5.1-alpha.
561 o Minor bugfixes (refactoring):
562 - Lift circuit_build_times_disabled() out of the
563 circuit_expire_building() loop, to save CPU time when there are
564 many circuits open. Fixes bug 33977; bugfix on 0.3.5.9.
566 o Minor bugfixes (relay, self-testing):
567 - When starting up as a relay, if we haven't been able to verify
568 that we're reachable, only launch reachability tests at most once
569 a minute. Previously, we had been launching tests up to once a
570 second, which was needlessly noisy. Fixes bug 40083; bugfix
573 o Minor bugfixes (relay, usability):
574 - Adjust the rules for when to warn about having too many
575 connections to other relays. Previously we'd tolerate up to 1.5
576 connections per relay on average. Now we tolerate more connections
577 for directory authorities, and raise the number of total
578 connections we need to see before we warn. Fixes bug 33880; bugfix
581 o Minor bugfixes (SOCKS, onion service client):
582 - Detect v3 onion service addresses of the wrong length when
583 returning the F6 ExtendedErrors code. Fixes bug 33873; bugfix
586 o Minor bugfixes (tests):
587 - Fix the behavior of the rend_cache/clean_v2_descs_as_dir when run
588 on its own. Previously, it would exit with an error. Fixes bug
589 40099; bugfix on 0.2.8.1-alpha.
591 o Minor bugfixes (v3 onion services):
592 - Remove a BUG() warning that could trigger in certain unlikely
593 edge-cases. Fixes bug 34086; bugfix on 0.3.2.1-alpha.
594 - Remove a BUG() that was causing a stacktrace when a descriptor
595 changed at an unexpected time. Fixes bug 28992; bugfix
598 o Minor bugfixes (windows):
599 - Fix a bug that prevented Tor from starting if its log file grew
600 above 2GB. Fixes bug 31036; bugfix on 0.2.1.8-alpha.
602 o Code simplification and refactoring:
603 - Define and use a new constant TOR_ADDRPORT_BUF_LEN which is like
604 TOR_ADDR_BUF_LEN but includes enough space for an IP address,
605 brackets, separating colon, and port number. Closes ticket 33956.
606 Patch by Neel Chauhan.
607 - Merge the orconn and ocirc events into the "core" subsystem, which
608 manages or connections and origin circuits. Previously they were
609 isolated in subsystems of their own.
610 - Move LOG_PROTOCOL_WARN to app/config. Resolves a dependency
611 inversion. Closes ticket 33633.
612 - Move the circuit extend code to the relay module. Split the
613 circuit extend function into smaller functions. Closes
615 - Rewrite port_parse_config() to use the default port flags from
616 port_cfg_new(). Closes ticket 32994. Patch by MrSquanchee.
617 - Updated comments in 'scheduler.c' to reflect old code changes, and
618 simplified the scheduler channel state change code. Closes
620 - Refactor configuration parsing to use the new config subsystem
621 code. Closes ticket 33014.
622 - Move a series of functions related to address resolving into their
623 own files. Closes ticket 33789.
626 - Replace most http:// URLs in our code and documentation with
627 https:// URLs. (We have left unchanged the code in src/ext/, and
628 the text in LICENSE.) Closes ticket 31812. Patch from Jeremy Rand.
629 - Document the limitations of using %include on config files with
630 seccomp sandbox enabled. Fixes documentation bug 34133; bugfix on
631 0.3.1.1-alpha. Patch by Daniel Pinto.
634 - Our "check-local" test target no longer tries to use the
635 Coccinelle semantic patching tool parse all the C files. While it
636 is a good idea to try to make sure Coccinelle works on our C
637 before we run a Coccinelle patch, doing so on every test run has
638 proven to be disruptive. You can still run this tool manually with
639 "make check-cocci". Closes ticket 40030.
640 - Remove the ClientAutoIPv6ORPort option. This option attempted to
641 randomly choose between IPv4 and IPv6 for client connections, and
642 wasn't a true implementation of Happy Eyeballs. Often, this option
643 failed on IPv4-only or IPv6-only connections. Closes ticket 32905.
644 Patch by Neel Chauhan.
645 - Stop shipping contrib/dist/rc.subr file, as it is not being used
646 on FreeBSD anymore. Closes issue 31576.
649 - Add a basic IPv6 test to "make test-network". This test only runs
650 when the local machine has an IPv6 stack. Closes ticket 33300.
651 - Add test-network-ipv4 and test-network-ipv6 jobs to the Makefile.
652 These jobs run the IPv4-only and dual-stack chutney flavours from
653 test-network-all. Closes ticket 33280.
654 - Remove a redundant distcheck job. Closes ticket 33194.
655 - Run the test-network-ipv6 Makefile target in the Travis CI IPv6
656 chutney job. This job runs on macOS, so it's a bit slow. Closes
658 - Sort the Travis jobs in order of speed. Putting the slowest jobs
659 first takes full advantage of Travis job concurrency. Closes
661 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
662 previously configured to fast_finish (which requires
663 allow_failure), to speed up the build. Closes ticket 33195.
664 - Test v3 onion services to tor's mixed IPv4 chutney network. And
665 add a mixed IPv6 chutney network. These networks are used in the
666 test-network-all, test-network-ipv4, and test-network-ipv6 make
667 targets. Closes ticket 33334.
668 - Use the "bridges+hs-v23" chutney network flavour in "make test-
669 network". This test requires a recent version of chutney (mid-
670 February 2020). Closes ticket 28208.
671 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
672 tool to produce detailed diagnostic output. Closes ticket 32792.
674 o Deprecated features (onion service v2):
675 - Add a deprecation warning for version 2 onion services. Closes
678 o Documentation (manual page):
679 - Add cross reference links and a table of contents to the HTML tor
680 manual page. Closes ticket 33369. Work by Swati Thacker as part of
681 Google Season of Docs.
682 - Alphabetize the Denial of Service Mitigation Options, Directory
683 Authority Server Options, Hidden Service Options, and Testing
684 Network Options sections of the tor(1) manual page. Closes ticket
685 33275. Work by Swati Thacker as part of Google Season of Docs.
686 - Refrain from mentioning nicknames in manpage section for MyFamily
687 torrc option. Resolves issue 33417.
688 - Updated the options set by TestingTorNetwork in the manual page.
692 Changes in version 0.4.3.5 - 2020-05-15
693 Tor 0.4.3.5 is the first stable release in the 0.4.3.x series. This
694 series adds support for building without relay code enabled, and
695 implements functionality needed for OnionBalance with v3 onion
696 services. It includes significant refactoring of our configuration and
697 controller functionality, and fixes numerous smaller bugs and
700 Per our support policy, we support each stable release series for nine
701 months after its first stable release, or three months after the first
702 stable release of the next series: whichever is longer. This means
703 that 0.4.3.x will be supported until around February 2021--later, if
704 0.4.4.x is later than anticipated.
706 Note also that support for 0.4.1.x is about to end on May 20 of this
707 year; 0.4.2.x will be supported until September 15. We still plan to
708 continue supporting 0.3.5.x, our long-term stable series, until
711 Below are the changes since 0.4.2.6. For a list of only the changes
712 since 0.4.3.4-rc, see the ChangeLog file.
714 o New system requirements:
715 - When building Tor, you now need to have Python 3 in order to run
716 the integration tests. (Python 2 is officially unsupported
717 upstream, as of 1 Jan 2020.) Closes ticket 32608.
719 o Major features (build system):
720 - The relay code can now be disabled using the --disable-module-relay
721 configure option. When this option is set, we also disable the
722 dirauth module. Closes ticket 32123.
723 - When Tor is compiled --disable-module-relay, we also omit the code
724 used to act as a directory cache. Closes ticket 32487.
726 o Major features (directory authority, ed25519):
727 - Add support for banning a relay's ed25519 keys in the approved-
728 routers file. This will help us migrate away from RSA keys in the
729 future. Previously, only RSA keys could be banned in approved-
730 routers. Resolves ticket 22029. Patch by Neel Chauhan.
732 o Major features (onion services):
733 - New control port commands to manage client-side onion service
734 authorization credentials. The ONION_CLIENT_AUTH_ADD command adds
735 a credential, ONION_CLIENT_AUTH_REMOVE deletes a credential, and
736 ONION_CLIENT_AUTH_VIEW lists the credentials. Closes ticket 30381.
737 - Introduce a new SocksPort flag, ExtendedErrors, to support more
738 detailed error codes in information for applications that support
739 them. Closes ticket 30382; implements proposal 304.
741 o Major features (proxy):
742 - In addition to its current supported proxy types (HTTP CONNECT,
743 SOCKS4, and SOCKS5), Tor can now make its OR connections through a
744 HAProxy server. A new torrc option was added to specify the
745 address/port of the server: TCPProxy <protocol> <host>:<port>.
746 Currently the only supported protocol for the option is haproxy.
747 Closes ticket 31518. Patch done by Suphanat Chunhapanya (haxxpop).
749 o Major bugfixes (security, denial-of-service):
750 - Fix a denial-of-service bug that could be used by anyone to
751 consume a bunch of CPU on any Tor relay or authority, or by
752 directories to consume a bunch of CPU on clients or hidden
753 services. Because of the potential for CPU consumption to
754 introduce observable timing patterns, we are treating this as a
755 high-severity security issue. Fixes bug 33119; bugfix on
756 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
757 as TROVE-2020-002 and CVE-2020-10592.
759 o Major bugfixes (circuit padding, memory leak):
760 - Avoid a remotely triggered memory leak in the case that a circuit
761 padding machine is somehow negotiated twice on the same circuit.
762 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
763 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
765 o Major bugfixes (directory authority):
766 - Directory authorities will now send a 503 (not enough bandwidth)
767 code to clients when under bandwidth pressure. Known relays and
768 other authorities will always be answered regardless of the
769 bandwidth situation. Fixes bug 33029; bugfix on 0.1.2.5-alpha.
771 o Major bugfixes (DoS defenses, bridges, pluggable transport):
772 - Fix a bug that was preventing DoS defenses from running on bridges
773 with a pluggable transport. Previously, the DoS subsystem was not
774 given the transport name of the client connection, thus failed to
775 find the GeoIP cache entry for that client address. Fixes bug
776 33491; bugfix on 0.3.3.2-alpha.
778 o Major bugfixes (networking):
779 - Correctly handle IPv6 addresses in SOCKS5 RESOLVE_PTR requests,
780 and accept strings as well as binary addresses. Fixes bug 32315;
781 bugfix on 0.3.5.1-alpha.
783 o Major bugfixes (onion service):
784 - Report HS circuit failure back into the HS subsystem so we take
785 appropriate action with regards to the client introduction point
786 failure cache. This improves reachability of onion services, since
787 now clients notice failing introduction circuits properly. Fixes
788 bug 32020; bugfix on 0.3.2.1-alpha.
790 o Minor feature (heartbeat, onion service):
791 - Add the DoS INTRODUCE2 defenses counter to the heartbeat DoS
792 message. Closes ticket 31371.
794 o Minor feature (sendme, flow control):
795 - Default to sending SENDME version 1 cells. (Clients are already
796 sending these, because of a consensus parameter telling them to do
797 so: this change only affects what clients would do if the
798 consensus didn't contain a recommendation.) Closes ticket 33623.
800 o Minor features (best practices tracker):
801 - Practracker now supports a --regen-overbroad option to regenerate
802 the exceptions file, but only to revise exceptions to be _less_
803 tolerant of best-practices violations. Closes ticket 32372.
805 o Minor features (configuration validation):
806 - Configuration validation can now be done by per-module callbacks,
807 rather than a global validation function. This will let us reduce
808 the size of config.c and some of its more cumbersome functions.
811 o Minor features (configuration):
812 - If a configured hardware crypto accelerator in AccelName is
813 prefixed with "!", Tor now exits when it cannot be found. Closes
815 - We now use flag-driven logic to warn about obsolete configuration
816 fields, so that we can include their names. In 0.4.2, we used a
817 special type, which prevented us from generating good warnings.
818 Implements ticket 32404.
820 o Minor features (configure, build system):
821 - Output a list of enabled/disabled features at the end of the
822 configure process in a pleasing way. Closes ticket 31373.
824 o Minor features (continuous integration):
825 - Run Doxygen Makefile target on Travis, so we can learn about
826 regressions in our internal documentation. Closes ticket 32455.
827 - Stop allowing failures on the Travis CI stem tests job. It looks
828 like all the stem hangs we were seeing before are now fixed.
831 o Minor features (controller):
832 - Add stream isolation data to STREAM event. Closes ticket 19859.
833 - Implement a new GETINFO command to fetch microdescriptor
834 consensus. Closes ticket 31684.
836 o Minor features (debugging, directory system):
837 - Don't crash when we find a non-guard with a guard-fraction value
838 set. Instead, log a bug warning, in an attempt to figure out how
839 this happened. Diagnostic for ticket 32868.
841 o Minor features (defense in depth):
842 - Add additional checks around tor_vasprintf() usage, in case the
843 function returns an error. Patch by Tobias Stoeckmann. Fixes
846 o Minor features (developer tools):
847 - Remove the 0.2.9.x series branches from git scripts (git-merge-
848 forward.sh, git-pull-all.sh, git-push-all.sh, git-setup-dirs.sh).
850 - Add a check_cocci_parse.sh script that checks that new code is
851 parseable by Coccinelle. Add an exceptions file for unparseable
852 files, and run the script from travis CI. Closes ticket 31919.
853 - Call the check_cocci_parse.sh script from a 'check-cocci' Makefile
854 target. Closes ticket 31919.
855 - Add a rename_c_identifiers.py tool to rename a bunch of C
856 identifiers at once, and generate a well-formed commit message
857 describing the change. This should help with refactoring. Closes
859 - Add some scripts in "scripts/coccinelle" to invoke the Coccinelle
860 semantic patching tool with the correct flags. These flags are
861 fairly easy to forget, and these scripts should help us use
862 Coccinelle more effectively in the future. Closes ticket 31705.
864 o Minor features (diagnostic):
865 - Improve assertions and add some memory-poisoning code to try to
866 track down possible causes of a rare crash (32564) in the EWMA
867 code. Closes ticket 33290.
869 o Minor features (directory authorities):
870 - Directory authorities now reject descriptors from relays running
871 Tor versions from the 0.2.9 and 0.4.0 series. The 0.3.5 series is
872 still allowed. Resolves ticket 32672. Patch by Neel Chauhan.
874 o Minor features (Doxygen):
875 - Update Doxygen configuration file to a more recent template (from
876 1.8.15). Closes ticket 32110.
877 - "make doxygen" now works with out-of-tree builds. Closes
879 - Make sure that doxygen outputs documentation for all of our C
880 files. Previously, some were missing @file declarations, causing
881 them to be ignored. Closes ticket 32307.
882 - Our "make doxygen" target now respects --enable-fatal-warnings by
883 default, and does not warn about items that are missing
884 documentation. To warn about missing documentation, run configure
885 with the "--enable-missing-doc-warnings" flag: doing so suspends
886 fatal warnings for doxygen. Closes ticket 32385.
888 o Minor features (git scripts):
889 - Add TOR_EXTRA_CLONE_ARGS to git-setup-dirs.sh for git clone
890 customisation. Closes ticket 32347.
891 - Add git-setup-dirs.sh, which sets up an upstream git repository
892 and worktrees for tor maintainers. Closes ticket 29603.
893 - Add TOR_EXTRA_REMOTE_* to git-setup-dirs.sh for a custom extra
894 remote. Closes ticket 32347.
895 - Call the check_cocci_parse.sh script from the git commit and push
896 hooks. Closes ticket 31919.
897 - Make git-push-all.sh skip unchanged branches when pushing to
898 upstream. The script already skipped unchanged test branches.
900 - Make git-setup-dirs.sh create a master symlink in the worktree
901 directory. Closes ticket 32347.
902 - Skip unmodified source files when doing some existing git hook
903 checks. Related to ticket 31919.
905 o Minor features (IPv6, client):
906 - Make Tor clients tell dual-stack exits that they prefer IPv6
907 connections. This change is equivalent to setting the PreferIPv6
908 flag on SOCKSPorts (and most other listener ports). Tor Browser
909 has been setting this flag for some time, and we want to remove a
910 client distinguisher at exits. Closes ticket 32637.
912 o Minor features (portability, android):
913 - When building for Android, disable some tests that depend on $HOME
914 and/or pwdb, which Android doesn't have. Closes ticket 32825.
915 Patch from Hans-Christoph Steiner.
917 o Minor features (relay modularity):
918 - Split the relay and server pluggable transport config code into
919 separate files in the relay module. Disable this code when the
920 relay module is disabled. Closes part of ticket 32213.
921 - When the relay module is disabled, reject attempts to set the
922 ORPort, DirPort, DirCache, BridgeRelay, ExtORPort, or
923 ServerTransport* options, rather than ignoring the values of these
924 options. Closes part of ticket 32213.
925 - When the relay module is disabled, change the default config so
926 that DirCache is 0, and ClientOnly is 1. Closes ticket 32410.
928 o Minor features (release tools):
929 - Port our ChangeLog formatting and sorting tools to Python 3.
932 o Minor features (testing):
933 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
934 variable to specify a list of space-separated test cases that
935 should not be executed. We will use this to disable certain tests
936 that are failing on Appveyor because of mismatched OpenSSL
937 libraries. Part of ticket 33643.
938 - Detect some common failure cases for test_parseconf.sh in
939 src/test/conf_failures. Closes ticket 32451.
940 - Allow test_parseconf.sh to test expected log outputs for successful
941 configs, as well as failed configs. Closes ticket 32451.
942 - The test_parseconf.sh script now supports result variants for any
943 combination of the optional libraries lzma, nss, and zstd. Closes
945 - When running the unit tests on Android, create temporary files in
946 a subdirectory of /data/local/tmp. Closes ticket 32172. Based on a
947 patch from Hans-Christoph Steiner.
949 o Minor features (usability):
950 - Include more information when failing to parse a configuration
951 value. This should make it easier to tell what's going wrong when
952 a configuration file doesn't parse. Closes ticket 33460.
954 o Minor bugfix (relay, configuration):
955 - Warn if the ContactInfo field is not set, and tell the relay
956 operator that not having a ContactInfo field set might cause their
957 relay to get rejected in the future. Fixes bug 33361; bugfix
960 o Minor bugfixes (bridges):
961 - Lowercase the configured value of BridgeDistribution before adding
962 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
964 o Minor bugfixes (build system):
965 - Fix "make autostyle" for out-of-tree builds. Fixes bug 32370;
966 bugfix on 0.4.1.2-alpha.
968 o Minor bugfixes (compiler compatibility):
969 - Avoid compiler warnings from Clang 10 related to the use of GCC-
970 style "/* falls through */" comments. Both Clang and GCC allow
971 __attribute__((fallthrough)) instead, so that's what we're using
972 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
973 - Fix compilation warnings with GCC 10.0.1. Fixes bug 34077; bugfix
976 o Minor bugfixes (configuration handling):
977 - Make control_event_conf_changed() take in a config_line_t instead
978 of a smartlist of alternating key/value entries. Fixes bug 31531;
979 bugfix on 0.2.3.3-alpha. Patch by Neel Chauhan.
980 - Check for multiplication overflow when parsing memory units inside
981 configuration. Fixes bug 30920; bugfix on 0.0.9rc1.
982 - When dumping the configuration, stop adding a trailing space after
983 the option name when there is no option value. This issue only
984 affects options that accept an empty value or list. (Most options
985 reject empty values, or delete the entire line from the dumped
986 options.) Fixes bug 32352; bugfix on 0.0.9pre6.
987 - Avoid changing the user's value of HardwareAccel as stored by
988 SAVECONF, when AccelName is set but HardwareAccel is not. Fixes
989 bug 32382; bugfix on 0.2.2.1-alpha.
990 - When creating a KeyDirectory with the same location as the
991 DataDirectory (not recommended), respect the DataDirectory's
992 group-readable setting if one has not been set for the
993 KeyDirectory. Fixes bug 27992; bugfix on 0.3.3.1-alpha.
995 o Minor bugfixes (continuous integration):
996 - Remove the buggy and unused mirroring job. Fixes bug 33213; bugfix
999 o Minor bugfixes (controller protocol):
1000 - When receiving "ACTIVE" or "DORMANT" signals on the control port,
1001 report them as SIGNAL events. Previously we would log a bug
1002 warning. Fixes bug 33104; bugfix on 0.4.0.1-alpha.
1004 o Minor bugfixes (controller):
1005 - In routerstatus_has_changed(), check all the fields that are
1006 output over the control port. Fixes bug 20218; bugfix
1009 o Minor bugfixes (developer tools):
1010 - Allow paths starting with ./ in scripts/add_c_file.py. Fixes bug
1011 31336; bugfix on 0.4.1.2-alpha.
1013 o Minor bugfixes (dirauth module):
1014 - Split the dirauth config code into a separate file in the dirauth
1015 module. Disable this code when the dirauth module is disabled.
1016 Closes ticket 32213.
1017 - When the dirauth module is disabled, reject attempts to set the
1018 AuthoritativeDir option, rather than ignoring the value of the
1019 option. Fixes bug 32213; bugfix on 0.3.4.1-alpha.
1021 o Minor bugfixes (embedded Tor):
1022 - When starting Tor any time after the first time in a process,
1023 register the thread in which it is running as the main thread.
1024 Previously, we only did this on Windows, which could lead to bugs
1025 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
1028 o Minor bugfixes (git scripts):
1029 - Avoid sleeping before the last push in git-push-all.sh. Closes
1031 - Forward all unrecognised arguments in git-push-all.sh to git push.
1032 Closes ticket 32216.
1034 o Minor bugfixes (key portability):
1035 - When reading PEM-encoded key data, tolerate CRLF line-endings even
1036 if we are not running on Windows. Previously, non-Windows hosts
1037 would reject these line-endings in certain positions, making
1038 certain key files hard to move from one host to another. Fixes bug
1039 33032; bugfix on 0.3.5.1-alpha.
1041 o Minor bugfixes (logging):
1042 - Stop truncating IPv6 addresses and ports in channel and connection
1043 logs. Fixes bug 33918; bugfix on 0.2.4.4-alpha.
1044 - Flush stderr, stdout, and file logs during shutdown, if supported
1045 by the OS. This change helps make sure that any final logs are
1046 recorded. Fixes bug 33087; bugfix on 0.4.1.6.
1047 - Stop closing stderr and stdout during shutdown. Closing these file
1048 descriptors can hide sanitiser logs. Fixes bug 33087; bugfix
1050 - If we encounter a bug when flushing a buffer to a TLS connection,
1051 only log the bug once per invocation of the Tor process.
1052 Previously we would log with every occurrence, which could cause
1053 us to run out of disk space. Fixes bug 33093; bugfix
1055 - When logging a bug, do not say "Future instances of this warning
1056 will be silenced" unless we are actually going to silence them.
1057 Previously we would say this whenever a BUG() check failed in the
1058 code. Fixes bug 33095; bugfix on 0.4.1.1-alpha.
1060 o Minor bugfixes (onion services v2):
1061 - Move a series of v2 onion service warnings to protocol-warning
1062 level because they can all be triggered remotely by a malformed
1063 request. Fixes bug 32706; bugfix on 0.1.1.14-alpha.
1064 - When sending the INTRO cell for a v2 Onion Service, look at the
1065 failure cache alongside timeout values to check if the intro point
1066 is marked as failed. Previously, we only looked at the relay
1067 timeout values. Fixes bug 25568; bugfix on 0.2.7.3-rc. Patch by
1070 o Minor bugfixes (onion services v3):
1071 - Remove a BUG() warning that would cause a stack trace if an onion
1072 service descriptor was freed while we were waiting for a
1073 rendezvous circuit to complete. Fixes bug 28992; bugfix
1075 - Relax severity of a log message that can appear naturally when
1076 decoding onion service descriptors as a relay. Also add some
1077 diagnostics to debug any future bugs in that area. Fixes bug
1078 31669; bugfix on 0.3.0.1-alpha.
1079 - Fix an assertion failure that could result from a corrupted
1080 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
1081 bugfix on 0.3.3.1-alpha. This issue is also tracked
1083 - Properly handle the client rendezvous circuit timeout. Previously
1084 Tor would sometimes timeout a rendezvous circuit awaiting the
1085 introduction ACK, and find itself unable to re-establish all
1086 circuits because the rendezvous circuit timed out too early. Fixes
1087 bug 32021; bugfix on 0.3.2.1-alpha.
1089 o Minor bugfixes (onion services):
1090 - Do not rely on a "circuit established" flag for intro circuits but
1091 instead always query the HS circuit map. This is to avoid sync
1092 issue with that flag and the map. Fixes bug 32094; bugfix
1095 o Minor bugfixes (onion services, all):
1096 - In cancel_descriptor_fetches(), use
1097 connection_list_by_type_purpose() instead of
1098 connection_list_by_type_state(). Fixes bug 32639; bugfix on
1099 0.3.2.1-alpha. Patch by Neel Chauhan.
1101 o Minor bugfixes (pluggable transports):
1102 - When receiving a message on standard error from a pluggable
1103 transport, log it at info level, rather than as a warning. Fixes
1104 bug 33005; bugfix on 0.4.0.1-alpha.
1106 o Minor bugfixes (rust, build):
1107 - Fix a syntax warning given by newer versions of Rust that was
1108 creating problems for our continuous integration. Fixes bug 33212;
1109 bugfix on 0.3.5.1-alpha.
1111 o Minor bugfixes (scripts):
1112 - Fix update_versions.py for out-of-tree builds. Fixes bug 32371;
1113 bugfix on 0.4.0.1-alpha.
1115 o Minor bugfixes (testing):
1116 - Use the same code to find the tor binary in all of our test
1117 scripts. This change makes sure we are always using the coverage
1118 binary when coverage is enabled. Fixes bug 32368; bugfix
1120 - Stop ignoring "tor --dump-config" errors in test_parseconf.sh.
1121 Fixes bug 32468; bugfix on 0.4.2.1-alpha.
1122 - Our option-validation tests no longer depend on specially
1123 configured non-default, non-passing sets of options. Previously,
1124 the tests had been written to assume that options would _not_ be
1125 set to their defaults, which led to needless complexity and
1126 verbosity. Fixes bug 32175; bugfix on 0.2.8.1-alpha.
1128 o Minor bugfixes (TLS bug handling):
1129 - When encountering a bug in buf_read_from_tls(), return a "MISC"
1130 error code rather than "WANTWRITE". This change might help avoid
1131 some CPU-wasting loops if the bug is ever triggered. Bug reported
1132 by opara. Fixes bug 32673; bugfix on 0.3.0.4-alpha.
1134 o Deprecated features:
1135 - Deprecate the ClientAutoIPv6ORPort option. This option was not
1136 true "Happy Eyeballs", and often failed on connections that
1137 weren't reliably dual-stack. Closes ticket 32942. Patch by
1141 - Provide a quickstart guide for a Circuit Padding Framework, and
1142 documentation for researchers to implement and study circuit
1143 padding machines. Closes ticket 28804.
1144 - Add documentation in 'HelpfulTools.md' to describe how to build a
1145 tag file. Closes ticket 32779.
1146 - Create a high-level description of the long-term software
1147 architecture goals. Closes ticket 32206.
1148 - Describe the --dump-config command in the manual page. Closes
1150 - Unite coding advice from this_not_that.md in torguts repo into our
1151 coding standards document. Resolves ticket 31853.
1154 - Our Doxygen configuration no longer generates LaTeX output. The
1155 reference manual produced by doing this was over 4000 pages long,
1156 and generally unusable. Closes ticket 32099.
1157 - The option "TestingEstimatedDescriptorPropagationTime" is now
1158 marked as obsolete. It has had no effect since 0.3.0.7, when
1159 clients stopped rejecting consensuses "from the future". Closes
1161 - We no longer support consensus methods before method 28; these
1162 methods were only used by authorities running versions of Tor that
1163 are now at end-of-life. In effect, this means that clients,
1164 relays, and authorities now assume that authorities will be
1165 running version 0.3.5.x or later. Closes ticket 32695.
1168 - Avoid conflicts between the fake sockets in tor's unit tests, and
1169 real file descriptors. Resolves issues running unit tests with
1170 GitHub Actions, where the process that embeds or launches the
1171 tests has already opened a large number of file descriptors. Fixes
1172 bug 33782; bugfix on 0.2.8.1-alpha. Found and fixed by
1174 - Add more test cases for tor's UTF-8 validation function. Also,
1175 check the arguments passed to the function for consistency. Closes
1177 - Improve test coverage for relay and dirauth config code, focusing
1178 on option validation and normalization. Closes ticket 32213.
1179 - Improve the consistency of test_parseconf.sh output, and run all
1180 the tests, even if one fails. Closes ticket 32213.
1181 - Run the practracker unit tests in the pre-commit git hook. Closes
1184 o Code simplification and refactoring (channel):
1185 - Channel layer had a variable length cell handler that was not used
1186 and thus removed. Closes ticket 32892.
1188 o Code simplification and refactoring (configuration):
1189 - Immutability is now implemented as a flag on individual
1190 configuration options rather than as part of the option-transition
1191 checking code. Closes ticket 32344.
1192 - Instead of keeping a list of configuration options to check for
1193 relative paths, check all the options whose type is "FILENAME".
1194 Solves part of ticket 32339.
1195 - Our default log (which ordinarily sends NOTICE-level messages to
1196 standard output) is now handled in a more logical manner.
1197 Previously, we replaced the configured log options if they were
1198 empty. Now, we interpret an empty set of log options as meaning
1199 "use the default log". Closes ticket 31999.
1200 - Remove some unused arguments from the options_validate() function,
1201 to simplify our code and tests. Closes ticket 32187.
1202 - Simplify the options_validate() code so that it looks at the
1203 default options directly, rather than taking default options as an
1204 argument. This change lets us simplify its interface. Closes
1206 - Use our new configuration architecture to move most authority-
1207 related options to the directory authority module. Closes
1209 - When parsing the command line, handle options that determine our
1210 "quiet level" and our mode of operation (e.g., --dump-config and
1211 so on) all in one table. Closes ticket 32003.
1213 o Code simplification and refactoring (controller):
1214 - Create a new abstraction for formatting control protocol reply
1215 lines based on key-value pairs. Refactor some existing control
1216 protocol code to take advantage of this. Closes ticket 30984.
1217 - Create a helper function that can fetch network status or
1218 microdesc consensuses. Closes ticket 31684.
1220 o Code simplification and refactoring (dirauth modularization):
1221 - Remove the last remaining HAVE_MODULE_DIRAUTH inside a function.
1222 Closes ticket 32163.
1223 - Replace some confusing identifiers in process_descs.c. Closes
1225 - Simplify some relay and dirauth config code. Closes ticket 32213.
1227 o Code simplification and refactoring (mainloop):
1228 - Simplify the ip_address_changed() function by removing redundant
1229 checks. Closes ticket 33091.
1231 o Code simplification and refactoring (misc):
1232 - Make all the structs we declare follow the same naming convention
1233 of ending with "_t". Closes ticket 32415.
1234 - Move and rename some configuration-related code for clarity.
1235 Closes ticket 32304.
1236 - Our include.am files are now broken up by subdirectory.
1237 Previously, src/core/include.am covered all of the subdirectories
1238 in "core", "feature", and "app". Closes ticket 32137.
1239 - Remove underused NS*() macros from test code: they make our tests
1240 more confusing, especially for code-formatting tools. Closes
1243 o Code simplification and refactoring (relay modularization):
1244 - Disable relay_periodic when the relay module is disabled. Closes
1246 - Disable relay_sys when the relay module is disabled. Closes
1249 o Code simplification and refactoring (tool support):
1250 - Add numerous missing dependencies to our include files, so that
1251 they can be included in different reasonable orders and still
1252 compile. Addresses part of ticket 32764.
1253 - Fix some parts of our code that were difficult for Coccinelle to
1254 parse. Related to ticket 31705.
1255 - Fix some small issues in our code that prevented automatic
1256 formatting tools from working. Addresses part of ticket 32764.
1258 o Documentation (manpage):
1259 - Alphabetize the Server and Directory server sections of the tor
1260 manpage. Also split Statistics options into their own section of
1261 the manpage. Closes ticket 33188. Work by Swati Thacker as part of
1262 Google Season of Docs.
1263 - Document the __OwningControllerProcess torrc option and specify
1264 its polling interval. Resolves issue 32971.
1265 - Split "Circuit Timeout" options and "Node Selection" options into
1266 their own sections of the tor manpage. Closes tickets 32928 and
1267 32929. Work by Swati Thacker as part of Google Season of Docs.
1268 - Alphabetize the Client Options section of the tor manpage. Closes
1270 - Alphabetize the General Options section of the tor manpage. Closes
1272 - In the tor(1) manpage, reword and improve formatting of the
1273 COMMAND-LINE OPTIONS and DESCRIPTION sections. Closes ticket
1274 32277. Based on work by Swati Thacker as part of Google Season
1276 - In the tor(1) manpage, reword and improve formatting of the FILES,
1277 SEE ALSO, and BUGS sections. Closes ticket 32176. Based on work by
1278 Swati Thacker as part of Google Season of Docs.
1280 o Testing (Appveyor CI):
1281 - In our Appveyor Windows CI, copy required DLLs to test and app
1282 directories, before running tor's tests. This ensures that tor.exe
1283 and test*.exe use the correct version of each DLL. This fix is not
1284 required, but we hope it will avoid DLL search issues in future.
1285 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
1286 - On Appveyor, skip the crypto/openssl_version test, which is
1287 failing because of a mismatched library installation. Fix
1290 o Testing (circuit, EWMA):
1291 - Add unit tests for circuitmux and EWMA subsystems. Closes
1294 o Testing (Travis CI):
1295 - Remove a redundant distcheck job. Closes ticket 33194.
1296 - Sort the Travis jobs in order of speed: putting the slowest jobs
1297 first takes full advantage of Travis job concurrency. Closes
1299 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
1300 previously configured to fast_finish (which requires
1301 allow_failure), to speed up the build. Closes ticket 33195.
1302 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
1303 tool to produce detailed diagnostic output. Closes ticket 32792.
1306 Changes in version 0.4.2.7 - 2020-03-18
1307 This is the third stable release in the 0.4.2.x series. It backports
1308 numerous fixes from later releases, including a fix for TROVE-2020-
1309 002, a major denial-of-service vulnerability that affected all
1310 released Tor instances since 0.2.1.5-alpha. Using this vulnerability,
1311 an attacker could cause Tor instances to consume a huge amount of CPU,
1312 disrupting their operations for several seconds or minutes. This
1313 attack could be launched by anybody against a relay, or by a directory
1314 cache against any client that had connected to it. The attacker could
1315 launch this attack as much as they wanted, thereby disrupting service
1316 or creating patterns that could aid in traffic analysis. This issue
1317 was found by OSS-Fuzz, and is also tracked as CVE-2020-10592.
1319 We do not have reason to believe that this attack is currently being
1320 exploited in the wild, but nonetheless we advise everyone to upgrade
1321 as soon as packages are available.
1323 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
1324 - Fix a denial-of-service bug that could be used by anyone to
1325 consume a bunch of CPU on any Tor relay or authority, or by
1326 directories to consume a bunch of CPU on clients or hidden
1327 services. Because of the potential for CPU consumption to
1328 introduce observable timing patterns, we are treating this as a
1329 high-severity security issue. Fixes bug 33119; bugfix on
1330 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
1331 as TROVE-2020-002 and CVE-2020-10592.
1333 o Major bugfixes (circuit padding, memory leak, backport from 0.4.3.3-alpha):
1334 - Avoid a remotely triggered memory leak in the case that a circuit
1335 padding machine is somehow negotiated twice on the same circuit.
1336 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
1337 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
1339 o Major bugfixes (directory authority, backport from 0.4.3.3-alpha):
1340 - Directory authorities will now send a 503 (not enough bandwidth)
1341 code to clients when under bandwidth pressure. Known relays and
1342 other authorities will always be answered regardless of the
1343 bandwidth situation. Fixes bug 33029; bugfix on 0.1.2.5-alpha.
1345 o Minor features (continuous integration, backport from 0.4.3.2-alpha):
1346 - Stop allowing failures on the Travis CI stem tests job. It looks
1347 like all the stem hangs we were seeing before are now fixed.
1348 Closes ticket 33075.
1350 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
1351 - Lowercase the configured value of BridgeDistribution before adding
1352 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
1354 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
1355 - If we encounter a bug when flushing a buffer to a TLS connection,
1356 only log the bug once per invocation of the Tor process.
1357 Previously we would log with every occurrence, which could cause
1358 us to run out of disk space. Fixes bug 33093; bugfix
1361 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
1362 - Fix an assertion failure that could result from a corrupted
1363 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
1364 bugfix on 0.3.3.1-alpha. This issue is also tracked
1367 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
1368 - Fix a syntax warning given by newer versions of Rust that was
1369 creating problems for our continuous integration. Fixes bug 33212;
1370 bugfix on 0.3.5.1-alpha.
1372 o Testing (Travis CI, backport from 0.4.3.3-alpha):
1373 - Remove a redundant distcheck job. Closes ticket 33194.
1374 - Sort the Travis jobs in order of speed: putting the slowest jobs
1375 first takes full advantage of Travis job concurrency. Closes
1377 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
1378 previously configured to fast_finish (which requires
1379 allow_failure), to speed up the build. Closes ticket 33195.
1380 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
1381 tool to produce detailed diagnostic output. Closes ticket 32792.
1384 Changes in version 0.4.1.9 - 2020-03-18
1385 Tor 0.4.1.9 backports important fixes from later Tor releases,
1386 including a fix for TROVE-2020-002, a major denial-of-service
1387 vulnerability that affected all released Tor instances since
1388 0.2.1.5-alpha. Using this vulnerability, an attacker could cause Tor
1389 instances to consume a huge amount of CPU, disrupting their operations
1390 for several seconds or minutes. This attack could be launched by
1391 anybody against a relay, or by a directory cache against any client
1392 that had connected to it. The attacker could launch this attack as
1393 much as they wanted, thereby disrupting service or creating patterns
1394 that could aid in traffic analysis. This issue was found by OSS-Fuzz,
1395 and is also tracked as CVE-2020-10592.
1397 We do not have reason to believe that this attack is currently being
1398 exploited in the wild, but nonetheless we advise everyone to upgrade
1399 as soon as packages are available.
1401 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
1402 - Fix a denial-of-service bug that could be used by anyone to
1403 consume a bunch of CPU on any Tor relay or authority, or by
1404 directories to consume a bunch of CPU on clients or hidden
1405 services. Because of the potential for CPU consumption to
1406 introduce observable timing patterns, we are treating this as a
1407 high-severity security issue. Fixes bug 33119; bugfix on
1408 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
1409 as TROVE-2020-002 and CVE-2020-10592.
1411 o Major bugfixes (circuit padding, memory leak, backport from 0.4.3.3-alpha):
1412 - Avoid a remotely triggered memory leak in the case that a circuit
1413 padding machine is somehow negotiated twice on the same circuit.
1414 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
1415 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
1417 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
1418 - Lowercase the configured value of BridgeDistribution before adding
1419 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
1421 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
1422 - If we encounter a bug when flushing a buffer to a TLS connection,
1423 only log the bug once per invocation of the Tor process.
1424 Previously we would log with every occurrence, which could cause
1425 us to run out of disk space. Fixes bug 33093; bugfix
1428 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
1429 - Fix an assertion failure that could result from a corrupted
1430 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
1431 bugfix on 0.3.3.1-alpha. This issue is also tracked
1434 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
1435 - Fix a syntax warning given by newer versions of Rust that was
1436 creating problems for our continuous integration. Fixes bug 33212;
1437 bugfix on 0.3.5.1-alpha.
1439 o Testing (Travis CI, backport from 0.4.3.3-alpha):
1440 - Remove a redundant distcheck job. Closes ticket 33194.
1441 - Sort the Travis jobs in order of speed: putting the slowest jobs
1442 first takes full advantage of Travis job concurrency. Closes
1444 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
1445 previously configured to fast_finish (which requires
1446 allow_failure), to speed up the build. Closes ticket 33195.
1447 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
1448 tool to produce detailed diagnostic output. Closes ticket 32792.
1451 Changes in version 0.3.5.10 - 2020-03-18
1452 Tor 0.3.5.10 backports many fixes from later Tor releases, including a
1453 fix for TROVE-2020-002, a major denial-of-service vulnerability that
1454 affected all released Tor instances since 0.2.1.5-alpha. Using this
1455 vulnerability, an attacker could cause Tor instances to consume a huge
1456 amount of CPU, disrupting their operations for several seconds or
1457 minutes. This attack could be launched by anybody against a relay, or
1458 by a directory cache against any client that had connected to it. The
1459 attacker could launch this attack as much as they wanted, thereby
1460 disrupting service or creating patterns that could aid in traffic
1461 analysis. This issue was found by OSS-Fuzz, and is also tracked
1464 We do not have reason to believe that this attack is currently being
1465 exploited in the wild, but nonetheless we advise everyone to upgrade
1466 as soon as packages are available.
1468 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
1469 - Fix a denial-of-service bug that could be used by anyone to
1470 consume a bunch of CPU on any Tor relay or authority, or by
1471 directories to consume a bunch of CPU on clients or hidden
1472 services. Because of the potential for CPU consumption to
1473 introduce observable timing patterns, we are treating this as a
1474 high-severity security issue. Fixes bug 33119; bugfix on
1475 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
1476 as TROVE-2020-002 and CVE-2020-10592.
1478 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
1479 - Correct how we use libseccomp. Particularly, stop assuming that
1480 rules are applied in a particular order or that more rules are
1481 processed after the first match. Neither is the case! In
1482 libseccomp <2.4.0 this lead to some rules having no effect.
1483 libseccomp 2.4.0 changed how rules are generated, leading to a
1484 different ordering, which in turn led to a fatal crash during
1485 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
1488 o Minor features (continuous integration, backport from 0.4.3.2-alpha):
1489 - Stop allowing failures on the Travis CI stem tests job. It looks
1490 like all the stem hangs we were seeing before are now fixed.
1491 Closes ticket 33075.
1493 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
1494 - Lowercase the configured value of BridgeDistribution before adding
1495 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
1497 o Minor bugfixes (crash, backport from 0.4.2.4-rc):
1498 - When running Tor with an option like --verify-config or
1499 --dump-config that does not start the event loop, avoid crashing
1500 if we try to exit early because of an error. Fixes bug 32407;
1501 bugfix on 0.3.3.1-alpha.
1503 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
1504 - If we encounter a bug when flushing a buffer to a TLS connection,
1505 only log the bug once per invocation of the Tor process.
1506 Previously we would log with every occurrence, which could cause
1507 us to run out of disk space. Fixes bug 33093; bugfix
1510 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
1511 - Fix an assertion failure that could result from a corrupted
1512 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
1513 bugfix on 0.3.3.1-alpha. This issue is also tracked
1516 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
1517 - Fix a syntax warning given by newer versions of Rust that was
1518 creating problems for our continuous integration. Fixes bug 33212;
1519 bugfix on 0.3.5.1-alpha.
1521 o Testing (backport from 0.4.3.1-alpha):
1522 - Re-enable the Travis CI macOS Chutney build, but don't let it
1523 prevent the Travis job from finishing. (The Travis macOS jobs are
1524 slow, so we don't want to have it delay the whole CI process.)
1525 Closes ticket 32629.
1526 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
1527 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
1528 fix the sandbox errors in 32722. Closes ticket 32240.
1530 o Testing (continuous integration, backport from 0.4.3.1-alpha):
1531 - Use zstd in our Travis Linux builds. Closes ticket 32242.
1533 o Testing (Travis CI, backport from 0.4.3.3-alpha):
1534 - Remove a redundant distcheck job. Closes ticket 33194.
1535 - Sort the Travis jobs in order of speed: putting the slowest jobs
1536 first takes full advantage of Travis job concurrency. Closes
1538 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
1539 previously configured to fast_finish (which requires
1540 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
1541 tool to produce detailed diagnostic output. Closes ticket 32792.
1544 Changes in version 0.4.2.6 - 2020-01-30
1545 This is the second stable release in the 0.4.2.x series. It backports
1546 several bugfixes from 0.4.3.1-alpha, including some that had affected
1547 the Linux seccomp2 sandbox or Windows services. If you're running with
1548 one of those configurations, you'll probably want to upgrade;
1549 otherwise, you should be fine with 0.4.2.5.
1551 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
1552 - Correct how we use libseccomp. Particularly, stop assuming that
1553 rules are applied in a particular order or that more rules are
1554 processed after the first match. Neither is the case! In
1555 libseccomp <2.4.0 this led to some rules having no effect.
1556 libseccomp 2.4.0 changed how rules are generated, leading to a
1557 different ordering, which in turn led to a fatal crash during
1558 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
1560 - Fix crash when reloading logging configuration while the
1561 experimental sandbox is enabled. Fixes bug 32841; bugfix on
1562 0.4.1.7. Patch by Peter Gerber.
1564 o Minor bugfixes (correctness checks, backport from 0.4.3.1-alpha):
1565 - Use GCC/Clang's printf-checking feature to make sure that
1566 tor_assertf() arguments are correctly typed. Fixes bug 32765;
1567 bugfix on 0.4.1.1-alpha.
1569 o Minor bugfixes (logging, crash, backport from 0.4.3.1-alpha):
1570 - Avoid a possible crash when trying to log a (fatal) assertion
1571 failure about mismatched magic numbers in configuration objects.
1572 Fixes bug 32771; bugfix on 0.4.2.1-alpha.
1574 o Minor bugfixes (testing, backport from 0.4.3.1-alpha):
1575 - When TOR_DISABLE_PRACTRACKER is set, do not apply it to the
1576 test_practracker.sh script. Doing so caused a test failure. Fixes
1577 bug 32705; bugfix on 0.4.2.1-alpha.
1578 - When TOR_DISABLE_PRACTRACKER is set, log a notice to stderr when
1579 skipping practracker checks. Fixes bug 32705; bugfix
1582 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
1583 - Initialize the publish/subscribe system when running as a windows
1584 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
1586 o Testing (backport from 0.4.3.1-alpha):
1587 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
1588 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
1589 fix the sandbox errors in 32722. Closes ticket 32240.
1590 - Re-enable the Travis CI macOS Chutney build, but don't let it
1591 prevent the Travis job from finishing. (The Travis macOS jobs are
1592 slow, so we don't want to have it delay the whole CI process.)
1593 Closes ticket 32629.
1595 o Testing (continuous integration, backport from 0.4.3.1-alpha):
1596 - Use zstd in our Travis Linux builds. Closes ticket 32242.
1599 Changes in version 0.4.1.8 - 2020-01-30
1600 This release backports several bugfixes from later release series,
1601 including some that had affected the Linux seccomp2 sandbox or Windows
1602 services. If you're running with one of those configurations, you'll
1603 probably want to upgrade; otherwise, you should be fine with your
1604 current version of 0.4.1.x.
1606 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
1607 - Correct how we use libseccomp. Particularly, stop assuming that
1608 rules are applied in a particular order or that more rules are
1609 processed after the first match. Neither is the case! In
1610 libseccomp <2.4.0 this led to some rules having no effect.
1611 libseccomp 2.4.0 changed how rules are generated, leading to a
1612 different ordering, which in turn led to a fatal crash during
1613 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
1615 - Fix crash when reloading logging configuration while the
1616 experimental sandbox is enabled. Fixes bug 32841; bugfix on
1617 0.4.1.7. Patch by Peter Gerber.
1619 o Minor bugfixes (crash, backport form 0.4.2.4-rc):
1620 - When running Tor with an option like --verify-config or
1621 --dump-config that does not start the event loop, avoid crashing
1622 if we try to exit early because of an error. Fixes bug 32407;
1623 bugfix on 0.3.3.1-alpha.
1625 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
1626 - Initialize the publish/subscribe system when running as a windows
1627 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
1629 o Testing (backport from 0.4.3.1-alpha):
1630 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
1631 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
1632 fix the sandbox errors in 32722. Closes ticket 32240.
1633 - Re-enable the Travis CI macOS Chutney build, but don't let it
1634 prevent the Travis job from finishing. (The Travis macOS jobs are
1635 slow, so we don't want to have it delay the whole CI process.)
1636 Closes ticket 32629.
1638 o Testing (continuous integration, backport from 0.4.3.1-alpha):
1639 - Use zstd in our Travis Linux builds. Closes ticket 32242.
1642 Changes in version 0.4.2.5 - 2019-12-09
1643 This is the first stable release in the 0.4.2.x series. This series
1644 improves reliability and stability, and includes several stability and
1645 correctness improvements for onion services. It also fixes many smaller
1646 bugs present in previous series.
1648 Per our support policy, we will support the 0.4.2.x series for nine
1649 months, or until three months after the release of a stable 0.4.3.x:
1650 whichever is longer. If you need longer-term support, please stick
1651 with 0.3.5.x, which will we plan to support until Feb 2022.
1653 Below are the changes since 0.4.1.4-rc. For a complete list of only
1654 the changes since 0.4.2.4-rc, see the ChangeLog file.
1656 o Major features (directory authorities):
1657 - Directory authorities now reject relays running all currently
1658 deprecated release series. The currently supported release series
1659 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
1661 o Major features (onion service v3, denial of service):
1662 - Add onion service introduction denial of service defenses. Intro
1663 points can now rate-limit client introduction requests, using
1664 parameters that can be sent by the service within the
1665 ESTABLISH_INTRO cell. If the cell extension for this is not used,
1666 the intro point will honor the consensus parameters. Closes
1669 o Major bugfixes (circuit build, guard):
1670 - When considering upgrading circuits from "waiting for guard" to
1671 "open", always ignore circuits that are marked for close.
1672 Previously we could end up in the situation where a subsystem is
1673 notified of a circuit opening, but the circuit is still marked for
1674 close, leading to undesirable behavior. Fixes bug 30871; bugfix
1677 o Major bugfixes (crash, Linux, Android):
1678 - Tolerate systems (including some Android installations) where
1679 madvise and MADV_DONTDUMP are available at build-time, but not at
1680 run time. Previously, these systems would notice a failed syscall
1681 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
1682 - Tolerate systems (including some Linux installations) where
1683 madvise and/or MADV_DONTFORK are available at build-time, but not
1684 at run time. Previously, these systems would notice a failed
1685 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
1687 o Major bugfixes (embedded Tor):
1688 - Avoid a possible crash when restarting Tor in embedded mode and
1689 enabling a different set of publish/subscribe messages. Fixes bug
1690 31898; bugfix on 0.4.1.1-alpha.
1692 o Major bugfixes (relay):
1693 - Relays now respect their AccountingMax bandwidth again. When
1694 relays entered "soft" hibernation (which typically starts when
1695 we've hit 90% of our AccountingMax), we had stopped checking
1696 whether we should enter hard hibernation. Soft hibernation refuses
1697 new connections and new circuits, but the existing circuits can
1698 continue, meaning that relays could have exceeded their configured
1699 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
1701 o Major bugfixes (torrc parsing):
1702 - Stop ignoring torrc options after an %include directive, when the
1703 included directory ends with a file that does not contain any
1704 config options (but does contain comments or whitespace). Fixes
1705 bug 31408; bugfix on 0.3.1.1-alpha.
1707 o Major bugfixes (v3 onion services):
1708 - Onion services now always use the exact number of intro points
1709 configured with the HiddenServiceNumIntroductionPoints option (or
1710 fewer if nodes are excluded). Before, a service could sometimes
1711 pick more intro points than configured. Fixes bug 31548; bugfix
1714 o Minor feature (onion services, control port):
1715 - The ADD_ONION command's keyword "BEST" now defaults to ED25519-V3
1716 (v3) onion services. Previously it defaulted to RSA1024 (v2).
1717 Closes ticket 29669.
1719 o Minor features (auto-formatting scripts):
1720 - When annotating C macros, never generate a line that our check-
1721 spaces script would reject. Closes ticket 31759.
1722 - When annotating C macros, try to remove cases of double-negation.
1723 Closes ticket 31779.
1725 o Minor features (best practices tracker):
1726 - Our best-practices tracker now integrates with our include-checker
1727 tool to keep track of how many layering violations we have not yet
1728 fixed. We hope to reduce this number over time to improve Tor's
1729 modularity. Closes ticket 31176.
1730 - Add a TOR_PRACTRACKER_OPTIONS variable for passing arguments to
1731 practracker from the environment. We may want this for continuous
1732 integration. Closes ticket 31309.
1733 - Give a warning rather than an error when a practracker exception
1734 is violated by a small amount, add a --list-overbroad option to
1735 practracker that lists exceptions that are stricter than they need
1736 to be, and provide an environment variable for disabling
1737 practracker. Closes ticket 30752.
1738 - Our best-practices tracker now looks at headers as well as C
1739 files. Closes ticket 31175.
1741 o Minor features (build system):
1742 - Make pkg-config use --prefix when cross-compiling, if
1743 PKG_CONFIG_PATH is not set. Closes ticket 32191.
1744 - Add --disable-manpage and --disable-html-manual options to
1745 configure script. This will enable shortening build times by not
1746 building documentation. Resolves issue 19381.
1748 o Minor features (compilation):
1749 - Log a more useful error message when we are compiling and one of
1750 the compile-time hardening options we have selected can be linked
1751 but not executed. Closes ticket 27530.
1753 o Minor features (configuration):
1754 - The configuration code has been extended to allow splitting
1755 configuration data across multiple objects. Previously, all
1756 configuration data needed to be kept in a single object, which
1757 tended to become bloated. Closes ticket 31240.
1759 o Minor features (continuous integration):
1760 - When building on Appveyor and Travis, pass the "-k" flag to make,
1761 so that we are informed of all compilation failures, not just the
1762 first one or two. Closes ticket 31372.
1763 - When running CI builds on Travis, put some random data in
1764 ~/.torrc, to make sure no tests are reading the Tor configuration
1765 file from its default location. Resolves issue 30102.
1767 o Minor features (debugging):
1768 - Log a nonfatal assertion failure if we encounter a configuration
1769 line whose command is "CLEAR" but which has a nonempty value. This
1770 should be impossible, according to the rules of our configuration
1771 line parsing. Closes ticket 31529.
1773 o Minor features (geoip):
1774 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
1775 Country database. Closes ticket 32685.
1777 o Minor features (git hooks):
1778 - Our pre-commit git hook now checks for a special file before
1779 running practracker, so that practracker only runs on branches
1780 that are based on master. Since the pre-push hook calls the pre-
1781 commit hook, practracker will also only run before pushes of
1782 branches based on master. Closes ticket 30979.
1784 o Minor features (git scripts):
1785 - Add a "--" command-line argument, to separate git-push-all.sh
1786 script arguments from arguments that are passed through to git
1787 push. Closes ticket 31314.
1788 - Add a -r <remote-name> argument to git-push-all.sh, so the script
1789 can push test branches to a personal remote. Closes ticket 31314.
1790 - Add a -t <test-branch-prefix> argument to git-merge-forward.sh and
1791 git-push-all.sh, which makes these scripts create, merge forward,
1792 and push test branches. Closes ticket 31314.
1793 - Add a -u argument to git-merge-forward.sh, so that the script can
1794 re-use existing test branches after a merge failure and fix.
1795 Closes ticket 31314.
1796 - Add a TOR_GIT_PUSH env var, which sets the default git push
1797 command and arguments for git-push-all.sh. Closes ticket 31314.
1798 - Add a TOR_PUSH_DELAY variable to git-push-all.sh, which makes the
1799 script push master and maint branches with a delay between each
1800 branch. These delays trigger the CI jobs in a set order, which
1801 should show the most likely failures first. Also make pushes
1802 atomic by default, and make the script pass any command-line
1803 arguments to git push. Closes ticket 29879.
1804 - Call the shellcheck script from the pre-commit hook. Closes
1806 - Skip pushing test branches that are the same as a remote
1807 maint/release/master branch in git-push-all.sh by default. Add a
1808 -s argument, so git-push-all.sh can push all test branches. Closes
1811 o Minor features (IPv6, logging):
1812 - Log IPv6 addresses as well as IPv4 addresses when describing
1813 routerinfos, routerstatuses, and nodes. Closes ticket 21003.
1815 o Minor features (maintenance scripts):
1816 - Add a Coccinelle script to detect bugs caused by incrementing or
1817 decrementing a variable inside a call to log_debug(). Since
1818 log_debug() is a macro whose arguments are conditionally
1819 evaluated, it is usually an error to do this. One such bug was
1820 30628, in which SENDME cells were miscounted by a decrement
1821 operator inside a log_debug() call. Closes ticket 30743.
1823 o Minor features (onion service v3):
1824 - Do not allow single hop clients to fetch or post an HS descriptor
1825 from an HSDir. Closes ticket 24964.
1827 o Minor features (onion service):
1828 - Disallow single-hop clients at the introduction point. We've
1829 removed Tor2web support a while back and single-hop rendezvous
1830 attempts are blocked at the relays. This change should remove load
1831 off the network from spammy clients. Close ticket 24963.
1833 o Minor features (onion services v3):
1834 - Assist users who try to setup v2 client authorization in v3 onion
1835 services by pointing them to the right documentation. Closes
1838 o Minor features (stem tests):
1839 - Change "make test-stem" so it only runs the stem tests that use
1840 tor. This change makes test-stem faster and more reliable. Closes
1843 o Minor features (testing):
1844 - When running tests that attempt to look up hostnames, replace the
1845 libc name lookup functions with ones that do not actually touch
1846 the network. This way, the tests complete more quickly in the
1847 presence of a slow or missing DNS resolver. Closes ticket 31841.
1848 - Add a script to invoke "tor --dump-config" and "tor
1849 --verify-config" with various configuration options, and see
1850 whether tor's resulting configuration or error messages are what
1851 we expect. Use it for integration testing of our +Option and
1852 /Option flags. Closes ticket 31637.
1853 - Improve test coverage for our existing configuration parsing and
1854 management API. Closes ticket 30893.
1855 - Add integration tests to make sure that practracker gives the
1856 outputs we expect. Closes ticket 31477.
1857 - The practracker self-tests are now run as part of the Tor test
1858 suite. Closes ticket 31304.
1860 o Minor features (testing, continuous integration):
1861 - Disable all but one Travis CI macOS build, to mitigate slow
1862 scheduling of Travis macOS jobs. Closes ticket 32177.
1863 - Run the chutney IPv6 networks as part of Travis CI. Closes
1865 - Simplify the Travis CI build matrix, and optimise for build time.
1866 Closes ticket 31859.
1867 - Use Windows Server 2019 instead of Windows Server 2016 in our
1868 Appveyor builds. Closes ticket 32086.
1870 o Minor features (token bucket):
1871 - Implement a generic token bucket that uses a single counter, for
1872 use in anti-DoS onion service work. Closes ticket 30687.
1874 o Minor bugfixes (Appveyor continuous integration):
1875 - Avoid spurious errors when Appveyor CI fails before the install
1876 step. Fixes bug 31884; bugfix on 0.3.4.2-alpha.
1878 o Minor bugfixes (best practices tracker):
1879 - Fix a few issues in the best-practices script, including tests,
1880 tab tolerance, error reporting, and directory-exclusion logic.
1881 Fixes bug 29746; bugfix on 0.4.1.1-alpha.
1882 - When running check-best-practices, only consider files in the src
1883 subdirectory. Previously we had recursively considered all
1884 subdirectories, which made us get confused by the temporary
1885 directories made by "make distcheck". Fixes bug 31578; bugfix
1888 o Minor bugfixes (build system):
1889 - Interpret "--disable-module-dirauth=no" correctly. Fixes bug
1890 32124; bugfix on 0.3.4.1-alpha.
1891 - Interpret "--with-tcmalloc=no" correctly. Fixes bug 32124; bugfix
1893 - Stop failing when jemalloc is requested, but tcmalloc is not
1894 found. Fixes bug 32124; bugfix on 0.3.5.1-alpha.
1895 - When pkg-config is not installed, or a library that depends on
1896 pkg-config is not found, tell the user what to do to fix the
1897 problem. Fixes bug 31922; bugfix on 0.3.1.1-alpha.
1898 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
1899 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
1901 o Minor bugfixes (chutney, makefiles, documentation):
1902 - "make test-network-all" now shows the warnings from each test-
1903 network.sh run on the console, so developers see new warnings
1904 early. We've also improved the documentation for this feature, and
1905 renamed a Makefile variable so the code is self-documenting. Fixes
1906 bug 30455; bugfix on 0.3.0.4-rc.
1908 o Minor bugfixes (client, onion service v3):
1909 - Fix a BUG() assertion that occurs within a very small race window
1910 between when a client intro circuit opens and when its descriptor
1911 gets cleaned up from the cache. The circuit is now closed early,
1912 which will trigger a re-fetch of the descriptor and continue the
1913 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
1915 o Minor bugfixes (code quality):
1916 - Fix "make check-includes" so it runs correctly on out-of-tree
1917 builds. Fixes bug 31335; bugfix on 0.3.5.1-alpha.
1919 o Minor bugfixes (compilation):
1920 - Add more stub functions to fix compilation on Android with link-
1921 time optimization when --disable-module-dirauth is used.
1922 Previously, these compilation settings would make the compiler
1923 look for functions that didn't exist. Fixes bug 31552; bugfix
1925 - Suppress spurious float-conversion warnings from GCC when calling
1926 floating-point classifier functions on FreeBSD. Fixes part of bug
1927 31687; bugfix on 0.3.1.5-alpha.
1929 o Minor bugfixes (configuration):
1930 - Invalid floating-point values in the configuration file are now
1931 treated as errors in the configuration. Previously, they were
1932 ignored and treated as zero. Fixes bug 31475; bugfix on 0.0.1.
1934 o Minor bugfixes (connections):
1935 - Avoid trying to read data from closed connections, which can cause
1936 needless loops in Libevent and infinite loops in Shadow. Fixes bug
1937 30344; bugfix on 0.1.1.1-alpha.
1939 o Minor bugfixes (controller protocol):
1940 - Fix the MAPADDRESS controller command to accept one or more
1941 arguments. Previously, it required two or more arguments, and
1942 ignored the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
1944 o Minor bugfixes (coverity):
1945 - Add an assertion when parsing a BEGIN cell so that coverity can be
1946 sure that we are not about to dereference a NULL address. Fixes
1947 bug 31026; bugfix on 0.2.4.7-alpha. This is CID 1447296.
1948 - In our siphash implementation, when building for coverity, use
1949 memcpy in place of a switch statement, so that coverity can tell
1950 we are not accessing out-of-bounds memory. Fixes bug 31025; bugfix
1951 on 0.2.8.1-alpha. This is tracked as CID 1447293 and 1447295.
1952 - Fix several coverity warnings from our unit tests. Fixes bug
1953 31030; bugfix on 0.2.4.1-alpha, 0.3.2.1-alpha, and 0.4.0.1-alpha.
1955 o Minor bugfixes (crash):
1956 - When running Tor with an option like --verify-config or
1957 --dump-config that does not start the event loop, avoid crashing
1958 if we try to exit early because of an error. Fixes bug 32407;
1959 bugfix on 0.3.3.1-alpha.
1961 o Minor bugfixes (developer tooling):
1962 - Only log git script changes in the post-merge script when the
1963 merge was to the master branch. Fixes bug 31040; bugfix
1966 o Minor bugfixes (directory authorities):
1967 - Return a distinct status when formatting annotations fails. Fixes
1968 bug 30780; bugfix on 0.2.0.8-alpha.
1970 o Minor bugfixes (error handling):
1971 - Always lock the backtrace buffer before it is used. Fixes bug
1972 31734; bugfix on 0.2.5.3-alpha.
1973 - On abort, try harder to flush the output buffers of log messages.
1974 On some platforms (macOS), log messages could be discarded when
1975 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1976 - Report the tor version whenever an assertion fails. Previously, we
1977 only reported the Tor version on some crashes, and some non-fatal
1978 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1979 - When tor aborts due to an error, close log file descriptors before
1980 aborting. Closing the logs makes some OSes flush log file buffers,
1981 rather than deleting buffered log lines. Fixes bug 31594; bugfix
1984 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6):
1985 - When extracting an IPv6 address from a PF-based proxy, verify that
1986 we are actually configured to receive an IPv6 address, and log an
1987 internal error if not. Fixes part of bug 31687; bugfix
1990 o Minor bugfixes (git hooks):
1991 - Remove a duplicate call to practracker from the pre-push hook. The
1992 pre-push hook already calls the pre-commit hook, which calls
1993 practracker. Fixes bug 31462; bugfix on 0.4.1.1-alpha.
1995 o Minor bugfixes (git scripts):
1996 - Stop hard-coding the bash path in the git scripts. Some OSes don't
1997 have bash in /usr/bin, others have an ancient bash at this path.
1998 Fixes bug 30840; bugfix on 0.4.0.1-alpha.
1999 - Stop hard-coding the tor master branch name and worktree path in
2000 the git scripts. Fixes bug 30841; bugfix on 0.4.0.1-alpha.
2001 - Allow git-push-all.sh to be run from any directory. Previously,
2002 the script only worked if run from an upstream worktree directory.
2003 Closes ticket 31678.
2005 o Minor bugfixes (guards):
2006 - When tor is missing descriptors for some primary entry guards,
2007 make the log message less alarming. It's normal for descriptors to
2008 expire, as long as tor fetches new ones soon after. Fixes bug
2009 31657; bugfix on 0.3.3.1-alpha.
2011 o Minor bugfixes (ipv6):
2012 - Check for private IPv6 addresses alongside their IPv4 equivalents
2013 when authorities check descriptors. Previously, we only checked
2014 for private IPv4 addresses. Fixes bug 31088; bugfix on
2015 0.2.3.21-rc. Patch by Neel Chauhan.
2016 - When parsing microdescriptors, we should check the IPv6 exit
2017 policy alongside IPv4. Previously, we checked both exit policies
2018 for only router info structures, while microdescriptors were
2019 IPv4-only. Fixes bug 27284; bugfix on 0.2.3.1-alpha. Patch by
2022 o Minor bugfixes (logging):
2023 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
2024 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
2025 - Disable backtrace signal handlers when shutting down tor. Fixes
2026 bug 31614; bugfix on 0.2.5.2-alpha.
2027 - Rate-limit our the logging message about the obsolete .exit
2028 notation. Previously, there was no limit on this warning, which
2029 could potentially be triggered many times by a hostile website.
2030 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
2031 - When initialising log domain masks, only set known log domains.
2032 Fixes bug 31854; bugfix on 0.2.1.1-alpha.
2033 - Change log level of message "Hash of session info was not as
2034 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
2036 - Fix a code issue that would have broken our parsing of log domains
2037 as soon as we had 33 of them. Fortunately, we still only have 29.
2038 Fixes bug 31451; bugfix on 0.4.1.4-rc.
2040 o Minor bugfixes (logging, protocol violations):
2041 - Do not log a nonfatal assertion failure when receiving a VERSIONS
2042 cell on a connection using the obsolete v1 link protocol. Log a
2043 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
2045 o Minor bugfixes (mainloop, periodic events, in-process API):
2046 - Reset the periodic events' "enabled" flag when Tor is shut down
2047 cleanly. Previously, this flag was left on, which caused periodic
2048 events not to be re-enabled when Tor was relaunched in-process
2049 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
2052 o Minor bugfixes (memory management):
2053 - Stop leaking a small amount of memory in nt_service_install(), in
2054 unreachable code. Fixes bug 30799; bugfix on 0.2.0.7-alpha. Patch
2057 o Minor bugfixes (modules):
2058 - Explain what the optional Directory Authority module is, and what
2059 happens when it is disabled. Fixes bug 31825; bugfix
2062 o Minor bugfixes (multithreading):
2063 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
2064 31736; bugfix on 0.0.7.
2066 o Minor bugfixes (networking, IP addresses):
2067 - When parsing addresses via Tor's internal DNS lookup API, reject
2068 IPv4 addresses in square brackets, and accept IPv6 addresses in
2069 square brackets. This change completes the work started in 23082,
2070 making address parsing consistent between tor's internal DNS
2071 lookup and address parsing APIs. Fixes bug 30721; bugfix
2073 - When parsing addresses via Tor's internal address:port parsing and
2074 DNS lookup APIs, require IPv6 addresses with ports to have square
2075 brackets. But allow IPv6 addresses without ports, whether or not
2076 they have square brackets. Fixes bug 30721; bugfix
2079 o Minor bugfixes (onion service v3):
2080 - When purging the client descriptor cache, close any introduction
2081 point circuits associated with purged cache entries. This avoids
2082 picking those circuits later when connecting to the same
2083 introduction points. Fixes bug 30921; bugfix on 0.3.2.1-alpha.
2085 o Minor bugfixes (onion services):
2086 - In the hs_ident_circuit_t data structure, remove the unused field
2087 circuit_type and the respective argument in hs_ident_circuit_new().
2088 This field was set by clients (for introduction) and services (for
2089 introduction and rendezvous) but was never used afterwards. Fixes
2090 bug 31490; bugfix on 0.3.2.1-alpha. Patch by Neel Chauhan.
2092 o Minor bugfixes (operator tools):
2093 - Make tor-print-ed-signing-cert(1) print certificate expiration
2094 date in RFC 1123 and UNIX timestamp formats, to make output
2095 machine readable. Fixes bug 31012; bugfix on 0.3.5.1-alpha.
2097 o Minor bugfixes (process management):
2098 - Remove overly strict assertions that triggered when a pluggable
2099 transport failed to launch. Fixes bug 31091; bugfix
2101 - Remove an assertion in the Unix process backend. This assertion
2102 would trigger when we failed to find the executable for a child
2103 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
2105 o Minor bugfixes (relay):
2106 - Avoid crashing when starting with a corrupt keys directory where
2107 the old ntor key and the new ntor key are identical. Fixes bug
2108 30916; bugfix on 0.2.4.8-alpha.
2110 o Minor bugfixes (rust):
2111 - Correctly exclude a redundant rust build job in Travis. Fixes bug
2112 31463; bugfix on 0.3.5.4-alpha.
2113 - Raise the minimum rustc version to 1.31.0, as checked by configure
2114 and CI. Fixes bug 31442; bugfix on 0.3.5.4-alpha.
2116 o Minor bugfixes (sendme, code structure):
2117 - Rename the trunnel SENDME file definition from sendme.trunnel to
2118 sendme_cell.trunnel to avoid having twice sendme.{c|h} in the
2119 repository. Fixes bug 30769; bugfix on 0.4.1.1-alpha.
2121 o Minor bugfixes (statistics):
2122 - Stop removing the ed25519 signature if the extra info file is too
2123 big. If the signature data was removed, but the keyword was kept,
2124 this could result in an unparseable extra info file. Fixes bug
2125 30958; bugfix on 0.2.7.2-alpha.
2127 o Minor bugfixes (subsystems):
2128 - Make the subsystem init order match the subsystem module
2129 dependencies. Call windows process security APIs as early as
2130 possible. Initialize logging before network and time, so that
2131 network and time can use logging. Fixes bug 31615; bugfix
2134 o Minor bugfixes (testing):
2135 - Avoid intermittent test failures due to a test that had relied on
2136 inconsistent timing sources. Fixes bug 31995; bugfix
2138 - When testing port rebinding, don't busy-wait for tor to log.
2139 Instead, actually sleep for a short time before polling again.
2140 Also improve the formatting of control commands and log messages.
2141 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
2142 - Teach the util/socketpair_ersatz test to work correctly when we
2143 have no network stack configured. Fixes bug 30804; bugfix
2146 o Minor bugfixes (tests, SunOS):
2147 - Avoid a map_anon_nofork test failure due to a signed/unsigned
2148 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
2150 o Minor bugfixes (tls, logging):
2151 - Log bugs about the TLS read buffer's length only once, rather than
2152 filling the logs with similar warnings. Fixes bug 31939; bugfix
2155 o Minor bugfixes (v2 single onion services):
2156 - Always retry v2 single onion service intro and rend circuits with
2157 a 3-hop path. Previously, v2 single onion services used a 3-hop
2158 path when rendezvous circuits were retried after a remote or
2159 delayed failure, but a 1-hop path for immediate retries. Fixes bug
2160 23818; bugfix on 0.2.9.3-alpha.
2162 o Minor bugfixes (v3 onion services):
2163 - When cleaning up intro circuits for a v3 onion service, don't
2164 remove circuits that have an established or pending circuit, even
2165 if they ran out of retries. This way, we don't remove a circuit on
2166 its last retry. Fixes bug 31652; bugfix on 0.3.2.1-alpha.
2168 o Minor bugfixes (v3 single onion services):
2169 - Always retry v3 single onion service intro and rend circuits with
2170 a 3-hop path. Previously, v3 single onion services used a 3-hop
2171 path when rend circuits were retried after a remote or delayed
2172 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
2173 bugfix on 0.3.2.1-alpha.
2174 - Make v3 single onion services fall back to a 3-hop intro, when all
2175 intro points are unreachable via a 1-hop path. Previously, v3
2176 single onion services failed when all intro nodes were unreachable
2177 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
2179 o Code simplification and refactoring:
2180 - Refactor connection_control_process_inbuf() to reduce the size of
2181 a practracker exception. Closes ticket 31840.
2182 - Refactor the microdescs_parse_from_string() function into smaller
2183 pieces, for better comprehensibility. Closes ticket 31675.
2184 - Use SEVERITY_MASK_IDX() to find the LOG_* mask indexes in the unit
2185 tests and fuzzers, rather than using hard-coded values. Closes
2187 - Interface for function `decrypt_desc_layer` cleaned up. Closes
2191 - Correct the description of "GuardLifetime". Fixes bug 31189;
2192 bugfix on 0.3.0.1-alpha.
2193 - Make clear in the man page, in both the bandwidth section and the
2194 AccountingMax section, that Tor counts in powers of two, not
2195 powers of ten: 1 GByte is 1024*1024*1024 bytes, not one billion
2196 bytes. Resolves ticket 32106.
2197 - Document the signal-safe logging behaviour in the tor man page.
2198 Also add some comments to the relevant functions. Closes
2200 - Explain why we can't destroy the backtrace buffer mutex. Explain
2201 why we don't need to destroy the log mutex. Closes ticket 31736.
2202 - The Tor source code repository now includes a (somewhat dated)
2203 description of Tor's modular architecture, in doc/HACKING/design.
2204 This is based on the old "tor-guts.git" repository, which we are
2205 adopting and superseding. Closes ticket 31849.
2206 - Improve documentation in circuit padding subsystem. Patch by
2207 Tobias Pulls. Closes ticket 31113.
2208 - Include an example usage for IPv6 ORPort in our sample torrc.
2209 Closes ticket 31320; patch from Ali Raheem.
2210 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
2211 notice.html so that operators no longer have to host it
2212 themselves. Closes ticket 31089.
2215 - No longer include recommended package digests in votes as detailed
2216 in proposal 301. The RecommendedPackages torrc option is
2217 deprecated and will no longer have any effect. "package" lines
2218 will still be considered when computing consensuses for consensus
2219 methods that include them. (This change has no effect on the list
2220 of recommended Tor versions, which is still in use.) Closes
2222 - Remove torctl.in from contrib/dist directory. Resolves
2226 - Require C99 standards-conforming code in Travis CI, but allow GNU
2227 gcc extensions. Also activates clang's -Wtypedef-redefinition
2228 warnings. Build some jobs with -std=gnu99, and some jobs without.
2229 Closes ticket 32500.
2230 - Run shellcheck for all non-third-party shell scripts that are
2231 shipped with Tor. Closes ticket 29533.
2232 - When checking shell scripts, ignore any user-created directories.
2233 Closes ticket 30967.
2235 o Code simplification and refactoring (config handling):
2236 - Extract our variable manipulation code from confparse.c to a new
2237 lower-level typedvar.h module. Closes ticket 30864.
2238 - Lower another layer of object management from confparse.c to a
2239 more general tool. Now typed structure members are accessible via
2240 an abstract type. Implements ticket 30914.
2241 - Move our backend logic for working with configuration and state
2242 files into a lower-level library, since it no longer depends on
2243 any tor-specific functionality. Closes ticket 31626.
2244 - Numerous simplifications in configuration-handling logic: remove
2245 duplicated macro definitions, replace magical names with flags,
2246 and refactor "TestingTorNetwork" to use the same default-option
2247 logic as the rest of Tor. Closes ticket 30935.
2248 - Replace our ad-hoc set of flags for configuration variables and
2249 configuration variable types with fine-grained orthogonal flags
2250 corresponding to the actual behavior we want. Closes ticket 31625.
2252 o Code simplification and refactoring (misc):
2253 - Eliminate some uses of lower-level control reply abstractions,
2254 primarily in the onion_helper functions. Closes ticket 30889.
2255 - Rework bootstrap tracking to use the new publish-subscribe
2256 subsystem. Closes ticket 29976.
2257 - Rewrite format_node_description() and router_get_verbose_nickname()
2258 to use strlcpy() and strlcat(). The previous implementation used
2259 memcpy() and pointer arithmetic, which was error-prone. Closes
2260 ticket 31545. This is CID 1452819.
2261 - Split extrainfo_dump_to_string() into smaller functions. Closes
2263 - Use the ptrdiff_t type consistently for expressing variable
2264 offsets and pointer differences. Previously we incorrectly (but
2265 harmlessly) used int and sometimes off_t for these cases. Closes
2267 - Use the subsystems mechanism to manage the main event loop code.
2268 Closes ticket 30806.
2269 - Various simplifications and minor improvements to the circuit
2270 padding machines. Patch by Tobias Pulls. Closes tickets 31112
2273 o Documentation (hard-coded directories):
2274 - Improve the documentation for the DirAuthority and FallbackDir
2275 torrc options. Closes ticket 30955.
2277 o Documentation (tor.1 man page):
2278 - Fix typo in tor.1 man page: the option is "--help", not "-help".
2279 Fixes bug 31008; bugfix on 0.2.2.9-alpha.
2281 o Testing (continuous integration):
2282 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
2283 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
2284 until we can fix some Bionic permissions issues (see ticket
2285 32240). Related to ticket 31919.
2286 - Install the mingw OpenSSL package in Appveyor. This makes sure
2287 that the OpenSSL headers and libraries match in Tor's Appveyor
2288 builds. (This bug was triggered by an Appveyor image update.)
2289 Fixes bug 32449; bugfix on 0.3.5.6-rc.
2290 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
2293 Changes in version 0.4.1.7 - 2019-12-09
2294 This release backports several bugfixes to improve stability and
2295 correctness. Anyone experiencing build problems or crashes with 0.4.1.6,
2296 including all relays relying on AccountingMax, should upgrade.
2298 o Major features (directory authorities, backport from 0.4.2.2-alpha):
2299 - Directory authorities now reject relays running all currently
2300 deprecated release series. The currently supported release series
2301 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
2303 o Major bugfixes (embedded Tor, backport from 0.4.2.2-alpha):
2304 - Avoid a possible crash when restarting Tor in embedded mode and
2305 enabling a different set of publish/subscribe messages. Fixes bug
2306 31898; bugfix on 0.4.1.1-alpha.
2308 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
2309 - Relays now respect their AccountingMax bandwidth again. When
2310 relays entered "soft" hibernation (which typically starts when
2311 we've hit 90% of our AccountingMax), we had stopped checking
2312 whether we should enter hard hibernation. Soft hibernation refuses
2313 new connections and new circuits, but the existing circuits can
2314 continue, meaning that relays could have exceeded their configured
2315 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
2317 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
2318 - Stop ignoring torrc options after an %include directive, when the
2319 included directory ends with a file that does not contain any
2320 config options (but does contain comments or whitespace). Fixes
2321 bug 31408; bugfix on 0.3.1.1-alpha.
2323 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
2324 - Onion services now always use the exact number of intro points
2325 configured with the HiddenServiceNumIntroductionPoints option (or
2326 fewer if nodes are excluded). Before, a service could sometimes
2327 pick more intro points than configured. Fixes bug 31548; bugfix
2330 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
2331 - When building on Appveyor and Travis, pass the "-k" flag to make,
2332 so that we are informed of all compilation failures, not just the
2333 first one or two. Closes ticket 31372.
2335 o Minor features (geoip, backport from 0.4.2.5):
2336 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
2337 Country database. Closes ticket 32685.
2339 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
2340 - Avoid spurious errors when Appveyor CI fails before the install step.
2341 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
2343 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
2344 - Fix a BUG() assertion that occurs within a very small race window
2345 between when a client intro circuit opens and when its descriptor
2346 gets cleaned up from the cache. The circuit is now closed early,
2347 which will trigger a re-fetch of the descriptor and continue the
2348 connection. Fixes bug 28970; bugfix on 0.3.2.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 (error handling, backport from 0.4.2.1-alpha):
2356 - On abort, try harder to flush the output buffers of log messages.
2357 On some platforms (macOS), log messages could be discarded when
2358 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
2359 - Report the tor version whenever an assertion fails. Previously, we
2360 only reported the Tor version on some crashes, and some non-fatal
2361 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
2362 - When tor aborts due to an error, close log file descriptors before
2363 aborting. Closing the logs makes some OSes flush log file buffers,
2364 rather than deleting buffered log lines. Fixes bug 31594; bugfix
2367 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
2368 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
2369 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
2370 - Disable backtrace signal handlers when shutting down tor. Fixes
2371 bug 31614; bugfix on 0.2.5.2-alpha.
2372 - Rate-limit our the logging message about the obsolete .exit
2373 notation. Previously, there was no limit on this warning, which
2374 could potentially be triggered many times by a hostile website.
2375 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
2377 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
2378 - Do not log a nonfatal assertion failure when receiving a VERSIONS
2379 cell on a connection using the obsolete v1 link protocol. Log a
2380 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
2382 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
2383 - Reset the periodic events' "enabled" flag when Tor is shut down
2384 cleanly. Previously, this flag was left on, which caused periodic
2385 events not to be re-enabled when Tor was relaunched in-process
2386 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
2389 o Minor bugfixes (multithreading, backport from 0.4.2.2-alpha):
2390 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
2391 31736; bugfix on 0.0.7.
2393 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
2394 - Remove overly strict assertions that triggered when a pluggable
2395 transport failed to launch. Fixes bug 31091; bugfix
2397 - Remove an assertion in the Unix process backend. This assertion
2398 would trigger when we failed to find the executable for a child
2399 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
2401 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
2402 - Avoid crashing when starting with a corrupt keys directory where
2403 the old ntor key and the new ntor key are identical. Fixes bug
2404 30916; bugfix on 0.2.4.8-alpha.
2406 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
2407 - When testing port rebinding, don't busy-wait for tor to log.
2408 Instead, actually sleep for a short time before polling again.
2409 Also improve the formatting of control commands and log messages.
2410 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
2412 o Minor bugfixes (tests, SunOS, backport from 0.4.2.2-alpha):
2413 - Avoid a map_anon_nofork test failure due to a signed/unsigned
2414 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
2416 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
2417 - Log bugs about the TLS read buffer's length only once, rather than
2418 filling the logs with similar warnings. Fixes bug 31939; bugfix
2421 o Documentation (backport from 0.4.2.2-alpha):
2422 - Explain why we can't destroy the backtrace buffer mutex. Explain
2423 why we don't need to destroy the log mutex. Closes ticket 31736.
2425 o Testing (continuous integration, backport from 0.4.2.3-alpha):
2426 - Disable all but one Travis CI macOS build, to mitigate slow
2427 scheduling of Travis macOS jobs. Closes ticket 32177.
2428 - Run the chutney IPv6 networks as part of Travis CI. Closes
2430 - Simplify the Travis CI build matrix, and optimise for build time.
2431 Closes ticket 31859.
2432 - Use Windows Server 2019 instead of Windows Server 2016 in our
2433 Appveyor builds. Closes ticket 32086.
2435 o Testing (continuous integration, backport from 0.4.2.4-rc):
2436 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
2437 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
2438 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
2439 until we can fix some Bionic permissions issues (see ticket
2440 32240). Related to ticket 31919.
2441 - Install the mingw OpenSSL package in Appveyor. This makes sure
2442 that the OpenSSL headers and libraries match in Tor's Appveyor
2443 builds. (This bug was triggered by an Appveyor image update.)
2444 Fixes bug 32449; bugfix on 0.3.5.6-rc.
2446 o Testing (continuous integration, backport from 0.4.2.5):
2447 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
2448 extensions. Also activates clang's -Wtypedef-redefinition warnings.
2449 Build some jobs with -std=gnu99, and some jobs without.
2450 Closes ticket 32500.
2453 Changes in version 0.4.0.6 - 2019-12-09
2454 This is the second stable release in the 0.4.0.x series. This release
2455 backports several bugfixes to improve stability and correctness. Anyone
2456 experiencing build problems or crashes with 0.4.0.5, including all relays
2457 relying on AccountingMax, should upgrade.
2459 Note that, per our support policy, support for the 0.4.0.x series will end
2460 on 2 Feb 2020. Anyone still running 0.4.0.x should plan to upgrade to the
2461 latest stable release, or downgrade to 0.3.5.x, which will get long-term
2462 support until 1 Feb 2022.
2464 o Directory authority changes (backport from 0.4.1.5):
2465 - The directory authority "dizum" has a new IP address. Closes
2468 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
2469 - Consider our directory information to have changed when our list
2470 of bridges changes. Previously, Tor would not re-compute the
2471 status of its directory information when bridges changed, and
2472 therefore would not realize that it was no longer able to build
2473 circuits. Fixes part of bug 29875.
2474 - Do not count previously configured working bridges towards our
2475 total of working bridges. Previously, when Tor's list of bridges
2476 changed, it would think that the old bridges were still usable,
2477 and delay fetching router descriptors for the new ones. Fixes part
2478 of bug 29875; bugfix on 0.3.0.1-alpha.
2480 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
2481 - When considering upgrading circuits from "waiting for guard" to
2482 "open", always ignore circuits that are marked for close. Otherwise,
2483 we can end up in the situation where a subsystem is notified that
2484 a closing circuit has just opened, leading to undesirable
2485 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
2487 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
2488 - Properly clean up the introduction point map when circuits change
2489 purpose from onion service circuits to pathbias, measurement, or
2490 other circuit types. This should fix some service-side instances
2491 of introduction point failure. Fixes bug 29034; bugfix
2494 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
2495 - Fix an unreachable bug in which an introduction point could try to
2496 send an INTRODUCE_ACK with a status code that Trunnel would refuse
2497 to encode, leading the relay to assert(). We've consolidated the
2498 ABI values into Trunnel now. Fixes bug 30454; bugfix
2500 - Clients can now handle unknown status codes from INTRODUCE_ACK
2501 cells. (The NACK behavior will stay the same.) This will allow us
2502 to extend status codes in the future without breaking the normal
2503 client behavior. Fixes another part of bug 30454; bugfix
2506 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
2507 - Relays now respect their AccountingMax bandwidth again. When
2508 relays entered "soft" hibernation (which typically starts when
2509 we've hit 90% of our AccountingMax), we had stopped checking
2510 whether we should enter hard hibernation. Soft hibernation refuses
2511 new connections and new circuits, but the existing circuits can
2512 continue, meaning that relays could have exceeded their configured
2513 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
2515 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
2516 - Stop ignoring torrc options after an %include directive, when the
2517 included directory ends with a file that does not contain any
2518 config options (but does contain comments or whitespace). Fixes
2519 bug 31408; bugfix on 0.3.1.1-alpha.
2521 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
2522 - Onion services now always use the exact number of intro points
2523 configured with the HiddenServiceNumIntroductionPoints option (or
2524 fewer if nodes are excluded). Before, a service could sometimes
2525 pick more intro points than configured. Fixes bug 31548; bugfix
2528 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
2529 - Add a "--list-modules" command to print a list of which compile-
2530 time modules are enabled. Closes ticket 30452.
2532 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
2533 - Remove sudo configuration lines from .travis.yml as they are no
2534 longer needed with current Travis build environment. Resolves
2537 o Minor features (continuous integration, backport from 0.4.1.4-rc):
2538 - Our Travis configuration now uses Chutney to run some network
2539 integration tests automatically. Closes ticket 29280.
2541 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
2542 - When building on Appveyor and Travis, pass the "-k" flag to make,
2543 so that we are informed of all compilation failures, not just the
2544 first one or two. Closes ticket 31372.
2546 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
2547 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
2548 in December 2018 (of which ~122 were still functional), with a
2549 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
2550 in June 2019. Closes ticket 28795.
2552 o Minor features (geoip, backport from 0.4.2.5):
2553 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
2554 Country database. Closes ticket 32685.
2556 o Minor features (stem tests, backport from 0.4.2.1-alpha):
2557 - Change "make test-stem" so it only runs the stem tests that use
2558 tor. This change makes test-stem faster and more reliable. Closes
2561 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
2562 - Avoid spurious errors when Appveyor CI fails before the install step.
2563 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
2565 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
2566 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
2567 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
2569 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
2570 - Fix a logic error that prevented the SessionGroup sub-option from
2571 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
2573 o Minor bugfixes (circuit padding, backport from 0.4.1.4-rc):
2574 - On relays, properly check that a padding machine is absent before
2575 logging a warning about it being absent. Fixes bug 30649; bugfix
2578 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
2579 - Fix a BUG() assertion that occurs within a very small race window
2580 between when a client intro circuit opens and when its descriptor
2581 gets cleaned up from the cache. The circuit is now closed early,
2582 which will trigger a re-fetch of the descriptor and continue the
2583 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
2585 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
2586 - Don't believe clock skew results from NETINFO cells that appear to
2587 arrive before we sent the VERSIONS cells they are responding to.
2588 Previously, we would accept them up to 3 minutes "in the past".
2589 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
2591 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
2592 - Fix a compilation warning on Windows about casting a function
2593 pointer for GetTickCount64(). Fixes bug 31374; bugfix
2596 o Minor bugfixes (compilation, backport from 0.4.1.5):
2597 - Avoid using labs() on time_t, which can cause compilation warnings
2598 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
2600 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
2601 - Suppress spurious float-conversion warnings from GCC when calling
2602 floating-point classifier functions on FreeBSD. Fixes part of bug
2603 31687; bugfix on 0.3.1.5-alpha.
2605 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
2606 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
2607 due to missing declarations of abort(), and prevent other such
2608 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
2610 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
2611 - Fix a bug that prevented us from supporting SOCKS5 proxies that
2612 want authentication along with configured (but unused!)
2613 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
2615 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
2616 - Avoid trying to read data from closed connections, which can cause
2617 needless loops in Libevent and infinite loops in Shadow. Fixes bug
2618 30344; bugfix on 0.1.1.1-alpha.
2620 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
2621 - Allow the test-stem job to fail in Travis, because it sometimes
2622 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
2623 - Skip test_rebind on macOS in Travis, because it is unreliable on
2624 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
2625 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
2626 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
2628 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
2629 - Avoid a set of possible code paths that could try to use freed
2630 memory in routerlist_free() while Tor was exiting. Fixes bug
2631 31003; bugfix on 0.1.2.2-alpha.
2633 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
2634 - Stop crashing after parsing an unknown descriptor purpose
2635 annotation. We think this bug can only be triggered by modifying a
2636 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
2638 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
2639 - Move the "bandwidth-file-headers" line in directory authority
2640 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
2643 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
2644 - On abort, try harder to flush the output buffers of log messages.
2645 On some platforms (macOS), log messages could be discarded when
2646 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
2647 - Report the tor version whenever an assertion fails. Previously, we
2648 only reported the Tor version on some crashes, and some non-fatal
2649 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
2651 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
2652 - When extracting an IPv6 address from a PF-based proxy, verify that
2653 we are actually configured to receive an IPv6 address, and log an
2654 internal error if not. Fixes part of bug 31687; bugfix
2657 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
2658 - When tor is missing descriptors for some primary entry guards,
2659 make the log message less alarming. It's normal for descriptors to
2660 expire, as long as tor fetches new ones soon after. Fixes bug
2661 31657; bugfix on 0.3.3.1-alpha.
2663 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
2664 - Do not log a warning when running with an OpenSSL version other
2665 than the one Tor was compiled with, if the two versions should be
2666 compatible. Previously, we would warn whenever the version was
2667 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
2669 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
2670 - Change log level of message "Hash of session info was not as
2671 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
2674 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
2675 - Rate-limit our the logging message about the obsolete .exit
2676 notation. Previously, there was no limit on this warning, which
2677 could potentially be triggered many times by a hostile website.
2678 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
2680 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
2681 - Do not log a nonfatal assertion failure when receiving a VERSIONS
2682 cell on a connection using the obsolete v1 link protocol. Log a
2683 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
2685 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
2686 - Reset the periodic events' "enabled" flag when Tor is shut down
2687 cleanly. Previously, this flag was left on, which caused periodic
2688 events not to be re-enabled when Tor was relaunched in-process
2689 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
2692 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
2693 - Avoid a minor memory leak that could occur on relays when failing
2694 to create a "keys" directory. Fixes bug 30148; bugfix
2697 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
2698 - Fix a trivial memory leak when parsing an invalid value
2699 from a download schedule in the configuration. Fixes bug
2700 30894; bugfix on 0.3.4.1-alpha.
2702 o Minor bugfixes (NetBSD, backport from 0.4.1.2-alpha):
2703 - Fix usage of minherit() on NetBSD and other platforms that define
2704 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
2705 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
2707 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
2708 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
2709 implemenation) when failing to load an onion service client
2710 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
2712 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
2713 - When purging the DNS cache because of an out-of-memory condition,
2714 try purging just the older entries at first. Previously, we would
2715 always purge the whole thing. Fixes bug 29617; bugfix
2718 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
2719 - Avoid crashing in our tor_vasprintf() implementation on systems
2720 that define neither vasprintf() nor _vscprintf(). (This bug has
2721 been here long enough that we question whether people are running
2722 Tor on such systems, but we're applying the fix out of caution.)
2723 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
2726 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
2727 - Remove overly strict assertions that triggered when a pluggable
2728 transport failed to launch. Fixes bug 31091; bugfix
2730 - Remove an assertion in the Unix process backend. This assertion
2731 would trigger when we failed to find the executable for a child
2732 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
2734 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
2735 - Avoid crashing when starting with a corrupt keys directory where
2736 the old ntor key and the new ntor key are identical. Fixes bug
2737 30916; bugfix on 0.2.4.8-alpha.
2739 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
2740 - Correctly exclude a redundant rust build job in Travis. Fixes bug
2741 31463; bugfix on 0.3.5.4-alpha.
2743 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
2744 - When testing port rebinding, don't busy-wait for tor to log.
2745 Instead, actually sleep for a short time before polling again.
2746 Also improve the formatting of control commands and log messages.
2747 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
2749 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
2750 - Log bugs about the TLS read buffer's length only once, rather than
2751 filling the logs with similar warnings. Fixes bug 31939; bugfix
2754 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
2755 - Always retry v2 single onion service intro and rend circuits with
2756 a 3-hop path. Previously, v2 single onion services used a 3-hop
2757 path when rendezvous circuits were retried after a remote or
2758 delayed failure, but a 1-hop path for immediate retries. Fixes bug
2759 23818; bugfix on 0.2.9.3-alpha.
2760 - Make v3 single onion services fall back to a 3-hop intro, when all
2761 intro points are unreachable via a 1-hop path. Previously, v3
2762 single onion services failed when all intro nodes were unreachable
2763 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
2765 o Documentation (backport from 0.4.2.1-alpha):
2766 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
2767 notice.html so that operators no longer have to host it
2768 themselves. Closes ticket 31089.
2770 o Testing (backport from 0.4.1.2-alpha):
2771 - Specify torrc paths (with empty files) when launching tor in
2772 integration tests; refrain from reading user and system torrcs.
2773 Resolves issue 29702.
2775 o Testing (continuous integration, backport from 0.4.1.1-alpha):
2776 - In Travis, show stem's tor log after failure. Closes ticket 30234.
2778 o Testing (continuous integration, backport from 0.4.1.5):
2779 - In Travis, make stem log a controller trace to the console, and
2780 tail stem's tor log after failure. Closes ticket 30591.
2781 - In Travis, only run the stem tests that use a tor binary. Closes
2784 o Testing (continuous integration, backport from 0.4.2.3-alpha):
2785 - Disable all but one Travis CI macOS build, to mitigate slow
2786 scheduling of Travis macOS jobs. Closes ticket 32177.
2787 - Run the chutney IPv6 networks as part of Travis CI. Closes
2789 - Simplify the Travis CI build matrix, and optimise for build time.
2790 Closes ticket 31859.
2791 - Use Windows Server 2019 instead of Windows Server 2016 in our
2792 Appveyor builds. Closes ticket 32086.
2794 o Testing (continuous integration, backport from 0.4.2.4-rc):
2795 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
2796 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
2797 until we can fix some Bionic permissions issues (see ticket
2798 32240). Related to ticket 31919.
2799 - Install the mingw OpenSSL package in Appveyor. This makes sure
2800 that the OpenSSL headers and libraries match in Tor's Appveyor
2801 builds. (This bug was triggered by an Appveyor image update.)
2802 Fixes bug 32449; bugfix on 0.3.5.6-rc.
2803 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
2805 o Testing (continuous integration, backport from 0.4.2.5):
2806 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
2807 extensions. Also activates clang's -Wtypedef-redefinition warnings.
2808 Build some jobs with -std=gnu99, and some jobs without.
2809 Closes ticket 32500.
2812 Changes in version 0.3.5.9 - 2019-12-09
2813 Tor 0.3.5.9 backports serveral fixes from later releases, including
2814 several that affect bridge users, relay stability, onion services,
2817 o Directory authority changes (backport from 0.4.1.5):
2818 - The directory authority "dizum" has a new IP address. Closes
2821 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
2822 - Consider our directory information to have changed when our list
2823 of bridges changes. Previously, Tor would not re-compute the
2824 status of its directory information when bridges changed, and
2825 therefore would not realize that it was no longer able to build
2826 circuits. Fixes part of bug 29875.
2827 - Do not count previously configured working bridges towards our
2828 total of working bridges. Previously, when Tor's list of bridges
2829 changed, it would think that the old bridges were still usable,
2830 and delay fetching router descriptors for the new ones. Fixes part
2831 of bug 29875; bugfix on 0.3.0.1-alpha.
2833 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
2834 - When considering upgrading circuits from "waiting for guard" to
2835 "open", always ignore circuits that are marked for close. Otherwise,
2836 we can end up in the situation where a subsystem is notified that
2837 a closing circuit has just opened, leading to undesirable
2838 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
2840 o Major bugfixes (NSS, relay, backport from 0.4.0.4-rc):
2841 - When running with NSS, disable TLS 1.2 ciphersuites that use
2842 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
2843 these ciphersuites don't work -- which caused relays to fail to
2844 handshake with one another when these ciphersuites were enabled.
2845 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
2847 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
2848 - Properly clean up the introduction point map when circuits change
2849 purpose from onion service circuits to pathbias, measurement, or
2850 other circuit types. This should fix some service-side instances
2851 of introduction point failure. Fixes bug 29034; bugfix
2854 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
2855 - Fix an unreachable bug in which an introduction point could try to
2856 send an INTRODUCE_ACK with a status code that Trunnel would refuse
2857 to encode, leading the relay to assert(). We've consolidated the
2858 ABI values into Trunnel now. Fixes bug 30454; bugfix
2860 - Clients can now handle unknown status codes from INTRODUCE_ACK
2861 cells. (The NACK behavior will stay the same.) This will allow us
2862 to extend status codes in the future without breaking the normal
2863 client behavior. Fixes another part of bug 30454; bugfix
2866 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
2867 - Stop ignoring torrc options after an %include directive, when the
2868 included directory ends with a file that does not contain any
2869 config options (but does contain comments or whitespace). Fixes
2870 bug 31408; bugfix on 0.3.1.1-alpha.
2872 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
2873 - Onion services now always use the exact number of intro points
2874 configured with the HiddenServiceNumIntroductionPoints option (or
2875 fewer if nodes are excluded). Before, a service could sometimes
2876 pick more intro points than configured. Fixes bug 31548; bugfix
2879 o Minor features (address selection, backport from 0.4.0.3-alpha):
2880 - Treat the subnet 100.64.0.0/10 as public for some purposes;
2881 private for others. This subnet is the RFC 6598 (Carrier Grade
2882 NAT) IP range, and is deployed by many ISPs as an alternative to
2883 RFC 1918 that does not break existing internal networks. Tor now
2884 blocks SOCKS and control ports on these addresses and warns users
2885 if client ports or ExtORPorts are listening on a RFC 6598 address.
2886 Closes ticket 28525. Patch by Neel Chauhan.
2888 o Minor features (bandwidth authority, backport from 0.4.0.4-rc):
2889 - Make bandwidth authorities ignore relays that are reported in the
2890 bandwidth file with the flag "vote=0". This change allows us to
2891 report unmeasured relays for diagnostic reasons without including
2892 their bandwidth in the bandwidth authorities' vote. Closes
2895 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
2896 - Add a "--list-modules" command to print a list of which compile-
2897 time modules are enabled. Closes ticket 30452.
2899 o Minor features (continuous integration, backport from 0.4.0.4-rc):
2900 - On Travis Rust builds, cleanup Rust registry and refrain from
2901 caching the "target/" directory to speed up builds. Resolves
2904 o Minor features (continuous integration, backport from 0.4.0.5):
2905 - In Travis, tell timelimit to use stem's backtrace signals, and
2906 launch python directly from timelimit, so python receives the
2907 signals from timelimit, rather than make. Closes ticket 30117.
2909 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
2910 - Remove sudo configuration lines from .travis.yml as they are no
2911 longer needed with current Travis build environment. Resolves
2914 o Minor features (continuous integration, backport from 0.4.1.4-rc):
2915 - Our Travis configuration now uses Chutney to run some network
2916 integration tests automatically. Closes ticket 29280.
2918 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
2919 - When building on Appveyor and Travis, pass the "-k" flag to make,
2920 so that we are informed of all compilation failures, not just the
2921 first one or two. Closes ticket 31372.
2923 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
2924 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
2925 in December 2018 (of which ~122 were still functional), with a
2926 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
2927 in June 2019. Closes ticket 28795.
2929 o Minor features (geoip, backport from 0.4.2.5):
2930 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
2931 Country database. Closes ticket 32685.
2933 o Minor features (NSS, diagnostic, backport from 0.4.0.4-rc):
2934 - Try to log an error from NSS (if there is any) and a more useful
2935 description of our situation if we are using NSS and a call to
2936 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
2938 o Minor features (stem tests, backport from 0.4.2.1-alpha):
2939 - Change "make test-stem" so it only runs the stem tests that use
2940 tor. This change makes test-stem faster and more reliable. Closes
2943 o Minor bugfixes (security, backport from 0.4.0.4-rc):
2944 - Verify in more places that we are not about to create a buffer
2945 with more than INT_MAX bytes, to avoid possible OOB access in the
2946 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
2947 fixed by Tobias Stoeckmann.
2948 - Fix a potential double free bug when reading huge bandwidth files.
2949 The issue is not exploitable in the current Tor network because
2950 the vulnerable code is only reached when directory authorities
2951 read bandwidth files, but bandwidth files come from a trusted
2952 source (usually the authorities themselves). Furthermore, the
2953 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
2954 which are not used by any of the current authorities. Fixes bug
2955 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
2958 o Minor bugfix (continuous integration, backport from 0.4.0.4-rc):
2959 - Reset coverage state on disk after Travis CI has finished. This
2960 should prevent future coverage merge errors from causing the test
2961 suite for the "process" subsystem to fail. The process subsystem
2962 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
2964 - Terminate test-stem if it takes more than 9.5 minutes to run.
2965 (Travis terminates the job after 10 minutes of no output.)
2966 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
2968 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
2969 - Avoid spurious errors when Appveyor CI fails before the install step.
2970 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
2972 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
2973 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
2974 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
2976 o Minor bugfixes (C correctness, backport from 0.4.0.4-rc):
2977 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
2978 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
2981 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
2982 - Fix a logic error that prevented the SessionGroup sub-option from
2983 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
2985 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
2986 - Fix a BUG() assertion that occurs within a very small race window
2987 between when a client intro circuit opens and when its descriptor
2988 gets cleaned up from the cache. The circuit is now closed early,
2989 which will trigger a re-fetch of the descriptor and continue the
2990 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
2992 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
2993 - Don't believe clock skew results from NETINFO cells that appear to
2994 arrive before we sent the VERSIONS cells they are responding to.
2995 Previously, we would accept them up to 3 minutes "in the past".
2996 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
2998 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
2999 - Fix a compilation warning on Windows about casting a function
3000 pointer for GetTickCount64(). Fixes bug 31374; bugfix
3003 o Minor bugfixes (compilation, backport from 0.4.0.2-alpha):
3004 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
3005 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
3007 o Minor bugfixes (compilation, backport from 0.4.1.5):
3008 - Avoid using labs() on time_t, which can cause compilation warnings
3009 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
3011 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
3012 - Suppress spurious float-conversion warnings from GCC when calling
3013 floating-point classifier functions on FreeBSD. Fixes part of bug
3014 31687; bugfix on 0.3.1.5-alpha.
3016 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
3017 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
3018 due to missing declarations of abort(), and prevent other such
3019 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
3021 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
3022 - Fix a bug that prevented us from supporting SOCKS5 proxies that
3023 want authentication along with configured (but unused!)
3024 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
3026 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
3027 - Avoid trying to read data from closed connections, which can cause
3028 needless loops in Libevent and infinite loops in Shadow. Fixes bug
3029 30344; bugfix on 0.1.1.1-alpha.
3031 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
3032 - Allow the test-stem job to fail in Travis, because it sometimes
3033 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
3034 - Skip test_rebind on macOS in Travis, because it is unreliable on
3035 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3036 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
3037 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3039 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
3040 - Avoid a set of possible code paths that could try to use freed
3041 memory in routerlist_free() while Tor was exiting. Fixes bug
3042 31003; bugfix on 0.1.2.2-alpha.
3044 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
3045 - Stop crashing after parsing an unknown descriptor purpose
3046 annotation. We think this bug can only be triggered by modifying a
3047 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
3049 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
3050 - Move the "bandwidth-file-headers" line in directory authority
3051 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
3054 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
3055 - On abort, try harder to flush the output buffers of log messages.
3056 On some platforms (macOS), log messages could be discarded when
3057 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3058 - Report the tor version whenever an assertion fails. Previously, we
3059 only reported the Tor version on some crashes, and some non-fatal
3060 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
3062 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
3063 - When extracting an IPv6 address from a PF-based proxy, verify that
3064 we are actually configured to receive an IPv6 address, and log an
3065 internal error if not. Fixes part of bug 31687; bugfix
3068 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
3069 - When tor is missing descriptors for some primary entry guards,
3070 make the log message less alarming. It's normal for descriptors to
3071 expire, as long as tor fetches new ones soon after. Fixes bug
3072 31657; bugfix on 0.3.3.1-alpha.
3074 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
3075 - Avoid logging that we are relaxing a circuit timeout when that
3076 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
3078 o Minor bugfixes (logging, backport from 0.4.0.3-alpha):
3079 - Correct a misleading error message when IPv4Only or IPv6Only is
3080 used but the resolved address can not be interpreted as an address
3081 of the specified IP version. Fixes bug 13221; bugfix on
3082 0.2.3.9-alpha. Patch from Kris Katterjohn.
3083 - Log the correct port number for listening sockets when "auto" is
3084 used to let Tor pick the port number. Previously, port 0 was
3085 logged instead of the actual port number. Fixes bug 29144; bugfix
3086 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
3087 - Stop logging a BUG() warning when Tor is waiting for exit
3088 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
3090 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
3091 - Do not log a warning when running with an OpenSSL version other
3092 than the one Tor was compiled with, if the two versions should be
3093 compatible. Previously, we would warn whenever the version was
3094 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
3096 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
3097 - Change log level of message "Hash of session info was not as
3098 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
3101 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
3102 - Rate-limit our the logging message about the obsolete .exit
3103 notation. Previously, there was no limit on this warning, which
3104 could potentially be triggered many times by a hostile website.
3105 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
3107 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
3108 - Do not log a nonfatal assertion failure when receiving a VERSIONS
3109 cell on a connection using the obsolete v1 link protocol. Log a
3110 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
3112 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
3113 - Reset the periodic events' "enabled" flag when Tor is shut down
3114 cleanly. Previously, this flag was left on, which caused periodic
3115 events not to be re-enabled when Tor was relaunched in-process
3116 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
3119 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
3120 - Avoid a minor memory leak that could occur on relays when failing
3121 to create a "keys" directory. Fixes bug 30148; bugfix
3124 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
3125 - Fix a trivial memory leak when parsing an invalid value
3126 from a download schedule in the configuration. Fixes bug
3127 30894; bugfix on 0.3.4.1-alpha.
3129 o Minor bugfixes (memory management, backport from 0.4.0.3-alpha):
3130 - Refactor the shared random state's memory management so that it
3131 actually takes ownership of the shared random value pointers.
3132 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
3134 o Minor bugfixes (memory management, testing, backport from 0.4.0.3-alpha):
3135 - Stop leaking parts of the shared random state in the shared-random
3136 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
3138 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
3139 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
3140 implemenation) when failing to load an onion service client
3141 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
3143 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
3144 - When purging the DNS cache because of an out-of-memory condition,
3145 try purging just the older entries at first. Previously, we would
3146 always purge the whole thing. Fixes bug 29617; bugfix
3149 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
3150 - Avoid crashing in our tor_vasprintf() implementation on systems
3151 that define neither vasprintf() nor _vscprintf(). (This bug has
3152 been here long enough that we question whether people are running
3153 Tor on such systems, but we're applying the fix out of caution.)
3154 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
3157 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
3158 - Avoid crashing when starting with a corrupt keys directory where
3159 the old ntor key and the new ntor key are identical. Fixes bug
3160 30916; bugfix on 0.2.4.8-alpha.
3162 o Minor bugfixes (rust, backport from 0.4.0.5):
3163 - Abort on panic in all build profiles, instead of potentially
3164 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
3166 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
3167 - Correctly exclude a redundant rust build job in Travis. Fixes bug
3168 31463; bugfix on 0.3.5.4-alpha.
3170 o Minor bugfixes (single onion services, backport from 0.4.0.3-alpha):
3171 - Allow connections to single onion services to remain idle without
3172 being disconnected. Previously, relays acting as rendezvous points
3173 for single onion services were mistakenly closing idle rendezvous
3174 circuits after 60 seconds, thinking that they were unused
3175 directory-fetching circuits that had served their purpose. Fixes
3176 bug 29665; bugfix on 0.2.1.26.
3178 o Minor bugfixes (stats, backport from 0.4.0.3-alpha):
3179 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
3180 relay and bridge extra-info documents. Fixes bug 29017; bugfix
3183 o Minor bugfixes (testing, backport from 0.4.0.3-alpha):
3184 - Downgrade some LOG_ERR messages in the address/* tests to
3185 warnings. The LOG_ERR messages were occurring when we had no
3186 configured network. We were failing the unit tests, because we
3187 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
3188 29530; bugfix on 0.3.5.8.
3189 - Fix our gcov wrapper script to look for object files at the
3190 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
3192 o Minor bugfixes (testing, backport from 0.4.0.4-rc):
3193 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
3194 recent test-network.sh to use new chutney features in CI. Fixes
3195 bug 29703; bugfix on 0.2.9.1-alpha.
3196 - Fix a test failure on Windows caused by an unexpected "BUG"
3197 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
3200 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
3201 - When testing port rebinding, don't busy-wait for tor to log.
3202 Instead, actually sleep for a short time before polling again.
3203 Also improve the formatting of control commands and log messages.
3204 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
3206 o Minor bugfixes (TLS protocol, backport form 0.4.0.4-rc):
3207 - When classifying a client's selection of TLS ciphers, if the
3208 client ciphers are not yet available, do not cache the result.
3209 Previously, we had cached the unavailability of the cipher list
3210 and never looked again, which in turn led us to assume that the
3211 client only supported the ancient V1 link protocol. This, in turn,
3212 was causing Stem integration tests to stall in some cases. Fixes
3213 bug 30021; bugfix on 0.2.4.8-alpha.
3215 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
3216 - Log bugs about the TLS read buffer's length only once, rather than
3217 filling the logs with similar warnings. Fixes bug 31939; bugfix
3220 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
3221 - Always retry v2 single onion service intro and rend circuits with
3222 a 3-hop path. Previously, v2 single onion services used a 3-hop
3223 path when rendezvous circuits were retried after a remote or
3224 delayed failure, but a 1-hop path for immediate retries. Fixes bug
3225 23818; bugfix on 0.2.9.3-alpha.
3226 - Make v3 single onion services fall back to a 3-hop intro, when all
3227 intro points are unreachable via a 1-hop path. Previously, v3
3228 single onion services failed when all intro nodes were unreachable
3229 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
3231 o Minor bugfixes (Windows, CI, backport from 0.4.0.3-alpha):
3232 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
3233 Windows Server 2012 R2 job. The remaining 2 jobs still provide
3234 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
3235 fast_finish, so failed jobs terminate the build immediately. Fixes
3236 bug 29601; bugfix on 0.3.5.4-alpha.
3238 o Documentation (backport from 0.4.2.1-alpha):
3239 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
3240 notice.html so that operators no longer have to host it
3241 themselves. Closes ticket 31089.
3243 o Testing (backport from 0.4.1.2-alpha):
3244 - Specify torrc paths (with empty files) when launching tor in
3245 integration tests; refrain from reading user and system torrcs.
3246 Resolves issue 29702.
3248 o Testing (continuous integration, backport from 0.4.1.1-alpha):
3249 - In Travis, show stem's tor log after failure. Closes ticket 30234.
3251 o Testing (continuous integration, backport from 0.4.1.5):
3252 - In Travis, make stem log a controller trace to the console, and
3253 tail stem's tor log after failure. Closes ticket 30591.
3254 - In Travis, only run the stem tests that use a tor binary. Closes
3257 o Testing (continuous integration, backport from 0.4.2.3-alpha):
3258 - Disable all but one Travis CI macOS build, to mitigate slow
3259 scheduling of Travis macOS jobs. Closes ticket 32177.
3260 - Run the chutney IPv6 networks as part of Travis CI. Closes
3262 - Simplify the Travis CI build matrix, and optimise for build time.
3263 Closes ticket 31859.
3264 - Use Windows Server 2019 instead of Windows Server 2016 in our
3265 Appveyor builds. Closes ticket 32086.
3267 o Testing (continuous integration, backport from 0.4.2.4-rc):
3268 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
3269 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
3270 until we can fix some Bionic permissions issues (see ticket
3271 32240). Related to ticket 31919.
3272 - Install the mingw OpenSSL package in Appveyor. This makes sure
3273 that the OpenSSL headers and libraries match in Tor's Appveyor
3274 builds. (This bug was triggered by an Appveyor image update.)
3275 Fixes bug 32449; bugfix on 0.3.5.6-rc.
3276 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
3278 o Testing (continuous integration, backport from 0.4.2.5):
3279 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
3280 extensions. Also activates clang's -Wtypedef-redefinition warnings.
3281 Build some jobs with -std=gnu99, and some jobs without.
3282 Closes ticket 32500.
3285 Changes in version 0.4.1.6 - 2019-09-19
3286 This release backports several bugfixes to improve stability and
3287 correctness. Anyone experiencing build problems or crashes with 0.4.1.5,
3288 or experiencing reliability issues with single onion services, should
3291 o Major bugfixes (crash, Linux, Android, backport from 0.4.2.1-alpha):
3292 - Tolerate systems (including some Android installations) where
3293 madvise and MADV_DONTDUMP are available at build-time, but not at
3294 run time. Previously, these systems would notice a failed syscall
3295 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
3296 - Tolerate systems (including some Linux installations) where
3297 madvise and/or MADV_DONTFORK are available at build-time, but not
3298 at run time. Previously, these systems would notice a failed
3299 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
3301 o Minor features (stem tests, backport from 0.4.2.1-alpha):
3302 - Change "make test-stem" so it only runs the stem tests that use
3303 tor. This change makes test-stem faster and more reliable. Closes
3306 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
3307 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
3308 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
3310 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
3311 - Add more stub functions to fix compilation on Android with link-
3312 time optimization when --disable-module-dirauth is used.
3313 Previously, these compilation settings would make the compiler
3314 look for functions that didn't exist. Fixes bug 31552; bugfix
3316 - Suppress spurious float-conversion warnings from GCC when calling
3317 floating-point classifier functions on FreeBSD. Fixes part of bug
3318 31687; bugfix on 0.3.1.5-alpha.
3320 o Minor bugfixes (controller protocol):
3321 - Fix the MAPADDRESS controller command to accept one or more
3322 arguments. Previously, it required two or more arguments, and ignored
3323 the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
3325 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
3326 - When extracting an IPv6 address from a PF-based proxy, verify that
3327 we are actually configured to receive an IPv6 address, and log an
3328 internal error if not. Fixes part of bug 31687; bugfix
3331 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
3332 - When tor is missing descriptors for some primary entry guards,
3333 make the log message less alarming. It's normal for descriptors to
3334 expire, as long as tor fetches new ones soon after. Fixes bug
3335 31657; bugfix on 0.3.3.1-alpha.
3337 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
3338 - Change log level of message "Hash of session info was not as
3339 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
3342 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
3343 - Correctly exclude a redundant rust build job in Travis. Fixes bug
3344 31463; bugfix on 0.3.5.4-alpha.
3346 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
3347 - Always retry v2 single onion service intro and rend circuits with
3348 a 3-hop path. Previously, v2 single onion services used a 3-hop
3349 path when rendezvous circuits were retried after a remote or
3350 delayed failure, but a 1-hop path for immediate retries. Fixes bug
3351 23818; bugfix on 0.2.9.3-alpha.
3353 o Minor bugfixes (v3 single onion services, backport from 0.4.2.1-alpha):
3354 - Always retry v3 single onion service intro and rend circuits with
3355 a 3-hop path. Previously, v3 single onion services used a 3-hop
3356 path when rend circuits were retried after a remote or delayed
3357 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
3358 bugfix on 0.3.2.1-alpha.
3359 - Make v3 single onion services fall back to a 3-hop intro, when all
3360 intro points are unreachable via a 1-hop path. Previously, v3
3361 single onion services failed when all intro nodes were unreachable
3362 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
3364 o Documentation (backport from 0.4.2.1-alpha):
3365 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
3366 notice.html so that operators no longer have to host it
3367 themselves. Closes ticket 31089.
3370 Changes in version 0.4.1.5 - 2019-08-20
3371 This is the first stable release in the 0.4.1.x series. This series
3372 adds experimental circuit-level padding, authenticated SENDME cells to
3373 defend against certain attacks, and several performance improvements
3374 to save on CPU consumption. It fixes bugs in bootstrapping and v3
3375 onion services. It also includes numerous smaller features and
3376 bugfixes on earlier versions.
3378 Per our support policy, we will support the 0.4.1.x series for nine
3379 months, or until three months after the release of a stable 0.4.2.x:
3380 whichever is longer. If you need longer-term support, please stick
3381 with 0.3.5.x, which will we plan to support until Feb 2022.
3383 Below are the changes since 0.4.0.5. For a list of only the changes
3384 since 0.4.1.4-rc, see the ChangeLog file.
3386 o Directory authority changes:
3387 - The directory authority "dizum" has a new IP address. Closes
3390 o Major features (circuit padding):
3391 - Onion service clients now add padding cells at the start of their
3392 INTRODUCE and RENDEZVOUS circuits, to make those circuits' traffic
3393 look more like general purpose Exit traffic. The overhead for this
3394 is 2 extra cells in each direction for RENDEZVOUS circuits, and 1
3395 extra upstream cell and 10 downstream cells for INTRODUCE
3396 circuits. This feature is only enabled when also supported by the
3397 circuit's middle node. (Clients may specify fixed middle nodes
3398 with the MiddleNodes option, and may force-disable this feature
3399 with the CircuitPadding option.) Closes ticket 28634.
3401 o Major features (code organization):
3402 - Tor now includes a generic publish-subscribe message-passing
3403 subsystem that we can use to organize intermodule dependencies. We
3404 hope to use this to reduce dependencies between modules that don't
3405 need to be related, and to generally simplify our codebase. Closes
3408 o Major features (controller protocol):
3409 - Controller commands are now parsed using a generalized parsing
3410 subsystem. Previously, each controller command was responsible for
3411 parsing its own input, which led to strange inconsistencies.
3412 Closes ticket 30091.
3414 o Major features (flow control):
3415 - Implement authenticated SENDMEs as detailed in proposal 289. A
3416 SENDME cell now includes the digest of the traffic that it
3417 acknowledges, so that once an end point receives the SENDME, it
3418 can confirm the other side's knowledge of the previous cells that
3419 were sent, and prevent certain types of denial-of-service attacks.
3420 This behavior is controlled by two new consensus parameters: see
3421 the proposal for more details. Fixes ticket 26288.
3423 o Major features (performance):
3424 - Our node selection algorithm now excludes nodes in linear time.
3425 Previously, the algorithm was quadratic, which could slow down
3426 heavily used onion services. Closes ticket 30307.
3428 o Major features (performance, RNG):
3429 - Tor now constructs a fast secure pseudorandom number generator for
3430 each thread, to use when performance is critical. This PRNG is
3431 based on AES-CTR, using a buffering construction similar to
3432 libottery and the (newer) OpenBSD arc4random() code. It
3433 outperforms OpenSSL 1.1.1a's CSPRNG by roughly a factor of 100 for
3434 small outputs. Although we believe it to be cryptographically
3435 strong, we are only using it when necessary for performance.
3436 Implements tickets 29023 and 29536.
3438 o Major bugfixes (bridges):
3439 - Consider our directory information to have changed when our list
3440 of bridges changes. Previously, Tor would not re-compute the
3441 status of its directory information when bridges changed, and
3442 therefore would not realize that it was no longer able to build
3443 circuits. Fixes part of bug 29875.
3444 - Do not count previously configured working bridges towards our
3445 total of working bridges. Previously, when Tor's list of bridges
3446 changed, it would think that the old bridges were still usable,
3447 and delay fetching router descriptors for the new ones. Fixes part
3448 of bug 29875; bugfix on 0.3.0.1-alpha.
3450 o Major bugfixes (circuit build, guard):
3451 - On relays, properly check that a padding machine is absent before
3452 logging a warning about it being absent. Fixes bug 30649; bugfix
3454 - When considering upgrading circuits from "waiting for guard" to
3455 "open", always ignore circuits that are marked for close. Otherwise,
3456 we can end up in the situation where a subsystem is notified that
3457 a closing circuit has just opened, leading to undesirable
3458 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
3460 o Major bugfixes (onion service reachability):
3461 - Properly clean up the introduction point map when circuits change
3462 purpose from onion service circuits to pathbias, measurement, or
3463 other circuit types. This should fix some service-side instances
3464 of introduction point failure. Fixes bug 29034; bugfix
3467 o Major bugfixes (onion service v3):
3468 - Fix an unreachable bug in which an introduction point could try to
3469 send an INTRODUCE_ACK with a status code that Trunnel would refuse
3470 to encode, leading the relay to assert(). We've consolidated the
3471 ABI values into Trunnel now. Fixes bug 30454; bugfix
3473 - Clients can now handle unknown status codes from INTRODUCE_ACK
3474 cells. (The NACK behavior will stay the same.) This will allow us
3475 to extend status codes in the future without breaking the normal
3476 client behavior. Fixes another part of bug 30454; bugfix
3479 o Minor features (authenticated SENDME):
3480 - Ensure that there is enough randomness on every circuit to prevent
3481 an attacker from successfully predicting the hashes they will need
3482 to include in authenticated SENDME cells. At a random interval, if
3483 we have not sent randomness already, we now leave some extra space
3484 at the end of a cell that we can fill with random bytes. Closes
3487 o Minor features (circuit padding logging):
3488 - Demote noisy client-side warn logs about circuit padding to protocol
3489 warnings. Add additional log messages and circuit ID fields to help
3490 with bug 30992 and any other future issues.
3492 o Minor features (circuit padding):
3493 - We now use a fast PRNG when scheduling circuit padding. Part of
3495 - Allow the padding machine designer to pick the edges of their
3496 histogram instead of trying to compute them automatically using an
3497 exponential formula. Resolves some undefined behavior in the case
3498 of small histograms and allows greater flexibility on machine
3499 design. Closes ticket 29298; bugfix on 0.4.0.1-alpha.
3500 - Allow circuit padding machines to hold a circuit open until they
3501 are done padding it. Closes ticket 28780.
3503 o Minor features (compile-time modules):
3504 - Add a "--list-modules" command to print a list of which compile-
3505 time modules are enabled. Closes ticket 30452.
3507 o Minor features (continuous integration):
3508 - Our Travis configuration now uses Chutney to run some network
3509 integration tests automatically. Closes ticket 29280.
3510 - When running coverage builds on Travis, we now set
3511 TOR_TEST_RNG_SEED, to avoid RNG-based coverage differences. Part
3513 - Remove sudo configuration lines from .travis.yml as they are no
3514 longer needed with current Travis build environment. Resolves
3516 - In Travis, show stem's tor log after failure. Closes ticket 30234.
3518 o Minor features (controller):
3519 - Add onion service version 3 support to the HSFETCH command.
3520 Previously, only version 2 onion services were supported. Closes
3521 ticket 25417. Patch by Neel Chauhan.
3523 o Minor features (debugging):
3524 - Introduce tor_assertf() and tor_assertf_nonfatal() to enable
3525 logging of additional information during assert failure. Now we
3526 can use format strings to include information for trouble
3527 shooting. Resolves ticket 29662.
3529 o Minor features (defense in depth):
3530 - In smartlist_remove_keeporder(), set unused pointers to NULL, in
3531 case a bug causes them to be used later. Closes ticket 30176.
3532 Patch from Tobias Stoeckmann.
3533 - Tor now uses a cryptographically strong PRNG even for decisions
3534 that we do not believe are security-sensitive. Previously, for
3535 performance reasons, we had used a trivially predictable linear
3536 congruential generator algorithm for certain load-balancing and
3537 statistical sampling decisions. Now we use our fast RNG in those
3538 cases. Closes ticket 29542.
3540 o Minor features (developer tools):
3541 - Tor's "practracker" test script now checks for files and functions
3542 that seem too long and complicated. Existing overlong functions
3543 and files are accepted for now, but should eventually be
3544 refactored. Closes ticket 29221.
3545 - Add some scripts used for git maintenance to scripts/git. Closes
3547 - Call practracker from pre-push and pre-commit git hooks to let
3548 developers know if they made any code style violations. Closes
3550 - Add a script to check that each header has a well-formed and
3551 unique guard macro. Closes ticket 29756.
3553 o Minor features (fallback directory list):
3554 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
3555 in December 2018 (of which ~122 were still functional), with a
3556 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
3557 in June 2019. Closes ticket 28795.
3559 o Minor features (geoip):
3560 - Update geoip and geoip6 to the June 10 2019 Maxmind GeoLite2
3561 Country database. Closes ticket 30852.
3562 - Update geoip and geoip6 to the May 13 2019 Maxmind GeoLite2
3563 Country database. Closes ticket 30522.
3565 o Minor features (HTTP tunnel):
3566 - Return an informative web page when the HTTPTunnelPort is used as
3567 an HTTP proxy. Closes ticket 27821, patch by "eighthave".
3569 o Minor features (IPv6, v3 onion services):
3570 - Make v3 onion services put IPv6 addresses in service descriptors.
3571 Before this change, service descriptors only contained IPv4
3572 addresses. Implements 26992.
3574 o Minor features (logging):
3575 - Give a more useful assertion failure message if we think we have
3576 minherit() but we fail to make a region non-inheritable. Give a
3577 compile-time warning if our support for minherit() is incomplete.
3578 Closes ticket 30686.
3580 o Minor features (maintenance):
3581 - Add a new "make autostyle" target that developers can use to apply
3582 all automatic Tor style and consistency conversions to the
3583 codebase. Closes ticket 30539.
3585 o Minor features (modularity):
3586 - The "--disable-module-dirauth" compile-time option now disables
3587 even more dirauth-only code. Closes ticket 30345.
3589 o Minor features (performance):
3590 - Use OpenSSL's implementations of SHA3 when available (in OpenSSL
3591 1.1.1 and later), since they tend to be faster than tiny-keccak.
3592 Closes ticket 28837.
3594 o Minor features (testing):
3595 - The circuitpadding tests now use a reproducible RNG implementation,
3596 so that if a test fails, we can learn why. Part of ticket 28878.
3597 - Tor's tests now support an environment variable, TOR_TEST_RNG_SEED,
3598 to set the RNG seed for tests that use a reproducible RNG. Part of
3600 - When running tests in coverage mode, take additional care to make
3601 our coverage deterministic, so that we can accurately track
3602 changes in code coverage. Closes ticket 30519.
3603 - Tor's unit test code now contains helper functions to replace the
3604 PRNG with a deterministic or reproducible version for testing.
3605 Previously, various tests implemented this in various ways.
3606 Implements ticket 29732.
3607 - We now have a script, cov-test-determinism.sh, to identify places
3608 where our unit test coverage has become nondeterministic. Closes
3610 - Check that representative subsets of values of `int` and `unsigned
3611 int` can be represented by `void *`. Resolves issue 29537.
3613 o Minor bugfixes (bridge authority):
3614 - Bridge authorities now set bridges as running or non-running when
3615 about to dump their status to a file. Previously, they set bridges
3616 as running in response to a GETINFO command, but those shouldn't
3617 modify data structures. Fixes bug 24490; bugfix on 0.2.0.13-alpha.
3618 Patch by Neel Chauhan.
3620 o Minor bugfixes (channel padding statistics):
3621 - Channel padding write totals and padding-enabled totals are now
3622 counted properly in relay extrainfo descriptors. Fixes bug 29231;
3623 bugfix on 0.3.1.1-alpha.
3625 o Minor bugfixes (circuit isolation):
3626 - Fix a logic error that prevented the SessionGroup sub-option from
3627 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
3629 o Minor bugfixes (circuit padding):
3630 - Add a "CircuitPadding" torrc option to disable circuit padding.
3631 Fixes bug 28693; bugfix on 0.4.0.1-alpha.
3632 - Allow circuit padding machines to specify that they do not
3633 contribute much overhead, and provide consensus flags and torrc
3634 options to force clients to only use these low overhead machines.
3635 Fixes bug 29203; bugfix on 0.4.0.1-alpha.
3636 - Provide a consensus parameter to fully disable circuit padding, to
3637 be used in emergency network overload situations. Fixes bug 30173;
3638 bugfix on 0.4.0.1-alpha.
3639 - The circuit padding subsystem will no longer schedule padding if
3640 dormant mode is enabled. Fixes bug 28636; bugfix on 0.4.0.1-alpha.
3641 - Inspect a circuit-level cell queue before sending padding, to
3642 avoid sending padding while too much data is already queued. Fixes
3643 bug 29204; bugfix on 0.4.0.1-alpha.
3644 - Avoid calling monotime_absolute_usec() in circuit padding machines
3645 that do not use token removal or circuit RTT estimation. Fixes bug
3646 29085; bugfix on 0.4.0.1-alpha.
3648 o Minor bugfixes (clock skew detection):
3649 - Don't believe clock skew results from NETINFO cells that appear to
3650 arrive before we sent the VERSIONS cells they are responding to.
3651 Previously, we would accept them up to 3 minutes "in the past".
3652 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
3654 o Minor bugfixes (compatibility, standards compliance):
3655 - Fix a bug that would invoke undefined behavior on certain
3656 operating systems when trying to asprintf() a string exactly
3657 INT_MAX bytes long. We don't believe this is exploitable, but it's
3658 better to fix it anyway. Fixes bug 31001; bugfix on 0.2.2.11-alpha.
3659 Found and fixed by Tobias Stoeckmann.
3661 o Minor bugfixes (compilation warning):
3662 - Fix a compilation warning on Windows about casting a function
3663 pointer for GetTickCount64(). Fixes bug 31374; bugfix on
3666 o Minor bugfixes (compilation):
3667 - Avoid using labs() on time_t, which can cause compilation warnings
3668 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
3670 o Minor bugfixes (compilation, unusual configurations):
3671 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
3672 due to missing declarations of abort(), and prevent other such
3673 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
3675 o Minor bugfixes (configuration, proxies):
3676 - Fix a bug that prevented us from supporting SOCKS5 proxies that
3677 want authentication along with configured (but unused!)
3678 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
3680 o Minor bugfixes (continuous integration):
3681 - Allow the test-stem job to fail in Travis, because it sometimes
3682 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
3683 - Skip test_rebind on macOS in Travis, because it is unreliable on
3684 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3685 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
3686 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3688 o Minor bugfixes (controller protocol):
3689 - Teach the controller parser to distinguish an object preceded by
3690 an argument list from one without. Previously, it couldn't
3691 distinguish an argument list from the first line of a multiline
3692 object. Fixes bug 29984; bugfix on 0.2.3.8-alpha.
3694 o Minor bugfixes (crash on exit):
3695 - Avoid a set of possible code paths that could try to use freed
3696 memory in routerlist_free() while Tor was exiting. Fixes bug
3697 31003; bugfix on 0.1.2.2-alpha.
3699 o Minor bugfixes (developer tooling):
3700 - Fix pre-push hook to allow fixup and squash commits when pushing
3701 to non-upstream git remote. Fixes bug 30286; bugfix
3704 o Minor bugfixes (directory authorities):
3705 - Stop crashing after parsing an unknown descriptor purpose
3706 annotation. We think this bug can only be triggered by modifying a
3707 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
3708 - Move the "bandwidth-file-headers" line in directory authority
3709 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
3711 - Directory authorities with IPv6 support now always mark themselves
3712 as reachable via IPv6. Fixes bug 24338; bugfix on 0.2.4.1-alpha.
3713 Patch by Neel Chauhan.
3715 o Minor bugfixes (documentation):
3716 - Improve the documentation for using MapAddress with ".exit". Fixes
3717 bug 30109; bugfix on 0.1.0.1-rc.
3718 - Improve the monotonic time module and function documentation to
3719 explain what "monotonic" actually means, and document some results
3720 that have surprised people. Fixes bug 29640; bugfix
3722 - Use proper formatting when providing an example on quoting options
3723 that contain whitespace. Fixes bug 29635; bugfix on 0.2.3.18-rc.
3725 o Minor bugfixes (logging):
3726 - Do not log a warning when running with an OpenSSL version other
3727 than the one Tor was compiled with, if the two versions should be
3728 compatible. Previously, we would warn whenever the version was
3729 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
3730 - Warn operators when the MyFamily option is set but ContactInfo is
3731 missing, as the latter should be set too. Fixes bug 25110; bugfix
3734 o Minor bugfixes (memory leaks):
3735 - Avoid a minor memory leak that could occur on relays when failing
3736 to create a "keys" directory. Fixes bug 30148; bugfix
3738 - Fix a trivial memory leak when parsing an invalid value from a
3739 download schedule in the configuration. Fixes bug 30894; bugfix
3742 o Minor bugfixes (NetBSD):
3743 - Fix usage of minherit() on NetBSD and other platforms that define
3744 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
3745 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
3747 o Minor bugfixes (onion services):
3748 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
3749 implemenation) when failing to load an onion service client
3750 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
3751 - When refusing to launch a controller's HSFETCH request because of
3752 rate-limiting, respond to the controller with a new response,
3753 "QUERY_RATE_LIMITED". Previously, we would log QUERY_NO_HSDIR for
3754 this case. Fixes bug 28269; bugfix on 0.3.1.1-alpha. Patch by
3756 - When relaunching a circuit to a rendezvous service, mark the
3757 circuit as needing high-uptime routers as appropriate. Fixes bug
3758 17357; bugfix on 0.1.0.1-rc. Patch by Neel Chauhan.
3759 - Stop ignoring IPv6 link specifiers sent to v3 onion services.
3760 (IPv6 support for v3 onion services is still incomplete: see
3761 ticket 23493 for details.) Fixes bug 23588; bugfix on
3762 0.3.2.1-alpha. Patch by Neel Chauhan.
3764 o Minor bugfixes (onion services, performance):
3765 - When building circuits to onion services, call tor_addr_parse()
3766 less often. Previously, we called tor_addr_parse() in
3767 circuit_is_acceptable() even if its output wasn't used. This
3768 change should improve performance when building circuits. Fixes
3769 bug 22210; bugfix on 0.2.8.12. Patch by Neel Chauhan.
3771 o Minor bugfixes (out-of-memory handler):
3772 - When purging the DNS cache because of an out-of-memory condition,
3773 try purging just the older entries at first. Previously, we would
3774 always purge the whole thing. Fixes bug 29617; bugfix
3777 o Minor bugfixes (performance):
3778 - When checking whether a node is a bridge, use a fast check to make
3779 sure that its identity is set. Previously, we used a constant-time
3780 check, which is not necessary in this case. Fixes bug 30308;
3781 bugfix on 0.3.5.1-alpha.
3783 o Minor bugfixes (pluggable transports):
3784 - Tor now sets TOR_PT_EXIT_ON_STDIN_CLOSE=1 for client transports as
3785 well as servers. Fixes bug 25614; bugfix on 0.2.7.1-alpha.
3787 o Minor bugfixes (portability):
3788 - Avoid crashing in our tor_vasprintf() implementation on systems
3789 that define neither vasprintf() nor _vscprintf(). (This bug has
3790 been here long enough that we question whether people are running
3791 Tor on such systems, but we're applying the fix out of caution.)
3792 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
3795 o Minor bugfixes (probability distributions):
3796 - Refactor and improve parts of the probability distribution code
3797 that made Coverity complain. Fixes bug 29805; bugfix
3800 o Minor bugfixes (python):
3801 - Stop assuming that /usr/bin/python3 exists. For scripts that work
3802 with python2, use /usr/bin/python. Otherwise, use /usr/bin/env
3803 python3. Fixes bug 29913; bugfix on 0.2.5.3-alpha.
3805 o Minor bugfixes (relay):
3806 - When running as a relay, if IPv6Exit is set to 1 while ExitRelay
3807 is auto, act as if ExitRelay is 1. Previously, we would ignore
3808 IPv6Exit if ExitRelay was 0 or auto. Fixes bug 29613; bugfix on
3809 0.3.5.1-alpha. Patch by Neel Chauhan.
3811 o Minor bugfixes (static analysis):
3812 - Fix several spurious Coverity warnings about the unit tests, to
3813 lower our chances of missing real warnings in the future. Fixes
3814 bug 30150; bugfix on 0.3.5.1-alpha and various other Tor versions.
3816 o Minor bugfixes (stats):
3817 - When ExtraInfoStatistics is 0, stop including bandwidth usage
3818 statistics, GeoIPFile hashes, ServerTransportPlugin lines, and
3819 bridge statistics by country in extra-info documents. Fixes bug
3820 29018; bugfix on 0.2.4.1-alpha.
3822 o Minor bugfixes (testing):
3823 - Call setrlimit() to disable core dumps in test_bt_cl.c. Previously
3824 we used `ulimit -c` in test_bt.sh, which violates POSIX shell
3825 compatibility. Fixes bug 29061; bugfix on 0.3.5.1-alpha.
3826 - Fix some incorrect code in the v3 onion service unit tests. Fixes
3827 bug 29243; bugfix on 0.3.2.1-alpha.
3828 - In the "routerkeys/*" tests, check the return values of mkdir()
3829 for possible failures. Fixes bug 29939; bugfix on 0.2.7.2-alpha.
3830 Found by Coverity as CID 1444254.
3831 - Split test_utils_general() into several smaller test functions.
3832 This makes it easier to perform resource deallocation on assert
3833 failure, and fixes Coverity warnings CID 1444117 and CID 1444118.
3834 Fixes bug 29823; bugfix on 0.2.9.1-alpha.
3836 o Minor bugfixes (tor-resolve):
3837 - Fix a memory leak in tor-resolve that could happen if Tor gave it
3838 a malformed SOCKS response. (Memory leaks in tor-resolve don't
3839 actually matter, but it's good to fix them anyway.) Fixes bug
3840 30151; bugfix on 0.4.0.1-alpha.
3842 o Code simplification and refactoring:
3843 - Abstract out the low-level formatting of replies on the control
3844 port. Implements ticket 30007.
3845 - Add several assertions in an attempt to fix some Coverity
3846 warnings. Closes ticket 30149.
3847 - Introduce a connection_dir_buf_add() helper function that checks
3848 for compress_state of dir_connection_t and automatically writes a
3849 string to directory connection with or without compression.
3850 Resolves issue 28816.
3851 - Make the base32_decode() API return the number of bytes written,
3852 for consistency with base64_decode(). Closes ticket 28913.
3853 - Move most relay-only periodic events out of mainloop.c into the
3854 relay subsystem. Closes ticket 30414.
3855 - Refactor and encapsulate parts of the codebase that manipulate
3856 crypt_path_t objects. Resolves issue 30236.
3857 - Refactor several places in our code that Coverity incorrectly
3858 believed might have memory leaks. Closes ticket 30147.
3859 - Remove redundant return values in crypto_format, and the
3860 associated return value checks elsewhere in the code. Make the
3861 implementations in crypto_format consistent, and remove redundant
3862 code. Resolves ticket 29660.
3863 - Rename tor_mem_is_zero() to fast_mem_is_zero(), to emphasize that
3864 it is not a constant-time function. Closes ticket 30309.
3865 - Replace hs_desc_link_specifier_t with link_specifier_t, and remove
3866 all hs_desc_link_specifier_t-specific code. Fixes bug 22781;
3867 bugfix on 0.3.2.1-alpha.
3868 - Simplify v3 onion service link specifier handling code. Fixes bug
3869 23576; bugfix on 0.3.2.1-alpha.
3870 - Split crypto_digest.c into NSS code, OpenSSL code, and shared
3871 code. Resolves ticket 29108.
3872 - Split control.c into several submodules, in preparation for
3873 distributing its current responsibilities throughout the codebase.
3874 Closes ticket 29894.
3875 - Start to move responsibility for knowing about periodic events to
3876 the appropriate subsystems, so that the mainloop doesn't need to
3877 know all the periodic events in the rest of the codebase.
3878 Implements tickets 30293 and 30294.
3881 - Mention URLs for Travis/Appveyor/Jenkins in ReleasingTor.md.
3882 Closes ticket 30630.
3883 - Document how to find git commits and tags for bug fixes in
3884 CodingStandards.md. Update some file documentation. Closes
3888 - Remove the linux-tor-prio.sh script from contrib/operator-tools
3889 directory. Resolves issue 29434.
3890 - Remove the obsolete OpenSUSE initscript. Resolves issue 30076.
3891 - Remove the obsolete script at contrib/dist/tor.sh.in. Resolves
3895 - Specify torrc paths (with empty files) when launching tor in
3896 integration tests; refrain from reading user and system torrcs.
3897 Resolves issue 29702.
3899 o Code simplification and refactoring (shell scripts):
3900 - Clean up many of our shell scripts to fix shellcheck warnings.
3901 These include autogen.sh (ticket 26069), test_keygen.sh (ticket
3902 29062), test_switch_id.sh (ticket 29065), test_rebind.sh (ticket
3903 29063), src/test/fuzz/minimize.sh (ticket 30079), test_rust.sh
3904 (ticket 29064), torify (ticket 29070), asciidoc-helper.sh (29926),
3905 fuzz_multi.sh (30077), fuzz_static_testcases.sh (ticket 29059),
3906 nagios-check-tor-authority-cert (ticket 29071),
3907 src/test/fuzz/fixup_filenames.sh (ticket 30078), test-network.sh
3908 (ticket 29060), test_key_expiration.sh (ticket 30002),
3909 zero_length_keys.sh (ticket 29068), and test_workqueue_*.sh
3912 o Testing (chutney):
3913 - In "make test-network-all", test IPv6-only v3 single onion
3914 services, using the chutney network single-onion-v23-ipv6-md.
3915 Closes ticket 27251.
3917 o Testing (continuous integration):
3918 - In Travis, make stem log a controller trace to the console, and tail
3919 stem's tor log after failure. Closes ticket 30591.
3920 - In Travis, only run the stem tests that use a tor binary.
3921 Closes ticket 30694.
3924 Changes in version 0.4.0.5 - 2019-05-02
3925 This is the first stable release in the 0.4.0.x series. It contains
3926 improvements for power management and bootstrap reporting, as well as
3927 preliminary backend support for circuit padding to prevent some kinds
3928 of traffic analysis. It also continues our work in refactoring Tor for
3929 long-term maintainability.
3931 Per our support policy, we will support the 0.4.0.x series for nine
3932 months, or until three months after the release of a stable 0.4.1.x:
3933 whichever is longer. If you need longer-term support, please stick
3934 with 0.3.5.x, which will we plan to support until Feb 2022.
3936 Below are the changes since 0.3.5.7. For a complete list of changes
3937 since 0.4.0.4-rc, see the ChangeLog file.
3939 o Major features (battery management, client, dormant mode):
3940 - When Tor is running as a client, and it is unused for a long time,
3941 it can now enter a "dormant" state. When Tor is dormant, it avoids
3942 network and CPU activity until it is reawoken either by a user
3943 request or by a controller command. For more information, see the
3944 configuration options starting with "Dormant". Implements tickets
3946 - The client's memory of whether it is "dormant", and how long it
3947 has spent idle, persists across invocations. Implements
3949 - There is a DormantOnFirstStartup option that integrators can use
3950 if they expect that in many cases, Tor will be installed but
3953 o Major features (bootstrap reporting):
3954 - When reporting bootstrap progress, report the first connection
3955 uniformly, regardless of whether it's a connection for building
3956 application circuits. This allows finer-grained reporting of early
3957 progress than previously possible, with the improvements of ticket
3958 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.
3959 - When reporting bootstrap progress, treat connecting to a proxy or
3960 pluggable transport as separate from having successfully used that
3961 proxy or pluggable transport to connect to a relay. Closes tickets
3964 o Major features (circuit padding):
3965 - Implement preliminary support for the circuit padding portion of
3966 Proposal 254. The implementation supports Adaptive Padding (aka
3967 WTF-PAD) state machines for use between experimental clients and
3968 relays. Support is also provided for APE-style state machines that
3969 use probability distributions instead of histograms to specify
3970 inter-packet delay. At the moment, Tor does not provide any
3971 padding state machines that are used in normal operation: for now,
3972 this feature exists solely for experimentation. Closes
3975 o Major features (refactoring):
3976 - Tor now uses an explicit list of its own subsystems when
3977 initializing and shutting down. Previously, these systems were
3978 managed implicitly in various places throughout the codebase.
3979 (There may still be some subsystems using the old system.) Closes
3982 o Major bugfixes (cell scheduler, KIST, security):
3983 - Make KIST consider the outbuf length when computing what it can
3984 put in the outbuf. Previously, KIST acted as though the outbuf
3985 were empty, which could lead to the outbuf becoming too full. It
3986 is possible that an attacker could exploit this bug to cause a Tor
3987 client or relay to run out of memory and crash. Fixes bug 29168;
3988 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
3989 TROVE-2019-001 and CVE-2019-8955.
3991 o Major bugfixes (networking):
3992 - Gracefully handle empty username/password fields in SOCKS5
3993 username/password auth message and allow SOCKS5 handshake to
3994 continue. Previously, we had rejected these handshakes, breaking
3995 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
3997 o Major bugfixes (NSS, relay):
3998 - When running with NSS, disable TLS 1.2 ciphersuites that use
3999 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
4000 these ciphersuites don't work -- which caused relays to fail to
4001 handshake with one another when these ciphersuites were enabled.
4002 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
4004 o Major bugfixes (windows, startup):
4005 - When reading a consensus file from disk, detect whether it was
4006 written in text mode, and re-read it in text mode if so. Always
4007 write consensus files in binary mode so that we can map them into
4008 memory later. Previously, we had written in text mode, which
4009 confused us when we tried to map the file on windows. Fixes bug
4010 28614; bugfix on 0.4.0.1-alpha.
4012 o Minor features (address selection):
4013 - Treat the subnet 100.64.0.0/10 as public for some purposes;
4014 private for others. This subnet is the RFC 6598 (Carrier Grade
4015 NAT) IP range, and is deployed by many ISPs as an alternative to
4016 RFC 1918 that does not break existing internal networks. Tor now
4017 blocks SOCKS and control ports on these addresses and warns users
4018 if client ports or ExtORPorts are listening on a RFC 6598 address.
4019 Closes ticket 28525. Patch by Neel Chauhan.
4021 o Minor features (bandwidth authority):
4022 - Make bandwidth authorities ignore relays that are reported in the
4023 bandwidth file with the flag "vote=0". This change allows us to
4024 report unmeasured relays for diagnostic reasons without including
4025 their bandwidth in the bandwidth authorities' vote. Closes
4027 - When a directory authority is using a bandwidth file to obtain the
4028 bandwidth values that will be included in the next vote, serve
4029 this bandwidth file at /tor/status-vote/next/bandwidth. Closes
4032 o Minor features (bootstrap reporting):
4033 - When reporting bootstrap progress, stop distinguishing between
4034 situations where only internal paths are available and situations
4035 where external paths are available. Previously, Tor would often
4036 erroneously report that it had only internal paths. Closes
4039 o Minor features (compilation):
4040 - Compile correctly when OpenSSL is built with engine support
4041 disabled, or with deprecated APIs disabled. Closes ticket 29026.
4042 Patches from "Mangix".
4044 o Minor features (continuous integration):
4045 - On Travis Rust builds, cleanup Rust registry and refrain from
4046 caching the "target/" directory to speed up builds. Resolves
4048 - Log Python version during each Travis CI job. Resolves
4050 - In Travis, tell timelimit to use stem's backtrace signals, and
4051 launch python directly from timelimit, so python receives the
4052 signals from timelimit, rather than make. Closes ticket 30117.
4054 o Minor features (controller):
4055 - Add a DROPOWNERSHIP command to undo the effects of TAKEOWNERSHIP.
4056 Implements ticket 28843.
4058 o Minor features (developer tooling):
4059 - Check that bugfix versions in changes files look like Tor versions
4060 from the versions spec. Warn when bugfixes claim to be on a future
4061 release. Closes ticket 27761.
4062 - Provide a git pre-commit hook that disallows committing if we have
4063 any failures in our code and changelog formatting checks. It is
4064 now available in scripts/maint/pre-commit.git-hook. Implements
4066 - Provide a git hook script to prevent "fixup!" and "squash!"
4067 commits from ending up in the master branch, as scripts/main/pre-
4068 push.git-hook. Closes ticket 27993.
4070 o Minor features (diagnostic):
4071 - Add more diagnostic log messages in an attempt to solve the issue
4072 of NUL bytes appearing in a microdescriptor cache. Related to
4075 o Minor features (directory authority):
4076 - When a directory authority is using a bandwidth file to obtain
4077 bandwidth values, include the digest of that file in the vote.
4078 Closes ticket 26698.
4079 - Directory authorities support a new consensus algorithm, under
4080 which the family lines in microdescriptors are encoded in a
4081 canonical form. This change makes family lines more compressible
4082 in transit, and on the client. Closes ticket 28266; implements
4085 o Minor features (directory authority, relay):
4086 - Authorities now vote on a "StaleDesc" flag to indicate that a
4087 relay's descriptor is so old that the relay should upload again
4088 soon. Relays treat this flag as a signal to upload a new
4089 descriptor. This flag will eventually let us remove the
4090 'published' date from routerstatus entries, and make our consensus
4091 diffs much smaller. Closes ticket 26770; implements proposal 293.
4093 o Minor features (dormant mode):
4094 - Add a DormantCanceledByStartup option to tell Tor that it should
4095 treat a startup event as cancelling any previous dormant state.
4096 Integrators should use this option with caution: it should only be
4097 used if Tor is being started because of something that the user
4098 did, and not if Tor is being automatically started in the
4099 background. Closes ticket 29357.
4101 o Minor features (fallback directory mirrors):
4102 - Update the fallback whitelist based on operator opt-ins and opt-
4103 outs. Closes ticket 24805, patch by Phoul.
4105 o Minor features (FreeBSD):
4106 - On FreeBSD-based systems, warn relay operators if the
4107 "net.inet.ip.random_id" sysctl (IP ID randomization) is disabled.
4108 Closes ticket 28518.
4110 o Minor features (geoip):
4111 - Update geoip and geoip6 to the April 2 2019 Maxmind GeoLite2
4112 Country database. Closes ticket 29992.
4114 o Minor features (HTTP standards compliance):
4115 - Stop sending the header "Content-type: application/octet-stream"
4116 along with transparently compressed documents: this confused
4117 browsers. Closes ticket 28100.
4119 o Minor features (IPv6):
4120 - We add an option ClientAutoIPv6ORPort, to make clients randomly
4121 prefer a node's IPv4 or IPv6 ORPort. The random preference is set
4122 every time a node is loaded from a new consensus or bridge config.
4123 We expect that this option will enable clients to bootstrap more
4124 quickly without having to determine whether they support IPv4,
4125 IPv6, or both. Closes ticket 27490. Patch by Neel Chauhan.
4126 - When using addrs_in_same_network_family(), avoid choosing circuit
4127 paths that pass through the same IPv6 subnet more than once.
4128 Previously, we only checked IPv4 subnets. Closes ticket 24393.
4129 Patch by Neel Chauhan.
4131 o Minor features (log messages):
4132 - Improve log message in v3 onion services that could print out
4133 negative revision counters. Closes ticket 27707. Patch
4136 o Minor features (memory usage):
4137 - Save memory by storing microdescriptor family lists with a more
4138 compact representation. Closes ticket 27359.
4139 - Tor clients now use mmap() to read consensus files from disk, so
4140 that they no longer need keep the full text of a consensus in
4141 memory when parsing it or applying a diff. Closes ticket 27244.
4143 o Minor features (NSS, diagnostic):
4144 - Try to log an error from NSS (if there is any) and a more useful
4145 description of our situation if we are using NSS and a call to
4146 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
4148 o Minor features (parsing):
4149 - Directory authorities now validate that router descriptors and
4150 ExtraInfo documents are in a valid subset of UTF-8, and reject
4151 them if they are not. Closes ticket 27367.
4153 o Minor features (performance):
4154 - Cache the results of summarize_protocol_flags(), so that we don't
4155 have to parse the same protocol-versions string over and over.
4156 This should save us a huge number of malloc calls on startup, and
4157 may reduce memory fragmentation with some allocators. Closes
4159 - Remove a needless memset() call from get_token_arguments, thereby
4160 speeding up the tokenization of directory objects by about 20%.
4161 Closes ticket 28852.
4162 - Replace parse_short_policy() with a faster implementation, to
4163 improve microdescriptor parsing time. Closes ticket 28853.
4164 - Speed up directory parsing a little by avoiding use of the non-
4165 inlined strcmp_len() function. Closes ticket 28856.
4166 - Speed up microdescriptor parsing by about 30%, to help improve
4167 startup time. Closes ticket 28839.
4169 o Minor features (pluggable transports):
4170 - Add support for emitting STATUS updates to Tor's control port from
4171 a pluggable transport process. Closes ticket 28846.
4172 - Add support for logging to Tor's logging subsystem from a
4173 pluggable transport process. Closes ticket 28180.
4175 o Minor features (process management):
4176 - Add a new process API for handling child processes. This new API
4177 allows Tor to have bi-directional communication with child
4178 processes on both Unix and Windows. Closes ticket 28179.
4179 - Use the subsystem manager to initialize and shut down the process
4180 module. Closes ticket 28847.
4182 o Minor features (relay):
4183 - When listing relay families, list them in canonical form including
4184 the relay's own identity, and try to give a more useful set of
4185 warnings. Part of ticket 28266 and proposal 298.
4187 o Minor features (required protocols):
4188 - Before exiting because of a missing required protocol, Tor will
4189 now check the publication time of the consensus, and not exit
4190 unless the consensus is newer than the Tor program's own release
4191 date. Previously, Tor would not check the consensus publication
4192 time, and so might exit because of a missing protocol that might
4193 no longer be required in a current consensus. Implements proposal
4194 297; closes ticket 27735.
4196 o Minor features (testing):
4197 - Treat all unexpected ERR and BUG messages as test failures. Closes
4199 - Allow a HeartbeatPeriod of less than 30 minutes in testing Tor
4200 networks. Closes ticket 28840. Patch by Rob Jansen.
4201 - Use the approx_time() function when setting the "Expires" header
4202 in directory replies, to make them more testable. Needed for
4205 o Minor bugfixes (security):
4206 - Fix a potential double free bug when reading huge bandwidth files.
4207 The issue is not exploitable in the current Tor network because
4208 the vulnerable code is only reached when directory authorities
4209 read bandwidth files, but bandwidth files come from a trusted
4210 source (usually the authorities themselves). Furthermore, the
4211 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
4212 which are not used by any of the current authorities. Fixes bug
4213 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
4215 - Verify in more places that we are not about to create a buffer
4216 with more than INT_MAX bytes, to avoid possible OOB access in the
4217 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
4218 fixed by Tobias Stoeckmann.
4220 o Minor bugfix (continuous integration):
4221 - Reset coverage state on disk after Travis CI has finished. This
4222 should prevent future coverage merge errors from causing the test
4223 suite for the "process" subsystem to fail. The process subsystem
4224 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
4226 - Terminate test-stem if it takes more than 9.5 minutes to run.
4227 (Travis terminates the job after 10 minutes of no output.)
4228 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
4230 o Minor bugfixes (build, compatibility, rust):
4231 - Update Cargo.lock file to match the version made by the latest
4232 version of Rust, so that "make distcheck" will pass again. Fixes
4233 bug 29244; bugfix on 0.3.3.4-alpha.
4235 o Minor bugfixes (C correctness):
4236 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
4237 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
4240 o Minor bugfixes (client, clock skew):
4241 - Bootstrap successfully even when Tor's clock is behind the clocks
4242 on the authorities. Fixes bug 28591; bugfix on 0.2.0.9-alpha.
4243 - Select guards even if the consensus has expired, as long as the
4244 consensus is still reasonably live. Fixes bug 24661; bugfix
4247 o Minor bugfixes (compilation):
4248 - Fix compilation warnings in test_circuitpadding.c. Fixes bug
4249 29169; bugfix on 0.4.0.1-alpha.
4250 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
4251 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
4252 - Compile correctly on OpenBSD; previously, we were missing some
4253 headers required in order to detect it properly. Fixes bug 28938;
4254 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
4256 o Minor bugfixes (directory clients):
4257 - Mark outdated dirservers when Tor only has a reasonably live
4258 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
4260 o Minor bugfixes (directory mirrors):
4261 - Even when a directory mirror's clock is behind the clocks on the
4262 authorities, we now allow the mirror to serve "future"
4263 consensuses. Fixes bug 28654; bugfix on 0.3.0.1-alpha.
4265 o Minor bugfixes (DNS):
4266 - Gracefully handle an empty or absent resolve.conf file by falling
4267 back to using "localhost" as a DNS server (and hoping it works).
4268 Previously, we would just stop running as an exit. Fixes bug
4269 21900; bugfix on 0.2.1.10-alpha.
4271 o Minor bugfixes (documentation):
4272 - Describe the contents of the v3 onion service client authorization
4273 files correctly: They hold public keys, not private keys. Fixes
4274 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
4276 o Minor bugfixes (guards):
4277 - In count_acceptable_nodes(), the minimum number is now one bridge
4278 or guard node, and two non-guard nodes for a circuit. Previously,
4279 we had added up the sum of all nodes with a descriptor, but that
4280 could cause us to build failing circuits when we had either too
4281 many bridges or not enough guard nodes. Fixes bug 25885; bugfix on
4282 0.2.3.1-alpha. Patch by Neel Chauhan.
4284 o Minor bugfixes (IPv6):
4285 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
4286 IPv6 socket was bound using an address family of AF_INET instead
4287 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
4290 o Minor bugfixes (linux seccomp sandbox):
4291 - Fix startup crash when experimental sandbox support is enabled.
4292 Fixes bug 29150; bugfix on 0.4.0.1-alpha. Patch by Peter Gerber.
4294 o Minor bugfixes (logging):
4295 - Correct a misleading error message when IPv4Only or IPv6Only is
4296 used but the resolved address can not be interpreted as an address
4297 of the specified IP version. Fixes bug 13221; bugfix on
4298 0.2.3.9-alpha. Patch from Kris Katterjohn.
4299 - Log the correct port number for listening sockets when "auto" is
4300 used to let Tor pick the port number. Previously, port 0 was
4301 logged instead of the actual port number. Fixes bug 29144; bugfix
4302 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
4303 - Stop logging a BUG() warning when Tor is waiting for exit
4304 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
4305 - Avoid logging that we are relaxing a circuit timeout when that
4306 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
4307 - Log more information at "warning" level when unable to read a
4308 private key; log more information at "info" level when unable to
4309 read a public key. We had warnings here before, but they were lost
4310 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
4311 - Rework rep_hist_log_link_protocol_counts() to iterate through all
4312 link protocol versions when logging incoming/outgoing connection
4313 counts. Tor no longer skips version 5, and we won't have to
4314 remember to update this function when new link protocol version is
4315 developed. Fixes bug 28920; bugfix on 0.2.6.10.
4317 o Minor bugfixes (memory management):
4318 - Refactor the shared random state's memory management so that it
4319 actually takes ownership of the shared random value pointers.
4320 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
4321 - Stop leaking parts of the shared random state in the shared-random
4322 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
4324 o Minor bugfixes (misc):
4325 - The amount of total available physical memory is now determined
4326 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
4327 when it is defined and a 64-bit variant is not available. Fixes
4328 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
4330 o Minor bugfixes (networking):
4331 - Introduce additional checks into tor_addr_parse() to reject
4332 certain incorrect inputs that previously were not detected. Fixes
4333 bug 23082; bugfix on 0.2.0.10-alpha.
4335 o Minor bugfixes (onion service v3, client):
4336 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
4337 connection waiting for a descriptor that we actually have in the
4338 cache. It turns out that this can actually happen, though it is
4339 rare. Now, tor will recover and retry the descriptor. Fixes bug
4340 28669; bugfix on 0.3.2.4-alpha.
4342 o Minor bugfixes (onion services):
4343 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
4344 than one private key for a hidden service. Fixes bug 29040; bugfix
4346 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
4347 "debug" level. Tor used to log it as a warning, which caused very
4348 long log lines to appear for some users. Fixes bug 29135; bugfix
4350 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
4351 as a warning. Instead, log it as a protocol warning, because there
4352 is nothing that relay operators can do to fix it. Fixes bug 29029;
4353 bugfix on 0.2.5.7-rc.
4355 o Minor bugfixes (periodic events):
4356 - Refrain from calling routerlist_remove_old_routers() from
4357 check_descriptor_callback(). Instead, create a new hourly periodic
4358 event. Fixes bug 27929; bugfix on 0.2.8.1-alpha.
4360 o Minor bugfixes (pluggable transports):
4361 - Make sure that data is continously read from standard output and
4362 standard error pipes of a pluggable transport child-process, to
4363 avoid deadlocking when a pipe's buffer is full. Fixes bug 26360;
4364 bugfix on 0.2.3.6-alpha.
4366 o Minor bugfixes (rust):
4367 - Abort on panic in all build profiles, instead of potentially
4368 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
4370 o Minor bugfixes (scheduler):
4371 - When re-adding channels to the pending list, check the correct
4372 channel's sched_heap_idx. This issue has had no effect in mainline
4373 Tor, but could have led to bugs down the road in improved versions
4374 of our circuit scheduling code. Fixes bug 29508; bugfix
4377 o Minor bugfixes (shellcheck):
4378 - Look for scripts in their correct locations during "make
4379 shellcheck". Previously we had looked in the wrong place during
4380 out-of-tree builds. Fixes bug 30263; bugfix on 0.4.0.1-alpha.
4382 o Minor bugfixes (single onion services):
4383 - Allow connections to single onion services to remain idle without
4384 being disconnected. Previously, relays acting as rendezvous points
4385 for single onion services were mistakenly closing idle rendezvous
4386 circuits after 60 seconds, thinking that they were unused
4387 directory-fetching circuits that had served their purpose. Fixes
4388 bug 29665; bugfix on 0.2.1.26.
4390 o Minor bugfixes (stats):
4391 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
4392 relay and bridge extra-info documents. Fixes bug 29017; bugfix
4395 o Minor bugfixes (testing):
4396 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
4397 recent test-network.sh to use new chutney features in CI. Fixes
4398 bug 29703; bugfix on 0.2.9.1-alpha.
4399 - Fix a test failure on Windows caused by an unexpected "BUG"
4400 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
4402 - Downgrade some LOG_ERR messages in the address/* tests to
4403 warnings. The LOG_ERR messages were occurring when we had no
4404 configured network. We were failing the unit tests, because we
4405 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
4406 29530; bugfix on 0.3.5.8.
4407 - Fix our gcov wrapper script to look for object files at the
4408 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
4409 - Decrease the false positive rate of stochastic probability
4410 distribution tests. Fixes bug 29693; bugfix on 0.4.0.1-alpha.
4411 - Fix intermittent failures on an adaptive padding test. Fixes one
4412 case of bug 29122; bugfix on 0.4.0.1-alpha.
4413 - Disable an unstable circuit-padding test that was failing
4414 intermittently because of an ill-defined small histogram. Such
4415 histograms will be allowed again after 29298 is implemented. Fixes
4416 a second case of bug 29122; bugfix on 0.4.0.1-alpha.
4417 - Detect and suppress "bug" warnings from the util/time test on
4418 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
4419 - Do not log an error-level message if we fail to find an IPv6
4420 network interface from the unit tests. Fixes bug 29160; bugfix
4422 - Instead of relying on hs_free_all() to clean up all onion service
4423 objects in test_build_descriptors(), we now deallocate them one by
4424 one. This lets Coverity know that we are not leaking memory there
4425 and fixes CID 1442277. Fixes bug 28989; bugfix on 0.3.5.1-alpha.
4426 - Check the time in the "Expires" header using approx_time(). Fixes
4427 bug 30001; bugfix on 0.4.0.4-rc.
4429 o Minor bugfixes (TLS protocol):
4430 - When classifying a client's selection of TLS ciphers, if the
4431 client ciphers are not yet available, do not cache the result.
4432 Previously, we had cached the unavailability of the cipher list
4433 and never looked again, which in turn led us to assume that the
4434 client only supported the ancient V1 link protocol. This, in turn,
4435 was causing Stem integration tests to stall in some cases. Fixes
4436 bug 30021; bugfix on 0.2.4.8-alpha.
4438 o Minor bugfixes (UI):
4439 - Lower log level of unlink() errors during bootstrap. Fixes bug
4440 29930; bugfix on 0.4.0.1-alpha.
4442 o Minor bugfixes (usability):
4443 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
4444 Some users took this phrasing to mean that the mentioned guard was
4445 under their control or responsibility, which it is not. Fixes bug
4446 28895; bugfix on Tor 0.3.0.1-alpha.
4448 o Minor bugfixes (Windows, CI):
4449 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
4450 Windows Server 2012 R2 job. The remaining 2 jobs still provide
4451 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
4452 fast_finish, so failed jobs terminate the build immediately. Fixes
4453 bug 29601; bugfix on 0.3.5.4-alpha.
4455 o Code simplification and refactoring:
4456 - Introduce a connection_dir_buf_add() helper function that detects
4457 whether compression is in use, and adds a string accordingly.
4458 Resolves issue 28816.
4459 - Refactor handle_get_next_bandwidth() to use
4460 connection_dir_buf_add(). Implements ticket 29897.
4461 - Reimplement NETINFO cell parsing and generation to rely on
4462 trunnel-generated wire format handling code. Closes ticket 27325.
4463 - Remove unnecessary unsafe code from the Rust macro "cstr!". Closes
4465 - Rework SOCKS wire format handling to rely on trunnel-generated
4466 parsing/generation code. Resolves ticket 27620.
4467 - Split out bootstrap progress reporting from control.c into a
4468 separate file. Part of ticket 27402.
4469 - The .may_include files that we use to describe our directory-by-
4470 directory dependency structure now describe a noncircular
4471 dependency graph over the directories that they cover. Our
4472 checkIncludes.py tool now enforces this noncircularity. Closes
4476 - Clarify that Tor performs stream isolation among *Port listeners
4477 by default. Resolves issue 29121.
4478 - In the manpage entry describing MapAddress torrc setting, use
4479 example IP addresses from ranges specified for use in documentation
4480 by RFC 5737. Resolves issue 28623.
4481 - Mention that you cannot add a new onion service if Tor is already
4482 running with Sandbox enabled. Closes ticket 28560.
4483 - Improve ControlPort documentation. Mention that it accepts
4484 address:port pairs, and can be used multiple times. Closes
4486 - Document the exact output of "tor --version". Closes ticket 28889.
4489 - Remove the old check-tor script. Resolves issue 29072.
4490 - Stop responding to the 'GETINFO status/version/num-concurring' and
4491 'GETINFO status/version/num-versioning' control port commands, as
4492 those were deprecated back in 0.2.0.30. Also stop listing them in
4493 output of 'GETINFO info/names'. Resolves ticket 28757.
4494 - The scripts used to generate and maintain the list of fallback
4495 directories have been extracted into a new "fallback-scripts"
4496 repository. Closes ticket 27914.
4499 - Run shellcheck for scripts in the in scripts/ directory. Closes
4501 - Add unit tests for tokenize_string() and get_next_token()
4502 functions. Resolves ticket 27625.
4504 o Code simplification and refactoring (onion service v3):
4505 - Consolidate the authorized client descriptor cookie computation
4506 code from client and service into one function. Closes
4509 o Code simplification and refactoring (shell scripts):
4510 - Cleanup scan-build.sh to silence shellcheck warnings. Closes
4512 - Fix issues that shellcheck found in chutney-git-bisect.sh.
4513 Resolves ticket 28006.
4514 - Fix issues that shellcheck found in updateRustDependencies.sh.
4515 Resolves ticket 28012.
4516 - Fix shellcheck warnings in cov-diff script. Resolves issue 28009.
4517 - Fix shellcheck warnings in run_calltool.sh. Resolves ticket 28011.
4518 - Fix shellcheck warnings in run_trunnel.sh. Resolves issue 28010.
4519 - Fix shellcheck warnings in scripts/test/coverage. Resolves
4523 Changes in version 0.3.5.8 - 2019-02-21
4524 Tor 0.3.5.8 backports several fixes from later releases, including fixes
4525 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
4528 It also includes a fix for a medium-severity security bug affecting Tor
4529 0.3.2.1-alpha and later. All Tor instances running an affected release
4530 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
4532 o Major bugfixes (cell scheduler, KIST, security):
4533 - Make KIST consider the outbuf length when computing what it can
4534 put in the outbuf. Previously, KIST acted as though the outbuf
4535 were empty, which could lead to the outbuf becoming too full. It
4536 is possible that an attacker could exploit this bug to cause a Tor
4537 client or relay to run out of memory and crash. Fixes bug 29168;
4538 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
4539 TROVE-2019-001 and CVE-2019-8955.
4541 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
4542 - Gracefully handle empty username/password fields in SOCKS5
4543 username/password auth messsage and allow SOCKS5 handshake to
4544 continue. Previously, we had rejected these handshakes, breaking
4545 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
4547 o Minor features (compilation, backport from 0.4.0.2-alpha):
4548 - Compile correctly when OpenSSL is built with engine support
4549 disabled, or with deprecated APIs disabled. Closes ticket 29026.
4550 Patches from "Mangix".
4552 o Minor features (geoip):
4553 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
4554 Country database. Closes ticket 29478.
4556 o Minor features (testing, backport from 0.4.0.2-alpha):
4557 - Treat all unexpected ERR and BUG messages as test failures. Closes
4560 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
4561 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
4562 connection waiting for a descriptor that we actually have in the
4563 cache. It turns out that this can actually happen, though it is
4564 rare. Now, tor will recover and retry the descriptor. Fixes bug
4565 28669; bugfix on 0.3.2.4-alpha.
4567 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
4568 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
4569 IPv6 socket was bound using an address family of AF_INET instead
4570 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
4573 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
4574 - Update Cargo.lock file to match the version made by the latest
4575 version of Rust, so that "make distcheck" will pass again. Fixes
4576 bug 29244; bugfix on 0.3.3.4-alpha.
4578 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
4579 - Select guards even if the consensus has expired, as long as the
4580 consensus is still reasonably live. Fixes bug 24661; bugfix
4583 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
4584 - Compile correctly on OpenBSD; previously, we were missing some
4585 headers required in order to detect it properly. Fixes bug 28938;
4586 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
4588 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
4589 - Describe the contents of the v3 onion service client authorization
4590 files correctly: They hold public keys, not private keys. Fixes
4591 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
4593 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
4594 - Rework rep_hist_log_link_protocol_counts() to iterate through all
4595 link protocol versions when logging incoming/outgoing connection
4596 counts. Tor no longer skips version 5, and we won't have to
4597 remember to update this function when new link protocol version is
4598 developed. Fixes bug 28920; bugfix on 0.2.6.10.
4600 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
4601 - Log more information at "warning" level when unable to read a
4602 private key; log more information at "info" level when unable to
4603 read a public key. We had warnings here before, but they were lost
4604 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
4606 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
4607 - The amount of total available physical memory is now determined
4608 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
4609 when it is defined and a 64-bit variant is not available. Fixes
4610 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
4612 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
4613 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
4614 than one private key for a hidden service. Fixes bug 29040; bugfix
4616 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
4617 "debug" level. Tor used to log it as a warning, which caused very
4618 long log lines to appear for some users. Fixes bug 29135; bugfix
4620 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
4621 as a warning. Instead, log it as a protocol warning, because there
4622 is nothing that relay operators can do to fix it. Fixes bug 29029;
4623 bugfix on 0.2.5.7-rc.
4625 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
4626 - Mark outdated dirservers when Tor only has a reasonably live
4627 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
4629 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
4630 - Detect and suppress "bug" warnings from the util/time test on
4631 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
4632 - Do not log an error-level message if we fail to find an IPv6
4633 network interface from the unit tests. Fixes bug 29160; bugfix
4636 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
4637 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
4638 Some users took this phrasing to mean that the mentioned guard was
4639 under their control or responsibility, which it is not. Fixes bug
4640 28895; bugfix on Tor 0.3.0.1-alpha.
4643 Changes in version 0.3.4.11 - 2019-02-21
4644 Tor 0.3.4.11 is the third stable release in its series. It includes
4645 a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
4646 later. All Tor instances running an affected release should upgrade to
4647 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
4649 o Major bugfixes (cell scheduler, KIST, security):
4650 - Make KIST consider the outbuf length when computing what it can
4651 put in the outbuf. Previously, KIST acted as though the outbuf
4652 were empty, which could lead to the outbuf becoming too full. It
4653 is possible that an attacker could exploit this bug to cause a Tor
4654 client or relay to run out of memory and crash. Fixes bug 29168;
4655 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
4656 TROVE-2019-001 and CVE-2019-8955.
4658 o Minor features (geoip):
4659 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
4660 Country database. Closes ticket 29478.
4662 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
4663 - Update Cargo.lock file to match the version made by the latest
4664 version of Rust, so that "make distcheck" will pass again. Fixes
4665 bug 29244; bugfix on 0.3.3.4-alpha.
4667 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
4668 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
4669 as a warning. Instead, log it as a protocol warning, because there
4670 is nothing that relay operators can do to fix it. Fixes bug 29029;
4671 bugfix on 0.2.5.7-rc.
4674 Changes in version 0.3.3.12 - 2019-02-21
4675 Tor 0.3.3.12 fixes a medium-severity security bug affecting Tor
4676 0.3.2.1-alpha and later. All Tor instances running an affected release
4677 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
4679 This release marks the end of support for the Tor 0.3.3.x series. We
4680 recommend that users switch to either the Tor 0.3.4 series (supported
4681 until at least 10 June 2019), or the Tor 0.3.5 series, which will
4682 receive long-term support until at least 1 Feb 2022.
4684 o Major bugfixes (cell scheduler, KIST, security):
4685 - Make KIST consider the outbuf length when computing what it can
4686 put in the outbuf. Previously, KIST acted as though the outbuf
4687 were empty, which could lead to the outbuf becoming too full. It
4688 is possible that an attacker could exploit this bug to cause a Tor
4689 client or relay to run out of memory and crash. Fixes bug 29168;
4690 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
4691 TROVE-2019-001 and CVE-2019-8955.
4693 o Minor features (geoip):
4694 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
4695 Country database. Closes ticket 29478.
4697 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
4698 - Update Cargo.lock file to match the version made by the latest
4699 version of Rust, so that "make distcheck" will pass again. Fixes
4700 bug 29244; bugfix on 0.3.3.4-alpha.
4702 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
4703 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
4704 as a warning. Instead, log it as a protocol warning, because there
4705 is nothing that relay operators can do to fix it. Fixes bug 29029;
4706 bugfix on 0.2.5.7-rc.
4709 Changes in version 0.3.3.11 - 2019-01-07
4710 Tor 0.3.3.11 backports numerous fixes from later versions of Tor.
4711 numerous fixes, including an important fix for anyone using OpenSSL
4712 1.1.1. Anyone running an earlier version of Tor 0.3.3 should upgrade
4713 to this version, or to a later series.
4715 As a reminder, support the Tor 0.3.3 series will end on 22 Feb 2019.
4716 We anticipate that this will be the last release of Tor 0.3.3, unless
4717 some major bug is before then. Some time between now and then, users
4718 should switch to either the Tor 0.3.4 series (supported until at least
4719 10 June 2019), or the Tor 0.3.5 series, which will receive long-term
4720 support until at least 1 Feb 2022.
4722 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
4723 - Fix our usage of named groups when running as a TLS 1.3 client in
4724 OpenSSL 1.1.1. Previously, we only initialized EC groups when
4725 running as a relay, which caused clients to fail to negotiate TLS
4726 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
4729 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
4730 - Fix a use-after-free error that could be caused by passing Tor an
4731 impossible set of options that would fail during options_act().
4732 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
4734 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
4735 - Only run one online rust build in Travis, to reduce network
4736 errors. Skip offline rust builds on Travis for Linux gcc, because
4737 they're redundant. Implements ticket 27252.
4738 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
4739 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
4740 Linux with default settings, because all the non-default builds
4741 use gcc on Linux. Implements ticket 27252.
4743 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
4744 - Use the Travis Homebrew addon to install packages on macOS during
4745 Travis CI. The package list is the same, but the Homebrew addon
4746 does not do a `brew update` by default. Implements ticket 27738.
4748 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
4749 - Replace the 150 fallbacks originally introduced in Tor
4750 0.3.3.1-alpha in January 2018 (of which ~115 were still
4751 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
4752 removed) generated in December 2018. Closes ticket 24803.
4754 o Minor features (geoip):
4755 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
4756 Country database. Closes ticket 29012.
4758 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
4759 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
4760 key export function from handling long labels. When this bug is
4761 detected, Tor will disable TLS 1.3. We recommend upgrading to a
4762 version of OpenSSL without this bug when it becomes available.
4763 Closes ticket 28973.
4765 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
4766 - Update relay descriptor on bandwidth changes only when the uptime
4767 is smaller than 24h, in order to reduce the efficiency of guard
4768 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
4770 o Minor bugfixes (C correctness, backport from 0.3.5.4-alpha):
4771 - Avoid undefined behavior in an end-of-string check when parsing
4772 the BEGIN line in a directory object. Fixes bug 28202; bugfix
4775 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
4776 - Rewrite our assertion macros so that they no longer suppress the
4777 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
4779 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
4780 - Initialize a variable unconditionally in aes_new_cipher(), since
4781 some compilers cannot tell that we always initialize it before
4782 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
4784 o Minor bugfixes (directory authority, backport from 0.3.5.4-alpha):
4785 - Log additional info when we get a relay that shares an ed25519 ID
4786 with a different relay, instead making a BUG() warning. Fixes bug
4787 27800; bugfix on 0.3.2.1-alpha.
4789 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
4790 - When a user requests a group-readable DataDirectory, give it to
4791 them. Previously, when the DataDirectory and the CacheDirectory
4792 were the same, the default setting (0) for
4793 CacheDirectoryGroupReadable would override the setting for
4794 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
4797 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
4798 - When the onion service directory can't be created or has the wrong
4799 permissions, do not log a stack trace. Fixes bug 27335; bugfix
4802 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
4803 - Close all SOCKS request (for the same .onion) if the newly fetched
4804 descriptor is unusable. Before that, we would close only the first
4805 one leaving the other hanging and let to time out by themselves.
4806 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
4808 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
4809 - Don't warn so loudly when Tor is unable to decode an onion
4810 descriptor. This can now happen as a normal use case if a client
4811 gets a descriptor with client authorization but the client is not
4812 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
4814 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
4815 - When deleting an ephemeral onion service (DEL_ONION), do not close
4816 any rendezvous circuits in order to let the existing client
4817 connections finish by themselves or closed by the application. The
4818 HS v2 is doing that already so now we have the same behavior for
4819 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
4821 o Minor bugfixes (HTTP tunnel):
4822 - Fix a bug warning when closing an HTTP tunnel connection due to
4823 an HTTP request we couldn't handle. Fixes bug 26470; bugfix on
4826 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
4827 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
4828 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
4830 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
4831 - Ensure circuitmux queues are empty before scheduling or sending
4832 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
4834 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
4835 - Reject protocol names containing bytes other than alphanumeric
4836 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
4839 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
4840 - Compute protover votes correctly in the rust version of the
4841 protover code. Previously, the protover rewrite in 24031 allowed
4842 repeated votes from the same voter for the same protocol version
4843 to be counted multiple times in protover_compute_vote(). Fixes bug
4844 27649; bugfix on 0.3.3.5-rc.
4845 - Reject protover names that contain invalid characters. Fixes bug
4846 27687; bugfix on 0.3.3.1-alpha.
4848 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
4849 - protover_all_supported() would attempt to allocate up to 16GB on
4850 some inputs, leading to a potential memory DoS. Fixes bug 27206;
4851 bugfix on 0.3.3.5-rc.
4853 o Minor bugfixes (rust, backport from 0.3.5.4-alpha):
4854 - Fix a potential null dereference in protover_all_supported(). Add
4855 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
4856 - Return a string that can be safely freed by C code, not one
4857 created by the rust allocator, in protover_all_supported(). Fixes
4858 bug 27740; bugfix on 0.3.3.1-alpha.
4859 - Fix an API mismatch in the rust implementation of
4860 protover_compute_vote(). This bug could have caused crashes on any
4861 directory authorities running Tor with Rust (which we do not yet
4862 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
4864 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
4865 - If a unit test running in a subprocess exits abnormally or with a
4866 nonzero status code, treat the test as having failed, even if the
4867 test reported success. Without this fix, memory leaks don't cause
4868 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
4869 bugfix on 0.2.2.4-alpha.
4871 o Minor bugfixes (testing, backport from 0.3.5.4-alpha):
4872 - Treat backtrace test failures as expected on BSD-derived systems
4873 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
4874 (FreeBSD failures have been treated as expected since 18204 in
4875 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
4877 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
4878 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
4879 bugfix on 0.3.0.1-alpha.
4882 Changes in version 0.3.4.10 - 2019-01-07
4883 Tor 0.3.4.9 is the second stable release in its series; it backports
4884 numerous fixes, including an important fix for relays, and for anyone
4885 using OpenSSL 1.1.1. Anyone running an earlier version of Tor 0.3.4
4888 As a reminder, the Tor 0.3.4 series will be supported until 10 June
4889 2019. Some time between now and then, users should switch to the Tor
4890 0.3.5 series, which will receive long-term support until at least 1
4893 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
4894 - Fix our usage of named groups when running as a TLS 1.3 client in
4895 OpenSSL 1.1.1. Previously, we only initialized EC groups when
4896 running as a relay, which caused clients to fail to negotiate TLS
4897 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
4900 o Major bugfixes (relay, directory, backport from 0.3.5.7):
4901 - Always reactivate linked connections in the main loop so long as
4902 any linked connection has been active. Previously, connections
4903 serving directory information wouldn't get reactivated after the
4904 first chunk of data was sent (usually 32KB), which would prevent
4905 clients from bootstrapping. Fixes bug 28912; bugfix on
4906 0.3.4.1-alpha. Patch by "cypherpunks3".
4908 o Minor features (continuous integration, Windows, backport from 0.3.5.6-rc):
4909 - Always show the configure and test logs, and upload them as build
4910 artifacts, when building for Windows using Appveyor CI.
4913 o Minor features (controller, backport from 0.3.5.1-alpha):
4914 - For purposes of CIRC_BW-based dropped cell detection, track half-
4915 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
4916 bias check cells to arrive without counting it as dropped until
4917 either the END arrives, or the windows are empty. Closes
4920 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
4921 - Replace the 150 fallbacks originally introduced in Tor
4922 0.3.3.1-alpha in January 2018 (of which ~115 were still
4923 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
4924 removed) generated in December 2018. Closes ticket 24803.
4926 o Minor features (geoip):
4927 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
4928 Country database. Closes ticket 28395.
4930 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
4931 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
4932 key export function from handling long labels. When this bug is
4933 detected, Tor will disable TLS 1.3. We recommend upgrading to a
4934 version of OpenSSL without this bug when it becomes available.
4935 Closes ticket 28973.
4937 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
4938 - Initialize a variable unconditionally in aes_new_cipher(), since
4939 some compilers cannot tell that we always initialize it before
4940 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
4942 o Minor bugfixes (connection, relay, backport from 0.3.5.5-alpha):
4943 - Avoid a logging a BUG() stacktrace when closing connection held
4944 open because the write side is rate limited but not the read side.
4945 Now, the connection read side is simply shut down until Tor is
4946 able to flush the connection and close it. Fixes bug 27750; bugfix
4949 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.5-alpha):
4950 - Manually configure the zstd compiler options, when building using
4951 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
4952 not come with a pkg-config file. Fixes bug 28454; bugfix
4954 - Stop using an external OpenSSL install, and stop installing MSYS2
4955 packages, when building using mingw on Appveyor Windows CI. Fixes
4956 bug 28399; bugfix on 0.3.4.1-alpha.
4958 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.6-rc):
4959 - Explicitly specify the path to the OpenSSL library and do not
4960 download OpenSSL from Pacman, but instead use the library that is
4961 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
4963 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
4964 - When a user requests a group-readable DataDirectory, give it to
4965 them. Previously, when the DataDirectory and the CacheDirectory
4966 were the same, the default setting (0) for
4967 CacheDirectoryGroupReadable would override the setting for
4968 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
4971 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
4972 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
4973 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
4975 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
4976 - Don't warn so loudly when Tor is unable to decode an onion
4977 descriptor. This can now happen as a normal use case if a client
4978 gets a descriptor with client authorization but the client is not
4979 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
4981 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
4982 - When deleting an ephemeral onion service (DEL_ONION), do not close
4983 any rendezvous circuits in order to let the existing client
4984 connections finish by themselves or closed by the application. The
4985 HS v2 is doing that already so now we have the same behavior for
4986 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
4988 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
4989 - Update relay descriptor on bandwidth changes only when the uptime
4990 is smaller than 24h, in order to reduce the efficiency of guard
4991 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
4993 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
4994 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
4995 bugfix on 0.3.0.1-alpha.
4998 Changes in version 0.3.5.7 - 2019-01-07
4999 Tor 0.3.5.7 is the first stable release in its series; it includes
5000 compilation and portability fixes, and a fix for a severe problem
5001 affecting directory caches.
5003 The Tor 0.3.5 series includes several new features and performance
5004 improvements, including client authorization for v3 onion services,
5005 cleanups to bootstrap reporting, support for improved bandwidth-
5006 measurement tools, experimental support for NSS in place of OpenSSL,
5007 and much more. It also begins a full reorganization of Tor's code
5008 layout, for improved modularity and maintainability in the future.
5009 Finally, there is the usual set of performance improvements and
5010 bugfixes that we try to do in every release series.
5012 There are a couple of changes in the 0.3.5 that may affect
5013 compatibility. First, the default version for newly created onion
5014 services is now v3. Use the HiddenServiceVersion option if you want to
5015 override this. Second, some log messages related to bootstrapping have
5016 changed; if you use stem, you may need to update to the latest version
5017 so it will recognize them.
5019 We have designated 0.3.5 as a "long-term support" (LTS) series: we
5020 will continue to patch major bugs in typical configurations of 0.3.5
5021 until at least 1 Feb 2022. (We do not plan to provide long-term
5022 support for embedding, Rust support, NSS support, running a directory
5023 authority, or unsupported platforms. For these, you will need to stick
5024 with the latest stable release.)
5026 Below are the changes since 0.3.4.9. For a complete list of changes
5027 since 0.3.5.6-rc, see the ChangeLog file.
5029 o Major features (bootstrap):
5030 - Don't report directory progress until after a connection to a
5031 relay or bridge has succeeded. Previously, we'd report 80%
5032 progress based on cached directory information when we couldn't
5033 even connect to the network. Closes ticket 27169.
5035 o Major features (new code layout):
5036 - Nearly all of Tor's source code has been moved around into more
5037 logical places. The "common" directory is now divided into a set
5038 of libraries in "lib", and files in the "or" directory have been
5039 split into "core" (logic absolutely needed for onion routing),
5040 "feature" (independent modules in Tor), and "app" (to configure
5041 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
5042 more information. Closes ticket 26481.
5044 This refactoring is not complete: although the libraries have been
5045 refactored to be acyclic, the main body of Tor is still too
5046 interconnected. We will attempt to improve this in the future.
5048 o Major features (onion services v3):
5049 - Implement onion service client authorization at the descriptor
5050 level: only authorized clients can decrypt a service's descriptor
5051 to find out how to contact it. A new torrc option was added to
5052 control this client side: ClientOnionAuthDir <path>. On the
5053 service side, if the "authorized_clients/" directory exists in the
5054 onion service directory path, client configurations are read from
5055 the files within. See the manpage for more details. Closes ticket
5056 27547. Patch done by Suphanat Chunhapanya (haxxpop).
5057 - Improve revision counter generation in next-gen onion services.
5058 Onion services can now scale by hosting multiple instances on
5059 different hosts without synchronization between them, which was
5060 previously impossible because descriptors would get rejected by
5061 HSDirs. Addresses ticket 25552.
5062 - Version 3 onion services can now use the per-service
5063 HiddenServiceExportCircuitID option to differentiate client
5064 circuits. It communicates with the service by using the HAProxy
5065 protocol to assign virtual IP addresses to inbound client
5066 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
5068 o Major features (onion services, UI change):
5069 - For a newly created onion service, the default version is now 3.
5070 Tor still supports existing version 2 services, but the operator
5071 now needs to set "HiddenServiceVersion 2" in order to create a new
5072 version 2 service. For existing services, Tor now learns the
5073 version by reading the key file. Closes ticket 27215.
5075 o Major features (portability, cryptography, experimental, TLS):
5076 - Tor now has the option to compile with the NSS library instead of
5077 OpenSSL. This feature is experimental, and we expect that bugs may
5078 remain. It is mainly intended for environments where Tor's
5079 performance is not CPU-bound, and where NSS is already known to be
5080 installed. To try it out, configure Tor with the --enable-nss
5081 flag. Closes tickets 26631, 26815, and 26816.
5083 If you are experimenting with this option and using an old cached
5084 consensus, Tor may fail to start. To solve this, delete your
5085 "cached-consensus" and "cached-microdesc-consensus" files,
5086 (if present), and restart Tor.
5088 o Major features (relay, UI change):
5089 - Relays no longer run as exits by default. If the "ExitRelay"
5090 option is auto (or unset), and no exit policy is specified with
5091 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
5092 Previously in this case, we allowed exit traffic and logged a
5093 warning message. Closes ticket 21530. Patch by Neel Chauhan.
5094 - Tor now validates that the ContactInfo config option is valid UTF-
5095 8 when parsing torrc. Closes ticket 27428.
5097 o Major bugfixes (compilation):
5098 - Fix compilation on ARM (and other less-used CPUs) when compiling
5099 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
5101 o Major bugfixes (compilation, rust):
5102 - Rust tests can now build and run successfully with the
5103 --enable-fragile-hardening option enabled. Doing this currently
5104 requires the rust beta channel; it will be possible with stable
5105 rust once Rust version 1.31 is released. Patch from Alex Crichton.
5106 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
5108 o Major bugfixes (directory authority):
5109 - Actually check that the address we get from DirAuthority
5110 configuration line is valid IPv4. Explicitly disallow DirAuthority
5111 address to be a DNS hostname. Fixes bug 26488; bugfix
5114 o Major bugfixes (embedding, main loop):
5115 - When DisableNetwork becomes set, actually disable periodic events
5116 that are already enabled. (Previously, we would refrain from
5117 enabling new ones, but we would leave the old ones turned on.)
5118 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
5120 o Major bugfixes (main loop, bootstrap):
5121 - Make sure Tor bootstraps and works properly if only the
5122 ControlPort is set. Prior to this fix, Tor would only bootstrap
5123 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
5124 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
5126 o Major bugfixes (onion service v3):
5127 - On an intro point for a version 3 onion service, stop closing
5128 introduction circuits on a NACK. This lets the client decide
5129 whether to reuse the circuit or discard it. Previously, we closed
5130 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
5131 0.3.2.1-alpha. Patch by Neel Chaunan.
5133 o Major bugfixes (OpenSSL, portability):
5134 - Fix our usage of named groups when running as a TLS 1.3 client in
5135 OpenSSL 1.1.1. Previously, we only initialized EC groups when
5136 running as a relay, which caused clients to fail to negotiate TLS
5137 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
5140 o Major bugfixes (relay bandwidth statistics):
5141 - When we close relayed circuits, report the data in the circuit
5142 queues as being written in our relay bandwidth stats. This
5143 mitigates guard discovery and other attacks that close circuits
5144 for the explicit purpose of noticing this discrepancy in
5145 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
5147 o Major bugfixes (relay):
5148 - When our write bandwidth limit is exhausted, stop writing on the
5149 connection. Previously, we had a typo in the code that would make
5150 us stop reading instead, leading to relay connections being stuck
5151 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
5153 - Always reactivate linked connections in the main loop so long as
5154 any linked connection has been active. Previously, connections
5155 serving directory information wouldn't get reactivated after the
5156 first chunk of data was sent (usually 32KB), which would prevent
5157 clients from bootstrapping. Fixes bug 28912; bugfix on
5158 0.3.4.1-alpha. Patch by "cypherpunks3".
5160 o Major bugfixes (restart-in-process):
5161 - Fix a use-after-free error that could be caused by passing Tor an
5162 impossible set of options that would fail during options_act().
5163 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
5165 o Minor features (admin tools):
5166 - Add a new --key-expiration option to print the expiration date of
5167 the signing cert in an ed25519_signing_cert file. Resolves
5170 o Minor features (build):
5171 - If you pass the "--enable-pic" option to configure, Tor will try
5172 to tell the compiler to build position-independent code suitable
5173 to link into a dynamic library. (The default remains -fPIE, for
5174 code suitable for a relocatable executable.) Closes ticket 23846.
5176 o Minor features (code correctness, testing):
5177 - Tor's build process now includes a "check-includes" make target to
5178 verify that no module of Tor relies on any headers from a higher-
5179 level module. We hope to use this feature over time to help
5180 refactor our codebase. Closes ticket 26447.
5182 o Minor features (code layout):
5183 - We have a new "lowest-level" error-handling API for use by code
5184 invoked from within the logging module. With this interface, the
5185 logging code is no longer at risk of calling into itself if a
5186 failure occurs while it is trying to log something. Closes
5189 o Minor features (compilation):
5190 - When possible, place our warning flags in a separate file, to
5191 avoid flooding verbose build logs. Closes ticket 28924.
5192 - Tor's configure script now supports a --with-malloc= option to
5193 select your malloc implementation. Supported options are
5194 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
5195 default). Addresses part of ticket 20424. Based on a patch from
5198 o Minor features (config):
5199 - The "auto" keyword in torrc is now case-insensitive. Closes
5202 o Minor features (continuous integration):
5203 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
5205 - Add new CI job to Travis configuration to run stem-based
5206 integration tests. Closes ticket 27913.
5207 - Use the Travis Homebrew addon to install packages on macOS during
5208 Travis CI. The package list is the same, but the Homebrew addon
5209 does not do a `brew update` by default. Implements ticket 27738.
5210 - Report what program produced the mysterious core file that we
5211 occasionally see on Travis CI during make distcheck. Closes
5213 - Don't do a distcheck with --disable-module-dirauth in Travis.
5214 Implements ticket 27252.
5215 - Install libcap-dev and libseccomp2-dev so these optional
5216 dependencies get tested on Travis CI. Closes ticket 26560.
5217 - Only run one online rust build in Travis, to reduce network
5218 errors. Skip offline rust builds on Travis for Linux gcc, because
5219 they're redundant. Implements ticket 27252.
5220 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
5221 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
5222 Linux with default settings, because all the non-default builds
5223 use gcc on Linux. Implements ticket 27252.
5225 o Minor features (continuous integration, Windows):
5226 - Always show the configure and test logs, and upload them as build
5227 artifacts, when building for Windows using Appveyor CI.
5229 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
5230 Appveyor's CI. Closes ticket 28318.
5232 o Minor features (controller):
5233 - Emit CIRC_BW events as soon as we detect that we processed an
5234 invalid or otherwise dropped cell on a circuit. This allows
5235 vanguards and other controllers to react more quickly to dropped
5236 cells. Closes ticket 27678.
5237 - For purposes of CIRC_BW-based dropped cell detection, track half-
5238 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
5239 bias check cells to arrive without counting it as dropped until
5240 either the END arrives, or the windows are empty. Closes
5242 - Implement a 'GETINFO md/all' controller command to enable getting
5243 all known microdescriptors. Closes ticket 8323.
5244 - The GETINFO command now support an "uptime" argument, to return
5245 Tor's uptime in seconds. Closes ticket 25132.
5247 o Minor features (denial-of-service avoidance):
5248 - Make our OOM handler aware of the DNS cache so that it doesn't
5249 fill up the memory. This check is important for our DoS mitigation
5250 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
5252 o Minor features (development):
5253 - Tor's makefile now supports running the "clippy" Rust style tool
5254 on our Rust code. Closes ticket 22156.
5256 o Minor features (directory authority):
5257 - There is no longer an artificial upper limit on the length of
5258 bandwidth lines. Closes ticket 26223.
5259 - When a bandwidth file is used to obtain the bandwidth measurements,
5260 include this bandwidth file headers in the votes. Closes
5262 - Improved support for networks with only a single authority or a
5263 single fallback directory. Patch from Gabriel Somlo. Closes
5266 o Minor features (embedding API):
5267 - The Tor controller API now supports a function to launch Tor with
5268 a preconstructed owning controller FD, so that embedding
5269 applications don't need to manage controller ports and
5270 authentication. Closes ticket 24204.
5271 - The Tor controller API now has a function that returns the name
5272 and version of the backend implementing the API. Closes
5275 o Minor features (fallback directory list):
5276 - Replace the 150 fallbacks originally introduced in Tor
5277 0.3.3.1-alpha in January 2018 (of which ~115 were still
5278 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
5279 removed) generated in December 2018. Closes ticket 24803.
5281 o Minor features (geoip):
5282 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
5283 Country database. Closes ticket 29012.
5285 o Minor features (memory management):
5286 - Get Libevent to use the same memory allocator as Tor, by calling
5287 event_set_mem_functions() during initialization. Resolves
5290 o Minor features (memory usage):
5291 - When not using them, store legacy TAP public onion keys in DER-
5292 encoded format, rather than as expanded public keys. This should
5293 save several megabytes on typical clients. Closes ticket 27246.
5295 o Minor features (OpenSSL bug workaround):
5296 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
5297 key export function from handling long labels. When this bug is
5298 detected, Tor will disable TLS 1.3. We recommend upgrading to a
5299 version of OpenSSL without this bug when it becomes available.
5300 Closes ticket 28973.
5302 o Minor features (OpenSSL):
5303 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
5304 than our own. Resolves ticket 19979.
5306 o Minor features (performance):
5307 - Remove about 96% of the work from the function that we run at
5308 startup to test our curve25519_basepoint implementation. Since
5309 this function has yet to find an actual failure, we now only run
5310 it for 8 iterations instead of 200. Based on our profile
5311 information, this change should save around 8% of our startup time
5312 on typical desktops, and may have a similar effect on other
5313 platforms. Closes ticket 28838.
5314 - Stop re-validating our hardcoded Diffie-Hellman parameters on
5315 every startup. Doing this wasted time and cycles, especially on
5316 low-powered devices. Closes ticket 28851.
5318 o Minor features (Rust, code quality):
5319 - Improve rust code quality in the rust protover implementation by
5320 making it more idiomatic. Includes changing an internal API to
5321 take &str instead of &String. Closes ticket 26492.
5323 o Minor features (testing):
5324 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
5325 chutney. Implements ticket 27211.
5327 o Minor features (tor-resolve):
5328 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
5329 Side-effect of the refactoring for ticket 26526.
5331 o Minor features (UI):
5332 - Log each included configuration file or directory as we read it,
5333 to provide more visibility about where Tor is reading from. Patch
5334 from Unto Sten; closes ticket 27186.
5335 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
5336 Closes ticket 26703.
5338 o Minor bugfixes (32-bit OSX and iOS, timing):
5339 - Fix an integer overflow bug in our optimized 32-bit millisecond-
5340 difference algorithm for 32-bit Apple platforms. Previously, it
5341 would overflow when calculating the difference between two times
5342 more than 47 days apart. Fixes part of bug 27139; bugfix
5344 - Improve the precision of our 32-bit millisecond difference
5345 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
5346 bugfix on 0.3.4.1-alpha.
5347 - Relax the tolerance on the mainloop/update_time_jumps test when
5348 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
5351 o Minor bugfixes (bootstrap):
5352 - Try harder to get descriptors in non-exit test networks, by using
5353 the mid weight for the third hop when there are no exits. Fixes
5354 bug 27237; bugfix on 0.2.6.2-alpha.
5356 o Minor bugfixes (C correctness):
5357 - Avoid casting smartlist index to int implicitly, as it may trigger
5358 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
5359 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
5360 - Use time_t for all values in
5361 predicted_ports_prediction_time_remaining(). Rework the code that
5362 computes difference between durations/timestamps. Fixes bug 27165;
5363 bugfix on 0.3.1.1-alpha.
5365 o Minor bugfixes (client, memory usage):
5366 - When not running as a directory cache, there is no need to store
5367 the text of the current consensus networkstatus in RAM.
5368 Previously, however, clients would store it anyway, at a cost of
5369 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
5372 o Minor bugfixes (client, ReachableAddresses):
5373 - Instead of adding a "reject *:*" line to ReachableAddresses when
5374 loading the configuration, add one to the policy after parsing it
5375 in parse_reachable_addresses(). This prevents extra "reject *.*"
5376 lines from accumulating on reloads. Fixes bug 20874; bugfix on
5377 0.1.1.5-alpha. Patch by Neel Chauhan.
5379 o Minor bugfixes (code quality):
5380 - Rename sandbox_getaddrinfo() and other functions to no longer
5381 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
5382 bugfix on 0.2.7.1-alpha.
5384 o Minor bugfixes (code safety):
5385 - Rewrite our assertion macros so that they no longer suppress the
5386 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
5389 o Minor bugfixes (compilation):
5390 - Initialize a variable unconditionally in aes_new_cipher(), since
5391 some compilers cannot tell that we always initialize it before
5392 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
5394 o Minor bugfixes (configuration):
5395 - Refuse to start with relative file paths and RunAsDaemon set
5396 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
5399 o Minor bugfixes (configuration, Onion Services):
5400 - In rend_service_parse_port_config(), disallow any input to remain
5401 after address-port pair was parsed. This will catch address and
5402 port being whitespace-separated by mistake of the user. Fixes bug
5403 27044; bugfix on 0.2.9.10.
5405 o Minor bugfixes (connection, relay):
5406 - Avoid a logging a BUG() stacktrace when closing connection held
5407 open because the write side is rate limited but not the read side.
5408 Now, the connection read side is simply shut down until Tor is
5409 able to flush the connection and close it. Fixes bug 27750; bugfix
5412 o Minor bugfixes (continuous integration, Windows):
5413 - Stop reinstalling identical packages in our Windows CI. Fixes bug
5414 27464; bugfix on 0.3.4.1-alpha.
5415 - Install only the necessary mingw packages during our appveyor
5416 builds. This change makes the build a little faster, and prevents
5417 a conflict with a preinstalled mingw openssl that appveyor now
5418 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
5419 - Explicitly specify the path to the OpenSSL library and do not
5420 download OpenSSL from Pacman, but instead use the library that is
5421 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
5422 - Manually configure the zstd compiler options, when building using
5423 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
5424 not come with a pkg-config file. Fixes bug 28454; bugfix
5426 - Stop using an external OpenSSL install, and stop installing MSYS2
5427 packages, when building using mingw on Appveyor Windows CI. Fixes
5428 bug 28399; bugfix on 0.3.4.1-alpha.
5430 o Minor bugfixes (controller):
5431 - Consider all routerinfo errors other than "not a server" to be
5432 transient for the purpose of "GETINFO exit-policy/*" controller
5433 request. Print stacktrace in the unlikely case of failing to
5434 recompute routerinfo digest. Fixes bug 27034; bugfix
5437 o Minor bugfixes (correctness):
5438 - Fix an unreached code path where we checked the value of
5439 "hostname" inside send_resolved_hostname_cell(). Previously, we
5440 used it before checking it; now we check it first. Fixes bug
5441 28879; bugfix on 0.1.2.7-alpha.
5443 o Minor bugfixes (directory connection shutdown):
5444 - Avoid a double-close when shutting down a stalled directory
5445 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
5447 o Minor bugfixes (directory permissions):
5448 - When a user requests a group-readable DataDirectory, give it to
5449 them. Previously, when the DataDirectory and the CacheDirectory
5450 were the same, the default setting (0) for
5451 CacheDirectoryGroupReadable would override the setting for
5452 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
5455 o Minor bugfixes (HTTP tunnel):
5456 - Fix a bug warning when closing an HTTP tunnel connection due to an
5457 HTTP request we couldn't handle. Fixes bug 26470; bugfix
5460 o Minor bugfixes (ipv6):
5461 - In addrs_in_same_network_family(), we choose the subnet size based
5462 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
5463 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
5464 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
5466 o Minor bugfixes (Linux seccomp2 sandbox):
5467 - Permit the "shutdown()" system call, which is apparently used by
5468 OpenSSL under some circumstances. Fixes bug 28183; bugfix
5471 o Minor bugfixes (logging):
5472 - Stop talking about the Named flag in log messages. Clients have
5473 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
5475 - As a precaution, do an early return from log_addr_has_changed() if
5476 Tor is running as client. Also, log a stack trace for debugging as
5477 this function should only be called when Tor runs as server. Fixes
5478 bug 26892; bugfix on 0.1.1.9-alpha.
5479 - Refrain from mentioning bug 21018 in the logs, as it is already
5480 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
5482 o Minor bugfixes (logging, documentation):
5483 - When SafeLogging is enabled, scrub IP address in
5484 channel_tls_process_netinfo_cell(). Also, add a note to manpage
5485 that scrubbing is not guaranteed on loglevels below Notice. Fixes
5486 bug 26882; bugfix on 0.2.4.10-alpha.
5488 o Minor bugfixes (memory leaks):
5489 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
5490 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
5491 - Fix a small memory leak when calling Tor with --dump-config. Fixes
5492 bug 27893; bugfix on 0.3.2.1-alpha.
5494 o Minor bugfixes (netflow padding):
5495 - Ensure circuitmux queues are empty before scheduling or sending
5496 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
5498 o Minor bugfixes (onion service v2):
5499 - Log at level "info", not "warning", in the case that we do not
5500 have a consensus when a .onion request comes in. This can happen
5501 normally while bootstrapping. Fixes bug 27040; bugfix
5504 o Minor bugfixes (onion service v3):
5505 - When deleting an ephemeral onion service (DEL_ONION), do not close
5506 any rendezvous circuits in order to let the existing client
5507 connections finish by themselves or closed by the application. The
5508 HS v2 is doing that already so now we have the same behavior for
5509 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
5510 - Build the service descriptor's signing key certificate before
5511 uploading, so we always have a fresh one: leaving no chances for
5512 it to expire service side. Fixes bug 27838; bugfix
5514 - Stop dumping a stack trace when trying to connect to an intro
5515 point without having a descriptor for it. Fixes bug 27774; bugfix
5517 - When selecting a v3 rendezvous point, don't only look at the
5518 protover, but also check whether the curve25519 onion key is
5519 present. This way we avoid picking a relay that supports the v3
5520 rendezvous but for which we don't have the microdescriptor. Fixes
5521 bug 27797; bugfix on 0.3.2.1-alpha.
5522 - Close all SOCKS request (for the same .onion) if the newly fetched
5523 descriptor is unusable. Before that, we would close only the first
5524 one leaving the other hanging and let to time out by themselves.
5525 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
5526 - When the onion service directory can't be created or has the wrong
5527 permissions, do not log a stack trace. Fixes bug 27335; bugfix
5529 - When replacing a descriptor in the client cache, make sure to
5530 close all client introduction circuits for the old descriptor, so
5531 we don't end up with unusable leftover circuits. Fixes bug 27471;
5532 bugfix on 0.3.2.1-alpha.
5534 o Minor bugfixes (OS compatibility):
5535 - Properly handle configuration changes that move a listener to/from
5536 wildcard IP address. If the first attempt to bind a socket fails,
5537 close the old listener and try binding the socket again. Fixes bug
5538 17873; bugfix on 0.0.8pre-1.
5540 o Minor bugfixes (performance)::
5541 - Rework node_is_a_configured_bridge() to no longer call
5542 node_get_all_orports(), which was performing too many memory
5543 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
5545 o Minor bugfixes (protover):
5546 - Reject protocol names containing bytes other than alphanumeric
5547 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
5550 o Minor bugfixes (protover, rust):
5551 - Reject extra commas in version strings. Fixes bug 27197; bugfix
5553 - protover_all_supported() would attempt to allocate up to 16GB on
5554 some inputs, leading to a potential memory DoS. Fixes bug 27206;
5555 bugfix on 0.3.3.5-rc.
5556 - Compute protover votes correctly in the rust version of the
5557 protover code. Previously, the protover rewrite in 24031 allowed
5558 repeated votes from the same voter for the same protocol version
5559 to be counted multiple times in protover_compute_vote(). Fixes bug
5560 27649; bugfix on 0.3.3.5-rc.
5561 - Reject protover names that contain invalid characters. Fixes bug
5562 27687; bugfix on 0.3.3.1-alpha.
5564 o Minor bugfixes (relay shutdown, systemd):
5565 - Notify systemd of ShutdownWaitLength so it can be set to longer
5566 than systemd's TimeoutStopSec. In Tor's systemd service file, set
5567 TimeoutSec to 60 seconds to allow Tor some time to shut down.
5568 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
5570 o Minor bugfixes (relay statistics):
5571 - Update relay descriptor on bandwidth changes only when the uptime
5572 is smaller than 24h, in order to reduce the efficiency of guard
5573 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
5575 o Minor bugfixes (relay):
5576 - Consider the fact that we'll be making direct connections to our
5577 entry and guard nodes when computing the fraction of nodes that
5578 have their descriptors. Also, if we are using bridges and there is
5579 at least one bridge with a full descriptor, treat the fraction of
5580 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
5581 Patch by Neel Chauhan.
5582 - Update the message logged on relays when DirCache is disabled.
5583 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
5584 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
5586 o Minor bugfixes (testing):
5587 - Stop running stem's unit tests as part of "make test-stem", but
5588 continue to run stem's unit and online tests during "make test-
5589 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
5590 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
5591 bugfix on 0.3.0.1-alpha.
5592 - Make the hs_service tests use the same time source when creating
5593 the introduction point and when testing it. Now tests work better
5594 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
5596 - Revise the "conditionvar_timeout" test so that it succeeds even on
5597 heavily loaded systems where the test threads are not scheduled
5598 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
5599 - Fix two unit tests to work when HOME environment variable is not
5600 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
5601 - If a unit test running in a subprocess exits abnormally or with a
5602 nonzero status code, treat the test as having failed, even if the
5603 test reported success. Without this fix, memory leaks don't cause
5604 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
5605 bugfix on 0.2.2.4-alpha.
5606 - When logging a version mismatch in our openssl_version tests,
5607 report the actual offending version strings. Fixes bug 26152;
5608 bugfix on 0.2.9.1-alpha.
5609 - Fix forking tests on Windows when there is a space somewhere in
5610 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
5612 o Minor bugfixes (Windows):
5613 - Correctly identify Windows 8.1, Windows 10, and Windows Server
5614 2008 and later from their NT versions. Fixes bug 28096; bugfix on
5615 0.2.2.34; reported by Keifer Bly.
5616 - On recent Windows versions, the GetVersionEx() function may report
5617 an earlier Windows version than the running OS. To avoid user
5618 confusion, add "[or later]" to Tor's version string on affected
5619 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
5621 - Remove Windows versions that were never supported by the
5622 GetVersionEx() function. Stop duplicating the latest Windows
5623 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
5624 reported by Keifer Bly.
5626 o Code simplification and refactoring:
5627 - When parsing a port configuration, make it more obvious to static
5628 analyzer tools that we always initialize the address. Closes
5630 - Divide more large Tor source files -- especially ones that span
5631 multiple areas of functionality -- into smaller parts, including
5632 onion.c and main.c. Closes ticket 26747.
5633 - Divide the "routerparse.c" module into separate modules for each
5634 group of parsed objects. Closes ticket 27924.
5635 - Move protover_rust.c to the same place protover.c was moved to.
5636 Closes ticket 27814.
5637 - Split directory.c into separate pieces for client, server, and
5638 common functionality. Closes ticket 26744.
5639 - Split the non-statistics-related parts from the rephist.c and
5640 geoip.c modules. Closes ticket 27892.
5641 - Split the router.c file into relay-only and shared components, to
5642 help with future modularization. Closes ticket 27864.
5643 - Divide the routerlist.c and dirserv.c modules into smaller parts.
5644 Closes ticket 27799.
5645 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
5646 longer needed. Closes ticket 26502.
5647 - Include paths to header files within Tor are now qualified by
5648 directory within the top-level src directory.
5649 - Many structures have been removed from the centralized "or.h"
5650 header, and moved into their own headers. This will allow us to
5651 reduce the number of places in the code that rely on each
5652 structure's contents and layout. Closes ticket 26383.
5653 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
5654 - Remove GetAdaptersAddresses_fn_t. The code that used it was
5655 removed as part of the 26481 refactor. Closes ticket 27467.
5656 - Rework Tor SOCKS server code to use Trunnel and benefit from
5657 autogenerated functions for parsing and generating SOCKS wire
5658 format. New implementation is cleaner, more maintainable and
5659 should be less prone to heartbleed-style vulnerabilities.
5660 Implements a significant fraction of ticket 3569.
5661 - Split sampled_guards_update_from_consensus() and
5662 select_entry_guard_for_circuit() into subfunctions. In
5663 entry_guards_update_primary() unite three smartlist enumerations
5664 into one and move smartlist comparison code out of the function.
5665 Closes ticket 21349.
5666 - Tor now assumes that you have standards-conformant stdint.h and
5667 inttypes.h headers when compiling. Closes ticket 26626.
5668 - Unify our bloom filter logic. Previously we had two copies of this
5669 code: one for routerlist filtering, and one for address set
5670 calculations. Closes ticket 26510.
5671 - Use the simpler strcmpstart() helper in
5672 rend_parse_v2_service_descriptor instead of strncmp(). Closes
5674 - Utility functions that can perform a DNS lookup are now wholly
5675 separated from those that can't, in separate headers and C
5676 modules. Closes ticket 26526.
5679 - In the tor-resolve(1) manpage, fix the reference to socks-
5680 extensions.txt by adding a web URL. Resolves ticket 27853.
5681 - Mention that we require Python to be 2.7 or newer for some
5682 integration tests that we ship with Tor. Resolves ticket 27677.
5683 - Copy paragraph and URL to Tor's code of conduct document from
5684 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
5685 - Remove old instructions from INSTALL document. Closes ticket 26588.
5686 - Warn users that they should not include MyFamily line(s) in their
5687 torrc when running Tor bridge. Closes ticket 26908.
5690 - Tor no longer supports building with the dmalloc library. For
5691 debugging memory issues, we suggest using gperftools or msan
5692 instead. Closes ticket 26426.
5693 - Tor no longer attempts to run on Windows environments without the
5694 GetAdaptersAddresses() function. This function has existed since
5695 Windows XP, which is itself already older than we support.
5696 - Remove Tor2web functionality for version 2 onion services. The
5697 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
5698 (This feature was never shipped in vanilla Tor and it was only
5699 possible to use this feature by building the support at compile
5700 time. Tor2webMode is not implemented for version 3 onion services.)
5701 Closes ticket 26367.
5704 - Increase logging and tag all log entries with timestamps in
5705 test_rebind.py. Provides diagnostics for issue 28229.
5707 o Code simplification and refactoring (shared random, dirauth):
5708 - Change many tor_assert() to use BUG() instead. The idea is to not
5709 crash a dirauth but rather scream loudly with a stacktrace and let
5710 it continue run. The shared random subsystem is very resilient and
5711 if anything wrong happens with it, at worst a non coherent value
5712 will be put in the vote and discarded by the other authorities.
5713 Closes ticket 19566.
5715 o Documentation (onion services):
5716 - Improve HSv3 client authorization by making some options more
5717 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
5718 - Document in the man page that changing ClientOnionAuthDir value or
5719 adding a new file in the directory will not work at runtime upon
5720 sending a HUP if Sandbox 1. Closes ticket 28128.
5721 - Note in the man page that the only real way to fully revoke an
5722 onion service v3 client authorization is by restarting the tor
5723 process. Closes ticket 28275.
5726 Changes in version 0.3.4.9 - 2018-11-02
5727 Tor 0.3.4.9 is the second stable release in its series; it backports
5728 numerous fixes, including a fix for a bandwidth management bug that
5729 was causing memory exhaustion on relays. Anyone running an earlier
5730 version of Tor 0.3.4.9 should upgrade.
5732 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
5733 - Fix compilation on ARM (and other less-used CPUs) when compiling
5734 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
5736 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
5737 - Make sure Tor bootstraps and works properly if only the
5738 ControlPort is set. Prior to this fix, Tor would only bootstrap
5739 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
5740 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
5742 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
5743 - When our write bandwidth limit is exhausted, stop writing on the
5744 connection. Previously, we had a typo in the code that would make
5745 us stop reading instead, leading to relay connections being stuck
5746 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
5749 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
5750 - Fix a use-after-free error that could be caused by passing Tor an
5751 impossible set of options that would fail during options_act().
5752 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
5754 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
5755 - Don't do a distcheck with --disable-module-dirauth in Travis.
5756 Implements ticket 27252.
5757 - Only run one online rust build in Travis, to reduce network
5758 errors. Skip offline rust builds on Travis for Linux gcc, because
5759 they're redundant. Implements ticket 27252.
5760 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
5761 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
5762 Linux with default settings, because all the non-default builds
5763 use gcc on Linux. Implements ticket 27252.
5765 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
5766 - Use the Travis Homebrew addon to install packages on macOS during
5767 Travis CI. The package list is the same, but the Homebrew addon
5768 does not do a `brew update` by default. Implements ticket 27738.
5770 o Minor features (geoip):
5771 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
5772 Country database. Closes ticket 27991.
5774 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
5775 - Fix an integer overflow bug in our optimized 32-bit millisecond-
5776 difference algorithm for 32-bit Apple platforms. Previously, it
5777 would overflow when calculating the difference between two times
5778 more than 47 days apart. Fixes part of bug 27139; bugfix
5780 - Improve the precision of our 32-bit millisecond difference
5781 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
5782 bugfix on 0.3.4.1-alpha.
5783 - Relax the tolerance on the mainloop/update_time_jumps test when
5784 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
5787 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
5788 - Avoid undefined behavior in an end-of-string check when parsing
5789 the BEGIN line in a directory object. Fixes bug 28202; bugfix
5792 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
5793 - Only install the necessary mingw packages during our appveyor
5794 builds. This change makes the build a little faster, and prevents
5795 a conflict with a preinstalled mingw openssl that appveyor now
5796 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
5798 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
5799 - Rewrite our assertion macros so that they no longer suppress the
5800 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
5802 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
5803 - Stop reinstalling identical packages in our Windows CI. Fixes bug
5804 27464; bugfix on 0.3.4.1-alpha.
5806 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
5807 - Log additional info when we get a relay that shares an ed25519 ID
5808 with a different relay, instead making a BUG() warning. Fixes bug
5809 27800; bugfix on 0.3.2.1-alpha.
5811 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
5812 - Avoid a double-close when shutting down a stalled directory
5813 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
5815 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
5816 - Fix a bug warning when closing an HTTP tunnel connection due to an
5817 HTTP request we couldn't handle. Fixes bug 26470; bugfix
5820 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
5821 - Ensure circuitmux queues are empty before scheduling or sending
5822 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
5824 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
5825 - When the onion service directory can't be created or has the wrong
5826 permissions, do not log a stack trace. Fixes bug 27335; bugfix
5829 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
5830 - Close all SOCKS request (for the same .onion) if the newly fetched
5831 descriptor is unusable. Before that, we would close only the first
5832 one leaving the other hanging and let to time out by themselves.
5833 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
5835 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
5836 - When selecting a v3 rendezvous point, don't only look at the
5837 protover, but also check whether the curve25519 onion key is
5838 present. This way we avoid picking a relay that supports the v3
5839 rendezvous but for which we don't have the microdescriptor. Fixes
5840 bug 27797; bugfix on 0.3.2.1-alpha.
5842 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
5843 - Reject protocol names containing bytes other than alphanumeric
5844 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
5847 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
5848 - Compute protover votes correctly in the rust version of the
5849 protover code. Previously, the protover rewrite in 24031 allowed
5850 repeated votes from the same voter for the same protocol version
5851 to be counted multiple times in protover_compute_vote(). Fixes bug
5852 27649; bugfix on 0.3.3.5-rc.
5853 - Reject protover names that contain invalid characters. Fixes bug
5854 27687; bugfix on 0.3.3.1-alpha.
5856 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
5857 - protover_all_supported() would attempt to allocate up to 16GB on
5858 some inputs, leading to a potential memory DoS. Fixes bug 27206;
5859 bugfix on 0.3.3.5-rc.
5861 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
5862 - Fix an API mismatch in the rust implementation of
5863 protover_compute_vote(). This bug could have caused crashes on any
5864 directory authorities running Tor with Rust (which we do not yet
5865 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
5867 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
5868 - Fix a potential null dereference in protover_all_supported(). Add
5869 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
5870 - Return a string that can be safely freed by C code, not one
5871 created by the rust allocator, in protover_all_supported(). Fixes
5872 bug 27740; bugfix on 0.3.3.1-alpha.
5874 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
5875 - If a unit test running in a subprocess exits abnormally or with a
5876 nonzero status code, treat the test as having failed, even if the
5877 test reported success. Without this fix, memory leaks don't cause
5878 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
5879 bugfix on 0.2.2.4-alpha.
5881 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
5882 - Make the hs_service tests use the same time source when creating
5883 the introduction point and when testing it. Now tests work better
5884 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
5887 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
5888 - Treat backtrace test failures as expected on BSD-derived systems
5889 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
5890 (FreeBSD failures have been treated as expected since 18204 in
5891 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
5894 Changes in version 0.2.9.17 - 2018-09-10
5895 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
5897 o Minor features (compatibility, backport from 0.3.4.8):
5898 - Tell OpenSSL to maintain backward compatibility with previous
5899 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
5900 ciphers are disabled by default. Closes ticket 27344.
5902 o Minor features (continuous integration, backport from 0.3.4.7-rc):
5903 - Enable macOS builds in our Travis CI configuration. Closes
5905 - Install libcap-dev and libseccomp2-dev so these optional
5906 dependencies get tested on Travis CI. Closes ticket 26560.
5907 - Run asciidoc during Travis CI. Implements ticket 27087.
5908 - Use ccache in our Travis CI configuration. Closes ticket 26952.
5910 o Minor features (geoip):
5911 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
5912 Country database. Closes ticket 27089.
5914 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
5915 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
5916 tell the compiler not to include the system malloc implementation.
5917 Fixes bug 20424; bugfix on 0.2.0.20-rc.
5919 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
5920 - Silence a spurious compiler warning on the GetAdaptersAddresses
5921 function pointer cast. This issue is already fixed by 26481 in
5922 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
5923 bugfix on 0.2.3.11-alpha.
5924 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
5925 supported, and always fails. Some compilers warn about the
5926 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
5929 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
5930 - Don't link or search for pthreads when building for Windows, even
5931 if we are using build environment (like mingw) that provides a
5932 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
5934 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
5935 - Skip a pair of unreliable key generation tests on Windows, until
5936 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
5937 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
5939 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
5940 - Pass the module flags to distcheck configure, and log the flags
5941 before running configure. (Backported to 0.2.9 and later as a
5942 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
5944 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
5945 - When a Travis build fails, and showing a log fails, keep trying to
5946 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
5947 - When we use echo in Travis, don't pass a --flag as the first
5948 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
5950 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
5951 - When voting for recommended versions, make sure that all of the
5952 versions are well-formed and parsable. Fixes bug 26485; bugfix
5955 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
5956 - Fix a bug in out sandboxing rules for the openat() syscall.
5957 Previously, no openat() call would be permitted, which would break
5958 filesystem operations on recent glibc versions. Fixes bug 25440;
5959 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
5961 o Minor bugfixes (onion services, backport from 0.3.4.8):
5962 - Silence a spurious compiler warning in
5963 rend_client_send_introduction(). Fixes bug 27463; bugfix
5966 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
5967 - Log a protocol warning when single onion services or Tor2web clients
5968 fail to authenticate direct connections to relays.
5969 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
5971 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
5972 - Disable core dumps in test_bt.sh, to avoid failures in "make
5973 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
5975 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
5976 - Before running make test-network-all, delete old logs and test
5977 result files, to avoid spurious failures. Fixes bug 27295; bugfix
5980 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
5981 - Our "tortls/cert_matches_key" unit test no longer relies on
5982 OpenSSL internals. Previously, it relied on unsupported OpenSSL
5983 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
5984 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
5986 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
5987 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
5988 27185; bugfix on 0.2.2.2-alpha.
5991 Changes in version 0.3.2.12 - 2018-09-10
5992 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
5994 o Minor features (compatibility, backport from 0.3.4.8):
5995 - Tell OpenSSL to maintain backward compatibility with previous
5996 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
5997 ciphers are disabled by default. Closes ticket 27344.
5999 o Minor features (continuous integration, backport from 0.3.4.7-rc):
6000 - Enable macOS builds in our Travis CI configuration. Closes
6002 - Install libcap-dev and libseccomp2-dev so these optional
6003 dependencies get tested on Travis CI. Closes ticket 26560.
6004 - Run asciidoc during Travis CI. Implements ticket 27087.
6005 - Use ccache in our Travis CI configuration. Closes ticket 26952.
6007 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
6008 - Use cargo cache in our Travis CI configuration. Closes
6011 o Minor features (controller, backport from 0.3.4.6-rc):
6012 - The control port now exposes the list of HTTPTunnelPorts and
6013 ExtOrPorts via GETINFO net/listeners/httptunnel and
6014 net/listeners/extor respectively. Closes ticket 26647.
6016 o Minor features (directory authorities, backport from 0.3.4.7-rc):
6017 - Authorities no longer vote to make the subprotocol version
6018 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
6019 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
6021 o Minor features (geoip):
6022 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
6023 Country database. Closes ticket 27089.
6025 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
6026 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
6027 tell the compiler not to include the system malloc implementation.
6028 Fixes bug 20424; bugfix on 0.2.0.20-rc.
6029 - Don't try to use a pragma to temporarily disable the
6030 -Wunused-const-variable warning if the compiler doesn't support
6031 it. Fixes bug 26785; bugfix on 0.3.2.11.
6033 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
6034 - Silence a spurious compiler warning on the GetAdaptersAddresses
6035 function pointer cast. This issue is already fixed by 26481 in
6036 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
6037 bugfix on 0.2.3.11-alpha.
6038 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
6039 supported, and always fails. Some compilers warn about the
6040 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
6043 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
6044 - Don't link or search for pthreads when building for Windows, even
6045 if we are using build environment (like mingw) that provides a
6046 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
6048 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
6049 - Skip a pair of unreliable key generation tests on Windows, until
6050 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
6051 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
6053 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
6054 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
6055 - Pass the module flags to distcheck configure, and log the flags
6056 before running configure. (Backported to 0.2.9 and later as a
6057 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
6059 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
6060 - When a Travis build fails, and showing a log fails, keep trying to
6061 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
6062 - When we use echo in Travis, don't pass a --flag as the first
6063 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
6065 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
6066 - When voting for recommended versions, make sure that all of the
6067 versions are well-formed and parsable. Fixes bug 26485; bugfix
6070 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
6071 - Fix a bug in out sandboxing rules for the openat() syscall.
6072 Previously, no openat() call would be permitted, which would break
6073 filesystem operations on recent glibc versions. Fixes bug 25440;
6074 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
6076 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
6077 - Improve the log message when connection initiators fail to
6078 authenticate direct connections to relays. Fixes bug 26927; bugfix
6081 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
6082 - Fix bug that causes services to not ever rotate their descriptors
6083 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
6086 o Minor bugfixes (onion services, backport from 0.3.4.8):
6087 - Silence a spurious compiler warning in
6088 rend_client_send_introduction(). Fixes bug 27463; bugfix
6091 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
6092 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
6094 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
6095 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
6096 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
6097 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
6099 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
6100 - Log a protocol warning when single onion services or Tor2web clients
6101 fail to authenticate direct connections to relays.
6102 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
6104 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
6105 - Disable core dumps in test_bt.sh, to avoid failures in "make
6106 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
6108 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
6109 - When running make test-network-all, use the mixed+hs-v2 network.
6110 (A previous fix to chutney removed v3 onion services from the
6111 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
6112 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
6113 - Before running make test-network-all, delete old logs and test
6114 result files, to avoid spurious failures. Fixes bug 27295; bugfix
6117 o Minor bugfixes (testing, openssl compatibility):
6118 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
6119 internals. Previously, it relied on unsupported OpenSSL behavior in
6120 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
6121 bugfix on 0.2.5.1-alpha.
6123 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
6124 - Our "tortls/cert_matches_key" unit test no longer relies on
6125 OpenSSL internals. Previously, it relied on unsupported OpenSSL
6126 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
6127 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
6129 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
6130 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
6131 27185; bugfix on 0.2.2.2-alpha.
6134 Changes in version 0.3.3.10 - 2018-09-10
6135 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
6137 o Minor features (bug workaround, backport from 0.3.4.7-rc):
6138 - Compile correctly on systems that provide the C11 stdatomic.h
6139 header, but where C11 atomic functions don't actually compile.
6140 Closes ticket 26779; workaround for Debian issue 903709.
6142 o Minor features (compatibility, backport from 0.3.4.8):
6143 - Tell OpenSSL to maintain backward compatibility with previous
6144 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
6145 ciphers are disabled by default. Closes ticket 27344.
6147 o Minor features (continuous integration, backport from 0.3.4.7-rc):
6148 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
6149 - Enable macOS builds in our Travis CI configuration. Closes
6151 - Install libcap-dev and libseccomp2-dev so these optional
6152 dependencies get tested on Travis CI. Closes ticket 26560.
6153 - Run asciidoc during Travis CI. Implements ticket 27087.
6154 - Use ccache in our Travis CI configuration. Closes ticket 26952.
6156 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
6157 - Use cargo cache in our Travis CI configuration. Closes
6160 o Minor features (controller, backport from 0.3.4.6-rc):
6161 - The control port now exposes the list of HTTPTunnelPorts and
6162 ExtOrPorts via GETINFO net/listeners/httptunnel and
6163 net/listeners/extor respectively. Closes ticket 26647.
6165 o Minor features (directory authorities, backport from 0.3.4.7-rc):
6166 - Authorities no longer vote to make the subprotocol version
6167 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
6168 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
6170 o Minor features (geoip):
6171 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
6172 Country database. Closes ticket 27089.
6174 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
6175 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
6176 tell the compiler not to include the system malloc implementation.
6177 Fixes bug 20424; bugfix on 0.2.0.20-rc.
6178 - Don't try to use a pragma to temporarily disable the
6179 -Wunused-const-variable warning if the compiler doesn't support
6180 it. Fixes bug 26785; bugfix on 0.3.2.11.
6182 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
6183 - Silence a spurious compiler warning on the GetAdaptersAddresses
6184 function pointer cast. This issue is already fixed by 26481 in
6185 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
6186 bugfix on 0.2.3.11-alpha.
6187 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
6188 supported, and always fails. Some compilers warn about the
6189 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
6192 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
6193 - Don't link or search for pthreads when building for Windows, even
6194 if we are using build environment (like mingw) that provides a
6195 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
6197 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
6198 - Skip a pair of unreliable key generation tests on Windows, until
6199 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
6200 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
6202 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
6203 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
6204 - Pass the module flags to distcheck configure, and log the flags
6205 before running configure. (Backported to 0.2.9 and later as a
6206 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
6208 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
6209 - When a Travis build fails, and showing a log fails, keep trying to
6210 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
6211 - When we use echo in Travis, don't pass a --flag as the first
6212 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
6214 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
6215 - When voting for recommended versions, make sure that all of the
6216 versions are well-formed and parsable. Fixes bug 26485; bugfix
6219 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
6220 - Always call tor_free_all() when leaving tor_run_main(). When we
6221 did not, restarting tor in-process would cause an assertion
6222 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
6224 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
6225 - Fix a bug in our sandboxing rules for the openat() syscall.
6226 Previously, no openat() call would be permitted, which would break
6227 filesystem operations on recent glibc versions. Fixes bug 25440;
6228 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
6230 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
6231 - Improve the log message when connection initiators fail to
6232 authenticate direct connections to relays. Fixes bug 26927; bugfix
6235 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
6236 - Fix bug that causes services to not ever rotate their descriptors
6237 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
6240 o Minor bugfixes (onion services, backport from 0.3.4.8):
6241 - Silence a spurious compiler warning in
6242 rend_client_send_introduction(). Fixes bug 27463; bugfix
6245 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
6246 - Work around two different bugs in the OS X 10.10 and later SDKs
6247 that would prevent us from successfully targeting earlier versions
6248 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
6250 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
6251 - Fix compilation of the unit tests on GNU/Hurd, which does not
6252 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
6255 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
6256 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
6258 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
6259 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
6260 - Protover parsing was accepting the presence of whitespace in
6261 version strings, which the C implementation would choke on, e.g.
6262 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
6263 - Protover parsing was ignoring a 2nd hyphen and everything after
6264 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
6266 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
6267 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
6268 - cd to ${abs_top_builddir}/src/rust before running cargo in
6269 src/test/test_rust.sh. This makes the working directory consistent
6270 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
6272 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
6273 - Log a protocol warning when single onion services or Tor2web clients
6274 fail to authenticate direct connections to relays.
6275 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
6277 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
6278 - Disable core dumps in test_bt.sh, to avoid failures in "make
6279 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
6281 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
6282 - When running make test-network-all, use the mixed+hs-v2 network.
6283 (A previous fix to chutney removed v3 onion services from the
6284 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
6285 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
6286 - Before running make test-network-all, delete old logs and test
6287 result files, to avoid spurious failures. Fixes bug 27295; bugfix
6290 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
6291 - Our "tortls/cert_matches_key" unit test no longer relies on
6292 OpenSSL internals. Previously, it relied on unsupported OpenSSL
6293 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
6294 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
6296 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
6297 - Stop sending ed25519 link specifiers in v3 onion service introduce
6298 cells and descriptors, when the rendezvous or introduction point
6299 doesn't support ed25519 link authentication. Fixes bug 26627;
6300 bugfix on 0.3.2.4-alpha.
6302 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
6303 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
6304 27185; bugfix on 0.2.2.2-alpha.
6307 Changes in version 0.3.4.8 - 2018-09-10
6308 Tor 0.3.4.8 is the first stable release in its series; it includes
6309 compilation and portability fixes.
6311 The Tor 0.3.4 series includes improvements for running Tor in
6312 low-power and embedded environments, which should help performance in
6313 general. We've begun work on better modularity, and included preliminary
6314 changes on the directory authority side to accommodate a new bandwidth
6315 measurement system. We've also integrated more continuous-integration
6316 systems into our development process, and made corresponding changes to
6317 Tor's testing infrastructure. Finally, we've continued to refine
6318 our anti-denial-of-service code.
6320 Below are the changes since 0.3.3.9. For a list of only the changes
6321 since 0.3.4.7-rc, see the ChangeLog file.
6323 o New system requirements:
6324 - Tor no longer tries to support old operating systems without
6325 mmap() or some local equivalent. Apparently, compilation on such
6326 systems has been broken for some time, without anybody noticing or
6327 complaining. Closes ticket 25398.
6329 o Major features (directory authority, modularization):
6330 - The directory authority subsystem has been modularized. The code
6331 is now located in src/or/dirauth/, and is compiled in by default.
6332 To disable the module, the configure option
6333 --disable-module-dirauth has been added. This module may be
6334 disabled by default in some future release. Closes ticket 25610.
6336 o Major features (main loop, CPU usage):
6337 - When Tor is disabled (via DisableNetwork or via hibernation), it
6338 no longer needs to run any per-second events. This change should
6339 make it easier for mobile applications to disable Tor while the
6340 device is sleeping, or Tor is not running. Closes ticket 26063.
6341 - Tor no longer enables all of its periodic events by default.
6342 Previously, Tor would enable all possible main loop events,
6343 regardless of whether it needed them. Furthermore, many of these
6344 events are now disabled when Tor is hibernating or DisableNetwork
6345 is set. This is a big step towards reducing client CPU usage by
6346 reducing the amount of wake-ups the daemon does. Closes tickets
6348 - The bandwidth-limitation logic has been refactored so that
6349 bandwidth calculations are performed on-demand, rather than every
6350 TokenBucketRefillInterval milliseconds. This change should improve
6351 the granularity of our bandwidth calculations, and limit the
6352 number of times that the Tor process needs to wake up when it is
6353 idle. Closes ticket 25373.
6354 - Move responsibility for many operations from a once-per-second
6355 callback to a callback that is only scheduled as needed. Moving
6356 this functionality has allowed us to disable the callback when
6357 Tor's network is disabled. Once enough items are removed from our
6358 once-per-second callback, we can eliminate it entirely to conserve
6359 CPU when idle. The functionality removed includes: closing
6360 connections, circuits, and channels (ticket 25932); consensus
6361 voting (25937); flushing log callbacks (25951); honoring delayed
6362 SIGNEWNYM requests (25949); rescanning the consensus cache
6363 (25931); saving the state file to disk (25948); warning relay
6364 operators about unreachable ports (25952); and keeping track of
6365 Tor's uptime (26009).
6367 o Minor features (accounting):
6368 - When Tor becomes dormant, it now uses a scheduled event to wake up
6369 at the right time. Previously, we would use the per-second timer
6370 to check whether to wake up, but we no longer have any per-second
6371 timers enabled when the network is disabled. Closes ticket 26064.
6373 o Minor features (bug workaround):
6374 - Compile correctly on systems that provide the C11 stdatomic.h
6375 header, but where C11 atomic functions don't actually compile.
6376 Closes ticket 26779; workaround for Debian issue 903709.
6378 o Minor features (code quality):
6379 - Add optional spell-checking for the Tor codebase, using the
6380 "misspell" program. To use this feature, run "make check-typos".
6381 Closes ticket 25024.
6383 o Minor features (compatibility):
6384 - Tell OpenSSL to maintain backward compatibility with previous
6385 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
6386 ciphers are disabled by default. Closes ticket 27344.
6387 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
6388 the no-deprecated option, and builds correctly with them. Closes
6389 tickets 19429, 19981, and 25353.
6391 o Minor features (compilation):
6392 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
6393 tell the compiler not to include the system malloc implementation.
6394 Fixes bug 20424; bugfix on 0.2.0.20-rc.
6395 - Don't try to use a pragma to temporarily disable the
6396 -Wunused-const-variable warning if the compiler doesn't support
6397 it. Fixes bug 26785; bugfix on 0.3.2.11.
6398 - When building Tor, prefer to use Python 3 over Python 2, and more
6399 recent (contemplated) versions over older ones. Closes
6402 o Minor features (compression, zstd):
6403 - When running with zstd, Tor now considers using advanced functions
6404 that the zstd maintainers have labeled as potentially unstable. To
6405 prevent breakage, Tor will only use this functionality when the
6406 runtime version of the zstd library matches the version with which
6407 Tor was compiled. Closes ticket 25162.
6409 o Minor features (configuration):
6410 - The "DownloadSchedule" options have been renamed to end with
6411 "DownloadInitialDelay". The old names are still allowed, but will
6412 produce a warning. Comma-separated lists are still permitted for
6413 these options, but all values after the first are ignored (as they
6414 have been since 0.2.9). Closes ticket 23354.
6416 o Minor features (continuous integration):
6417 - Log the compiler path and version during Appveyor builds.
6418 Implements ticket 27449.
6419 - Show config.log and test-suite.log after failed Appveyor builds.
6420 Also upload the zipped full logs as a build artifact. Implements
6422 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
6423 - Enable macOS builds in our Travis CI configuration. Closes
6425 - Install libcap-dev and libseccomp2-dev so these optional
6426 dependencies get tested on Travis CI. Closes ticket 26560.
6427 - Only post Appveyor IRC notifications when the build fails.
6428 Implements ticket 27275.
6429 - Run asciidoc during Travis CI. Implements ticket 27087.
6430 - Use ccache in our Travis CI configuration. Closes ticket 26952.
6431 - Add the necessary configuration files for continuous integration
6432 testing on Windows, via the Appveyor platform. Closes ticket
6433 25549. Patches from Marcin Cieślak and Isis Lovecruft.
6435 o Minor features (continuous integration, rust):
6436 - Use cargo cache in our Travis CI configuration. Closes
6439 o Minor features (control port):
6440 - Introduce GETINFO "current-time/{local,utc}" to return the local
6441 and UTC times respectively in ISO format. This helps a controller
6442 like Tor Browser detect a time-related error. Closes ticket 25511.
6443 Patch by Neel Chauhan.
6444 - Introduce new fields to the CIRC_BW event. There are two new
6445 fields in each of the read and written directions. The DELIVERED
6446 fields report the total valid data on the circuit, as measured by
6447 the payload sizes of verified and error-checked relay command
6448 cells. The OVERHEAD fields report the total unused bytes in each
6449 of these cells. Closes ticket 25903.
6451 o Minor features (controller):
6452 - The control port now exposes the list of HTTPTunnelPorts and
6453 ExtOrPorts via GETINFO net/listeners/httptunnel and
6454 net/listeners/extor respectively. Closes ticket 26647.
6456 o Minor features (directory authorities):
6457 - Stop warning about incomplete bw lines before the first complete
6458 bw line has been found, so that additional header lines can be
6459 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
6460 - Authorities no longer vote to make the subprotocol version
6461 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
6462 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
6464 o Minor features (directory authority):
6465 - Directory authorities now open their key-pinning files as O_SYNC,
6466 to limit their chances of accidentally writing partial lines.
6467 Closes ticket 23909.
6469 o Minor features (directory authority, forward compatibility):
6470 - Make the lines of the measured bandwidth file able to contain
6471 their entries in any order. Previously, the node_id entry needed
6472 to come first. Closes ticket 26004.
6474 o Minor features (entry guards):
6475 - Introduce a new torrc option NumPrimaryGuards for controlling the
6476 number of primary guards. Closes ticket 25843.
6478 o Minor features (geoip):
6479 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
6480 Country database. Closes ticket 27089.
6482 o Minor features (performance):
6483 - Avoid a needless call to malloc() when processing an incoming
6484 relay cell. Closes ticket 24914.
6485 - Make our timing-wheel code run a tiny bit faster on 32-bit
6486 platforms, by preferring 32-bit math to 64-bit. Closes
6488 - Avoid a needless malloc()/free() pair every time we handle an ntor
6489 handshake. Closes ticket 25150.
6491 o Minor features (Rust, portability):
6492 - Rust cross-compilation is now supported. Closes ticket 25895.
6494 o Minor features (testing):
6495 - Add a unit test for voting_schedule_get_start_of_next_interval().
6496 Closes ticket 26014, and helps make unit test coverage
6498 - A new unittests module specifically for testing the functions in
6499 the (new-ish) bridges.c module has been created with new
6500 unittests, raising the code coverage percentages. Closes 25425.
6501 - We now have improved testing for addressmap_get_virtual_address()
6502 function. This should improve our test coverage, and make our test
6503 coverage more deterministic. Closes ticket 25993.
6505 o Minor features (timekeeping, circuit scheduling):
6506 - When keeping track of how busy each circuit have been recently on
6507 a given connection, use coarse-grained monotonic timers rather
6508 than gettimeofday(). This change should marginally increase
6509 accuracy and performance. Implements part of ticket 25927.
6511 o Minor features (unit tests):
6512 - Test complete bandwidth measurements files, and test that
6513 incomplete bandwidth lines only give warnings when the end of the
6514 header has not been detected. Fixes bug 25947; bugfix
6517 o Minor bugfixes (bandwidth management):
6518 - Consider ourselves "low on write bandwidth" if we have exhausted
6519 our write bandwidth some time in the last second. This was the
6520 documented behavior before, but the actual behavior was to change
6521 this value every TokenBucketRefillInterval. Fixes bug 25828;
6522 bugfix on 0.2.3.5-alpha.
6524 o Minor bugfixes (C correctness):
6525 - Add a missing lock acquisition in the shutdown code of the control
6526 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
6527 Coverity; this is CID 1433643.
6529 o Minor bugfixes (code style):
6530 - Fixed multiple includes of transports.h in src/or/connection.c
6531 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
6532 - Remove the unused variable n_possible from the function
6533 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
6535 o Minor bugfixes (compilation):
6536 - Silence a spurious compiler warning on the GetAdaptersAddresses
6537 function pointer cast. This issue is already fixed by 26481 in
6538 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
6539 bugfix on 0.2.3.11-alpha.
6540 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
6541 supported, and always fails. Some compilers warn about the
6542 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
6544 - Fix a compilation warning on some versions of GCC when building
6545 code that calls routerinfo_get_my_routerinfo() twice, assuming
6546 that the second call will succeed if the first one did. Fixes bug
6547 26269; bugfix on 0.2.8.2-alpha.
6548 - Refrain from compiling unit testing related object files when
6549 --disable-unittests is set to configure script. Fixes bug 24891;
6550 bugfix on 0.2.5.1-alpha.
6551 - The --enable-fatal-warnings flag now affects Rust code as well.
6552 Closes ticket 26245.
6553 - Avoid a compiler warning when casting the return value of
6554 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
6555 26283; bugfix on 0.2.4.10-alpha.
6557 o Minor bugfixes (compilation, windows):
6558 - Don't link or search for pthreads when building for Windows, even
6559 if we are using build environment (like mingw) that provides a
6560 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
6562 o Minor bugfixes (continuous integration):
6563 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
6564 - Skip a pair of unreliable key generation tests on Windows, until
6565 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
6566 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
6568 o Minor bugfixes (control port):
6569 - Respond with more human-readable error messages to GETINFO exit-
6570 policy/* requests. Also, let controller know if an error is
6571 transient (response code 551) or not (response code 552). Fixes
6572 bug 25852; bugfix on 0.2.8.1-alpha.
6573 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
6574 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
6575 on 0.3.3.1-alpha. Patch by "akwizgran".
6576 - Make CIRC_BW event reflect the total of all data sent on a
6577 circuit, including padding and dropped cells. Also fix a mis-
6578 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
6579 bugfix on 0.2.5.2-alpha.
6581 o Minor bugfixes (correctness, flow control):
6582 - Upon receiving a stream-level SENDME cell, verify that our window
6583 has not grown too large. Fixes bug 26214; bugfix on svn
6586 o Minor bugfixes (directory authority):
6587 - When voting for recommended versions, make sure that all of the
6588 versions are well-formed and parsable. Fixes bug 26485; bugfix
6591 o Minor bugfixes (directory client):
6592 - When unverified-consensus is verified, rename it to cached-
6593 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
6594 - Fixed launching a certificate fetch always during the scheduled
6595 periodic consensus fetch by fetching only in those cases when
6596 consensus are waiting for certs. Fixes bug 24740; bugfix
6599 o Minor bugfixes (error reporting):
6600 - Improve tolerance for directory authorities with skewed clocks.
6601 Previously, an authority with a clock more than 60 seconds ahead
6602 could cause a client with a correct clock to warn that the
6603 client's clock was behind. Now the clocks of a majority of
6604 directory authorities have to be ahead of the client before this
6605 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
6607 o Minor bugfixes (in-process restart):
6608 - Always call tor_free_all() when leaving tor_run_main(). When we
6609 did not, restarting tor in-process would cause an assertion
6610 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
6612 o Minor bugfixes (Linux seccomp2 sandbox):
6613 - Fix a bug in our sandboxing rules for the openat() syscall.
6614 Previously, no openat() call would be permitted, which would break
6615 filesystem operations on recent glibc versions. Fixes bug 25440;
6616 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
6618 o Minor bugfixes (logging):
6619 - Improve the log message when connection initiators fail to
6620 authenticate direct connections to relays. Fixes bug 26927; bugfix
6623 o Minor bugfixes (onion services):
6624 - Silence a spurious compiler warning in
6625 rend_client_send_introduction(). Fixes bug 27463; bugfix
6627 - Fix bug that causes services to not ever rotate their descriptors
6628 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
6630 - Recompute some consensus information after detecting a clock jump,
6631 or after transitioning from a non-live consensus to a live
6632 consensus. We do this to avoid having an outdated state, and
6633 miscalculating the index for next-generation onion services. Fixes
6634 bug 24977; bugfix on 0.3.2.1-alpha.
6636 o Minor bugfixes (portability):
6637 - Fix compilation of the unit tests on GNU/Hurd, which does not
6638 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
6640 - Work around two different bugs in the OS X 10.10 and later SDKs
6641 that would prevent us from successfully targeting earlier versions
6642 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
6643 - Do not align mmap length, as it is not required by POSIX, and the
6644 getpagesize function is deprecated. Fixes bug 25399; bugfix
6647 o Minor bugfixes (portability, FreeBSD):
6648 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
6649 does not stringify on FreeBSD, so we switch to tor_asprintf().
6650 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
6652 o Minor bugfixes (relay statistics):
6653 - When a relay is collecting internal statistics about how many
6654 create cell requests it has seen of each type, accurately count
6655 the requests from relays that temporarily fall out of the
6656 consensus. (To be extra conservative, we were already ignoring
6657 requests from clients in our counts, and we continue ignoring them
6658 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
6660 o Minor bugfixes (rust):
6661 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
6663 - Protover parsing was accepting the presence of whitespace in
6664 version strings, which the C implementation would choke on, e.g.
6665 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
6666 - Protover parsing was ignoring a 2nd hyphen and everything after
6667 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
6669 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
6670 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
6671 - cd to ${abs_top_builddir}/src/rust before running cargo in
6672 src/test/test_rust.sh. This makes the working directory consistent
6673 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
6675 o Minor bugfixes (single onion services, Tor2web):
6676 - Log a protocol warning when single onion services or Tor2web
6677 clients fail to authenticate direct connections to relays. Fixes
6678 bug 26924; bugfix on 0.2.9.1-alpha.
6680 o Minor bugfixes (test coverage tools):
6681 - Update our "cov-diff" script to handle output from the latest
6682 version of gcov, and to remove extraneous timestamp information
6683 from its output. Fixes bugs 26101 and 26102; bugfix
6686 o Minor bugfixes (testing):
6687 - Disable core dumps in test_bt.sh, to avoid failures in "make
6688 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
6689 - When testing workqueue event-cancellation, make sure that we
6690 actually cancel an event, and that cancel each event with equal
6691 probability. (It was previously possible, though extremely
6692 unlikely, for our event-canceling test not to cancel any events.)
6693 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
6694 - Repeat part of the test in test_client_pick_intro() a number of
6695 times, to give it consistent coverage. Fixes bug 25996; bugfix
6697 - Remove randomness from the hs_common/responsible_hsdirs test, so
6698 that it always takes the same path through the function it tests.
6699 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
6700 - Change the behavior of the "channel/outbound" test so that it
6701 never causes a 10-second rollover for the EWMA circuitmux code.
6702 Previously, this behavior would happen randomly, and result in
6703 fluctuating test coverage. Fixes bug 25994; bugfix
6705 - Use X509_new() to allocate certificates that will be freed later
6706 with X509_free(). Previously, some parts of the unit tests had
6707 used tor_malloc_zero(), which is incorrect, and which caused test
6708 failures on Windows when they were built with extra hardening.
6709 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
6711 - While running the circuit_timeout test, fix the PRNG to a
6712 deterministic AES stream, so that the test coverage from this test
6713 will itself be deterministic. Fixes bug 25995; bugfix
6716 o Minor bugfixes (testing, bootstrap):
6717 - When calculating bootstrap progress, check exit policies and the
6718 exit flag. Previously, Tor would only check the exit flag, which
6719 caused race conditions in small and fast networks like chutney.
6720 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
6722 o Minor bugfixes (testing, chutney):
6723 - When running make test-network-all, use the mixed+hs-v2 network.
6724 (A previous fix to chutney removed v3 onion services from the
6725 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
6726 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
6727 - Before running make test-network-all, delete old logs and test
6728 result files, to avoid spurious failures. Fixes bug 27295; bugfix
6731 o Minor bugfixes (testing, openssl compatibility):
6732 - Our "tortls/cert_matches_key" unit test no longer relies on
6733 OpenSSL internals. Previously, it relied on unsupported OpenSSL
6734 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
6735 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
6737 o Minor bugfixes (v3 onion services):
6738 - Stop sending ed25519 link specifiers in v3 onion service introduce
6739 cells and descriptors, when the rendezvous or introduction point
6740 doesn't support ed25519 link authentication. Fixes bug 26627;
6741 bugfix on 0.3.2.4-alpha.
6743 o Minor bugfixes (vanguards):
6744 - Allow the last hop in a vanguard circuit to be the same as our
6745 first, to prevent the adversary from influencing guard node choice
6746 by choice of last hop. Also prevent the creation of A - B - A
6747 paths, or A - A paths, which are forbidden by relays. Fixes bug
6748 25870; bugfix on 0.3.3.1-alpha.
6750 o Minor bugfixes (Windows, compilation):
6751 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
6752 27185; bugfix on 0.2.2.2-alpha.
6754 o Code simplification and refactoring:
6755 - Remove duplicate code in parse_{c,s}method_line and bootstrap
6756 their functionalities into a single function. Fixes bug 6236;
6757 bugfix on 0.2.3.6-alpha.
6758 - We remove the PortForwarding and PortForwardingHelper options,
6759 related functions, and the port_forwarding tests. These options
6760 were used by the now-deprecated Vidalia to help ordinary users
6761 become Tor relays or bridges. Closes ticket 25409. Patch by
6763 - In order to make the OR and dir checking function in router.c less
6764 confusing we renamed some functions and
6765 consider_testing_reachability() has been split into
6766 router_should_check_reachability() and
6767 router_do_reachability_checks(). Also we improved the documentation
6768 in some functions. Closes ticket 18918.
6769 - Initial work to isolate Libevent usage to a handful of modules in
6770 our codebase, to simplify our call structure, and so that we can
6771 more easily change event loops in the future if needed. Closes
6773 - Introduce a function to call getsockname() and return tor_addr_t,
6774 to save a little complexity throughout the codebase. Closes
6776 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
6777 as hsdir_index is always present. Also, we move hsdir_index_t into
6778 or.h. Closes ticket 23094. Patch by Neel Chauhan.
6779 - Merge functions used for describing nodes and suppress the
6780 functions that do not allocate memory for the output buffer
6781 string. NODE_DESC_BUF_LEN constant and format_node_description()
6782 function cannot be used externally from router.c module anymore.
6783 Closes ticket 25432. Patch by valentecaio.
6784 - Our main loop has been simplified so that all important operations
6785 happen inside events. Previously, some operations had to happen
6786 outside the event loop, to prevent infinite sequences of event
6787 activations. Closes ticket 25374.
6788 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
6789 it in register_intro_circ() and service_intro_point_new(). This
6790 prevents the digest from being re-calculated each time. Closes
6791 ticket 23107. Patch by Neel Chauhan.
6792 - Refactor token-bucket implementations to use a common backend.
6793 Closes ticket 25766.
6794 - Remove extern declaration of stats_n_seconds_working variable from
6795 main, protecting its accesses with get_uptime() and reset_uptime()
6796 functions. Closes ticket 25081, patch by “valentecaio”.
6797 - Remove our previous logic for "cached gettimeofday()" -- our
6798 coarse monotonic timers are fast enough for this purpose, and far
6799 less error-prone. Implements part of ticket 25927.
6800 - Remove the return value for fascist_firewall_choose_address_base(),
6801 and sister functions such as fascist_firewall_choose_address_node()
6802 and fascist_firewall_choose_address_rs(). Also, while we're here,
6803 initialize the ap argument as leaving it uninitialized can pose a
6804 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
6805 - Rename two fields of connection_t struct. timestamp_lastwritten is
6806 renamed to timestamp_last_write_allowed and timestamp_lastread is
6807 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
6809 - Since Tor requires C99, remove our old workaround code for libc
6810 implementations where free(NULL) doesn't work. Closes ticket 24484.
6811 - Use our standard rate-limiting code to deal with excessive
6812 libevent failures, rather than the hand-rolled logic we had
6813 before. Closes ticket 26016.
6814 - We remove the return value of node_get_prim_orport() and
6815 node_get_prim_dirport(), and introduce node_get_prim_orport() in
6816 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
6817 check for a null address. Closes ticket 23873. Patch by
6819 - We switch to should_record_bridge_info() in
6820 geoip_note_client_seen() and options_need_geoip_info() instead of
6821 accessing the configuration values directly. Fixes bug 25290;
6822 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
6824 o Deprecated features:
6825 - As we are not recommending 0.2.5 anymore, we require relays that
6826 once had an ed25519 key associated with their RSA key to always
6827 have that key, instead of allowing them to drop back to a version
6828 that didn't support ed25519. This means they need to use a new RSA
6829 key if they want to downgrade to an older version of tor without
6830 ed25519. Closes ticket 20522.
6833 - Directory authorities will no longer support voting according to
6834 any consensus method before consensus method 25. This keeps
6835 authorities compatible with all authorities running 0.2.9.8 and
6836 later, and does not break any clients or relays. Implements ticket
6837 24378 and proposal 290.
6838 - The PortForwarding and PortForwardingHelper features have been
6839 removed. The reasoning is, given that implementations of NAT
6840 traversal protocols within common consumer grade routers are
6841 frequently buggy, and that the target audience for a NAT punching
6842 feature is a perhaps less-technically-inclined relay operator,
6843 when the helper fails to setup traversal the problems are usually
6844 deep, ugly, and very router specific, making them horrendously
6845 impossible for technical support to reliable assist with, and thus
6846 resulting in frustration all around. Unfortunately, relay
6847 operators who would like to run relays behind NATs will need to
6848 become more familiar with the port forwarding configurations on
6849 their local router. Closes 25409.
6850 - The TestingEnableTbEmptyEvent option has been removed. It was used
6851 in testing simulations to measure how often connection buckets
6852 were emptied, in order to improve our scheduling, but it has not
6853 been actively used in years. Closes ticket 25760.
6854 - The old "round-robin" circuit multiplexer (circuitmux)
6855 implementation has been removed, along with a fairly large set of
6856 code that existed to support it. It has not been the default
6857 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
6858 but it still required an unreasonable amount of memory and CPU.
6859 Closes ticket 25268.
6862 Changes in version 0.3.3.9 - 2018-07-13
6863 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
6864 bridge relays should upgrade.
6866 o Directory authority changes:
6867 - The "Bifroest" bridge authority has been retired; the new bridge
6868 authority is "Serge", and it is operated by George from the
6869 TorBSD project. Closes ticket 26771.
6872 Changes in version 0.3.2.11 - 2018-07-13
6873 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
6874 bridge relays should upgrade. We also take this opportunity to backport
6877 o Directory authority changes:
6878 - The "Bifroest" bridge authority has been retired; the new bridge
6879 authority is "Serge", and it is operated by George from the
6880 TorBSD project. Closes ticket 26771.
6882 o Directory authority changes (backport from 0.3.3.7):
6883 - Add an IPv6 address for the "dannenberg" directory authority.
6884 Closes ticket 26343.
6886 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
6887 - When directory authorities read a zero-byte bandwidth file, they
6888 would previously log a warning with the contents of an
6889 uninitialised buffer. They now log a warning about the empty file
6890 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
6892 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
6893 - Correctly detect when onion services get disabled after HUP. Fixes
6894 bug 25761; bugfix on 0.3.2.1.
6896 o Minor features (sandbox, backport from 0.3.3.4-alpha):
6897 - Explicitly permit the poll() system call when the Linux
6898 seccomp2-based sandbox is enabled: apparently, some versions of
6899 libc use poll() when calling getpwnam(). Closes ticket 25313.
6901 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
6902 - Update the Travis CI configuration to use the stable Rust channel,
6903 now that we have decided to require that. Closes ticket 25714.
6905 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
6906 - Our .travis.yml configuration now includes support for testing the
6907 results of "make distcheck". (It's not uncommon for "make check"
6908 to pass but "make distcheck" to fail.) Closes ticket 25814.
6909 - Our Travis CI configuration now integrates with the Coveralls
6910 coverage analysis tool. Closes ticket 25818.
6912 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
6913 - Add several checks to detect whether Tor relays are uploading
6914 their descriptors without specifying why they regenerated them.
6915 Diagnostic for ticket 25686.
6917 o Minor features (compilation, backport from 0.3.4.4-rc):
6918 - When building Tor, prefer to use Python 3 over Python 2, and more
6919 recent (contemplated) versions over older ones. Closes
6922 o Minor features (geoip):
6923 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
6924 Country database. Closes ticket 26674.
6926 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
6927 - Upon receiving a malformed connected cell, stop processing the
6928 cell immediately. Previously we would mark the connection for
6929 close, but continue processing the cell as if the connection were
6930 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
6932 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
6933 - Allow the nanosleep() system call, which glibc uses to implement
6934 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
6936 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
6937 - When running the hs_ntor_ref.py test, make sure only to pass
6938 strings (rather than "bytes" objects) to the Python subprocess
6939 module. Python 3 on Windows seems to require this. Fixes bug
6940 26535; bugfix on 0.3.1.1-alpha.
6941 - When running the ntor_ref.py test, make sure only to pass strings
6942 (rather than "bytes" objects) to the Python subprocess module.
6943 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
6946 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
6947 - Work around a change in OpenSSL 1.1.1 where return values that
6948 would previously indicate "no password" now indicate an empty
6949 password. Without this workaround, Tor instances running with
6950 OpenSSL 1.1.1 would accept descriptors that other Tor instances
6951 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
6953 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
6954 - Document that the PerConnBW{Rate,Burst} options will fall back to
6955 their corresponding consensus parameters only if those parameters
6956 are set. Previously we had claimed that these values would always
6957 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
6959 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
6960 - Fix a compilation warning on some versions of GCC when building
6961 code that calls routerinfo_get_my_routerinfo() twice, assuming
6962 that the second call will succeed if the first one did. Fixes bug
6963 26269; bugfix on 0.2.8.2-alpha.
6965 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
6966 - Don't consider Tor running as a client if the ControlPort is open,
6967 but no actual client ports are open. Fixes bug 26062; bugfix
6970 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
6971 - Prevent a possible out-of-bounds smartlist read in
6972 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
6974 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
6975 - Fix a very unlikely (impossible, we believe) null pointer
6976 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
6977 Coverity; this is CID 1430932.
6979 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
6980 - Fix a memory leak when a v3 onion service is configured and gets a
6981 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
6982 - When parsing the descriptor signature, look for the token plus an
6983 extra white-space at the end. This is more correct but also will
6984 allow us to support new fields that might start with "signature".
6985 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
6987 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
6988 - Relays now correctly block attempts to re-extend to the previous
6989 relay by Ed25519 identity. Previously they would warn in this
6990 case, but not actually reject the attempt. Fixes bug 26158; bugfix
6993 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
6994 - Avoid a crash when running with DirPort set but ORPort turned off.
6995 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
6997 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
6998 - Silence unused-const-variable warnings in zstd.h with some GCC
6999 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
7001 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
7002 - Avoid intermittent test failures due to a test that had relied on
7003 onion service introduction point creation finishing within 5
7004 seconds of real clock time. Fixes bug 25450; bugfix
7007 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
7008 - Fix a C99 compliance issue in our configuration script that caused
7009 compilation issues when compiling Tor with certain versions of
7010 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
7012 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
7013 - Fix a number of small memory leaks identified by coverity. Fixes
7014 bug 26467; bugfix on numerous Tor versions.
7016 o Code simplification and refactoring (backport from 0.3.3.5-rc):
7017 - Move the list of default directory authorities to its own file.
7018 Closes ticket 24854. Patch by "beastr0".
7021 Changes in version 0.2.9.16 - 2018-07-13
7022 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
7023 bridge relays should upgrade. We also take this opportunity to backport
7026 o Directory authority changes:
7027 - The "Bifroest" bridge authority has been retired; the new bridge
7028 authority is "Serge", and it is operated by George from the
7029 TorBSD project. Closes ticket 26771.
7031 o Directory authority changes (backport from 0.3.3.7):
7032 - Add an IPv6 address for the "dannenberg" directory authority.
7033 Closes ticket 26343.
7035 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
7036 - When directory authorities read a zero-byte bandwidth file, they
7037 would previously log a warning with the contents of an
7038 uninitialised buffer. They now log a warning about the empty file
7039 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
7041 o Minor features (sandbox, backport from 0.3.3.4-alpha):
7042 - Explicitly permit the poll() system call when the Linux
7043 seccomp2-based sandbox is enabled: apparently, some versions of
7044 libc use poll() when calling getpwnam(). Closes ticket 25313.
7046 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
7047 - Our .travis.yml configuration now includes support for testing the
7048 results of "make distcheck". (It's not uncommon for "make check"
7049 to pass but "make distcheck" to fail.) Closes ticket 25814.
7050 - Our Travis CI configuration now integrates with the Coveralls
7051 coverage analysis tool. Closes ticket 25818.
7053 o Minor features (compilation, backport from 0.3.4.4-rc):
7054 - When building Tor, prefer to use Python 3 over Python 2, and more
7055 recent (contemplated) versions over older ones. Closes
7058 o Minor features (geoip):
7059 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
7060 Country database. Closes ticket 26674.
7062 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
7063 - Upon receiving a malformed connected cell, stop processing the
7064 cell immediately. Previously we would mark the connection for
7065 close, but continue processing the cell as if the connection were
7066 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
7068 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
7069 - Allow the nanosleep() system call, which glibc uses to implement
7070 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
7072 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
7073 - When running the ntor_ref.py test, make sure only to pass strings
7074 (rather than "bytes" objects) to the Python subprocess module.
7075 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
7078 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
7079 - Work around a change in OpenSSL 1.1.1 where return values that
7080 would previously indicate "no password" now indicate an empty
7081 password. Without this workaround, Tor instances running with
7082 OpenSSL 1.1.1 would accept descriptors that other Tor instances
7083 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
7085 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
7086 - Fix a compilation warning on some versions of GCC when building
7087 code that calls routerinfo_get_my_routerinfo() twice, assuming
7088 that the second call will succeed if the first one did. Fixes bug
7089 26269; bugfix on 0.2.8.2-alpha.
7091 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
7092 - Don't consider Tor running as a client if the ControlPort is open,
7093 but no actual client ports are open. Fixes bug 26062; bugfix
7096 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
7097 - Prevent a possible out-of-bounds smartlist read in
7098 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
7100 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
7101 - Fix a very unlikely (impossible, we believe) null pointer
7102 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
7103 Coverity; this is CID 1430932.
7105 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
7106 - Fix a number of small memory leaks identified by coverity. Fixes
7107 bug 26467; bugfix on numerous Tor versions.
7109 o Code simplification and refactoring (backport from 0.3.3.5-rc):
7110 - Move the list of default directory authorities to its own file.
7111 Closes ticket 24854. Patch by "beastr0".
7114 Changes in version 0.3.3.8 - 2018-07-09
7115 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
7116 fixes for a memory leak affecting directory authorities.
7118 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
7119 - Stop leaking memory on directory authorities when planning to
7120 vote. This bug was crashing authorities by exhausting their
7121 memory. Fixes bug 26435; bugfix on 0.3.3.6.
7123 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
7124 - Make sure that failing tests in Rust will actually cause the build
7125 to fail: previously, they were ignored. Fixes bug 26258; bugfix
7128 o Minor features (compilation, backport from 0.3.4.4-rc):
7129 - When building Tor, prefer to use Python 3 over Python 2, and more
7130 recent (contemplated) versions over older ones. Closes
7133 o Minor features (geoip):
7134 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
7135 Country database. Closes ticket 26674.
7137 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
7138 - Add several checks to detect whether Tor relays are uploading
7139 their descriptors without specifying why they regenerated them.
7140 Diagnostic for ticket 25686.
7142 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
7143 - Don't count path selection failures as circuit build failures.
7144 This change should eliminate cases where Tor blames its guard or
7145 the network for situations like insufficient microdescriptors
7146 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
7149 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
7150 - Fix a compilation warning on some versions of GCC when building
7151 code that calls routerinfo_get_my_routerinfo() twice, assuming
7152 that the second call will succeed if the first one did. Fixes bug
7153 26269; bugfix on 0.2.8.2-alpha.
7155 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
7156 - Handle the HSADDRESS= argument to the HSPOST command properly.
7157 (Previously, this argument was misparsed and thus ignored.) Fixes
7158 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
7160 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
7161 - Fix a number of small memory leaks identified by coverity. Fixes
7162 bug 26467; bugfix on numerous Tor versions.
7164 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
7165 - Relays now correctly block attempts to re-extend to the previous
7166 relay by Ed25519 identity. Previously they would warn in this
7167 case, but not actually reject the attempt. Fixes bug 26158; bugfix
7170 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
7171 - When shutting down, Tor now clears all the flags in the control.c
7172 module. This should prevent a bug where authentication cookies are
7173 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
7175 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
7176 - When running the hs_ntor_ref.py test, make sure only to pass
7177 strings (rather than "bytes" objects) to the Python subprocess
7178 module. Python 3 on Windows seems to require this. Fixes bug
7179 26535; bugfix on 0.3.1.1-alpha.
7180 - When running the ntor_ref.py test, make sure only to pass strings
7181 (rather than "bytes" objects) to the Python subprocess module.
7182 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
7186 Changes in version 0.3.3.7 - 2018-06-12
7187 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
7188 fixes for bugs affecting compatibility and stability.
7190 o Directory authority changes:
7191 - Add an IPv6 address for the "dannenberg" directory authority.
7192 Closes ticket 26343.
7194 o Minor features (geoip):
7195 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
7196 Country database. Closes ticket 26351.
7198 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
7199 - Work around a change in OpenSSL 1.1.1 where return values that
7200 would previously indicate "no password" now indicate an empty
7201 password. Without this workaround, Tor instances running with
7202 OpenSSL 1.1.1 would accept descriptors that other Tor instances
7203 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
7205 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
7206 - Silence unused-const-variable warnings in zstd.h with some GCC
7207 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
7209 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
7210 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
7211 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
7212 miscounting the total number of circuits for these field values.)
7213 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
7215 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
7216 - Prevent a possible out-of-bounds smartlist read in
7217 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
7219 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
7220 - Only select relays when they have the descriptors we prefer to use
7221 for them. This change fixes a bug where we could select a relay
7222 because it had _some_ descriptor, but reject it later with a
7223 nonfatal assertion error because it didn't have the exact one we
7224 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
7227 Changes in version 0.3.3.6 - 2018-05-22
7228 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
7229 backports several important fixes from the 0.3.4.1-alpha.
7231 The Tor 0.3.3 series includes controller support and other
7232 improvements for v3 onion services, official support for embedding Tor
7233 within other applications, and our first non-trivial module written in
7234 the Rust programming language. (Rust is still not enabled by default
7235 when building Tor.) And as usual, there are numerous other smaller
7236 bugfixes, features, and improvements.
7238 Below are the changes since 0.3.2.10. For a list of only the changes
7239 since 0.3.3.5-rc, see the ChangeLog file.
7241 o New system requirements:
7242 - When built with Rust, Tor now depends on version 0.2.39 of the
7243 libc crate. Closes tickets 25310 and 25664.
7245 o Major features (embedding):
7246 - There is now a documented stable API for programs that need to
7247 embed Tor. See tor_api.h for full documentation and known bugs.
7248 Closes ticket 23684.
7249 - Tor now has support for restarting in the same process.
7250 Controllers that run Tor using the "tor_api.h" interface can now
7251 restart Tor after Tor has exited. This support is incomplete,
7252 however: we fixed crash bugs that prevented it from working at
7253 all, but many bugs probably remain, including a possibility of
7254 security issues. Implements ticket 24581.
7256 o Major features (IPv6, directory documents):
7257 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
7258 consensus. This information makes it easier for IPv6 clients to
7259 bootstrap and choose reachable entry guards. Implements
7261 - Add consensus method 28, which removes IPv6 ORPorts from
7262 microdescriptors. Now that the consensus contains IPv6 ORPorts,
7263 they are redundant in microdescs. This change will be used by Tor
7264 clients on 0.2.8.x and later. (That is to say, with all Tor
7265 clients that have IPv6 bootstrap and guard support.) Implements
7267 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
7268 set by different numbers of authorities. Fixes 23870
7271 o Major features (onion service v3, control port):
7272 - The control port now supports commands and events for v3 onion
7273 services. It is now possible to create ephemeral v3 services using
7274 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
7275 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
7276 DEL_ONION) have been extended to support v3 onion services. Closes
7277 ticket 20699; implements proposal 284.
7279 o Major features (onion services):
7280 - Provide torrc options to pin the second and third hops of onion
7281 service circuits to a list of nodes. The option HSLayer2Guards
7282 pins the second hop, and the option HSLayer3Guards pins the third
7283 hop. These options are for use in conjunction with experiments
7284 with "vanguards" for preventing guard enumeration attacks. Closes
7286 - When v3 onion service clients send introduce cells, they now
7287 include the IPv6 address of the rendezvous point, if it has one.
7288 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
7289 in future Tor versions, IPv6-only v3 single onion services will be
7290 able to use IPv6 addresses to connect directly to the rendezvous
7291 point. Closes ticket 23577. Patch by Neel Chauhan.
7293 o Major features (relay):
7294 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
7295 operator to use a more reasonable ("reduced") exit policy, rather
7296 than the default one. If you want to run an exit node without
7297 thinking too hard about which ports to allow, this one is for you.
7298 Closes ticket 13605. Patch from Neel Chauhan.
7300 o Major features (rust, portability, experimental):
7301 - Tor now ships with an optional implementation of one of its
7302 smaller modules (protover.c) in the Rust programming language. To
7303 try it out, install a Rust build environment, and configure Tor
7304 with "--enable-rust --enable-cargo-online-mode". This should not
7305 cause any user-visible changes, but should help us gain more
7306 experience with Rust, and plan future Rust integration work.
7307 Implementation by Chelsea Komlo. Closes ticket 22840.
7309 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
7310 - When directory authorities read a zero-byte bandwidth file, they
7311 would previously log a warning with the contents of an
7312 uninitialised buffer. They now log a warning about the empty file
7313 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
7315 o Major bugfixes (security, directory authority, denial-of-service):
7316 - Fix a bug that could have allowed an attacker to force a directory
7317 authority to use up all its RAM by passing it a maliciously
7318 crafted protocol versions string. Fixes bug 25517; bugfix on
7319 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
7321 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
7322 - Avoid a rare assertion failure in the circuit build timeout code
7323 if we fail to allow any circuits to actually complete. Fixes bug
7324 25733; bugfix on 0.2.2.2-alpha.
7326 o Major bugfixes (netflow padding):
7327 - Stop adding unneeded channel padding right after we finish
7328 flushing to a connection that has been trying to flush for many
7329 seconds. Instead, treat all partial or complete flushes as
7330 activity on the channel, which will defer the time until we need
7331 to add padding. This fix should resolve confusing and scary log
7332 messages like "Channel padding timeout scheduled 221453ms in the
7333 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
7335 o Major bugfixes (networking):
7336 - Tor will no longer reject IPv6 address strings from Tor Browser
7337 when they are passed as hostnames in SOCKS5 requests. Fixes bug
7338 25036, bugfix on Tor 0.3.1.2.
7340 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
7341 - Correctly detect when onion services get disabled after HUP. Fixes
7342 bug 25761; bugfix on 0.3.2.1.
7344 o Major bugfixes (performance, load balancing):
7345 - Directory authorities no longer vote in favor of the Guard flag
7346 for relays without directory support. Starting in Tor
7347 0.3.0.1-alpha, clients have been avoiding using such relays in the
7348 Guard position, leading to increasingly broken load balancing for
7349 the 5%-or-so of Guards that don't advertise directory support.
7350 Fixes bug 22310; bugfix on 0.3.0.6.
7352 o Major bugfixes (relay):
7353 - If we have failed to connect to a relay and received a connection
7354 refused, timeout, or similar error (at the TCP level), do not try
7355 that same address/port again for 60 seconds after the failure has
7356 occurred. Fixes bug 24767; bugfix on 0.0.6.
7358 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
7359 - Impose a limit on circuit cell queue size. The limit can be
7360 controlled by a consensus parameter. Fixes bug 25226; bugfix
7363 o Minor features (cleanup):
7364 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
7365 when it stops. Closes ticket 23271.
7367 o Minor features (compatibility, backport from 0.3.4.1-alpha):
7368 - Avoid some compilation warnings with recent versions of LibreSSL.
7369 Closes ticket 26006.
7371 o Minor features (config options):
7372 - Change the way the default value for MaxMemInQueues is calculated.
7373 We now use 40% of the hardware RAM if the system has 8 GB RAM or
7374 more. Otherwise we use the former value of 75%. Closes
7377 o Minor features (continuous integration):
7378 - Update the Travis CI configuration to use the stable Rust channel,
7379 now that we have decided to require that. Closes ticket 25714.
7381 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
7382 - Our .travis.yml configuration now includes support for testing the
7383 results of "make distcheck". (It's not uncommon for "make check"
7384 to pass but "make distcheck" to fail.) Closes ticket 25814.
7385 - Our Travis CI configuration now integrates with the Coveralls
7386 coverage analysis tool. Closes ticket 25818.
7388 o Minor features (defensive programming):
7389 - Most of the functions in Tor that free objects have been replaced
7390 with macros that free the objects and set the corresponding
7391 pointers to NULL. This change should help prevent a large class of
7392 dangling pointer bugs. Closes ticket 24337.
7393 - Where possible, the tor_free() macro now only evaluates its input
7394 once. Part of ticket 24337.
7395 - Check that microdesc ed25519 ids are non-zero in
7396 node_get_ed25519_id() before returning them. Implements ticket
7397 24001, patch by "aruna1234".
7399 o Minor features (directory authority):
7400 - When directory authorities are unable to add signatures to a
7401 pending consensus, log the reason why. Closes ticket 24849.
7403 o Minor features (embedding):
7404 - Tor can now start with a preauthenticated control connection
7405 created by the process that launched it. This feature is meant for
7406 use by programs that want to launch and manage a Tor process
7407 without allowing other programs to manage it as well. For more
7408 information, see the __OwningControllerFD option documented in
7409 control-spec.txt. Closes ticket 23900.
7410 - On most errors that would cause Tor to exit, it now tries to
7411 return from the tor_main() function, rather than calling the
7412 system exit() function. Most users won't notice a difference here,
7413 but it should be significant for programs that run Tor inside a
7414 separate thread: they should now be able to survive Tor's exit
7415 conditions rather than having Tor shut down the entire process.
7416 Closes ticket 23848.
7417 - Applications that want to embed Tor can now tell Tor not to
7418 register any of its own POSIX signal handlers, using the
7419 __DisableSignalHandlers option. Closes ticket 24588.
7421 o Minor features (fallback directory list):
7422 - Avoid selecting fallbacks that change their IP addresses too
7423 often. Select more fallbacks by ignoring the Guard flag, and
7424 allowing lower cutoffs for the Running and V2Dir flags. Also allow
7425 a lower bandwidth, and a higher number of fallbacks per operator
7426 (5% of the list). Implements ticket 24785.
7427 - Update the fallback whitelist and blacklist based on opt-ins and
7428 relay changes. Closes tickets 22321, 24678, 22527, 24135,
7431 o Minor features (fallback directory mirror configuration):
7432 - Add a nickname to each fallback in a C comment. This makes it
7433 easier for operators to find their relays, and allows stem to use
7434 nicknames to identify fallbacks. Implements ticket 24600.
7435 - Add a type and version header to the fallback directory mirror
7436 file. Also add a delimiter to the end of each fallback entry. This
7437 helps external parsers like stem and Relay Search. Implements
7439 - Add an extrainfo cache flag for each fallback in a C comment. This
7440 allows stem to use fallbacks to fetch extra-info documents, rather
7441 than using authorities. Implements ticket 22759.
7442 - Add the generateFallbackDirLine.py script for automatically
7443 generating fallback directory mirror lines from relay fingerprints.
7444 No more typos! Add the lookupFallbackDirContact.py script for
7445 automatically looking up operator contact info from relay
7446 fingerprints. Implements ticket 24706, patch by teor and atagar.
7447 - Reject any fallback directory mirror that serves an expired
7448 consensus. Implements ticket 20942, patch by "minik".
7449 - Remove commas and equals signs from external string inputs to the
7450 fallback list. This avoids format confusion attacks. Implements
7452 - Remove the "weight=10" line from fallback directory mirror
7453 entries. Ticket 24681 will maintain the current fallback weights
7454 by changing Tor's default fallback weight to 10. Implements
7456 - Stop logging excessive information about fallback netblocks.
7457 Implements ticket 24791.
7459 o Minor features (forward-compatibility):
7460 - If a relay supports some link authentication protocol that we do
7461 not recognize, then include that relay's ed25519 key when telling
7462 other relays to extend to it. Previously, we treated future
7463 versions as if they were too old to support ed25519 link
7464 authentication. Closes ticket 20895.
7466 o Minor features (geoip):
7467 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
7468 database. Closes ticket 26104.
7470 o Minor features (heartbeat):
7471 - Add onion service information to our heartbeat logs, displaying
7472 stats about the activity of configured onion services. Closes
7475 o Minor features (instrumentation, development):
7476 - Add the MainloopStats option to allow developers to get
7477 instrumentation information from the main event loop via the
7478 heartbeat messages. We hope to use this to improve Tor's behavior
7479 when it's trying to sleep. Closes ticket 24605.
7481 o Minor features (IPv6):
7482 - Make IPv6-only clients wait for microdescs for relays, even if we
7483 were previously using descriptors (or were using them as a bridge)
7484 and have a cached descriptor for them. Implements ticket 23827.
7485 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
7486 them, rather than waiting to download microdescriptors. Implements
7489 o Minor features (log messages):
7490 - Improve log message in the out-of-memory handler to include
7491 information about memory usage from the different compression
7492 backends. Closes ticket 25372.
7493 - Improve a warning message that happens when we fail to re-parse an
7494 old router because of an expired certificate. Closes ticket 20020.
7495 - Make the log more quantitative when we hit MaxMemInQueues
7496 threshold exposing some values. Closes ticket 24501.
7498 o Minor features (logging):
7499 - Clarify the log messages produced when getrandom() or a related
7500 entropy-generation mechanism gives an error. Closes ticket 25120.
7501 - Added support for the Android logging subsystem. Closes
7504 o Minor features (performance):
7505 - Support predictive circuit building for onion service circuits
7506 with multiple layers of guards. Closes ticket 23101.
7507 - Use stdatomic.h where available, rather than mutexes, to implement
7508 atomic_counter_t. Closes ticket 23953.
7510 o Minor features (performance, 32-bit):
7511 - Improve performance on 32-bit systems by avoiding 64-bit division
7512 when calculating the timestamp in milliseconds for channel padding
7513 computations. Implements ticket 24613.
7514 - Improve performance on 32-bit systems by avoiding 64-bit division
7515 when timestamping cells and buffer chunks for OOM calculations.
7516 Implements ticket 24374.
7518 o Minor features (performance, OSX, iOS):
7519 - Use the mach_approximate_time() function (when available) to
7520 implement coarse monotonic time. Having a coarse time function
7521 should avoid a large number of system calls, and improve
7522 performance slightly, especially under load. Closes ticket 24427.
7524 o Minor features (performance, windows):
7525 - Improve performance on Windows Vista and Windows 7 by adjusting
7526 TCP send window size according to the recommendation from
7527 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
7530 o Minor features (sandbox):
7531 - Explicitly permit the poll() system call when the Linux
7532 seccomp2-based sandbox is enabled: apparently, some versions of
7533 libc use poll() when calling getpwnam(). Closes ticket 25313.
7535 o Minor features (storage, configuration):
7536 - Users can store cached directory documents somewhere other than
7537 the DataDirectory by using the CacheDirectory option. Similarly,
7538 the storage location for relay's keys can be overridden with the
7539 KeyDirectory option. Closes ticket 22703.
7541 o Minor features (testing):
7542 - Add a "make test-rust" target to run the rust tests only. Closes
7545 o Minor features (testing, debugging, embedding):
7546 - For development purposes, Tor now has a mode in which it runs for
7547 a few seconds, then stops, and starts again without exiting the
7548 process. This mode is meant to help us debug various issues with
7549 ticket 23847. To use this feature, compile with
7550 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
7551 environment variable. This is expected to crash a lot, and is
7552 really meant for developers only. It will likely be removed in a
7553 future release. Implements ticket 24583.
7555 o Minor bugfixes (build, rust):
7556 - Fix output of autoconf checks to display success messages for Rust
7557 dependencies and a suitable rustc compiler version. Fixes bug
7558 24612; bugfix on 0.3.1.3-alpha.
7559 - Don't pass the --quiet option to cargo: it seems to suppress some
7560 errors, which is not what we want to do when building. Fixes bug
7561 24518; bugfix on 0.3.1.7.
7562 - Build correctly when building from outside Tor's source tree with
7563 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
7566 o Minor bugfixes (C correctness):
7567 - Fix a very unlikely (impossible, we believe) null pointer
7568 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
7569 Coverity; this is CID 1430932.
7571 o Minor bugfixes (channel, client):
7572 - Better identify client connection when reporting to the geoip
7573 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
7575 o Minor bugfixes (circuit, cannibalization):
7576 - Don't cannibalize preemptively-built circuits if we no longer
7577 recognize their first hop. This situation can happen if our Guard
7578 relay went off the consensus after the circuit was created. Fixes
7579 bug 24469; bugfix on 0.0.6.
7581 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
7582 - Don't consider Tor running as a client if the ControlPort is open,
7583 but no actual client ports are open. Fixes bug 26062; bugfix
7586 o Minor bugfixes (compilation):
7587 - Fix a C99 compliance issue in our configuration script that caused
7588 compilation issues when compiling Tor with certain versions of
7589 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
7591 o Minor bugfixes (controller):
7592 - Restore the correct operation of the RESOLVE command, which had
7593 been broken since we added the ability to enable/disable DNS on
7594 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
7595 - Avoid a (nonfatal) assertion failure when extending a one-hop
7596 circuit from the controller to become a multihop circuit. Fixes
7597 bug 24903; bugfix on 0.2.5.2-alpha.
7599 o Minor bugfixes (correctness):
7600 - Remove a nonworking, unnecessary check to see whether a circuit
7601 hop's identity digest was set when the circuit failed. Fixes bug
7602 24927; bugfix on 0.2.4.4-alpha.
7604 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
7605 - Upon receiving a malformed connected cell, stop processing the
7606 cell immediately. Previously we would mark the connection for
7607 close, but continue processing the cell as if the connection were
7608 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
7610 o Minor bugfixes (directory authorities, IPv6):
7611 - When creating a routerstatus (vote) from a routerinfo (descriptor),
7612 set the IPv6 address to the unspecified IPv6 address, and
7613 explicitly initialize the port to zero. Fixes bug 24488; bugfix
7616 o Minor bugfixes (documentation):
7617 - Document that the PerConnBW{Rate,Burst} options will fall back to
7618 their corresponding consensus parameters only if those parameters
7619 are set. Previously we had claimed that these values would always
7620 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
7622 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
7623 - Stop saying in the manual that clients cache ipv4 dns answers from
7624 exit relays. We haven't used them since 0.2.6.3-alpha, and in
7625 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
7626 we forgot to say so in the man page. Fixes bug 26052; bugfix
7629 o Minor bugfixes (exit relay DNS retries):
7630 - Re-attempt timed-out DNS queries 3 times before failure, since our
7631 timeout is 5 seconds for them, but clients wait 10-15. Also allow
7632 slightly more timeouts per resolver when an exit has multiple
7633 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
7635 o Minor bugfixes (fallback directory mirrors):
7636 - Make updateFallbackDirs.py search harder for python. (Some OSs
7637 don't put it in /usr/bin.) Fixes bug 24708; bugfix
7640 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
7641 - When hibernating, close connections normally and allow them to
7642 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
7644 - Do not attempt to launch self-reachability tests when entering
7645 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
7646 - Resolve several bugs related to descriptor fetching on bridge
7647 clients with bandwidth accounting enabled. (This combination is
7648 not recommended!) Fixes a case of bug 12062; bugfix
7650 - When hibernating, do not attempt to launch DNS checks. Fixes a
7651 case of bug 12062; bugfix on 0.1.2.2-alpha.
7652 - When hibernating, do not try to upload or download descriptors.
7653 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
7655 o Minor bugfixes (IPv6, bridges):
7656 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
7657 bugfix on 0.2.8.2-alpha.
7658 - Tor now sets IPv6 address in the routerstatus as well as in the
7659 router descriptors when updating addresses for a bridge. Closes
7660 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
7662 o Minor bugfixes (Linux seccomp2 sandbox):
7663 - When running with the sandbox enabled, reload configuration files
7664 correctly even when %include was used. Previously we would crash.
7665 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
7667 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
7668 - Allow the nanosleep() system call, which glibc uses to implement
7669 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
7671 o Minor bugfixes (logging):
7672 - Fix a (mostly harmless) race condition when invoking
7673 LOG_PROTOCOL_WARN message from a subthread while the torrc options
7674 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
7676 o Minor bugfixes (man page, SocksPort):
7677 - Remove dead code from the old "SocksSocket" option, and rename
7678 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old
7679 option still works, but is deprecated. Fixes bug 24343; bugfix
7682 o Minor bugfixes (memory leaks):
7683 - Avoid possible at-exit memory leaks related to use of Libevent's
7684 event_base_once() function. (This function tends to leak memory if
7685 the event_base is closed before the event fires.) Fixes bug 24584;
7686 bugfix on 0.2.8.1-alpha.
7687 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
7690 o Minor bugfixes (network IPv6 test):
7691 - Tor's test scripts now check if "ping -6 ::1" works when the user
7692 runs "make test-network-all". Fixes bug 24677; bugfix on
7693 0.2.9.3-alpha. Patch by "ffmancera".
7695 o Minor bugfixes (networking):
7696 - string_is_valid_hostname() will not consider IP strings to be
7697 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
7699 o Minor bugfixes (onion service v3):
7700 - Avoid an assertion failure when the next onion service descriptor
7701 rotation type is out of sync with the consensus's valid-after
7702 time. Instead, log a warning message with extra information, so we
7703 can better hunt down the cause of this assertion. Fixes bug 25306;
7704 bugfix on 0.3.2.1-alpha.
7706 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
7707 - Fix a memory leak when a v3 onion service is configured and gets a
7708 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
7709 - When parsing the descriptor signature, look for the token plus an
7710 extra white-space at the end. This is more correct but also will
7711 allow us to support new fields that might start with "signature".
7712 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
7714 o Minor bugfixes (onion services):
7715 - If we are configured to offer a single onion service, don't log
7716 long-term established one hop rendezvous points in the heartbeat.
7717 Fixes bug 25116; bugfix on 0.2.9.6-rc.
7719 o Minor bugfixes (performance):
7720 - Reduce the number of circuits that will be opened at once during
7721 the circuit build timeout phase. This is done by increasing the
7722 idle timeout to 3 minutes, and lowering the maximum number of
7723 concurrent learning circuits to 10. Fixes bug 24769; bugfix
7725 - Avoid calling protocol_list_supports_protocol() from inside tight
7726 loops when running with cached routerinfo_t objects. Instead,
7727 summarize the relevant protocols as flags in the routerinfo_t, as
7728 we do for routerstatus_t objects. This change simplifies our code
7729 a little, and saves a large amount of short-term memory allocation
7730 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
7732 o Minor bugfixes (performance, timeouts):
7733 - Consider circuits for timeout as soon as they complete a hop. This
7734 is more accurate than applying the timeout in
7735 circuit_expire_building() because that function is only called
7736 once per second, which is now too slow for typical timeouts on the
7737 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
7738 - Use onion service circuits (and other circuits longer than 3 hops)
7739 to calculate a circuit build timeout. Previously, Tor only
7740 calculated its build timeout based on circuits that planned to be
7741 exactly 3 hops long. With this change, we include measurements
7742 from all circuits at the point where they complete their third
7743 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
7745 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
7746 - Avoid a crash when running with DirPort set but ORPort turned off.
7747 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
7749 o Minor bugfixes (Rust FFI):
7750 - Fix a minor memory leak which would happen whenever the C code
7751 would call the Rust implementation of
7752 protover_get_supported_protocols(). This was due to the C version
7753 returning a static string, whereas the Rust version newly allocated
7754 a CString to pass across the FFI boundary. Consequently, the C
7755 code was not expecting to need to free() what it was given. Fixes
7756 bug 25127; bugfix on 0.3.2.1-alpha.
7758 o Minor bugfixes (spelling):
7759 - Use the "misspell" tool to detect and fix typos throughout the
7760 source code. Fixes bug 23650; bugfix on various versions of Tor.
7761 Patch from Deepesh Pathak.
7763 o Minor bugfixes (testing):
7764 - Avoid intermittent test failures due to a test that had relied on
7765 onion service introduction point creation finishing within 5
7766 seconds of real clock time. Fixes bug 25450; bugfix
7768 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
7769 bugfix on 0.2.3.1-alpha.
7771 o Minor bugfixes (unit test, monotonic time):
7772 - Increase a constant (1msec to 10msec) in the monotonic time test
7773 that makes sure the nsec/usec/msec times read are synchronized.
7774 This change was needed to accommodate slow systems like armel or
7775 when the clock_gettime() is not a VDSO on the running kernel.
7776 Fixes bug 25113; bugfix on 0.2.9.1.
7778 o Code simplification and refactoring:
7779 - Move the list of default directory authorities to its own file.
7780 Closes ticket 24854. Patch by "beastr0".
7781 - Remove the old (deterministic) directory retry logic entirely:
7782 We've used exponential backoff exclusively for some time. Closes
7784 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
7786 - Remove a series of counters used to track circuit extend attempts
7787 and connection status but that in reality we aren't using for
7788 anything other than stats logged by a SIGUSR1 signal. Closes
7790 - Remove /usr/athena from search path in configure.ac. Closes
7792 - Remove duplicate code in node_has_curve25519_onion_key() and
7793 node_get_curve25519_onion_key(), and add a check for a zero
7794 microdesc curve25519 onion key. Closes ticket 23966, patch by
7795 "aruna1234" and teor.
7796 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
7797 memory allocations with large numbers of OR connections (e.g.
7798 relays). Closes ticket 24119.
7799 - Separate the function that deletes ephemeral files when Tor
7801 - Small changes to Tor's buf_t API to make it suitable for use as a
7802 general-purpose safe string constructor. Closes ticket 22342.
7803 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
7804 avoid source code identifier confusion. Closes ticket 24467.
7805 - The tor_git_revision[] constant no longer needs to be redeclared
7806 by everything that links against the rest of Tor. Done as part of
7807 ticket 23845, to simplify our external API.
7808 - We make extend_info_from_node() use node_get_curve25519_onion_key()
7809 introduced in ticket 23577 to access the curve25519 public keys
7810 rather than accessing it directly. Closes ticket 23760. Patch by
7812 - Add a function to log channels' scheduler state changes to aid
7813 debugging efforts. Closes ticket 24531.
7816 - Improved the documentation of AccountingStart parameter. Closes
7818 - Update the documentation for "Log" to include the current list of
7819 logging domains. Closes ticket 25378.
7820 - Add documentation on how to build tor with Rust dependencies
7821 without having to be online. Closes ticket 22907; bugfix
7823 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
7824 traffic. Closes ticket 24318.
7825 - Document that OutboundBindAddress doesn't apply to DNS requests.
7826 Closes ticket 22145. Patch from Aruna Maurya.
7828 o Code simplification and refactoring (channels):
7829 - Remove the incoming and outgoing channel queues. These were never
7830 used, but still took up a step in our fast path.
7831 - The majority of the channel unit tests have been rewritten and the
7832 code coverage has now been raised to 83.6% for channel.c. Closes
7834 - Remove other dead code from the channel subsystem: All together,
7835 this cleanup has removed more than 1500 lines of code overall and
7836 adding very little except for unit test.
7838 o Code simplification and refactoring (circuit rendezvous):
7839 - Split the client-side rendezvous circuit lookup into two
7840 functions: one that returns only established circuits and another
7841 that returns all kinds of circuits. Closes ticket 23459.
7843 o Code simplification and refactoring (controller):
7844 - Make most of the variables in networkstatus_getinfo_by_purpose()
7845 const. Implements ticket 24489.
7847 o Documentation (backport from 0.3.4.1-alpha):
7848 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
7849 ticket 25857. Patch from "CTassisF".
7851 o Documentation (man page):
7852 - The HiddenServiceVersion torrc option accepts only one number:
7853 either version 2 or 3. Closes ticket 25026; bugfix
7856 o Documentation (manpage, denial of service):
7857 - Provide more detail about the denial-of-service options, by
7858 listing each mitigation and explaining how they relate. Closes
7862 Changes in version 0.3.1.10 - 2018-03-03
7863 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
7866 It includes an important security fix for a remote crash attack
7867 against directory authorities, tracked as TROVE-2018-001.
7869 This release also backports our new system for improved resistance to
7870 denial-of-service attacks against relays.
7872 This release also fixes several minor bugs and annoyances from
7875 All directory authorities should upgrade to one of the versions
7876 released today. Relays running 0.3.1.x may wish to update to one of
7877 the versions released today, for the DoS mitigations.
7879 Please note: according to our release calendar, Tor 0.3.1 will no
7880 longer be supported after 1 July 2018. If you will be running Tor
7881 after that date, you should make sure to plan to upgrade to the latest
7882 stable version, or downgrade to 0.2.9 (which will receive long-term
7885 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
7886 - Fix a protocol-list handling bug that could be used to remotely crash
7887 directory authorities with a null-pointer exception. Fixes bug 25074;
7888 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
7891 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
7892 - Give relays some defenses against the recent network overload. We
7893 start with three defenses (default parameters in parentheses).
7894 First: if a single client address makes too many concurrent
7895 connections (>100), hang up on further connections. Second: if a
7896 single client address makes circuits too quickly (more than 3 per
7897 second, with an allowed burst of 90) while also having too many
7898 connections open (3), refuse new create cells for the next while
7899 (1-2 hours). Third: if a client asks to establish a rendezvous
7900 point to you directly, ignore the request. These defenses can be
7901 manually controlled by new torrc options, but relays will also
7902 take guidance from consensus parameters, so there's no need to
7903 configure anything manually. Implements ticket 24902.
7905 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
7906 - Update the sandbox rules so that they should now work correctly
7907 with Glibc 2.26. Closes ticket 24315.
7909 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
7910 - Fix an "off by 2" error in counting rendezvous failures on the
7911 onion service side. While we thought we would stop the rendezvous
7912 attempt after one failed circuit, we were actually making three
7913 circuit attempts before giving up. Now switch to a default of 2,
7914 and allow the consensus parameter "hs_service_max_rdv_failures" to
7915 override. Fixes bug 24895; bugfix on 0.0.6.
7917 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
7918 - Add Link protocol version 5 to the supported protocols list. Fixes
7919 bug 25070; bugfix on 0.3.1.1-alpha.
7921 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
7922 - Fix a set of false positives where relays would consider
7923 connections to other relays as being client-only connections (and
7924 thus e.g. deserving different link padding schemes) if those
7925 relays fell out of the consensus briefly. Now we look only at the
7926 initial handshake and whether the connection authenticated as a
7927 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
7929 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
7930 - Make our OOM handler aware of the geoip client history cache so it
7931 doesn't fill up the memory. This check is important for IPv6 and
7932 our DoS mitigation subsystem. Closes ticket 25122.
7934 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
7935 - Change relay bandwidth reporting stats interval from 4 hours to 24
7936 hours in order to reduce the efficiency of guard discovery
7937 attacks. Fixes ticket 23856.
7939 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
7940 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
7941 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
7942 since they neither disabled TLS 1.3 nor enabled any of the
7943 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
7944 Closes ticket 24978.
7946 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
7947 - The fallback directory list has been re-generated based on the
7948 current status of the network. Tor uses fallback directories to
7949 bootstrap when it doesn't yet have up-to-date directory
7950 information. Closes ticket 24801.
7951 - Make the default DirAuthorityFallbackRate 0.1, so that clients
7952 prefer to bootstrap from fallback directory mirrors. This is a
7953 follow-up to 24679, which removed weights from the default
7954 fallbacks. Implements ticket 24681.
7956 o Minor features (geoip):
7957 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
7960 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
7961 - Use the actual observed address of an incoming relay connection,
7962 not the canonical address of the relay from its descriptor, when
7963 making decisions about how to handle the incoming connection.
7964 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
7966 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
7967 - Directory authorities, when refusing a descriptor from a rejected
7968 relay, now explicitly tell the relay (in its logs) to set a valid
7969 ContactInfo address and contact the bad-relays@ mailing list.
7970 Fixes bug 25170; bugfix on 0.2.9.1.
7972 o Minor bugfixes (address selection, backport from 0.3.2.9):
7973 - When the fascist_firewall_choose_address_ functions don't find a
7974 reachable address, set the returned address to the null address
7975 and port. This is a precautionary measure, because some callers do
7976 not check the return value. Fixes bug 24736; bugfix
7979 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
7980 - Fetch descriptors aggressively whenever we lack enough to build
7981 circuits, regardless of how many descriptors we are missing.
7982 Previously, we would delay launching the fetch when we had fewer
7983 than 15 missing descriptors, even if some of those descriptors
7984 were blocking circuits from building. Fixes bug 23985; bugfix on
7985 0.1.1.11-alpha. The effects of this bug became worse in
7986 0.3.0.3-alpha, when we began treating missing descriptors from our
7987 primary guards as a reason to delay circuits.
7988 - Don't try fetching microdescriptors from relays that have failed
7989 to deliver them in the past. Fixes bug 23817; bugfix
7992 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
7993 - Fix a signed/unsigned comparison warning introduced by our fix to
7994 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
7996 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
7997 - Avoid a crash when attempting to use the seccomp2 sandbox together
7998 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
8001 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
8002 - Fix a possible crash on malformed consensus. If a consensus had
8003 contained an unparseable protocol line, it could have made clients
8004 and relays crash with a null-pointer exception. To exploit this
8005 issue, however, an attacker would need to be able to subvert the
8006 directory authority system. Fixes bug 25251; bugfix on
8007 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
8009 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
8010 - Recover better from empty or corrupt files in the consensus cache
8011 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
8012 - When a consensus diff calculation is only partially successful,
8013 only record the successful parts as having succeeded. Partial
8014 success can happen if (for example) one compression method fails
8015 but the others succeed. Previously we misrecorded all the
8016 calculations as having succeeded, which would later cause a
8017 nonfatal assertion failure. Fixes bug 24086; bugfix
8020 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
8021 - Tor now updates its guard state when it reads a consensus
8022 regardless of whether it's missing descriptors. That makes tor use
8023 its primary guards to fetch descriptors in some edge cases where
8024 it would previously have used fallback directories. Fixes bug
8025 23862; bugfix on 0.3.0.1-alpha.
8027 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
8028 - Don't treat inability to store a cached consensus object as a bug:
8029 it can happen normally when we are out of disk space. Fixes bug
8030 24859; bugfix on 0.3.1.1-alpha.
8032 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
8033 - When queuing DESTROY cells on a channel, only queue the circuit-id
8034 and reason fields: not the entire 514-byte cell. This fix should
8035 help mitigate any bugs or attacks that fill up these queues, and
8036 free more RAM for other uses. Fixes bug 24666; bugfix
8039 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
8040 - When closing a connection via close_connection_immediately(), we
8041 mark it as "not blocked on bandwidth", to prevent later calls from
8042 trying to unblock it, and give it permission to read. This fixes a
8043 backtrace warning that can happen on relays under various
8044 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
8046 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
8047 - When selecting relays by bandwidth, avoid a rounding error that
8048 could sometimes cause load to be imbalanced incorrectly.
8049 Previously, we would always round upwards; now, we round towards
8050 the nearest integer. This had the biggest effect when a relay's
8051 weight adjustments should have given it weight 0, but it got
8052 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
8053 - When calculating the fraction of nodes that have descriptors, and
8054 all nodes in the network have zero bandwidths, count the number of
8055 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
8056 - Actually log the total bandwidth in compute_weighted_bandwidths().
8057 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
8059 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
8060 - Improve the performance of our consensus-diff application code
8061 when Tor is built with the --enable-fragile-hardening option set.
8062 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
8064 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
8065 - Don't exit the Tor process if setrlimit() fails to change the file
8066 limit (which can happen sometimes on some versions of OSX). Fixes
8067 bug 21074; bugfix on 0.0.9pre5.
8069 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
8070 - Fix a bug in the bit-counting parts of our timing-wheel code on
8071 MSVC. (Note that MSVC is still not a supported build platform, due
8072 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
8075 o Minor bugfixes (relay, partial backport):
8076 - Make the internal channel_is_client() function look at what sort
8077 of connection handshake the other side used, rather than whether
8078 the other side ever sent a create_fast cell to us. Backports part
8079 of the fixes from bugs 22805 and 24898.
8081 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
8082 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
8084 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
8085 bugfix on 0.2.9.4-alpha.
8087 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
8088 - Update the "rust dependencies" submodule to be a project-level
8089 repository, rather than a user repository. Closes ticket 25323.
8092 Changes in version 0.2.9.15 - 2018-03-03
8093 Tor 0.2.9.15 backports important security and stability bugfixes from
8096 It includes an important security fix for a remote crash attack
8097 against directory authorities, tracked as TROVE-2018-001.
8099 This release also backports our new system for improved resistance to
8100 denial-of-service attacks against relays.
8102 This release also fixes several minor bugs and annoyances from
8105 All directory authorities should upgrade to one of the versions
8106 released today. Relays running 0.2.9.x may wish to update to one of
8107 the versions released today, for the DoS mitigations.
8109 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
8110 - Fix a protocol-list handling bug that could be used to remotely crash
8111 directory authorities with a null-pointer exception. Fixes bug 25074;
8112 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
8115 o Major features (denial-of-service mitigation):
8116 - Give relays some defenses against the recent network overload. We
8117 start with three defenses (default parameters in parentheses).
8118 First: if a single client address makes too many concurrent
8119 connections (>100), hang up on further connections. Second: if a
8120 single client address makes circuits too quickly (more than 3 per
8121 second, with an allowed burst of 90) while also having too many
8122 connections open (3), refuse new create cells for the next while
8123 (1-2 hours). Third: if a client asks to establish a rendezvous
8124 point to you directly, ignore the request. These defenses can be
8125 manually controlled by new torrc options, but relays will also
8126 take guidance from consensus parameters, so there's no need to
8127 configure anything manually. Implements ticket 24902.
8129 o Major bugfixes (bootstrapping):
8130 - Fetch descriptors aggressively whenever we lack enough to build
8131 circuits, regardless of how many descriptors we are missing.
8132 Previously, we would delay launching the fetch when we had fewer
8133 than 15 missing descriptors, even if some of those descriptors
8134 were blocking circuits from building. Fixes bug 23985; bugfix on
8135 0.1.1.11-alpha. The effects of this bug became worse in
8136 0.3.0.3-alpha, when we began treating missing descriptors from our
8137 primary guards as a reason to delay circuits.
8139 o Major bugfixes (onion services, retry behavior):
8140 - Fix an "off by 2" error in counting rendezvous failures on the
8141 onion service side. While we thought we would stop the rendezvous
8142 attempt after one failed circuit, we were actually making three
8143 circuit attempts before giving up. Now switch to a default of 2,
8144 and allow the consensus parameter "hs_service_max_rdv_failures" to
8145 override. Fixes bug 24895; bugfix on 0.0.6.
8147 o Minor feature (relay statistics):
8148 - Change relay bandwidth reporting stats interval from 4 hours to 24
8149 hours in order to reduce the efficiency of guard discovery
8150 attacks. Fixes ticket 23856.
8152 o Minor features (compatibility, OpenSSL):
8153 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
8154 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
8155 since they neither disabled TLS 1.3 nor enabled any of the
8156 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
8157 Closes ticket 24978.
8159 o Minor features (denial-of-service avoidance):
8160 - Make our OOM handler aware of the geoip client history cache so it
8161 doesn't fill up the memory. This check is important for IPv6 and
8162 our DoS mitigation subsystem. Closes ticket 25122.
8164 o Minor features (fallback directory mirrors):
8165 - The fallback directory list has been re-generated based on the
8166 current status of the network. Tor uses fallback directories to
8167 bootstrap when it doesn't yet have up-to-date directory
8168 information. Closes ticket 24801.
8169 - Make the default DirAuthorityFallbackRate 0.1, so that clients
8170 prefer to bootstrap from fallback directory mirrors. This is a
8171 follow-up to 24679, which removed weights from the default
8172 fallbacks. Implements ticket 24681.
8174 o Minor features (geoip):
8175 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
8178 o Minor features (linux seccomp2 sandbox):
8179 - Update the sandbox rules so that they should now work correctly
8180 with Glibc 2.26. Closes ticket 24315.
8182 o Minor bugfix (channel connection):
8183 - Use the actual observed address of an incoming relay connection,
8184 not the canonical address of the relay from its descriptor, when
8185 making decisions about how to handle the incoming connection.
8186 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
8188 o Minor bugfix (directory authority):
8189 - Directory authorities, when refusing a descriptor from a rejected
8190 relay, now explicitly tell the relay (in its logs) to set a valid
8191 ContactInfo address and contact the bad-relays@ mailing list.
8192 Fixes bug 25170; bugfix on 0.2.9.1.
8194 o Minor bugfixes (address selection):
8195 - When the fascist_firewall_choose_address_ functions don't find a
8196 reachable address, set the returned address to the null address
8197 and port. This is a precautionary measure, because some callers do
8198 not check the return value. Fixes bug 24736; bugfix
8201 o Minor bugfixes (compilation):
8202 - Fix a signed/unsigned comparison warning introduced by our fix to
8203 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
8205 o Minor bugfixes (control port, linux seccomp2 sandbox):
8206 - Avoid a crash when attempting to use the seccomp2 sandbox together
8207 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
8210 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
8211 - Fix a possible crash on malformed consensus. If a consensus had
8212 contained an unparseable protocol line, it could have made clients
8213 and relays crash with a null-pointer exception. To exploit this
8214 issue, however, an attacker would need to be able to subvert the
8215 directory authority system. Fixes bug 25251; bugfix on
8216 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
8218 o Minor bugfixes (memory usage):
8219 - When queuing DESTROY cells on a channel, only queue the circuit-id
8220 and reason fields: not the entire 514-byte cell. This fix should
8221 help mitigate any bugs or attacks that fill up these queues, and
8222 free more RAM for other uses. Fixes bug 24666; bugfix
8225 o Minor bugfixes (network layer):
8226 - When closing a connection via close_connection_immediately(), we
8227 mark it as "not blocked on bandwidth", to prevent later calls from
8228 trying to unblock it, and give it permission to read. This fixes a
8229 backtrace warning that can happen on relays under various
8230 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
8232 o Minor bugfixes (OSX):
8233 - Don't exit the Tor process if setrlimit() fails to change the file
8234 limit (which can happen sometimes on some versions of OSX). Fixes
8235 bug 21074; bugfix on 0.0.9pre5.
8237 o Minor bugfixes (path selection):
8238 - When selecting relays by bandwidth, avoid a rounding error that
8239 could sometimes cause load to be imbalanced incorrectly.
8240 Previously, we would always round upwards; now, we round towards
8241 the nearest integer. This had the biggest effect when a relay's
8242 weight adjustments should have given it weight 0, but it got
8243 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
8244 - When calculating the fraction of nodes that have descriptors, and
8245 all nodes in the network have zero bandwidths, count the number of
8246 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
8247 - Actually log the total bandwidth in compute_weighted_bandwidths().
8248 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
8250 o Minor bugfixes (portability, msvc):
8251 - Fix a bug in the bit-counting parts of our timing-wheel code on
8252 MSVC. (Note that MSVC is still not a supported build platform, due
8253 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
8256 o Minor bugfixes (relay):
8257 - Make the internal channel_is_client() function look at what sort
8258 of connection handshake the other side used, rather than whether
8259 the other side ever sent a create_fast cell to us. Backports part
8260 of the fixes from bugs 22805 and 24898.
8262 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
8263 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
8265 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
8266 bugfix on 0.2.9.4-alpha.
8269 Changes in version 0.3.2.10 - 2018-03-03
8270 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
8271 backports a number of bugfixes, including important fixes for security
8274 It includes an important security fix for a remote crash attack
8275 against directory authorities, tracked as TROVE-2018-001.
8277 Additionally, it backports a fix for a bug whose severity we have
8278 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
8279 triggered in order to crash relays with a use-after-free pattern. As
8280 such, we are now tracking that bug as TROVE-2018-002 and
8281 CVE-2018-0491, and backporting it to earlier releases. This bug
8282 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
8285 This release also backports our new system for improved resistance to
8286 denial-of-service attacks against relays.
8288 This release also fixes several minor bugs and annoyances from
8291 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
8292 today, for the fix to TROVE-2018-002. Directory authorities should
8293 also upgrade. (Relays on earlier versions might want to update too for
8294 the DoS mitigations.)
8296 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
8297 - Fix a protocol-list handling bug that could be used to remotely crash
8298 directory authorities with a null-pointer exception. Fixes bug 25074;
8299 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
8302 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
8303 - Avoid adding the same channel twice in the KIST scheduler pending
8304 list, which could lead to remote denial-of-service use-after-free
8305 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
8307 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
8308 - Give relays some defenses against the recent network overload. We
8309 start with three defenses (default parameters in parentheses).
8310 First: if a single client address makes too many concurrent
8311 connections (>100), hang up on further connections. Second: if a
8312 single client address makes circuits too quickly (more than 3 per
8313 second, with an allowed burst of 90) while also having too many
8314 connections open (3), refuse new create cells for the next while
8315 (1-2 hours). Third: if a client asks to establish a rendezvous
8316 point to you directly, ignore the request. These defenses can be
8317 manually controlled by new torrc options, but relays will also
8318 take guidance from consensus parameters, so there's no need to
8319 configure anything manually. Implements ticket 24902.
8321 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
8322 - Fix an "off by 2" error in counting rendezvous failures on the
8323 onion service side. While we thought we would stop the rendezvous
8324 attempt after one failed circuit, we were actually making three
8325 circuit attempts before giving up. Now switch to a default of 2,
8326 and allow the consensus parameter "hs_service_max_rdv_failures" to
8327 override. Fixes bug 24895; bugfix on 0.0.6.
8328 - New-style (v3) onion services now obey the "max rendezvous circuit
8329 attempts" logic. Previously they would make as many rendezvous
8330 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
8331 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
8333 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
8334 - Add Link protocol version 5 to the supported protocols list. Fixes
8335 bug 25070; bugfix on 0.3.1.1-alpha.
8337 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
8338 - Fix a set of false positives where relays would consider
8339 connections to other relays as being client-only connections (and
8340 thus e.g. deserving different link padding schemes) if those
8341 relays fell out of the consensus briefly. Now we look only at the
8342 initial handshake and whether the connection authenticated as a
8343 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
8345 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
8346 - The scheduler subsystem was failing to promptly notice changes in
8347 consensus parameters, making it harder to switch schedulers
8348 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
8350 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
8351 - Make our OOM handler aware of the geoip client history cache so it
8352 doesn't fill up the memory. This check is important for IPv6 and
8353 our DoS mitigation subsystem. Closes ticket 25122.
8355 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
8356 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
8357 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
8358 since they neither disabled TLS 1.3 nor enabled any of the
8359 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
8360 Closes ticket 24978.
8362 o Minor features (geoip):
8363 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
8366 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
8367 - When logging a failure to create an onion service's descriptor,
8368 also log what the problem with the descriptor was. Diagnostic
8371 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
8372 - Use the actual observed address of an incoming relay connection,
8373 not the canonical address of the relay from its descriptor, when
8374 making decisions about how to handle the incoming connection.
8375 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
8377 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
8378 - Fix a possible crash on malformed consensus. If a consensus had
8379 contained an unparseable protocol line, it could have made clients
8380 and relays crash with a null-pointer exception. To exploit this
8381 issue, however, an attacker would need to be able to subvert the
8382 directory authority system. Fixes bug 25251; bugfix on
8383 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
8385 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
8386 - Directory authorities, when refusing a descriptor from a rejected
8387 relay, now explicitly tell the relay (in its logs) to set a valid
8388 ContactInfo address and contact the bad-relays@ mailing list.
8389 Fixes bug 25170; bugfix on 0.2.9.1.
8391 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
8392 - When building with Rust on OSX, link against libresolv, to work
8393 around the issue at https://github.com/rust-lang/rust/issues/46797.
8394 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
8396 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
8397 - Remove a BUG() statement when a client fetches an onion descriptor
8398 that has a lower revision counter than the one in its cache. This
8399 can happen in normal circumstances due to HSDir desync. Fixes bug
8400 24976; bugfix on 0.3.2.1-alpha.
8402 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
8403 - Don't treat inability to store a cached consensus object as a bug:
8404 it can happen normally when we are out of disk space. Fixes bug
8405 24859; bugfix on 0.3.1.1-alpha.
8407 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
8408 - Improve the performance of our consensus-diff application code
8409 when Tor is built with the --enable-fragile-hardening option set.
8410 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
8412 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
8413 - Don't exit the Tor process if setrlimit() fails to change the file
8414 limit (which can happen sometimes on some versions of OSX). Fixes
8415 bug 21074; bugfix on 0.0.9pre5.
8417 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
8418 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
8420 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
8421 bugfix on 0.2.9.4-alpha.
8423 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
8424 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
8425 25005; bugfix on 0.3.2.7-rc.
8427 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
8428 - Look at the "HSRend" protocol version, not the "HSDir" protocol
8429 version, when deciding whether a consensus entry can support the
8430 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
8431 bugfix on 0.3.2.1-alpha.
8433 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
8434 - Update the "rust dependencies" submodule to be a project-level
8435 repository, rather than a user repository. Closes ticket 25323.
8437 o Documentation (backport from 0.3.3.1-alpha)
8438 - Document that operators who run more than one relay or bridge are
8439 expected to set MyFamily and ContactInfo correctly. Closes
8443 Changes in version 0.3.2.9 - 2018-01-09
8444 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
8446 The 0.3.2 series includes our long-anticipated new onion service
8447 design, with numerous security features. (For more information, see
8448 our blog post at https://blog.torproject.org/fall-harvest.) We also
8449 have a new circuit scheduler algorithm for improved performance on
8450 relays everywhere (see https://blog.torproject.org/kist-and-tell),
8451 along with many smaller features and bugfixes.
8453 Per our stable release policy, we plan to support each stable release
8454 series for at least the next nine months, or for three months after
8455 the first stable release of the next series: whichever is longer. If
8456 you need a release with long-term support, we recommend that you stay
8457 with the 0.2.9 series.
8459 Below is a list of the changes since 0.3.1.7. For a list of all
8460 changes since 0.3.2.8-rc, see the ChangeLog file.
8462 o Directory authority changes:
8463 - Add "Bastet" as a ninth directory authority to the default list.
8464 Closes ticket 23910.
8465 - The directory authority "Longclaw" has changed its IP address.
8466 Closes ticket 23592.
8467 - Remove longclaw's IPv6 address, as it will soon change. Authority
8468 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
8469 3/8 directory authorities with IPv6 addresses, but there are also
8470 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
8471 - Add an IPv6 address for the "bastet" directory authority. Closes
8474 o Major features (next-generation onion services):
8475 - Tor now supports the next-generation onion services protocol for
8476 clients and services! As part of this release, the core of
8477 proposal 224 has been implemented and is available for
8478 experimentation and testing by our users. This newer version of
8479 onion services ("v3") features many improvements over the legacy
8482 a) Better crypto (replaced SHA1/DH/RSA1024
8483 with SHA3/ed25519/curve25519)
8485 b) Improved directory protocol, leaking much less information to
8488 c) Improved directory protocol, with smaller surface for
8491 d) Better onion address security against impersonation.
8493 e) More extensible introduction/rendezvous protocol.
8495 f) A cleaner and more modular codebase.
8497 You can identify a next-generation onion address by its length:
8498 they are 56 characters long, as in
8499 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
8501 In the future, we will release more options and features for v3
8502 onion services, but we first need a testing period, so that the
8503 current codebase matures and becomes more robust. Planned features
8504 include: offline keys, advanced client authorization, improved
8505 guard algorithms, and statistics. For full details, see
8508 Legacy ("v2") onion services will still work for the foreseeable
8509 future, and will remain the default until this new codebase gets
8510 tested and hardened. Service operators who want to experiment with
8511 the new system can use the 'HiddenServiceVersion 3' torrc
8512 directive along with the regular onion service configuration
8513 options. For more information, see our blog post at
8514 "https://blog.torproject.org/fall-harvest". Enjoy!
8516 o Major feature (scheduler, channel):
8517 - Tor now uses new schedulers to decide which circuits should
8518 deliver cells first, in order to improve congestion at relays. The
8519 first type is called "KIST" ("Kernel Informed Socket Transport"),
8520 and is only available on Linux-like systems: it uses feedback from
8521 the kernel to prevent the kernel's TCP buffers from growing too
8522 full. The second new scheduler type is called "KISTLite": it
8523 behaves the same as KIST, but runs on systems without kernel
8524 support for inspecting TCP implementation details. The old
8525 scheduler is still available, under the name "Vanilla". To change
8526 the default scheduler preference order, use the new "Schedulers"
8527 option. (The default preference order is "KIST,KISTLite,Vanilla".)
8529 Matt Traudt implemented KIST, based on research by Rob Jansen,
8530 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
8531 more information, see the design paper at
8532 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
8533 followup implementation paper at https://arxiv.org/abs/1709.01044.
8534 Closes ticket 12541. For more information, see our blog post at
8535 "https://blog.torproject.org/kist-and-tell".
8537 o Major bugfixes (security, general):
8538 - Fix a denial of service bug where an attacker could use a
8539 malformed directory object to cause a Tor instance to pause while
8540 OpenSSL would try to read a passphrase from the terminal. (Tor
8541 instances run without a terminal, which is the case for most Tor
8542 packages, are not impacted.) Fixes bug 24246; bugfix on every
8543 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
8544 Found by OSS-Fuzz as testcase 6360145429790720.
8546 o Major bugfixes (security, directory authority):
8547 - Fix a denial of service issue where an attacker could crash a
8548 directory authority using a malformed router descriptor. Fixes bug
8549 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
8552 o Major bugfixes (security, onion service v2):
8553 - Fix a use-after-free error that could crash v2 Tor onion services
8554 when they failed to open circuits while expiring introduction
8555 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
8556 also tracked as TROVE-2017-013 and CVE-2017-8823.
8557 - When checking for replays in the INTRODUCE1 cell data for a
8558 (legacy) onion service, correctly detect replays in the RSA-
8559 encrypted part of the cell. We were previously checking for
8560 replays on the entire cell, but those can be circumvented due to
8561 the malleability of Tor's legacy hybrid encryption. This fix helps
8562 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
8563 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
8566 o Major bugfixes (security, relay):
8567 - When running as a relay, make sure that we never build a path
8568 through ourselves, even in the case where we have somehow lost the
8569 version of our descriptor appearing in the consensus. Fixes part
8570 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
8571 as TROVE-2017-012 and CVE-2017-8822.
8572 - When running as a relay, make sure that we never choose ourselves
8573 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
8574 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
8576 o Major bugfixes (bootstrapping):
8577 - Fetch descriptors aggressively whenever we lack enough to build
8578 circuits, regardless of how many descriptors we are missing.
8579 Previously, we would delay launching the fetch when we had fewer
8580 than 15 missing descriptors, even if some of those descriptors
8581 were blocking circuits from building. Fixes bug 23985; bugfix on
8582 0.1.1.11-alpha. The effects of this bug became worse in
8583 0.3.0.3-alpha, when we began treating missing descriptors from our
8584 primary guards as a reason to delay circuits.
8585 - Don't try fetching microdescriptors from relays that have failed
8586 to deliver them in the past. Fixes bug 23817; bugfix
8589 o Major bugfixes (circuit prediction):
8590 - Fix circuit prediction logic so that a client doesn't treat a port
8591 as being "handled" by a circuit if that circuit already has
8592 isolation settings on it. This change should make Tor clients more
8593 responsive by improving their chances of having a pre-created
8594 circuit ready for use when a request arrives. Fixes bug 18859;
8595 bugfix on 0.2.3.3-alpha.
8597 o Major bugfixes (exit relays, DNS):
8598 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
8599 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
8600 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
8601 identifying and finding a workaround to this bug and to Moritz,
8602 Arthur Edelstein, and Roger for helping to track it down and
8605 o Major bugfixes (relay, crash, assertion failure):
8606 - Fix a timing-based assertion failure that could occur when the
8607 circuit out-of-memory handler freed a connection's output buffer.
8608 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
8610 o Major bugfixes (usability, control port):
8611 - Report trusted clock skew indications as bootstrap errors, so
8612 controllers can more easily alert users when their clocks are
8613 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
8615 o Minor features (bridge):
8616 - Bridge relays can now set the BridgeDistribution config option to
8617 add a "bridge-distribution-request" line to their bridge
8618 descriptor, which tells BridgeDB how they'd like their bridge
8619 address to be given out. (Note that as of Oct 2017, BridgeDB does
8620 not yet implement this feature.) As a side benefit, this feature
8621 provides a way to distinguish bridge descriptors from non-bridge
8622 descriptors. Implements tickets 18329.
8623 - When handling the USERADDR command on an ExtOrPort, warn when the
8624 transports provides a USERADDR with no port. In a future version,
8625 USERADDR commands of this format may be rejected. Detects problems
8626 related to ticket 23080.
8628 o Minor features (bug detection):
8629 - Log a warning message with a stack trace for any attempt to call
8630 get_options() during option validation. This pattern has caused
8631 subtle bugs in the past. Closes ticket 22281.
8633 o Minor features (build, compilation):
8634 - The "check-changes" feature is now part of the "make check" tests;
8635 we'll use it to try to prevent misformed changes files from
8636 accumulating. Closes ticket 23564.
8637 - Tor builds should now fail if there are any mismatches between the
8638 C type representing a configuration variable and the C type the
8639 data-driven parser uses to store a value there. Previously, we
8640 needed to check these by hand, which sometimes led to mistakes.
8641 Closes ticket 23643.
8643 o Minor features (client):
8644 - You can now use Tor as a tunneled HTTP proxy: use the new
8645 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
8646 requests. Closes ticket 22407.
8647 - Add an extra check to make sure that we always use the newer guard
8648 selection code for picking our guards. Closes ticket 22779.
8649 - When downloading (micro)descriptors, don't split the list into
8650 multiple requests unless we want at least 32 descriptors.
8651 Previously, we split at 4, not 32, which led to significant
8652 overhead in HTTP request size and degradation in compression
8653 performance. Closes ticket 23220.
8654 - Improve log messages when missing descriptors for primary guards.
8655 Resolves ticket 23670.
8657 o Minor features (command line):
8658 - Add a new commandline option, --key-expiration, which prints when
8659 the current signing key is going to expire. Implements ticket
8660 17639; patch by Isis Lovecruft.
8662 o Minor features (control port):
8663 - If an application tries to use the control port as an HTTP proxy,
8664 respond with a meaningful "This is the Tor control port" message,
8665 and log the event. Closes ticket 1667. Patch from Ravi
8667 - Provide better error message for GETINFO desc/(id|name) when not
8668 fetching router descriptors. Closes ticket 5847. Patch by
8670 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
8671 whether Tor will try to download router descriptors and
8672 microdescriptors respectively. Closes ticket 22684.
8673 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
8674 so controllers can tell whether the geoip databases are loaded.
8675 Closes ticket 23237.
8676 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
8677 events. Closes ticket 19254. Patch by "DonnchaC".
8679 o Minor features (development support):
8680 - Developers can now generate a call-graph for Tor using the
8681 "calltool" python program, which post-processes object dumps. It
8682 should work okay on many Linux and OSX platforms, and might work
8683 elsewhere too. To run it, install calltool from
8684 https://gitweb.torproject.org/user/nickm/calltool.git and run
8685 "make callgraph". Closes ticket 19307.
8687 o Minor features (directory authority):
8688 - Make the "Exit" flag assignment only depend on whether the exit
8689 policy allows connections to ports 80 and 443. Previously relays
8690 would get the Exit flag if they allowed connections to one of
8691 these ports and also port 6667. Resolves ticket 23637.
8693 o Minor features (ed25519):
8694 - Add validation function to checks for torsion components in
8695 ed25519 public keys, used by prop224 client-side code. Closes
8696 ticket 22006. Math help by Ian Goldberg.
8698 o Minor features (exit relay, DNS):
8699 - Improve the clarity and safety of the log message from evdns when
8700 receiving an apparently spoofed DNS reply. Closes ticket 3056.
8702 o Minor features (fallback directory mirrors):
8703 - The fallback directory list has been re-generated based on the
8704 current status of the network. Tor uses fallback directories to
8705 bootstrap when it doesn't yet have up-to-date directory
8706 information. Closes ticket 24801.
8707 - Make the default DirAuthorityFallbackRate 0.1, so that clients
8708 prefer to bootstrap from fallback directory mirrors. This is a
8709 follow-up to 24679, which removed weights from the default
8710 fallbacks. Implements ticket 24681.
8712 o Minor features (geoip):
8713 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
8716 o Minor features (integration, hardening):
8717 - Add a new NoExec option to prevent Tor from running other
8718 programs. When this option is set to 1, Tor will never try to run
8719 another program, regardless of the settings of
8720 PortForwardingHelper, ClientTransportPlugin, or
8721 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
8722 without restarting Tor. Closes ticket 22976.
8724 o Minor features (linux seccomp2 sandbox):
8725 - Update the sandbox rules so that they should now work correctly
8726 with Glibc 2.26. Closes ticket 24315.
8728 o Minor features (logging):
8729 - Provide better warnings when the getrandom() syscall fails. Closes
8731 - Downgrade a pair of log messages that could occur when an exit's
8732 resolver gave us an unusual (but not forbidden) response. Closes
8734 - Improve the message we log when re-enabling circuit build timeouts
8735 after having received a consensus. Closes ticket 20963.
8736 - Log more circuit information whenever we are about to try to
8737 package a relay cell on a circuit with a nonexistent n_chan.
8738 Attempt to diagnose ticket 8185.
8739 - Improve info-level log identification of particular circuits, to
8740 help with debugging. Closes ticket 23645.
8741 - Improve the warning message for specifying a relay by nickname.
8742 The previous message implied that nickname registration was still
8743 part of the Tor network design, which it isn't. Closes
8745 - If the sandbox filter fails to load, suggest to the user that
8746 their kernel might not support seccomp2. Closes ticket 23090.
8748 o Minor features (onion service, circuit, logging):
8749 - Improve logging of many callsite in the circuit subsystem to print
8750 the circuit identifier(s).
8751 - Log when we cleanup an intro point from a service so we know when
8752 and for what reason it happened. Closes ticket 23604.
8754 o Minor features (portability):
8755 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
8756 (It doesn't yet work with the sandbox enabled.) Closes
8758 - Check at configure time whether uint8_t is the same type as
8759 unsigned char. Lots of existing code already makes this
8760 assumption, and there could be strict aliasing issues if the
8761 assumption is violated. Closes ticket 22410.
8763 o Minor features (relay):
8764 - When choosing which circuits can be expired as unused, consider
8765 circuits from clients even if those clients used regular CREATE
8766 cells to make them; and do not consider circuits from relays even
8767 if they were made with CREATE_FAST. Part of ticket 22805.
8768 - Reject attempts to use relative file paths when RunAsDaemon is
8769 set. Previously, Tor would accept these, but the directory-
8770 changing step of RunAsDaemon would give strange and/or confusing
8771 results. Closes ticket 22731.
8773 o Minor features (relay statistics):
8774 - Change relay bandwidth reporting stats interval from 4 hours to 24
8775 hours in order to reduce the efficiency of guard discovery
8776 attacks. Fixes ticket 23856.
8778 o Minor features (reverted deprecations):
8779 - The ClientDNSRejectInternalAddresses flag can once again be set in
8780 non-testing Tor networks, so long as they do not use the default
8781 directory authorities. This change also removes the deprecation of
8782 this flag from 0.2.9.2-alpha. Closes ticket 21031.
8784 o Minor features (robustness):
8785 - Change several fatal assertions when flushing buffers into non-
8786 fatal assertions, to prevent any recurrence of 23690.
8788 o Minor features (startup, safety):
8789 - When configured to write a PID file, Tor now exits if it is unable
8790 to do so. Previously, it would warn and continue. Closes
8793 o Minor features (static analysis):
8794 - The BUG() macro has been changed slightly so that Coverity no
8795 longer complains about dead code if the bug is impossible. Closes
8798 o Minor features (testing):
8799 - Our fuzzing tests now test the encrypted portions of v3 onion
8800 service descriptors. Implements more of 21509.
8801 - Add a unit test to make sure that our own generated platform
8802 string will be accepted by directory authorities. Closes
8804 - The default chutney network tests now include tests for the v3
8805 onion service design. Make sure you have the latest version of
8806 chutney if you want to run these. Closes ticket 22437.
8807 - Add a unit test to verify that we can parse a hardcoded v2 onion
8808 service descriptor. Closes ticket 15554.
8810 o Minor bugfixes (address selection):
8811 - When the fascist_firewall_choose_address_ functions don't find a
8812 reachable address, set the returned address to the null address
8813 and port. This is a precautionary measure, because some callers do
8814 not check the return value. Fixes bug 24736; bugfix
8817 o Minor bugfixes (bootstrapping):
8818 - When warning about state file clock skew, report the correct
8819 direction for the detected skew. Fixes bug 23606; bugfix
8822 o Minor bugfixes (bridge clients, bootstrap):
8823 - Retry directory downloads when we get our first bridge descriptor
8824 during bootstrap or while reconnecting to the network. Keep
8825 retrying every time we get a bridge descriptor, until we have a
8826 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
8827 - Stop delaying bridge descriptor fetches when we have cached bridge
8828 descriptors. Instead, only delay bridge descriptor fetches when we
8829 have at least one reachable bridge. Fixes part of bug 24367;
8830 bugfix on 0.2.0.3-alpha.
8831 - Stop delaying directory fetches when we have cached bridge
8832 descriptors. Instead, only delay bridge descriptor fetches when
8833 all our bridges are definitely unreachable. Fixes part of bug
8834 24367; bugfix on 0.2.0.3-alpha.
8836 o Minor bugfixes (bridge):
8837 - Overwrite the bridge address earlier in the process of retrieving
8838 its descriptor, to make sure we reach it on the configured
8839 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
8841 o Minor bugfixes (build, compilation):
8842 - Fix a compilation warning when building with zstd support on
8843 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
8844 and fixed by Andreas Stieger.
8845 - When searching for OpenSSL, don't accept any OpenSSL library that
8846 lacks TLSv1_1_method(): Tor doesn't build with those versions.
8847 Additionally, look in /usr/local/opt/openssl, if it's present.
8848 These changes together repair the default build on OSX systems
8849 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
8850 - Fix a signed/unsigned comparison warning introduced by our fix to
8851 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
8852 - Fix a memory leak warning in one of the libevent-related
8853 configuration tests that could occur when manually specifying
8854 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
8855 Found and patched by Alex Xu.
8856 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
8857 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
8859 o Minor bugfixes (certificate handling):
8860 - Fix a time handling bug in Tor certificates set to expire after
8861 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
8862 Coverity as CID 1415728.
8864 o Minor bugfixes (client):
8865 - By default, do not enable storage of client-side DNS values. These
8866 values were unused by default previously, but they should not have
8867 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
8869 o Minor bugfixes (client, usability):
8870 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
8871 SOCKS4a requests that contain IP address strings, even when
8872 SafeSocks in enabled, as this prevents user from connecting to
8873 known IP addresses without relying on DNS for resolving. SafeSocks
8874 still rejects SOCKS connections that connect to IP addresses when
8875 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
8876 bugfix on Tor 0.2.6.2-alpha.
8878 o Minor bugfixes (code correctness):
8879 - Call htons() in extend_cell_format() for encoding a 16-bit value.
8880 Previously we used ntohs(), which happens to behave the same on
8881 all the platforms we support, but which isn't really correct.
8882 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
8883 - For defense-in-depth, make the controller's write_escaped_data()
8884 function robust to extremely long inputs. Fixes bug 19281; bugfix
8885 on 0.1.1.1-alpha. Reported by Guido Vranken.
8886 - Fix several places in our codebase where a C compiler would be
8887 likely to eliminate a check, based on assuming that undefined
8888 behavior had not happened elsewhere in the code. These cases are
8889 usually a sign of redundant checking or dubious arithmetic. Found
8890 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
8891 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
8894 o Minor bugfixes (compression):
8895 - Handle a pathological case when decompressing Zstandard data when
8896 the output buffer size is zero. Fixes bug 23551; bugfix
8899 o Minor bugfixes (consensus expiry):
8900 - Check for adequate directory information correctly. Previously, Tor
8901 would reconsider whether it had sufficient directory information
8902 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
8904 o Minor bugfixes (control port, linux seccomp2 sandbox):
8905 - Avoid a crash when attempting to use the seccomp2 sandbox together
8906 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
8909 o Minor bugfixes (control port, onion services):
8910 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
8911 HS_DESC event when a service is not able to upload a descriptor.
8912 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
8914 o Minor bugfixes (directory cache):
8915 - Recover better from empty or corrupt files in the consensus cache
8916 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
8917 - When a consensus diff calculation is only partially successful,
8918 only record the successful parts as having succeeded. Partial
8919 success can happen if (for example) one compression method fails
8920 but the others succeed. Previously we misrecorded all the
8921 calculations as having succeeded, which would later cause a
8922 nonfatal assertion failure. Fixes bug 24086; bugfix
8925 o Minor bugfixes (directory client):
8926 - On failure to download directory information, delay retry attempts
8927 by a random amount based on the "decorrelated jitter" algorithm.
8928 Our previous delay algorithm tended to produce extra-long delays
8929 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
8931 o Minor bugfixes (directory protocol):
8932 - Directory servers now include a "Date:" http header for response
8933 codes other than 200. Clients starting with a skewed clock and a
8934 recent consensus were getting "304 Not modified" responses from
8935 directory authorities, so without the Date header, the client
8936 would never hear about a wrong clock. Fixes bug 23499; bugfix
8938 - Make clients wait for 6 seconds before trying to download a
8939 consensus from an authority. Fixes bug 17750; bugfix
8942 o Minor bugfixes (documentation):
8943 - Document better how to read gcov, and what our gcov postprocessing
8944 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
8945 - Fix manpage to not refer to the obsolete (and misspelled)
8946 UseEntryGuardsAsDirectoryGuards parameter in the description of
8947 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
8949 o Minor bugfixes (DoS-resistance):
8950 - If future code asks if there are any running bridges, without
8951 checking if bridges are enabled, log a BUG warning rather than
8952 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
8954 o Minor bugfixes (entry guards):
8955 - Tor now updates its guard state when it reads a consensus
8956 regardless of whether it's missing descriptors. That makes tor use
8957 its primary guards to fetch descriptors in some edge cases where
8958 it would previously have used fallback directories. Fixes bug
8959 23862; bugfix on 0.3.0.1-alpha.
8961 o Minor bugfixes (format strictness):
8962 - Restrict several data formats to decimal. Previously, the
8963 BuildTimeHistogram entries in the state file, the "bw=" entries in
8964 the bandwidth authority file, and the process IDs passed to the
8965 __OwningControllerProcess option could all be specified in hex or
8966 octal as well as in decimal. This was not an intentional feature.
8967 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
8970 o Minor bugfixes (heartbeat):
8971 - If we fail to write a heartbeat message, schedule a retry for the
8972 minimum heartbeat interval number of seconds in the future. Fixes
8973 bug 19476; bugfix on 0.2.3.1-alpha.
8975 o Minor bugfixes (logging):
8976 - Suppress a log notice when relay descriptors arrive. We already
8977 have a bootstrap progress for this so no need to log notice
8978 everytime tor receives relay descriptors. Microdescriptors behave
8979 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
8980 - Remove duplicate log messages regarding opening non-local
8981 SocksPorts upon parsing config and opening listeners at startup.
8982 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
8983 - Use a more comprehensible log message when telling the user
8984 they've excluded every running exit node. Fixes bug 7890; bugfix
8986 - When logging the number of descriptors we intend to download per
8987 directory request, do not log a number higher than then the number
8988 of descriptors we're fetching in total. Fixes bug 19648; bugfix
8990 - When warning about a directory owned by the wrong user, log the
8991 actual name of the user owning the directory. Previously, we'd log
8992 the name of the process owner twice. Fixes bug 23487; bugfix
8994 - Fix some messages on unexpected errors from the seccomp2 library.
8995 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
8996 - The tor specification says hop counts are 1-based, so fix two log
8997 messages that mistakenly logged 0-based hop counts. Fixes bug
8998 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
8999 Credit to Xiaofan Li for reporting this issue.
9001 o Minor bugfixes (logging, relay shutdown, annoyance):
9002 - When a circuit is marked for close, do not attempt to package any
9003 cells for channels on that circuit. Previously, we would detect
9004 this condition lower in the call stack, when we noticed that the
9005 circuit had no attached channel, and log an annoying message.
9006 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
9008 o Minor bugfixes (memory safety, defensive programming):
9009 - Clear the target address when node_get_prim_orport() returns
9010 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
9012 o Minor bugfixes (memory usage):
9013 - When queuing DESTROY cells on a channel, only queue the circuit-id
9014 and reason fields: not the entire 514-byte cell. This fix should
9015 help mitigate any bugs or attacks that fill up these queues, and
9016 free more RAM for other uses. Fixes bug 24666; bugfix
9019 o Minor bugfixes (network layer):
9020 - When closing a connection via close_connection_immediately(), we
9021 mark it as "not blocked on bandwidth", to prevent later calls from
9022 trying to unblock it, and give it permission to read. This fixes a
9023 backtrace warning that can happen on relays under various
9024 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
9026 o Minor bugfixes (onion services):
9027 - The introduction circuit was being timed out too quickly while
9028 waiting for the rendezvous circuit to complete. Keep the intro
9029 circuit around longer instead of timing out and reopening new ones
9030 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
9031 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
9032 so it matches dir-spec.txt. Fixes bug 24262; bugfix
9034 - When handling multiple SOCKS request for the same .onion address,
9035 only fetch the service descriptor once.
9036 - Avoid a possible double close of a circuit by the intro point on
9037 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
9038 bugfix on 0.3.0.1-alpha.
9039 - When reloading configured onion services, copy all information
9040 from the old service object. Previously, some data was omitted,
9041 causing delays in descriptor upload, and other bugs. Fixes bug
9042 23790; bugfix on 0.2.1.9-alpha.
9044 o Minor bugfixes (path selection):
9045 - When selecting relays by bandwidth, avoid a rounding error that
9046 could sometimes cause load to be imbalanced incorrectly.
9047 Previously, we would always round upwards; now, we round towards
9048 the nearest integer. This had the biggest effect when a relay's
9049 weight adjustments should have given it weight 0, but it got
9050 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
9051 - When calculating the fraction of nodes that have descriptors, and
9052 all nodes in the network have zero bandwidths, count the number of
9053 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
9054 - Actually log the total bandwidth in compute_weighted_bandwidths().
9055 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
9057 o Minor bugfixes (portability):
9058 - Stop using the PATH_MAX variable, which is not defined on GNU
9059 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
9060 - Fix a bug in the bit-counting parts of our timing-wheel code on
9061 MSVC. (Note that MSVC is still not a supported build platform, due
9062 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
9065 o Minor bugfixes (relay):
9066 - When uploading our descriptor for the first time after startup,
9067 report the reason for uploading as "Tor just started" rather than
9068 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
9069 - Avoid unnecessary calls to directory_fetches_from_authorities() on
9070 relays, to prevent spurious address resolutions and descriptor
9071 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
9072 bugfix on in 0.2.8.1-alpha.
9073 - Avoid a crash when transitioning from client mode to bridge mode.
9074 Previously, we would launch the worker threads whenever our
9075 "public server" mode changed, but not when our "server" mode
9076 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
9078 o Minor bugfixes (testing):
9079 - Fix a spurious fuzzing-only use of an uninitialized value. Found
9080 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
9081 - Test that IPv6-only clients can use microdescriptors when running
9082 "make test-network-all". Requires chutney master 61c28b9 or later.
9083 Closes ticket 24109.
9084 - Prevent scripts/test/coverage from attempting to move gcov output
9085 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
9086 - Capture and detect several "Result does not fit" warnings in unit
9087 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
9089 - Fix additional channelpadding unit test failures by using mocked
9090 time instead of actual time for all tests. Fixes bug 23608; bugfix
9092 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
9093 to correctly handle cases where a caller gives it an RSA key of
9094 under 160 bits. (This is not actually a bug in Tor itself, but
9095 rather in our fuzzing code.) Fixes bug 24247; bugfix on
9096 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
9097 - Fix a broken unit test for the OutboundAddress option: the parsing
9098 function was never returning an error on failure. Fixes bug 23366;
9099 bugfix on 0.3.0.3-alpha.
9100 - Fix a signed-integer overflow in the unit tests for
9101 dir/download_status_random_backoff, which was untriggered until we
9102 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
9104 o Minor bugfixes (usability, control port):
9105 - Stop making an unnecessary routerlist check in NETINFO clock skew
9106 detection; this was preventing clients from reporting NETINFO clock
9107 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
9109 o Code simplification and refactoring:
9110 - Remove various ways of testing circuits and connections for
9111 "clientness"; instead, favor channel_is_client(). Part of
9113 - Extract the code for handling newly-open channels into a separate
9114 function from the general code to handle channel state
9115 transitions. This change simplifies our callgraph, reducing the
9116 size of the largest strongly connected component by roughly a
9117 factor of two. Closes ticket 22608.
9118 - Remove dead code for largely unused statistics on the number of
9119 times we've attempted various public key operations. Fixes bug
9120 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
9121 - Remove several now-obsolete functions for asking about old
9122 variants directory authority status. Closes ticket 22311; patch
9124 - Remove some of the code that once supported "Named" and "Unnamed"
9125 routers. Authorities no longer vote for these flags. Closes
9127 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
9128 and old hidden services, to indicate that they aren't suitable for
9129 new protocols or formats. Closes ticket 23026.
9130 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
9131 22521. Patch from Neel Chauhan.
9132 - Split the enormous circuit_send_next_onion_skin() function into
9133 multiple subfunctions. Closes ticket 22804.
9134 - Split the portions of the buffer.c module that handle particular
9135 protocols into separate modules. Part of ticket 23149.
9136 - Use our test macros more consistently, to produce more useful
9137 error messages when our unit tests fail. Add coccinelle patches to
9138 allow us to re-check for test macro uses. Closes ticket 22497.
9140 o Deprecated features:
9141 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
9142 now deprecated; they do not apply to relays, and they have had no
9143 effect on clients since 0.2.8.x. Closes ticket 19704.
9144 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
9145 only applies to direct unencrypted HTTP connections to your
9146 directory server, which your Tor probably isn't using. Closes
9150 - Add notes in man page regarding OS support for the various
9151 scheduler types. Attempt to use less jargon in the scheduler
9152 section. Closes ticket 24254.
9153 - Clarify that the Address option is entirely about setting an
9154 advertised IPv4 address. Closes ticket 18891.
9155 - Clarify the manpage's use of the term "address" to clarify what
9156 kind of address is intended. Closes ticket 21405.
9157 - Document that onion service subdomains are allowed, and ignored.
9158 Closes ticket 18736.
9159 - Clarify in the manual that "Sandbox 1" is only supported on Linux
9160 kernels. Closes ticket 22677.
9161 - Document all values of PublishServerDescriptor in the manpage.
9162 Closes ticket 15645.
9163 - Improve the documentation for the directory port part of the
9164 DirAuthority line. Closes ticket 20152.
9165 - Restore documentation for the authorities' "approved-routers"
9166 file. Closes ticket 21148.
9169 - The AllowDotExit option has been removed as unsafe. It has been
9170 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
9171 - The ClientDNSRejectInternalAddresses flag can no longer be set on
9172 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
9173 Closes ticket 21031.
9174 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
9175 nobody was using it any longer. Closes ticket 22377.
9178 Changes in version 0.3.1.9 - 2017-12-01:
9179 Tor 0.3.1.9 backports important security and stability fixes from the
9180 0.3.2 development series. All Tor users should upgrade to this
9181 release, or to another of the releases coming out today.
9183 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9184 - Fix a denial of service bug where an attacker could use a
9185 malformed directory object to cause a Tor instance to pause while
9186 OpenSSL would try to read a passphrase from the terminal. (Tor
9187 instances run without a terminal, which is the case for most Tor
9188 packages, are not impacted.) Fixes bug 24246; bugfix on every
9189 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9190 Found by OSS-Fuzz as testcase 6360145429790720.
9191 - Fix a denial of service issue where an attacker could crash a
9192 directory authority using a malformed router descriptor. Fixes bug
9193 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
9195 - When checking for replays in the INTRODUCE1 cell data for a
9196 (legacy) onion service, correctly detect replays in the RSA-
9197 encrypted part of the cell. We were previously checking for
9198 replays on the entire cell, but those can be circumvented due to
9199 the malleability of Tor's legacy hybrid encryption. This fix helps
9200 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9201 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9204 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
9205 - Fix a use-after-free error that could crash v2 Tor onion services
9206 when they failed to open circuits while expiring introduction
9207 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9208 also tracked as TROVE-2017-013 and CVE-2017-8823.
9210 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9211 - When running as a relay, make sure that we never build a path
9212 through ourselves, even in the case where we have somehow lost the
9213 version of our descriptor appearing in the consensus. Fixes part
9214 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9215 as TROVE-2017-012 and CVE-2017-8822.
9216 - When running as a relay, make sure that we never choose ourselves
9217 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
9218 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
9220 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
9221 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
9222 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
9223 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
9224 identifying and finding a workaround to this bug and to Moritz,
9225 Arthur Edelstein, and Roger for helping to track it down and
9228 o Minor features (bridge):
9229 - Bridges now include notice in their descriptors that they are
9230 bridges, and notice of their distribution status, based on their
9231 publication settings. Implements ticket 18329. For more fine-
9232 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9235 o Minor features (directory authority, backport from 0.3.2.6-alpha):
9236 - Add an IPv6 address for the "bastet" directory authority. Closes
9239 o Minor features (geoip):
9240 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9243 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
9244 - Avoid unnecessary calls to directory_fetches_from_authorities() on
9245 relays, to prevent spurious address resolutions and descriptor
9246 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
9247 bugfix on in 0.2.8.1-alpha.
9249 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
9250 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
9251 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
9253 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
9254 - When a circuit is marked for close, do not attempt to package any
9255 cells for channels on that circuit. Previously, we would detect
9256 this condition lower in the call stack, when we noticed that the
9257 circuit had no attached channel, and log an annoying message.
9258 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
9260 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
9261 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
9262 so it matches dir-spec.txt. Fixes bug 24262; bugfix
9265 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
9266 - Avoid a crash when transitioning from client mode to bridge mode.
9267 Previously, we would launch the worker threads whenever our
9268 "public server" mode changed, but not when our "server" mode
9269 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
9272 Changes in version 0.3.0.13 - 2017-12-01
9273 Tor 0.3.0.13 backports important security and stability bugfixes from
9274 later Tor releases. All Tor users should upgrade to this release, or
9275 to another of the releases coming out today.
9277 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
9278 2018. If you need a release with long-term support, please stick with
9279 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9281 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9282 - Fix a denial of service bug where an attacker could use a
9283 malformed directory object to cause a Tor instance to pause while
9284 OpenSSL would try to read a passphrase from the terminal. (Tor
9285 instances run without a terminal, which is the case for most Tor
9286 packages, are not impacted.) Fixes bug 24246; bugfix on every
9287 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9288 Found by OSS-Fuzz as testcase 6360145429790720.
9289 - Fix a denial of service issue where an attacker could crash a
9290 directory authority using a malformed router descriptor. Fixes bug
9291 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
9293 - When checking for replays in the INTRODUCE1 cell data for a
9294 (legacy) onion service, correctly detect replays in the RSA-
9295 encrypted part of the cell. We were previously checking for
9296 replays on the entire cell, but those can be circumvented due to
9297 the malleability of Tor's legacy hybrid encryption. This fix helps
9298 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9299 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9302 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
9303 - Fix a use-after-free error that could crash v2 Tor onion services
9304 when they failed to open circuits while expiring introduction
9305 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9306 also tracked as TROVE-2017-013 and CVE-2017-8823.
9308 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9309 - When running as a relay, make sure that we never build a path
9310 through ourselves, even in the case where we have somehow lost the
9311 version of our descriptor appearing in the consensus. Fixes part
9312 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9313 as TROVE-2017-012 and CVE-2017-8822.
9314 - When running as a relay, make sure that we never choose ourselves
9315 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
9316 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
9318 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
9319 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
9320 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
9321 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
9322 identifying and finding a workaround to this bug and to Moritz,
9323 Arthur Edelstein, and Roger for helping to track it down and
9326 o Minor features (security, windows, backport from 0.3.1.1-alpha):
9327 - Enable a couple of pieces of Windows hardening: one
9328 (HeapEnableTerminationOnCorruption) that has been on-by-default
9329 since Windows 8, and unavailable before Windows 7; and one
9330 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
9331 affect us, but shouldn't do any harm. Closes ticket 21953.
9333 o Minor features (bridge, backport from 0.3.1.9):
9334 - Bridges now include notice in their descriptors that they are
9335 bridges, and notice of their distribution status, based on their
9336 publication settings. Implements ticket 18329. For more fine-
9337 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9340 o Minor features (directory authority, backport from 0.3.2.6-alpha):
9341 - Add an IPv6 address for the "bastet" directory authority. Closes
9344 o Minor features (geoip):
9345 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9348 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
9349 - Avoid unnecessary calls to directory_fetches_from_authorities() on
9350 relays, to prevent spurious address resolutions and descriptor
9351 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
9352 bugfix on in 0.2.8.1-alpha.
9354 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
9355 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
9356 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
9358 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
9359 - When a circuit is marked for close, do not attempt to package any
9360 cells for channels on that circuit. Previously, we would detect
9361 this condition lower in the call stack, when we noticed that the
9362 circuit had no attached channel, and log an annoying message.
9363 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
9365 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
9366 - Avoid a crash when transitioning from client mode to bridge mode.
9367 Previously, we would launch the worker threads whenever our
9368 "public server" mode changed, but not when our "server" mode
9369 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
9371 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
9372 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
9373 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
9376 Changes in version 0.2.9.14 - 2017-12-01
9377 Tor 0.3.0.13 backports important security and stability bugfixes from
9378 later Tor releases. All Tor users should upgrade to this release, or
9379 to another of the releases coming out today.
9381 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
9382 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
9383 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
9384 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
9385 identifying and finding a workaround to this bug and to Moritz,
9386 Arthur Edelstein, and Roger for helping to track it down and
9389 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9390 - Fix a denial of service bug where an attacker could use a
9391 malformed directory object to cause a Tor instance to pause while
9392 OpenSSL would try to read a passphrase from the terminal. (Tor
9393 instances run without a terminal, which is the case for most Tor
9394 packages, are not impacted.) Fixes bug 24246; bugfix on every
9395 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9396 Found by OSS-Fuzz as testcase 6360145429790720.
9397 - Fix a denial of service issue where an attacker could crash a
9398 directory authority using a malformed router descriptor. Fixes bug
9399 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
9401 - When checking for replays in the INTRODUCE1 cell data for a
9402 (legacy) onion service, correctly detect replays in the RSA-
9403 encrypted part of the cell. We were previously checking for
9404 replays on the entire cell, but those can be circumvented due to
9405 the malleability of Tor's legacy hybrid encryption. This fix helps
9406 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9407 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9410 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
9411 - Fix a use-after-free error that could crash v2 Tor onion services
9412 when they failed to open circuits while expiring introduction
9413 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9414 also tracked as TROVE-2017-013 and CVE-2017-8823.
9416 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9417 - When running as a relay, make sure that we never build a path
9418 through ourselves, even in the case where we have somehow lost the
9419 version of our descriptor appearing in the consensus. Fixes part
9420 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9421 as TROVE-2017-012 and CVE-2017-8822.
9423 o Minor features (bridge, backport from 0.3.1.9):
9424 - Bridges now include notice in their descriptors that they are
9425 bridges, and notice of their distribution status, based on their
9426 publication settings. Implements ticket 18329. For more fine-
9427 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9430 o Minor features (directory authority, backport from 0.3.2.6-alpha):
9431 - Add an IPv6 address for the "bastet" directory authority. Closes
9434 o Minor features (geoip):
9435 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9438 o Minor features (security, windows, backport from 0.3.1.1-alpha):
9439 - Enable a couple of pieces of Windows hardening: one
9440 (HeapEnableTerminationOnCorruption) that has been on-by-default
9441 since Windows 8, and unavailable before Windows 7; and one
9442 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
9443 affect us, but shouldn't do any harm. Closes ticket 21953.
9445 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
9446 - Avoid unnecessary calls to directory_fetches_from_authorities() on
9447 relays, to prevent spurious address resolutions and descriptor
9448 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
9449 bugfix on in 0.2.8.1-alpha.
9451 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
9452 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
9453 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
9455 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
9456 - When a circuit is marked for close, do not attempt to package any
9457 cells for channels on that circuit. Previously, we would detect
9458 this condition lower in the call stack, when we noticed that the
9459 circuit had no attached channel, and log an annoying message.
9460 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
9462 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
9463 - Avoid a crash when transitioning from client mode to bridge mode.
9464 Previously, we would launch the worker threads whenever our
9465 "public server" mode changed, but not when our "server" mode
9466 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
9468 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
9469 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
9470 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
9473 Changes in version 0.2.8.17 - 2017-12-01
9474 Tor 0.2.8.17 backports important security and stability bugfixes from
9475 later Tor releases. All Tor users should upgrade to this release, or
9476 to another of the releases coming out today.
9478 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
9479 2018. If you need a release with long-term support, please upgrade with
9480 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9482 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9483 - Fix a denial of service bug where an attacker could use a
9484 malformed directory object to cause a Tor instance to pause while
9485 OpenSSL would try to read a passphrase from the terminal. (Tor
9486 instances run without a terminal, which is the case for most Tor
9487 packages, are not impacted.) Fixes bug 24246; bugfix on every
9488 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9489 Found by OSS-Fuzz as testcase 6360145429790720.
9490 - When checking for replays in the INTRODUCE1 cell data for a
9491 (legacy) onion service, correctly detect replays in the RSA-
9492 encrypted part of the cell. We were previously checking for
9493 replays on the entire cell, but those can be circumvented due to
9494 the malleability of Tor's legacy hybrid encryption. This fix helps
9495 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9496 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9499 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
9500 - Fix a use-after-free error that could crash v2 Tor onion services
9501 when they failed to open circuits while expiring introduction
9502 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9503 also tracked as TROVE-2017-013 and CVE-2017-8823.
9505 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9506 - When running as a relay, make sure that we never build a path through
9507 ourselves, even in the case where we have somehow lost the version of
9508 our descriptor appearing in the consensus. Fixes part of bug 21534;
9509 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
9512 o Minor features (bridge, backport from 0.3.1.9):
9513 - Bridges now include notice in their descriptors that they are
9514 bridges, and notice of their distribution status, based on their
9515 publication settings. Implements ticket 18329. For more fine-
9516 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9519 o Minor features (directory authority, backport from 0.3.2.6-alpha):
9520 - Add an IPv6 address for the "bastet" directory authority. Closes
9523 o Minor features (geoip):
9524 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9527 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
9528 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
9529 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
9532 Changes in version 0.2.5.16 - 2017-12-01
9533 Tor 0.2.5.13 backports important security and stability bugfixes from
9534 later Tor releases. All Tor users should upgrade to this release, or
9535 to another of the releases coming out today.
9537 Note: the Tor 0.2.5 series will no longer be supported after 1 May
9538 2018. If you need a release with long-term support, please upgrade to
9539 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9541 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9542 - Fix a denial of service bug where an attacker could use a
9543 malformed directory object to cause a Tor instance to pause while
9544 OpenSSL would try to read a passphrase from the terminal. (Tor
9545 instances run without a terminal, which is the case for most Tor
9546 packages, are not impacted.) Fixes bug 24246; bugfix on every
9547 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9548 Found by OSS-Fuzz as testcase 6360145429790720.
9549 - When checking for replays in the INTRODUCE1 cell data for a
9550 (legacy) onion service, correctly detect replays in the RSA-
9551 encrypted part of the cell. We were previously checking for
9552 replays on the entire cell, but those can be circumvented due to
9553 the malleability of Tor's legacy hybrid encryption. This fix helps
9554 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9555 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9558 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9559 - When running as a relay, make sure that we never build a path
9560 through ourselves, even in the case where we have somehow lost the
9561 version of our descriptor appearing in the consensus. Fixes part
9562 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9563 as TROVE-2017-012 and CVE-2017-8822.
9565 o Minor features (bridge, backport from 0.3.1.9):
9566 - Bridges now include notice in their descriptors that they are
9567 bridges, and notice of their distribution status, based on their
9568 publication settings. Implements ticket 18329. For more fine-
9569 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9572 o Minor features (geoip):
9573 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9577 Changes in version 0.2.5.15 - 2017-10-25
9578 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
9579 series. It also adds a new directory authority, Bastet.
9581 Note: the Tor 0.2.5 series will no longer be supported after 1 May
9582 2018. If you need a release with long-term support, please upgrade to
9583 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9585 o Directory authority changes:
9586 - Add "Bastet" as a ninth directory authority to the default list.
9587 Closes ticket 23910.
9588 - The directory authority "Longclaw" has changed its IP address.
9589 Closes ticket 23592.
9591 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
9592 - Avoid an assertion failure bug affecting our implementation of
9593 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
9594 handling of "0xx" differs from what we had expected. Fixes bug
9595 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
9597 o Minor features (geoip):
9598 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9601 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
9602 - Fix a memset() off the end of an array when packing cells. This
9603 bug should be harmless in practice, since the corrupted bytes are
9604 still in the same structure, and are always padding bytes,
9605 ignored, or immediately overwritten, depending on compiler
9606 behavior. Nevertheless, because the memset()'s purpose is to make
9607 sure that any other cell-handling bugs can't expose bytes to the
9608 network, we need to fix it. Fixes bug 22737; bugfix on
9609 0.2.4.11-alpha. Fixes CID 1401591.
9611 o Build features (backport from 0.3.1.5-alpha):
9612 - Tor's repository now includes a Travis Continuous Integration (CI)
9613 configuration file (.travis.yml). This is meant to help new
9614 developers and contributors who fork Tor to a Github repository be
9615 better able to test their changes, and understand what we expect
9616 to pass. To use this new build feature, you must fork Tor to your
9617 Github account, then go into the "Integrations" menu in the
9618 repository settings for your fork and enable Travis, then push
9619 your changes. Closes ticket 22636.
9622 Changes in version 0.2.8.16 - 2017-10-25
9623 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
9624 series, including a bugfix for a crash issue that had affected relays
9625 under memory pressure. It also adds a new directory authority, Bastet.
9627 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
9628 2018. If you need a release with long-term support, please stick with
9629 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9631 o Directory authority changes:
9632 - Add "Bastet" as a ninth directory authority to the default list.
9633 Closes ticket 23910.
9634 - The directory authority "Longclaw" has changed its IP address.
9635 Closes ticket 23592.
9637 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
9638 - Fix a timing-based assertion failure that could occur when the
9639 circuit out-of-memory handler freed a connection's output buffer.
9640 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
9642 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
9643 - Remove longclaw's IPv6 address, as it will soon change. Authority
9644 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
9645 3/8 directory authorities with IPv6 addresses, but there are also
9646 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
9648 o Minor features (geoip):
9649 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9653 Changes in version 0.2.9.13 - 2017-10-25
9654 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
9655 series, including a bugfix for a crash issue that had affected relays
9656 under memory pressure. It also adds a new directory authority, Bastet.
9658 o Directory authority changes:
9659 - Add "Bastet" as a ninth directory authority to the default list.
9660 Closes ticket 23910.
9661 - The directory authority "Longclaw" has changed its IP address.
9662 Closes ticket 23592.
9664 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
9665 - Fix a timing-based assertion failure that could occur when the
9666 circuit out-of-memory handler freed a connection's output buffer.
9667 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
9669 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
9670 - Remove longclaw's IPv6 address, as it will soon change. Authority
9671 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
9672 3/8 directory authorities with IPv6 addresses, but there are also
9673 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
9675 o Minor features (geoip):
9676 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9679 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
9680 - When a directory authority rejects a descriptor or extrainfo with
9681 a given digest, mark that digest as undownloadable, so that we do
9682 not attempt to download it again over and over. We previously
9683 tried to avoid downloading such descriptors by other means, but we
9684 didn't notice if we accidentally downloaded one anyway. This
9685 behavior became problematic in 0.2.7.2-alpha, when authorities
9686 began pinning Ed25519 keys. Fixes bug 22349; bugfix
9689 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
9690 - Clear the address when node_get_prim_orport() returns early.
9691 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
9693 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
9694 - When running as a Windows service, set the ID of the main thread
9695 correctly. Failure to do so made us fail to send log messages to
9696 the controller in 0.2.1.16-rc, slowed down controller event
9697 delivery in 0.2.7.3-rc and later, and crash with an assertion
9698 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
9699 Patch and diagnosis from "Vort".
9702 Changes in version 0.3.0.12 - 2017-10-25
9703 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
9704 series, including a bugfix for a crash issue that had affected relays
9705 under memory pressure. It also adds a new directory authority, Bastet.
9707 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
9708 2018. If you need a release with long-term support, please stick with
9709 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9711 o Directory authority changes:
9712 - Add "Bastet" as a ninth directory authority to the default list.
9713 Closes ticket 23910.
9714 - The directory authority "Longclaw" has changed its IP address.
9715 Closes ticket 23592.
9717 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
9718 - Fix a timing-based assertion failure that could occur when the
9719 circuit out-of-memory handler freed a connection's output buffer.
9720 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
9722 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
9723 - Remove longclaw's IPv6 address, as it will soon change. Authority
9724 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
9725 3/8 directory authorities with IPv6 addresses, but there are also
9726 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
9728 o Minor features (geoip):
9729 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9732 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
9733 - When a directory authority rejects a descriptor or extrainfo with
9734 a given digest, mark that digest as undownloadable, so that we do
9735 not attempt to download it again over and over. We previously
9736 tried to avoid downloading such descriptors by other means, but we
9737 didn't notice if we accidentally downloaded one anyway. This
9738 behavior became problematic in 0.2.7.2-alpha, when authorities
9739 began pinning Ed25519 keys. Fixes bug 22349; bugfix
9742 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
9743 - Avoid a possible double close of a circuit by the intro point on
9744 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
9745 bugfix on 0.3.0.1-alpha.
9747 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
9748 - Clear the address when node_get_prim_orport() returns early.
9749 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
9751 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
9752 - When running as a Windows service, set the ID of the main thread
9753 correctly. Failure to do so made us fail to send log messages to
9754 the controller in 0.2.1.16-rc, slowed down controller event
9755 delivery in 0.2.7.3-rc and later, and crash with an assertion
9756 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
9757 Patch and diagnosis from "Vort".
9760 Changes in version 0.3.1.8 - 2017-10-25
9761 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
9762 It includes several bugfixes, including a bugfix for a crash issue
9763 that had affected relays under memory pressure. It also adds
9764 a new directory authority, Bastet.
9766 o Directory authority changes:
9767 - Add "Bastet" as a ninth directory authority to the default list.
9768 Closes ticket 23910.
9769 - The directory authority "Longclaw" has changed its IP address.
9770 Closes ticket 23592.
9772 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
9773 - Fix a timing-based assertion failure that could occur when the
9774 circuit out-of-memory handler freed a connection's output buffer.
9775 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
9777 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
9778 - Remove longclaw's IPv6 address, as it will soon change. Authority
9779 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
9780 3/8 directory authorities with IPv6 addresses, but there are also
9781 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
9783 o Minor features (geoip):
9784 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9787 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
9788 - Fix a compilation warning when building with zstd support on
9789 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
9790 and fixed by Andreas Stieger.
9792 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
9793 - Handle a pathological case when decompressing Zstandard data when
9794 the output buffer size is zero. Fixes bug 23551; bugfix
9797 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
9798 - Remove the length limit on HTTP status lines that authorities can
9799 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
9801 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
9802 - Avoid a possible double close of a circuit by the intro point on
9803 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
9804 bugfix on 0.3.0.1-alpha.
9806 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
9807 - Clear the address when node_get_prim_orport() returns early.
9808 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
9810 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
9811 - Fix additional channelpadding unit test failures by using mocked
9812 time instead of actual time for all tests. Fixes bug 23608; bugfix
9816 Changes in version 0.2.8.15 - 2017-09-18
9817 Tor 0.2.8.15 backports a collection of bugfixes from later
9820 Most significantly, it includes a fix for TROVE-2017-008, a
9821 security bug that affects hidden services running with the
9822 SafeLogging option disabled. For more information, see
9823 https://trac.torproject.org/projects/tor/ticket/23490
9825 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
9826 2018. We suggest that you upgrade to the latest stable release if
9827 possible. If you can't, we recommend that you upgrade at least to
9828 0.2.9, which will be supported until 2020.
9830 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
9831 - Avoid an assertion failure bug affecting our implementation of
9832 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
9833 handling of "0xx" differs from what we had expected. Fixes bug
9834 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
9837 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
9840 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
9841 - Backport a fix for an "unused variable" warning that appeared
9842 in some versions of mingw. Fixes bug 22838; bugfix on
9845 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
9846 - Fix a memset() off the end of an array when packing cells. This
9847 bug should be harmless in practice, since the corrupted bytes are
9848 still in the same structure, and are always padding bytes,
9849 ignored, or immediately overwritten, depending on compiler
9850 behavior. Nevertheless, because the memset()'s purpose is to make
9851 sure that any other cell-handling bugs can't expose bytes to the
9852 network, we need to fix it. Fixes bug 22737; bugfix on
9853 0.2.4.11-alpha. Fixes CID 1401591.
9855 o Build features (backport from 0.3.1.5-alpha):
9856 - Tor's repository now includes a Travis Continuous Integration (CI)
9857 configuration file (.travis.yml). This is meant to help new
9858 developers and contributors who fork Tor to a Github repository be
9859 better able to test their changes, and understand what we expect
9860 to pass. To use this new build feature, you must fork Tor to your
9861 Github account, then go into the "Integrations" menu in the
9862 repository settings for your fork and enable Travis, then push
9863 your changes. Closes ticket 22636.
9866 Changes in version 0.2.9.12 - 2017-09-18
9867 Tor 0.2.9.12 backports a collection of bugfixes from later
9870 Most significantly, it includes a fix for TROVE-2017-008, a
9871 security bug that affects hidden services running with the
9872 SafeLogging option disabled. For more information, see
9873 https://trac.torproject.org/projects/tor/ticket/23490
9875 o Major features (security, backport from 0.3.0.2-alpha):
9876 - Change the algorithm used to decide DNS TTLs on client and server
9877 side, to better resist DNS-based correlation attacks like the
9878 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
9879 Feamster. Now relays only return one of two possible DNS TTL
9880 values, and clients are willing to believe DNS TTL values up to 3
9881 hours long. Closes ticket 19769.
9883 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
9884 - Fix a rare crash when sending a begin cell on a circuit whose
9885 linked directory connection had already been closed. Fixes bug
9886 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
9888 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
9889 - Fix a bug that prevented exit nodes from caching DNS records for
9890 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
9892 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
9893 - Fix a typo that had prevented TPROXY-based transparent proxying
9894 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
9895 Patch from "d4fq0fQAgoJ".
9897 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
9898 - Avoid an assertion failure bug affecting our implementation of
9899 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
9900 handling of "0xx" differs from what we had expected. Fixes bug
9901 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
9903 o Minor features (code style, backport from 0.3.1.3-alpha):
9904 - Add "Falls through" comments to our codebase, in order to silence
9905 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
9906 Stieger. Closes ticket 22446.
9908 o Minor features (geoip):
9909 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
9912 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
9913 - Roll over monthly accounting at the configured hour and minute,
9914 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
9915 Found by Andrey Karpov with PVS-Studio.
9917 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
9918 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
9919 bugfix on 0.2.8.1-alpha.
9920 - Fix warnings when building with libscrypt and openssl scrypt support
9921 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
9922 - When building with certain versions the mingw C header files, avoid
9923 float-conversion warnings when calling the C functions isfinite(),
9924 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
9926 o Minor bugfixes (compilation, backport from 0.3.1.7):
9927 - Avoid compiler warnings in the unit tests for running tor_sscanf()
9928 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
9930 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
9931 - Backport a fix for an "unused variable" warning that appeared
9932 in some versions of mingw. Fixes bug 22838; bugfix on
9935 o Minor bugfixes (controller, backport from 0.3.1.7):
9936 - Do not crash when receiving a HSPOST command with an empty body.
9937 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
9938 - Do not crash when receiving a POSTDESCRIPTOR command with an
9939 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
9941 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
9942 - Avoid Coverity build warnings related to our BUG() macro. By
9943 default, Coverity treats BUG() as the Linux kernel does: an
9944 instant abort(). We need to override that so our BUG() macro
9945 doesn't prevent Coverity from analyzing functions that use it.
9946 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
9948 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
9949 - Fix a memset() off the end of an array when packing cells. This
9950 bug should be harmless in practice, since the corrupted bytes are
9951 still in the same structure, and are always padding bytes,
9952 ignored, or immediately overwritten, depending on compiler
9953 behavior. Nevertheless, because the memset()'s purpose is to make
9954 sure that any other cell-handling bugs can't expose bytes to the
9955 network, we need to fix it. Fixes bug 22737; bugfix on
9956 0.2.4.11-alpha. Fixes CID 1401591.
9958 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
9959 - When setting the maximum number of connections allowed by the OS,
9960 always allow some extra file descriptors for other files. Fixes
9961 bug 22797; bugfix on 0.2.0.10-alpha.
9963 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
9964 - Avoid a sandbox failure when trying to re-bind to a socket and
9965 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
9967 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
9968 - Permit the fchmod system call, to avoid crashing on startup when
9969 starting with the seccomp2 sandbox and an unexpected set of
9970 permissions on the data directory or its contents. Fixes bug
9971 22516; bugfix on 0.2.5.4-alpha.
9973 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
9974 - Avoid a double-marked-circuit warning that could happen when we
9975 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
9978 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
9979 - Reject version numbers with non-numeric prefixes (such as +, -, or
9980 whitespace). Disallowing whitespace prevents differential version
9981 parsing between POSIX-based and Windows platforms. Fixes bug 21507
9982 and part of 21508; bugfix on 0.0.8pre1.
9984 o Build features (backport from 0.3.1.5-alpha):
9985 - Tor's repository now includes a Travis Continuous Integration (CI)
9986 configuration file (.travis.yml). This is meant to help new
9987 developers and contributors who fork Tor to a Github repository be
9988 better able to test their changes, and understand what we expect
9989 to pass. To use this new build feature, you must fork Tor to your
9990 Github account, then go into the "Integrations" menu in the
9991 repository settings for your fork and enable Travis, then push
9992 your changes. Closes ticket 22636.
9995 Changes in version 0.3.0.11 - 2017-09-18
9996 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
9999 Most significantly, it includes a fix for TROVE-2017-008, a
10000 security bug that affects hidden services running with the
10001 SafeLogging option disabled. For more information, see
10002 https://trac.torproject.org/projects/tor/ticket/23490
10004 o Minor features (code style, backport from 0.3.1.7):
10005 - Add "Falls through" comments to our codebase, in order to silence
10006 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
10007 Stieger. Closes ticket 22446.
10010 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
10013 o Minor bugfixes (compilation, backport from 0.3.1.7):
10014 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
10015 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
10017 o Minor bugfixes (controller, backport from 0.3.1.7):
10018 - Do not crash when receiving a HSPOST command with an empty body.
10019 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
10020 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
10021 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
10023 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
10024 - When setting the maximum number of connections allowed by the OS,
10025 always allow some extra file descriptors for other files. Fixes
10026 bug 22797; bugfix on 0.2.0.10-alpha.
10028 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
10029 - Remove a forgotten debugging message when an introduction point
10030 successfully establishes a hidden service prop224 circuit with
10032 - Change three other log_warn() for an introduction point to
10033 protocol warnings, because they can be failure from the network
10034 and are not relevant to the operator. Fixes bug 23078; bugfix on
10035 0.3.0.1-alpha and 0.3.0.2-alpha.
10038 Changes in version 0.3.1.7 - 2017-09-18
10039 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
10041 With the 0.3.1 series, Tor now serves and downloads directory
10042 information in more compact formats, to save on bandwidth overhead. It
10043 also contains a new padding system to resist netflow-based traffic
10044 analysis, and experimental support for building parts of Tor in Rust
10045 (though no parts of Tor are in Rust yet). There are also numerous
10046 small features, bugfixes on earlier release series, and groundwork for
10047 the hidden services revamp of 0.3.2.
10049 This release also includes a fix for TROVE-2017-008, a security bug
10050 that affects hidden services running with the SafeLogging option
10051 disabled. For more information, see
10052 https://trac.torproject.org/projects/tor/ticket/23490
10054 Per our stable release policy, we plan to support each stable release
10055 series for at least the next nine months, or for three months after
10056 the first stable release of the next series: whichever is longer. If
10057 you need a release with long-term support, we recommend that you stay
10058 with the 0.2.9 series.
10060 Below is a list of the changes since 0.3.0. For a list of all
10061 changes since 0.3.1.6-rc, see the ChangeLog file.
10063 o New dependencies:
10064 - To build with zstd and lzma support, Tor now requires the
10065 pkg-config tool at build time.
10067 o Major bugfixes (security, hidden services, loggging):
10068 - Fix a bug where we could log uninitialized stack when a certain
10069 hidden service error occurred while SafeLogging was disabled.
10070 Fixes bug #23490; bugfix on 0.2.7.2-alpha.
10071 This is also tracked as TROVE-2017-008 and CVE-2017-0380.
10073 o Major features (build system, continuous integration):
10074 - Tor's repository now includes a Travis Continuous Integration (CI)
10075 configuration file (.travis.yml). This is meant to help new
10076 developers and contributors who fork Tor to a Github repository be
10077 better able to test their changes, and understand what we expect
10078 to pass. To use this new build feature, you must fork Tor to your
10079 Github account, then go into the "Integrations" menu in the
10080 repository settings for your fork and enable Travis, then push
10081 your changes. Closes ticket 22636.
10083 o Major features (directory protocol):
10084 - Tor relays and authorities can now serve clients an abbreviated
10085 version of the consensus document, containing only the changes
10086 since an older consensus document that the client holds. Clients
10087 now request these documents when available. When both client and
10088 server use this new protocol, they will use far less bandwidth (up
10089 to 94% less) to keep the client's consensus up-to-date. Implements
10090 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
10091 - Tor can now compress directory traffic with lzma or with zstd
10092 compression algorithms, which can deliver better bandwidth
10093 performance. Because lzma is computationally expensive, it's only
10094 used for documents that can be compressed once and served many
10095 times. Support for these algorithms requires that tor is built
10096 with the libzstd and/or liblzma libraries available. Implements
10097 proposal 278; closes ticket 21662.
10098 - Relays now perform the more expensive compression operations, and
10099 consensus diff generation, in worker threads. This separation
10100 avoids delaying the main thread when a new consensus arrives.
10102 o Major features (experimental):
10103 - Tor can now build modules written in Rust. To turn this on, pass
10104 the "--enable-rust" flag to the configure script. It's not time to
10105 get excited yet: currently, there is no actual Rust functionality
10106 beyond some simple glue code, and a notice at startup to tell you
10107 that Rust is running. Still, we hope that programmers and
10108 packagers will try building Tor with Rust support, so that we can
10109 find issues and solve portability problems. Closes ticket 22106.
10111 o Major features (traffic analysis resistance):
10112 - Connections between clients and relays now send a padding cell in
10113 each direction every 1.5 to 9.5 seconds (tunable via consensus
10114 parameters). This padding will not resist specialized
10115 eavesdroppers, but it should be enough to make many ISPs' routine
10116 network flow logging less useful in traffic analysis against
10119 Padding is negotiated using Tor's link protocol, so both relays
10120 and clients must upgrade for this to take effect. Clients may
10121 still send padding despite the relay's version by setting
10122 ConnectionPadding 1 in torrc, and may disable padding by setting
10123 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
10124 users with the torrc option ReducedConnectionPadding. Implements
10125 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
10126 - Relays will publish 24 hour totals of padding and non-padding cell
10127 counts to their extra-info descriptors, unless PaddingStatistics 0
10128 is set in torrc. These 24 hour totals are also rounded to
10129 multiples of 10000.
10131 o Major bugfixes (hidden service, relay, security):
10132 - Fix a remotely triggerable assertion failure when a hidden service
10133 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
10134 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
10135 - Fix a remotely triggerable assertion failure caused by receiving a
10136 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
10137 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
10140 o Major bugfixes (path selection, security):
10141 - When choosing which guard to use for a circuit, avoid the exit's
10142 family along with the exit itself. Previously, the new guard
10143 selection logic avoided the exit, but did not consider its family.
10144 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
10145 006 and CVE-2017-0377.
10147 o Major bugfixes (connection usage):
10148 - We use NETINFO cells to try to determine if both relays involved
10149 in a connection will agree on the canonical status of that
10150 connection. We prefer the connections where this is the case for
10151 extend cells, and try to close connections where relays disagree
10152 on their canonical status early. Also, we now prefer the oldest
10153 valid connection for extend cells. These two changes should reduce
10154 the number of long-term connections that are kept open between
10155 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
10156 - Relays now log hourly statistics (look for
10157 "channel_check_for_duplicates" lines) on the total number of
10158 connections to other relays. If the number of connections per
10159 relay is unexpectedly large, this log message is at notice level.
10160 Otherwise it is at info.
10162 o Major bugfixes (entry guards):
10163 - When starting with an old consensus, do not add new entry guards
10164 unless the consensus is "reasonably live" (under 1 day old). Fixes
10165 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
10166 - Don't block bootstrapping when a primary bridge is offline and we
10167 can't get its descriptor. Fixes bug 22325; fixes one case of bug
10168 21969; bugfix on 0.3.0.3-alpha.
10170 o Major bugfixes (linux TPROXY support):
10171 - Fix a typo that had prevented TPROXY-based transparent proxying
10172 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
10173 Patch from "d4fq0fQAgoJ".
10175 o Major bugfixes (openbsd, denial-of-service):
10176 - Avoid an assertion failure bug affecting our implementation of
10177 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
10178 handling of "0xx" differs from what we had expected. Fixes bug
10179 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
10181 o Major bugfixes (relay, link handshake):
10182 - When performing the v3 link handshake on a TLS connection, report
10183 that we have the x509 certificate that we actually used on that
10184 connection, even if we have changed certificates since that
10185 connection was first opened. Previously, we would claim to have
10186 used our most recent x509 link certificate, which would sometimes
10187 make the link handshake fail. Fixes one case of bug 22460; bugfix
10190 o Major bugfixes (relays, key management):
10191 - Regenerate link and authentication certificates whenever the key
10192 that signs them changes; also, regenerate link certificates
10193 whenever the signed key changes. Previously, these processes were
10194 only weakly coupled, and we relays could (for minutes to hours)
10195 wind up with an inconsistent set of keys and certificates, which
10196 other relays would not accept. Fixes two cases of bug 22460;
10197 bugfix on 0.3.0.1-alpha.
10198 - When sending an Ed25519 signing->link certificate in a CERTS cell,
10199 send the certificate that matches the x509 certificate that we
10200 used on the TLS connection. Previously, there was a race condition
10201 if the TLS context rotated after we began the TLS handshake but
10202 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
10205 o Minor features (security, windows):
10206 - Enable a couple of pieces of Windows hardening: one
10207 (HeapEnableTerminationOnCorruption) that has been on-by-default
10208 since Windows 8, and unavailable before Windows 7; and one
10209 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
10210 affect us, but shouldn't do any harm. Closes ticket 21953.
10212 o Minor features (bridge authority):
10213 - Add "fingerprint" lines to the networkstatus-bridges file produced
10214 by bridge authorities. Closes ticket 22207.
10216 o Minor features (code style):
10217 - Add "Falls through" comments to our codebase, in order to silence
10218 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
10219 Stieger. Closes ticket 22446.
10221 o Minor features (config options):
10222 - Allow "%include" directives in torrc configuration files. These
10223 directives import the settings from other files, or from all the
10224 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
10225 - Make SAVECONF return an error when overwriting a torrc that has
10226 includes. Using SAVECONF with the FORCE option will allow it to
10227 overwrite torrc even if includes are used. Related to ticket 1922.
10228 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
10229 will work without the FORCE option. Related to ticket 1922.
10231 o Minor features (controller):
10232 - Warn the first time that a controller requests data in the long-
10233 deprecated 'GETINFO network-status' format. Closes ticket 21703.
10235 o Minor features (defaults):
10236 - The default value for UseCreateFast is now 0: clients which
10237 haven't yet received a consensus document will now use a proper
10238 ntor handshake to talk to their directory servers whenever they
10239 can. Closes ticket 21407.
10240 - Onion key rotation and expiry intervals are now defined as a
10241 network consensus parameter, per proposal 274. The default
10242 lifetime of an onion key is increased from 7 to 28 days. Old onion
10243 keys will expire after 7 days by default. This change will make
10244 consensus diffs much smaller, and save significant bandwidth.
10245 Closes ticket 21641.
10247 o Minor features (defensive programming):
10248 - Create a pair of consensus parameters, nf_pad_tor2web and
10249 nf_pad_single_onion, to disable netflow padding in the consensus
10250 for non-anonymous connections in case the overhead is high. Closes
10253 o Minor features (diagnostic):
10254 - Add a stack trace to the bug warnings that can be logged when
10255 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
10256 attempt for bug 23105.
10257 - Add logging messages to try to diagnose a rare bug that seems to
10258 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
10259 think this is happening because of incorrect system clocks, but
10260 we'd like to know for certain. Diagnostic for bug 22466.
10261 - Avoid an assertion failure, and log a better error message, when
10262 unable to remove a file from the consensus cache on Windows.
10263 Attempts to mitigate and diagnose bug 22752.
10265 o Minor features (directory authority):
10266 - Improve the message that authorities report to relays that present
10267 RSA/Ed25519 keypairs that conflict with previously pinned keys.
10268 Closes ticket 22348.
10270 o Minor features (directory cache, consensus diff):
10271 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
10272 operators with low-resource environments to adjust the number of
10273 consensuses they'll store and generate diffs from. Most cache
10274 operators should leave it unchanged. Helps to work around
10277 o Minor features (fallback directory list):
10278 - Update the fallback directory mirror whitelist and blacklist based
10279 on operator emails. Closes task 21121.
10280 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
10281 December 2016 (of which ~126 were still functional) with a list of
10282 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
10283 2017. Resolves ticket 21564.
10285 o Minor features (geoip):
10286 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
10289 o Minor features (hidden services, logging):
10290 - Log a message when a hidden service descriptor has fewer
10291 introduction points than specified in
10292 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
10293 - Log a message when a hidden service reaches its introduction point
10294 circuit limit, and when that limit is reset. Follow up to ticket
10295 21594; closes ticket 21622.
10296 - Warn user if multiple entries in EntryNodes and at least one
10297 HiddenService are used together. Pinning EntryNodes along with a
10298 hidden service can be possibly harmful; for instance see ticket
10299 14917 or 21155. Closes ticket 21155.
10301 o Minor features (linux seccomp2 sandbox):
10302 - We now have a document storage backend compatible with the Linux
10303 seccomp2 sandbox. This backend is used for consensus documents and
10304 diffs between them; in the long term, we'd like to use it for
10305 unparseable directory material too. Closes ticket 21645
10306 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
10307 from 1MB to 16MB. This was necessary with the glibc allocator in
10308 order to allow worker threads to allocate more memory -- which in
10309 turn is necessary because of our new use of worker threads for
10310 compression. Closes ticket 22096.
10312 o Minor features (logging):
10313 - Log files are no longer created world-readable by default.
10314 (Previously, most distributors would store the logs in a non-
10315 world-readable location to prevent inappropriate access. This
10316 change is an extra precaution.) Closes ticket 21729; patch
10319 o Minor features (performance):
10320 - Our Keccak (SHA-3) implementation now accesses memory more
10321 efficiently, especially on little-endian systems. Closes
10323 - Add an O(1) implementation of channel_find_by_global_id(), to
10324 speed some controller functions.
10326 o Minor features (relay, configuration):
10327 - The MyFamily option may now be repeated as many times as desired,
10328 for relays that want to configure large families. Closes ticket
10329 4998; patch by Daniel Pinto.
10331 o Minor features (relay, performance):
10332 - Always start relays with at least two worker threads, to prevent
10333 priority inversion on slow tasks. Part of the fix for bug 22883.
10334 - Allow background work to be queued with different priorities, so
10335 that a big pile of slow low-priority jobs will not starve out
10336 higher priority jobs. This lays the groundwork for a fix for
10339 o Minor features (safety):
10340 - Add an explicit check to extrainfo_parse_entry_from_string() for
10341 NULL inputs. We don't believe this can actually happen, but it may
10342 help silence a warning from the Clang analyzer. Closes
10345 o Minor features (testing):
10346 - Add more tests for compression backend initialization. Closes
10348 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
10349 When Tor is compiled with this option, we disable a number of
10350 redundant memory-safety failsafes that are intended to stop bugs
10351 from becoming security issues. This makes it easier to hunt for
10352 bugs that would be security issues without the failsafes turned
10353 on. Closes ticket 21439.
10354 - Add a general event-tracing instrumentation support to Tor. This
10355 subsystem will enable developers and researchers to add fine-
10356 grained instrumentation to their Tor instances, for use when
10357 examining Tor network performance issues. There are no trace
10358 events yet, and event-tracing is off by default unless enabled at
10359 compile time. Implements ticket 13802.
10360 - Improve our version parsing tests: add tests for typical version
10361 components, add tests for invalid versions, including numeric
10362 range and non-numeric prefixes. Unit tests 21278, 21450, and
10363 21507. Partially implements 21470.
10365 o Minor bugfixes (bandwidth accounting):
10366 - Roll over monthly accounting at the configured hour and minute,
10367 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
10368 Found by Andrey Karpov with PVS-Studio.
10370 o Minor bugfixes (code correctness):
10371 - Accurately identify client connections by their lack of peer
10372 authentication. This means that we bail out earlier if asked to
10373 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
10376 o Minor bugfixes (compilation warnings):
10377 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
10378 22915; bugfix on 0.2.8.1-alpha.
10379 - Fix warnings when building with libscrypt and openssl scrypt
10380 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
10381 - When building with certain versions of the mingw C header files,
10382 avoid float-conversion warnings when calling the C functions
10383 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
10386 o Minor bugfixes (compilation):
10387 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
10388 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
10390 o Minor bugfixes (compression):
10391 - When spooling compressed data to an output buffer, don't try to
10392 spool more data when there is no more data to spool and we are not
10393 trying to flush the input. Previously, we would sometimes launch
10394 compression requests with nothing to do, which interferes with our
10395 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
10397 o Minor bugfixes (configuration):
10398 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
10399 bug 22252; bugfix on 0.2.9.3-alpha.
10401 o Minor bugfixes (connection lifespan):
10402 - Allow more control over how long TLS connections are kept open:
10403 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
10404 single option called CircuitsAvailableTimeout. Also, allow the
10405 consensus to control the default values for both this preference
10406 and the lifespan of relay-to-relay connections. Fixes bug 17592;
10407 bugfix on 0.2.5.5-alpha.
10408 - Increase the initial circuit build timeout testing frequency, to
10409 help ensure that ReducedConnectionPadding clients finish learning
10410 a timeout before their orconn would expire. The initial testing
10411 rate was set back in the days of TAP and before the Tor Browser
10412 updater, when we had to be much more careful about new clients
10413 making lots of circuits. With this change, a circuit build timeout
10414 is learned in about 15-20 minutes, instead of 100-120 minutes.
10416 o Minor bugfixes (controller):
10417 - Do not crash when receiving a HSPOST command with an empty body.
10418 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
10419 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
10420 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
10421 - GETINFO onions/current and onions/detached no longer respond with
10422 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
10423 - Trigger HS descriptor events on the control port when the client
10424 fails to pick a hidden service directory for a hidden service.
10425 This can happen if all the hidden service directories are in
10426 ExcludeNodes, or they have all been queried within the last 15
10427 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
10429 o Minor bugfixes (correctness):
10430 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
10431 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
10433 o Minor bugfixes (coverity build support):
10434 - Avoid Coverity build warnings related to our BUG() macro. By
10435 default, Coverity treats BUG() as the Linux kernel does: an
10436 instant abort(). We need to override that so our BUG() macro
10437 doesn't prevent Coverity from analyzing functions that use it.
10438 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
10440 o Minor bugfixes (defensive programming):
10441 - Detect and break out of infinite loops in our compression code. We
10442 don't think that any such loops exist now, but it's best to be
10443 safe. Closes ticket 22672.
10444 - Fix a memset() off the end of an array when packing cells. This
10445 bug should be harmless in practice, since the corrupted bytes are
10446 still in the same structure, and are always padding bytes,
10447 ignored, or immediately overwritten, depending on compiler
10448 behavior. Nevertheless, because the memset()'s purpose is to make
10449 sure that any other cell-handling bugs can't expose bytes to the
10450 network, we need to fix it. Fixes bug 22737; bugfix on
10451 0.2.4.11-alpha. Fixes CID 1401591.
10453 o Minor bugfixes (directory authority):
10454 - When a directory authority rejects a descriptor or extrainfo with
10455 a given digest, mark that digest as undownloadable, so that we do
10456 not attempt to download it again over and over. We previously
10457 tried to avoid downloading such descriptors by other means, but we
10458 didn't notice if we accidentally downloaded one anyway. This
10459 behavior became problematic in 0.2.7.2-alpha, when authorities
10460 began pinning Ed25519 keys. Fixes bug 22349; bugfix
10462 - When rejecting a router descriptor for running an obsolete version
10463 of Tor without ntor support, warn about the obsolete tor version,
10464 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
10465 - Prevent the shared randomness subsystem from asserting when
10466 initialized by a bridge authority with an incomplete configuration
10467 file. Fixes bug 21586; bugfix on 0.2.9.8.
10469 o Minor bugfixes (error reporting, windows):
10470 - When formatting Windows error messages, use the English format to
10471 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
10474 o Minor bugfixes (exit-side DNS):
10475 - Fix an untriggerable assertion that checked the output of a
10476 libevent DNS error, so that the assertion actually behaves as
10477 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
10478 Karpov using PVS-Studio.
10480 o Minor bugfixes (fallback directories):
10481 - Make the usage example in updateFallbackDirs.py actually work, and
10482 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
10483 - Decrease the guard flag average required to be a fallback. This
10484 allows us to keep relays that have their guard flag removed when
10485 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
10486 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
10487 bugfix on 0.2.8.1-alpha.
10488 - Make sure fallback directory mirrors have the same address, port,
10489 and relay identity key for at least 30 days before they are
10490 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
10492 o Minor bugfixes (file limits, osx):
10493 - When setting the maximum number of connections allowed by the OS,
10494 always allow some extra file descriptors for other files. Fixes
10495 bug 22797; bugfix on 0.2.0.10-alpha.
10497 o Minor bugfixes (hidden services):
10498 - Increase the number of circuits that a service is allowed to
10499 open over a specific period of time. The value was lower than it
10500 should be (8 vs 12) in the normal case of 3 introduction points.
10501 Fixes bug 22159; bugfix on 0.3.0.5-rc.
10502 - Fix a BUG warning during HSv3 descriptor decoding that could be
10503 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
10504 on 0.3.0.1-alpha. Bug found by "haxxpop".
10505 - Stop printing a cryptic warning when a hidden service gets a
10506 request to connect to a virtual port that it hasn't configured.
10507 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
10508 - Simplify hidden service descriptor creation by using an existing
10509 flag to check if an introduction point is established. Fixes bug
10510 21599; bugfix on 0.2.7.2-alpha.
10512 o Minor bugfixes (link handshake):
10513 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
10514 months, and regenerate it when it is within one month of expiring.
10515 Previously, we had generated this certificate at startup with a
10516 ten-year lifetime, but that could lead to weird behavior when Tor
10517 was started with a grossly inaccurate clock. Mitigates bug 22466;
10518 mitigation on 0.3.0.1-alpha.
10520 o Minor bugfixes (linux seccomp2 sandbox):
10521 - Avoid a sandbox failure when trying to re-bind to a socket and
10522 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
10523 - Permit the fchmod system call, to avoid crashing on startup when
10524 starting with the seccomp2 sandbox and an unexpected set of
10525 permissions on the data directory or its contents. Fixes bug
10526 22516; bugfix on 0.2.5.4-alpha.
10528 o Minor bugfixes (logging):
10529 - When decompressing, do not warn if we fail to decompress using a
10530 compression method that we merely guessed. Fixes part of bug
10531 22670; bugfix on 0.1.1.14-alpha.
10532 - When decompressing, treat mismatch between content-encoding and
10533 actual compression type as a protocol warning. Fixes part of bug
10534 22670; bugfix on 0.1.1.9-alpha.
10535 - Downgrade "assigned_to_cpuworker failed" message to info-level
10536 severity. In every case that can reach it, either a better warning
10537 has already been logged, or no warning is warranted. Fixes bug
10538 22356; bugfix on 0.2.6.3-alpha.
10539 - Log a better message when a directory authority replies to an
10540 upload with an unexpected status code. Fixes bug 11121; bugfix
10542 - Downgrade a log statement about unexpected relay cells from "bug"
10543 to "protocol warning", because there is at least one use case
10544 where it can be triggered by a buggy tor implementation. Fixes bug
10545 21293; bugfix on 0.1.1.14-alpha.
10547 o Minor bugfixes (logging, relay):
10548 - Remove a forgotten debugging message when an introduction point
10549 successfully establishes a hidden service prop224 circuit with
10551 - Change three other log_warn() for an introduction point to
10552 protocol warnings, because they can be failure from the network
10553 and are not relevant to the operator. Fixes bug 23078; bugfix on
10554 0.3.0.1-alpha and 0.3.0.2-alpha.
10556 o Minor bugfixes (relay):
10557 - Inform the geoip and rephist modules about all requests, even on
10558 relays that are only fetching microdescriptors. Fixes a bug
10559 related to 21585; bugfix on 0.3.0.1-alpha.
10561 o Minor bugfixes (memory leaks):
10562 - Fix a small memory leak at exit from the backtrace handler code.
10563 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
10564 - When directory authorities reject a router descriptor due to
10565 keypinning, free the router descriptor rather than leaking the
10566 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
10567 - Fix a small memory leak when validating a configuration that uses
10568 two or more AF_UNIX sockets for the same port type. Fixes bug
10569 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
10571 o Minor bugfixes (process behavior):
10572 - When exiting because of an error, always exit with a nonzero exit
10573 status. Previously, we would fail to report an error in our exit
10574 status in cases related to __OwningControllerProcess failure,
10575 lockfile contention, and Ed25519 key initialization. Fixes bug
10576 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
10577 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
10580 o Minor bugfixes (robustness, error handling):
10581 - Improve our handling of the cases where OpenSSL encounters a
10582 memory error while encoding keys and certificates. We haven't
10583 observed these errors in the wild, but if they do happen, we now
10584 detect and respond better. Fixes bug 19418; bugfix on all versions
10585 of Tor. Reported by Guido Vranken.
10587 o Minor bugfixes (testing):
10588 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
10589 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
10590 - Use unbuffered I/O for utility functions around the
10591 process_handle_t type. This fixes unit test failures reported on
10592 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
10593 - Make display of captured unit test log messages consistent. Fixes
10594 bug 21510; bugfix on 0.2.9.3-alpha.
10595 - Make test-network.sh always call chutney's test-network.sh.
10596 Previously, this only worked on systems which had bash installed,
10597 due to some bash-specific code in the script. Fixes bug 19699;
10598 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
10599 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
10600 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
10601 - The unit tests now pass on systems where localhost is misconfigured
10602 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
10605 o Minor bugfixes (voting consistency):
10606 - Reject version numbers with non-numeric prefixes (such as +, -, or
10607 whitespace). Disallowing whitespace prevents differential version
10608 parsing between POSIX-based and Windows platforms. Fixes bug 21507
10609 and part of 21508; bugfix on 0.0.8pre1.
10611 o Minor bugfixes (Windows service):
10612 - When running as a Windows service, set the ID of the main thread
10613 correctly. Failure to do so made us fail to send log messages to
10614 the controller in 0.2.1.16-rc, slowed down controller event
10615 delivery in 0.2.7.3-rc and later, and crash with an assertion
10616 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
10617 Patch and diagnosis from "Vort".
10619 o Minor bugfixes (windows, relay):
10620 - Resolve "Failure from drain_fd: No error" warnings on Windows
10621 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
10623 o Code simplification and refactoring:
10624 - Break up the 630-line function connection_dir_client_reached_eof()
10625 into a dozen smaller functions. This change should help
10626 maintainability and readability of the client directory code.
10627 - Isolate our use of the openssl headers so that they are only
10628 included from our crypto wrapper modules, and from tests that
10629 examine those modules' internals. Closes ticket 21841.
10630 - Simplify our API to launch directory requests, making it more
10631 extensible and less error-prone. Now it's easier to add extra
10632 headers to directory requests. Closes ticket 21646.
10633 - Our base64 decoding functions no longer overestimate the output
10634 space that they need when parsing unpadded inputs. Closes
10636 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
10637 Resolves ticket 22213.
10638 - The logic that directory caches use to spool request to clients,
10639 serving them one part at a time so as not to allocate too much
10640 memory, has been refactored for consistency. Previously there was
10641 a separate spooling implementation per type of spoolable data. Now
10642 there is one common spooling implementation, with extensible data
10643 types. Closes ticket 21651.
10644 - Tor's compression module now supports multiple backends. Part of
10645 the implementation for proposal 278; closes ticket 21663.
10648 - Add a manpage description for the key-pinning-journal file. Closes
10650 - Correctly note that bandwidth accounting values are stored in the
10651 state file, and the bw_accounting file is now obsolete. Closes
10653 - Document more of the files in the Tor data directory, including
10654 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
10655 approved-routers, sr-random, and diff-cache. Found while fixing
10657 - Clarify the manpage for the (deprecated) torify script. Closes
10659 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
10660 Closes ticket 21873.
10661 - Correct documentation about the default DataDirectory value.
10662 Closes ticket 21151.
10663 - Document the default behavior of NumEntryGuards and
10664 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
10666 - Document key=value pluggable transport arguments for Bridge lines
10667 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
10668 - Note that bandwidth-limiting options don't affect TCP headers or
10669 DNS. Closes ticket 17170.
10671 o Removed features (configuration options, all in ticket 22060):
10672 - These configuration options are now marked Obsolete, and no longer
10673 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
10674 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
10675 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
10676 in 0.2.9.2-alpha and have now been removed. The previous default
10677 behavior is now always chosen; the previous (less secure) non-
10678 default behavior is now unavailable.
10679 - CloseHSClientCircuitsImmediatelyOnTimeout and
10680 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
10681 0.2.9.2-alpha and now have been removed. HS circuits never close
10682 on circuit build timeout; they have a longer timeout period.
10683 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
10684 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
10685 (and others) to configure listen-only and advertise-only addresses.
10687 o Removed features (tools):
10688 - We've removed the tor-checkkey tool from src/tools. Long ago, we
10689 used it to help people detect RSA keys that were generated by
10690 versions of Debian affected by CVE-2008-0166. But those keys have
10691 been out of circulation for ages, and this tool is no longer
10692 required. Closes ticket 21842.
10695 Changes in version 0.3.0.10 - 2017-08-02
10696 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
10697 from the current Tor alpha series. OpenBSD users and TPROXY users
10698 should upgrade; others are probably okay sticking with 0.3.0.9.
10700 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
10701 - Tor's repository now includes a Travis Continuous Integration (CI)
10702 configuration file (.travis.yml). This is meant to help new
10703 developers and contributors who fork Tor to a Github repository be
10704 better able to test their changes, and understand what we expect
10705 to pass. To use this new build feature, you must fork Tor to your
10706 Github account, then go into the "Integrations" menu in the
10707 repository settings for your fork and enable Travis, then push
10708 your changes. Closes ticket 22636.
10710 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
10711 - Fix a typo that had prevented TPROXY-based transparent proxying
10712 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
10713 Patch from "d4fq0fQAgoJ".
10715 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
10716 - Avoid an assertion failure bug affecting our implementation of
10717 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
10718 handling of "0xbar" differs from what we had expected. Fixes bug
10719 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
10721 o Minor features (backport from 0.3.1.5-alpha):
10722 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
10725 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
10726 - Roll over monthly accounting at the configured hour and minute,
10727 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
10728 Found by Andrey Karpov with PVS-Studio.
10730 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
10731 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
10732 bugfix on 0.2.8.1-alpha.
10733 - Fix warnings when building with libscrypt and openssl scrypt
10734 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
10735 - When building with certain versions of the mingw C header files,
10736 avoid float-conversion warnings when calling the C functions
10737 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
10740 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
10741 - Backport a fix for an "unused variable" warning that appeared
10742 in some versions of mingw. Fixes bug 22838; bugfix on
10745 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
10746 - Avoid Coverity build warnings related to our BUG() macro. By
10747 default, Coverity treats BUG() as the Linux kernel does: an
10748 instant abort(). We need to override that so our BUG() macro
10749 doesn't prevent Coverity from analyzing functions that use it.
10750 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
10752 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
10753 - When rejecting a router descriptor for running an obsolete version
10754 of Tor without ntor support, warn about the obsolete tor version,
10755 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
10757 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
10758 - Avoid a sandbox failure when trying to re-bind to a socket and
10759 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
10761 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
10762 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
10763 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
10766 Changes in version 0.3.0.9 - 2017-06-29
10767 Tor 0.3.0.9 fixes a path selection bug that would allow a client
10768 to use a guard that was in the same network family as a chosen exit
10769 relay. This is a security regression; all clients running earlier
10770 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
10773 This release also backports several other bugfixes from the 0.3.1.x
10776 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
10777 - When choosing which guard to use for a circuit, avoid the exit's
10778 family along with the exit itself. Previously, the new guard
10779 selection logic avoided the exit, but did not consider its family.
10780 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
10781 006 and CVE-2017-0377.
10783 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
10784 - Don't block bootstrapping when a primary bridge is offline and we
10785 can't get its descriptor. Fixes bug 22325; fixes one case of bug
10786 21969; bugfix on 0.3.0.3-alpha.
10788 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
10789 - When starting with an old consensus, do not add new entry guards
10790 unless the consensus is "reasonably live" (under 1 day old). Fixes
10791 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
10793 o Minor features (geoip):
10794 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
10797 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
10798 - Reject version numbers with non-numeric prefixes (such as +, -, or
10799 whitespace). Disallowing whitespace prevents differential version
10800 parsing between POSIX-based and Windows platforms. Fixes bug 21507
10801 and part of 21508; bugfix on 0.0.8pre1.
10803 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
10804 - Permit the fchmod system call, to avoid crashing on startup when
10805 starting with the seccomp2 sandbox and an unexpected set of
10806 permissions on the data directory or its contents. Fixes bug
10807 22516; bugfix on 0.2.5.4-alpha.
10809 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
10810 - Fix a memset() off the end of an array when packing cells. This
10811 bug should be harmless in practice, since the corrupted bytes are
10812 still in the same structure, and are always padding bytes,
10813 ignored, or immediately overwritten, depending on compiler
10814 behavior. Nevertheless, because the memset()'s purpose is to make
10815 sure that any other cell-handling bugs can't expose bytes to the
10816 network, we need to fix it. Fixes bug 22737; bugfix on
10817 0.2.4.11-alpha. Fixes CID 1401591.
10820 Changes in version 0.3.0.8 - 2017-06-08
10821 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
10822 remotely crash a hidden service with an assertion failure. Anyone
10823 running a hidden service should upgrade to this version, or to some
10824 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
10826 Tor 0.3.0.8 also includes fixes for several key management bugs
10827 that sometimes made relays unreliable, as well as several other
10828 bugfixes described below.
10830 o Major bugfixes (hidden service, relay, security, backport
10831 from 0.3.1.3-alpha):
10832 - Fix a remotely triggerable assertion failure when a hidden service
10833 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
10834 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
10835 - Fix a remotely triggerable assertion failure caused by receiving a
10836 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
10837 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
10840 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
10841 - When performing the v3 link handshake on a TLS connection, report
10842 that we have the x509 certificate that we actually used on that
10843 connection, even if we have changed certificates since that
10844 connection was first opened. Previously, we would claim to have
10845 used our most recent x509 link certificate, which would sometimes
10846 make the link handshake fail. Fixes one case of bug 22460; bugfix
10849 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
10850 - Regenerate link and authentication certificates whenever the key
10851 that signs them changes; also, regenerate link certificates
10852 whenever the signed key changes. Previously, these processes were
10853 only weakly coupled, and we relays could (for minutes to hours)
10854 wind up with an inconsistent set of keys and certificates, which
10855 other relays would not accept. Fixes two cases of bug 22460;
10856 bugfix on 0.3.0.1-alpha.
10857 - When sending an Ed25519 signing->link certificate in a CERTS cell,
10858 send the certificate that matches the x509 certificate that we
10859 used on the TLS connection. Previously, there was a race condition
10860 if the TLS context rotated after we began the TLS handshake but
10861 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
10864 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
10865 - Stop rejecting v3 hidden service descriptors because their size
10866 did not match an old padding rule. Fixes bug 22447; bugfix on
10869 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
10870 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
10871 December 2016 (of which ~126 were still functional) with a list of
10872 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
10873 2017. Resolves ticket 21564.
10875 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
10876 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
10877 bug 22252; bugfix on 0.2.9.3-alpha.
10879 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
10880 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
10881 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
10883 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
10884 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
10885 months, and regenerate it when it is within one month of expiring.
10886 Previously, we had generated this certificate at startup with a
10887 ten-year lifetime, but that could lead to weird behavior when Tor
10888 was started with a grossly inaccurate clock. Mitigates bug 22466;
10889 mitigation on 0.3.0.1-alpha.
10891 o Minor bugfixes (memory leak, directory authority, backport from
10893 - When directory authorities reject a router descriptor due to
10894 keypinning, free the router descriptor rather than leaking the
10895 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
10898 Changes in version 0.2.9.11 - 2017-06-08
10899 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
10900 remotely crash a hidden service with an assertion failure. Anyone
10901 running a hidden service should upgrade to this version, or to some
10902 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
10903 are not affected by TROVE-2017-004.)
10905 Tor 0.2.9.11 also backports fixes for several key management bugs
10906 that sometimes made relays unreliable, as well as several other
10907 bugfixes described below.
10909 o Major bugfixes (hidden service, relay, security, backport
10910 from 0.3.1.3-alpha):
10911 - Fix a remotely triggerable assertion failure caused by receiving a
10912 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
10913 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
10916 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
10917 - When performing the v3 link handshake on a TLS connection, report
10918 that we have the x509 certificate that we actually used on that
10919 connection, even if we have changed certificates since that
10920 connection was first opened. Previously, we would claim to have
10921 used our most recent x509 link certificate, which would sometimes
10922 make the link handshake fail. Fixes one case of bug 22460; bugfix
10925 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
10926 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
10927 December 2016 (of which ~126 were still functional) with a list of
10928 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
10929 2017. Resolves ticket 21564.
10931 o Minor features (future-proofing, backport from 0.3.0.7):
10932 - Tor no longer refuses to download microdescriptors or descriptors if
10933 they are listed as "published in the future". This change will
10934 eventually allow us to stop listing meaningful "published" dates
10935 in microdescriptor consensuses, and thereby allow us to reduce the
10936 resources required to download consensus diffs by over 50%.
10937 Implements part of ticket 21642; implements part of proposal 275.
10939 o Minor features (directory authorities, backport from 0.3.0.4-rc)
10940 - Directory authorities now reject relays running versions
10941 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
10942 suffer from bug 20499 and don't keep their consensus cache
10943 up-to-date. Resolves ticket 20509.
10945 o Minor features (geoip):
10946 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
10949 o Minor bugfixes (control port, backport from 0.3.0.6):
10950 - The GETINFO extra-info/digest/<digest> command was broken because
10951 of a wrong base16 decode return value check, introduced when
10952 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
10954 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
10955 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
10956 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
10958 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
10959 - The getpid() system call is now permitted under the Linux seccomp2
10960 sandbox, to avoid crashing with versions of OpenSSL (and other
10961 libraries) that attempt to learn the process's PID by using the
10962 syscall rather than the VDSO code. Fixes bug 21943; bugfix
10965 o Minor bugfixes (memory leak, directory authority, backport
10966 from 0.3.1.2-alpha):
10967 - When directory authorities reject a router descriptor due to
10968 keypinning, free the router descriptor rather than leaking the
10969 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
10971 Changes in version 0.2.8.14 - 2017-06-08
10972 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
10973 remotely crash a hidden service with an assertion failure. Anyone
10974 running a hidden service should upgrade to this version, or to some
10975 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
10976 are not affected by TROVE-2017-004.)
10978 o Major bugfixes (hidden service, relay, security):
10979 - Fix a remotely triggerable assertion failure caused by receiving a
10980 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
10981 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
10984 o Minor features (geoip):
10985 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
10988 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
10989 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
10990 December 2016 (of which ~126 were still functional) with a list of
10991 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
10992 2017. Resolves ticket 21564.
10994 o Minor bugfixes (correctness):
10995 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
10996 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
10998 Changes in version 0.2.7.8 - 2017-06-08
10999 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
11000 remotely crash a hidden service with an assertion failure. Anyone
11001 running a hidden service should upgrade to this version, or to some
11002 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11003 are not affected by TROVE-2017-004.)
11005 o Major bugfixes (hidden service, relay, security):
11006 - Fix a remotely triggerable assertion failure caused by receiving a
11007 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11008 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11011 o Minor features (geoip):
11012 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11015 o Minor bugfixes (correctness):
11016 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11017 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11020 Changes in version 0.2.6.12 - 2017-06-08
11021 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
11022 remotely crash a hidden service with an assertion failure. Anyone
11023 running a hidden service should upgrade to this version, or to some
11024 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11025 are not affected by TROVE-2017-004.)
11027 o Major bugfixes (hidden service, relay, security):
11028 - Fix a remotely triggerable assertion failure caused by receiving a
11029 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11030 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11033 o Minor features (geoip):
11034 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11037 o Minor bugfixes (correctness):
11038 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11039 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11041 Changes in version 0.2.5.14 - 2017-06-08
11042 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
11043 remotely crash a hidden service with an assertion failure. Anyone
11044 running a hidden service should upgrade to this version, or to some
11045 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11046 are not affected by TROVE-2017-004.)
11048 o Major bugfixes (hidden service, relay, security):
11049 - Fix a remotely triggerable assertion failure caused by receiving a
11050 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11051 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11054 o Minor features (geoip):
11055 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11058 o Minor bugfixes (correctness):
11059 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11060 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11062 Changes in version 0.2.4.29 - 2017-06-08
11063 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
11064 remotely crash a hidden service with an assertion failure. Anyone
11065 running a hidden service should upgrade to this version, or to some
11066 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11067 are not affected by TROVE-2017-004.)
11069 o Major bugfixes (hidden service, relay, security):
11070 - Fix a remotely triggerable assertion failure caused by receiving a
11071 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11072 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11075 o Minor features (geoip):
11076 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11079 o Minor bugfixes (correctness):
11080 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11081 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11084 Changes in version 0.3.0.7 - 2017-05-15
11085 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
11086 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
11087 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
11088 clients are not affected.
11090 o Major bugfixes (hidden service directory, security):
11091 - Fix an assertion failure in the hidden service directory code, which
11092 could be used by an attacker to remotely cause a Tor relay process to
11093 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
11094 should upgrade. This security issue is tracked as TROVE-2017-002.
11095 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
11098 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11101 o Minor features (future-proofing):
11102 - Tor no longer refuses to download microdescriptors or descriptors
11103 if they are listed as "published in the future". This change will
11104 eventually allow us to stop listing meaningful "published" dates
11105 in microdescriptor consensuses, and thereby allow us to reduce the
11106 resources required to download consensus diffs by over 50%.
11107 Implements part of ticket 21642; implements part of proposal 275.
11109 o Minor bugfixes (Linux seccomp2 sandbox):
11110 - The getpid() system call is now permitted under the Linux seccomp2
11111 sandbox, to avoid crashing with versions of OpenSSL (and other
11112 libraries) that attempt to learn the process's PID by using the
11113 syscall rather than the VDSO code. Fixes bug 21943; bugfix
11117 Changes in version 0.3.0.6 - 2017-04-26
11118 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
11120 With the 0.3.0 series, clients and relays now use Ed25519 keys to
11121 authenticate their link connections to relays, rather than the old
11122 RSA1024 keys that they used before. (Circuit crypto has been
11123 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
11124 the guard selection and replacement algorithm to behave more robustly
11125 in the presence of unreliable networks, and to resist guard-
11128 This series also includes numerous other small features and bugfixes,
11129 along with more groundwork for the upcoming hidden-services revamp.
11131 Per our stable release policy, we plan to support the Tor 0.3.0
11132 release series for at least the next nine months, or for three months
11133 after the first stable release of the 0.3.1 series: whichever is
11134 longer. If you need a release with long-term support, we recommend
11135 that you stay with the 0.2.9 series.
11137 Below are the changes since 0.2.9.10. For a list of only the changes
11138 since 0.3.0.5-rc, see the ChangeLog file.
11140 o Major features (directory authority, security):
11141 - The default for AuthDirPinKeys is now 1: directory authorities
11142 will reject relays where the RSA identity key matches a previously
11143 seen value, but the Ed25519 key has changed. Closes ticket 18319.
11145 o Major features (guard selection algorithm):
11146 - Tor's guard selection algorithm has been redesigned from the
11147 ground up, to better support unreliable networks and restrictive
11148 sets of entry nodes, and to better resist guard-capture attacks by
11149 hostile local networks. Implements proposal 271; closes
11152 o Major features (next-generation hidden services):
11153 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
11154 prop224 aka "Next Generation Hidden Services". Service and clients
11155 don't use this functionality yet. Closes ticket 19043. Based on
11156 initial code by Alec Heifetz.
11157 - Relays now support the HSDir version 3 protocol, so that they can
11158 can store and serve v3 descriptors. This is part of the next-
11159 generation onion service work detailed in proposal 224. Closes
11162 o Major features (protocol, ed25519 identity keys):
11163 - Clients now support including Ed25519 identity keys in the EXTEND2
11164 cells they generate. By default, this is controlled by a consensus
11165 parameter, currently disabled. You can turn this feature on for
11166 testing by setting ExtendByEd25519ID in your configuration. This
11167 might make your traffic appear different than the traffic
11168 generated by other users, however. Implements part of ticket
11169 15056; part of proposal 220.
11170 - Relays now understand requests to extend to other relays by their
11171 Ed25519 identity keys. When an Ed25519 identity key is included in
11172 an EXTEND2 cell, the relay will only extend the circuit if the
11173 other relay can prove ownership of that identity. Implements part
11174 of ticket 15056; part of proposal 220.
11175 - Relays now use Ed25519 to prove their Ed25519 identities and to
11176 one another, and to clients. This algorithm is faster and more
11177 secure than the RSA-based handshake we've been doing until now.
11178 Implements the second big part of proposal 220; Closes
11181 o Major features (security):
11182 - Change the algorithm used to decide DNS TTLs on client and server
11183 side, to better resist DNS-based correlation attacks like the
11184 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
11185 Feamster. Now relays only return one of two possible DNS TTL
11186 values, and clients are willing to believe DNS TTL values up to 3
11187 hours long. Closes ticket 19769.
11189 o Major bugfixes (client, onion service, also in 0.2.9.9):
11190 - Fix a client-side onion service reachability bug, where multiple
11191 socks requests to an onion service (or a single slow request)
11192 could cause us to mistakenly mark some of the service's
11193 introduction points as failed, and we cache that failure so
11194 eventually we run out and can't reach the service. Also resolves a
11195 mysterious "Remote server sent bogus reason code 65021" log
11196 warning. The bug was introduced in ticket 17218, where we tried to
11197 remember the circuit end reason as a uint16_t, which mangled
11198 negative values. Partially fixes bug 21056 and fixes bug 20307;
11199 bugfix on 0.2.8.1-alpha.
11201 o Major bugfixes (crash, directory connections):
11202 - Fix a rare crash when sending a begin cell on a circuit whose
11203 linked directory connection had already been closed. Fixes bug
11204 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
11206 o Major bugfixes (directory authority):
11207 - During voting, when marking a relay as a probable sybil, do not
11208 clear its BadExit flag: sybils can still be bad in other ways
11209 too. (We still clear the other flags.) Fixes bug 21108; bugfix
11212 o Major bugfixes (DNS):
11213 - Fix a bug that prevented exit nodes from caching DNS records for
11214 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
11216 o Major bugfixes (IPv6 Exits):
11217 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
11218 any IPv6 addresses. Instead, only reject a port over IPv6 if the
11219 exit policy rejects that port on more than an IPv6 /16 of
11220 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
11221 which rejected a relay's own IPv6 address by default. Fixes bug
11222 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
11224 o Major bugfixes (parsing):
11225 - Fix an integer underflow bug when comparing malformed Tor
11226 versions. This bug could crash Tor when built with
11227 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
11228 0.2.9.8, which were built with -ftrapv by default. In other cases
11229 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
11230 on 0.0.8pre1. Found by OSS-Fuzz.
11231 - When parsing a malformed content-length field from an HTTP
11232 message, do not read off the end of the buffer. This bug was a
11233 potential remote denial-of-service attack against Tor clients and
11234 relays. A workaround was released in October 2016, to prevent this
11235 bug from crashing Tor. This is a fix for the underlying issue,
11236 which should no longer matter (if you applied the earlier patch).
11237 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
11238 using AFL (http://lcamtuf.coredump.cx/afl/).
11240 o Major bugfixes (scheduler):
11241 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
11242 caused the channel scheduler to behave more or less randomly,
11243 rather than preferring channels with higher-priority circuits.
11244 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
11246 o Major bugfixes (security, also in 0.2.9.9):
11247 - Downgrade the "-ftrapv" option from "always on" to "only on when
11248 --enable-expensive-hardening is provided." This hardening option,
11249 like others, can turn survivable bugs into crashes--and having it
11250 on by default made a (relatively harmless) integer overflow bug
11251 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
11252 bugfix on 0.2.9.1-alpha.
11254 o Minor feature (client):
11255 - Enable IPv6 traffic on the SocksPort by default. To disable this,
11256 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
11258 o Minor feature (fallback scripts):
11259 - Add a check_existing mode to updateFallbackDirs.py, which checks
11260 if fallbacks in the hard-coded list are working. Closes ticket
11261 20174. Patch by haxxpop.
11263 o Minor feature (protocol versioning):
11264 - Add new protocol version for proposal 224. HSIntro now advertises
11265 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
11267 o Minor features (ciphersuite selection):
11268 - Allow relays to accept a wider range of ciphersuites, including
11269 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
11270 - Clients now advertise a list of ciphersuites closer to the ones
11271 preferred by Firefox. Closes part of ticket 15426.
11273 o Minor features (controller):
11274 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
11275 shared-random values to the controller. Closes ticket 19925.
11276 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
11277 rather than "unrecognized." Closes ticket 20389; patch from
11280 o Minor features (controller, configuration):
11281 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
11282 and so on, now comes with a __*Port variant that will not be saved
11283 to the torrc file by the controller's SAVECONF command. This
11284 change allows TorBrowser to set up a single-use domain socket for
11285 each time it launches Tor. Closes ticket 20956.
11286 - The GETCONF command can now query options that may only be
11287 meaningful in context-sensitive lists. This allows the controller
11288 to query the mixed SocksPort/__SocksPort style options introduced
11289 in feature 20956. Implements ticket 21300.
11291 o Minor features (diagnostic, directory client):
11292 - Warn when we find an unexpected inconsistency in directory
11293 download status objects. Prevents some negative consequences of
11296 o Minor features (directory authorities):
11297 - Directory authorities now reject descriptors that claim to be
11298 malformed versions of Tor. Helps prevent exploitation of
11300 - Reject version numbers with components that exceed INT32_MAX.
11301 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
11302 Fixes bug 21450; bugfix on 0.0.8pre1.
11304 o Minor features (directory authority):
11305 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
11306 default) to control whether authorities should try to probe relays
11307 by their Ed25519 link keys. This option will go away in a few
11308 releases--unless we encounter major trouble in our ed25519 link
11309 protocol rollout, in which case it will serve as a safety option.
11311 o Minor features (directory cache):
11312 - Relays and bridges will now refuse to serve the consensus they
11313 have if they know it is too old for a client to use. Closes
11316 o Minor features (ed25519 link handshake):
11317 - Advertise support for the ed25519 link handshake using the
11318 subprotocol-versions mechanism, so that clients can tell which
11319 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
11321 o Minor features (entry guards):
11322 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
11323 break regression tests.
11324 - Require UseEntryGuards when UseBridges is set, in order to make
11325 sure bridges aren't bypassed. Resolves ticket 20502.
11327 o Minor features (fallback directories):
11328 - Allow 3 fallback relays per operator, which is safe now that we
11329 are choosing 200 fallback relays. Closes ticket 20912.
11330 - Annotate updateFallbackDirs.py with the bandwidth and consensus
11331 weight for each candidate fallback. Closes ticket 20878.
11332 - Display the relay fingerprint when downloading consensuses from
11333 fallbacks. Closes ticket 20908.
11334 - Exclude relays affected by bug 20499 from the fallback list.
11335 Exclude relays from the fallback list if they are running versions
11336 known to be affected by bug 20499, or if in our tests they deliver
11337 a stale consensus (i.e. one that expired more than 24 hours ago).
11338 Closes ticket 20539.
11339 - Make it easier to change the output sort order of fallbacks.
11340 Closes ticket 20822.
11341 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
11343 - Require fallback directories to have the same address and port for
11344 7 days (now that we have enough relays with this stability).
11345 Relays whose OnionOO stability timer is reset on restart by bug
11346 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
11347 this issue. Closes ticket 20880; maintains short-term fix
11349 - Require fallbacks to have flags for 90% of the time (weighted
11350 decaying average), rather than 95%. This allows at least 73% of
11351 clients to bootstrap in the first 5 seconds without contacting an
11352 authority. Part of ticket 18828.
11353 - Select 200 fallback directories for each release. Closes
11356 o Minor features (fingerprinting resistance, authentication):
11357 - Extend the length of RSA keys used for TLS link authentication to
11358 2048 bits. (These weren't used for forward secrecy; for forward
11359 secrecy, we used P256.) Closes ticket 13752.
11361 o Minor features (geoip):
11362 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
11365 o Minor features (geoip, also in 0.2.9.9):
11366 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
11369 o Minor features (infrastructure):
11370 - Implement smartlist_add_strdup() function. Replaces the use of
11371 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
11373 o Minor features (linting):
11374 - Enhance the changes file linter to warn on Tor versions that are
11375 prefixed with "tor-". Closes ticket 21096.
11377 o Minor features (logging):
11378 - In several places, describe unset ed25519 keys as "<unset>",
11379 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
11381 o Minor features (portability, compilation):
11382 - Autoconf now checks to determine if OpenSSL structures are opaque,
11383 instead of explicitly checking for OpenSSL version numbers. Part
11385 - Support building with recent LibreSSL code that uses opaque
11386 structures. Closes ticket 21359.
11388 o Minor features (relay):
11389 - We now allow separation of exit and relay traffic to different
11390 source IP addresses, using the OutboundBindAddressExit and
11391 OutboundBindAddressOR options respectively. Closes ticket 17975.
11392 Written by Michael Sonntag.
11394 o Minor features (reliability, crash):
11395 - Try better to detect problems in buffers where they might grow (or
11396 think they have grown) over 2 GB in size. Diagnostic for
11399 o Minor features (testing):
11400 - During 'make test-network-all', if tor logs any warnings, ask
11401 chutney to output them. Requires a recent version of chutney with
11402 the 21572 patch. Implements 21570.
11404 o Minor bugfix (control protocol):
11405 - The reply to a "GETINFO config/names" request via the control
11406 protocol now spells the type "Dependent" correctly. This is a
11407 breaking change in the control protocol. (The field seems to be
11408 ignored by the most common known controllers.) Fixes bug 18146;
11409 bugfix on 0.1.1.4-alpha.
11410 - The GETINFO extra-info/digest/<digest> command was broken because
11411 of a wrong base16 decode return value check, introduced when
11412 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
11414 o Minor bugfix (logging):
11415 - Don't recommend the use of Tor2web in non-anonymous mode.
11416 Recommending Tor2web is a bad idea because the client loses all
11417 anonymity. Tor2web should only be used in specific cases by users
11418 who *know* and understand the issues. Fixes bug 21294; bugfix
11421 o Minor bugfixes (bug resilience):
11422 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
11423 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
11424 Hans Jerry Illikainen.
11426 o Minor bugfixes (build):
11427 - Replace obsolete Autoconf macros with their modern equivalent and
11428 prevent similar issues in the future. Fixes bug 20990; bugfix
11431 o Minor bugfixes (certificate expiration time):
11432 - Avoid using link certificates that don't become valid till some
11433 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
11435 o Minor bugfixes (client):
11436 - Always recover from failures in extend_info_from_node(), in an
11437 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
11438 bugfix on 0.2.3.1-alpha.
11439 - When clients that use bridges start up with a cached consensus on
11440 disk, they were ignoring it and downloading a new one. Now they
11441 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
11443 o Minor bugfixes (code correctness):
11444 - Repair a couple of (unreachable or harmless) cases of the risky
11445 comparison-by-subtraction pattern that caused bug 21278.
11447 o Minor bugfixes (config):
11448 - Don't assert on startup when trying to get the options list and
11449 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
11450 options so of course they aren't ready yet. Fixes bug 21062;
11451 bugfix on 0.2.9.3-alpha.
11453 o Minor bugfixes (configuration):
11454 - Accept non-space whitespace characters after the severity level in
11455 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
11456 - Support "TByte" and "TBytes" units in options given in bytes.
11457 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
11458 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
11460 o Minor bugfixes (configure, autoconf):
11461 - Rename the configure option --enable-expensive-hardening to
11462 --enable-fragile-hardening. Expensive hardening makes the tor
11463 daemon abort when some kinds of issues are detected. Thus, it
11464 makes tor more at risk of remote crashes but safer against RCE or
11465 heartbleed bug category. We now try to explain this issue in a
11466 message from the configure script. Fixes bug 21290; bugfix
11469 o Minor bugfixes (consensus weight):
11470 - Add new consensus method that initializes bw weights to 1 instead
11471 of 0. This prevents a zero weight from making it all the way to
11472 the end (happens in small testing networks) and causing an error.
11473 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
11475 o Minor bugfixes (crash prevention):
11476 - Fix an (currently untriggerable, but potentially dangerous) crash
11477 bug when base32-encoding inputs whose sizes are not a multiple of
11478 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
11480 o Minor bugfixes (dead code):
11481 - Remove a redundant check for PidFile changes at runtime in
11482 options_transition_allowed(): this check is already performed
11483 regardless of whether the sandbox is active. Fixes bug 21123;
11484 bugfix on 0.2.5.4-alpha.
11486 o Minor bugfixes (descriptors):
11487 - Correctly recognise downloaded full descriptors as valid, even
11488 when using microdescriptors as circuits. This affects clients with
11489 FetchUselessDescriptors set, and may affect directory authorities.
11490 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
11492 o Minor bugfixes (directory mirrors):
11493 - Allow relays to use directory mirrors without a DirPort: these
11494 relays need to be contacted over their ORPorts using a begindir
11495 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
11496 - Clarify the message logged when a remote relay is unexpectedly
11497 missing an ORPort or DirPort: users were confusing this with a
11498 local port. Fixes another case of bug 20711; bugfix
11501 o Minor bugfixes (directory system):
11502 - Bridges and relays now use microdescriptors (like clients do)
11503 rather than old-style router descriptors. Now bridges will blend
11504 in with clients in terms of the circuits they build. Fixes bug
11505 6769; bugfix on 0.2.3.2-alpha.
11506 - Download all consensus flavors, descriptors, and authority
11507 certificates when FetchUselessDescriptors is set, regardless of
11508 whether tor is a directory cache or not. Fixes bug 20667; bugfix
11509 on all recent tor versions.
11511 o Minor bugfixes (documentation):
11512 - Update the tor manual page to document every option that can not
11513 be changed while tor is running. Fixes bug 21122.
11515 o Minor bugfixes (ed25519 certificates):
11516 - Correctly interpret ed25519 certificates that would expire some
11517 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
11519 o Minor bugfixes (fallback directories):
11520 - Avoid checking fallback candidates' DirPorts if they are down in
11521 OnionOO. When a relay operator has multiple relays, this
11522 prioritizes relays that are up over relays that are down. Fixes
11523 bug 20926; bugfix on 0.2.8.3-alpha.
11524 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
11525 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
11526 - Stop failing when a relay has no uptime data in
11527 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
11529 o Minor bugfixes (hidden service):
11530 - Clean up the code for expiring intro points with no associated
11531 circuits. It was causing, rarely, a service with some expiring
11532 introduction points to not open enough additional introduction
11533 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
11534 - Resolve two possible underflows which could lead to creating and
11535 closing a lot of introduction point circuits in a non-stop loop.
11536 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
11537 - Stop setting the torrc option HiddenServiceStatistics to "0" just
11538 because we're not a bridge or relay. Instead, we preserve whatever
11539 value the user set (or didn't set). Fixes bug 21150; bugfix
11542 o Minor bugfixes (hidden services):
11543 - Make hidden services check for failed intro point connections,
11544 even when they have exceeded their intro point creation limit.
11545 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
11546 - Make hidden services with 8 to 10 introduction points check for
11547 failed circuits immediately after startup. Previously, they would
11548 wait for 5 minutes before performing their first checks. Fixes bug
11549 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
11550 - Stop ignoring misconfigured hidden services. Instead, refuse to
11551 start tor until the misconfigurations have been corrected. Fixes
11552 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
11555 o Minor bugfixes (IPv6):
11556 - Make IPv6-using clients try harder to find an IPv6 directory
11557 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
11558 - When IPv6 addresses have not been downloaded yet (microdesc
11559 consensus documents don't list relay IPv6 addresses), use hard-
11560 coded addresses for authorities, fallbacks, and configured
11561 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
11562 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
11564 o Minor bugfixes (memory leak at exit):
11565 - Fix a small harmless memory leak at exit of the previously unused
11566 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
11569 o Minor bugfixes (onion services):
11570 - Allow the number of introduction points to be as low as 0, rather
11571 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
11573 o Minor bugfixes (portability):
11574 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
11575 It is supported by OpenBSD itself, and also by most OpenBSD
11576 variants (such as Bitrig). Fixes bug 20980; bugfix
11579 o Minor bugfixes (portability, also in 0.2.9.9):
11580 - Avoid crashing when Tor is built using headers that contain
11581 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
11582 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
11584 - Fix Libevent detection on platforms without Libevent 1 headers
11585 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
11587 o Minor bugfixes (relay):
11588 - Avoid a double-marked-circuit warning that could happen when we
11589 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
11591 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
11592 initializing the keys would reset the DataDirectory to 0700
11593 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
11594 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
11596 o Minor bugfixes (testing):
11597 - Fix Raspbian build issues related to missing socket errno in
11598 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch by "hein".
11599 - Remove undefined behavior from the backtrace generator by removing
11600 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
11601 - Use bash in src/test/test-network.sh. This ensures we reliably
11602 call chutney's newer tools/test-network.sh when available. Fixes
11603 bug 21562; bugfix on 0.2.9.1-alpha.
11605 o Minor bugfixes (tor-resolve):
11606 - The tor-resolve command line tool now rejects hostnames over 255
11607 characters in length. Previously, it would silently truncate them,
11608 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
11609 Patch by "junglefowl".
11611 o Minor bugfixes (unit tests):
11612 - Allow the unit tests to pass even when DNS lookups of bogus
11613 addresses do not fail as expected. Fixes bug 20862 and 20863;
11614 bugfix on unit tests introduced in 0.2.8.1-alpha
11615 through 0.2.9.4-alpha.
11617 o Minor bugfixes (util):
11618 - When finishing writing a file to disk, if we were about to replace
11619 the file with the temporary file created before and we fail to
11620 replace it, remove the temporary file so it doesn't stay on disk.
11621 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
11623 o Minor bugfixes (Windows services):
11624 - Be sure to initialize the monotonic time subsystem before using
11625 it, even when running as an NT service. Fixes bug 21356; bugfix
11628 o Minor bugfixes (Windows):
11629 - Check for getpagesize before using it to mmap files. This fixes
11630 compilation in some MinGW environments. Fixes bug 20530; bugfix on
11631 0.1.2.1-alpha. Reported by "ice".
11633 o Code simplification and refactoring:
11634 - Abolish all global guard context in entrynodes.c; replace with new
11635 guard_selection_t structure as preparation for proposal 271.
11636 Closes ticket 19858.
11637 - Extract magic numbers in circuituse.c into defined variables.
11638 - Introduce rend_service_is_ephemeral() that tells if given onion
11639 service is ephemeral. Replace unclear NULL-checkings for service
11640 directory with this function. Closes ticket 20526.
11641 - Refactor circuit_is_available_for_use to remove unnecessary check.
11642 - Refactor circuit_predict_and_launch_new for readability and
11643 testability. Closes ticket 18873.
11644 - Refactor code to manipulate global_origin_circuit_list into
11645 separate functions. Closes ticket 20921.
11646 - Refactor large if statement in purpose_needs_anonymity to use
11647 switch statement instead. Closes part of ticket 20077.
11648 - Refactor the hashing API to return negative values for errors, as
11649 is done as throughout the codebase. Closes ticket 20717.
11650 - Remove data structures that were used to index or_connection
11651 objects by their RSA identity digests. These structures are fully
11652 redundant with the similar structures used in the
11653 channel abstraction.
11654 - Remove duplicate code in the channel_write_*cell() functions.
11655 Closes ticket 13827; patch from Pingl.
11656 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
11657 use only purpose_needs_anonymity. Closes part of ticket 20077.
11658 - The code to generate and parse EXTEND and EXTEND2 cells has been
11659 replaced with code automatically generated by the
11662 o Documentation (formatting):
11663 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
11664 blocks were incorrectly appearing. Closes ticket 20885.
11666 o Documentation (man page):
11667 - Clarify many options in tor.1 and add some min/max values for
11668 HiddenService options. Closes ticket 21058.
11671 - Change '1' to 'weight_scale' in consensus bw weights calculation
11672 comments, as that is reality. Closes ticket 20273. Patch
11674 - Clarify that when ClientRejectInternalAddresses is enabled (which
11675 is the default), multicast DNS hostnames for machines on the local
11676 network (of the form *.local) are also rejected. Closes
11678 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
11679 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix on 0.2.5.6-alpha.
11680 - Include the "TBits" unit in Tor's man page. Fixes part of bug
11681 20622; bugfix on 0.2.5.1-alpha.
11682 - Small fixes to the fuzzing documentation. Closes ticket 21472.
11683 - Stop the man page from incorrectly stating that HiddenServiceDir
11684 must already exist. Fixes 20486.
11685 - Update the description of the directory server options in the
11686 manual page, to clarify that a relay no longer needs to set
11687 DirPort in order to be a directory cache. Closes ticket 21720.
11689 o Removed features:
11690 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
11691 limit for relays running on a single IP applies to authority IP
11692 addresses as well as to non-authority IP addresses. Closes
11694 - The UseDirectoryGuards torrc option no longer exists: all users
11695 that use entry guards will also use directory guards. Related to
11696 proposal 271; implements part of ticket 20831.
11699 - Add tests for networkstatus_compute_bw_weights_v10.
11700 - Add unit tests circuit_predict_and_launch_new.
11701 - Extract dummy_origin_circuit_new so it can be used by other
11703 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
11704 from "overcaffeinated".
11705 - Perform the coding style checks when running the tests and fail
11706 when coding style violations are found. Closes ticket 5500.
11709 Changes in version 0.2.8.13 - 2017-03-03
11710 Tor 0.2.8.13 backports a security fix from later Tor
11711 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
11712 this release, if for some reason they cannot upgrade to a later
11713 release series, and if they build Tor with the --enable-expensive-hardening
11716 Note that support for Tor 0.2.8.x is ending next year: we will not issue
11717 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
11718 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
11720 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
11721 - Fix an integer underflow bug when comparing malformed Tor
11722 versions. This bug could crash Tor when built with
11723 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
11724 0.2.9.8, which were built with -ftrapv by default. In other cases
11725 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
11726 on 0.0.8pre1. Found by OSS-Fuzz.
11728 o Minor features (geoip):
11729 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
11733 Changes in version 0.2.7.7 - 2017-03-03
11734 Tor 0.2.7.7 backports a number of security fixes from later Tor
11735 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
11736 this release, if for some reason they cannot upgrade to a later
11739 Note that support for Tor 0.2.7.x is ending this year: we will not issue
11740 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
11741 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
11743 o Directory authority changes (backport from 0.2.8.5-rc):
11744 - Urras is no longer a directory authority. Closes ticket 19271.
11746 o Directory authority changes (backport from 0.2.9.2-alpha):
11747 - The "Tonga" bridge authority has been retired; the new bridge
11748 authority is "Bifroest". Closes tickets 19728 and 19690.
11750 o Directory authority key updates (backport from 0.2.8.1-alpha):
11751 - Update the V3 identity key for the dannenberg directory authority:
11752 it was changed on 18 November 2015. Closes task 17906. Patch
11755 o Major bugfixes (parsing, security, backport from 0.2.9.8):
11756 - Fix a bug in parsing that could cause clients to read a single
11757 byte past the end of an allocated region. This bug could be used
11758 to cause hardened clients (built with --enable-expensive-hardening)
11759 to crash if they tried to visit a hostile hidden service. Non-
11760 hardened clients are only affected depending on the details of
11761 their platform's memory allocator. Fixes bug 21018; bugfix on
11762 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
11763 2016-12-002 and as CVE-2016-1254.
11765 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
11766 - Stop a crash that could occur when a client running with DNSPort
11767 received a query with multiple address types, and the first
11768 address type was not supported. Found and fixed by Scott Dial.
11769 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
11770 - Prevent a class of security bugs caused by treating the contents
11771 of a buffer chunk as if they were a NUL-terminated string. At
11772 least one such bug seems to be present in all currently used
11773 versions of Tor, and would allow an attacker to remotely crash
11774 most Tor instances, especially those compiled with extra compiler
11775 hardening. With this defense in place, such bugs can't crash Tor,
11776 though we should still fix them as they occur. Closes ticket
11777 20384 (TROVE-2016-10-001).
11779 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
11780 - Avoid a difficult-to-trigger heap corruption attack when extending
11781 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
11782 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
11783 Reported by Guido Vranken.
11785 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
11786 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
11787 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
11789 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
11790 - If OpenSSL fails to generate an RSA key, do not retain a dangling
11791 pointer to the previous (uninitialized) key value. The impact here
11792 should be limited to a difficult-to-trigger crash, if OpenSSL is
11793 running an engine that makes key generation failures possible, or
11794 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
11795 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
11798 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
11799 - Fix an integer underflow bug when comparing malformed Tor
11800 versions. This bug could crash Tor when built with
11801 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
11802 0.2.9.8, which were built with -ftrapv by default. In other cases
11803 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
11804 on 0.0.8pre1. Found by OSS-Fuzz.
11806 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
11807 - Make memwipe() do nothing when passed a NULL pointer or buffer of
11808 zero size. Check size argument to memwipe() for underflow. Fixes
11809 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
11812 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
11813 - Make Tor survive errors involving connections without a
11814 corresponding event object. Previously we'd fail with an
11815 assertion; now we produce a log message. Related to bug 16248.
11817 o Minor features (geoip):
11818 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
11822 Changes in version 0.2.6.11 - 2017-03-03
11823 Tor 0.2.6.11 backports a number of security fixes from later Tor
11824 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
11825 this release, if for some reason they cannot upgrade to a later
11828 Note that support for Tor 0.2.6.x is ending this year: we will not issue
11829 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
11830 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
11832 o Directory authority changes (backport from 0.2.8.5-rc):
11833 - Urras is no longer a directory authority. Closes ticket 19271.
11835 o Directory authority changes (backport from 0.2.9.2-alpha):
11836 - The "Tonga" bridge authority has been retired; the new bridge
11837 authority is "Bifroest". Closes tickets 19728 and 19690.
11839 o Directory authority key updates (backport from 0.2.8.1-alpha):
11840 - Update the V3 identity key for the dannenberg directory authority:
11841 it was changed on 18 November 2015. Closes task 17906. Patch
11844 o Major features (security fixes, backport from 0.2.9.4-alpha):
11845 - Prevent a class of security bugs caused by treating the contents
11846 of a buffer chunk as if they were a NUL-terminated string. At
11847 least one such bug seems to be present in all currently used
11848 versions of Tor, and would allow an attacker to remotely crash
11849 most Tor instances, especially those compiled with extra compiler
11850 hardening. With this defense in place, such bugs can't crash Tor,
11851 though we should still fix them as they occur. Closes ticket
11852 20384 (TROVE-2016-10-001).
11854 o Major bugfixes (parsing, security, backport from 0.2.9.8):
11855 - Fix a bug in parsing that could cause clients to read a single
11856 byte past the end of an allocated region. This bug could be used
11857 to cause hardened clients (built with --enable-expensive-hardening)
11858 to crash if they tried to visit a hostile hidden service. Non-
11859 hardened clients are only affected depending on the details of
11860 their platform's memory allocator. Fixes bug 21018; bugfix on
11861 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
11862 2016-12-002 and as CVE-2016-1254.
11864 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
11865 - Stop a crash that could occur when a client running with DNSPort
11866 received a query with multiple address types, and the first
11867 address type was not supported. Found and fixed by Scott Dial.
11868 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
11870 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
11871 - Fix an error that could cause us to read 4 bytes before the
11872 beginning of an openssl string. This bug could be used to cause
11873 Tor to crash on systems with unusual malloc implementations, or
11874 systems with unusual hardening installed. Fixes bug 17404; bugfix
11877 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
11878 - Avoid a difficult-to-trigger heap corruption attack when extending
11879 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
11880 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
11881 Reported by Guido Vranken.
11883 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
11884 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
11885 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
11887 o Major bugfixes (guard selection, backport from 0.2.7.6):
11888 - Actually look at the Guard flag when selecting a new directory
11889 guard. When we implemented the directory guard design, we
11890 accidentally started treating all relays as if they have the Guard
11891 flag during guard selection, leading to weaker anonymity and worse
11892 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
11895 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
11896 - If OpenSSL fails to generate an RSA key, do not retain a dangling
11897 pointer to the previous (uninitialized) key value. The impact here
11898 should be limited to a difficult-to-trigger crash, if OpenSSL is
11899 running an engine that makes key generation failures possible, or
11900 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
11901 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
11904 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
11905 - Fix an integer underflow bug when comparing malformed Tor
11906 versions. This bug could crash Tor when built with
11907 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
11908 0.2.9.8, which were built with -ftrapv by default. In other cases
11909 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
11910 on 0.0.8pre1. Found by OSS-Fuzz.
11912 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
11913 - Make memwipe() do nothing when passed a NULL pointer or buffer of
11914 zero size. Check size argument to memwipe() for underflow. Fixes
11915 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
11918 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
11919 - Make Tor survive errors involving connections without a
11920 corresponding event object. Previously we'd fail with an
11921 assertion; now we produce a log message. Related to bug 16248.
11923 o Minor features (geoip):
11924 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
11927 o Minor bugfixes (compilation, backport from 0.2.7.6):
11928 - Fix a compilation warning with Clang 3.6: Do not check the
11929 presence of an address which can never be NULL. Fixes bug 17781.
11932 Changes in version 0.2.5.13 - 2017-03-03
11933 Tor 0.2.5.13 backports a number of security fixes from later Tor
11934 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
11935 this release, if for some reason they cannot upgrade to a later
11938 Note that support for Tor 0.2.5.x is ending next year: we will not issue
11939 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
11940 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
11942 o Directory authority changes (backport from 0.2.8.5-rc):
11943 - Urras is no longer a directory authority. Closes ticket 19271.
11945 o Directory authority changes (backport from 0.2.9.2-alpha):
11946 - The "Tonga" bridge authority has been retired; the new bridge
11947 authority is "Bifroest". Closes tickets 19728 and 19690.
11949 o Directory authority key updates (backport from 0.2.8.1-alpha):
11950 - Update the V3 identity key for the dannenberg directory authority:
11951 it was changed on 18 November 2015. Closes task 17906. Patch
11954 o Major features (security fixes, backport from 0.2.9.4-alpha):
11955 - Prevent a class of security bugs caused by treating the contents
11956 of a buffer chunk as if they were a NUL-terminated string. At
11957 least one such bug seems to be present in all currently used
11958 versions of Tor, and would allow an attacker to remotely crash
11959 most Tor instances, especially those compiled with extra compiler
11960 hardening. With this defense in place, such bugs can't crash Tor,
11961 though we should still fix them as they occur. Closes ticket
11962 20384 (TROVE-2016-10-001).
11964 o Major bugfixes (parsing, security, backport from 0.2.9.8):
11965 - Fix a bug in parsing that could cause clients to read a single
11966 byte past the end of an allocated region. This bug could be used
11967 to cause hardened clients (built with --enable-expensive-hardening)
11968 to crash if they tried to visit a hostile hidden service. Non-
11969 hardened clients are only affected depending on the details of
11970 their platform's memory allocator. Fixes bug 21018; bugfix on
11971 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
11972 2016-12-002 and as CVE-2016-1254.
11974 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
11975 - Stop a crash that could occur when a client running with DNSPort
11976 received a query with multiple address types, and the first
11977 address type was not supported. Found and fixed by Scott Dial.
11978 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
11980 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
11981 - Fix an error that could cause us to read 4 bytes before the
11982 beginning of an openssl string. This bug could be used to cause
11983 Tor to crash on systems with unusual malloc implementations, or
11984 systems with unusual hardening installed. Fixes bug 17404; bugfix
11987 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
11988 - Avoid a difficult-to-trigger heap corruption attack when extending
11989 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
11990 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
11991 Reported by Guido Vranken.
11993 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
11994 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
11995 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
11997 o Major bugfixes (guard selection, backport from 0.2.7.6):
11998 - Actually look at the Guard flag when selecting a new directory
11999 guard. When we implemented the directory guard design, we
12000 accidentally started treating all relays as if they have the Guard
12001 flag during guard selection, leading to weaker anonymity and worse
12002 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
12005 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
12006 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12007 pointer to the previous (uninitialized) key value. The impact here
12008 should be limited to a difficult-to-trigger crash, if OpenSSL is
12009 running an engine that makes key generation failures possible, or
12010 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12011 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12014 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12015 - Fix an integer underflow bug when comparing malformed Tor
12016 versions. This bug could crash Tor when built with
12017 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12018 0.2.9.8, which were built with -ftrapv by default. In other cases
12019 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12020 on 0.0.8pre1. Found by OSS-Fuzz.
12022 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
12023 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12024 zero size. Check size argument to memwipe() for underflow. Fixes
12025 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12028 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
12029 - Make Tor survive errors involving connections without a
12030 corresponding event object. Previously we'd fail with an
12031 assertion; now we produce a log message. Related to bug 16248.
12033 o Minor features (geoip):
12034 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12037 o Minor bugfixes (compilation, backport from 0.2.7.6):
12038 - Fix a compilation warning with Clang 3.6: Do not check the
12039 presence of an address which can never be NULL. Fixes bug 17781.
12041 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
12042 - Check for failures from crypto_early_init, and refuse to continue.
12043 A previous typo meant that we could keep going with an
12044 uninitialized crypto library, and would have OpenSSL initialize
12045 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
12046 when implementing ticket 4900. Patch by "teor".
12048 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
12049 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
12050 a client authorized hidden service. Fixes bug 15823; bugfix
12054 Changes in version 0.2.4.28 - 2017-03-03
12055 Tor 0.2.4.28 backports a number of security fixes from later Tor
12056 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
12057 this release, if for some reason they cannot upgrade to a later
12060 Note that support for Tor 0.2.4.x is ending soon: we will not issue
12061 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
12062 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
12064 o Directory authority changes (backport from 0.2.8.5-rc):
12065 - Urras is no longer a directory authority. Closes ticket 19271.
12067 o Directory authority changes (backport from 0.2.9.2-alpha):
12068 - The "Tonga" bridge authority has been retired; the new bridge
12069 authority is "Bifroest". Closes tickets 19728 and 19690.
12071 o Directory authority key updates (backport from 0.2.8.1-alpha):
12072 - Update the V3 identity key for the dannenberg directory authority:
12073 it was changed on 18 November 2015. Closes task 17906. Patch
12076 o Major features (security fixes, backport from 0.2.9.4-alpha):
12077 - Prevent a class of security bugs caused by treating the contents
12078 of a buffer chunk as if they were a NUL-terminated string. At
12079 least one such bug seems to be present in all currently used
12080 versions of Tor, and would allow an attacker to remotely crash
12081 most Tor instances, especially those compiled with extra compiler
12082 hardening. With this defense in place, such bugs can't crash Tor,
12083 though we should still fix them as they occur. Closes ticket
12084 20384 (TROVE-2016-10-001).
12086 o Major bugfixes (parsing, security, backport from 0.2.9.8):
12087 - Fix a bug in parsing that could cause clients to read a single
12088 byte past the end of an allocated region. This bug could be used
12089 to cause hardened clients (built with --enable-expensive-hardening)
12090 to crash if they tried to visit a hostile hidden service. Non-
12091 hardened clients are only affected depending on the details of
12092 their platform's memory allocator. Fixes bug 21018; bugfix on
12093 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12094 2016-12-002 and as CVE-2016-1254.
12096 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
12097 - Fix an error that could cause us to read 4 bytes before the
12098 beginning of an openssl string. This bug could be used to cause
12099 Tor to crash on systems with unusual malloc implementations, or
12100 systems with unusual hardening installed. Fixes bug 17404; bugfix
12103 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
12104 - Avoid a difficult-to-trigger heap corruption attack when extending
12105 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12106 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12107 Reported by Guido Vranken.
12109 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
12110 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12111 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12113 o Major bugfixes (guard selection, backport from 0.2.7.6):
12114 - Actually look at the Guard flag when selecting a new directory
12115 guard. When we implemented the directory guard design, we
12116 accidentally started treating all relays as if they have the Guard
12117 flag during guard selection, leading to weaker anonymity and worse
12118 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
12121 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
12122 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12123 pointer to the previous (uninitialized) key value. The impact here
12124 should be limited to a difficult-to-trigger crash, if OpenSSL is
12125 running an engine that makes key generation failures possible, or
12126 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12127 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12130 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12131 - Fix an integer underflow bug when comparing malformed Tor
12132 versions. This bug could crash Tor when built with
12133 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12134 0.2.9.8, which were built with -ftrapv by default. In other cases
12135 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12136 on 0.0.8pre1. Found by OSS-Fuzz.
12138 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
12139 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12140 zero size. Check size argument to memwipe() for underflow. Fixes
12141 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12144 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
12145 - Make Tor survive errors involving connections without a
12146 corresponding event object. Previously we'd fail with an
12147 assertion; now we produce a log message. Related to bug 16248.
12149 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
12150 - Make it harder for attackers to overload hidden services with
12151 introductions, by blocking multiple introduction requests on the
12152 same circuit. Resolves ticket 15515.
12154 o Minor features (geoip):
12155 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12158 o Minor bugfixes (compilation, backport from 0.2.7.6):
12159 - Fix a compilation warning with Clang 3.6: Do not check the
12160 presence of an address which can never be NULL. Fixes bug 17781.
12162 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
12163 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
12164 a client authorized hidden service. Fixes bug 15823; bugfix
12168 Changes in version 0.2.9.10 - 2017-03-01
12169 Tor 0.2.9.10 backports a security fix from later Tor release. It also
12170 includes fixes for some major issues affecting directory authorities,
12171 LibreSSL compatibility, and IPv6 correctness.
12173 The Tor 0.2.9.x release series is now marked as a long-term-support
12174 series. We intend to backport security fixes to 0.2.9.x until at
12175 least January of 2020.
12177 o Major bugfixes (directory authority, 0.3.0.3-alpha):
12178 - During voting, when marking a relay as a probable sybil, do not
12179 clear its BadExit flag: sybils can still be bad in other ways
12180 too. (We still clear the other flags.) Fixes bug 21108; bugfix
12183 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
12184 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
12185 any IPv6 addresses. Instead, only reject a port over IPv6 if the
12186 exit policy rejects that port on more than an IPv6 /16 of
12187 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
12188 which rejected a relay's own IPv6 address by default. Fixes bug
12189 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
12191 o Major bugfixes (parsing, also in 0.3.0.4-rc):
12192 - Fix an integer underflow bug when comparing malformed Tor
12193 versions. This bug could crash Tor when built with
12194 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12195 0.2.9.8, which were built with -ftrapv by default. In other cases
12196 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12197 on 0.0.8pre1. Found by OSS-Fuzz.
12199 o Minor features (directory authorities, also in 0.3.0.4-rc):
12200 - Directory authorities now reject descriptors that claim to be
12201 malformed versions of Tor. Helps prevent exploitation of
12203 - Reject version numbers with components that exceed INT32_MAX.
12204 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
12205 Fixes bug 21450; bugfix on 0.0.8pre1.
12207 o Minor features (geoip):
12208 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12211 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
12212 - Autoconf now checks to determine if OpenSSL structures are opaque,
12213 instead of explicitly checking for OpenSSL version numbers. Part
12215 - Support building with recent LibreSSL code that uses opaque
12216 structures. Closes ticket 21359.
12218 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
12219 - Repair a couple of (unreachable or harmless) cases of the risky
12220 comparison-by-subtraction pattern that caused bug 21278.
12222 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
12223 - The tor-resolve command line tool now rejects hostnames over 255
12224 characters in length. Previously, it would silently truncate them,
12225 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
12226 Patch by "junglefowl".
12229 Changes in version 0.2.9.9 - 2017-01-23
12230 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
12231 cause relays and clients to crash, even if they were not built with
12232 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
12233 versions, and also affects 0.3.0.1-alpha: all relays running an affected
12234 version should upgrade.
12236 This release also resolves a client-side onion service reachability
12237 bug, and resolves a pair of small portability issues.
12239 o Major bugfixes (security):
12240 - Downgrade the "-ftrapv" option from "always on" to "only on when
12241 --enable-expensive-hardening is provided." This hardening option,
12242 like others, can turn survivable bugs into crashes -- and having
12243 it on by default made a (relatively harmless) integer overflow bug
12244 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
12245 bugfix on 0.2.9.1-alpha.
12247 o Major bugfixes (client, onion service):
12248 - Fix a client-side onion service reachability bug, where multiple
12249 socks requests to an onion service (or a single slow request)
12250 could cause us to mistakenly mark some of the service's
12251 introduction points as failed, and we cache that failure so
12252 eventually we run out and can't reach the service. Also resolves a
12253 mysterious "Remote server sent bogus reason code 65021" log
12254 warning. The bug was introduced in ticket 17218, where we tried to
12255 remember the circuit end reason as a uint16_t, which mangled
12256 negative values. Partially fixes bug 21056 and fixes bug 20307;
12257 bugfix on 0.2.8.1-alpha.
12259 o Minor features (geoip):
12260 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
12263 o Minor bugfixes (portability):
12264 - Avoid crashing when Tor is built using headers that contain
12265 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
12266 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
12268 - Fix Libevent detection on platforms without Libevent 1 headers
12269 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
12272 Changes in version 0.2.8.12 - 2016-12-19
12273 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
12274 below) where Tor clients could crash when attempting to visit a
12275 hostile hidden service. Clients are recommended to upgrade as packages
12276 become available for their systems.
12278 It also includes an updated list of fallback directories, backported
12281 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
12282 backported to 0.2.8 in the future.
12284 o Major bugfixes (parsing, security, backported from 0.2.9.8):
12285 - Fix a bug in parsing that could cause clients to read a single
12286 byte past the end of an allocated region. This bug could be used
12287 to cause hardened clients (built with --enable-expensive-hardening)
12288 to crash if they tried to visit a hostile hidden service. Non-
12289 hardened clients are only affected depending on the details of
12290 their platform's memory allocator. Fixes bug 21018; bugfix on
12291 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12292 2016-12-002 and as CVE-2016-1254.
12294 o Minor features (fallback directory list, backported from 0.2.9.8):
12295 - Replace the 81 remaining fallbacks of the 100 originally
12296 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
12297 fallbacks (123 new, 54 existing, 27 removed) generated in December
12298 2016. Resolves ticket 20170.
12300 o Minor features (geoip, backported from 0.2.9.7-rc):
12301 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
12305 Changes in version 0.2.9.8 - 2016-12-19
12306 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
12308 The Tor 0.2.9 series makes mandatory a number of security features
12309 that were formerly optional. It includes support for a new shared-
12310 randomness protocol that will form the basis for next generation
12311 hidden services, includes a single-hop hidden service mode for
12312 optimizing .onion services that don't actually want to be hidden,
12313 tries harder not to overload the directory authorities with excessive
12314 downloads, and supports a better protocol versioning scheme for
12315 improved compatibility with other implementations of the Tor protocol.
12317 And of course, there are numerous other bugfixes and improvements.
12319 This release also includes a fix for a medium-severity issue (bug
12320 21018 below) where Tor clients could crash when attempting to visit a
12321 hostile hidden service. Clients are recommended to upgrade as packages
12322 become available for their systems.
12324 Below are listed the changes since Tor 0.2.8.11. For a list of
12325 changes since 0.2.9.7-rc, see the ChangeLog file.
12327 o New system requirements:
12328 - When building with OpenSSL, Tor now requires version 1.0.1 or
12329 later. OpenSSL 1.0.0 and earlier are no longer supported by the
12330 OpenSSL team, and should not be used. Closes ticket 20303.
12331 - Tor now requires Libevent version 2.0.10-stable or later. Older
12332 versions of Libevent have less efficient backends for several
12333 platforms, and lack the DNS code that we use for our server-side
12334 DNS support. This implements ticket 19554.
12335 - Tor now requires zlib version 1.2 or later, for security,
12336 efficiency, and (eventually) gzip support. (Back when we started,
12337 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
12338 released in 2003. We recommend the latest version.)
12340 o Deprecated features:
12341 - A number of DNS-cache-related sub-options for client ports are now
12342 deprecated for security reasons, and may be removed in a future
12343 version of Tor. (We believe that client-side DNS caching is a bad
12344 idea for anonymity, and you should not turn it on.) The options
12345 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
12346 UseIPv4Cache, and UseIPv6Cache.
12347 - A number of options are deprecated for security reasons, and may
12348 be removed in a future version of Tor. The options are:
12349 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
12350 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
12351 CloseHSClientCircuitsImmediatelyOnTimeout,
12352 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
12353 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
12354 UseNTorHandshake, and WarnUnsafeSocks.
12355 - The *ListenAddress options are now deprecated as unnecessary: the
12356 corresponding *Port options should be used instead. These options
12357 may someday be removed. The affected options are:
12358 ControlListenAddress, DNSListenAddress, DirListenAddress,
12359 NATDListenAddress, ORListenAddress, SocksListenAddress,
12360 and TransListenAddress.
12362 o Major bugfixes (parsing, security, new since 0.2.9.7-rc):
12363 - Fix a bug in parsing that could cause clients to read a single
12364 byte past the end of an allocated region. This bug could be used
12365 to cause hardened clients (built with --enable-expensive-hardening)
12366 to crash if they tried to visit a hostile hidden service. Non-
12367 hardened clients are only affected depending on the details of
12368 their platform's memory allocator. Fixes bug 21018; bugfix on
12369 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12370 2016-12-002 and as CVE-2016-1254.
12372 o Major features (build, hardening):
12373 - Tor now builds with -ftrapv by default on compilers that support
12374 it. This option detects signed integer overflow (which C forbids),
12375 and turns it into a hard-failure. We do not apply this option to
12376 code that needs to run in constant time to avoid side-channels;
12377 instead, we use -fwrapv in that code. Closes ticket 17983.
12378 - When --enable-expensive-hardening is selected, stop applying the
12379 clang/gcc sanitizers to code that needs to run in constant time.
12380 Although we are aware of no introduced side-channels, we are not
12381 able to prove that there are none. Related to ticket 17983.
12383 o Major features (circuit building, security):
12384 - Authorities, relays, and clients now require ntor keys in all
12385 descriptors, for all hops (except for rare hidden service protocol
12386 cases), for all circuits, and for all other roles. Part of
12388 - Authorities, relays, and clients only use ntor, except for
12389 rare cases in the hidden service protocol. Part of ticket 19163.
12391 o Major features (compilation):
12392 - Our big list of extra GCC warnings is now enabled by default when
12393 building with GCC (or with anything like Clang that claims to be
12394 GCC-compatible). To make all warnings into fatal compilation
12395 errors, pass --enable-fatal-warnings to configure. Closes
12397 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
12398 turn on C and POSIX extensions. (Previously, we attempted to do
12399 this on an ad hoc basis.) Closes ticket 19139.
12401 o Major features (directory authorities, hidden services):
12402 - Directory authorities can now perform the shared randomness
12403 protocol specified by proposal 250. Using this protocol, directory
12404 authorities generate a global fresh random value every day. In the
12405 future, this value will be used by hidden services to select
12406 HSDirs. This release implements the directory authority feature;
12407 the hidden service side will be implemented in the future as part
12408 of proposal 224. Resolves ticket 16943; implements proposal 250.
12410 o Major features (downloading, random exponential backoff):
12411 - When we fail to download an object from a directory service, wait
12412 for an (exponentially increasing) randomized amount of time before
12413 retrying, rather than a fixed interval as we did before. This
12414 prevents a group of Tor instances from becoming too synchronized,
12415 or a single Tor instance from becoming too predictable, in its
12416 download schedule. Closes ticket 15942.
12418 o Major features (resource management):
12419 - Tor can now notice it is about to run out of sockets, and
12420 preemptively close connections of lower priority. (This feature is
12421 off by default for now, since the current prioritizing method is
12422 yet not mature enough. You can enable it by setting
12423 "DisableOOSCheck 0", but watch out: it might close some sockets
12424 you would rather have it keep.) Closes ticket 18640.
12426 o Major features (single-hop "hidden" services):
12427 - Add experimental HiddenServiceSingleHopMode and
12428 HiddenServiceNonAnonymousMode options. When both are set to 1,
12429 every hidden service on that Tor instance becomes a non-anonymous
12430 Single Onion Service. Single Onions make one-hop (direct)
12431 connections to their introduction and rendezvous points. One-hop
12432 circuits make Single Onion servers easily locatable, but clients
12433 remain location-anonymous. This is compatible with the existing
12434 hidden service implementation, and works on the current Tor
12435 network without any changes to older relays or clients. Implements
12436 proposal 260, completes ticket 17178. Patch by teor and asn.
12438 o Major features (subprotocol versions):
12439 - Tor directory authorities now vote on a set of recommended
12440 "subprotocol versions", and on a set of required subprotocol
12441 versions. Clients and relays that lack support for a _required_
12442 subprotocol version will not start; those that lack support for a
12443 _recommended_ subprotocol version will warn the user to upgrade.
12444 This change allows compatible implementations of the Tor protocol(s)
12445 to exist without pretending to be 100% bug-compatible with
12446 particular releases of Tor itself. Closes ticket 19958; implements
12447 part of proposal 264.
12449 o Major bugfixes (circuit building):
12450 - Hidden service client-to-intro-point and service-to-rendezvous-
12451 point circuits use the TAP key supplied by the protocol, to avoid
12452 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
12454 o Major bugfixes (download scheduling):
12455 - Avoid resetting download status for consensuses hourly, since we
12456 already have another, smarter retry mechanism. Fixes bug 8625;
12457 bugfix on 0.2.0.9-alpha.
12458 - If a consensus expires while we are waiting for certificates to
12459 download, stop waiting for certificates.
12460 - If we stop waiting for certificates less than a minute after we
12461 started downloading them, do not consider the certificate download
12462 failure a separate failure. Fixes bug 20533; bugfix
12464 - When using exponential backoff in test networks, use a lower
12465 exponent, so the delays do not vary as much. This helps test
12466 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
12468 o Major bugfixes (exit policies):
12469 - Avoid disclosing exit outbound bind addresses, configured port
12470 bind addresses, and local interface addresses in relay descriptors
12471 by default under ExitPolicyRejectPrivate. Instead, only reject
12472 these (otherwise unlisted) addresses if
12473 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
12474 0.2.7.2-alpha. Patch by teor.
12476 o Major bugfixes (hidden services):
12477 - Allow Tor clients with appropriate controllers to work with
12478 FetchHidServDescriptors set to 0. Previously, this option also
12479 disabled descriptor cache lookup, thus breaking hidden services
12480 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
12481 - Clients now require hidden services to include the TAP keys for
12482 their intro points in the hidden service descriptor. This prevents
12483 an inadvertent upgrade to ntor, which a malicious hidden service
12484 could use to distinguish clients by consensus version. Fixes bug
12485 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
12487 o Major bugfixes (relay, resolver, logging):
12488 - For relays that don't know their own address, avoid attempting a
12489 local hostname resolve for each descriptor we download. This
12490 will cut down on the number of "Success: chose address 'x.x.x.x'"
12491 log lines, and also avoid confusing clock jumps if the resolver
12492 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
12494 o Minor features (port flags):
12495 - Add new flags to the *Port options to give finer control over which
12496 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
12497 and the synthetic flag OnionTrafficOnly, which is equivalent to
12498 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
12499 18693; patch by "teor".
12501 o Minor features (build, hardening):
12502 - Detect and work around a libclang_rt problem that would prevent
12503 clang from finding __mulodi4() on some 32-bit platforms, and thus
12504 keep -ftrapv from linking on those systems. Closes ticket 19079.
12505 - When building on a system without runtime support for the runtime
12506 hardening options, try to log a useful warning at configuration
12507 time, rather than an incomprehensible warning at link time. If
12508 expensive hardening was requested, this warning becomes an error.
12509 Closes ticket 18895.
12511 o Minor features (client, directory):
12512 - Since authorities now omit all routers that lack the Running and
12513 Valid flags, we assume that any relay listed in the consensus must
12514 have those flags. Closes ticket 20001; implements part of
12517 o Minor features (code safety):
12518 - In our integer-parsing functions, ensure that the maximum value we
12519 allow is no smaller than the minimum value. Closes ticket 19063;
12520 patch from "U+039b".
12522 o Minor features (compilation, portability):
12523 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
12526 o Minor features (config):
12527 - Warn users when descriptor and port addresses are inconsistent.
12528 Mitigates bug 13953; patch by teor.
12530 o Minor features (controller):
12531 - Allow controllers to configure basic client authorization on
12532 hidden services when they create them with the ADD_ONION controller
12533 command. Implements ticket 15588. Patch by "special".
12534 - Fire a STATUS_SERVER controller event whenever the hibernation
12535 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
12536 - Implement new GETINFO queries for all downloads that use
12537 download_status_t to schedule retries. This allows controllers to
12538 examine the schedule for pending downloads. Closes ticket 19323.
12540 o Minor features (development tools, etags):
12541 - Teach the "make tags" Makefile target how to correctly find
12542 "MOCK_IMPL" function definitions. Patch from nherring; closes
12545 o Minor features (directory authority):
12546 - After voting, if the authorities decide that a relay is not
12547 "Valid", they no longer include it in the consensus at all. Closes
12548 ticket 20002; implements part of proposal 272.
12549 - Directory authorities now only give the Guard flag to a relay if
12550 they are also giving it the Stable flag. This change allows us to
12551 simplify path selection for clients. It should have minimal effect
12552 in practice, since >99% of Guards already have the Stable flag.
12553 Implements ticket 18624.
12554 - Directory authorities now write their v3-status-votes file out to
12555 disk earlier in the consensus process, so we have a record of the
12556 votes even if we abort the consensus process. Resolves
12559 o Minor features (fallback directory list, new since 0.2.9.7-rc):
12560 - Replace the 81 remaining fallbacks of the 100 originally
12561 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
12562 fallbacks (123 new, 54 existing, 27 removed) generated in December
12563 2016. Resolves ticket 20170.
12565 o Minor features (hidden service):
12566 - Stop being so strict about the payload length of "rendezvous1"
12567 cells. We used to be locked in to the "TAP" handshake length, and
12568 now we can handle better handshakes like "ntor". Resolves
12571 o Minor features (infrastructure, time):
12572 - Tor now includes an improved timer backend, so that we can
12573 efficiently support tens or hundreds of thousands of concurrent
12574 timers, as will be needed for some of our planned anti-traffic-
12575 analysis work. This code is based on William Ahern's "timeout.c"
12576 project, which implements a "tickless hierarchical timing wheel".
12577 Closes ticket 18365.
12578 - Tor now uses the operating system's monotonic timers (where
12579 available) for internal fine-grained timing. Previously we would
12580 look at the system clock, and then attempt to compensate for the
12581 clock running backwards. Closes ticket 18908.
12583 o Minor features (logging):
12584 - Add a set of macros to check nonfatal assertions, for internal
12585 use. Migrating more of our checks to these should help us avoid
12586 needless crash bugs. Closes ticket 18613.
12587 - Provide a more useful warning message when configured with an
12588 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
12589 - When dumping unparseable router descriptors, optionally store them
12590 in separate files, named by digest, up to a configurable size
12591 limit. You can change the size limit by setting the
12592 MaxUnparseableDescSizeToLog option, and disable this feature by
12593 setting that option to 0. Closes ticket 18322.
12595 o Minor features (performance):
12596 - Change the "optimistic data" extension from "off by default" to
12597 "on by default". The default was ordinarily overridden by a
12598 consensus option, but when clients were bootstrapping for the
12599 first time, they would not have a consensus to get the option
12600 from. Changing this default saves a round-trip during startup.
12601 Closes ticket 18815.
12603 o Minor features (relay, usability):
12604 - When the directory authorities refuse a bad relay's descriptor,
12605 encourage the relay operator to contact us. Many relay operators
12606 won't notice this line in their logs, but it's a win if even a few
12607 learn why we don't like what their relay was doing. Resolves
12610 o Minor features (security, TLS):
12611 - Servers no longer support clients that lack AES ciphersuites.
12612 (3DES is no longer considered an acceptable cipher.) We believe
12613 that no such Tor clients currently exist, since Tor has required
12614 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
12616 o Minor features (testing):
12617 - Disable memory protections on OpenBSD when performing our unit
12618 tests for memwipe(). The test deliberately invokes undefined
12619 behavior, and the OpenBSD protections interfere with this. Patch
12620 from "rubiate". Closes ticket 20066.
12621 - Move the test-network.sh script to chutney, and modify tor's test-
12622 network.sh to call the (newer) chutney version when available.
12623 Resolves ticket 19116. Patch by teor.
12624 - Use the lcov convention for marking lines as unreachable, so that
12625 we don't count them when we're generating test coverage data.
12626 Update our coverage tools to understand this convention. Closes
12628 - Our link-handshake unit tests now check that when invalid
12629 handshakes fail, they fail with the error messages we expected.
12630 - Our unit testing code that captures log messages no longer
12631 prevents them from being written out if the user asked for them
12632 (by passing --debug or --info or --notice or --warn to the "test"
12633 binary). This change prevents us from missing unexpected log
12634 messages simply because we were looking for others. Related to
12636 - The unit tests now log all warning messages with the "BUG" flag.
12637 Previously, they only logged errors by default. This change will
12638 help us make our testing code more correct, and make sure that we
12639 only hit this code when we mean to. In the meantime, however,
12640 there will be more warnings in the unit test logs than before.
12641 This is preparatory work for ticket 19999.
12642 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
12643 assertion as a test failure.
12644 - We've done significant work to make the unit tests run faster.
12646 o Minor features (testing, ipv6):
12647 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
12648 tests. Remove bridges+hs, as it's somewhat redundant. This
12649 requires a recent chutney version that supports IPv6 clients,
12650 relays, and authorities. Closes ticket 20069; patch by teor.
12651 - Add the single-onion and single-onion-ipv6 chutney targets to
12652 "make test-network-all". This requires a recent chutney version
12653 with the single onion network flavors (git c72a652 or later).
12654 Closes ticket 20072; patch by teor.
12656 o Minor features (Tor2web):
12657 - Make Tor2web clients respect ReachableAddresses. This feature was
12658 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
12659 0.2.8.7. Implements feature 20034. Patch by teor.
12661 o Minor features (unix domain sockets):
12662 - When configuring a unix domain socket for a SocksPort,
12663 ControlPort, or Hidden service, you can now wrap the address in
12664 quotes, using C-style escapes inside the quotes. This allows unix
12665 domain socket paths to contain spaces. Resolves ticket 18753.
12667 o Minor features (user interface):
12668 - Tor now supports the ability to declare options deprecated, so
12669 that we can recommend that people stop using them. Previously, this
12670 was done in an ad-hoc way. There is a new --list-deprecated-options
12671 command-line option to list all of the deprecated options. Closes
12674 o Minor features (virtual addresses):
12675 - Increase the maximum number of bits for the IPv6 virtual network
12676 prefix from 16 to 104. In this way, the condition for address
12677 allocation is less restrictive. Closes ticket 20151; feature
12680 o Minor bug fixes (circuits):
12681 - Use the CircuitBuildTimeout option whenever
12682 LearnCircuitBuildTimeout is disabled. Previously, we would respect
12683 the option when a user disabled it, but not when it was disabled
12684 because some other option was set. Fixes bug 20073; bugfix on
12685 0.2.4.12-alpha. Patch by teor.
12687 o Minor bugfixes (build):
12688 - The current Git revision when building from a local repository is
12689 now detected correctly when using git worktrees. Fixes bug 20492;
12690 bugfix on 0.2.3.9-alpha.
12692 o Minor bugfixes (relay address discovery):
12693 - Stop reordering IP addresses returned by the OS. This makes it
12694 more likely that Tor will guess the same relay IP address every
12695 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
12696 Reported by René Mayrhofer, patch by "cypherpunks".
12698 o Minor bugfixes (memory allocation):
12699 - Change how we allocate memory for large chunks on buffers, to
12700 avoid a (currently impossible) integer overflow, and to waste less
12701 space when allocating unusually large chunks. Fixes bug 20081;
12702 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
12704 o Minor bugfixes (bootstrap):
12705 - Remember the directory server we fetched the consensus or previous
12706 certificates from, and use it to fetch future authority
12707 certificates. This change improves bootstrapping performance.
12708 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
12710 o Minor bugfixes (circuits):
12711 - Make sure extend_info_from_router() is only called on servers.
12712 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
12714 o Minor bugfixes (client, fascistfirewall):
12715 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
12716 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
12718 o Minor bugfixes (client, unix domain sockets):
12719 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
12720 the client address is meaningless. Fixes bug 20261; bugfix
12723 o Minor bugfixes (code style):
12724 - Fix an integer signedness conversion issue in the case conversion
12725 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
12727 o Minor bugfixes (compilation):
12728 - Build correctly on versions of libevent2 without support for
12729 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
12731 - When building with Clang, use a full set of GCC warnings.
12732 (Previously, we included only a subset, because of the way we
12733 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
12734 - Detect Libevent2 functions correctly on systems that provide
12735 libevent2, but where libevent1 is linked with -levent. Fixes bug
12736 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
12737 - Run correctly when built on Windows build environments that
12738 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
12740 o Minor bugfixes (configuration):
12741 - When parsing quoted configuration values from the torrc file,
12742 handle Windows line endings correctly. Fixes bug 19167; bugfix on
12743 0.2.0.16-alpha. Patch from "Pingl".
12745 o Minor bugfixes (directory authority):
12746 - Authorities now sort the "package" lines in their votes, for ease
12747 of debugging. (They are already sorted in consensus documents.)
12748 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
12749 - Die with a more useful error when the operator forgets to place
12750 the authority_signing_key file into the keys directory. This
12751 avoids an uninformative assert & traceback about having an invalid
12752 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
12753 - When allowing private addresses, mark Exits that only exit to
12754 private locations as such. Fixes bug 20064; bugfix
12756 - When parsing a detached signature, make sure we use the length of
12757 the digest algorithm instead of a hardcoded DIGEST256_LEN in
12758 order to avoid comparing bytes out-of-bounds with a smaller digest
12759 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
12761 o Minor bugfixes (getpass):
12762 - Defensively fix a non-triggerable heap corruption at do_getpass()
12763 to protect ourselves from mistakes in the future. Fixes bug
12764 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
12767 o Minor bugfixes (guard selection):
12768 - Don't mark guards as unreachable if connection_connect() fails.
12769 That function fails for local reasons, so it shouldn't reveal
12770 anything about the status of the guard. Fixes bug 14334; bugfix
12772 - Use a single entry guard even if the NumEntryGuards consensus
12773 parameter is not provided. Fixes bug 17688; bugfix
12776 o Minor bugfixes (hidden services):
12777 - Increase the minimum number of internal circuits we preemptively
12778 build from 2 to 3, so a circuit is available when a client
12779 connects to another onion service. Fixes bug 13239; bugfix
12781 - Allow hidden services to run on IPv6 addresses even when the
12782 IPv6Exit option is not set. Fixes bug 18357; bugfix
12784 - Stop logging intro point details to the client log on certain
12785 error conditions. Fixed as part of bug 20012; bugfix on
12786 0.2.4.8-alpha. Patch by teor.
12787 - When deleting an ephemeral hidden service, close its intro points
12788 even if they are not completely open. Fixes bug 18604; bugfix
12790 - When configuring hidden services, check every hidden service
12791 directory's permissions. Previously, we only checked the last
12792 hidden service. Fixes bug 20529; bugfix on 0.2.6.2-alpha.
12794 o Minor bugfixes (IPv6, testing):
12795 - Check for IPv6 correctly on Linux when running test networks.
12796 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
12798 o Minor bugfixes (Linux seccomp2 sandbox):
12799 - Add permission to run the sched_yield() and sigaltstack() system
12800 calls, in order to support versions of Tor compiled with asan or
12801 ubsan code that use these calls. Now "sandbox 1" and
12802 "--enable-expensive-hardening" should be compatible on more
12803 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
12805 o Minor bugfixes (logging):
12806 - Downgrade a harmless log message about the
12807 pending_entry_connections list from "warn" to "info". Mitigates
12809 - Log a more accurate message when we fail to dump a microdescriptor.
12810 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
12811 - When logging a directory ownership mismatch, log the owning
12812 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
12813 - When we are unable to remove the bw_accounting file, do not warn
12814 if the reason we couldn't remove it was that it didn't exist.
12815 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from pastly.
12817 o Minor bugfixes (memory leak):
12818 - Fix a series of slow memory leaks related to parsing torrc files
12819 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
12820 - Avoid a small memory leak when informing worker threads about
12821 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
12822 - Fix a small memory leak when receiving AF_UNIX connections on a
12823 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
12824 - When moving a signed descriptor object from a source to an
12825 existing destination, free the allocated memory inside that
12826 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
12827 - Fix a memory leak and use-after-free error when removing entries
12828 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
12829 0.2.5.5-alpha. Patch from "cypherpunks".
12830 - Fix a small, uncommon memory leak that could occur when reading a
12831 truncated ed25519 key file. Fixes bug 18956; bugfix
12834 o Minor bugfixes (option parsing):
12835 - Count unix sockets when counting client listeners (SOCKS, Trans,
12836 NATD, and DNS). This has no user-visible behavior changes: these
12837 options are set once, and never read. Required for correct
12838 behavior in ticket 17178. Fixes bug 19677; bugfix on
12839 0.2.6.3-alpha. Patch by teor.
12841 o Minor bugfixes (options):
12842 - Check the consistency of UseEntryGuards and EntryNodes more
12843 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
12845 - Stop changing the configured value of UseEntryGuards on
12846 authorities and Tor2web clients. Fixes bug 20074; bugfix on
12847 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
12850 o Minor bugfixes (relay):
12851 - Ensure relays don't make multiple connections during bootstrap.
12852 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
12853 - Do not try to parallelize workers more than 16x without the user
12854 explicitly configuring us to do so, even if we do detect more than
12855 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
12857 o Minor bugfixes (testing):
12858 - The test-stem and test-network makefile targets now depend only on
12859 the tor binary that they are testing. Previously, they depended on
12860 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
12861 patch from "cypherpunks".
12862 - Allow clients to retry HSDirs much faster in test networks. Fixes
12863 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
12864 - Avoid a unit test failure on systems with over 16 detectable CPU
12865 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
12866 - Let backtrace tests work correctly under AddressSanitizer:
12867 disable ASAN's detection of segmentation faults while running
12868 test_bt.sh, so that we can make sure that our own backtrace
12869 generation code works. Fixes bug 18934; bugfix
12870 on 0.2.5.2-alpha. Patch from "cypherpunks".
12871 - Fix the test-network-all target on out-of-tree builds by using the
12872 correct path to the test driver script. Fixes bug 19421; bugfix
12874 - Stop spurious failures in the local interface address discovery
12875 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
12877 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
12878 removed the ECDH ciphers which caused the tests to fail on
12879 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
12880 - The tor_tls_server_info_callback unit test no longer crashes when
12881 debug-level logging is turned on. Fixes bug 20041; bugfix
12884 o Minor bugfixes (time):
12885 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
12886 bugfix on all released tor versions.
12887 - When computing the difference between two times in milliseconds,
12888 we now round to the nearest millisecond correctly. Previously, we
12889 could sometimes round in the wrong direction. Fixes bug 19428;
12890 bugfix on 0.2.2.2-alpha.
12892 o Minor bugfixes (Tor2web):
12893 - Prevent Tor2web clients from running hidden services: these services
12894 are not anonymous due to the one-hop client paths. Fixes bug
12895 19678. Patch by teor.
12897 o Minor bugfixes (user interface):
12898 - Display a more accurate number of suppressed messages in the log
12899 rate-limiter. Previously, there was a potential integer overflow
12900 in the counter. Now, if the number of messages hits a maximum, the
12901 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
12903 - Fix a typo in the passphrase prompt for the ed25519 identity key.
12904 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
12906 o Code simplification and refactoring:
12907 - Remove redundant declarations of the MIN macro. Closes
12909 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
12910 Closes ticket 18462; patch from "icanhasaccount".
12911 - Split the 600-line directory_handle_command_get function into
12912 separate functions for different URL types. Closes ticket 16698.
12915 - Add module-level internal documentation for 36 C files that
12916 previously didn't have a high-level overview. Closes ticket 20385.
12917 - Correct the IPv6 syntax in our documentation for the
12918 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
12919 - Correct the minimum bandwidth value in torrc.sample, and queue a
12920 corresponding change for torrc.minimal. Closes ticket 20085.
12921 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
12922 ticket 19153. Patch from "U+039b".
12923 - Module-level documentation for several more modules. Closes
12924 tickets 19287 and 19290.
12925 - Document the --passphrase-fd option in the tor manpage. Fixes bug
12926 19504; bugfix on 0.2.7.3-rc.
12927 - Document the default PathsNeededToBuildCircuits value that's used
12928 by clients when the directory authorities don't set
12929 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 0.2.4.10-alpha.
12930 Patch by teor, reported by Jesse V.
12931 - Fix manual for the User option: it takes a username, not a UID.
12932 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
12934 - Fix the description of the --passphrase-fd option in the
12935 tor-gencert manpage. The option is used to pass the number of a
12936 file descriptor to read the passphrase from, not to read the file
12937 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
12940 - We no longer include the (dead, deprecated) bufferevent code in
12941 Tor. Closes ticket 19450. Based on a patch from "U+039b".
12943 o Removed features:
12944 - Remove support for "GET /tor/bytes.txt" DirPort request, and
12945 "GETINFO dir-usage" controller request, which were only available
12946 via a compile-time option in Tor anyway. Feature was added in
12947 0.2.2.1-alpha. Resolves ticket 19035.
12948 - There is no longer a compile-time option to disable support for
12949 TransPort. (If you don't want TransPort, just don't use it.) Patch
12950 from "U+039b". Closes ticket 19449.
12953 - Run more workqueue tests as part of "make check". These had
12954 previously been implemented, but you needed to know special
12955 command-line options to enable them.
12956 - We now have unit tests for our code to reject zlib "compression
12957 bombs". (Fortunately, the code works fine.)
12960 Changes in version 0.2.8.11 - 2016-12-08
12961 Tor 0.2.8.11 backports fixes for additional portability issues that
12962 could prevent Tor from building correctly on OSX Sierra, or with
12963 OpenSSL 1.1. Affected users should upgrade; others can safely stay
12966 o Minor bugfixes (portability):
12967 - Avoid compilation errors when building on OSX Sierra. Sierra began
12968 to support the getentropy() and clock_gettime() APIs, but created
12969 a few problems in doing so. Tor 0.2.9 has a more thorough set of
12970 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
12971 monotonic time interfaces. Fixes bug 20865. Bugfix
12974 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
12975 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
12976 architectures. Closes ticket 20588.
12979 Changes in version 0.2.8.10 - 2016-12-02
12980 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
12981 unusable after they left standby mode. It also backports fixes for
12982 a few portability issues and a small but problematic memory leak.
12984 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
12985 - When Tor leaves standby because of a new application request, open
12986 circuits as needed to serve that request. Previously, we would
12987 potentially wait a very long time. Fixes part of bug 19969; bugfix
12990 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
12991 - Clients now respond to new application stream requests immediately
12992 when they arrive, rather than waiting up to one second before
12993 starting to handle them. Fixes part of bug 19969; bugfix
12996 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
12997 - Work around a bug in the OSX 10.12 SDK that would prevent us from
12998 successfully targeting earlier versions of OSX. Resolves
13001 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
13002 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
13003 20551; bugfix on 0.2.1.1-alpha.
13005 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
13006 - Work around a memory leak in OpenSSL 1.1 when encoding public
13007 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
13009 o Minor features (geoip):
13010 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
13014 Changes in version 0.2.8.9 - 2016-10-17
13015 Tor 0.2.8.9 backports a fix for a security hole in previous versions
13016 of Tor that would allow a remote attacker to crash a Tor client,
13017 hidden service, relay, or authority. All Tor users should upgrade to
13018 this version, or to 0.2.9.4-alpha. Patches will be released for older
13021 o Major features (security fixes, also in 0.2.9.4-alpha):
13022 - Prevent a class of security bugs caused by treating the contents
13023 of a buffer chunk as if they were a NUL-terminated string. At
13024 least one such bug seems to be present in all currently used
13025 versions of Tor, and would allow an attacker to remotely crash
13026 most Tor instances, especially those compiled with extra compiler
13027 hardening. With this defense in place, such bugs can't crash Tor,
13028 though we should still fix them as they occur. Closes ticket
13029 20384 (TROVE-2016-10-001).
13031 o Minor features (geoip):
13032 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
13036 Changes in version 0.2.8.8 - 2016-09-23
13037 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
13038 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
13039 who select public relays as their bridges.
13041 o Major bugfixes (crash):
13042 - Fix a complicated crash bug that could affect Tor clients
13043 configured to use bridges when replacing a networkstatus consensus
13044 in which one of their bridges was mentioned. OpenBSD users saw
13045 more crashes here, but all platforms were potentially affected.
13046 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
13048 o Major bugfixes (relay, OOM handler):
13049 - Fix a timing-dependent assertion failure that could occur when we
13050 tried to flush from a circuit after having freed its cells because
13051 of an out-of-memory condition. Fixes bug 20203; bugfix on
13052 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
13055 o Minor feature (fallback directories):
13056 - Remove broken fallbacks from the hard-coded fallback directory
13057 list. Closes ticket 20190; patch by teor.
13059 o Minor features (geoip):
13060 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
13064 Changes in version 0.2.8.7 - 2016-08-24
13065 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
13066 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
13067 who sets the ReachableAddresses option, and all bridges, are strongly
13068 encouraged to upgrade.
13070 o Directory authority changes:
13071 - The "Tonga" bridge authority has been retired; the new bridge
13072 authority is "Bifroest". Closes tickets 19728 and 19690.
13074 o Major bugfixes (client, security):
13075 - Only use the ReachableAddresses option to restrict the first hop
13076 in a path. In earlier versions of 0.2.8.x, it would apply to
13077 every hop in the path, with a possible degradation in anonymity
13078 for anyone using an uncommon ReachableAddress setting. Fixes bug
13079 19973; bugfix on 0.2.8.2-alpha.
13081 o Minor features (geoip):
13082 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
13085 o Minor bugfixes (compilation):
13086 - Remove an inappropriate "inline" in tortls.c that was causing
13087 warnings on older versions of GCC. Fixes bug 19903; bugfix
13090 o Minor bugfixes (fallback directories):
13091 - Avoid logging a NULL string pointer when loading fallback
13092 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
13093 and 0.2.8.1-alpha. Report and patch by "rubiate".
13096 Changes in version 0.2.8.6 - 2016-08-02
13098 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
13100 The Tor 0.2.8 series improves client bootstrapping performance,
13101 completes the authority-side implementation of improved identity
13102 keys for relays, and includes numerous bugfixes and performance
13103 improvements throughout the program. This release continues to
13104 improve the coverage of Tor's test suite. For a full list of
13105 changes since Tor 0.2.7, see the ReleaseNotes file.
13107 Below is a list of the changes since Tor 0.2.7.
13109 o New system requirements:
13110 - Tor no longer attempts to support platforms where the "time_t"
13111 type is unsigned. (To the best of our knowledge, only OpenVMS does
13112 this, and Tor has never actually built on OpenVMS.) Closes
13114 - Tor no longer supports versions of OpenSSL with a broken
13115 implementation of counter mode. (This bug was present in OpenSSL
13116 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
13117 longer runs with, these versions.
13118 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
13119 later (released in 2008 and 2009 respectively). If you are
13120 building Tor from the git repository instead of from the source
13121 distribution, and your tools are older than this, you will need to
13122 upgrade. Closes ticket 17732.
13124 o Directory authority changes:
13125 - Update the V3 identity key for the dannenberg directory authority:
13126 it was changed on 18 November 2015. Closes task 17906. Patch
13128 - Urras is no longer a directory authority. Closes ticket 19271.
13130 o Major features (directory system):
13131 - Include a trial list of default fallback directories, based on an
13132 opt-in survey of suitable relays. Doing this should make clients
13133 bootstrap more quickly and reliably, and reduce the load on the
13134 directory authorities. Closes ticket 15775. Patch by teor.
13135 Candidates identified using an OnionOO script by weasel, teor,
13136 gsathya, and karsten.
13137 - Previously only relays that explicitly opened a directory port
13138 (DirPort) accepted directory requests from clients. Now all
13139 relays, with and without a DirPort, accept and serve tunneled
13140 directory requests that they receive through their ORPort. You can
13141 disable this behavior using the new DirCache option. Closes
13143 - When bootstrapping multiple consensus downloads at a time, use the
13144 first one that starts downloading, and close the rest. This
13145 reduces failures when authorities or fallback directories are slow
13146 or down. Together with the code for feature 15775, this feature
13147 should reduces failures due to fallback churn. Implements ticket
13148 4483. Patch by teor. Implements IPv4 portions of proposal 210 by
13149 mikeperry and teor.
13151 o Major features (security, Linux):
13152 - When Tor starts as root on Linux and is told to switch user ID, it
13153 can now retain the capability to bind to low ports. By default,
13154 Tor will do this only when it's switching user ID and some low
13155 ports have been configured. You can change this behavior with the
13156 new option KeepBindCapabilities. Closes ticket 8195.
13158 o Major bugfixes (client, bootstrapping):
13159 - Check if bootstrap consensus downloads are still needed when the
13160 linked connection attaches. This prevents tor making unnecessary
13161 begindir-style connections, which are the only directory
13162 connections tor clients make since the fix for 18483 was merged.
13163 - Fix some edge cases where consensus download connections may not
13164 have been closed, even though they were not needed. Related to fix
13166 - Make relays retry consensus downloads the correct number of times,
13167 rather than the more aggressive client retry count. Fixes part of
13170 o Major bugfixes (dns proxy mode, crash):
13171 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
13172 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
13174 o Major bugfixes (ed25519, voting):
13175 - Actually enable support for authorities to match routers by their
13176 Ed25519 identities. Previously, the code had been written, but
13177 some debugging code that had accidentally been left in the
13178 codebase made it stay turned off. Fixes bug 17702; bugfix
13180 - When collating votes by Ed25519 identities, authorities now
13181 include a "NoEdConsensus" flag if the ed25519 value (or lack
13182 thereof) for a server does not reflect the majority consensus.
13183 Related to bug 17668; bugfix on 0.2.7.2-alpha.
13184 - When generating a vote with keypinning disabled, never include two
13185 entries for the same ed25519 identity. This bug was causing
13186 authorities to generate votes that they could not parse when a
13187 router violated key pinning by changing its RSA identity but
13188 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
13189 18318. Bugfix on 0.2.7.2-alpha.
13191 o Major bugfixes (key management):
13192 - If OpenSSL fails to generate an RSA key, do not retain a dangling
13193 pointer to the previous (uninitialized) key value. The impact here
13194 should be limited to a difficult-to-trigger crash, if OpenSSL is
13195 running an engine that makes key generation failures possible, or
13196 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
13197 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
13200 o Major bugfixes (security, client, DNS proxy):
13201 - Stop a crash that could occur when a client running with DNSPort
13202 received a query with multiple address types, and the first
13203 address type was not supported. Found and fixed by Scott Dial.
13204 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
13206 o Major bugfixes (security, compilation):
13207 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
13208 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
13209 cause a compiler warning, thereby making other checks fail, and
13210 needlessly disabling compiler-hardening support. Fixes one case of
13211 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
13212 - Repair hardened builds under the clang compiler. Previously, our
13213 use of _FORTIFY_SOURCE would conflict with clang's address
13214 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
13216 o Major bugfixes (security, pointers):
13217 - Avoid a difficult-to-trigger heap corruption attack when extending
13218 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
13219 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
13220 Reported by Guido Vranken.
13222 o Major bugfixes (testing):
13223 - Fix a bug that would block 'make test-network-all' on systems where
13224 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
13226 o Major bugfixes (user interface):
13227 - Correctly give a warning in the cases where a relay is specified
13228 by nickname, and one such relay is found, but it is not officially
13229 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
13231 o Minor features (accounting):
13232 - Added two modes to the AccountingRule option: One for limiting
13233 only the number of bytes sent ("AccountingRule out"), and one for
13234 limiting only the number of bytes received ("AccountingRule in").
13235 Closes ticket 15989; patch from "unixninja92".
13237 o Minor features (bug-resistance):
13238 - Make Tor survive errors involving connections without a
13239 corresponding event object. Previously we'd fail with an
13240 assertion; now we produce a log message. Related to bug 16248.
13241 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
13242 level code, to harden against accidental failures to NUL-
13243 terminate. Part of ticket 17852. Patch from jsturgix. Found
13246 o Minor features (build):
13247 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
13248 as having possible IPFW support. Closes ticket 18448. Patch from
13249 Steven Chamberlain.
13250 - Since our build process now uses "make distcheck", we no longer
13251 force "make dist" to depend on "make check". Closes ticket 17893;
13252 patch from "cypherpunks".
13253 - Tor now builds once again with the recent OpenSSL 1.1 development
13254 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev). We have been
13255 tracking OpenSSL 1.1 development as it has progressed, and fixing
13256 numerous compatibility issues as they arose. See tickets
13257 17549, 17921, 17984, 19499, and 18286.
13258 - When building manual pages, set the timezone to "UTC", so that the
13259 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
13260 Patch from intrigeri.
13262 o Minor features (clients):
13263 - Make clients, onion services, and bridge relays always use an
13264 encrypted begindir connection for directory requests. Resolves
13265 ticket 18483. Patch by teor.
13267 o Minor features (controller):
13268 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
13269 controllers can examine the the reject rules added by
13270 ExitPolicyRejectPrivate. This makes it easier for stem to display
13272 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
13273 tickets 16774 and 17817. Patch by George Tankersley.
13274 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
13275 service descriptor from a service's local hidden service
13276 descriptor cache. Closes ticket 14846.
13278 o Minor features (crypto):
13279 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
13280 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
13282 - Improve performance when hashing non-multiple of 8 sized buffers,
13283 based on Andrew Moon's public domain SipHash-2-4 implementation.
13284 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
13285 - Validate the hard-coded Diffie-Hellman parameters and ensure that
13286 p is a safe prime, and g is a suitable generator. Closes
13288 - When allocating a digest state object, allocate no more space than
13289 we actually need. Previously, we would allocate as much space as
13290 the state for the largest algorithm would need. This change saves
13291 up to 672 bytes per circuit. Closes ticket 17796.
13293 o Minor features (directory downloads):
13294 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
13295 directory mirrors. The default is 1; set it to 0 to disable
13296 fallbacks. Implements ticket 17576. Patch by teor.
13297 - Wait for busy authorities and fallback directories to become non-
13298 busy when bootstrapping. (A similar change was made in 6c443e987d
13299 for directory caches chosen from the consensus.) Closes ticket
13300 17864; patch by teor.
13302 o Minor features (geoip):
13303 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
13306 o Minor features (hidden service directory):
13307 - Streamline relay-side hsdir handling: when relays consider whether
13308 to accept an uploaded hidden service descriptor, they no longer
13309 check whether they are one of the relays in the network that is
13310 "supposed" to handle that descriptor. Implements ticket 18332.
13312 o Minor features (IPv6):
13313 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
13314 to 1, tor prefers IPv6 directory addresses.
13315 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
13316 avoids using IPv4 for client OR and directory connections.
13317 - Add address policy assume_action support for IPv6 addresses.
13318 - Add an argument 'ipv6=address:orport' to the DirAuthority and
13319 FallbackDir torrc options, to specify an IPv6 address for an
13320 authority or fallback directory. Add hard-coded ipv6 addresses for
13321 directory authorities that have them. Closes ticket 17327; patch
13322 from Nick Mathewson and teor.
13323 - Allow users to configure directory authorities and fallback
13324 directory servers with IPv6 addresses and ORPorts. Resolves
13326 - Limit IPv6 mask bits to 128.
13327 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
13328 17638; bugfix on 0.0.2pre8. Patch by teor.
13329 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
13330 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
13331 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
13332 - Warn when comparing against an AF_UNSPEC address in a policy, it's
13333 almost always a bug. Closes ticket 17863; patch by teor.
13334 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
13335 17060; bugfix on 0.2.1.3-alpha. Patch by teor.
13337 o Minor features (Linux seccomp2 sandbox):
13338 - Reject attempts to change our Address with "Sandbox 1" enabled.
13339 Changing Address with Sandbox turned on would never actually work,
13340 but previously it would fail in strange and confusing ways. Found
13341 while fixing 18548.
13343 o Minor features (logging):
13344 - When logging to syslog, allow a tag to be added to the syslog
13345 identity (the string prepended to every log message). The tag can
13346 be configured with SyslogIdentityTag and defaults to none. Setting
13347 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
13350 o Minor features (portability):
13351 - Use timingsafe_memcmp() where available. Closes ticket 17944;
13352 patch from <logan@hackers.mu>.
13354 o Minor features (relay, address discovery):
13355 - Add a family argument to get_interface_addresses_raw() and
13356 subfunctions to make network interface address interogation more
13357 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
13358 types of interfaces from the operating system. Resolves
13360 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
13361 fails to enumerate interface addresses using the platform-specific
13362 API, have it rely on the UDP socket fallback technique to try and
13363 find out what IP addresses (both IPv4 and IPv6) our machine has.
13364 Resolves ticket 17951.
13366 o Minor features (replay cache):
13367 - The replay cache now uses SHA256 instead of SHA1. Implements
13368 feature 8961. Patch by teor, issue reported by rransom.
13370 o Minor features (robustness):
13371 - Exit immediately with an error message if the code attempts to use
13372 Libevent without having initialized it. This should resolve some
13373 frequently-made mistakes in our unit tests. Closes ticket 18241.
13375 o Minor features (security, clock):
13376 - Warn when the system clock appears to move back in time (when the
13377 state file was last written in the future). Tor doesn't know that
13378 consensuses have expired if the clock is in the past. Patch by
13379 teor. Implements ticket 17188.
13381 o Minor features (security, exit policies):
13382 - ExitPolicyRejectPrivate now rejects more private addresses by
13383 default. Specifically, it now rejects the relay's outbound bind
13384 addresses (if configured), and the relay's configured port
13385 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
13386 0.2.0.11-alpha. Patch by teor.
13388 o Minor features (security, memory erasure):
13389 - Make memwipe() do nothing when passed a NULL pointer or buffer of
13390 zero size. Check size argument to memwipe() for underflow. Fixes
13391 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
13393 - Set the unused entries in a smartlist to NULL. This helped catch
13394 a (harmless) bug, and shouldn't affect performance too much.
13395 Implements ticket 17026.
13396 - Use SecureMemoryWipe() function to securely clean memory on
13397 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
13398 Implements feature 17986.
13399 - Use explicit_bzero or memset_s when present. Previously, we'd use
13400 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
13401 from <logan@hackers.mu> and <selven@hackers.mu>.
13403 o Minor features (security, RNG):
13404 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
13405 positively are not allowed to fail. Previously we depended on
13406 internal details of OpenSSL's behavior. Closes ticket 17686.
13407 - Never use the system entropy output directly for anything besides
13408 seeding the PRNG. When we want to generate important keys, instead
13409 of using system entropy directly, we now hash it with the PRNG
13410 stream. This may help resist certain attacks based on broken OS
13411 entropy implementations. Closes part of ticket 17694.
13412 - Use modern system calls (like getentropy() or getrandom()) to
13413 generate strong entropy on platforms that have them. Closes
13416 o Minor features (security, win32):
13417 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
13418 attack. Fixes bug 18123; bugfix on all tor versions. Patch
13421 o Minor features (unix domain sockets):
13422 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
13423 Unix domain sockets without checking the permissions on the parent
13424 directory. (Tor checks permissions by default because some
13425 operating systems only check permissions on the parent directory.
13426 However, some operating systems do look at permissions on the
13427 socket, and tor's default check is unneeded.) Closes ticket 18458.
13430 o Minor features (unix file permissions):
13431 - Defer creation of Unix sockets until after setuid. This avoids
13432 needing CAP_CHOWN and CAP_FOWNER when using systemd's
13433 CapabilityBoundingSet, or chown and fowner when using SELinux.
13434 Implements part of ticket 17562. Patch from Jamie Nguyen.
13435 - If any directory created by Tor is marked as group readable, the
13436 filesystem group is allowed to be either the default GID or the
13437 root user. Allowing root to read the DataDirectory prevents the
13438 need for CAP_READ_SEARCH when using systemd's
13439 CapabilityBoundingSet, or dac_read_search when using SELinux.
13440 Implements part of ticket 17562. Patch from Jamie Nguyen.
13441 - Introduce a new DataDirectoryGroupReadable option. If it is set to
13442 1, the DataDirectory will be made readable by the default GID.
13443 Implements part of ticket 17562. Patch from Jamie Nguyen.
13445 o Minor bugfixes (accounting):
13446 - The max bandwidth when using 'AccountRule sum' is now correctly
13447 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
13448 from "unixninja92".
13450 o Minor bugfixes (assert, portability):
13451 - Fix an assertion failure in memarea.c on systems where "long" is
13452 shorter than the size of a pointer. Fixes bug 18716; bugfix
13455 o Minor bugfixes (bootstrap):
13456 - Consistently use the consensus download schedule for authority
13457 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
13459 o Minor bugfixes (build):
13460 - Avoid spurious failures from configure files related to calling
13461 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
13462 0.2.0.1-alpha. Patch from "cypherpunks".
13463 - Do not link the unit tests against both the testing and non-
13464 testing versions of the static libraries. Fixes bug 18490; bugfix
13466 - Resolve warnings when building on systems that are concerned with
13467 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
13469 - Silence spurious clang-scan warnings in the ed25519_donna code by
13470 explicitly initializing some objects. Fixes bug 18384; bugfix on
13471 0.2.7.2-alpha. Patch by teor.
13472 - When libscrypt.h is found, but no libscrypt library can be linked,
13473 treat libscrypt as absent. Fixes bug 19161; bugfix
13475 - Cause the unit tests to compile correctly on mingw64 versions that
13476 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
13477 - Don't try to use the pthread_condattr_setclock() function unless
13478 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
13479 17819; bugfix on 0.2.6.3-alpha.
13480 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
13482 - Fix search for libevent libraries on OpenBSD (and other systems
13483 that install libevent 1 and libevent 2 in parallel). Fixes bug
13484 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
13485 - Isolate environment variables meant for tests from the rest of the
13486 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
13487 - Mark all object files that include micro-revision.i as depending
13488 on it, so as to make parallel builds more reliable. Fixes bug
13489 17826; bugfix on 0.2.5.1-alpha.
13490 - Remove config.log only from make distclean, not from make clean.
13491 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
13492 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
13494 - Remove an #endif from configure.ac so that we correctly detect the
13495 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
13498 o Minor bugfixes (client, bootstrap):
13499 - Count receipt of new microdescriptors as progress towards
13500 bootstrapping. Previously, with EntryNodes set, Tor might not
13501 successfully repopulate the guard set on bootstrapping. Fixes bug
13502 16825; bugfix on 0.2.3.1-alpha.
13504 o Minor bugfixes (code correctness):
13505 - Fix a bad memory handling bug that would occur if we had queued a
13506 cell on a channel's incoming queue. Fortunately, we can't actually
13507 queue a cell like that as our code is constructed today, but it's
13508 best to avoid this kind of error, even if there isn't any code
13509 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
13510 - Assert that allocated memory held by the reputation code is freed
13511 according to its internal counters. Fixes bug 17753; bugfix
13513 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
13515 - Update to the latest version of Trunnel, which tries harder to
13516 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
13517 by clang address sanitizer. Fixes bug 18373; bugfix
13519 - When closing an entry connection, generate a warning if we should
13520 have sent an end cell for it but we haven't. Fixes bug 17876;
13521 bugfix on 0.2.3.2-alpha.
13523 o Minor bugfixes (configuration):
13524 - Fix a tiny memory leak when parsing a port configuration ending in
13525 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
13527 o Minor bugfixes (containers):
13528 - If we somehow attempt to construct a heap with more than
13529 1073741822 elements, avoid an integer overflow when maintaining
13530 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
13532 o Minor bugfixes (controller, microdescriptors):
13533 - Make GETINFO dir/status-vote/current/consensus conform to the
13534 control specification by returning "551 Could not open cached
13535 consensus..." when not caching consensuses. Fixes bug 18920;
13536 bugfix on 0.2.2.6-alpha.
13538 o Minor bugfixes (crypto):
13539 - Check the return value of HMAC() and assert on failure. Fixes bug
13540 17658; bugfix on 0.2.3.6-alpha. Patch by teor.
13542 o Minor bugfixes (directories):
13543 - When fetching extrainfo documents, compare their SHA256 digests
13544 and Ed25519 signing key certificates with the routerinfo that led
13545 us to fetch them, rather than with the most recent routerinfo.
13546 Otherwise we generate many spurious warnings about mismatches.
13547 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
13548 - When generating a URL for a directory server on an IPv6 address,
13549 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
13550 on 0.2.3.9-alpha. Patch from Malek.
13552 o Minor bugfixes (downloading):
13553 - Predict more correctly whether we'll be downloading over HTTP when
13554 we determine the maximum length of a URL. This should avoid a
13555 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
13558 o Minor bugfixes (exit policies, security):
13559 - Refresh an exit relay's exit policy when interface addresses
13560 change. Previously, tor only refreshed the exit policy when the
13561 configured external address changed. Fixes bug 18208; bugfix on
13562 0.2.7.3-rc. Patch by teor.
13564 o Minor bugfixes (fallback directories):
13565 - Mark fallbacks as "too busy" when they return a 503 response,
13566 rather than just marking authorities. Fixes bug 17572; bugfix on
13567 0.2.4.7-alpha. Patch by teor.
13568 - When requesting extrainfo descriptors from a trusted directory
13569 server, check whether it is an authority or a fallback directory
13570 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
13571 0.2.4.7-alpha. Reported by atagar, patch by teor.
13573 o Minor bugfixes (hidden service, client):
13574 - Handle the case where the user makes several fast consecutive
13575 requests to the same .onion address. Previously, the first six
13576 requests would each trigger a descriptor fetch, each picking a
13577 directory (there are 6 overall) and the seventh one would fail
13578 because no directories were left, thereby triggering a close on
13579 all current directory connections asking for the hidden service.
13580 The solution here is to not close the connections if we have
13581 pending directory fetches. Fixes bug 15937; bugfix
13584 o Minor bugfixes (hidden service, control port):
13585 - Add the onion address to the HS_DESC event for the UPLOADED action
13586 both on success or failure. It was previously hardcoded with
13587 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
13589 o Minor bugfixes (hidden service, directory):
13590 - Bridges now refuse "rendezvous2" (hidden service descriptor)
13591 publish attempts. Suggested by ticket 18332.
13593 o Minor bugfixes (IPv6):
13594 - Update the limits in max_dl_per_request for IPv6 address length.
13595 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
13597 o Minor bugfixes (Linux seccomp2 sandbox):
13598 - Allow more syscalls when running with "Sandbox 1" enabled:
13599 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
13600 some systems, these are required for Tor to start. Fixes bug
13601 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
13602 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
13603 so that get_interface_address6_via_udp_socket_hack() can work.
13604 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
13605 - Allow the setrlimit syscall, and the prlimit and prlimit64
13606 syscalls, which some libc implementations use under the hood.
13607 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
13608 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
13609 enabled and no DNS resolvers configured. This should help TAILS
13610 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
13611 - Fix a crash when using offline master ed25519 keys with the Linux
13612 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
13613 - Allow statistics to be written to disk when "Sandbox 1" is
13614 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
13615 0.2.6.1-alpha respectively.
13617 o Minor bugfixes (logging):
13618 - In log messages that include a function name, use __FUNCTION__
13619 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
13620 with clang __PRETTY_FUNCTION__ has extra information we don't
13621 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
13623 - Remove needless quotes from a log message about unparseable
13624 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
13625 - Scrub service name in "unrecognized service ID" log messages.
13626 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
13627 - When logging information about an unparsable networkstatus vote or
13628 consensus, do not say "vote" when we mean consensus. Fixes bug
13629 18368; bugfix on 0.2.0.8-alpha.
13630 - When we can't generate a signing key because OfflineMasterKey is
13631 set, do not imply that we should have been able to load it. Fixes
13632 bug 18133; bugfix on 0.2.7.2-alpha.
13633 - When logging a malformed hostname received through socks4, scrub
13634 it if SafeLogging says we should. Fixes bug 17419; bugfix
13637 o Minor bugfixes (memory safety):
13638 - Avoid freeing an uninitialized pointer when opening a socket fails
13639 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
13640 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
13642 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
13643 18672; bugfix on 0.2.5.1-alpha.
13644 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
13647 o Minor bugfixes (pluggable transports):
13648 - Avoid reporting a spurious error when we decide that we don't need
13649 to terminate a pluggable transport because it has already exited.
13650 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
13652 o Minor bugfixes (pointer arithmetic):
13653 - Fix a bug in memarea_alloc() that could have resulted in remote
13654 heap write access, if Tor had ever passed an unchecked size to
13655 memarea_alloc(). Fortunately, all the sizes we pass to
13656 memarea_alloc() are pre-checked to be less than 128 kilobytes.
13657 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
13660 o Minor bugfixes (private directory):
13661 - Prevent a race condition when creating private directories. Fixes
13662 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
13663 Patch from jsturgix. Found with Flawfinder.
13665 o Minor bugfixes (relays):
13666 - Check that both the ORPort and DirPort (if present) are reachable
13667 before publishing a relay descriptor. Otherwise, relays publish a
13668 descriptor with DirPort 0 when the DirPort reachability test takes
13669 longer than the ORPort reachability test. Fixes bug 18050; bugfix
13670 on 0.1.0.1-rc. Reported by "starlight", patch by teor.
13671 - Resolve some edge cases where we might launch an ORPort
13672 reachability check even when DisableNetwork is set. Noticed while
13673 fixing bug 18616; bugfix on 0.2.3.9-alpha.
13675 o Minor bugfixes (relays, hidden services):
13676 - Refuse connection requests to private OR addresses unless
13677 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
13678 then refuse to send any cells to a private address. Fixes bugs
13679 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by teor.
13681 o Minor bugfixes (security, hidden services):
13682 - Prevent hidden services connecting to client-supplied rendezvous
13683 addresses that are reserved as internal or multicast. Fixes bug
13684 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
13686 o Minor bugfixes (statistics):
13687 - Consistently check for overflow in round_*_to_next_multiple_of
13688 functions, and add unit tests with additional and maximal values.
13689 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
13690 - Handle edge cases in the laplace functions: avoid division by
13691 zero, avoid taking the log of zero, and silence clang type
13692 conversion warnings using round and trunc. Add unit tests for edge
13693 cases with maximal values. Fixes part of bug 13192; bugfix
13695 - We now include consensus downloads via IPv6 in our directory-
13696 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
13698 o Minor bugfixes (test networks, IPv6):
13699 - Allow internal IPv6 addresses in descriptors in test networks.
13700 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
13703 o Minor bugfixes (testing):
13704 - Check the full results of SHA256 and SHA512 digests in the unit
13705 tests. Bugfix on 0.2.2.4-alpha. Patch by teor.
13706 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
13708 - Fix a small memory leak that would occur when the
13709 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
13710 bugfix on 0.2.5.2-alpha.
13711 - Make unit tests pass on IPv6-only systems, and systems without
13712 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
13713 bugfix on 0.2.7.3-rc. Patch by teor.
13714 - The test for log_heartbeat was incorrectly failing in timezones
13715 with non-integer offsets. Instead of comparing the end of the time
13716 string against a constant, compare it to the output of
13717 format_local_iso_time when given the correct input. Fixes bug
13718 18039; bugfix on 0.2.5.4-alpha.
13719 - We no longer disable assertions in the unit tests when coverage is
13720 enabled. Instead, we require you to say --disable-asserts-in-tests
13721 to the configure script if you need assertions disabled in the
13722 unit tests (for example, if you want to perform branch coverage).
13723 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
13725 o Minor bugfixes (time handling):
13726 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
13727 field. Otherwise, our unit tests crash on Windows. Fixes bug
13728 18977; bugfix on 0.2.2.25-alpha.
13729 - Avoid overflow in tor_timegm when parsing dates in and after 2038
13730 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
13731 0.0.2pre14. Patch by teor.
13733 o Minor bugfixes (tor-gencert):
13734 - Correctly handle the case where an authority operator enters a
13735 passphrase but sends an EOF before sending a newline. Fixes bug
13736 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
13738 o Code simplification and refactoring:
13739 - Clean up a little duplicated code in
13740 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
13742 - Decouple the list of streams waiting to be attached to circuits
13743 from the overall connection list. This change makes it possible to
13744 attach streams quickly while simplifying Tor's callgraph and
13745 avoiding O(N) scans of the entire connection list. Closes
13747 - Extract the more complicated parts of circuit_mark_for_close()
13748 into a new function that we run periodically before circuits are
13749 freed. This change removes more than half of the functions
13750 currently in the "blob". Closes ticket 17218.
13751 - Move logging of redundant policy entries in
13752 policies_parse_exit_policy_internal into its own function. Closes
13753 ticket 17608; patch from "juce".
13754 - Quote all the string interpolations in configure.ac -- even those
13755 which we are pretty sure can't contain spaces. Closes ticket
13756 17744. Patch from zerosion.
13757 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
13758 use them. Closes ticket 17926.
13759 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
13760 inplace, so there's no need to have a separate implementation for
13761 the non-inplace code. Closes ticket 18258. Patch from Malek.
13762 - Simplify return types for some crypto functions that can't
13763 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
13764 - When a direct directory request fails immediately on launch,
13765 instead of relaunching that request from inside the code that
13766 launches it, instead mark the connection for teardown. This change
13767 simplifies Tor's callback and prevents the directory-request
13768 launching code from invoking itself recursively. Closes
13772 - Add a description of the correct use of the '--keygen' command-
13773 line option. Closes ticket 17583; based on text by 's7r'.
13774 - Change build messages to refer to "Fedora" instead of "Fedora
13775 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
13776 Patches from "icanhasaccount" and "cypherpunks".
13777 - Document the contents of the 'datadir/keys' subdirectory in the
13778 manual page. Closes ticket 17621.
13779 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
13780 - Explain actual minima for BandwidthRate. Closes ticket 16382.
13781 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
13782 - Mention torspec URL in the manpage and point the reader to it
13783 whenever we mention a document that belongs in torspce. Fixes
13785 - Stop recommending use of nicknames to identify relays in our
13786 MapAddress documentation. Closes ticket 18312.
13788 o Removed features:
13789 - Remove client-side support for connecting to Tor relays running
13790 versions of Tor before 0.2.3.6-alpha. These relays didn't support
13791 the v3 TLS handshake protocol, and are no longer allowed on the
13792 Tor network. Implements the client side of ticket 11150. Based on
13793 patches by Tom van der Woerdt.
13794 - We no longer maintain an internal freelist in memarea.c.
13795 Allocators should be good enough to make this code unnecessary,
13796 and it's doubtful that it ever had any performance benefit.
13799 - Add unit tests to check for common RNG failure modes, such as
13800 returning all zeroes, identical values, or incrementing values
13801 (OpenSSL's rand_predictable feature). Patch by teor.
13802 - Always test both ed25519 backends, so that we can be sure that our
13803 batch-open replacement code works. Part of ticket 16794.
13804 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
13805 portion of ticket 16831.
13806 - Fix several warnings from clang's address sanitizer produced in
13808 - Log more information when the backtrace tests fail. Closes ticket
13809 17892. Patch from "cypherpunks."
13810 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
13811 util_format.c, directory.c, and options_validate.c. Closes tickets
13812 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
13814 - Treat backtrace test failures as expected on FreeBSD until we
13815 solve bug 17808. Closes ticket 18204.
13816 - Unit tests for directory_handle_command_get. Closes ticket 17004.
13817 Patch from Reinaldo de Souza Jr.
13820 Changes in version 0.2.7.6 - 2015-12-10
13821 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
13822 well as a minor bug in hidden service reliability.
13824 o Major bugfixes (guard selection):
13825 - Actually look at the Guard flag when selecting a new directory
13826 guard. When we implemented the directory guard design, we
13827 accidentally started treating all relays as if they have the Guard
13828 flag during guard selection, leading to weaker anonymity and worse
13829 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
13832 o Minor features (geoip):
13833 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
13836 o Minor bugfixes (compilation):
13837 - When checking for net/pfvar.h, include netinet/in.h if possible.
13838 This fixes transparent proxy detection on OpenBSD. Fixes bug
13839 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
13840 - Fix a compilation warning with Clang 3.6: Do not check the
13841 presence of an address which can never be NULL. Fixes bug 17781.
13843 o Minor bugfixes (correctness):
13844 - When displaying an IPv6 exit policy, include the mask bits
13845 correctly even when the number is greater than 31. Fixes bug
13846 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
13847 - The wrong list was used when looking up expired intro points in a
13848 rend service object, causing what we think could be reachability
13849 issues for hidden services, and triggering a BUG log. Fixes bug
13850 16702; bugfix on 0.2.7.2-alpha.
13851 - Fix undefined behavior in the tor_cert_checksig function. Fixes
13852 bug 17722; bugfix on 0.2.7.2-alpha.
13855 Changes in version 0.2.7.5 - 2015-11-20
13856 The Tor 0.2.7 release series is dedicated to the memory of Tor user
13857 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
13858 tirelessly to advocate human rights regardless of national borders,
13859 and oppose the encroachments of mass surveillance. He opposed national
13860 exceptionalism, he brought clarity to legal and policy debates, he
13861 understood and predicted the impact of mass surveillance on the world,
13862 and he laid the groundwork for resisting it. While serving on the Tor
13863 Project's board of directors, he brought us his uncompromising focus
13864 on technical excellence in the service of humankind. Caspar was an
13865 inimitable force for good and a wonderful friend. He was kind,
13866 humorous, generous, gallant, and believed we should protect one
13867 another without exception. We honor him here for his ideals, his
13868 efforts, and his accomplishments. Please honor his memory with works
13869 that would make him proud.
13871 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
13873 The 0.2.7 series adds a more secure identity key type for relays,
13874 improves cryptography performance, resolves several longstanding
13875 hidden-service performance issues, improves controller support for
13876 hidden services, and includes small bugfixes and performance
13877 improvements throughout the program. This release series also includes
13878 more tests than before, and significant simplifications to which parts
13879 of Tor invoke which others. For a full list of changes, see below.
13881 o New system requirements:
13882 - Tor no longer includes workarounds to support Libevent versions
13883 before 1.3e. Libevent 2.0 or later is recommended. Closes
13885 - Tor no longer supports copies of OpenSSL that are missing support
13886 for Elliptic Curve Cryptography. (We began using ECC when
13887 available in 0.2.4.8-alpha, for more safe and efficient key
13888 negotiation.) In particular, support for at least one of P256 or
13889 P224 is now required, with manual configuration needed if only
13890 P224 is available. Resolves ticket 16140.
13891 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
13892 on an operating system that has not upgraded to OpenSSL 1.0 or
13893 later, and you compile Tor from source, you will need to install a
13894 more recent OpenSSL to link Tor against.) These versions of
13895 OpenSSL are still supported by the OpenSSL, but the numerous
13896 cryptographic improvements in later OpenSSL releases makes them a
13897 clear choice. Resolves ticket 16034.
13899 o Major features (controller):
13900 - Add the ADD_ONION and DEL_ONION commands that allow the creation
13901 and management of hidden services via the controller. Closes
13903 - New "GETINFO onions/current" and "GETINFO onions/detached"
13904 commands to get information about hidden services created via the
13905 controller. Part of ticket 6411.
13906 - New HSFETCH command to launch a request for a hidden service
13907 descriptor. Closes ticket 14847.
13908 - New HSPOST command to upload a hidden service descriptor. Closes
13909 ticket 3523. Patch by "DonnchaC".
13911 o Major features (Ed25519 identity keys, Proposal 220):
13912 - Add support for offline encrypted Ed25519 master keys. To use this
13913 feature on your tor relay, run "tor --keygen" to make a new master
13914 key (or to make a new signing key if you already have a master
13915 key). Closes ticket 13642.
13916 - All relays now maintain a stronger identity key, using the Ed25519
13917 elliptic curve signature format. This master key is designed so
13918 that it can be kept offline. Relays also generate an online
13919 signing key, and a set of other Ed25519 keys and certificates.
13920 These are all automatically regenerated and rotated as needed.
13921 Implements part of ticket 12498.
13922 - Directory authorities now vote on Ed25519 identity keys along with
13923 RSA1024 keys. Implements part of ticket 12498.
13924 - Directory authorities track which Ed25519 identity keys have been
13925 used with which RSA1024 identity keys, and do not allow them to
13926 vary freely. Implements part of ticket 12498.
13927 - Microdescriptors now include Ed25519 identity keys. Implements
13928 part of ticket 12498.
13929 - Add a --newpass option to allow changing or removing the
13930 passphrase of an encrypted key with tor --keygen. Implements part
13932 - Add a new OfflineMasterKey option to tell Tor never to try loading
13933 or generating a secret Ed25519 identity key. You can use this in
13934 combination with tor --keygen to manage offline and/or encrypted
13935 Ed25519 keys. Implements ticket 16944.
13936 - On receiving a HUP signal, check to see whether the Ed25519
13937 signing key has changed, and reload it if so. Closes ticket 16790.
13938 - Significant usability improvements for Ed25519 key management. Log
13939 messages are better, and the code can recover from far more
13940 failure conditions. Thanks to "s7r" for reporting and diagnosing
13943 o Major features (ECC performance):
13944 - Improve the runtime speed of Ed25519 signature verification by
13945 using Ed25519-donna's batch verification support. Implements
13947 - Improve the speed of Ed25519 operations and Curve25519 keypair
13948 generation when built targeting 32 bit x86 platforms with SSE2
13949 available. Implements ticket 16535.
13950 - Improve the runtime speed of Ed25519 operations by using the
13951 public-domain Ed25519-donna by Andrew M. ("floodyberry").
13952 Implements ticket 16467.
13953 - Improve the runtime speed of the ntor handshake by using an
13954 optimized curve25519 basepoint scalarmult implementation from the
13955 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
13956 ideas by Adam Langley. Implements ticket 9663.
13958 o Major features (Hidden services):
13959 - Hidden services, if using the EntryNodes option, are required to
13960 use more than one EntryNode, in order to avoid a guard discovery
13961 attack. (This would only affect people who had configured hidden
13962 services and manually specified the EntryNodes option with a
13963 single entry-node. The impact was that it would be easy to
13964 remotely identify the guard node used by such a hidden service.
13965 See ticket for more information.) Fixes ticket 14917.
13966 - Add the torrc option HiddenServiceNumIntroductionPoints, to
13967 specify a fixed number of introduction points. Its maximum value
13968 is 10 and default is 3. Using this option can increase a hidden
13969 service's reliability under load, at the cost of making it more
13970 visible that the hidden service is facing extra load. Closes
13972 - Remove the adaptive algorithm for choosing the number of
13973 introduction points, which used to change the number of
13974 introduction points (poorly) depending on the number of
13975 connections the HS sees. Closes ticket 4862.
13977 o Major features (onion key cross-certification):
13978 - Relay descriptors now include signatures of their own identity
13979 keys, made using the TAP and ntor onion keys. These signatures
13980 allow relays to prove ownership of their own onion keys. Because
13981 of this change, microdescriptors will no longer need to include
13982 RSA identity keys. Implements proposal 228; closes ticket 12499.
13984 o Major bugfixes (client-side privacy, also in 0.2.6.9):
13985 - Properly separate out each SOCKSPort when applying stream
13986 isolation. The error occurred because each port's session group
13987 was being overwritten by a default value when the listener
13988 connection was initialized. Fixes bug 16247; bugfix on
13989 0.2.6.3-alpha. Patch by "jojelino".
13991 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
13992 - Stop refusing to store updated hidden service descriptors on a
13993 client. This reverts commit 9407040c59218 (which indeed fixed bug
13994 14219, but introduced a major hidden service reachability
13995 regression detailed in bug 16381). This is a temporary fix since
13996 we can live with the minor issue in bug 14219 (it just results in
13997 some load on the network) but the regression of 16381 is too much
13998 of a setback. First-round fix for bug 16381; bugfix
14001 o Major bugfixes (hidden services):
14002 - Revert commit that made directory authorities assign the HSDir
14003 flag to relays without a DirPort; this was bad because such relays
14004 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
14006 - When cannibalizing a circuit for an introduction point, always
14007 extend to the chosen exit node (creating a 4 hop circuit).
14008 Previously Tor would use the current circuit exit node, which
14009 changed the original choice of introduction point, and could cause
14010 the hidden service to skip excluded introduction points or
14011 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
14014 o Major bugfixes (memory leaks):
14015 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
14016 17398; bugfix on 0.2.6.1-alpha.
14018 o Major bugfixes (open file limit):
14019 - The open file limit wasn't checked before calling
14020 tor_accept_socket_nonblocking(), which would make Tor exceed the
14021 limit. Now, before opening a new socket, Tor validates the open
14022 file limit just before, and if the max has been reached, return an
14023 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
14025 o Major bugfixes (security, correctness):
14026 - Fix an error that could cause us to read 4 bytes before the
14027 beginning of an openssl string. This bug could be used to cause
14028 Tor to crash on systems with unusual malloc implementations, or
14029 systems with unusual hardening installed. Fixes bug 17404; bugfix
14032 o Major bugfixes (stability, also in 0.2.6.10):
14033 - Stop crashing with an assertion failure when parsing certain kinds
14034 of malformed or truncated microdescriptors. Fixes bug 16400;
14035 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
14036 by "cypherpunks_backup".
14037 - Stop random client-side assertion failures that could occur when
14038 connecting to a busy hidden service, or connecting to a hidden
14039 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
14042 o Minor features (client, SOCKS):
14043 - Add GroupWritable and WorldWritable options to unix-socket based
14044 SocksPort and ControlPort options. These options apply to a single
14045 socket, and override {Control,Socks}SocketsGroupWritable. Closes
14047 - Relax the validation done to hostnames in SOCKS5 requests, and
14048 allow a single trailing '.' to cope with clients that pass FQDNs
14049 using that syntax to explicitly indicate that the domain name is
14050 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
14051 - Relax the validation of hostnames in SOCKS5 requests, allowing the
14052 character '_' to appear, in order to cope with domains observed in
14053 the wild that are serving non-RFC compliant records. Resolves
14056 o Minor features (client-side privacy):
14057 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
14058 lifespan when IsolateSOCKSAuth and streams with SOCKS
14059 authentication are attached to the circuit. This allows
14060 applications like TorBrowser to manage circuit lifetime on their
14061 own. Implements feature 15482.
14062 - When logging malformed hostnames from SOCKS5 requests, respect
14063 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
14065 o Minor features (clock-jump tolerance):
14066 - Recover better when our clock jumps back many hours, like might
14067 happen for Tails or Whonix users who start with a very wrong
14068 hardware clock, use Tor to discover a more accurate time, and then
14069 fix their clock. Resolves part of ticket 8766.
14071 o Minor features (command-line interface):
14072 - Make --hash-password imply --hush to prevent unnecessary noise.
14073 Closes ticket 15542. Patch from "cypherpunks".
14074 - Print a warning whenever we find a relative file path being used
14075 as torrc option. Resolves issue 14018.
14077 o Minor features (compilation):
14078 - Give a warning as early as possible when trying to build with an
14079 unsupported OpenSSL version. Closes ticket 16901.
14080 - Use C99 variadic macros when the compiler is not GCC. This avoids
14081 failing compilations on MSVC, and fixes a log-file-based race
14082 condition in our old workarounds. Original patch from Gisle Vanem.
14084 o Minor features (control protocol):
14085 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
14086 the control protocol. Resolves ticket 15358.
14088 o Minor features (controller):
14089 - Add DirAuthority lines for default directory authorities to the
14090 output of the "GETINFO config/defaults" command if not already
14091 present. Implements ticket 14840.
14092 - Controllers can now use "GETINFO hs/client/desc/id/..." to
14093 retrieve items from the client's hidden service descriptor cache.
14094 Closes ticket 14845.
14095 - Implement a new controller command "GETINFO status/fresh-relay-
14096 descs" to fetch a descriptor/extrainfo pair that was generated on
14097 demand just for the controller's use. Implements ticket 14784.
14099 o Minor features (directory authorities):
14100 - Directory authorities no longer vote against the "Fast", "Stable",
14101 and "HSDir" flags just because they were going to vote against
14102 "Running": if the consensus turns out to be that the router was
14103 running, then the authority's vote should count. Patch from Peter
14104 Retzlaff; closes issue 8712.
14106 o Minor features (directory authorities, security, also in 0.2.6.9):
14107 - The HSDir flag given by authorities now requires the Stable flag.
14108 For the current network, this results in going from 2887 to 2806
14109 HSDirs. Also, it makes it harder for an attacker to launch a sybil
14110 attack by raising the effort for a relay to become Stable to
14111 require at the very least 7 days, while maintaining the 96 hours
14112 uptime requirement for HSDir. Implements ticket 8243.
14114 o Minor features (DoS-resistance):
14115 - Make it harder for attackers to overload hidden services with
14116 introductions, by blocking multiple introduction requests on the
14117 same circuit. Resolves ticket 15515.
14119 o Minor features (geoip):
14120 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
14123 o Minor features (hidden services):
14124 - Add the new options "HiddenServiceMaxStreams" and
14125 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
14126 limit the maximum number of simultaneous streams per circuit, and
14127 optionally tear down the circuit when the limit is exceeded. Part
14129 - Client now uses an introduction point failure cache to know when
14130 to fetch or keep a descriptor in their cache. Previously, failures
14131 were recorded implicitly, but not explicitly remembered. Closes
14133 - Relays need to have the Fast flag to get the HSDir flag. As this
14134 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
14135 drop. This change should make some attacks against the hidden
14136 service directory system harder. Fixes ticket 15963.
14137 - Turn on hidden service statistics collection by setting the torrc
14138 option HiddenServiceStatistics to "1" by default. (This keeps
14139 track only of the fraction of traffic used by hidden services, and
14140 the total number of hidden services in existence.) Closes
14142 - To avoid leaking HS popularity, don't cycle the introduction point
14143 when we've handled a fixed number of INTRODUCE2 cells but instead
14144 cycle it when a random number of introductions is reached, thus
14145 making it more difficult for an attacker to find out the amount of
14146 clients that have used the introduction point for a specific HS.
14147 Closes ticket 15745.
14149 o Minor features (logging):
14150 - Include the Tor version in all LD_BUG log messages, since people
14151 tend to cut and paste those into the bugtracker. Implements
14154 o Minor features (pluggable transports):
14155 - When launching managed pluggable transports on Linux systems,
14156 attempt to have the kernel deliver a SIGTERM on tor exit if the
14157 pluggable transport process is still running. Resolves
14159 - When launching managed pluggable transports, setup a valid open
14160 stdin in the child process that can be used to detect if tor has
14161 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
14162 can be used by implementations to detect this new behavior.
14163 Resolves ticket 15435.
14165 o Minor bugfixes (torrc exit policies):
14166 - In each instance above, usage advice is provided to avoid the
14167 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
14168 16069; bugfix on 0.2.4.7-alpha.
14169 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
14170 produce IPv6 wildcard addresses. Previously they would produce
14171 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
14172 of bug 16069; bugfix on 0.2.4.7-alpha.
14173 - When parsing torrc ExitPolicies, we now issue an info-level
14174 message when expanding an "accept/reject *" line to include both
14175 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
14176 - When parsing torrc ExitPolicies, we now warn for a number of cases
14177 where the user's intent is likely to differ from Tor's actual
14178 behavior. These include: using an IPv4 address with an accept6 or
14179 reject6 line; using "private" on an accept6 or reject6 line; and
14180 including any ExitPolicy lines after accept *:* or reject *:*.
14181 Related to ticket 16069.
14183 o Minor bugfixes (command-line interface):
14184 - When "--quiet" is provided along with "--validate-config", do not
14185 write anything to stdout on success. Fixes bug 14994; bugfix
14187 - When complaining about bad arguments to "--dump-config", use
14188 stderr, not stdout.
14189 - Print usage information for --dump-config when it is used without
14190 an argument. Also, fix the error message to use different wording
14191 and add newline at the end. Fixes bug 15541; bugfix
14194 o Minor bugfixes (compilation):
14195 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
14196 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
14197 - Repair compilation with the most recent (unreleased, alpha)
14198 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
14200 o Minor bugfixes (compilation, also in 0.2.6.9):
14201 - Build with --enable-systemd correctly when libsystemd is
14202 installed, but systemd is not. Fixes bug 16164; bugfix on
14203 0.2.6.3-alpha. Patch from Peter Palfrader.
14205 o Minor bugfixes (configuration, unit tests):
14206 - Only add the default fallback directories when the DirAuthorities,
14207 AlternateDirAuthority, and FallbackDir directory config options
14208 are set to their defaults. The default fallback directory list is
14209 currently empty, this fix will only change tor's behavior when it
14210 has default fallback directories. Includes unit tests for
14211 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
14212 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
14214 o Minor bugfixes (controller):
14215 - Add the descriptor ID in each HS_DESC control event. It was
14216 missing, but specified in control-spec.txt. Fixes bug 15881;
14217 bugfix on 0.2.5.2-alpha.
14219 o Minor bugfixes (correctness):
14220 - For correctness, avoid modifying a constant string in
14221 handle_control_postdescriptor. Fixes bug 15546; bugfix
14223 - Remove side-effects from tor_assert() calls. This was harmless,
14224 because we never disable assertions, but it is bad style and
14225 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
14227 - When calling channel_free_list(), avoid calling smartlist_remove()
14228 while inside a FOREACH loop. This partially reverts commit
14229 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
14230 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
14232 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
14233 - Check for failures from crypto_early_init, and refuse to continue.
14234 A previous typo meant that we could keep going with an
14235 uninitialized crypto library, and would have OpenSSL initialize
14236 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
14237 when implementing ticket 4900. Patch by "teor".
14239 o Minor bugfixes (hidden service):
14240 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
14241 a client authorized hidden service. Fixes bug 15823; bugfix
14243 - Remove an extraneous newline character from the end of hidden
14244 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
14246 o Minor bugfixes (Linux seccomp2 sandbox):
14247 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
14248 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
14249 - Allow bridge authorities to run correctly under the seccomp2
14250 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
14251 - Add the "hidserv-stats" filename to our sandbox filter for the
14252 HiddenServiceStatistics option to work properly. Fixes bug 17354;
14253 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
14255 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
14256 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
14257 these when eventfd2() support is missing. Fixes bug 16363; bugfix
14258 on 0.2.6.3-alpha. Patch from "teor".
14260 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
14261 - Allow systemd connections to work with the Linux seccomp2 sandbox
14262 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
14264 - Fix sandboxing to work when running as a relay, by allowing the
14265 renaming of secret_id_key, and allowing the eventfd2 and futex
14266 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
14269 o Minor bugfixes (logging):
14270 - When building Tor under Clang, do not include an extra set of
14271 parentheses in log messages that include function names. Fixes bug
14272 15269; bugfix on every released version of Tor when compiled with
14273 recent enough Clang.
14275 o Minor bugfixes (network):
14276 - When attempting to use fallback technique for network interface
14277 lookup, disregard loopback and multicast addresses since they are
14278 unsuitable for public communications.
14280 o Minor bugfixes (open file limit):
14281 - Fix set_max_file_descriptors() to set by default the max open file
14282 limit to the current limit when setrlimit() fails. Fixes bug
14283 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
14285 o Minor bugfixes (portability):
14286 - Check correctly for Windows socket errors in the workqueue
14287 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
14288 - Try harder to normalize the exit status of the Tor process to the
14289 standard-provided range. Fixes bug 16975; bugfix on every version
14291 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes part
14292 of bug 17151; bugfix on 0.2.5.2-alpha. Patch from Marcin Cieślak.
14294 o Minor bugfixes (relay):
14295 - Ensure that worker threads actually exit when a fatal error or
14296 shutdown is indicated. This fix doesn't currently affect the
14297 behavior of Tor, because Tor workers never indicates fatal error
14298 or shutdown except in the unit tests. Fixes bug 16868; bugfix
14300 - Fix a rarely-encountered memory leak when failing to initialize
14301 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
14302 from "cypherpunks".
14303 - Unblock threads before releasing the work queue mutex to ensure
14304 predictable scheduling behavior. Fixes bug 16644; bugfix
14307 o Minor bugfixes (security, exit policies):
14308 - ExitPolicyRejectPrivate now also rejects the relay's published
14309 IPv6 address (if any), and any publicly routable IPv4 or IPv6
14310 addresses on any local interfaces. ticket 17027. Patch by "teor".
14311 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
14313 o Minor bugfixes (statistics):
14314 - Disregard the ConnDirectionStatistics torrc options when Tor is
14315 not a relay since in that mode of operation no sensible data is
14316 being collected and because Tor might run into measurement hiccups
14317 when running as a client for some time, then becoming a relay.
14318 Fixes bug 15604; bugfix on 0.2.2.35.
14320 o Minor bugfixes (systemd):
14321 - Tor's systemd unit file no longer contains extraneous spaces.
14322 These spaces would sometimes confuse tools like deb-systemd-
14323 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
14325 o Minor bugfixes (test networks):
14326 - When self-testing reachability, use ExtendAllowPrivateAddresses to
14327 determine if local/private addresses imply reachability. The
14328 previous fix used TestingTorNetwork, which implies
14329 ExtendAllowPrivateAddresses, but this excluded rare configurations
14330 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
14331 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
14332 issue discovered by CJ Ess.
14334 o Minor bugfixes (tests, also in 0.2.6.9):
14335 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
14336 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
14338 o Code simplification and refactoring:
14339 - Change the function that's called when we need to retry all
14340 downloads so that it only reschedules the downloads to happen
14341 immediately, rather than launching them all at once itself. This
14342 further simplifies Tor's callgraph.
14343 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
14344 to ensure they remain consistent and visible everywhere.
14345 - Move some format-parsing functions out of crypto.c and
14346 crypto_curve25519.c into crypto_format.c and/or util_format.c.
14347 - Move the client-only parts of init_keys() into a separate
14348 function. Closes ticket 16763.
14349 - Move the hacky fallback code out of get_interface_address6() into
14350 separate function and get it covered with unit-tests. Resolves
14352 - Refactor hidden service client-side cache lookup to intelligently
14353 report its various failure cases, and disentangle failure cases
14354 involving a lack of introduction points. Closes ticket 14391.
14355 - Remove some vestigial workarounds for the MSVC6 compiler. We
14356 haven't supported that in ages.
14357 - Remove the unused "nulterminate" argument from buf_pullup().
14358 - Simplify the microdesc_free() implementation so that it no longer
14359 appears (to code analysis tools) to potentially invoke a huge
14360 suite of other microdesc functions.
14361 - Simply the control graph further by deferring the inner body of
14362 directory_all_unreachable() into a callback. Closes ticket 16762.
14363 - The link authentication code has been refactored for better
14364 testability and reliability. It now uses code generated with the
14365 "trunnel" binary encoding generator, to reduce the risk of bugs
14366 due to programmer error. Done as part of ticket 12498.
14367 - Treat the loss of an owning controller as equivalent to a SIGTERM
14368 signal. This removes a tiny amount of duplicated code, and
14369 simplifies our callgraph. Closes ticket 16788.
14370 - Use our own Base64 encoder instead of OpenSSL's, to allow more
14371 control over the output. Part of ticket 15652.
14372 - When generating an event to send to the controller, we no longer
14373 put the event over the network immediately. Instead, we queue
14374 these events, and use a Libevent callback to deliver them. This
14375 change simplifies Tor's callgraph by reducing the number of
14376 functions from which all other Tor functions are reachable. Closes
14378 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
14379 that try to scan or compile every file on Unix won't decide that
14383 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
14384 - Improve the descriptions of statistics-related torrc options in
14385 the manpage to describe rationale and possible uses cases. Fixes
14387 - Improve the layout and formatting of ./configure --help messages.
14388 Closes ticket 15024. Patch from "cypherpunks".
14389 - Include a specific and (hopefully) accurate documentation of the
14390 torrc file's meta-format in doc/torrc_format.txt. This is mainly
14391 of interest to people writing programs to parse or generate torrc
14392 files. This document is not a commitment to long-term
14393 compatibility; some aspects of the current format are a bit
14394 ridiculous. Closes ticket 2325.
14395 - Include the TUNING document in our source tarball. It is referred
14396 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
14398 - Note that HiddenServicePorts can take a unix domain socket. Closes
14400 - Recommend a 40 GB example AccountingMax in torrc.sample rather
14401 than a 4 GB max. Closes ticket 16742.
14402 - Standardize on the term "server descriptor" in the manual page.
14403 Previously, we had used "router descriptor", "server descriptor",
14404 and "relay descriptor" interchangeably. Part of ticket 14987.
14405 - Advise users on how to configure separate IPv4 and IPv6 exit
14406 policies in the manpage and sample torrcs. Related to ticket 16069.
14407 - Fix an error in the manual page and comments for
14408 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
14409 required "ORPort connectivity". While this is true, it is in no
14410 way unique to the HSDir flag. Of all the flags, only HSDirs need a
14411 DirPort configured in order for the authorities to assign that
14412 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
14414 - Fix the usage message of tor-resolve(1) so that it no longer lists
14415 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
14418 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
14419 and always use the internal Base64 decoder. The internal decoder
14420 has been part of tor since 0.2.0.10-alpha, and no one should
14421 be using the OpenSSL one. Part of ticket 15652.
14422 - Remove the 'tor_strclear()' function; use memwipe() instead.
14423 Closes ticket 14922.
14424 - Remove the code that would try to aggressively flush controller
14425 connections while writing to them. This code was introduced in
14426 0.1.2.7-alpha, in order to keep output buffers from exceeding
14427 their limits. But there is no longer a maximum output buffer size,
14428 and flushing data in this way caused some undesirable recursions
14429 in our call graph. Closes ticket 16480.
14430 - The internal pure-C tor-fw-helper tool is now removed from the Tor
14431 distribution, in favor of the pure-Go clone available from
14432 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
14433 used by the C tor-fw-helper are not, in our opinion, very
14434 confidence- inspiring in their secure-programming techniques.
14435 Closes ticket 13338.
14437 o Removed features:
14438 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
14439 fingerprinting we now recommend pluggable transports; for forward-
14440 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
14441 - Remove the HidServDirectoryV2 option. Now all relays offer to
14442 store hidden service descriptors. Related to 16543.
14443 - Remove the VoteOnHidServDirectoriesV2 option, since all
14444 authorities have long set it to 1. Closes ticket 16543.
14445 - Remove the undocumented "--digests" command-line option. It
14446 complicated our build process, caused subtle build issues on
14447 multiple platforms, and is now redundant since we started
14448 including git version identifiers. Closes ticket 14742.
14449 - Tor no longer contains checks for ancient directory cache versions
14450 that didn't know about microdescriptors.
14451 - Tor no longer contains workarounds for stat files generated by
14452 super-old versions of Tor that didn't choose guards sensibly.
14455 - The test-network.sh script now supports performance testing.
14456 Requires corresponding chutney performance testing changes. Patch
14457 by "teor". Closes ticket 14175.
14458 - Add a new set of callgraph analysis scripts that use clang to
14459 produce a list of which Tor functions are reachable from which
14460 other Tor functions. We're planning to use these to help simplify
14461 our code structure by identifying illogical dependencies.
14462 - Add new 'test-full' and 'test-full-online' targets to run all
14463 tests, including integration tests with stem and chutney.
14464 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
14465 by-side in the same parent directory. Closes ticket 16903. Patch
14467 - Document use of coverity, clang static analyzer, and clang dynamic
14468 undefined behavior and address sanitizers in doc/HACKING. Include
14469 detailed usage instructions in the blacklist. Patch by "teor".
14470 Closes ticket 15817.
14471 - Make "bridges+hs" the default test network. This tests almost all
14472 tor functionality during make test-network, while allowing tests
14473 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
14474 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
14475 (chutney). Patches by "teor".
14476 - Make the test-workqueue test work on Windows by initializing the
14477 network before we begin.
14478 - New make target (make test-network-all) to run multiple applicable
14479 chutney test cases. Patch from Teor; closes 16953.
14480 - Now that OpenSSL has its own scrypt implementation, add an unit
14481 test that checks for interoperability between libscrypt_scrypt()
14482 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
14483 and rely on EVP_PBE_scrypt() whenever possible. Resolves
14485 - The link authentication protocol code now has extensive tests.
14486 - The relay descriptor signature testing code now has
14488 - The test_workqueue program now runs faster, and is enabled by
14489 default as a part of "make check".
14490 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
14491 functions in dns.c. Implements a portion of ticket 16831.
14492 - Use environment variables rather than autoconf substitutions to
14493 send variables from the build system to the test scripts. This
14494 change should be easier to maintain, and cause 'make distcheck' to
14495 work better than before. Fixes bug 17148.
14496 - When building Tor with testing coverage enabled, run Chutney tests
14497 (if any) using the 'tor-cov' coverage binary.
14498 - When running test-network or test-stem, check for the absence of
14499 stem/chutney before doing any build operations.
14500 - Add a test to verify that the compiler does not eliminate our
14501 memwipe() implementation. Closes ticket 15377.
14502 - Add make rule `check-changes` to verify the format of changes
14503 files. Closes ticket 15180.
14504 - Add unit tests for control_event_is_interesting(). Add a compile-
14505 time check that the number of events doesn't exceed the capacity
14506 of control_event_t.event_mask. Closes ticket 15431, checks for
14507 bugs similar to 13085. Patch by "teor".
14508 - Command-line argument tests moved to Stem. Resolves ticket 14806.
14509 - Integrate the ntor, backtrace, and zero-length keys tests into the
14510 automake test suite. Closes ticket 15344.
14511 - Remove assertions during builds to determine Tor's test coverage.
14512 We don't want to trigger these even in assertions, so including
14513 them artificially makes our branch coverage look worse than it is.
14514 This patch provides the new test-stem-full and coverage-html-full
14515 configure options. Implements ticket 15400.
14516 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
14517 explicitly manage consensus flags in testing networks. Patch by
14518 "robgjansen", modified by "teor". Implements part of ticket 14882.
14519 - Check for matching value in server response in ntor_ref.py. Fixes
14520 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
14522 - Set the severity correctly when testing
14523 get_interface_addresses_ifaddrs() and
14524 get_interface_addresses_win32(), so that the tests fail gracefully
14525 instead of triggering an assertion. Fixes bug 15759; bugfix on
14526 0.2.6.3-alpha. Reported by Nicolas Derive.
14528 Changes in version 0.2.6.10 - 2015-07-12
14529 Tor version 0.2.6.10 fixes some significant stability and hidden
14530 service client bugs, bulletproofs the cryptography init process, and
14531 fixes a bug when using the sandbox code with some older versions of
14532 Linux. Everyone running an older version, especially an older version
14533 of 0.2.6, should upgrade.
14535 o Major bugfixes (hidden service clients, stability):
14536 - Stop refusing to store updated hidden service descriptors on a
14537 client. This reverts commit 9407040c59218 (which indeed fixed bug
14538 14219, but introduced a major hidden service reachability
14539 regression detailed in bug 16381). This is a temporary fix since
14540 we can live with the minor issue in bug 14219 (it just results in
14541 some load on the network) but the regression of 16381 is too much
14542 of a setback. First-round fix for bug 16381; bugfix
14545 o Major bugfixes (stability):
14546 - Stop crashing with an assertion failure when parsing certain kinds
14547 of malformed or truncated microdescriptors. Fixes bug 16400;
14548 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
14549 by "cypherpunks_backup".
14550 - Stop random client-side assertion failures that could occur when
14551 connecting to a busy hidden service, or connecting to a hidden
14552 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
14555 o Minor features (geoip):
14556 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
14557 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
14559 o Minor bugfixes (crypto error-handling):
14560 - Check for failures from crypto_early_init, and refuse to continue.
14561 A previous typo meant that we could keep going with an
14562 uninitialized crypto library, and would have OpenSSL initialize
14563 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
14564 when implementing ticket 4900. Patch by "teor".
14566 o Minor bugfixes (Linux seccomp2 sandbox):
14567 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
14568 these when eventfd2() support is missing. Fixes bug 16363; bugfix
14569 on 0.2.6.3-alpha. Patch from "teor".
14572 Changes in version 0.2.6.9 - 2015-06-11
14573 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
14574 requirements for receiving an HSDir flag, and addresses some other small
14575 bugs in the systemd and sandbox code. Clients using circuit isolation
14576 should upgrade; all directory authorities should upgrade.
14578 o Major bugfixes (client-side privacy):
14579 - Properly separate out each SOCKSPort when applying stream
14580 isolation. The error occurred because each port's session group was
14581 being overwritten by a default value when the listener connection
14582 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
14585 o Minor feature (directory authorities, security):
14586 - The HSDir flag given by authorities now requires the Stable flag.
14587 For the current network, this results in going from 2887 to 2806
14588 HSDirs. Also, it makes it harder for an attacker to launch a sybil
14589 attack by raising the effort for a relay to become Stable which
14590 takes at the very least 7 days to do so and by keeping the 96
14591 hours uptime requirement for HSDir. Implements ticket 8243.
14593 o Minor bugfixes (compilation):
14594 - Build with --enable-systemd correctly when libsystemd is
14595 installed, but systemd is not. Fixes bug 16164; bugfix on
14596 0.2.6.3-alpha. Patch from Peter Palfrader.
14598 o Minor bugfixes (Linux seccomp2 sandbox):
14599 - Fix sandboxing to work when running as a relaymby renaming of
14600 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
14601 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
14602 - Allow systemd connections to work with the Linux seccomp2 sandbox
14603 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
14606 o Minor bugfixes (tests):
14607 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
14608 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
14611 Changes in version 0.2.6.8 - 2015-05-21
14612 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
14613 fixes an authority-side bug in assigning the HSDir flag. All directory
14614 authorities should upgrade.
14616 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
14617 - Revert commit that made directory authorities assign the HSDir
14618 flag to relays without a DirPort; this was bad because such relays
14619 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
14622 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
14623 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
14624 a client authorized hidden service. Fixes bug 15823; bugfix
14627 o Minor features (geoip):
14628 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
14629 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
14633 Changes in version 0.2.6.7 - 2015-04-06
14634 Tor 0.2.6.7 fixes two security issues that could be used by an
14635 attacker to crash hidden services, or crash clients visiting hidden
14636 services. Hidden services should upgrade as soon as possible; clients
14637 should upgrade whenever packages become available.
14639 This release also contains two simple improvements to make hidden
14640 services a bit less vulnerable to denial-of-service attacks.
14642 o Major bugfixes (security, hidden service):
14643 - Fix an issue that would allow a malicious client to trigger an
14644 assertion failure and halt a hidden service. Fixes bug 15600;
14645 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
14646 - Fix a bug that could cause a client to crash with an assertion
14647 failure when parsing a malformed hidden service descriptor. Fixes
14648 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
14650 o Minor features (DoS-resistance, hidden service):
14651 - Introduction points no longer allow multiple INTRODUCE1 cells to
14652 arrive on the same circuit. This should make it more expensive for
14653 attackers to overwhelm hidden services with introductions.
14654 Resolves ticket 15515.
14655 - Decrease the amount of reattempts that a hidden service performs
14656 when its rendezvous circuits fail. This reduces the computational
14657 cost for running a hidden service under heavy load. Resolves
14661 Changes in version 0.2.5.12 - 2015-04-06
14662 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
14663 could be used by an attacker to crash hidden services, or crash clients
14664 visiting hidden services. Hidden services should upgrade as soon as
14665 possible; clients should upgrade whenever packages become available.
14667 This release also backports a simple improvement to make hidden
14668 services a bit less vulnerable to denial-of-service attacks.
14670 o Major bugfixes (security, hidden service):
14671 - Fix an issue that would allow a malicious client to trigger an
14672 assertion failure and halt a hidden service. Fixes bug 15600;
14673 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
14674 - Fix a bug that could cause a client to crash with an assertion
14675 failure when parsing a malformed hidden service descriptor. Fixes
14676 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
14678 o Minor features (DoS-resistance, hidden service):
14679 - Introduction points no longer allow multiple INTRODUCE1 cells to
14680 arrive on the same circuit. This should make it more expensive for
14681 attackers to overwhelm hidden services with introductions.
14682 Resolves ticket 15515.
14685 Changes in version 0.2.4.27 - 2015-04-06
14686 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
14687 could be used by an attacker to crash hidden services, or crash clients
14688 visiting hidden services. Hidden services should upgrade as soon as
14689 possible; clients should upgrade whenever packages become available.
14691 This release also backports a simple improvement to make hidden
14692 services a bit less vulnerable to denial-of-service attacks.
14694 o Major bugfixes (security, hidden service):
14695 - Fix an issue that would allow a malicious client to trigger an
14696 assertion failure and halt a hidden service. Fixes bug 15600;
14697 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
14698 - Fix a bug that could cause a client to crash with an assertion
14699 failure when parsing a malformed hidden service descriptor. Fixes
14700 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
14702 o Minor features (DoS-resistance, hidden service):
14703 - Introduction points no longer allow multiple INTRODUCE1 cells to
14704 arrive on the same circuit. This should make it more expensive for
14705 attackers to overwhelm hidden services with introductions.
14706 Resolves ticket 15515.
14709 Changes in version 0.2.6.6 - 2015-03-24
14710 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
14712 It adds numerous safety, security, correctness, and performance
14713 improvements. Client programs can be configured to use more kinds of
14714 sockets, AutomapHosts works better, the multithreading backend is
14715 improved, cell transmission is refactored, test coverage is much
14716 higher, more denial-of-service attacks are handled, guard selection is
14717 improved to handle long-term guards better, pluggable transports
14718 should work a bit better, and some annoying hidden service performance
14719 bugs should be addressed.
14721 o New compiler and system requirements:
14722 - Tor 0.2.6.x requires that your compiler support more of the C99
14723 language standard than before. The 'configure' script now detects
14724 whether your compiler supports C99 mid-block declarations and
14725 designated initializers. If it does not, Tor will not compile.
14727 We may revisit this requirement if it turns out that a significant
14728 number of people need to build Tor with compilers that don't
14729 bother implementing a 15-year-old standard. Closes ticket 13233.
14730 - Tor no longer supports systems without threading support. When we
14731 began working on Tor, there were several systems that didn't have
14732 threads, or where the thread support wasn't able to run the
14733 threads of a single process on multiple CPUs. That no longer
14734 holds: every system where Tor needs to run well now has threading
14735 support. Resolves ticket 12439.
14737 o Deprecated versions and removed support:
14738 - Tor relays older than 0.2.4.18-rc are no longer allowed to
14739 advertise themselves on the network. Closes ticket 13555.
14740 - Tor clients no longer support connecting to hidden services
14741 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
14742 option has been removed. (There shouldn't be any hidden services
14743 running these versions on the network.) Closes ticket 7803.
14745 o Directory authority changes:
14746 - The directory authority Faravahar has a new IP address. This
14747 closes ticket 14487.
14748 - Remove turtles as a directory authority.
14749 - Add longclaw as a new (v3) directory authority. This implements
14750 ticket 13296. This keeps the directory authority count at 9.
14752 o Major features (bridges):
14753 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
14754 transports if they are configured via the "TOR_PT_PROXY"
14755 environment variable. Implements proposal 232. Resolves
14758 o Major features (changed defaults):
14759 - Prevent relay operators from unintentionally running exits: When a
14760 relay is configured as an exit node, we now warn the user unless
14761 the "ExitRelay" option is set to 1. We warn even more loudly if
14762 the relay is configured with the default exit policy, since this
14763 can indicate accidental misconfiguration. Setting "ExitRelay 0"
14764 stops Tor from running as an exit relay. Closes ticket 10067.
14766 o Major features (client performance, hidden services):
14767 - Allow clients to use optimistic data when connecting to a hidden
14768 service, which should remove a round-trip from hidden service
14769 initialization. See proposal 181 for details. Implements
14772 o Major features (directory system):
14773 - Upon receiving an unparseable directory object, if its digest
14774 matches what we expected, then don't try to download it again.
14775 Previously, when we got a descriptor we didn't like, we would keep
14776 trying to download it over and over. Closes ticket 11243.
14777 - When downloading server- or microdescriptors from a directory
14778 server, we no longer launch multiple simultaneous requests to the
14779 same server. This reduces load on the directory servers,
14780 especially when directory guards are in use. Closes ticket 9969.
14781 - When downloading server- or microdescriptors over a tunneled
14782 connection, do not limit the length of our requests to what the
14783 Squid proxy is willing to handle. Part of ticket 9969.
14784 - Authorities can now vote on the correct digests and latest
14785 versions for different software packages. This allows packages
14786 that include Tor to use the Tor authority system as a way to get
14787 notified of updates and their correct digests. Implements proposal
14788 227. Closes ticket 10395.
14790 o Major features (guards):
14791 - Introduce the Guardfraction feature to improves load balancing on
14792 guard nodes. Specifically, it aims to reduce the traffic gap that
14793 guard nodes experience when they first get the Guard flag. This is
14794 a required step if we want to increase the guard lifetime to 9
14795 months or greater. Closes ticket 9321.
14797 o Major features (hidden services):
14798 - Make HS port scanning more difficult by immediately closing the
14799 circuit when a user attempts to connect to a nonexistent port.
14800 Closes ticket 13667.
14801 - Add a HiddenServiceStatistics option that allows Tor relays to
14802 gather and publish statistics about the overall size and volume of
14803 hidden service usage. Specifically, when this option is turned on,
14804 an HSDir will publish an approximate number of hidden services
14805 that have published descriptors to it the past 24 hours. Also, if
14806 a relay has acted as a hidden service rendezvous point, it will
14807 publish the approximate amount of rendezvous cells it has relayed
14808 the past 24 hours. The statistics themselves are obfuscated so
14809 that the exact values cannot be derived. For more details see
14810 proposal 238, "Better hidden service stats from Tor relays". This
14811 feature is currently disabled by default. Implements feature 13192.
14813 o Major features (performance):
14814 - Make the CPU worker implementation more efficient by avoiding the
14815 kernel and lengthening pipelines. The original implementation used
14816 sockets to transfer data from the main thread to the workers, and
14817 didn't allow any thread to be assigned more than a single piece of
14818 work at once. The new implementation avoids communications
14819 overhead by making requests in shared memory, avoiding kernel IO
14820 where possible, and keeping more requests in flight at once.
14821 Implements ticket 9682.
14823 o Major features (relay):
14824 - Raise the minimum acceptable configured bandwidth rate for bridges
14825 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
14826 20 KiB/sec.) Closes ticket 13822.
14827 - Complete revision of the code that relays use to decide which cell
14828 to send next. Formerly, we selected the best circuit to write on
14829 each channel, but we didn't select among channels in any
14830 sophisticated way. Now, we choose the best circuits globally from
14831 among those whose channels are ready to deliver traffic.
14833 This patch implements a new inter-cmux comparison API, a global
14834 high/low watermark mechanism and a global scheduler loop for
14835 transmission prioritization across all channels as well as among
14836 circuits on one channel. This schedule is currently tuned to
14837 (tolerantly) avoid making changes in network performance, but it
14838 should form the basis for major circuit performance increases in
14839 the future. Code by Andrea; tuning by Rob Jansen; implements
14842 o Major features (sample torrc):
14843 - Add a new, infrequently-changed "torrc.minimal". This file is
14844 similar to torrc.sample, but it will change as infrequently as
14845 possible, for the benefit of users whose systems prompt them for
14846 intervention whenever a default configuration file is changed.
14847 Making this change allows us to update torrc.sample to be a more
14848 generally useful "sample torrc".
14850 o Major features (security, unix domain sockets):
14851 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
14852 applications can reach Tor without having to create AF_INET or
14853 AF_INET6 sockets, meaning they can completely disable their
14854 ability to make non-Tor network connections. To create a socket of
14855 this type, use "SocksPort unix:/path/to/socket". Implements
14857 - Support mapping hidden service virtual ports to AF_UNIX sockets.
14858 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
14859 Implements ticket 11485.
14861 o Major bugfixes (client, automap):
14862 - Repair automapping with IPv6 addresses. This automapping should
14863 have worked previously, but one piece of debugging code that we
14864 inserted to detect a regression actually caused the regression to
14865 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
14866 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
14869 o Major bugfixes (crash, OSX, security):
14870 - Fix a remote denial-of-service opportunity caused by a bug in
14871 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
14874 o Major bugfixes (directory authorities):
14875 - Do not assign the HSDir flag to relays if they are not Valid, or
14876 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
14878 o Major bugfixes (directory bandwidth performance):
14879 - Don't flush the zlib buffer aggressively when compressing
14880 directory information for clients. This should save about 7% of
14881 the bandwidth currently used for compressed descriptors and
14882 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
14884 o Major bugfixes (exit node stability):
14885 - Fix an assertion failure that could occur under high DNS load.
14886 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
14887 diagnosed and fixed by "cypherpunks".
14889 o Major bugfixes (FreeBSD IPFW transparent proxy):
14890 - Fix address detection with FreeBSD transparent proxies, when
14891 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
14894 o Major bugfixes (hidden services):
14895 - When closing an introduction circuit that was opened in parallel
14896 with others, don't mark the introduction point as unreachable.
14897 Previously, the first successful connection to an introduction
14898 point would make the other introduction points get marked as
14899 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
14901 o Major bugfixes (Linux seccomp2 sandbox):
14902 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
14903 crash during attempts to call wait4. Fixes bug 15088; bugfix on
14904 0.2.5.1-alpha. Patch from "sanic".
14906 o Major bugfixes (mixed relay-client operation):
14907 - When running as a relay and client at the same time (not
14908 recommended), if we decide not to use a new guard because we want
14909 to retry older guards, only close the locally-originating circuits
14910 passing through that guard. Previously we would close all the
14911 circuits through that guard. Fixes bug 9819; bugfix on
14912 0.2.1.1-alpha. Reported by "skruffy".
14914 o Major bugfixes (pluggable transports):
14915 - Initialize the extended OR Port authentication cookie before
14916 launching pluggable transports. This prevents a race condition
14917 that occurred when server-side pluggable transports would cache the
14918 authentication cookie before it has been (re)generated. Fixes bug
14919 15240; bugfix on 0.2.5.1-alpha.
14921 o Major bugfixes (relay, stability, possible security):
14922 - Fix a bug that could lead to a relay crashing with an assertion
14923 failure if a buffer of exactly the wrong layout is passed to
14924 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
14925 0.2.0.10-alpha. Patch from "cypherpunks".
14926 - Do not assert if the 'data' pointer on a buffer is advanced to the
14927 very end of the buffer; log a BUG message instead. Only assert if
14928 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
14930 o Minor features (build):
14931 - New --disable-system-torrc compile-time option to prevent Tor from
14932 looking for the system-wide torrc or torrc-defaults files.
14933 Resolves ticket 13037.
14935 o Minor features (client):
14936 - Clients are now willing to send optimistic data (before they
14937 receive a 'connected' cell) to relays of any version. (Relays
14938 without support for optimistic data are no longer supported on the
14939 Tor network.) Resolves ticket 13153.
14941 o Minor features (client):
14942 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
14943 is enabled, reject requests with IP addresses as hostnames.
14944 Resolves ticket 13315.
14946 o Minor features (controller):
14947 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
14948 write an unscheduled heartbeat message to the log. Implements
14950 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
14951 events so controllers can observe circuit isolation inputs. Closes
14953 - ControlPort now supports the unix:/path/to/socket syntax as an
14954 alternative to the ControlSocket option, for consistency with
14955 SocksPort and HiddenServicePort. Closes ticket 14451.
14956 - New "GETINFO bw-event-cache" to get information about recent
14957 bandwidth events. Closes ticket 14128. Useful for controllers to
14958 get recent bandwidth history after the fix for ticket 13988.
14959 - Messages about problems in the bootstrap process now include
14960 information about the server we were trying to connect to when we
14961 noticed the problem. Closes ticket 15006.
14963 o Minor features (Denial of service resistance):
14964 - Count the total number of bytes used storing hidden service
14965 descriptors against the value of MaxMemInQueues. If we're low on
14966 memory, and more than 20% of our memory is used holding hidden
14967 service descriptors, free them until no more than 10% of our
14968 memory holds hidden service descriptors. Free the least recently
14969 fetched descriptors first. Resolves ticket 13806.
14970 - When we have recently been under memory pressure (over 3/4 of
14971 MaxMemInQueues is allocated), then allocate smaller zlib objects
14972 for small requests. Closes ticket 11791.
14974 o Minor features (directory authorities):
14975 - Don't list relays with a bandwidth estimate of 0 in the consensus.
14976 Implements a feature proposed during discussion of bug 13000.
14977 - In tor-gencert, report an error if the user provides the same
14978 argument more than once.
14979 - If a directory authority can't find a best consensus method in the
14980 votes that it holds, it now falls back to its favorite consensus
14981 method. Previously, it fell back to method 1. Neither of these is
14982 likely to get enough signatures, but "fall back to favorite"
14983 doesn't require us to maintain support an obsolete consensus
14984 method. Implements part of proposal 215.
14986 o Minor features (geoip):
14987 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
14988 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
14991 o Minor features (guard nodes):
14992 - Reduce the time delay before saving guard status to disk from 10
14993 minutes to 30 seconds (or from one hour to 10 minutes if
14994 AvoidDiskWrites is set). Closes ticket 12485.
14996 o Minor features (heartbeat):
14997 - On relays, report how many connections we negotiated using each
14998 version of the Tor link protocols. This information will let us
14999 know if removing support for very old versions of the Tor
15000 protocols is harming the network. Closes ticket 15212.
15002 o Minor features (hidden service):
15003 - Make Sybil attacks against hidden services harder by changing the
15004 minimum time required to get the HSDir flag from 25 hours up to 96
15005 hours. Addresses ticket 14149.
15006 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
15007 services to disable the anti-scanning feature introduced in
15008 0.2.6.2-alpha. With this option not set, a connection to an
15009 unlisted port closes the circuit. With this option set, only a
15010 RELAY_DONE cell is sent. Closes ticket 14084.
15011 - When re-enabling the network, don't try to build introduction
15012 circuits until we have successfully built a circuit. This makes
15013 hidden services come up faster when the network is re-enabled.
15014 Patch from "akwizgran". Closes ticket 13447.
15015 - When we fail to retrieve a hidden service descriptor, send the
15016 controller an "HS_DESC FAILED" controller event. Implements
15018 - New HiddenServiceDirGroupReadable option to cause hidden service
15019 directories and hostname files to be created group-readable. Patch
15020 from "anon", David Stainton, and "meejah". Closes ticket 11291.
15022 o Minor features (interface):
15023 - Implement "-f -" command-line option to read torrc configuration
15024 from standard input, if you don't want to store the torrc file in
15025 the file system. Implements feature 13865.
15027 o Minor features (logging):
15028 - Add a count of unique clients to the bridge heartbeat message.
15029 Resolves ticket 6852.
15030 - Suppress "router info incompatible with extra info" message when
15031 reading extrainfo documents from cache. (This message got loud
15032 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
15034 - Elevate hidden service authorized-client message from DEBUG to
15035 INFO. Closes ticket 14015.
15036 - On Unix-like systems, you can now use named pipes as the target of
15037 the Log option, and other options that try to append to files.
15038 Closes ticket 12061. Patch from "carlo von lynX".
15039 - When opening a log file at startup, send it every log message that
15040 we generated between startup and opening it. Previously, log
15041 messages that were generated before opening the log file were only
15042 logged to stdout. Closes ticket 6938.
15043 - Add a TruncateLogFile option to overwrite logs instead of
15044 appending to them. Closes ticket 5583.
15045 - Quiet some log messages in the heartbeat and at startup. Closes
15048 o Minor features (portability, Solaris):
15049 - Threads are no longer disabled by default on Solaris; we believe
15050 that the versions of Solaris with broken threading support are all
15051 obsolete by now. Resolves ticket 9495.
15053 o Minor features (relay):
15054 - Re-check our address after we detect a changed IP address from
15055 getsockname(). This ensures that the controller command "GETINFO
15056 address" will report the correct value. Resolves ticket 11582.
15058 - A new AccountingRule option lets Relays set whether they'd like
15059 AccountingMax to be applied separately to inbound and outbound
15060 traffic, or applied to the sum of inbound and outbound traffic.
15061 Resolves ticket 961. Patch by "chobe".
15062 - When identity keypair is generated for first time, log a
15063 congratulatory message that links to the new relay lifecycle
15064 document. Implements feature 10427.
15066 o Minor features (security, memory wiping):
15067 - Ensure we securely wipe keys from memory after
15068 crypto_digest_get_digest and init_curve25519_keypair_from_file
15069 have finished using them. Resolves ticket 13477.
15071 o Minor features (security, out-of-memory handling):
15072 - When handling an out-of-memory condition, allocate less memory for
15073 temporary data structures. Fixes issue 10115.
15074 - When handling an out-of-memory condition, consider more types of
15075 buffers, including those on directory connections, and zlib
15076 buffers. Resolves ticket 11792.
15078 o Minor features (stability):
15079 - Add assertions in our hash-table iteration code to check for
15080 corrupted values that could cause infinite loops. Closes
15083 o Minor features (systemd):
15084 - Various improvements and modernizations in systemd hardening
15085 support. Closes ticket 13805. Patch from Craig Andrews.
15086 - Where supported, when running with systemd, report successful
15087 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
15088 - When running with systemd, support systemd watchdog messages. Part
15089 of ticket 11016. Patch by Michael Scherer.
15091 o Minor features (testing networks):
15092 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
15093 the "Exit" flag regardless of their uptime, bandwidth, or exit
15094 policy. TestingTorNetwork must be set for this option to have any
15095 effect. Previously, authorities would take up to 35 minutes to
15096 give nodes the Exit flag in a test network. Partially implements
15098 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
15099 and the default on a testing network to 2 minutes. Drop the
15100 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
15101 keep the default on a testing network at 30 seconds. This reduces
15102 HS bootstrap time to around 25 seconds. Also, change the default
15103 time in test-network.sh to match. Closes ticket 13401. Patch
15105 - Create TestingDirAuthVoteHSDir to correspond to
15106 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
15107 HSDir flag for the listed relays regardless of uptime or ORPort
15108 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
15109 Partial implementation for ticket 14067. Patch by "teor".
15111 o Minor features (tor2web mode):
15112 - Introduce the config option Tor2webRendezvousPoints, which allows
15113 clients in Tor2webMode to select a specific Rendezvous Point to be
15114 used in HS circuits. This might allow better performance for
15115 Tor2Web nodes. Implements ticket 12844.
15117 o Minor features (transparent proxy):
15118 - Update the transparent proxy option checks to allow for both ipfw
15119 and pf on OS X. Closes ticket 14002.
15120 - Use the correct option when using IPv6 with transparent proxy
15121 support on Linux. Resolves 13808. Patch by Francisco Blas
15124 o Minor features (validation):
15125 - Check all date/time values passed to tor_timegm and
15126 parse_rfc1123_time for validity, taking leap years into account.
15127 Improves HTTP header validation. Implemented with bug 13476.
15128 - In correct_tm(), limit the range of values returned by system
15129 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
15130 This means we don't have to deal with negative or too large dates,
15131 even if a clock is wrong. Otherwise we might fail to read a file
15132 written by us which includes such a date. Fixes bug 13476.
15133 - Stop allowing invalid address patterns like "*/24" that contain
15134 both a wildcard address and a bit prefix length. This affects all
15135 our address-range parsing code. Fixes bug 7484; bugfix
15138 o Minor bugfixes (bridge clients):
15139 - When configured to use a bridge without an identity digest (not
15140 recommended), avoid launching an extra channel to it when
15141 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
15143 o Minor bugfixes (bridges):
15144 - When DisableNetwork is set, do not launch pluggable transport
15145 plugins, and if any are running, terminate them. Fixes bug 13213;
15146 bugfix on 0.2.3.6-alpha.
15148 o Minor bugfixes (C correctness):
15149 - Fix several instances of possible integer overflow/underflow/NaN.
15150 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
15152 - In circuit_build_times_calculate_timeout() in circuitstats.c,
15153 avoid dividing by zero in the pareto calculations. This traps
15154 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
15156 - Fix an integer overflow in format_time_interval(). Fixes bug
15157 13393; bugfix on 0.2.0.10-alpha.
15158 - Set the correct day of year value when the system's localtime(_r)
15159 or gmtime(_r) functions fail to set struct tm. Not externally
15160 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
15161 - Avoid unlikely signed integer overflow in tor_timegm on systems
15162 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
15164 o Minor bugfixes (certificate handling):
15165 - If an authority operator accidentally makes a signing certificate
15166 with a future publication time, do not discard its real signing
15167 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
15168 - Remove any old authority certificates that have been superseded
15169 for at least two days. Previously, we would keep superseded
15170 certificates until they expired, if they were published close in
15171 time to the certificate that superseded them. Fixes bug 11454;
15172 bugfix on 0.2.1.8-alpha.
15174 o Minor bugfixes (client):
15175 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
15176 BadExit flag are not considered worthy candidates. Fixes bug
15177 13066; bugfix on 0.1.2.3-alpha.
15178 - Use the consensus schedule for downloading consensuses, and not
15179 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
15180 - Handle unsupported or malformed SOCKS5 requests properly by
15181 responding with the appropriate error message before closing the
15182 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
15184 o Minor bugfixes (client, automapping):
15185 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
15186 no value follows the option. Fixes bug 14142; bugfix on
15187 0.2.4.7-alpha. Patch by "teor".
15188 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
15189 14195; bugfix on 0.1.0.1-rc.
15190 - Prevent changes to other options from removing the wildcard value
15191 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
15193 - Allow MapAddress and AutomapHostsOnResolve to work together when
15194 an address is mapped into another address type (like .onion) that
15195 must be automapped at resolve time. Fixes bug 7555; bugfix
15198 o Minor bugfixes (client, bridges):
15199 - When we are using bridges and we had a network connectivity
15200 problem, only retry connecting to our currently configured
15201 bridges, not all bridges we know about and remember using. Fixes
15202 bug 14216; bugfix on 0.2.2.17-alpha.
15204 o Minor bugfixes (client, DNS):
15205 - Report the correct cached DNS expiration times on SOCKS port or in
15206 DNS replies. Previously, we would report everything as "never
15207 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
15208 - Avoid a small memory leak when we find a cached answer for a
15209 reverse DNS lookup in a client-side DNS cache. (Remember, client-
15210 side DNS caching is off by default, and is not recommended.) Fixes
15211 bug 14259; bugfix on 0.2.0.1-alpha.
15213 o Minor bugfixes (client, IPv6):
15214 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
15215 flag is not set; and not because the NoIPv4Traffic flag was set.
15216 Previously we'd looked at the NoIPv4Traffic flag for both types of
15217 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
15219 o Minor bugfixes (client, microdescriptors):
15220 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
15221 computing which microdescriptors to download. This keeps us from
15222 erroneous download behavior if two microdescriptor digests ever
15223 have the same first 160 bits. Fixes part of bug 13399; bugfix
15225 - Reset a router's status if its microdescriptor digest changes,
15226 even if the first 160 bits remain the same. Fixes part of bug
15227 13399; bugfix on 0.2.3.1-alpha.
15229 o Minor bugfixes (client, torrc):
15230 - Stop modifying the value of our DirReqStatistics torrc option just
15231 because we're not a bridge or relay. This bug was causing Tor
15232 Browser users to write "DirReqStatistics 0" in their torrc files
15233 as if they had chosen to change the config. Fixes bug 4244; bugfix
15235 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
15236 that our options have changed every time we SIGHUP. Fixes bug
15237 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
15239 o Minor bugfixes (compilation):
15240 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
15242 - Silence clang warnings under --enable-expensive-hardening,
15243 including implicit truncation of 64 bit values to 32 bit, const
15244 char assignment to self, tautological compare, and additional
15245 parentheses around equality tests. Fixes bug 13577; bugfix
15247 - Fix a clang warning about checking whether an address in the
15248 middle of a structure is NULL. Fixes bug 14001; bugfix
15250 - The address of an array in the middle of a structure will always
15251 be non-NULL. clang recognises this and complains. Disable the
15252 tautologous and redundant check to silence this warning. Fixes bug
15253 14001; bugfix on 0.2.1.2-alpha.
15254 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
15255 Addresses ticket 14188.
15256 - Build without warnings with the stock OpenSSL srtp.h header, which
15257 has a duplicate declaration of SSL_get_selected_srtp_profile().
15258 Fixes bug 14220; this is OpenSSL's bug, not ours.
15259 - Do not compile any code related to Tor2Web mode when Tor2Web mode
15260 is not enabled at compile time. Previously, this code was included
15261 in a disabled state. See discussion on ticket 12844.
15262 - Allow our configure script to build correctly with autoconf 2.62
15263 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
15264 - Improve the error message from ./configure to make it clear that
15265 when asciidoc has not been found, the user will have to either add
15266 --disable-asciidoc argument or install asciidoc. Resolves
15269 o Minor bugfixes (controller):
15270 - Report "down" in response to the "GETINFO entry-guards" command
15271 when relays are down with an unreachable_since value. Previously,
15272 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
15273 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
15274 14116; bugfix on 0.2.2.9-alpha.
15276 o Minor bugfixes (controller):
15277 - Return an error when the second or later arguments of the
15278 "setevents" controller command are invalid events. Previously we
15279 would return success while silently skipping invalid events. Fixes
15280 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
15282 o Minor bugfixes (directory authority):
15283 - Allow directory authorities to fetch more data from one another if
15284 they find themselves missing lots of votes. Previously, they had
15285 been bumping against the 10 MB queued data limit. Fixes bug 14261;
15286 bugfix on 0.1.2.5-alpha.
15287 - Do not attempt to download extrainfo documents which we will be
15288 unable to validate with a matching server descriptor. Fixes bug
15289 13762; bugfix on 0.2.0.1-alpha.
15290 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
15291 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
15292 - Enlarge the buffer to read bwauth generated files to avoid an
15293 issue when parsing the file in dirserv_read_measured_bandwidths().
15294 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
15295 - When running as a v3 directory authority, advertise that you serve
15296 extra-info documents so that clients who want them can find them
15297 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
15299 o Minor bugfixes (directory system):
15300 - Always believe that v3 directory authorities serve extra-info
15301 documents, whether they advertise "caches-extra-info" or not.
15302 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
15303 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
15304 Previously, directories offering BRIDGE_DIRINFO and some other
15305 flag (i.e. microdescriptors or extrainfo) would be ignored when
15306 looking for bridges. Partially fixes bug 13163; bugfix
15309 o Minor bugfixes (file handling):
15310 - Stop failing when key files are zero-length. Instead, generate new
15311 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
15312 on all versions of Tor. Patch by "teor".
15313 - Stop generating a fresh .old RSA onion key file when the .old file
15314 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
15315 - Avoid overwriting .old key files with empty key files.
15316 - Skip loading zero-length extrainfo store, router store, stats,
15317 state, and key files.
15318 - Avoid crashing when trying to reload a torrc specified as a
15319 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
15322 o Minor bugfixes (hidden services):
15323 - Close the introduction circuit when we have no more usable intro
15324 points, instead of waiting for it to time out. This also ensures
15325 that no follow-up HS descriptor fetch is triggered when the
15326 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
15327 - When fetching a hidden service descriptor for a down service that
15328 was recently up, do not keep refetching until we try the same
15329 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
15330 - Correctly send a controller event when we find that a rendezvous
15331 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
15332 - Pre-check directory permissions for new hidden-services to avoid
15333 at least one case of "Bug: Acting on config options left us in a
15334 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
15335 - When fetching hidden service descriptors, we now check not only
15336 for whether we got the hidden service we had in mind, but also
15337 whether we got the particular descriptors we wanted. This prevents
15338 a class of inefficient but annoying DoS attacks by hidden service
15339 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
15342 o Minor bugfixes (Linux seccomp2 sandbox):
15343 - Make transparent proxy support work along with the seccomp2
15344 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
15345 by Francisco Blas Izquierdo Riera.
15346 - Fix a memory leak in tor-resolve when running with the sandbox
15347 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
15348 - Allow glibc fatal errors to be sent to stderr before Tor exits.
15349 Previously, glibc would try to write them to /dev/tty, and the
15350 sandbox would trap the call and make Tor exit prematurely. Fixes
15351 bug 14759; bugfix on 0.2.5.1-alpha.
15353 o Minor bugfixes (logging):
15354 - Avoid crashing when there are more log domains than entries in
15355 domain_list. Bugfix on 0.2.3.1-alpha.
15356 - Downgrade warnings about RSA signature failures to info log level.
15357 Emit a warning when an extra info document is found incompatible
15358 with a corresponding router descriptor. Fixes bug 9812; bugfix
15360 - Make connection_ap_handshake_attach_circuit() log the circuit ID
15361 correctly. Fixes bug 13701; bugfix on 0.0.6.
15363 o Minor bugfixes (networking):
15364 - Check for orconns and use connection_or_close_for_error() rather
15365 than connection_mark_for_close() directly in the getsockopt()
15366 failure case of connection_handle_write_impl(). Fixes bug 11302;
15367 bugfix on 0.2.4.4-alpha.
15369 o Minor bugfixes (parsing):
15370 - Stop accepting milliseconds (or other junk) at the end of
15371 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
15372 - Support two-number and three-number version numbers correctly, in
15373 case we change the Tor versioning system in the future. Fixes bug
15374 13661; bugfix on 0.0.8pre1.
15376 o Minor bugfixes (portability):
15377 - Fix the ioctl()-based network interface lookup code so that it
15378 will work on systems that have variable-length struct ifreq, for
15380 - Use the correct datatype in the SipHash-2-4 function to prevent
15381 compilers from assuming any sort of alignment. Fixes bug 15436;
15382 bugfix on 0.2.5.3-alpha.
15384 o Minor bugfixes (preventative security, C safety):
15385 - When reading a hexadecimal, base-32, or base-64 encoded value from
15386 a string, always overwrite the whole output buffer. This prevents
15387 some bugs where we would look at (but fortunately, not reveal)
15388 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
15390 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
15391 just the part that's used. This makes it harder for data leak bugs
15392 to occur in the event of other programming failures. Resolves
15395 o Minor bugfixes (relay):
15396 - When generating our family list, remove spaces from around the
15397 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
15398 - If our previous bandwidth estimate was 0 bytes, allow publishing a
15399 new relay descriptor immediately. Fixes bug 13000; bugfix
15402 o Minor bugfixes (shutdown):
15403 - When shutting down, always call event_del() on lingering read or
15404 write events before freeing them. Otherwise, we risk double-frees
15405 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
15408 o Minor bugfixes (small memory leaks):
15409 - Avoid leaking memory when using IPv6 virtual address mappings.
15410 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
15413 o Minor bugfixes (statistics):
15414 - Increase period over which bandwidth observations are aggregated
15415 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
15417 o Minor bugfixes (systemd support):
15418 - Run correctly under systemd with the RunAsDaemon option set. Fixes
15419 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
15420 - Inform the systemd supervisor about more changes in the Tor
15421 process status. Implements part of ticket 14141. Patch from
15424 o Minor bugfixes (testing networks):
15425 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
15426 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
15427 - Stop using the default authorities in networks which provide both
15428 AlternateDirAuthority and AlternateBridgeAuthority. Partially
15429 fixes bug 13163; bugfix on 0.2.0.13-alpha.
15431 o Minor bugfixes (testing networks, fast startup):
15432 - Allow Tor to build circuits using a consensus with no exits. If
15433 the consensus has no exits (typical of a bootstrapping test
15434 network), allow Tor to build circuits once enough descriptors have
15435 been downloaded. This assists in bootstrapping a testing Tor
15436 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
15438 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
15439 header to directory servers. This allows us to obtain consensuses
15440 promptly when the consensus interval is very short. This assists
15441 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
15442 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
15443 - Stop assuming that private addresses are local when checking
15444 reachability in a TestingTorNetwork. Instead, when testing, assume
15445 all OR connections are remote. (This is necessary due to many test
15446 scenarios running all relays on localhost.) This assists in
15447 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
15448 0.1.0.1-rc. Patch by "teor".
15449 - Avoid building exit circuits from a consensus with no exits. Now
15450 thanks to our fix for 13718, we accept a no-exit network as not
15451 wholly lost, but we need to remember not to try to build exit
15452 circuits on it. Closes ticket 13814; patch by "teor".
15453 - Stop requiring exits to have non-zero bandwithcapacity in a
15454 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
15455 ignore exit bandwidthcapacity. This assists in bootstrapping a
15456 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
15457 on 0.2.0.3-alpha. Patch by "teor".
15458 - Add "internal" to some bootstrap statuses when no exits are
15459 available. If the consensus does not contain Exits, Tor will only
15460 build internal circuits. In this case, relevant statuses will
15461 contain the word "internal" as indicated in the Tor control-
15462 spec.txt. When bootstrap completes, Tor will be ready to build
15463 internal circuits. If a future consensus contains Exits, exit
15464 circuits may become available. Fixes part of bug 13718; bugfix on
15465 0.2.4.10-alpha. Patch by "teor".
15466 - Decrease minimum consensus interval to 10 seconds when
15467 TestingTorNetwork is set, or 5 seconds for the first consensus.
15468 Fix assumptions throughout the code that assume larger intervals.
15469 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
15471 - Avoid excluding guards from path building in minimal test
15472 networks, when we're in a test network and excluding guards would
15473 exclude all relays. This typically occurs in incredibly small tor
15474 networks, and those using "TestingAuthVoteGuard *". Fixes part of
15475 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
15477 o Minor bugfixes (testing):
15478 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
15479 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
15480 - Stop spawn test failures due to a race condition between the
15481 SIGCHLD handler updating the process status, and the test reading
15482 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
15483 - Avoid passing an extra backslash when creating a temporary
15484 directory for running the unit tests on Windows. Fixes bug 12392;
15485 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
15487 o Minor bugfixes (TLS):
15488 - Check more thoroughly throughout the TLS code for possible
15489 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
15491 o Minor bugfixes (transparent proxy):
15492 - Use getsockname, not getsockopt, to retrieve the address for a
15493 TPROXY-redirected connection. Fixes bug 13796; bugfix
15496 o Minor bugfixes (windows):
15497 - Remove code to special-case handling of NTE_BAD_KEYSET when
15498 acquiring windows CryptoAPI context. This error can't actually
15499 occur for the parameters we're providing. Fixes bug 10816; bugfix
15502 o Minor bugfixes (zlib):
15503 - Avoid truncating a zlib stream when trying to finalize it with an
15504 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
15506 o Code simplification and refactoring:
15507 - Change the entry_is_live() function to take named bitfield
15508 elements instead of an unnamed list of booleans. Closes
15510 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
15511 Resolves ticket 12205.
15512 - Use calloc and reallocarray functions instead of multiply-
15513 then-malloc. This makes it less likely for us to fall victim to an
15514 integer overflow attack when allocating. Resolves ticket 12855.
15515 - Use the standard macro name SIZE_MAX, instead of our
15517 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
15518 functions which take them as arguments. Replace 0 with NO_DIRINFO
15519 in a function call for clarity. Seeks to prevent future issues
15521 - Avoid 4 null pointer errors under clang static analysis by using
15522 tor_assert() to prove that the pointers aren't null. Fixes
15524 - Rework the API of policies_parse_exit_policy() to use a bitmask to
15525 represent parsing options, instead of a confusing mess of
15526 booleans. Resolves ticket 8197.
15527 - Introduce a helper function to parse ExitPolicy in
15528 or_options_t structure.
15529 - Move fields related to isolating and configuring client ports into
15530 a shared structure. Previously, they were duplicated across
15531 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
15532 to copy them correctly had been the cause of at least one bug in
15533 the past. Closes ticket 8546.
15534 - Refactor the get_interface_addresses_raw() doom-function into
15535 multiple smaller and simpler subfunctions. Cover the resulting
15536 subfunctions with unit-tests. Fixes a significant portion of
15538 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
15539 only for version <= 0.2.2.24 which is now deprecated. Closes
15541 - Remove a test for a long-defunct broken version-one
15543 - Refactor main loop to extract the 'loop' part. This makes it
15544 easier to run Tor under Shadow. Closes ticket 15176.
15545 - Stop using can_complete_circuits as a global variable; access it
15546 with a function instead.
15547 - Avoid using operators directly as macro arguments: this lets us
15548 apply coccinelle transformations to our codebase more directly.
15549 Closes ticket 13172.
15550 - Combine the functions used to parse ClientTransportPlugin and
15551 ServerTransportPlugin into a single function. Closes ticket 6456.
15552 - Add inline functions and convenience macros for inspecting channel
15553 state. Refactor the code to use convenience macros instead of
15554 checking channel state directly. Fixes issue 7356.
15555 - Document all members of was_router_added_t and rename
15556 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
15557 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
15558 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
15559 constant instead of hardcoded value. Fixes issue 13840.
15560 - Refactor our generic strmap and digestmap types into a single
15561 implementation, so that we can add a new digest256map
15565 - Add a doc/TUNING document with tips for handling large numbers of
15566 TCP connections when running busy Tor relay. Update the warning
15567 message to point to this file when running out of sockets
15568 operating system is allowing to use simultaneously. Resolves
15570 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
15571 for writing the OpenBSD-specific tips. Resolves ticket 13702.
15572 - Make the tor-resolve documentation match its help string and its
15573 options. Resolves part of ticket 14325.
15574 - Log a more useful error message from tor-resolve when failing to
15575 look up a hidden service address. Resolves part of ticket 14325.
15576 - Document the bridge-authority-only 'networkstatus-bridges' file.
15577 Closes ticket 13713; patch from "tom".
15578 - Fix typo in PredictedPortsRelevanceTime option description in
15579 manpage. Resolves issue 13707.
15580 - Stop suggesting that users specify relays by nickname: it isn't a
15581 good idea. Also, properly cross-reference how to specify relays in
15582 all parts of manual documenting options that take a list of
15583 relays. Closes ticket 13381.
15584 - Clarify the HiddenServiceDir option description in manpage to make
15585 it clear that relative paths are taken with respect to the current
15586 working directory. Also clarify that this behavior is not
15587 guaranteed to remain indefinitely. Fixes issue 13913.
15589 o Distribution (systemd):
15590 - systemd unit file: only allow tor to write to /var/lib/tor and
15591 /var/log/tor. The rest of the filesystem is accessible for reading
15592 only. Patch by intrigeri; resolves ticket 12751.
15593 - systemd unit file: ensure that the process and all its children
15594 can never gain new privileges. Patch by intrigeri; resolves
15596 - systemd unit file: set up /var/run/tor as writable for the Tor
15597 service. Patch by intrigeri; resolves ticket 13196.
15599 o Downgraded warnings:
15600 - Don't warn when we've attempted to contact a relay using the wrong
15601 ntor onion key. Closes ticket 9635.
15604 - Remove some lingering dead code that once supported mempools.
15605 Mempools were disabled by default in 0.2.5, and removed entirely
15606 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
15609 o Removed features (directory authorities):
15610 - Remove code that prevented authorities from listing Tor relays
15611 affected by CVE-2011-2769 as guards. These relays are already
15612 rejected altogether due to the minimum version requirement of
15613 0.2.3.16-alpha. Closes ticket 13152.
15614 - The "AuthDirRejectUnlisted" option no longer has any effect, as
15615 the fingerprints file (approved-routers) has been deprecated.
15616 - Directory authorities do not support being Naming dirauths anymore.
15617 The "NamingAuthoritativeDir" config option is now obsolete.
15618 - Directory authorities do not support giving out the BadDirectory
15620 - Directory authorities no longer advertise or support consensus
15621 methods 1 through 12 inclusive. These consensus methods were
15622 obsolete and/or insecure: maintaining the ability to support them
15623 served no good purpose. Implements part of proposal 215; closes
15626 o Removed features:
15627 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
15628 longer silently accepted as an alias for "ExitNodes".
15629 - The --enable-mempool and --enable-buf-freelists options, which
15630 were originally created to work around bad malloc implementations,
15631 no longer exist. They were off-by-default in 0.2.5. Closes
15633 - We no longer remind the user about configuration options that have
15634 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
15635 - Remove our old, non-weighted bandwidth-based node selection code.
15636 Previously, we used it as a fallback when we couldn't perform
15637 weighted bandwidth-based node selection. But that would only
15638 happen in the cases where we had no consensus, or when we had a
15639 consensus generated by buggy or ancient directory authorities. In
15640 either case, it's better to use the more modern, better maintained
15641 algorithm, with reasonable defaults for the weights. Closes
15643 - Remove the --disable-curve25519 configure option. Relays and
15644 clients now are required to support curve25519 and the
15646 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
15647 used to be deprecated synonyms for "StrictNodes", are now marked
15648 obsolete. Resolves ticket 12226.
15649 - Clients don't understand the BadDirectory flag in the consensus
15650 anymore, and ignore it.
15652 o Removed platform support:
15653 - We no longer include special code to build on Windows CE; as far
15654 as we know, nobody has used Tor on Windows CE in a very long time.
15655 Closes ticket 11446.
15657 o Testing (test-network.sh):
15658 - Stop using "echo -n", as some shells' built-in echo doesn't
15659 support "-n". Instead, use "/bin/echo -n". Partially fixes
15661 - Stop an apparent test-network hang when used with make -j2. Fixes
15663 - Add a --delay option to test-network.sh, which configures the
15664 delay before the chutney network tests for data transmission.
15665 Partially implements ticket 13161.
15668 - Test that tor does not fail when key files are zero-length. Check
15669 that tor generates new keys, and overwrites the empty key files.
15670 - Test that tor generates new keys when keys are missing
15671 (existing behavior).
15672 - Test that tor does not overwrite key files that already contain
15673 data (existing behavior). Tests bug 13111. Patch by "teor".
15674 - New "make test-stem" target to run stem integration tests.
15675 Requires that the "STEM_SOURCE_DIR" environment variable be set.
15676 Closes ticket 14107.
15677 - Make the test_cmdline_args.py script work correctly on Windows.
15678 Patch from Gisle Vanem.
15679 - Move the slower unit tests into a new "./src/test/test-slow"
15680 binary that can be run independently of the other tests. Closes
15682 - New tests for many parts of channel, relay, and circuitmux
15683 functionality. Code by Andrea; part of 9262.
15684 - New tests for parse_transport_line(). Part of ticket 6456.
15685 - In the unit tests, use chgrp() to change the group of the unit
15686 test temporary directory to the current user, so that the sticky
15687 bit doesn't interfere with tests that check directory groups.
15689 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
15691 - Refactor the function that chooses guard nodes so that it can more
15692 easily be tested; write some tests for it.
15693 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
15694 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
15695 - Create unit tests for format_time_interval(). With bug 13393.
15696 - Add unit tests for tor_timegm signed overflow, tor_timegm and
15697 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
15698 tests (visible) fixes in bug 13476.
15699 - Add a "coverage-html" make target to generate HTML-visualized
15700 coverage results when building with --enable-coverage. (Requires
15701 lcov.) Patch from Kevin Murray.
15702 - Enable the backtrace handler (where supported) when running the
15704 - Revise all unit tests that used the legacy test_* macros to
15705 instead use the recommended tt_* macros. This patch was generated
15706 with coccinelle, to avoid manual errors. Closes ticket 13119.
15708 Changes in version 0.2.5.11 - 2015-03-17
15709 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
15711 It backports several bugfixes from the 0.2.6 branch, including a
15712 couple of medium-level security fixes for relays and exit nodes.
15713 It also updates the list of directory authorities.
15715 o Directory authority changes:
15716 - Remove turtles as a directory authority.
15717 - Add longclaw as a new (v3) directory authority. This implements
15718 ticket 13296. This keeps the directory authority count at 9.
15719 - The directory authority Faravahar has a new IP address. This
15720 closes ticket 14487.
15722 o Major bugfixes (crash, OSX, security):
15723 - Fix a remote denial-of-service opportunity caused by a bug in
15724 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
15727 o Major bugfixes (relay, stability, possible security):
15728 - Fix a bug that could lead to a relay crashing with an assertion
15729 failure if a buffer of exactly the wrong layout was passed to
15730 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
15731 0.2.0.10-alpha. Patch from 'cypherpunks'.
15732 - Do not assert if the 'data' pointer on a buffer is advanced to the
15733 very end of the buffer; log a BUG message instead. Only assert if
15734 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
15736 o Major bugfixes (exit node stability):
15737 - Fix an assertion failure that could occur under high DNS load.
15738 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
15739 diagnosed and fixed by "cypherpunks".
15741 o Major bugfixes (Linux seccomp2 sandbox):
15742 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
15743 crash during attempts to call wait4. Fixes bug 15088; bugfix on
15744 0.2.5.1-alpha. Patch from "sanic".
15746 o Minor features (controller):
15747 - New "GETINFO bw-event-cache" to get information about recent
15748 bandwidth events. Closes ticket 14128. Useful for controllers to
15749 get recent bandwidth history after the fix for ticket 13988.
15751 o Minor features (geoip):
15752 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
15753 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
15756 o Minor bugfixes (client, automapping):
15757 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
15758 no value follows the option. Fixes bug 14142; bugfix on
15759 0.2.4.7-alpha. Patch by "teor".
15760 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
15761 14195; bugfix on 0.1.0.1-rc.
15763 o Minor bugfixes (compilation):
15764 - Build without warnings with the stock OpenSSL srtp.h header, which
15765 has a duplicate declaration of SSL_get_selected_srtp_profile().
15766 Fixes bug 14220; this is OpenSSL's bug, not ours.
15768 o Minor bugfixes (directory authority):
15769 - Allow directory authorities to fetch more data from one another if
15770 they find themselves missing lots of votes. Previously, they had
15771 been bumping against the 10 MB queued data limit. Fixes bug 14261;
15772 bugfix on 0.1.2.5-alpha.
15773 - Enlarge the buffer to read bwauth generated files to avoid an
15774 issue when parsing the file in dirserv_read_measured_bandwidths().
15775 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
15777 o Minor bugfixes (statistics):
15778 - Increase period over which bandwidth observations are aggregated
15779 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
15781 o Minor bugfixes (preventative security, C safety):
15782 - When reading a hexadecimal, base-32, or base-64 encoded value from
15783 a string, always overwrite the whole output buffer. This prevents
15784 some bugs where we would look at (but fortunately, not reveal)
15785 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
15789 Changes in version 0.2.4.26 - 2015-03-17
15790 Tor 0.2.4.26 includes an updated list of directory authorities. It
15791 also backports a couple of stability and security bugfixes from 0.2.5
15794 o Directory authority changes:
15795 - Remove turtles as a directory authority.
15796 - Add longclaw as a new (v3) directory authority. This implements
15797 ticket 13296. This keeps the directory authority count at 9.
15798 - The directory authority Faravahar has a new IP address. This
15799 closes ticket 14487.
15801 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
15802 - Fix an assertion failure that could occur under high DNS load.
15803 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
15804 diagnosed and fixed by "cypherpunks".
15806 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
15807 - Fix a bug that could lead to a relay crashing with an assertion
15808 failure if a buffer of exactly the wrong layout was passed to
15809 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
15810 0.2.0.10-alpha. Patch from 'cypherpunks'.
15811 - Do not assert if the 'data' pointer on a buffer is advanced to the
15812 very end of the buffer; log a BUG message instead. Only assert if
15813 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
15815 o Minor features (geoip):
15816 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
15817 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
15820 Changes in version 0.2.5.10 - 2014-10-24
15821 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
15823 It adds several new security features, including improved
15824 denial-of-service resistance for relays, new compiler hardening
15825 options, and a system-call sandbox for hardened installations on Linux
15826 (requires seccomp2). The controller protocol has several new features,
15827 resolving IPv6 addresses should work better than before, and relays
15828 should be a little more CPU-efficient. We've added support for more
15829 OpenBSD and FreeBSD transparent proxy types. We've improved the build
15830 system and testing infrastructure to allow unit testing of more parts
15831 of the Tor codebase. Finally, we've addressed several nagging pluggable
15832 transport usability issues, and included numerous other small bugfixes
15833 and features mentioned below.
15835 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
15836 have accumulated many known flaws; everyone should upgrade.
15838 o Major features (security):
15839 - The ntor handshake is now on-by-default, no matter what the
15840 directory authorities recommend. Implements ticket 8561.
15841 - Make the "tor-gencert" tool used by directory authority operators
15842 create 2048-bit signing keys by default (rather than 1024-bit, since
15843 1024-bit is uncomfortably small these days). Addresses ticket 10324.
15844 - Warn about attempts to run hidden services and relays in the same
15845 process: that's probably not a good idea. Closes ticket 12908.
15846 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
15847 today support TLS 1.0 or later, so we can safely turn off support
15848 for this old (and insecure) protocol. Fixes bug 13426.
15850 o Major features (relay security, DoS-resistance):
15851 - When deciding whether we have run out of memory and we need to
15852 close circuits, also consider memory allocated in buffers for
15853 streams attached to each circuit.
15855 This change, which extends an anti-DoS feature introduced in
15856 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
15857 better resist more memory-based DoS attacks than before. Since the
15858 MaxMemInCellQueues option now applies to all queues, it is renamed
15859 to MaxMemInQueues. This feature fixes bug 10169.
15860 - Avoid hash-flooding denial-of-service attacks by using the secure
15861 SipHash-2-4 hash function for our hashtables. Without this
15862 feature, an attacker could degrade performance of a targeted
15863 client or server by flooding their data structures with a large
15864 number of entries to be stored at the same hash table position,
15865 thereby slowing down the Tor instance. With this feature, hash
15866 table positions are derived from a randomized cryptographic key,
15867 and an attacker cannot predict which entries will collide. Closes
15869 - If you don't specify MaxMemInQueues yourself, Tor now tries to
15870 pick a good value based on your total system memory. Previously,
15871 the default was always 8 GB. You can still override the default by
15872 setting MaxMemInQueues yourself. Resolves ticket 11396.
15874 o Major features (bridges and pluggable transports):
15875 - Add support for passing arguments to managed pluggable transport
15876 proxies. Implements ticket 3594.
15877 - Bridges now track GeoIP information and the number of their users
15878 even when pluggable transports are in use, and report usage
15879 statistics in their extra-info descriptors. Resolves tickets 4773
15881 - Don't launch pluggable transport proxies if we don't have any
15882 bridges configured that would use them. Now we can list many
15883 pluggable transports, and Tor will dynamically start one when it
15884 hears a bridge address that needs it. Resolves ticket 5018.
15885 - The bridge directory authority now assigns status flags (Stable,
15886 Guard, etc) to bridges based on thresholds calculated over all
15887 Running bridges. Now bridgedb can finally make use of its features
15888 to e.g. include at least one Stable bridge in its answers. Fixes
15891 o Major features (controller):
15892 - Extend ORCONN controller event to include an "ID" parameter,
15893 and add four new controller event types CONN_BW, CIRC_BW,
15894 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
15895 The new events are emitted in private Tor networks only, with the
15896 goal of being able to better track performance and load during
15897 full-network simulations. Implements proposal 218 and ticket 7359.
15899 o Major features (relay performance):
15900 - Speed up server-side lookups of rendezvous and introduction point
15901 circuits by using hashtables instead of linear searches. These
15902 functions previously accounted between 3 and 7% of CPU usage on
15903 some busy relays. Resolves ticket 9841.
15904 - Avoid wasting CPU when extending a circuit over a channel that is
15905 nearly out of circuit IDs. Previously, we would do a linear scan
15906 over possible circuit IDs before finding one or deciding that we
15907 had exhausted our possibilities. Now, we try at most 64 random
15908 circuit IDs before deciding that we probably won't succeed. Fixes
15909 a possible root cause of ticket 11553.
15911 o Major features (seccomp2 sandbox, Linux only):
15912 - Use the seccomp2 syscall filtering facility on Linux to limit
15913 which system calls Tor can invoke. This is an experimental,
15914 Linux-only feature to provide defense-in-depth against unknown
15915 attacks. To try turning it on, set "Sandbox 1" in your torrc
15916 file. Please be ready to report bugs. We hope to add support
15917 for better sandboxing in the future, including more fine-grained
15918 filters, better division of responsibility, and support for more
15919 platforms. This work has been done by Cristian-Matei Toader for
15920 Google Summer of Code. Resolves tickets 11351 and 11465.
15922 o Major features (testing networks):
15923 - Make testing Tor networks bootstrap better: lower directory fetch
15924 retry schedules and maximum interval without directory requests,
15925 and raise maximum download tries. Implements ticket 6752.
15926 - Add make target 'test-network' to run tests on a Chutney network.
15927 Implements ticket 8530.
15929 o Major features (other):
15930 - On some platforms (currently: recent OSX versions, glibc-based
15931 platforms that support the ELF format, and a few other
15932 Unix-like operating systems), Tor can now dump stack traces
15933 when a crash occurs or an assertion fails. By default, traces
15934 are dumped to stderr (if possible) and to any logs that are
15935 reporting errors. Implements ticket 9299.
15937 o Deprecated versions:
15938 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
15939 attention for some while.
15941 o Major bugfixes (security, directory authorities):
15942 - Directory authorities now include a digest of each relay's
15943 identity key as a part of its microdescriptor.
15945 This is a workaround for bug 11743 (reported by "cypherpunks"),
15946 where Tor clients do not support receiving multiple
15947 microdescriptors with the same SHA256 digest in the same
15948 consensus. When clients receive a consensus like this, they only
15949 use one of the relays. Without this fix, a hostile relay could
15950 selectively disable some client use of target relays by
15951 constructing a router descriptor with a different identity and the
15952 same microdescriptor parameters and getting the authorities to
15953 list it in a microdescriptor consensus. This fix prevents an
15954 attacker from causing a microdescriptor collision, because the
15955 router's identity is not forgeable.
15957 o Major bugfixes (openssl bug workaround):
15958 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
15959 1.0.1j, built with the 'no-ssl3' configuration option. Fixes
15960 bug 13471. This is a workaround for an OpenSSL bug.
15962 o Major bugfixes (client):
15963 - Perform circuit cleanup operations even when circuit
15964 construction operations are disabled (because the network is
15965 disabled, or because there isn't enough directory information).
15966 Previously, when we were not building predictive circuits, we
15967 were not closing expired circuits either. Fixes bug 8387; bugfix on
15968 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
15969 became more strict about when we have "enough directory information
15970 to build circuits".
15972 o Major bugfixes (client, pluggable transports):
15973 - When managing pluggable transports, use OS notification facilities
15974 to learn if they have crashed, and don't attempt to kill any
15975 process that has already exited. Fixes bug 8746; bugfix
15978 o Major bugfixes (relay denial of service):
15979 - Instead of writing destroy cells directly to outgoing connection
15980 buffers, queue them and intersperse them with other outgoing cells.
15981 This can prevent a set of resource starvation conditions where too
15982 many pending destroy cells prevent data cells from actually getting
15983 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
15984 bugfix on 0.2.0.1-alpha.
15986 o Major bugfixes (relay):
15987 - Avoid queuing or sending destroy cells for circuit ID zero when we
15988 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
15989 Found and fixed by "cypherpunks".
15990 - Fix ORPort reachability detection on relays running behind a
15991 proxy, by correctly updating the "local" mark on the controlling
15992 channel when changing the address of an or_connection_t after the
15993 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
15994 - Use a direct dirport connection when uploading non-anonymous
15995 descriptors to the directory authorities. Previously, relays would
15996 incorrectly use tunnel connections under a fairly wide variety of
15997 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
15998 - When a circuit accidentally has the same circuit ID for its
15999 forward and reverse direction, correctly detect the direction of
16000 cells using that circuit. Previously, this bug made roughly one
16001 circuit in a million non-functional. Fixes bug 12195; this is a
16002 bugfix on every version of Tor.
16004 o Minor features (security):
16005 - New --enable-expensive-hardening option to enable security
16006 hardening options that consume nontrivial amounts of CPU and
16007 memory. Right now, this includes AddressSanitizer and UbSan, which
16008 are supported in newer versions of GCC and Clang. Closes ticket
16010 - Authorities now assign the Guard flag to the fastest 25% of the
16011 network (it used to be the fastest 50%). Also raise the consensus
16012 weight that guarantees the Guard flag from 250 to 2000. For the
16013 current network, this results in about 1100 guards, down from 2500.
16014 This step paves the way for moving the number of entry guards
16015 down to 1 (proposal 236) while still providing reasonable expected
16016 performance for most users. Implements ticket 12690.
16018 o Minor features (security, memory management):
16019 - Memory allocation tricks (mempools and buffer freelists) are now
16020 disabled by default. You can turn them back on with
16021 --enable-mempools and --enable-buf-freelists respectively. We're
16022 disabling these features because malloc performance is good enough
16023 on most platforms, and a similar feature in OpenSSL exacerbated
16024 exploitation of the Heartbleed attack. Resolves ticket 11476.
16026 o Minor features (bridge client):
16027 - Report a more useful failure message when we can't connect to a
16028 bridge because we don't have the right pluggable transport
16029 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
16031 o Minor features (bridge):
16032 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
16033 cookie file for the ExtORPort g+r by default.
16035 o Minor features (bridges, pluggable transports):
16036 - Bridges now write the SHA1 digest of their identity key
16037 fingerprint (that is, a hash of a hash of their public key) to
16038 notice-level logs, and to a new hashed-fingerprint file. This
16039 information will help bridge operators look up their bridge in
16040 Globe and similar tools. Resolves ticket 10884.
16041 - Improve the message that Tor displays when running as a bridge
16042 using pluggable transports without an Extended ORPort listener.
16043 Also, log the message in the log file too. Resolves ticket 11043.
16044 - Add threshold cutoffs to the networkstatus document created by
16045 the Bridge Authority. Fixes bug 1117.
16046 - On Windows, spawn background processes using the CREATE_NO_WINDOW
16047 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
16048 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
16049 Vidalia set this option for us.) Implements ticket 10297.
16051 o Minor features (build):
16052 - The configure script has a --disable-seccomp option to turn off
16053 support for libseccomp on systems that have it, in case it (or
16054 Tor's use of it) is broken. Resolves ticket 11628.
16055 - Assume that a user using ./configure --host wants to cross-compile,
16056 and give an error if we cannot find a properly named
16057 tool-chain. Add a --disable-tool-name-check option to proceed
16058 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
16059 - If we run ./configure and the compiler recognizes -fstack-protector
16060 but the linker rejects it, warn the user about a potentially missing
16061 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
16062 - Add support for `--library-versions` flag. Implements ticket 6384.
16063 - Return the "unexpected sendme" warnings to a warn severity, but make
16064 them rate limited, to help diagnose ticket 8093.
16065 - Detect a missing asciidoc, and warn the user about it, during
16066 configure rather than at build time. Fixes issue 6506. Patch from
16069 o Minor features (client):
16070 - Add a new option, PredictedPortsRelevanceTime, to control how long
16071 after having received a request to connect to a given port Tor
16072 will try to keep circuits ready in anticipation of future requests
16073 for that port. Patch from "unixninja92"; implements ticket 9176.
16075 o Minor features (config options and command line):
16076 - Add an --allow-missing-torrc commandline option that tells Tor to
16077 run even if the configuration file specified by -f is not available.
16078 Implements ticket 10060.
16079 - Add support for the TPROXY transparent proxying facility on Linux.
16080 See documentation for the new TransProxyType option for more
16081 details. Implementation by "thomo". Closes ticket 10582.
16083 o Minor features (config options):
16084 - Config (torrc) lines now handle fingerprints which are missing
16085 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
16086 - Support a --dump-config option to print some or all of the
16087 configured options. Mainly useful for debugging the command-line
16088 option parsing code. Helps resolve ticket 4647.
16089 - Raise awareness of safer logging: notify user of potentially
16090 unsafe config options, like logging more verbosely than severity
16091 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
16092 - Add a new configuration option TestingV3AuthVotingStartOffset
16093 that bootstraps a network faster by changing the timing for
16094 consensus votes. Addresses ticket 8532.
16095 - Add a new torrc option "ServerTransportOptions" that allows
16096 bridge operators to pass configuration parameters to their
16097 pluggable transports. Resolves ticket 8929.
16098 - The config (torrc) file now accepts bandwidth and space limits in
16099 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
16100 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
16103 o Minor features (controller):
16104 - Make the entire exit policy available from the control port via
16105 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
16107 - Because of the fix for ticket 11396, the real limit for memory
16108 usage may no longer match the configured MaxMemInQueues value. The
16109 real limit is now exposed via GETINFO limits/max-mem-in-queues.
16110 - Add a new "HS_DESC" controller event that reports activities
16111 related to hidden service descriptors. Resolves ticket 8510.
16112 - New "DROPGUARDS" controller command to forget all current entry
16113 guards. Not recommended for ordinary use, since replacing guards
16114 too frequently makes several attacks easier. Resolves ticket 9934;
16116 - Implement the TRANSPORT_LAUNCHED control port event that
16117 notifies controllers about new launched pluggable
16118 transports. Resolves ticket 5609.
16120 o Minor features (diagnostic):
16121 - When logging a warning because of bug 7164, additionally check the
16122 hash table for consistency (as proposed on ticket 11737). This may
16123 help diagnose bug 7164.
16124 - When we log a heartbeat, log how many one-hop circuits we have
16125 that are at least 30 minutes old, and log status information about
16126 a few of them. This is an attempt to track down bug 8387.
16127 - When encountering an unexpected CR while writing text to a file on
16128 Windows, log the name of the file. Should help diagnosing
16130 - Give more specific warnings when a client notices that an onion
16131 handshake has failed. Fixes ticket 9635.
16132 - Add significant new logging code to attempt to diagnose bug 12184,
16133 where relays seem to run out of available circuit IDs.
16134 - Improve the diagnostic log message for bug 8387 even further to
16135 try to improve our odds of figuring out why one-hop directory
16136 circuits sometimes do not get closed.
16137 - Add more log messages to diagnose bug 7164, which causes
16138 intermittent "microdesc_free() called but md was still referenced"
16139 warnings. We now include more information, to figure out why we
16140 might be cleaning a microdescriptor for being too old if it's
16141 still referenced by a live node_t object.
16142 - Log current accounting state (bytes sent and received + remaining
16143 time for the current accounting period) in the relay's heartbeat
16144 message. Implements ticket 5526; patch from Peter Retzlaff.
16146 o Minor features (geoip):
16147 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
16150 o Minor features (interface):
16151 - Generate a warning if any ports are listed in the SocksPolicy,
16152 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
16153 AuthDirBadExit options. (These options only support address
16154 ranges.) Fixes part of ticket 11108.
16156 o Minor features (kernel API usage):
16157 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
16158 sockets in a single system call. Implements ticket 5129.
16160 o Minor features (log messages):
16161 - When ServerTransportPlugin is set on a bridge, Tor can write more
16162 useful statistics about bridge use in its extrainfo descriptors,
16163 but only if the Extended ORPort ("ExtORPort") is set too. Add a
16164 log message to inform the user in this case. Resolves ticket 9651.
16165 - When receiving a new controller connection, log the origin address.
16166 Resolves ticket 9698; patch from "sigpipe".
16167 - When logging OpenSSL engine status at startup, log the status of
16168 more engines. Fixes ticket 10043; patch from Joshua Datko.
16170 o Minor features (log verbosity):
16171 - Demote the message that we give when a flushing connection times
16172 out for too long from NOTICE to INFO. It was usually meaningless.
16173 Resolves ticket 5286.
16174 - Don't log so many notice-level bootstrapping messages at startup
16175 about downloading descriptors. Previously, we'd log a notice
16176 whenever we learned about more routers. Now, we only log a notice
16177 at every 5% of progress. Fixes bug 9963.
16178 - Warn less verbosely when receiving a malformed
16179 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
16181 o Minor features (performance):
16182 - If we're using the pure-C 32-bit curve25519_donna implementation
16183 of curve25519, build it with the -fomit-frame-pointer option to
16184 make it go faster on register-starved hosts. This improves our
16185 handshake performance by about 6% on i386 hosts without nacl.
16186 Closes ticket 8109.
16188 o Minor features (relay):
16189 - If a circuit timed out for at least 3 minutes, check if we have a
16190 new external IP address, and publish a new descriptor with the new
16191 IP address if it changed. Resolves ticket 2454.
16193 o Minor features (testing):
16194 - If Python is installed, "make check" now runs extra tests beyond
16195 the unit test scripts.
16196 - When bootstrapping a test network, sometimes very few relays get
16197 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
16198 specify a set of relays which should be voted Guard regardless of
16199 their uptime or bandwidth. Addresses ticket 9206.
16201 o Minor features (transparent proxy, *BSD):
16202 - Support FreeBSD's ipfw firewall interface for TransPort ports on
16203 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
16204 10267; patch from "yurivict".
16205 - Support OpenBSD's divert-to rules with the pf firewall for
16206 transparent proxy ports. To enable it, set "TransProxyType
16207 pf-divert". This allows Tor to run a TransPort transparent proxy
16208 port on OpenBSD 4.4 or later without root privileges. See the
16209 pf.conf(5) manual page for information on configuring pf to use
16210 divert-to rules. Closes ticket 10896; patch from Dana Koch.
16212 o Minor bugfixes (bridge client):
16213 - Stop accepting bridge lines containing hostnames. Doing so would
16214 cause clients to perform DNS requests on the hostnames, which was
16215 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
16217 o Minor bugfixes (bridges):
16218 - Avoid potential crashes or bad behavior when launching a
16219 server-side managed proxy with ORPort or ExtORPort temporarily
16220 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
16221 - Fix a bug where the first connection works to a bridge that uses a
16222 pluggable transport with client-side parameters, but we don't send
16223 the client-side parameters on subsequent connections. (We don't
16224 use any pluggable transports with client-side parameters yet,
16225 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
16226 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
16228 o Minor bugfixes (build, auxiliary programs):
16229 - Stop preprocessing the "torify" script with autoconf, since
16230 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
16232 - The tor-fw-helper program now follows the standard convention and
16233 exits with status code "0" on success. Fixes bug 9030; bugfix on
16234 0.2.3.1-alpha. Patch by Arlo Breault.
16235 - Corrected ./configure advice for what openssl dev package you should
16236 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
16238 o Minor bugfixes (client):
16239 - Avoid "Tried to open a socket with DisableNetwork set" warnings
16240 when starting a client with bridges configured and DisableNetwork
16241 set. (Tor launcher starts Tor with DisableNetwork set the first
16242 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
16243 - Improve the log message when we can't connect to a hidden service
16244 because all of the hidden service directory nodes hosting its
16245 descriptor are excluded. Improves on our fix for bug 10722, which
16246 was a bugfix on 0.2.0.10-alpha.
16247 - Raise a control port warning when we fail to connect to all of
16248 our bridges. Previously, we didn't inform the controller, and
16249 the bootstrap process would stall. Fixes bug 11069; bugfix on
16251 - Exit immediately when a process-owning controller exits.
16252 Previously, tor relays would wait for a little while after their
16253 controller exited, as if they had gotten an INT signal -- but this
16254 was problematic, since there was no feedback for the user. To do a
16255 clean shutdown, controllers should send an INT signal and give Tor
16256 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
16257 - Stop attempting to connect to bridges before our pluggable
16258 transports are configured (harmless but resulted in some erroneous
16259 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
16260 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
16261 generating incorrect SOCKS5 responses, and confusing client
16262 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
16264 o Minor bugfixes (client, DNSPort):
16265 - When using DNSPort, try to respond to AAAA requests with AAAA
16266 answers. Previously, we hadn't looked at the request type when
16267 deciding which answer type to prefer. Fixes bug 10468; bugfix on
16269 - When receiving a DNS query for an unsupported record type, reply
16270 with no answer rather than with a NOTIMPL error. This behavior
16271 isn't correct either, but it will break fewer client programs, we
16272 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
16275 o Minor bugfixes (client, logging during bootstrap):
16276 - Only report the first fatal bootstrap error on a given OR
16277 connection. This stops us from telling the controller bogus error
16278 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
16279 - Avoid generating spurious warnings when starting with
16280 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
16283 o Minor bugfixes (closing OR connections):
16284 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
16285 check if it's an or_connection_t and correctly call
16286 connection_or_close_for_error() rather than
16287 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
16289 - When closing all connections on setting DisableNetwork to 1, use
16290 connection_or_close_normally() rather than closing OR connections
16291 out from under the channel layer. Fixes bug 11306; bugfix on
16294 o Minor bugfixes (code correctness):
16295 - Previously we used two temporary files when writing descriptors to
16296 disk; now we only use one. Fixes bug 1376.
16297 - Remove an erroneous (but impossible and thus harmless) pointer
16298 comparison that would have allowed compilers to skip a bounds
16299 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
16300 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
16301 - Fix an always-true assertion in pluggable transports code so it
16302 actually checks what it was trying to check. Fixes bug 10046;
16303 bugfix on 0.2.3.9-alpha. Found by "dcb".
16305 o Minor bugfixes (command line):
16306 - Use a single command-line parser for parsing torrc options on the
16307 command line and for finding special command-line options to avoid
16308 inconsistent behavior for torrc option arguments that have the same
16309 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
16311 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
16312 9573; bugfix on 0.0.9pre5.
16314 o Minor bugfixes (compilation):
16315 - Compile correctly with builds and forks of OpenSSL (such as
16316 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
16317 0.2.1.1-alpha. Patch from "dhill".
16318 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
16319 turned off (that is, without support for v2 link handshakes). Fixes
16320 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
16321 - In routerlist_assert_ok(), don't take the address of a
16322 routerinfo's cache_info member unless that routerinfo is non-NULL.
16323 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
16324 - Fix a large number of false positive warnings from the clang
16325 analyzer static analysis tool. This should make real warnings
16326 easier for clang analyzer to find. Patch from "teor". Closes
16328 - Resolve GCC complaints on OpenBSD about discarding constness in
16329 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
16330 on 0.1.1.23. Patch from Dana Koch.
16331 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
16332 treatment of long and time_t as comparable types. Fixes part of
16333 bug 11633. Patch from Dana Koch.
16334 - When deciding whether to build the 64-bit curve25519
16335 implementation, detect platforms where we can compile 128-bit
16336 arithmetic but cannot link it. Fixes bug 11729; bugfix on
16337 0.2.4.8-alpha. Patch from "conradev".
16338 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
16339 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
16340 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
16342 - Build and run correctly on systems like OpenBSD-current that have
16343 patched OpenSSL to remove get_cipher_by_char and/or its
16344 implementations. Fixes issue 13325.
16346 o Minor bugfixes (controller and command-line):
16347 - If changing a config option via "setconf" fails in a recoverable
16348 way, we used to nonetheless write our new control ports to the
16349 file described by the "ControlPortWriteToFile" option. Now we only
16350 write out that file if we successfully switch to the new config
16351 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
16353 o Minor bugfixes (directory server):
16354 - No longer accept malformed http headers when parsing urls from
16355 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
16356 bugfix on 0.0.6pre1.
16357 - When sending a compressed set of descriptors or microdescriptors,
16358 make sure to finalize the zlib stream. Previously, we would write
16359 all the compressed data, but if the last descriptor we wanted to
16360 send was missing or too old, we would not mark the stream as
16361 finished. This caused problems for decompression tools. Fixes bug
16362 11648; bugfix on 0.1.1.23.
16364 o Minor bugfixes (hidden service):
16365 - Only retry attempts to connect to a chosen rendezvous point 8
16366 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
16368 o Minor bugfixes (interface):
16369 - Reject relative control socket paths and emit a warning. Previously,
16370 single-component control socket paths would be rejected, but Tor
16371 would not log why it could not validate the config. Fixes bug 9258;
16372 bugfix on 0.2.3.16-alpha.
16374 o Minor bugfixes (log messages):
16375 - Fix a bug where clients using bridges would report themselves
16376 as 50% bootstrapped even without a live consensus document.
16377 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
16378 - Suppress a warning where, if there's only one directory authority
16379 in the network, we would complain that votes and signatures cannot
16380 be uploaded to other directory authorities. Fixes bug 10842;
16381 bugfix on 0.2.2.26-beta.
16382 - Report bootstrapping progress correctly when we're downloading
16383 microdescriptors. We had updated our "do we have enough microdescs
16384 to begin building circuits?" logic most recently in 0.2.4.10-alpha
16385 (see bug 5956), but we left the bootstrap status event logic at
16386 "how far through getting 1/4 of them are we?" Fixes bug 9958;
16387 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
16389 o Minor bugfixes (logging):
16390 - Downgrade "Unexpected onionskin length after decryption" warning
16391 to a protocol-warn, since there's nothing relay operators can do
16392 about a client that sends them a malformed create cell. Resolves
16393 bug 12996; bugfix on 0.0.6rc1.
16394 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
16395 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
16396 - When logging information about an EXTEND2 or EXTENDED2 cell, log
16397 their names correctly. Fixes part of bug 12700; bugfix
16399 - When logging information about a relay cell whose command we don't
16400 recognize, log its command as an integer. Fixes part of bug 12700;
16401 bugfix on 0.2.1.10-alpha.
16402 - Escape all strings from the directory connection before logging
16403 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
16404 - Squelch a spurious LD_BUG message "No origin circuit for
16405 successful SOCKS stream" in certain hidden service failure cases;
16407 - Downgrade the severity of the 'unexpected sendme cell from client'
16408 from 'warn' to 'protocol warning'. Closes ticket 8093.
16410 o Minor bugfixes (misc code correctness):
16411 - In munge_extrainfo_into_routerinfo(), check the return value of
16412 memchr(). This would have been a serious issue if we ever passed
16413 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
16415 - On the chance that somebody manages to build Tor on a
16416 platform where time_t is unsigned, correct the way that
16417 microdesc_add_to_cache() handles negative time arguments.
16418 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
16419 - Fix various instances of undefined behavior in channeltls.c,
16420 tor_memmem(), and eventdns.c that would cause us to construct
16421 pointers to memory outside an allocated object. (These invalid
16422 pointers were not accessed, but C does not even allow them to
16423 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
16424 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
16425 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
16426 fix some miscellaneous errors in our tests and codebase. Fixes bug
16427 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
16428 - Always check return values for unlink, munmap, UnmapViewOfFile;
16429 check strftime return values more often. In some cases all we can
16430 do is report a warning, but this may help prevent deeper bugs from
16431 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
16433 - Fix numerous warnings from the clang "scan-build" static analyzer.
16434 Some of these are programming style issues; some of them are false
16435 positives that indicated awkward code; some are undefined behavior
16436 cases related to constructing (but not using) invalid pointers;
16437 some are assumptions about API behavior; some are (harmlessly)
16438 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
16439 correct; and one or two are genuine bugs that weren't reachable
16440 from the rest of the program. Fixes bug 8793; bugfixes on many,
16443 o Minor bugfixes (node selection):
16444 - If ExcludeNodes is set, consider non-excluded hidden service
16445 directory servers before excluded ones. Do not consider excluded
16446 hidden service directory servers at all if StrictNodes is
16447 set. (Previously, we would sometimes decide to connect to those
16448 servers, and then realize before we initiated a connection that
16449 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
16450 Reported by "mr-4".
16451 - If we set the ExitNodes option but it doesn't include any nodes
16452 that have the Exit flag, we would choose not to bootstrap. Now we
16453 bootstrap so long as ExitNodes includes nodes which can exit to
16454 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
16456 o Minor bugfixes (performance):
16457 - Avoid a bug where every successful connection made us recompute
16458 the flag telling us whether we have sufficient information to
16459 build circuits. Previously, we would forget our cached value
16460 whenever we successfully opened a channel (or marked a router as
16461 running or not running for any other reason), regardless of
16462 whether we had previously believed the router to be running. This
16463 forced us to run an expensive update operation far too often.
16464 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
16465 - Avoid using tor_memeq() for checking relay cell integrity. This
16466 removes a possible performance bottleneck. Fixes part of bug
16467 12169; bugfix on 0.2.1.31.
16469 o Minor bugfixes (platform-specific):
16470 - When dumping a malformed directory object to disk, save it in
16471 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
16473 - Don't report failures from make_socket_reuseable() on incoming
16474 sockets on OSX: this can happen when incoming connections close
16475 early. Fixes bug 10081.
16477 o Minor bugfixes (pluggable transports):
16478 - Avoid another 60-second delay when starting Tor in a pluggable-
16479 transport-using configuration when we already have cached
16480 descriptors for our bridges. Fixes bug 11965; bugfix
16483 o Minor bugfixes (protocol correctness):
16484 - When receiving a VERSIONS cell with an odd number of bytes, close
16485 the connection immediately since the cell is malformed. Fixes bug
16486 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
16489 o Minor bugfixes (relay, other):
16490 - We now drop CREATE cells for already-existent circuit IDs and for
16491 zero-valued circuit IDs, regardless of other factors that might
16492 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
16494 - When rejecting DATA cells for stream_id zero, still count them
16495 against the circuit's deliver window so that we don't fail to send
16496 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
16498 o Minor bugfixes (relay, threading):
16499 - Check return code on spawn_func() in cpuworker code, so that we
16500 don't think we've spawned a nonworking cpuworker and write junk to
16501 it forever. Fix related to bug 4345; bugfix on all released Tor
16502 versions. Found by "skruffy".
16503 - Use a pthread_attr to make sure that spawn_func() cannot return an
16504 error while at the same time launching a thread. Fix related to
16505 bug 4345; bugfix on all released Tor versions. Reported
16508 o Minor bugfixes (relays and bridges):
16509 - Avoid crashing on a malformed resolv.conf file when running a
16510 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
16511 - Non-exit relays no longer launch mock DNS requests to check for
16512 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
16513 non-exit relays stopped servicing DNS requests. Fixes bug 965;
16514 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
16515 - Bridges now report complete directory request statistics. Related
16516 to bug 5824; bugfix on 0.2.2.1-alpha.
16517 - Bridges now never collect statistics that were designed for
16518 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
16520 o Minor bugfixes (testing):
16521 - Fix all valgrind warnings produced by the unit tests. There were
16522 over a thousand memory leak warnings previously, mostly produced
16523 by forgetting to free things in the unit test code. Fixes bug
16524 11618, bugfixes on many versions of Tor.
16526 o Minor bugfixes (tor-fw-helper):
16527 - Give a correct log message when tor-fw-helper fails to launch.
16528 (Previously, we would say something like "tor-fw-helper sent us a
16529 string we could not parse".) Fixes bug 9781; bugfix
16532 o Minor bugfixes (trivial memory leaks):
16533 - Fix a small memory leak when signing a directory object. Fixes bug
16534 11275; bugfix on 0.2.4.13-alpha.
16535 - Resolve some memory leaks found by coverity in the unit tests, on
16536 exit in tor-gencert, and on a failure to compute digests for our
16537 own keys when generating a v3 networkstatus vote. These leaks
16538 should never have affected anyone in practice.
16540 o Code simplification and refactoring:
16541 - Remove some old fallback code designed to keep Tor clients working
16542 in a network with only two working relays. Elsewhere in the code we
16543 have long since stopped supporting such networks, so there wasn't
16544 much point in keeping it around. Addresses ticket 9926.
16545 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
16546 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
16547 - Extract the common duplicated code for creating a subdirectory
16548 of the data directory and writing to a file in it. Fixes ticket
16549 4282; patch from Peter Retzlaff.
16550 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
16551 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
16552 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
16553 - Add a set of accessor functions for the circuit timeout data
16554 structure. Fixes ticket 6153; patch from "piet".
16555 - Clean up exit paths from connection_listener_new(). Closes ticket
16556 8789. Patch from Arlo Breault.
16557 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
16558 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
16559 - Use a doubly-linked list to implement the global circuit list.
16560 Resolves ticket 9108. Patch from Marek Majkowski.
16561 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
16562 - Remove constants and tests for PKCS1 padding; it's insecure and
16563 shouldn't be used for anything new. Fixes bug 8792; patch
16565 - Remove instances of strcpy() from the unit tests. They weren't
16566 hurting anything, since they were only in the unit tests, but it's
16567 embarrassing to have strcpy() in the code at all, and some analysis
16568 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
16569 0.2.3.8-alpha. Patch from Arlo Breault.
16570 - Remove is_internal_IP() function. Resolves ticket 4645.
16571 - Remove unused function circuit_dump_by_chan from circuitlist.c.
16572 Closes issue 9107; patch from "marek".
16573 - Change our use of the ENUM_BF macro to avoid declarations that
16575 - Get rid of router->address, since in all cases it was just the
16576 string representation of router->addr. Resolves ticket 5528.
16579 - Adjust the URLs in the README to refer to the new locations of
16580 several documents on the website. Fixes bug 12830. Patch from
16582 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
16584 - Update manpage to describe some of the files you can expect to
16585 find in Tor's DataDirectory. Addresses ticket 9839.
16586 - Clean up several option names in the manpage to match their real
16587 names, add the missing documentation for a couple of testing and
16588 directory authority options, remove the documentation for a
16589 V2-directory fetching option that no longer exists. Resolves
16591 - Correct the documentation so that it lists the correct directory
16592 for the stats files. (They are in a subdirectory called "stats",
16594 - In the manpage, move more authority-only options into the
16595 directory authority section so that operators of regular directory
16596 caches don't get confused.
16597 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
16598 11061; bugfix on 0.2.4.7-alpha.
16599 - Resolve warnings from Doxygen.
16600 - Document in the manpage that "KBytes" may also be written as
16601 "kilobytes" or "KB", that "Kbits" may also be written as
16602 "kilobits", and so forth. Closes ticket 9222.
16603 - Document that the ClientOnly config option overrides ORPort.
16604 Our old explanation made ClientOnly sound as though it did
16605 nothing at all. Resolves bug 9059.
16606 - Explain that SocksPolicy, DirPolicy, and similar options don't
16607 take port arguments. Fixes the other part of ticket 11108.
16608 - Fix a comment about the rend_server_descriptor_t.protocols field
16609 to more accurately describe its range. Also, make that field
16610 unsigned, to more accurately reflect its usage. Fixes bug 9099;
16611 bugfix on 0.2.1.5-alpha.
16612 - Fix the manpage's description of HiddenServiceAuthorizeClient:
16613 the maximum client name length is 16, not 19. Fixes bug 11118;
16614 bugfix on 0.2.1.6-alpha.
16617 - The contrib directory has been sorted and tidied. Before, it was
16618 an unsorted dumping ground for useful and not-so-useful things.
16619 Now, it is divided based on functionality, and the items which
16620 seemed to be nonfunctional or useless have been removed. Resolves
16621 ticket 8966; based on patches from "rl1987".
16623 o Removed code and features:
16624 - Clients now reject any directory authority certificates lacking
16625 a dir-key-crosscert element. These have been included since
16626 0.2.1.9-alpha, so there's no real reason for them to be optional
16627 any longer. Completes proposal 157. Resolves ticket 10162.
16628 - Remove all code that existed to support the v2 directory system,
16629 since there are no longer any v2 directory authorities. Resolves
16631 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
16632 options, which were used for designating authorities as "Hidden
16633 service authorities". There has been no use of hidden service
16634 authorities since 0.2.2.1-alpha, when we stopped uploading or
16635 downloading v0 hidden service descriptors. Fixes bug 10881; also
16636 part of a fix for bug 10841.
16637 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
16638 and MTBF calculations, but that nobody was using. Fixes bug 11742.
16639 - The TunnelDirConns and PreferTunnelledDirConns options no longer
16640 exist; tunneled directory connections have been available since
16641 0.1.2.5-alpha, and turning them off is not a good idea. This is a
16642 brute-force fix for 10849, where "TunnelDirConns 0" would break
16644 - Remove all code for the long unused v1 directory protocol.
16645 Resolves ticket 11070.
16646 - Remove all remaining code related to version-0 hidden service
16647 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
16648 the rest of bug 10841.
16649 - Remove migration code from when we renamed the "cached-routers"
16650 file to "cached-descriptors" back in 0.2.0.8-alpha. This
16651 incidentally resolves ticket 6502 by cleaning up the related code
16652 a bit. Patch from Akshay Hebbar.
16654 o Test infrastructure:
16655 - Tor now builds each source file in two modes: a mode that avoids
16656 exposing identifiers needlessly, and another mode that exposes
16657 more identifiers for testing. This lets the compiler do better at
16658 optimizing the production code, while enabling us to take more
16659 radical measures to let the unit tests test things.
16660 - The production builds no longer include functions used only in
16661 the unit tests; all functions exposed from a module only for
16662 unit-testing are now static in production builds.
16663 - Add an --enable-coverage configuration option to make the unit
16664 tests (and a new src/or/tor-cov target) to build with gcov test
16666 - Update to the latest version of tinytest.
16667 - Improve the tinytest implementation of string operation tests so
16668 that comparisons with NULL strings no longer crash the tests; they
16669 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
16670 - New macros in test.h to simplify writing mock-functions for unit
16671 tests. Part of ticket 11507. Patch from Dana Koch.
16672 - We now have rudimentary function mocking support that our unit
16673 tests can use to test functions in isolation. Function mocking
16674 lets the tests temporarily replace a function's dependencies with
16675 stub functions, so that the tests can check the function without
16676 invoking the other functions it calls.
16679 - Complete tests for the status.c module. Resolves ticket 11507.
16680 Patch from Dana Koch.
16681 - Add more unit tests for the <circid,channel>->circuit map, and
16682 the destroy-cell-tracking code to fix bug 7912.
16683 - Unit tests for failing cases of the TAP onion handshake.
16684 - More unit tests for address-manipulation functions.
16686 o Distribution (systemd):
16687 - Include a tor.service file in contrib/dist for use with systemd.
16688 Some distributions will be able to use this file unmodified;
16689 others will need to tweak it, or write their own. Patch from Jamie
16690 Nguyen; resolves ticket 8368.
16691 - Verify configuration file via ExecStartPre in the systemd unit
16692 file. Patch from intrigeri; resolves ticket 12730.
16693 - Explicitly disable RunAsDaemon in the systemd unit file. Our
16694 current systemd unit uses "Type = simple", so systemd does not
16695 expect tor to fork. If the user has "RunAsDaemon 1" in their
16696 torrc, then things won't work as expected. This is e.g. the case
16697 on Debian (and derivatives), since there we pass "--defaults-torrc
16698 /usr/share/tor/tor-service-defaults-torrc" (that contains
16699 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
16703 Changes in version 0.2.4.25 - 2014-10-20
16704 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
16705 (even though POODLE does not affect Tor). It also works around a crash
16706 bug caused by some operating systems' response to the "POODLE" attack
16707 (which does affect Tor).
16709 o Major security fixes (also in 0.2.5.9-rc):
16710 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
16711 today support TLS 1.0 or later, so we can safely turn off support
16712 for this old (and insecure) protocol. Fixes bug 13426.
16714 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
16715 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
16716 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
16717 13471. This is a workaround for an OpenSSL bug.
16720 Changes in version 0.2.4.24 - 2014-09-22
16721 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
16722 connecting to hidden services, and it updates the location of one of
16723 the directory authorities.
16726 - Clients now send the correct address for their chosen rendezvous
16727 point when trying to access a hidden service. They used to send
16728 the wrong address, which would still work some of the time because
16729 they also sent the identity digest of the rendezvous point, and if
16730 the hidden service happened to try connecting to the rendezvous
16731 point from a relay that already had a connection open to it,
16732 the relay would reuse that connection. Now connections to hidden
16733 services should be more robust and faster. Also, this bug meant
16734 that clients were leaking to the hidden service whether they were
16735 on a little-endian (common) or big-endian (rare) system, which for
16736 some users might have reduced their anonymity. Fixes bug 13151;
16737 bugfix on 0.2.1.5-alpha.
16739 o Directory authority changes:
16740 - Change IP address for gabelmoo (v3 directory authority).
16742 o Minor features (geoip):
16743 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
16747 Changes in version 0.2.4.23 - 2014-07-28
16748 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
16749 guard rotation, and also backports several important fixes from the
16750 Tor 0.2.5 alpha release series.
16753 - Clients now look at the "usecreatefast" consensus parameter to
16754 decide whether to use CREATE_FAST or CREATE cells for the first hop
16755 of their circuit. This approach can improve security on connections
16756 where Tor's circuit handshake is stronger than the available TLS
16757 connection security levels, but the tradeoff is more computational
16758 load on guard relays. Implements proposal 221. Resolves ticket 9386.
16759 - Make the number of entry guards configurable via a new
16760 NumEntryGuards consensus parameter, and the number of directory
16761 guards configurable via a new NumDirectoryGuards consensus
16762 parameter. Implements ticket 12688.
16765 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
16766 implementation that caused incorrect results on 32-bit
16767 implementations when certain malformed inputs were used along with
16768 a small class of private ntor keys. This bug does not currently
16769 appear to allow an attacker to learn private keys or impersonate a
16770 Tor server, but it could provide a means to distinguish 32-bit Tor
16771 implementations from 64-bit Tor implementations. Fixes bug 12694;
16772 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
16776 - Warn and drop the circuit if we receive an inbound 'relay early'
16777 cell. Those used to be normal to receive on hidden service circuits
16778 due to bug 1038, but the buggy Tor versions are long gone from
16779 the network so we can afford to resume watching for them. Resolves
16780 the rest of bug 1038; bugfix on 0.2.1.19.
16781 - Correct a confusing error message when trying to extend a circuit
16782 via the control protocol but we don't know a descriptor or
16783 microdescriptor for one of the specified relays. Fixes bug 12718;
16784 bugfix on 0.2.3.1-alpha.
16785 - Avoid an illegal read from stack when initializing the TLS
16786 module using a version of OpenSSL without all of the ciphers
16787 used by the v2 link handshake. Fixes bug 12227; bugfix on
16788 0.2.4.8-alpha. Found by "starlight".
16791 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
16795 Changes in version 0.2.4.22 - 2014-05-16
16796 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
16797 alpha release series. These include blocking all authority signing
16798 keys that may have been affected by the OpenSSL "heartbleed" bug,
16799 choosing a far more secure set of TLS ciphersuites by default, closing
16800 a couple of memory leaks that could be used to run a target relay out
16801 of RAM, and several others.
16803 o Major features (security, backport from 0.2.5.4-alpha):
16804 - Block authority signing keys that were used on authorities
16805 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
16806 don't have any evidence that these keys _were_ compromised; we're
16807 doing this to be prudent.) Resolves ticket 11464.
16809 o Major bugfixes (security, OOM):
16810 - Fix a memory leak that could occur if a microdescriptor parse
16811 fails during the tokenizing step. This bug could enable a memory
16812 exhaustion attack by directory servers. Fixes bug 11649; bugfix
16815 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
16816 - The relay ciphersuite list is now generated automatically based on
16817 uniform criteria, and includes all OpenSSL ciphersuites with
16818 acceptable strength and forward secrecy. Previously, we had left
16819 some perfectly fine ciphersuites unsupported due to omission or
16820 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
16821 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
16822 - Relays now trust themselves to have a better view than clients of
16823 which TLS ciphersuites are better than others. (Thanks to bug
16824 11513, the relay list is now well-considered, whereas the client
16825 list has been chosen mainly for anti-fingerprinting purposes.)
16826 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
16827 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
16828 AES128. Resolves ticket 11528.
16829 - Clients now try to advertise the same list of ciphersuites as
16830 Firefox 28. This change enables selection of (fast) GCM
16831 ciphersuites, disables some strange old ciphers, and stops
16832 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
16833 Resolves ticket 11438.
16835 o Minor bugfixes (configuration, security):
16836 - When running a hidden service, do not allow TunneledDirConns 0:
16837 trying to set that option together with a hidden service would
16838 otherwise prevent the hidden service from running, and also make
16839 it publish its descriptors directly over HTTP. Fixes bug 10849;
16840 bugfix on 0.2.1.1-alpha.
16842 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
16843 - Avoid sending a garbage value to the controller when a circuit is
16844 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
16846 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
16847 - Stop leaking memory when we successfully resolve a PTR record.
16848 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
16850 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
16851 - Avoid 60-second delays in the bootstrapping process when Tor is
16852 launching for a second time while using bridges. Fixes bug 9229;
16853 bugfix on 0.2.0.3-alpha.
16855 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
16856 - Give the correct URL in the warning message when trying to run a
16857 relay on an ancient version of Windows. Fixes bug 9393.
16859 o Minor bugfixes (compilation):
16860 - Fix a compilation error when compiling with --disable-curve25519.
16861 Fixes bug 9700; bugfix on 0.2.4.17-rc.
16864 - Downgrade the warning severity for the the "md was still
16865 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
16866 for trying to diagnose this bug, and the current warning in
16867 earlier versions of tor achieves nothing useful. Addresses warning
16870 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
16871 - When we run out of usable circuit IDs on a channel, log only one
16872 warning for the whole channel, and describe how many circuits
16873 there were on the channel. Fixes part of ticket 11553.
16875 o Minor features (security, backport from 0.2.5.4-alpha):
16876 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
16877 leave the default at 8GBytes), to better support Raspberry Pi
16878 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
16880 o Documentation (backport from 0.2.5.4-alpha):
16881 - Correctly document that we search for a system torrc file before
16882 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
16886 Changes in version 0.2.4.21 - 2014-02-28
16887 Tor 0.2.4.21 further improves security against potential adversaries who
16888 find breaking 1024-bit crypto doable, and backports several stability
16889 and robustness patches from the 0.2.5 branch.
16891 o Major features (client security):
16892 - When we choose a path for a 3-hop circuit, make sure it contains
16893 at least one relay that supports the NTor circuit extension
16894 handshake. Otherwise, there is a chance that we're building
16895 a circuit that's worth attacking by an adversary who finds
16896 breaking 1024-bit crypto doable, and that chance changes the game
16897 theory. Implements ticket 9777.
16900 - Do not treat streams that fail with reason
16901 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
16902 since it could also indicate an ENETUNREACH connection error. Fixes
16903 part of bug 10777; bugfix on 0.2.4.8-alpha.
16905 o Code simplification and refactoring:
16906 - Remove data structures which were introduced to implement the
16907 CellStatistics option: they are now redundant with the new timestamp
16908 field in the regular packed_cell_t data structure, which we did
16909 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
16912 - Always clear OpenSSL bignums before freeing them -- even bignums
16913 that don't contain secrets. Resolves ticket 10793. Patch by
16915 - Build without warnings under clang 3.4. (We have some macros that
16916 define static functions only some of which will get used later in
16917 the module. Starting with clang 3.4, these give a warning unless the
16918 unused attribute is set on them.) Resolves ticket 10904.
16919 - Update geoip and geoip6 files to the February 7 2014 Maxmind
16920 GeoLite2 Country database.
16923 - Set the listen() backlog limit to the largest actually supported
16924 on the system, not to the value in a header file. Fixes bug 9716;
16925 bugfix on every released Tor.
16926 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
16927 exit node as a NOROUTE error, not an INTERNAL error, since they
16928 can apparently happen when trying to connect to the wrong sort
16929 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
16930 - Fix build warnings about missing "a2x" comment when building the
16931 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
16932 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
16933 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
16934 not entirely remove it from the connection lists. Fixes bug 9602;
16935 bugfix on 0.2.4.4-alpha.
16936 - Fix a segmentation fault in our benchmark code when running with
16937 Fedora's OpenSSL package, or any other OpenSSL that provides
16938 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
16939 - Turn "circuit handshake stats since last time" log messages into a
16940 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
16942 o Documentation fixes:
16943 - Document that all but one DirPort entry must have the NoAdvertise
16944 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
16947 Changes in version 0.2.4.20 - 2013-12-22
16948 Tor 0.2.4.20 fixes potentially poor random number generation for users
16949 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
16950 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
16951 and 4) have no state file in their DataDirectory (as would happen on
16952 first start). Users who generated relay or hidden service identity
16953 keys in such a situation should discard them and generate new ones.
16955 This release also fixes a logic error that caused Tor clients to build
16956 many more preemptive circuits than they actually need.
16959 - Do not allow OpenSSL engines to replace the PRNG, even when
16960 HardwareAccel is set. The only default builtin PRNG engine uses
16961 the Intel RDRAND instruction to replace the entire PRNG, and
16962 ignores all attempts to seed it with more entropy. That's
16963 cryptographically stupid: the right response to a new alleged
16964 entropy source is never to discard all previously used entropy
16965 sources. Fixes bug 10402; works around behavior introduced in
16966 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
16968 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
16969 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
16970 - Avoid launching spurious extra circuits when a stream is pending.
16971 This fixes a bug where any circuit that _wasn't_ unusable for new
16972 streams would be treated as if it were, causing extra circuits to
16973 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
16976 - Avoid a crash bug when starting with a corrupted microdescriptor
16977 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
16978 - If we fail to dump a previously cached microdescriptor to disk, avoid
16979 freeing duplicate data later on. Fixes bug 10423; bugfix on
16980 0.2.4.13-alpha. Spotted by "bobnomnom".
16983 Changes in version 0.2.4.19 - 2013-12-11
16984 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
16985 (1986-2013). Aaron worked on diverse projects including helping to guide
16986 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
16987 transparency to the U.S government's PACER documents, and contributing
16988 design and development for Tor and Tor2Web. Aaron was one of the latest
16989 martyrs in our collective fight for civil liberties and human rights,
16990 and his death is all the more painful because he was one of us.
16992 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
16993 a new circuit handshake and link encryption that use ECC to provide
16994 better security and efficiency; makes relays better manage circuit
16995 creation requests; uses "directory guards" to reduce client enumeration
16996 risks; makes bridges collect and report statistics about the pluggable
16997 transports they support; cleans up and improves our geoip database;
16998 gets much closer to IPv6 support for clients, bridges, and relays; makes
16999 directory authorities use measured bandwidths rather than advertised
17000 ones when computing flags and thresholds; disables client-side DNS
17001 caching to reduce tracking risks; and fixes a big bug in bridge
17002 reachability testing. This release introduces two new design
17003 abstractions in the code: a new "channel" abstraction between circuits
17004 and or_connections to allow for implementing alternate relay-to-relay
17005 transports, and a new "circuitmux" abstraction storing the queue of
17006 circuits for a channel. The release also includes many stability,
17007 security, and privacy fixes.
17009 o Major features (new circuit handshake):
17010 - Tor now supports a new circuit extension handshake designed by Ian
17011 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
17012 circuit extension handshake, later called "TAP", was a bit slow
17013 (especially on the relay side), had a fragile security proof, and
17014 used weaker keys than we'd now prefer. The new circuit handshake
17015 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
17016 function, making it significantly more secure than the older
17017 handshake, and significantly faster. Tor can use one of two built-in
17018 pure-C curve25519-donna implementations by Adam Langley, or it
17019 can link against the "nacl" library for a tuned version if present.
17021 The built-in version is very fast for 64-bit systems when building
17022 with GCC. The built-in 32-bit version is still faster than the
17023 old TAP protocol, but using libnacl is better on most such hosts.
17025 Implements proposal 216; closes ticket 7202.
17027 o Major features (better link encryption):
17028 - Relays can now enable the ECDHE TLS ciphersuites when available
17029 and appropriate. These ciphersuites let us negotiate forward-secure
17030 TLS secret keys more safely and more efficiently than with our
17031 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
17032 public relays prefer the (faster) P224 group, and bridges prefer
17033 the (more common) P256 group; you can override this with the
17036 This feature requires clients running 0.2.3.17-beta or later,
17037 and requires both sides to be running OpenSSL 1.0.0 or later
17038 with ECC support. OpenSSL 1.0.1, with the compile-time option
17039 "enable-ec_nistp_64_gcc_128", is highly recommended.
17041 Implements the relay side of proposal 198; closes ticket 7200.
17043 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
17044 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
17045 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
17046 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
17047 them to solve bug 6033.)
17049 o Major features (relay performance):
17050 - Instead of limiting the number of queued onionskins (aka circuit
17051 create requests) to a fixed, hard-to-configure number, we limit
17052 the size of the queue based on how many we expect to be able to
17053 process in a given amount of time. We estimate the time it will
17054 take to process an onionskin based on average processing time
17055 of previous onionskins. Closes ticket 7291. You'll never have to
17056 configure MaxOnionsPending again.
17057 - Relays process the new "NTor" circuit-level handshake requests
17058 with higher priority than the old "TAP" circuit-level handshake
17059 requests. We still process some TAP requests to not totally starve
17060 0.2.3 clients when NTor becomes popular. A new consensus parameter
17061 "NumNTorsPerTAP" lets us tune the balance later if we need to.
17062 Implements ticket 9574.
17064 o Major features (client bootstrapping resilience):
17065 - Add a new "FallbackDir" torrc option to use when we can't use
17066 a directory mirror from the consensus (either because we lack a
17067 consensus, or because they're all down). Currently, all authorities
17068 are fallbacks by default, and there are no other default fallbacks,
17069 but that will change. This option will allow us to give clients a
17070 longer list of servers to try to get a consensus from when first
17071 connecting to the Tor network, and thereby reduce load on the
17072 directory authorities. Implements proposal 206, "Preconfigured
17073 directory sources for bootstrapping". We also removed the old
17074 "FallbackNetworkstatus" option, since we never got it working well
17075 enough to use it. Closes bug 572.
17076 - If we have no circuits open, use a relaxed timeout (the
17077 95th-percentile cutoff) until a circuit succeeds. This heuristic
17078 should allow Tor to succeed at building circuits even when the
17079 network connection drastically changes. Should help with bug 3443.
17081 o Major features (use of guards):
17082 - Support directory guards (proposal 207): when possible, clients now
17083 use their entry guards for non-anonymous directory requests. This
17084 can help prevent client enumeration. Note that this behavior only
17085 works when we have a usable consensus directory, and when options
17086 about what to download are more or less standard. In the future we
17087 should re-bootstrap from our guards, rather than re-bootstrapping
17088 from the preconfigured list of directory sources that ships with
17089 Tor. Resolves ticket 6526.
17090 - Raise the default time that a client keeps an entry guard from
17091 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
17092 2012 paper. (We would make it even longer, but we need better client
17093 load balancing first.) Also, make the guard lifetime controllable
17094 via a new GuardLifetime torrc option and a GuardLifetime consensus
17095 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
17097 o Major features (bridges with pluggable transports):
17098 - Bridges now report the pluggable transports they support to the
17099 bridge authority, so it can pass the supported transports on to
17100 bridgedb and/or eventually do reachability testing. Implements
17102 - Automatically forward the TCP ports of pluggable transport
17103 proxies using tor-fw-helper if PortForwarding is enabled. Implements
17106 o Major features (geoip database):
17107 - Maxmind began labelling Tor relays as being in country "A1",
17108 which breaks by-country node selection inside Tor. Now we use a
17109 script to replace "A1" ("Anonymous Proxy") entries in our geoip
17110 file with real country codes. This script fixes about 90% of "A1"
17111 entries automatically and uses manual country code assignments to
17112 fix the remaining 10%. See src/config/README.geoip for details.
17114 - Add GeoIP database for IPv6 addresses. The new config option
17116 - Update to the October 2 2013 Maxmind GeoLite Country database.
17118 o Major features (IPv6):
17119 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
17120 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
17121 to happen. Implements ticket 5535.
17122 - All kind of relays, not just bridges, can now advertise an IPv6
17123 OR port. Implements ticket 6362.
17124 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
17125 connectivity, then set the IPv6Exit flag to 1. Also make sure your
17126 exit policy reads as you would like: the address * applies to all
17127 address families, whereas *4 is IPv4 address only, and *6 is IPv6
17128 addresses only. On the client side, you'll need to wait for enough
17129 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
17130 and use Socks5. Closes ticket 5547, implements proposal 117 as
17131 revised in proposal 208.
17132 - Bridge authorities now accept IPv6 bridge addresses and include
17133 them in network status documents. Implements ticket 5534.
17134 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
17136 o Major features (directory authorities):
17137 - Directory authorities now prefer using measured bandwidths to
17138 advertised ones when computing flags and thresholds. Resolves
17140 - Directory authorities that vote measured bandwidths about more
17141 than a threshold number of relays now treat relays with
17142 unmeasured bandwidths as having bandwidth 0 when computing their
17143 flags. Resolves ticket 8435.
17144 - Directory authorities now support a new consensus method (17)
17145 where they cap the published bandwidth of relays for which
17146 insufficient bandwidth measurements exist. Fixes part of bug 2286.
17147 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
17148 serve any v2 directory information. Now we can test disabling the
17149 old deprecated v2 directory format, and see whether doing so has
17150 any effect on network load. Begins to fix bug 6783.
17152 o Major features (build and portability):
17153 - Switch to a nonrecursive Makefile structure. Now instead of each
17154 Makefile.am invoking other Makefile.am's, there is a master
17155 Makefile.am that includes the others. This change makes our build
17156 process slightly more maintainable, and improves parallelism for
17157 building with make -j. Original patch by Stewart Smith; various
17158 fixes by Jim Meyering.
17159 - Where available, we now use automake's "silent" make rules by
17160 default, so that warnings are easier to spot. You can get the old
17161 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
17162 - Resume building correctly with MSVC and Makefile.nmake. This patch
17163 resolves numerous bugs and fixes reported by ultramage, including
17164 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
17166 o Security features:
17167 - Switch to a completely time-invariant approach for picking nodes
17168 weighted by bandwidth. Our old approach would run through the
17169 part of the loop after it had made its choice slightly slower
17170 than it ran through the part of the loop before it had made its
17171 choice. Addresses ticket 6538.
17172 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
17173 by tor2web clients allows hidden services to identify tor2web
17174 clients through their repeated selection of the same rendezvous
17175 and introduction point circuit endpoints (their guards). Resolves
17178 o Major bugfixes (relay denial of service):
17179 - When we have too much memory queued in circuits (according to a new
17180 MaxMemInCellQueues option), close the circuits that have the oldest
17181 queued cells, on the theory that those are most responsible for
17182 us running low on memory. This prevents us from running out of
17183 memory as a relay if circuits fill up faster than they can be
17184 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
17185 Tor. This bug is a further fix beyond bug 6252, whose fix was
17186 merged into 0.2.3.21-rc.
17187 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
17188 ID: these could be used to create unexpected streams and circuits
17189 which would count as "present" to some parts of Tor but "absent"
17190 to others, leading to zombie circuits and streams or to a bandwidth
17191 denial-of-service. Fixes bug 7889; bugfix on every released version
17192 of Tor. Reported by "oftc_must_be_destroyed".
17193 - Avoid a bug where our response to TLS renegotiation under certain
17194 network conditions could lead to a busy-loop, with 100% CPU
17195 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
17197 o Major bugfixes (asserts, crashes, leaks):
17198 - Prevent the get_freelists() function from running off the end of
17199 the list of freelists if it somehow gets an unrecognized
17200 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
17202 - Avoid a memory leak where we would leak a consensus body when we
17203 find that a consensus which we couldn't previously verify due to
17204 missing certificates is now verifiable. Fixes bug 8719; bugfix
17206 - If we are unable to save a microdescriptor to the journal, do not
17207 drop it from memory and then reattempt downloading it. Fixes bug
17208 9645; bugfix on 0.2.2.6-alpha.
17209 - Fix an assertion failure that would occur when disabling the
17210 ORPort setting on a running Tor process while accounting was
17211 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
17212 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
17213 when an exit connection with optimistic data succeeds immediately
17214 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
17216 - Fix a memory leak that would occur whenever a configuration
17217 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
17219 o Major bugfixes (relay rate limiting):
17220 - When a TLS write is partially successful but incomplete, remember
17221 that the flushed part has been flushed, and notice that bytes were
17222 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
17223 bugfix on Tor 0.1.0.5-rc.
17224 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
17225 to 1GB/1GB. The previous defaults were intended to be "basically
17226 infinite", but it turns out they're now limiting our 100mbit+
17227 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
17228 last time we raised it).
17229 - No longer stop reading or writing on cpuworker connections when
17230 our rate limiting buckets go empty. Now we should handle circuit
17231 handshake requests more promptly. Resolves bug 9731.
17233 o Major bugfixes (client-side privacy):
17234 - When we mark a circuit as unusable for new circuits, have it
17235 continue to be unusable for new circuits even if MaxCircuitDirtiness
17236 is increased too much at the wrong time, or the system clock jumps
17237 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
17238 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
17239 which have resolved to internal addresses") is set, apply that
17240 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
17241 - When an exit relay rejects a stream with reason "exit policy", but
17242 we only know an exit policy summary (e.g. from the microdesc
17243 consensus) for it, do not mark the relay as useless for all exiting.
17244 Instead, mark just the circuit as unsuitable for that particular
17245 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
17247 o Major bugfixes (stream isolation):
17248 - Allow applications to get proper stream isolation with
17249 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
17250 username/password authentication also offer "no authentication". Tor
17251 had previously preferred "no authentication", so the applications
17252 never actually sent Tor their auth details. Now Tor selects
17253 username/password authentication if it's offered. You can disable
17254 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
17255 bug 8117; bugfix on 0.2.3.3-alpha.
17256 - Follow the socks5 protocol when offering username/password
17257 authentication. The fix for bug 8117 exposed this bug, and it
17258 turns out real-world applications like Pidgin do care. Bugfix on
17259 0.2.3.2-alpha; fixes bug 8879.
17261 o Major bugfixes (client circuit building):
17262 - Alter circuit build timeout measurement to start at the point
17263 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
17264 initialization). This should make our timeout measurements more
17265 uniform. Previously, we were sometimes including ORconn setup time
17266 in our circuit build time measurements. Should resolve bug 3443.
17267 - If the circuit build timeout logic is disabled (via the consensus,
17268 or because we are an authority), then don't build testing circuits.
17269 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
17271 o Major bugfixes (client-side DNS):
17272 - Turn off the client-side DNS cache by default. Updating and using
17273 the DNS cache is now configurable on a per-client-port
17274 level. SOCKSPort, DNSPort, etc lines may now contain
17275 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
17276 cache these types of DNS answers when we receive them from an
17277 exit node in response to an application request on this port, and
17278 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
17279 cached DNS answers of these types, we shouldn't use them. It's
17280 potentially risky to use cached DNS answers at the client, since
17281 doing so can indicate to one exit what answers we've gotten
17282 for DNS lookups in the past. With IPv6, this becomes especially
17283 problematic. Using cached DNS answers for requests on the same
17284 circuit would present less linkability risk, since all traffic
17285 on a circuit is already linkable, but it would also provide
17286 little performance benefit: the exit node caches DNS replies
17287 too. Implements a simplified version of Proposal 205. Implements
17290 o Major bugfixes (hidden service privacy):
17291 - Limit hidden service descriptors to at most ten introduction
17292 points, to slow one kind of guard enumeration. Fixes bug 9002;
17293 bugfix on 0.1.1.11-alpha.
17295 o Major bugfixes (directory fetching):
17296 - If the time to download the next old-style networkstatus is in
17297 the future, do not decline to consider whether to download the
17298 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
17300 - We used to always request authority certificates by identity digest,
17301 meaning we'd get the newest one even when we wanted one with a
17302 different signing key. Then we would complain about being given
17303 a certificate we already had, and never get the one we really
17304 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
17305 resource to request the one we want. Fixes bug 5595; bugfix on
17308 o Major bugfixes (bridge reachability):
17309 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
17310 previously they did not, which prevented them from receiving
17311 successful connections from relays for self-test or bandwidth
17312 testing. Also, when a relay is extending a circuit to a bridge,
17313 it needs to send a NETINFO cell, even when the bridge hasn't sent
17314 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
17316 o Major bugfixes (control interface):
17317 - When receiving a new configuration file via the control port's
17318 LOADCONF command, do not treat the defaults file as absent.
17319 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
17321 o Major bugfixes (directory authorities):
17322 - Stop marking every relay as having been down for one hour every
17323 time we restart a directory authority. These artificial downtimes
17324 were messing with our Stable and Guard flag calculations. Fixes
17325 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
17326 - When computing directory thresholds, ignore any rejected-as-sybil
17327 nodes during the computation so that they can't influence Fast,
17328 Guard, etc. (We should have done this for proposal 109.) Fixes
17330 - When marking a node as a likely sybil, reset its uptime metrics
17331 to zero, so that it cannot time towards getting marked as Guard,
17332 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
17334 - Fix a bug in the voting algorithm that could yield incorrect results
17335 when a non-naming authority declared too many flags. Fixes bug 9200;
17336 bugfix on 0.2.0.3-alpha.
17338 o Internal abstraction features:
17339 - Introduce new channel_t abstraction between circuits and
17340 or_connection_t to allow for implementing alternate OR-to-OR
17341 transports. A channel_t is an abstract object which can either be a
17342 cell-bearing channel, which is responsible for authenticating and
17343 handshaking with the remote OR and transmitting cells to and from
17344 it, or a listening channel, which spawns new cell-bearing channels
17345 at the request of remote ORs. Implements part of ticket 6465.
17346 - Make a channel_tls_t subclass of channel_t, adapting it to the
17347 existing or_connection_t code. The V2/V3 protocol handshaking
17348 code which formerly resided in command.c has been moved below the
17349 channel_t abstraction layer and may be found in channeltls.c now.
17350 Implements the rest of ticket 6465.
17351 - Introduce new circuitmux_t storing the queue of circuits for
17352 a channel; this encapsulates and abstracts the queue logic and
17353 circuit selection policy, and allows the latter to be overridden
17354 easily by switching out a policy object. The existing EWMA behavior
17355 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
17357 o New build requirements:
17358 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
17359 strongly recommended.
17360 - Tor maintainers now require Automake version 1.9 or later to build
17361 Tor from the Git repository. (Automake is not required when building
17362 from a source distribution.)
17364 o Minor features (protocol):
17365 - No longer include the "opt" prefix when generating routerinfos
17366 or v2 directories: it has been needless since Tor 0.1.2. Closes
17368 - Reject EXTEND cells sent to nonexistent streams. According to the
17369 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
17370 we were only checking for stream IDs that were currently in use.
17371 Found while hunting for more instances of bug 6271. Bugfix on
17372 0.0.2pre8, which introduced incremental circuit construction.
17373 - Tor relays and clients now support a better CREATE/EXTEND cell
17374 format, allowing the sender to specify multiple address, identity,
17375 and handshake types. Implements Robert Ransom's proposal 200;
17376 closes ticket 7199.
17377 - Reject as invalid most directory objects containing a NUL.
17378 Belt-and-suspender fix for bug 8037.
17380 o Minor features (security):
17381 - Clear keys and key-derived material left on the stack in
17382 rendservice.c and rendclient.c. Check return value of
17383 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
17384 These fixes should make us more forward-secure against cold-boot
17385 attacks and the like. Fixes bug 2385.
17386 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
17387 Irix's random() only return 15 bits; Solaris's random() returns more
17388 bits but its RAND_MAX says it only returns 15, and so on. Motivated
17389 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
17391 o Minor features (control protocol):
17392 - Add a "GETINFO signal/names" control port command. Implements
17394 - Provide default values for all options via "GETINFO config/defaults".
17395 Implements ticket 4971.
17396 - Allow an optional $ before the node identity digest in the
17397 controller command GETINFO ns/id/<identity>, for consistency with
17398 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
17399 - Add CACHED keyword to ADDRMAP events in the control protocol
17400 to indicate whether a DNS result will be cached or not. Resolves
17402 - Generate bootstrapping status update events correctly when fetching
17403 microdescriptors. Fixes bug 9927.
17405 o Minor features (path selection):
17406 - When deciding whether we have enough descriptors to build circuits,
17407 instead of looking at raw relay counts, look at which fraction
17408 of (bandwidth-weighted) paths we're able to build. This approach
17409 keeps clients from building circuits if their paths are likely to
17410 stand out statistically. The default fraction of paths needed is
17411 taken from the consensus directory; you can override it with the
17412 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
17413 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
17414 and we have GeoIP information, also exclude all nodes with unknown
17415 countries "??" and "A1". This behavior is controlled by the
17416 new GeoIPExcludeUnknown option: you can make such nodes always
17417 excluded with "GeoIPExcludeUnknown 1", and disable the feature
17418 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
17419 gets you the default behavior. Implements feature 7706.
17421 o Minor features (hidden services):
17422 - Improve circuit build timeout handling for hidden services.
17423 In particular: adjust build timeouts more accurately depending
17424 upon the number of hop-RTTs that a particular circuit type
17425 undergoes. Additionally, launch intro circuits in parallel
17426 if they timeout, and take the first one to reply as valid.
17427 - The Tor client now ignores sub-domain components of a .onion
17428 address. This change makes HTTP "virtual" hosting
17429 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
17430 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
17431 hosted on the same hidden service. Implements proposal 204.
17432 - Enable Tor to read configuration, state, and key information from
17433 a FIFO. Previously Tor would only read from files with a positive
17434 stat.st_size. Code from meejah; fixes bug 6044.
17436 o Minor features (clients):
17437 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
17438 microdescriptor-related dir requests, and only fall back to normal
17439 descriptors if none of their bridges can handle microdescriptors
17440 (as opposed to the fix in ticket 4013, which caused them to fall
17441 back to normal descriptors if *any* of their bridges preferred
17442 them). Resolves ticket 4994.
17443 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
17444 TCP ports to forward. In the past it only accepted two ports:
17445 the ORPort and the DirPort.
17447 o Minor features (protecting client timestamps):
17448 - Clients no longer send timestamps in their NETINFO cells. These were
17449 not used for anything, and they provided one small way for clients
17450 to be distinguished from each other as they moved from network to
17451 network or behind NAT. Implements part of proposal 222.
17452 - Clients now round timestamps in INTRODUCE cells down to the nearest
17453 10 minutes. If a new Support022HiddenServices option is set to 0, or
17454 if it's set to "auto" and the feature is disabled in the consensus,
17455 the timestamp is sent as 0 instead. Implements part of proposal 222.
17456 - Stop sending timestamps in AUTHENTICATE cells. This is not such
17457 a big deal from a security point of view, but it achieves no actual
17458 good purpose, and isn't needed. Implements part of proposal 222.
17459 - Reduce down accuracy of timestamps in hidden service descriptors.
17460 Implements part of proposal 222.
17462 o Minor features (bridges):
17463 - Make bridge relays check once a minute for whether their IP
17464 address has changed, rather than only every 15 minutes. Resolves
17465 bugs 1913 and 1992.
17466 - Bridge statistics now count bridge clients connecting over IPv6:
17467 bridge statistics files now list "bridge-ip-versions" and
17468 extra-info documents list "geoip6-db-digest". The control protocol
17469 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
17470 implementation by "shkoo", addressing ticket 5055.
17471 - Add a new torrc option "ServerTransportListenAddr" to let bridge
17472 operators select the address where their pluggable transports will
17473 listen for connections. Resolves ticket 7013.
17474 - Randomize the lifetime of our SSL link certificate, so censors can't
17475 use the static value for filtering Tor flows. Resolves ticket 8443;
17476 related to ticket 4014 which was included in 0.2.2.33.
17478 o Minor features (relays):
17479 - Option OutboundBindAddress can be specified multiple times and
17480 accepts IPv6 addresses. Resolves ticket 6876.
17482 o Minor features (IPv6, client side):
17483 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
17484 prefer to hand out virtual IPv6 addresses, since there are more of
17485 them and we can't run out. To override this behavior and make IPv4
17486 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
17487 or DNSPort you're using for resolving. Implements ticket 7571.
17488 - AutomapHostsOnResolve responses are now randomized, to avoid
17489 annoying situations where Tor is restarted and applications
17490 connect to the wrong addresses.
17491 - Never try more than 1000 times to pick a new virtual address when
17492 AutomapHostsOnResolve is set. That's good enough so long as we
17493 aren't close to handing out our entire virtual address space;
17494 if you're getting there, it's best to switch to IPv6 virtual
17497 o Minor features (IPv6, relay/authority side):
17498 - New config option "AuthDirHasIPv6Connectivity 1" that directory
17499 authorities should set if they have IPv6 connectivity and want to
17500 do reachability tests for IPv6 relays. Implements feature 5974.
17501 - A relay with an IPv6 OR port now sends that address in NETINFO
17502 cells (in addition to its other address). Implements ticket 6364.
17504 o Minor features (directory authorities):
17505 - Directory authorities no long accept descriptors for any version of
17506 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
17507 These versions are insecure, unsupported, or both. Implements
17509 - When directory authorities are computing thresholds for flags,
17510 never let the threshold for the Fast flag fall below 4096
17511 bytes. Also, do not consider nodes with extremely low bandwidths
17512 when deciding thresholds for various directory flags. This change
17513 should raise our threshold for Fast relays, possibly in turn
17514 improving overall network performance; see ticket 1854. Resolves
17516 - Directory authorities now include inside each vote a statement of
17517 the performance thresholds they used when assigning flags.
17518 Implements ticket 8151.
17519 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
17520 in directory authority votes to describe whether they have enough
17521 measured bandwidths to ignore advertised (relay descriptor)
17522 bandwidth claims. Resolves ticket 8711.
17524 o Minor features (path bias detection):
17525 - Path Use Bias: Perform separate accounting for successful circuit
17526 use. Keep separate statistics on stream attempt rates versus stream
17527 success rates for each guard. Provide configurable thresholds to
17528 determine when to emit log messages or disable use of guards that
17529 fail too many stream attempts. Resolves ticket 7802.
17530 - Create three levels of Path Bias log messages, as opposed to just
17531 two. These are configurable via consensus as well as via the torrc
17532 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
17533 The default values are 0.70, 0.50, and 0.30 respectively.
17534 - Separate the log message levels from the decision to drop guards,
17535 which also is available via torrc option PathBiasDropGuards.
17536 PathBiasDropGuards still defaults to 0 (off).
17537 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
17538 in combination with PathBiasExtremeRate.
17539 - Increase the default values for PathBiasScaleThreshold and
17540 PathBiasCircThreshold from (200, 20) to (300, 150).
17541 - Add in circuit usage accounting to path bias. If we try to use a
17542 built circuit but fail for any reason, it counts as path bias.
17543 Certain classes of circuits where the adversary gets to pick your
17544 destination node are exempt from this accounting. Usage accounting
17545 can be specifically disabled via consensus parameter or torrc.
17546 - Convert all internal path bias state to double-precision floating
17547 point, to avoid roundoff error and other issues.
17548 - Only record path bias information for circuits that have completed
17549 *two* hops. Assuming end-to-end tagging is the attack vector, this
17550 makes us more resilient to ambient circuit failure without any
17551 detection capability loss.
17553 o Minor features (build):
17554 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
17555 dhill. Resolves ticket 6982.
17556 - Compile on win64 using mingw64. Fixes bug 7260; patches from
17558 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
17559 separate error codes; or at least, don't break for that reason.
17560 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
17562 o Build improvements (autotools):
17563 - Warn if building on a platform with an unsigned time_t: there
17564 are too many places where Tor currently assumes that time_t can
17565 hold negative values. We'd like to fix them all, but probably
17567 - Do not report status verbosely from autogen.sh unless the -v flag
17568 is specified. Fixes issue 4664. Patch from Onizuka.
17569 - Detect and reject attempts to build Tor with threading support
17570 when OpenSSL has been compiled without threading support.
17572 - Try to detect if we are ever building on a platform where
17573 memset(...,0,...) does not set the value of a double to 0.0. Such
17574 platforms are permitted by the C standard, though in practice
17575 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
17576 currently support them, but it's better to detect them and fail
17577 than to perform erroneously.
17578 - We no longer warn so much when generating manpages from their
17580 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
17581 the signs of types during autoconf. This is better than our old
17582 approach, which didn't work when cross-compiling.
17584 o Minor features (log messages, warnings):
17585 - Detect when we're running with a version of OpenSSL other than the
17586 one we compiled with. This conflict has occasionally given people
17587 hard-to-track-down errors.
17588 - Warn users who run hidden services on a Tor client with
17589 UseEntryGuards disabled that their hidden services will be
17590 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
17591 attack which motivated Tor to support entry guards in the first
17592 place). Resolves ticket 6889.
17593 - Warn when we are binding low ports when hibernation is enabled;
17594 previously we had warned when we were _advertising_ low ports with
17595 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
17596 - Issue a warning when running with the bufferevents backend enabled.
17597 It's still not stable, and people should know that they're likely
17598 to hit unexpected problems. Closes ticket 9147.
17600 o Minor features (log messages, notices):
17601 - Refactor resolve_my_address() so it returns the method by which we
17602 decided our public IP address (explicitly configured, resolved from
17603 explicit hostname, guessed from interfaces, learned by gethostname).
17604 Now we can provide more helpful log messages when a relay guesses
17605 its IP address incorrectly (e.g. due to unexpected lines in
17606 /etc/hosts). Resolves ticket 2267.
17607 - Track how many "TAP" and "NTor" circuit handshake requests we get,
17608 and how many we complete, and log it every hour to help relay
17609 operators follow trends in network load. Addresses ticket 9658.
17611 o Minor features (log messages, diagnostics):
17612 - If we fail to free a microdescriptor because of bug 7164, log
17613 the filename and line number from which we tried to free it.
17614 - We compute the overhead from passing onionskins back and forth to
17615 cpuworkers, and report it when dumping statistics in response to
17616 SIGUSR1. Supports ticket 7291.
17617 - Add another diagnostic to the heartbeat message: track and log
17618 overhead that TLS is adding to the data we write. If this is
17619 high, we are sending too little data to SSL_write at a time.
17620 Diagnostic for bug 7707.
17621 - Log packaged cell fullness as part of the heartbeat message.
17622 Diagnosis to try to determine the extent of bug 7743.
17623 - Add more detail to a log message about relaxed timeouts, to help
17625 - When learning a fingerprint for a bridge, log its corresponding
17626 transport type. Implements ticket 7896.
17627 - Warn more aggressively when flushing microdescriptors to a
17628 microdescriptor cache fails, in an attempt to mitigate bug 8031,
17629 or at least make it more diagnosable.
17630 - Improve the log message when "Bug/attack: unexpected sendme cell
17631 from client" occurs, to help us track bug 8093.
17632 - Improve debugging output to help track down bug 8185 ("Bug:
17633 outgoing relay cell has n_chan==NULL. Dropping.")
17635 o Minor features (log messages, quieter bootstrapping):
17636 - Log fewer lines at level "notice" about our OpenSSL and Libevent
17637 versions and capabilities when everything is going right. Resolves
17638 part of ticket 6736.
17639 - Omit the first heartbeat log message, because it never has anything
17640 useful to say, and it clutters up the bootstrapping messages.
17641 Resolves ticket 6758.
17642 - Don't log about reloading the microdescriptor cache at startup. Our
17643 bootstrap warnings are supposed to tell the user when there's a
17644 problem, and our bootstrap notices say when there isn't. Resolves
17645 ticket 6759; bugfix on 0.2.2.6-alpha.
17646 - Don't log "I learned some more directory information" when we're
17647 reading cached directory information. Reserve it for when new
17648 directory information arrives in response to a fetch. Resolves
17650 - Don't complain about bootstrapping problems while hibernating.
17651 These complaints reflect a general code problem, but not one
17652 with any problematic effects (no connections are actually
17653 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
17655 o Minor features (testing):
17656 - In our testsuite, create temporary directories with a bit more
17657 entropy in their name to make name collisions less likely. Fixes
17659 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
17660 (P-256) Diffie-Hellman handshakes to src/or/bench.
17661 - Add benchmark functions to test onion handshake performance.
17664 - The DirServer option is now DirAuthority, for consistency with
17665 current naming patterns. You can still use the old DirServer form.
17667 o Minor bugfixes (protocol):
17668 - Fix the handling of a TRUNCATE cell when it arrives while the
17669 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
17670 - When a Tor client gets a "truncated" relay cell, the first byte of
17671 its payload specifies why the circuit was truncated. We were
17672 ignoring this 'reason' byte when tearing down the circuit, resulting
17673 in the controller not being told why the circuit closed. Now we
17674 pass the reason from the truncated cell to the controller. Bugfix
17675 on 0.1.2.3-alpha; fixes bug 7039.
17676 - Fix a misframing issue when reading the version numbers in a
17677 VERSIONS cell. Previously we would recognize [00 01 00 02] as
17678 'version 1, version 2, and version 0x100', when it should have
17679 only included versions 1 and 2. Fixes bug 8059; bugfix on
17680 0.2.0.10-alpha. Reported pseudonymously.
17681 - Make the format and order of STREAM events for DNS lookups
17682 consistent among the various ways to launch DNS lookups. Fixes
17683 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
17685 o Minor bugfixes (syscalls and disk interaction):
17686 - Always check the return values of functions fcntl() and
17687 setsockopt(). We don't believe these are ever actually failing in
17688 practice, but better safe than sorry. Also, checking these return
17689 values should please analysis tools like Coverity. Patch from
17690 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
17691 - Avoid double-closing the listener socket in our socketpair()
17692 replacement (used on Windows) in the case where the addresses on
17693 our opened sockets don't match what we expected. Fixes bug 9400;
17694 bugfix on 0.0.2pre7. Found by Coverity.
17695 - Correctly store microdescriptors and extrainfo descriptors that
17696 include an internal NUL byte. Fixes bug 8037; bugfix on
17697 0.2.0.1-alpha. Bug reported by "cypherpunks".
17698 - If for some reason we fail to write a microdescriptor while
17699 rebuilding the cache, do not let the annotations from that
17700 microdescriptor linger in the cache file, and do not let the
17701 microdescriptor stay recorded as present in its old location.
17702 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
17703 - Use direct writes rather than stdio when building microdescriptor
17704 caches, in an attempt to mitigate bug 8031, or at least make it
17707 o Minor fixes (config options):
17708 - Warn and fail if a server is configured not to advertise any
17709 ORPorts at all. (We need *something* to put in our descriptor,
17710 or we just won't work.)
17711 - Behave correctly when the user disables LearnCircuitBuildTimeout
17712 but doesn't tell us what they would like the timeout to be. Fixes
17713 bug 6304; bugfix on 0.2.2.14-alpha.
17714 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
17715 to start with a triple-underscore so the controller won't touch it.
17716 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
17717 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
17718 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
17719 - When autodetecting the number of CPUs, use the number of available
17720 CPUs in preference to the number of configured CPUs. Inform the
17721 user if this reduces the number of available CPUs. Fixes bug 8002;
17722 bugfix on 0.2.3.1-alpha.
17723 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
17724 - Make it an error when you set EntryNodes but disable UseGuardNodes,
17725 since it will (surprisingly to some users) ignore EntryNodes. Fixes
17726 bug 8180; bugfix on 0.2.3.11-alpha.
17727 - Avoid overflows when the user sets MaxCircuitDirtiness to a
17728 ridiculously high value, by imposing a (ridiculously high) 30-day
17729 maximum on MaxCircuitDirtiness.
17731 o Minor bugfixes (control protocol):
17732 - Stop sending a stray "(null)" in some cases for the server status
17733 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
17735 - The ADDRMAP command can no longer generate an ill-formed error
17736 code on a failed MAPADDRESS. It now says "internal" rather than
17737 an English sentence fragment with spaces in the middle. Bugfix on
17738 Tor 0.2.0.19-alpha.
17740 o Minor bugfixes (clients / edges):
17741 - When we receive a RELAY_END cell with the reason DONE, or with no
17742 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
17743 status as "connection refused". Previously we reported these cases
17744 as success but then immediately closed the connection. Fixes bug
17745 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
17746 - If the guard we choose first doesn't answer, we would try the
17747 second guard, but once we connected to the second guard we would
17748 abandon it and retry the first one, slowing down bootstrapping.
17749 The fix is to treat all our initially chosen guards as acceptable
17750 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
17751 - When choosing which stream on a formerly stalled circuit to wake
17752 first, make better use of the platform's weak RNG. Previously,
17753 we had been using the % ("modulo") operator to try to generate a
17754 1/N chance of picking each stream, but this behaves badly with
17755 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
17758 o Minor bugfixes (path bias detection):
17759 - If the state file's path bias counts are invalid (presumably from a
17760 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
17761 additional checks and log messages to the scaling of Path Bias
17762 counts, in case there still are remaining issues with scaling.
17763 Should help resolve bug 8235.
17764 - Prevent rounding error in path bias counts when scaling
17765 them down, and use the correct scale factor default. Also demote
17766 some path bias related log messages down a level and make others
17767 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
17768 - Remove a source of rounding error during path bias count scaling;
17769 don't count cannibalized circuits as used for path bias until we
17770 actually try to use them; and fix a circuit_package_relay_cell()
17771 warning message about n_chan==NULL. Fixes bug 7802.
17772 - Paste the description for PathBias parameters from the man
17773 page into or.h, so the code documents them too. Fixes bug 7982;
17774 bugfix on 0.2.3.17-beta.
17776 o Minor bugfixes (relays):
17777 - Stop trying to resolve our hostname so often (e.g. every time we
17778 think about doing a directory fetch). Now we reuse the cached
17779 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
17780 and 2410 (bugfix on 0.1.2.2-alpha).
17781 - When examining the list of network interfaces to find our address,
17782 do not consider non-running or disabled network interfaces. Fixes
17783 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
17785 o Minor bugfixes (blocking resistance):
17786 - Only disable TLS session ticket support when running as a TLS
17787 server. Now clients will blend better with regular Firefox
17788 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
17790 o Minor bugfixes (IPv6):
17791 - Use square brackets around IPv6 addresses in numerous places
17792 that needed them, including log messages, HTTPS CONNECT proxy
17793 requests, TransportProxy statefile entries, and pluggable transport
17794 extra-info lines. Fixes bug 7011; patch by David Fifield.
17796 o Minor bugfixes (directory authorities):
17797 - Reject consensus votes with more than 64 known-flags. We aren't even
17798 close to that limit yet, and our code doesn't handle it correctly.
17799 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
17800 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
17801 bugfix on 0.2.0.3-alpha.
17803 o Minor bugfixes (memory leaks):
17804 - Avoid leaking memory if we fail to compute a consensus signature
17805 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
17806 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
17807 on 0.2.1.1-alpha; fixes bug 7816.
17808 - Fix a memory leak during safe-cookie controller authentication.
17809 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
17810 - Free some more still-in-use memory at exit, to make hunting for
17811 memory leaks easier. Resolves bug 7029.
17813 o Minor bugfixes (code correctness):
17814 - Increase the width of the field used to remember a connection's
17815 link protocol version to two bytes. Harmless for now, since the
17816 only currently recognized versions are one byte long. Reported
17817 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
17818 - Fix a crash when debugging unit tests on Windows: deallocate a
17819 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
17820 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
17821 - When detecting the largest possible file descriptor (in order to
17822 close all file descriptors when launching a new program), actually
17823 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
17824 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
17826 - Avoid a crash if we fail to generate an extrainfo descriptor.
17827 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
17828 this is CID 718634.
17829 - Avoid an off-by-one error when checking buffer boundaries when
17830 formatting the exit status of a pluggable transport helper.
17831 This is probably not an exploitable bug, but better safe than
17832 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
17834 - Get rid of a couple of harmless clang warnings, where we compared
17835 enums to ints. These warnings are newly introduced in clang 3.2.
17837 o Minor bugfixes (code cleanliness):
17838 - Avoid use of reserved identifiers in our C code. The C standard
17839 doesn't like us declaring anything that starts with an
17840 underscore, so let's knock it off before we get in trouble. Fix
17841 for bug 1031; bugfix on the first Tor commit.
17842 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
17843 with large values. This situation was untriggered, but nevertheless
17844 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
17845 - Fix an impossible buffer overrun in the AES unit tests. Fixes
17846 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
17847 - Fix handling of rendezvous client authorization types over 8.
17848 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
17849 - Remove a couple of extraneous semicolons that were upsetting the
17850 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
17851 bugfix on 0.2.2.1-alpha.
17852 - When complaining about a client port on a public address, log
17853 which address we're complaining about. Fixes bug 4020; bugfix on
17854 0.2.3.3-alpha. Patch by Tom Fitzhenry.
17856 o Minor bugfixes (log messages, warnings):
17857 - If we encounter a write failure on a SOCKS connection before we
17858 finish our SOCKS handshake, don't warn that we closed the
17859 connection before we could send a SOCKS reply. Fixes bug 8427;
17860 bugfix on 0.1.0.1-rc.
17861 - Fix a directory authority warn caused when we have a large amount
17862 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
17863 - Downgrade "Failed to hand off onionskin" messages to "debug"
17864 severity, since they're typically redundant with the "Your computer
17865 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
17866 - Avoid spurious warnings when configuring multiple client ports of
17867 which only some are nonlocal. Previously, we had claimed that some
17868 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
17871 o Minor bugfixes (log messages, other):
17872 - Fix log messages and comments to avoid saying "GMT" when we mean
17873 "UTC". Fixes bug 6113.
17874 - When rejecting a configuration because we were unable to parse a
17875 quoted string, log an actual error message. Fixes bug 7950; bugfix
17877 - Correctly recognize that [::1] is a loopback address. Fixes
17878 bug 8377; bugfix on 0.2.1.3-alpha.
17879 - Don't log inappropriate heartbeat messages when hibernating: a
17880 hibernating node is _expected_ to drop out of the consensus,
17881 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
17882 bugfix on 0.2.3.1-alpha.
17883 - Eliminate several instances where we use "Nickname=ID" to refer to
17884 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
17885 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
17888 o Minor bugfixes (build):
17889 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
17890 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
17891 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
17893 o Documentation fixes:
17894 - Make the torify manpage no longer refer to tsocks; torify hasn't
17895 supported tsocks since 0.2.3.14-alpha.
17896 - Make the tor manpage no longer reference tsocks.
17897 - Fix the GeoIPExcludeUnknown documentation to refer to
17898 ExcludeExitNodes rather than the currently nonexistent
17899 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
17900 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
17902 - Say "KBytes" rather than "KB" in the man page (for various values
17903 of K), to further reduce confusion about whether Tor counts in
17904 units of memory or fractions of units of memory. Resolves ticket 7054.
17905 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
17906 names match. Fixes bug 7768.
17907 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
17908 message is logged at notice, not at info.
17909 - Clarify the usage and risks of setting the ContactInfo torrc line
17910 for your relay or bridge. Resolves ticket 9854.
17911 - Add anchors to the manpage so we can link to the html version of
17912 the documentation for specific options. Resolves ticket 9866.
17913 - Replace remaining references to DirServer in man page and
17914 log entries. Resolves ticket 10124.
17916 o Removed features:
17917 - Stop exporting estimates of v2 and v3 directory traffic shares
17918 in extrainfo documents. They were unneeded and sometimes inaccurate.
17919 Also stop exporting any v2 directory request statistics. Resolves
17921 - Drop support for detecting and warning about versions of Libevent
17922 before 1.3e. Nothing reasonable ships with them any longer; warning
17923 the user about them shouldn't be needed. Resolves ticket 6826.
17924 - Now that all versions before 0.2.2.x are disallowed, we no longer
17925 need to work around their missing features. Remove a bunch of
17926 compatibility code.
17929 - The tor-tsocks.conf is no longer distributed or installed. We
17930 recommend that tsocks users use torsocks instead. Resolves
17932 - Remove some of the older contents of doc/ as obsolete; move others
17933 to torspec.git. Fixes bug 8965.
17935 o Code simplification:
17936 - Avoid using character buffers when constructing most directory
17937 objects: this approach was unwieldy and error-prone. Instead,
17938 build smartlists of strings, and concatenate them when done.
17939 - Rename "isin" functions to "contains", for grammar. Resolves
17941 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
17942 with the natural logarithm function from the system libm. Resolves
17944 - Start using OpenBSD's implementation of queue.h, so that we don't
17945 need to hand-roll our own pointer and list structures whenever we
17946 need them. (We can't rely on a sys/queue.h, since some operating
17947 systems don't have them, and the ones that do have them don't all
17948 present the same extensions.)
17949 - Start using OpenBSD's implementation of queue.h (originally by
17951 - Enhance our internal sscanf replacement so that we can eliminate
17952 the last remaining uses of the system sscanf. (Though those uses
17953 of sscanf were safe, sscanf itself is generally error prone, so
17954 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
17956 - Replace all calls to snprintf() outside of src/ext with
17957 tor_snprintf(). Also remove the #define to replace snprintf with
17958 _snprintf on Windows; they have different semantics, and all of
17959 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
17962 - Add a wrapper function for the common "log a message with a
17964 - Split the onion.c file into separate modules for the onion queue
17965 and the different handshakes it supports.
17966 - Move the client-side address-map/virtual-address/DNS-cache code
17967 out of connection_edge.c into a new addressmap.c module.
17968 - Move the entry node code from circuitbuild.c to its own file.
17969 - Move the circuit build timeout tracking code from circuitbuild.c
17971 - Source files taken from other packages now reside in src/ext;
17972 previously they were scattered around the rest of Tor.
17973 - Move the generic "config" code into a new file, and have "config.c"
17974 hold only torrc- and state-related code. Resolves ticket 6823.
17975 - Move the core of our "choose a weighted element at random" logic
17976 into its own function, and give it unit tests. Now the logic is
17977 testable, and a little less fragile too.
17978 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
17979 - Move last_reachable and testing_since from routerinfo_t to node_t.
17980 Implements ticket 5529.
17981 - Add replaycache_t structure, functions and unit tests, then refactor
17982 rend_service_introduce() to be more clear to read, improve, debug,
17983 and test. Resolves bug 6177.
17986 - Remove some now-needless code that tried to aggressively flush
17987 OR connections as data was added to them. Since 0.2.0.1-alpha, our
17988 cell queue logic has saved us from the failure mode that this code
17989 was supposed to prevent. Removing this code will limit the number
17990 of baroque control flow paths through Tor's network logic. Reported
17991 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
17992 - Remove unused code for parsing v1 directories and "running routers"
17993 documents. Fixes bug 6887.
17994 - Remove the marshalling/unmarshalling code for sending requests to
17995 cpuworkers over a socket, and instead just send structs. The
17996 recipient will always be the same Tor binary as the sender, so
17997 any encoding is overkill.
17998 - Remove the testing_since field of node_t, which hasn't been used
17999 for anything since 0.2.0.9-alpha.
18000 - Finally remove support for malloc_good_size and malloc_usable_size.
18001 We had hoped that these functions would let us eke a little more
18002 memory out of our malloc implementation. Unfortunately, the only
18003 implementations that provided these functions are also ones that
18004 are already efficient about not overallocation: they never got us
18005 more than 7 or so bytes per allocation. Removing them saves us a
18006 little code complexity and a nontrivial amount of build complexity.
18009 Changes in version 0.2.3.25 - 2012-11-19
18010 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
18011 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
18012 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
18013 programmer, and friend. Unstinting in his dedication to the cause of
18014 freedom, he inspired and helped many of us as we began our work on
18015 anonymity, and inspires us still. Please honor his memory by writing
18016 software to protect people's freedoms, and by helping others to do so.
18018 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
18019 significantly reduced directory overhead (via microdescriptors),
18020 enormous crypto performance improvements for fast relays on new
18021 enough hardware, a new v3 TLS handshake protocol that can better
18022 resist fingerprinting, support for protocol obfuscation plugins (aka
18023 pluggable transports), better scalability for hidden services, IPv6
18024 support for bridges, performance improvements like allowing clients
18025 to skip the first round-trip on the circuit ("optimistic data") and
18026 refilling token buckets more often, a new "stream isolation" design
18027 to isolate different applications on different circuits, and many
18028 stability, security, and privacy fixes.
18030 Major features (v3 directory protocol):
18031 - Clients now use microdescriptors instead of regular descriptors
18032 to build circuits. Microdescriptors are authority-generated
18033 summaries of regular descriptors' contents, designed to change very
18034 rarely (see proposal 158 for details). This feature is designed
18035 to save bandwidth, especially for clients on slow internet
18036 connections. Use "UseMicrodescriptors 0" to disable it.
18037 - Caches now download, cache, and serve microdescriptors, as well
18038 as multiple "flavors" of the consensus, including a flavor that
18039 describes microdescriptors.
18041 o Major features (build hardening):
18042 - Enable gcc and ld hardening by default. Resolves ticket 5210.
18044 o Major features (relay scaling):
18045 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
18046 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
18047 vectorized AES implementations as appropriate. These can be much,
18048 much faster than other AES implementations.
18049 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
18050 implementation. It makes AES_CTR about 7% faster than our old one
18051 (which was about 10% faster than the one OpenSSL used to provide).
18052 Resolves ticket 4526.
18053 - Use OpenSSL's EVP interface for AES encryption, so that all AES
18054 operations can use hardware acceleration (if present). Resolves
18056 - Unconditionally use OpenSSL's AES implementation instead of our
18057 old built-in one. OpenSSL's AES has been better for a while, and
18058 relatively few servers should still be on any version of OpenSSL
18059 that doesn't have good optimized assembly AES.
18061 o Major features (blocking resistance):
18062 - Update TLS cipher list to match Firefox 8 and later. Resolves
18064 - Remove support for clients falsely claiming to support standard
18065 ciphersuites that they can actually provide. As of modern OpenSSL
18066 versions, it's not necessary to fake any standard ciphersuite,
18067 and doing so prevents us from using better ciphersuites in the
18068 future, since servers can't know whether an advertised ciphersuite
18069 is really supported or not. Some hosts -- notably, ones with very
18070 old versions of OpenSSL or where OpenSSL has been built with ECC
18071 disabled -- will stand out because of this change; TBB users should
18072 not be affected. Implements the client side of proposal 198.
18073 - Implement a new handshake protocol (v3) for authenticating Tors to
18074 each other over TLS. It should be more resistant to fingerprinting
18075 than previous protocols, and should require less TLS hacking for
18076 future Tor implementations. Implements proposal 176.
18077 - Allow variable-length padding cells, to disguise the length of
18078 Tor's TLS records. Implements part of proposal 184.
18079 - While we're trying to bootstrap, record how many TLS connections
18080 fail in each state, and report which states saw the most failures
18081 in response to any bootstrap failures. This feature may speed up
18082 diagnosis of censorship events. Implements ticket 3116.
18084 o Major features (pluggable transports):
18085 - Clients and bridges can now be configured to use a separate
18086 "transport" proxy. This approach makes the censorship arms race
18087 easier by allowing bridges to use protocol obfuscation plugins.
18088 Implements proposal 180 (tickets 2841 and 3472).
18090 o Major features (DoS resistance):
18091 - Now that Tor 0.2.0.x is completely deprecated, enable the final
18092 part of "Proposal 110: Avoiding infinite length circuits" by
18093 refusing all circuit-extend requests that do not use a relay_early
18094 cell. This change helps Tor resist a class of denial-of-service
18095 attacks by limiting the maximum circuit length.
18096 - Tear down the circuit if we get an unexpected SENDME cell. Clients
18097 could use this trick to make their circuits receive cells faster
18098 than our flow control would have allowed, or to gum up the network,
18099 or possibly to do targeted memory denial-of-service attacks on
18100 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
18101 from July 2002, before the release of Tor 0.0.0.
18103 o Major features (hidden services):
18104 - Adjust the number of introduction points that a hidden service
18105 will try to maintain based on how long its introduction points
18106 remain in use and how many introductions they handle. Fixes
18108 - Add a "tor2web mode" for clients that want to connect to hidden
18109 services non-anonymously (and possibly more quickly). As a safety
18110 measure to try to keep users from turning this on without knowing
18111 what they are doing, tor2web mode must be explicitly enabled at
18112 compile time, and a copy of Tor compiled to run in tor2web mode
18113 cannot be used as a normal Tor client. Implements feature 2553.
18115 o Major features (IPv6):
18116 - Clients can now connect to private bridges over IPv6. Bridges
18117 still need at least one IPv4 address in order to connect to
18118 other relays. Note that we don't yet handle the case where the
18119 user has two bridge lines for the same bridge (one IPv4, one
18120 IPv6). Implements parts of proposal 186.
18122 o Major features (directory authorities):
18123 - Use a more secure consensus parameter voting algorithm. Now at
18124 least three directory authorities or a majority of them must
18125 vote on a given parameter before it will be included in the
18126 consensus. Implements proposal 178.
18127 - Remove the artificially low cutoff of 20KB to guarantee the Fast
18128 flag. In the past few years the average relay speed has picked
18129 up, and while the "top 7/8 of the network get the Fast flag" and
18130 "all relays with 20KB or more of capacity get the Fast flag" rules
18131 used to have the same result, now the top 7/8 of the network has
18132 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
18134 o Major features (performance):
18135 - Exit nodes now accept and queue data on not-yet-connected streams.
18136 Previously, the client wasn't allowed to send data until the
18137 stream was connected, which slowed down all connections. This
18138 change will enable clients to perform a "fast-start" on streams
18139 and send data without having to wait for a confirmation that the
18140 stream has opened. Patch from Ian Goldberg; implements the server
18141 side of Proposal 174.
18142 - When using an exit relay running 0.2.3.x, clients can now
18143 "optimistically" send data before the exit relay reports that
18144 the stream has opened. This saves a round trip when starting
18145 connections where the client speaks first (such as web browsing).
18146 This behavior is controlled by a consensus parameter (currently
18147 disabled). To turn it on or off manually, use the "OptimisticData"
18148 torrc option. Implements proposal 181; code by Ian Goldberg.
18149 - Add a new TokenBucketRefillInterval option to refill token buckets
18150 more frequently than once per second. This should improve network
18151 performance, alleviate queueing problems, and make traffic less
18152 bursty. Implements proposal 183; closes ticket 3630. Design by
18153 Florian Tschorsch and Björn Scheuermann; implementation by
18155 - Raise the threshold of server descriptors needed (75%) and exit
18156 server descriptors needed (50%) before we will declare ourselves
18157 bootstrapped. This will make clients start building circuits a
18158 little later, but makes the initially constructed circuits less
18159 skewed and less in conflict with further directory fetches. Fixes
18162 o Major features (relays):
18163 - Relays now try regenerating and uploading their descriptor more
18164 frequently if they are not listed in the consensus, or if the
18165 version of their descriptor listed in the consensus is too
18166 old. This fix should prevent situations where a server declines
18167 to re-publish itself because it has done so too recently, even
18168 though the authorities decided not to list its recent-enough
18169 descriptor. Fix for bug 3327.
18171 o Major features (stream isolation):
18172 - You can now configure Tor so that streams from different
18173 applications are isolated on different circuits, to prevent an
18174 attacker who sees your streams as they leave an exit node from
18175 linking your sessions to one another. To do this, choose some way
18176 to distinguish the applications: have them connect to different
18177 SocksPorts, or have one of them use SOCKS4 while the other uses
18178 SOCKS5, or have them pass different authentication strings to the
18179 SOCKS proxy. Then, use the new SocksPort syntax to configure the
18180 degree of isolation you need. This implements Proposal 171.
18181 - There's a new syntax for specifying multiple client ports (such as
18182 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
18183 multiple *Port entries with full addr:port syntax on each.
18184 The old *ListenAddress format is still supported, but you can't
18185 mix it with the new *Port syntax.
18187 o Major features (bufferevents):
18188 - Tor can now optionally build with the "bufferevents" buffered IO
18189 backend provided by Libevent 2. To use this feature, make sure you
18190 have the latest possible version of Libevent, and pass the
18191 --enable-bufferevents flag to configure when building Tor from
18192 source. This feature will make our networking code more flexible,
18193 let us stack layers on each other, and let us use more efficient
18194 zero-copy transports where available.
18195 - Add experimental support for running on Windows with IOCP and no
18196 kernel-space socket buffers. This feature is controlled by a new
18197 "UserspaceIOCPBuffers" config option (off by default), which has
18198 no effect unless Tor has been built with bufferevents enabled,
18199 you're running on Windows, and you've set "DisableIOCP 0". In the
18200 long run, this may help solve or mitigate bug 98.
18202 o Major features (path selection):
18203 - The EntryNodes option can now include country codes like {de} or IP
18204 addresses or network masks. Previously we had disallowed these
18205 options because we didn't have an efficient way to keep the list up
18206 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
18209 o Major features (port forwarding):
18210 - Add support for automatic port mapping on the many home routers
18211 that support NAT-PMP or UPnP. To build the support code, you'll
18212 need to have the libnatpnp library and/or the libminiupnpc library,
18213 and you'll need to enable the feature specifically by passing
18214 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
18215 it on, use the new PortForwarding option.
18217 o Major features (logging):
18218 - Add a new 'Heartbeat' log message type to periodically log a message
18219 describing Tor's status at level Notice. This feature is meant for
18220 operators who log at notice, and want to make sure that their Tor
18221 server is still working. Implementation by George Kadianakis.
18222 - Make logging resolution configurable with a new LogTimeGranularity
18223 option, and change the default from 1 millisecond to 1 second.
18224 Implements enhancement 1668.
18226 o Major features (other):
18227 - New "DisableNetwork" config option to prevent Tor from launching any
18228 connections or accepting any connections except on a control port.
18229 Bundles and controllers can set this option before letting Tor talk
18230 to the rest of the network, for example to prevent any connections
18231 to a non-bridge address. Packages like Orbot can also use this
18232 option to instruct Tor to save power when the network is off.
18233 - Try to use system facilities for enumerating local interface
18234 addresses, before falling back to our old approach (which was
18235 binding a UDP socket, and calling getsockname() on it). That
18236 approach was scaring OS X users whose draconian firewall
18237 software warned about binding to UDP sockets regardless of
18238 whether packets were sent. Now we try to use getifaddrs(),
18239 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
18240 system supports. Resolves ticket 1827.
18241 - Add experimental support for a "defaults" torrc file to be parsed
18242 before the regular torrc. Torrc options override the defaults file's
18243 options in the same way that the command line overrides the torrc.
18244 The SAVECONF controller command saves only those options which
18245 differ between the current configuration and the defaults file. HUP
18246 reloads both files. Implements task 4552.
18248 o New directory authorities:
18249 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
18250 authority. Closes ticket 5749.
18252 o Security/privacy fixes:
18253 - Avoid read-from-freed-memory and double-free bugs that could occur
18254 when a DNS request fails while launching it. Fixes bug 6480;
18255 bugfix on 0.2.0.1-alpha.
18256 - Reject any attempt to extend to an internal address. Without
18257 this fix, a router could be used to probe addresses on an internal
18258 network to see whether they were accepting connections. Fixes bug
18259 6710; bugfix on 0.0.8pre1.
18260 - Close any connection that sends unrecognized junk before the TLS
18261 handshake. Solves an issue noted in bug 4369.
18262 - The advertised platform of a relay now includes only its operating
18263 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
18264 its service pack level (for Windows) or its CPU architecture
18265 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
18266 can insert an extra string in the platform line by setting the
18267 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
18268 - Disable TLS session tickets. OpenSSL's implementation was giving
18269 our TLS session keys the lifetime of our TLS context objects, when
18270 perfect forward secrecy would want us to discard anything that
18271 could decrypt a link connection as soon as the link connection
18272 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
18273 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
18274 - Tor tries to wipe potentially sensitive data after using it, so
18275 that if some subsequent security failure exposes Tor's memory,
18276 the damage will be limited. But we had a bug where the compiler
18277 was eliminating these wipe operations when it decided that the
18278 memory was no longer visible to a (correctly running) program,
18279 hence defeating our attempt at defense in depth. We fix that
18280 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
18281 is unlikely to optimize away. Future versions of Tor may use
18282 a less ridiculously heavy approach for this. Fixes bug 7352.
18283 Reported in an article by Andrey Karpov.
18285 o Major bugfixes (crashes and asserts):
18286 - Avoid a pair of double-free and use-after-mark bugs that can
18287 occur with certain timings in canceled and re-received DNS
18288 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
18289 - Fix a denial of service attack by which any directory authority
18290 could crash all the others, or by which a single v2 directory
18291 authority could crash everybody downloading v2 directory
18292 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
18293 - Fix an assert that directory authorities could trigger on sighup
18294 during some configuration state transitions. We now don't treat
18295 it as a fatal error when the new descriptor we just generated in
18296 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
18297 - Avoid segfault when starting up having run with an extremely old
18298 version of Tor and parsing its state file. Fixes bug 6801; bugfix
18301 o Major bugfixes (clients):
18302 - If we are unable to find any exit that supports our predicted ports,
18303 stop calling them predicted, so that we don't loop and build
18304 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
18305 which introduced predicted ports.
18306 - Check at each new consensus whether our entry guards were picked
18307 long enough ago that we should rotate them. Previously, we only
18308 did this check at startup, which could lead to us holding a guard
18309 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
18310 - When fetching a bridge descriptor from a bridge authority,
18311 always do so anonymously, whether we have been able to open
18312 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
18313 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
18314 but we'll need to wait for bug 6010 before it's actually usable.
18316 o Major bugfixes (directory voting):
18317 - Check more thoroughly to prevent a rogue authority from
18318 double-voting on any consensus directory parameter. Previously,
18319 authorities would crash in this case if the total number of
18320 votes for any parameter exceeded the number of active voters,
18321 but would let it pass otherwise. Partially fixes bug 5786; bugfix
18323 - When computing weight parameters, behave more robustly in the
18324 presence of a bad bwweightscale value. Previously, the authorities
18325 would crash if they agreed on a sufficiently broken weight_scale
18326 value; now, they use a reasonable default and carry on. Fixes the
18327 rest of bug 5786; bugfix on 0.2.2.17-alpha.
18328 - If authorities are unable to get a v2 consensus document from other
18329 directory authorities, they no longer fall back to fetching
18330 them from regular directory caches. Fixes bug 5635; bugfix on
18331 0.2.2.26-beta, where routers stopped downloading v2 consensus
18332 documents entirely.
18334 o Major bugfixes (relays):
18335 - Fix a bug handling SENDME cells on nonexistent streams that could
18336 result in bizarre window values. Report and patch contributed
18337 pseudonymously. Fixes part of bug 6271. This bug was introduced
18338 before the first Tor release, in svn commit r152.
18339 - Don't update the AccountingSoftLimitHitAt state file entry whenever
18340 tor gets started. This prevents a wrong average bandwidth
18341 estimate, which would cause relays to always start a new accounting
18342 interval at the earliest possible moment. Fixes bug 2003; bugfix
18343 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
18344 immensely in tracking this bug down.
18345 - Fix a possible crash bug when checking for deactivated circuits
18346 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
18347 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
18348 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
18349 connections. This change should allow busy exit relays to stop
18350 running out of available sockets as quickly. Fixes bug 4950;
18351 bugfix on 0.2.2.26-beta.
18353 o Major bugfixes (blocking resistance):
18354 - Bridges no longer include their address in NETINFO cells on outgoing
18355 OR connections, to allow them to blend in better with clients.
18356 Removes another avenue for enumerating bridges. Reported by
18357 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
18358 cells were introduced.
18359 - Warn the user when HTTPProxy, but no other proxy type, is
18360 configured. This can cause surprising behavior: it doesn't send
18361 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
18362 directory traffic only. Resolves ticket 4663.
18364 o Major bugfixes (hidden services):
18365 - Improve hidden service robustness: when an attempt to connect to
18366 a hidden service ends, be willing to refetch its hidden service
18367 descriptors from each of the HSDir relays responsible for them
18368 immediately. Previously, we would not consider refetching the
18369 service's descriptors from each HSDir for 15 minutes after the last
18370 fetch, which was inconvenient if the hidden service was not running
18371 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
18372 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
18373 They used to check that the timestamp was within 30 minutes
18374 of their system clock, so they could cap the size of their
18375 replay-detection cache, but that approach unnecessarily refused
18376 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
18377 the v3 intro-point protocol (the first one which sent a timestamp
18378 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
18379 - When one of a hidden service's introduction points appears to be
18380 unreachable, stop trying it. Previously, we would keep trying
18381 to build circuits to the introduction point until we lost the
18382 descriptor, usually because the user gave up and restarted Tor.
18383 Fixes part of bug 3825.
18385 o Changes to default torrc file:
18386 - Stop listing "socksport 9050" in torrc.sample. We open a socks
18387 port on 9050 by default anyway, so this should not change anything
18389 - Stop mentioning the deprecated *ListenAddress options in
18390 torrc.sample. Fixes bug 5438.
18391 - Document unit of bandwidth-related options in sample torrc.
18393 - Fix broken URLs in the sample torrc file, and tell readers about
18394 the OutboundBindAddress, ExitPolicyRejectPrivate, and
18395 PublishServerDescriptor options. Addresses bug 4652.
18397 o Minor features (directory authorities):
18398 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
18399 change when the authority is deciding whether to accept a newly
18400 uploaded descriptor. Implements ticket 6423.
18401 - Directory authorities are now a little more lenient at accepting
18402 older router descriptors, or newer router descriptors that don't
18403 make big changes. This should help ameliorate past and future
18404 issues where routers think they have uploaded valid descriptors,
18405 but the authorities don't think so. Fix for ticket 2479.
18406 - Authority operators can now vote for all relays in a given
18407 set of countries to be BadDir/BadExit/Invalid/Rejected.
18408 - Provide two consensus parameters (FastFlagMinThreshold and
18409 FastFlagMaxThreshold) to control the range of allowable bandwidths
18410 for the Fast directory flag. These allow authorities to run
18411 experiments on appropriate requirements for being a "Fast" node.
18412 The AuthDirFastGuarantee config value still applies. Implements
18415 o Minor features (bridges / bridge authorities):
18416 - Make bridge SSL certificates a bit more stealthy by using random
18417 serial numbers, in the same fashion as OpenSSL when generating
18418 self-signed certificates. Implements ticket 4584.
18419 - Tag a bridge's descriptor as "never to be sent unencrypted".
18420 This shouldn't matter, since bridges don't open non-anonymous
18421 connections to the bridge authority and don't allow unencrypted
18422 directory connections from clients, but we might as well make
18423 sure. Closes bug 5139.
18424 - The Bridge Authority now writes statistics on how many bridge
18425 descriptors it gave out in total, and how many unique descriptors
18426 it gave out. It also lists how often the most and least commonly
18427 fetched descriptors were given out, as well as the median and
18428 25th/75th percentile. Implements tickets 4200 and 4294.
18430 o Minor features (IPv6):
18431 - Make the code that clients use to detect an address change be
18432 IPv6-aware, so that it won't fill clients' logs with error
18433 messages when trying to get the IPv4 address of an IPv6
18434 connection. Implements ticket 5537.
18435 - Relays now understand an IPv6 address when they get one from a
18436 directory server. Resolves ticket 4875.
18438 o Minor features (hidden services):
18439 - Expire old or over-used hidden service introduction points.
18440 Required by fix for bug 3460.
18441 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
18442 public key replay-detection cache from 60 minutes to 5 minutes. This
18443 replay-detection cache is now used only to detect multiple
18444 INTRODUCE2 cells specifying the same rendezvous point, so we can
18445 avoid launching multiple simultaneous attempts to connect to it.
18446 - When a hidden service's introduction point times out, consider
18447 trying it again during the next attempt to connect to the
18448 HS. Previously, we would not try it again unless a newly fetched
18449 descriptor contained it. Required by fixes for bugs 1297 and 3825.
18451 o Minor features (relays):
18452 - Relays now include a reason for regenerating their descriptors
18453 in an HTTP header when uploading to the authorities. This will
18454 make it easier to debug descriptor-upload issues in the future.
18455 - Turn on directory request statistics by default and include them in
18456 extra-info descriptors. Don't break if we have no GeoIP database.
18457 - Replace files in stats/ rather than appending to them. Now that we
18458 include statistics in extra-info descriptors, it makes no sense to
18459 keep old statistics forever. Implements ticket 2930.
18460 - Relays that set "ConnDirectionStatistics 1" write statistics on the
18461 bidirectional use of connections to disk every 24 hours.
18462 - Add a GeoIP file digest to the extra-info descriptor. Implements
18465 o Minor features (new config options):
18466 - New config option "DynamicDHGroups" (disabled by default) provides
18467 each bridge with a unique prime DH modulus to be used during
18468 SSL handshakes. This option attempts to help against censors
18469 who might use the Apache DH modulus as a static identifier for
18470 bridges. Addresses ticket 4548.
18471 - New config option "DisableDebuggerAttachment" (on by default)
18472 to prevent basic debugging attachment attempts by other processes.
18473 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
18474 - Ordinarily, Tor does not count traffic from private addresses (like
18475 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
18476 There is now a new option, CountPrivateBandwidth, to disable this
18477 behavior. Patch from Daniel Cagara.
18479 o Minor features (different behavior for old config options):
18480 - Allow MapAddress directives to specify matches against super-domains,
18481 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
18482 Implements issue 933.
18483 - Don't disable the DirPort when we cannot exceed our AccountingMax
18484 limit during this interval because the effective bandwidthrate is
18485 low enough. This is useful in a situation where AccountMax is only
18486 used as an additional safeguard or to provide statistics.
18487 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
18488 implements ticket 3439.
18489 - When configuring a large set of nodes in EntryNodes, and there are
18490 enough of them listed as Guard so that we don't need to consider
18491 the non-guard entries, prefer the ones listed with the Guard flag.
18492 - If you set the NumCPUs option to 0, Tor will now try to detect how
18493 many CPUs you have. This is the new default behavior.
18494 - The NodeFamily option -- which let you declare that you want to
18495 consider nodes to be part of a family whether they list themselves
18496 that way or not -- now allows IP address ranges and country codes.
18498 o Minor features (new command-line config behavior):
18499 - Slightly change behavior of "list" options (that is, config
18500 options that can appear more than once) when they appear both in
18501 torrc and on the command line. Previously, the command-line options
18502 would be appended to the ones from torrc. Now, the command-line
18503 options override the torrc options entirely. This new behavior
18504 allows the user to override list options (like exit policies and
18505 ports to listen on) from the command line, rather than simply
18506 appending to the list.
18507 - You can get the old (appending) command-line behavior for "list"
18508 options by prefixing the option name with a "+".
18509 - You can remove all the values for a "list" option from the command
18510 line without adding any new ones by prefixing the option name
18513 o Minor features (controller, new events):
18514 - Extend the control protocol to report flags that control a circuit's
18515 path selection in CIRC events and in replies to 'GETINFO
18516 circuit-status'. Implements part of ticket 2411.
18517 - Extend the control protocol to report the hidden service address
18518 and current state of a hidden-service-related circuit in CIRC
18519 events and in replies to 'GETINFO circuit-status'. Implements part
18521 - Include the creation time of a circuit in CIRC and CIRC2
18522 control-port events and the list produced by the 'GETINFO
18523 circuit-status' control-port command.
18524 - Add a new CONF_CHANGED event so that controllers can be notified
18525 of any configuration changes made by other controllers, or by the
18526 user. Implements ticket 1692.
18527 - Add a new SIGNAL event to the controller interface so that
18528 controllers can be notified when Tor handles a signal. Resolves
18529 issue 1955. Patch by John Brooks.
18531 o Minor features (controller, new getinfo options):
18532 - Expose our view of whether we have gone dormant to the controller,
18533 via a new "GETINFO dormant" value. Torbutton and other controllers
18534 can use this to avoid doing periodic requests through Tor while
18535 it's dormant (bug 4718). Resolves ticket 5954.
18536 - Add a new GETINFO option to get total bytes read and written. Patch
18537 from pipe, revised by atagar. Resolves ticket 2345.
18538 - Implement new GETINFO controller fields to provide information about
18539 the Tor process's pid, euid, username, and resource limits.
18541 o Minor features (controller, other):
18542 - Allow controllers to request an event notification whenever a
18543 circuit is cannibalized or its purpose is changed. Implements
18544 part of ticket 3457.
18545 - Use absolute path names when reporting the torrc filename in the
18546 control protocol, so a controller can more easily find the torrc
18547 file. Resolves bug 1101.
18548 - When reporting the path to the cookie file to the controller,
18549 give an absolute path. Resolves ticket 4881.
18551 o Minor features (log messages):
18552 - Add more information to a log statement that might help track down
18553 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
18554 non-IP address" messages (or any Bug messages, for that matter!),
18555 please let us know about it.
18556 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
18557 EntryNodes will have no effect. Resolves issue 2571.
18558 - Try to make the introductory warning message that Tor prints on
18559 startup more useful for actually finding help and information.
18560 Resolves ticket 2474.
18561 - When the system call to create a listener socket fails, log the
18562 error message explaining why. This may help diagnose bug 4027.
18564 o Minor features (other):
18565 - When we fail to initialize Libevent, retry with IOCP disabled so we
18566 don't need to turn on multi-threading support in Libevent, which in
18567 turn requires a working socketpair(). This is a workaround for bug
18568 4457, which affects Libevent versions from 2.0.1-alpha through
18570 - When starting as root and then changing our UID via the User
18571 control option, and we have a ControlSocket configured, make sure
18572 that the ControlSocket is owned by the same account that Tor will
18573 run under. Implements ticket 3421; fix by Jérémy Bobbio.
18574 - Accept attempts to include a password authenticator in the
18575 handshake, as supported by SOCKS5. This handles SOCKS clients that
18576 don't know how to omit a password when authenticating. Resolves
18578 - Check for and recover from inconsistency in the microdescriptor
18579 cache. This will make it harder for us to accidentally free a
18580 microdescriptor without removing it from the appropriate data
18581 structures. Fixes issue 3135; issue noted by "wanoskarnet".
18582 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
18584 o Minor bugfixes (code security):
18585 - Prevent a null-pointer dereference when receiving a data cell
18586 for a nonexistent stream when the circuit in question has an
18587 empty deliver window. We don't believe this is triggerable,
18588 since we don't currently allow deliver windows to become empty,
18589 but the logic is tricky enough that it's better to make the code
18590 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
18591 - Fix a (harmless) integer overflow in cell statistics reported by
18592 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
18593 - Fix our implementation of crypto_random_hostname() so it can't
18594 overflow on ridiculously large inputs. (No Tor version has ever
18595 provided this kind of bad inputs, but let's be correct in depth.)
18596 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
18597 - Add a (probably redundant) memory clear between iterations of
18598 the router status voting loop, to prevent future coding errors
18599 where data might leak between iterations of the loop. Resolves
18602 o Minor bugfixes (wrapper functions):
18603 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
18604 utility function used in the control-port code). This shouldn't
18605 ever happen unless Tor is completely out of memory, but if it did
18606 happen and Tor somehow recovered from it, Tor could have sent a log
18607 message to a control port in the middle of a reply to a controller
18608 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
18609 - Fix some (not actually triggerable) buffer size checks in usage of
18610 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
18612 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
18613 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
18614 - Enforce correct return behavior of tor_vsscanf() when the '%%'
18615 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
18616 - Make our replacement implementation of strtok_r() compatible with
18617 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
18618 bugfix on 0.2.2.1-alpha.
18619 - Find more places in the code that should have been testing for
18620 invalid sockets using the SOCKET_OK macro. Required for a fix
18621 for bug 4533. Bugfix on 0.2.2.28-beta.
18623 o Minor bugfixes (code correctness):
18624 - Check return value of fputs() when writing authority certificate
18625 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
18626 - When building Tor on Windows with -DUNICODE (not default), ensure
18627 that error messages, filenames, and DNS server names are always
18628 NUL-terminated when we convert them to a single-byte encoding.
18629 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
18630 - Fix a memory leak when trying to launch a DNS request when the
18631 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
18633 - Correct file sizes when reading binary files on Cygwin, to avoid
18634 a bug where Tor would fail to read its state file. Fixes bug 6844;
18635 bugfix on 0.1.2.7-alpha.
18636 - Make sure to set *socket_error in all error cases in
18637 connection_connect(), so it can't produce a warning about
18638 errno being zero from errno_to_orconn_end_reason(). Bugfix on
18639 0.2.1.1-alpha; resolves ticket 6028.
18640 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
18641 bug 4532; found by "troll_un".
18643 o Minor bugfixes (clients):
18644 - Allow one-hop directory-fetching circuits the full "circuit build
18645 timeout" period, rather than just half of it, before failing them
18646 and marking the relay down. This fix should help reduce cases where
18647 clients declare relays (or worse, bridges) unreachable because
18648 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
18649 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
18651 - Ensure we don't cannibalize circuits that are longer than three hops
18652 already, so we don't end up making circuits with 5 or more
18653 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
18654 0.1.0.1-rc which introduced cannibalization.
18656 o Minor bugfixes (relays):
18657 - Don't publish a new relay descriptor when we reload our onion key,
18658 unless the onion key has actually changed. Fixes bug 3263 and
18659 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
18660 - When relays refuse a "create" cell because their queue of pending
18661 create cells is too big (typically because their cpu can't keep up
18662 with the arrival rate), send back reason "resource limit" rather
18663 than reason "internal", so network measurement scripts can get a
18664 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
18665 - Exit nodes don't need to fetch certificates for authorities that
18666 they don't recognize; only directory authorities, bridges,
18667 and caches need to do that. Fixes part of bug 2297; bugfix on
18670 o Minor bugfixes (directory authority / mirrors):
18671 - Avoid O(n^2) performance characteristics when parsing a large
18672 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
18673 - Authorities no longer include any router in their microdescriptor
18674 consensuses for which they couldn't generate or agree on a
18675 microdescriptor. Fixes the second piece of bug 6404; fix on
18677 - When checking for requested signatures on the latest consensus
18678 before serving it to a client, make sure to check the right
18679 consensus flavor. Bugfix on 0.2.2.6-alpha.
18680 - Fix an edge case where TestingTorNetwork is set but the authorities
18681 and relays all have an uptime of zero, so the private Tor network
18682 could briefly lack support for hidden services. Fixes bug 3886;
18683 bugfix on 0.2.2.18-alpha.
18684 - Directory caches no longer refuse to clean out descriptors because
18685 of missing v2 networkstatus documents, unless they're configured
18686 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
18687 0.2.2.26-beta. Patch by Daniel Bryg.
18688 - Don't serve or accept v2 hidden service descriptors over a relay's
18689 DirPort. It's never correct to do so, and disabling it might
18690 make it more annoying to exploit any bugs that turn up in the
18691 descriptor-parsing code. Fixes bug 7149.
18693 o Minor bugfixes (hidden services, client-side):
18694 - Assert that hidden-service-related operations are not performed
18695 using single-hop circuits. Previously, Tor would assert that
18696 client-side streams are not attached to single-hop circuits,
18697 but not that other sensitive operations on the client and service
18698 side are not performed using single-hop circuits. Fixes bug 3332;
18700 - Avoid undefined behavior when parsing the list of supported
18701 rendezvous/introduction protocols in a hidden service descriptor.
18702 Previously, Tor would have confused (as-yet-unused) protocol version
18703 numbers greater than 32 with lower ones on many platforms. Fixes
18704 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
18705 - Don't close hidden service client circuits which have almost
18706 finished connecting to their destination when they reach
18707 the normal circuit-build timeout. Previously, we would close
18708 introduction circuits which are waiting for an acknowledgement
18709 from the introduction point, and rendezvous circuits which have
18710 been specified in an INTRODUCE1 cell sent to a hidden service,
18711 after the normal CBT. Now, we mark them as 'timed out', and launch
18712 another rendezvous attempt in parallel. This behavior change can
18713 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
18714 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
18716 o Minor bugfixes (hidden services, service-side):
18717 - Don't close hidden-service-side rendezvous circuits when they
18718 reach the normal circuit-build timeout. This behavior change can
18719 be disabled using the new
18720 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
18721 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
18722 - Don't launch more than 10 service-side introduction-point circuits
18723 for a hidden service in five minutes. Previously, we would consider
18724 launching more introduction-point circuits if at least one second
18725 had passed without any introduction-point circuits failing. Fixes
18726 bug 4607; bugfix on 0.0.7pre1.
18728 o Minor bugfixes (config option behavior):
18729 - If the user tries to set MyFamily on a bridge, refuse to
18730 do so, and warn about the security implications. Fixes bug 4657;
18731 bugfix on 0.2.0.3-alpha.
18732 - The "--quiet" and "--hush" options now apply not only to Tor's
18733 behavior before logs are configured, but also to Tor's behavior in
18734 the absence of configured logs. Fixes bug 3550; bugfix on
18736 - Change the AllowDotExit rules so they should actually work.
18737 We now enforce AllowDotExit only immediately after receiving an
18738 address via SOCKS or DNSPort: other sources are free to provide
18739 .exit addresses after the resolution occurs. Fixes bug 3940;
18740 bugfix on 0.2.2.1-alpha.
18741 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
18742 don't depend on the consensus parameters or compute adaptive
18743 timeouts when it is disabled. Fixes bug 5049; bugfix on
18745 - After we pick a directory mirror, we would refuse to use it if
18746 it's in our ExcludeExitNodes list, resulting in mysterious failures
18747 to bootstrap for people who just wanted to avoid exiting from
18748 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
18749 - When told to add a bridge with the same digest as a preexisting
18750 bridge but a different addr:port, change the addr:port as
18751 requested. Previously we would not notice the change. Fixes half
18752 of bug 5603; fix on 0.2.2.26-beta.
18754 o Minor bugfixes (controller):
18755 - Allow manual 'authenticate' commands to the controller interface
18756 from netcat (nc) as well as telnet. We were rejecting them because
18757 they didn't come with the expected whitespace at the end of the
18758 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
18759 - Report a real bootstrap problem to the controller on router
18760 identity mismatch. Previously we just said "foo", which probably
18761 made a lot of sense at the time. Fixes bug 4169; bugfix on
18763 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
18764 option is set to 0 (which Vidalia version 0.2.16 now does when
18765 a SAVECONF attempt fails), perform other actions that SIGHUP
18766 usually causes (like reopening the logs). Fixes bug 5095; bugfix
18768 - Correctly handle checking the permissions on the parent
18769 directory of a control socket in the root directory. Bug found
18770 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
18772 - End AUTHCHALLENGE error messages (in the control protocol) with
18773 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
18775 o Minor bugfixes (network reading/writing):
18776 - Disable writing on marked-for-close connections when they are
18777 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
18778 bug 5263; bugfix on 0.0.2pre13, where we first added a special
18779 case for flushing marked connections.
18780 - Make sure that there are no unhandled pending TLS errors before
18781 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
18782 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
18783 Bugfix on 0.1.0.5-rc; fixes bug 4528.
18784 - Detect SSL handshake even when the initial attempt to write the
18785 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
18786 - If the client fails to set a reasonable set of ciphersuites
18787 during its v2 handshake renegotiation, allow the renegotiation to
18788 continue nevertheless (i.e. send all the required certificates).
18789 Fixes bug 4591; bugfix on 0.2.0.20-rc.
18791 o Minor bugfixes (other):
18792 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
18793 resource exhaustion, so that clients can adjust their load to
18794 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
18795 started using END_STREAM_REASON_RESOURCELIMIT.
18796 - Don't check for whether the address we're using for outbound
18797 connections has changed until after the outbound connection has
18798 completed. On Windows, getsockname() doesn't succeed until the
18799 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
18800 - Don't hold a Windows file handle open for every file mapping;
18801 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
18803 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
18804 bugfix on 0.2.1.10-alpha.
18805 - If we fail to write a microdescriptor to the disk cache, do not
18806 continue replacing the old microdescriptor file. Fixes bug 2954;
18807 bugfix on 0.2.2.6-alpha.
18809 o Minor bugfixes (log messages, path selection):
18810 - Downgrade "set buildtimeout to low value" messages to "info"
18811 severity; they were never an actual problem, there was never
18812 anything reasonable to do about them, and they tended to spam logs
18813 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
18814 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
18815 more information to it, so that we can track it down in case it
18816 returns again. Mitigates bug 5235.
18817 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
18818 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
18819 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
18820 - Issue a log message if a guard completes less than 40% of your
18821 circuits. Threshold is configurable by torrc option
18822 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
18823 additional, off-by-default code to disable guards which fail too
18824 many circuits. Addresses ticket 5458.
18826 o Minor bugfixes (log messages, client):
18827 - Downgrade "Got a certificate, but we already have it" log messages
18828 from warning to info, except when we're a dirauth. Fixes bug 5238;
18829 bugfix on 0.2.1.7-alpha.
18830 - Fix the log message describing how we work around discovering
18831 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
18832 4837; bugfix on 0.2.2.9-alpha.
18833 - When logging about a disallowed .exit name, do not also call it
18834 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
18835 - Fix a log message suggesting that people contact a non-existent
18836 email address. Fixes bug 3448.
18837 - Rephrase the log message emitted if the TestSocks check is
18838 successful. Patch from Fabian Keil; fixes bug 4094.
18839 - Log (at debug level) whenever a circuit's purpose is changed.
18840 - Log SSL state transitions at log level DEBUG, log domain
18841 HANDSHAKE. This can be useful for debugging censorship events.
18842 Implements ticket 3264.
18843 - We now log which torrc file we're using on startup. Implements
18845 - Rate-limit log messages when asked to connect anonymously to
18846 a private address. When these hit, they tended to hit fast and
18847 often. Also, don't bother trying to connect to addresses that we
18848 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
18849 reply makes us think we have been lied to, even when the address the
18850 client tried to connect to was "localhost." Resolves ticket 2822.
18852 o Minor bugfixes (log messages, non-client):
18853 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
18854 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
18855 - Don't log that we have "decided to publish new relay descriptor"
18856 unless we are actually publishing a descriptor. Fixes bug 3942;
18857 bugfix on 0.2.2.28-beta.
18858 - Log which authority we're missing votes from when we go to fetch
18859 them from the other auths.
18860 - Replace "Sending publish request" log messages with "Launching
18861 upload", so that they no longer confusingly imply that we're
18862 sending something to a directory we might not even be connected
18863 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
18864 - Warn when Tor is configured to use accounting in a way that can
18865 link a hidden service to some other hidden service or public
18866 address. Resolves ticket 6490.
18867 - Fix a minor formatting issue in one of tor-gencert's error messages.
18871 - Update to the latest version of the tinytest unit testing framework.
18872 This includes a couple of bugfixes that can be relevant for
18873 running forked unit tests on Windows, and removes all reserved
18875 - Avoid a false positive in the util/threads unit test by increasing
18876 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
18877 - Make it possible to set the TestingTorNetwork configuration
18878 option using AlternateDirAuthority and AlternateBridgeAuthority
18879 as an alternative to setting DirServer. Addresses ticket 6377.
18880 - Add a unit test for the environment_variable_names_equal() function.
18881 - A wide variety of new unit tests by Esteban Manchado Velázquez.
18882 - Numerous new unit tests for functions in util.c and address.c by
18884 - The long-disabled benchmark tests are now split into their own
18885 ./src/test/bench binary.
18886 - The benchmark tests can now use more accurate timers than
18887 gettimeofday() when such timers are available.
18888 - Use tt_assert(), not tor_assert(), for checking for test failures.
18889 This makes the unit tests more able to go on in the event that
18892 o Build improvements:
18893 - Use the dead_strip option when building Tor on OS X. This reduces
18894 binary size by almost 19% when linking openssl and libevent
18895 statically, which we do for Tor Browser Bundle.
18896 - Provide a better error message about possible OSX Asciidoc failure
18897 reasons. Fixes bug 6436.
18898 - Detect attempts to build Tor on (as yet hypothetical) versions
18899 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
18900 fix for bug 4533. Bugfix on 0.2.2.28-beta.
18901 - On Windows, we now define the _WIN32_WINNT macros only if they
18902 are not already defined. This lets the person building Tor decide,
18903 if they want, to require a later version of Windows.
18904 - Our autogen.sh script now uses autoreconf to launch autoconf,
18905 automake, and so on. This is more robust against some of the failure
18906 modes associated with running the autotools pieces on their own.
18907 - Running "make version" now displays the version of Tor that
18908 we're about to build. Idea from katmagic; resolves issue 4400.
18909 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
18910 on 0.2.2.4-alpha; fixes bug 3427.
18911 - New --enable-static-tor configure option for building Tor as
18912 statically as possible. Idea, general hackery and thoughts from
18913 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
18915 - Limited, experimental support for building with nmake and MSVC.
18917 o Build requirements:
18918 - Building Tor with bufferevent support now requires Libevent
18919 2.0.13-stable or later. Previous versions of Libevent had bugs in
18920 SSL-related bufferevents and related issues that would make Tor
18921 work badly with bufferevents. Requiring 2.0.13-stable also allows
18922 Tor with bufferevents to take advantage of Libevent APIs
18923 introduced after 2.0.8-rc.
18924 - Our build system requires automake 1.6 or later to create the
18925 Makefile.in files. Previously, you could have used 1.4.
18926 This only affects developers and people building Tor from git;
18927 people who build Tor from the source distribution without changing
18928 the Makefile.am files should be fine.
18929 - Detect when we try to build on a platform that doesn't define
18930 AF_UNSPEC to 0. We don't work there, so refuse to compile.
18932 o Build fixes (compile/link):
18933 - Format more doubles with %f, not %lf. Patch from grarpamp to make
18934 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
18936 - When building with --enable-static-tor on OpenBSD, do not
18937 erroneously attempt to link -lrt. Fixes bug 5103.
18938 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
18939 that IPv6 stuff will compile on MSVC, and compilation issues
18940 will be easier to track down. Fixes bug 5861.
18941 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
18942 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
18943 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
18944 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
18946 o Build fixes (other):
18947 - Use the _WIN32 macro throughout our code to detect Windows.
18948 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
18950 - Properly handle the case where the build-tree is not the same
18951 as the source tree when generating src/common/common_sha1.i,
18952 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
18953 bugfix on 0.2.0.1-alpha.
18954 - During configure, search for library containing cos function as
18955 libm lives in libcore on some platforms (BeOS/Haiku). Linking
18956 against libm was hard-coded before. Fixes the first part of bug
18957 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
18959 - Prevent a false positive from the check-spaces script, by disabling
18960 the "whitespace between function name and (" check for functions
18963 o Packaging (RPM) changes:
18964 - Update our default RPM spec files to work with mock and rpmbuild
18965 on RHEL/Fedora. They have an updated set of dependencies and
18966 conflicts, a fix for an ancient typo when creating the "_tor"
18967 user, and better instructions. Thanks to Ondrej Mikle for the
18968 patch series. Fixes bug 6043.
18969 - On OpenSUSE, create the /var/run/tor directory on startup if it
18970 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
18972 o Code refactoring (safety):
18973 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
18974 10 lines. Also, don't nest them. Doing so in the past has
18975 led to hard-to-debug code. The new style is to use the
18976 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
18977 - Use macros to indicate OpenSSL versions, so we don't need to worry
18978 about accidental hexadecimal bit shifts.
18979 - Use tor_sscanf() in place of scanf() in more places through the
18980 code. This makes us a little more locale-independent, and
18981 should help shut up code-analysis tools that can't tell
18982 a safe sscanf string from a dangerous one.
18983 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
18984 - Use the smartlist_add_asprintf() alias more consistently.
18986 o Code refactoring (consolidate):
18987 - A major revision to our internal node-selecting and listing logic.
18988 Tor already had at least two major ways to look at the question of
18989 "which Tor servers do we know about": a list of router descriptors,
18990 and a list of entries in the current consensus. With
18991 microdescriptors, we're adding a third. Having so many systems
18992 without an abstraction layer over them was hurting the codebase.
18993 Now, we have a new "node_t" abstraction that presents a consistent
18994 interface to a client's view of a Tor node, and holds (nearly) all
18995 of the mutable state formerly in routerinfo_t and routerstatus_t.
18996 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
18997 Libevent's notion of cached time when possible.
18998 - Remove duplicate code for invoking getrlimit() from control.c.
18999 - Use OpenSSL's built-in SSL_state_string_long() instead of our
19000 own homebrewed ssl_state_to_string() replacement. Patch from
19001 Emile Snyder. Fixes bug 4653.
19002 - Change the symmetric cipher interface so that creating and
19003 initializing a stream cipher are no longer separate functions.
19005 o Code refactoring (separate):
19006 - Make a new "entry connection" struct as an internal subtype of "edge
19007 connection", to simplify the code and make exit connections smaller.
19008 - Split connection_about_to_close() into separate functions for each
19010 - Rewrite the listener-selection logic so that parsing which ports
19011 we want to listen on is now separate from binding to the ports
19014 o Code refactoring (name changes):
19015 - Rename a handful of old identifiers, mostly related to crypto
19016 structures and crypto functions. By convention, our "create an
19017 object" functions are called "type_new()", our "free an object"
19018 functions are called "type_free()", and our types indicate that
19019 they are types only with a final "_t". But a handful of older
19020 types and functions broke these rules, with function names like
19021 "type_create" or "subsystem_op_type", or with type names like
19023 - Rename Tor functions that turn strings into addresses, so that
19024 "parse" indicates that no hostname resolution occurs, and
19025 "lookup" indicates that hostname resolution may occur. This
19026 should help prevent mistakes in the future. Fixes bug 3512.
19027 - Use the name "CERTS" consistently to refer to the new cell type;
19028 we were calling it CERT in some places and CERTS in others.
19029 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
19030 invalid value, rather than just -1.
19031 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
19032 can pick them up when the tests aren't disabled. Bugfix on
19033 0.2.2.4-alpha which introduced tinytest.
19035 o Code refactoring (other):
19036 - Defensively refactor rend_mid_rendezvous() so that protocol
19037 violations and length checks happen in the beginning. Fixes
19039 - Remove the pure attribute from all functions that used it
19040 previously. In many cases we assigned it incorrectly, because the
19041 functions might assert or call impure functions, and we don't have
19042 evidence that keeping the pure attribute is worthwhile. Implements
19043 changes suggested in ticket 4421.
19044 - Move the replay-detection cache for the RSA-encrypted parts of
19045 INTRODUCE2 cells to the introduction point data structures.
19046 Previously, we would use one replay-detection cache per hidden
19047 service. Required by fix for bug 3460.
19048 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
19049 no longer link against Libevent: they never used it, but
19050 our library structure used to force them to link it.
19052 o Removed features and files:
19053 - Remove all internal support for unpadded RSA. We never used it, and
19054 it would be a bad idea to start.
19055 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
19057 - Remove some redundant #include directives throughout the code.
19058 Patch from Andrea Gelmini.
19059 - Remove some old code to remember statistics about which descriptors
19060 we've served as a directory mirror. The feature wasn't used and
19061 is outdated now that microdescriptors are around.
19062 - Remove some old code to work around even older versions of Tor that
19063 used forked processes to handle DNS requests. Such versions of Tor
19064 are no longer in use as relays.
19065 - The "torify" script no longer supports the "tsocks" socksifier
19066 tool, since tsocks doesn't support DNS and UDP right for Tor.
19067 Everyone should be using torsocks instead. Fixes bugs 3530 and
19068 5180. Based on a patch by "ugh".
19069 - Remove the torrc.bridge file: we don't use it for anything, and
19070 it had become badly desynchronized from torrc.sample. Resolves
19074 - Begin a doc/state-contents.txt file to explain the contents of
19075 the Tor state file. Fixes bug 2987.
19076 - Clarify the documentation for the Alternate*Authority options.
19078 - Document the --defaults-torrc option, and the new semantics for
19079 overriding, extending, and clearing lists of options. Closes
19081 - Add missing man page documentation for consensus and microdesc
19082 files. Resolves ticket 6732.
19083 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
19085 o Documentation fixes:
19086 - Improve the manual's documentation for the NT Service command-line
19087 options. Addresses ticket 3964.
19088 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
19089 - Document the changes to the ORPort and DirPort options, and the
19090 fact that {OR/Dir}ListenAddress is now unnecessary (and
19091 therefore deprecated). Resolves ticket 5597.
19092 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
19093 - Clarify that hidden services are TCP only. Fixes bug 6024.
19096 Changes in version 0.2.2.39 - 2012-09-11
19097 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
19101 - Fix an assertion failure in tor_timegm() that could be triggered
19102 by a badly formatted directory object. Bug found by fuzzing with
19103 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
19104 - Do not crash when comparing an address with port value 0 to an
19105 address policy. This bug could have been used to cause a remote
19106 assertion failure by or against directory authorities, or to
19107 allow some applications to crash clients. Fixes bug 6690; bugfix
19111 Changes in version 0.2.2.38 - 2012-08-12
19112 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
19113 attack that could in theory leak path information.
19116 - Avoid an uninitialized memory read when reading a vote or consensus
19117 document that has an unrecognized flavor name. This read could
19118 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
19119 - Try to leak less information about what relays a client is
19120 choosing to a side-channel attacker. Previously, a Tor client would
19121 stop iterating through the list of available relays as soon as it
19122 had chosen one, thus finishing a little earlier when it picked
19123 a router earlier in the list. If an attacker can recover this
19124 timing information (nontrivial but not proven to be impossible),
19125 they could learn some coarse-grained information about which relays
19126 a client was picking (middle nodes in particular are likelier to
19127 be affected than exits). The timing attack might be mitigated by
19128 other factors (see bug 6537 for some discussion), but it's best
19129 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
19132 Changes in version 0.2.2.37 - 2012-06-06
19133 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
19134 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
19138 - Work around a bug in OpenSSL that broke renegotiation with TLS
19139 1.1 and TLS 1.2. Without this workaround, all attempts to speak
19140 the v2 Tor connection protocol when both sides were using OpenSSL
19141 1.0.1 would fail. Resolves ticket 6033.
19142 - When waiting for a client to renegotiate, don't allow it to add
19143 any bytes to the input buffer. This fixes a potential DoS issue.
19144 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
19145 - Fix an edge case where if we fetch or publish a hidden service
19146 descriptor, we might build a 4-hop circuit and then use that circuit
19147 for exiting afterwards -- even if the new last hop doesn't obey our
19148 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
19151 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
19152 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
19155 - Tell GCC and Clang to check for any errors in format strings passed
19156 to the tor_v*(print|scan)f functions.
19159 Changes in version 0.2.2.36 - 2012-05-24
19160 Tor 0.2.2.36 updates the addresses for two of the eight directory
19161 authorities, fixes some potential anonymity and security issues,
19162 and fixes several crash bugs.
19164 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
19165 known flaws, and nobody should be using them. You should upgrade. If
19166 you're using a Linux or BSD and its packages are obsolete, stop using
19167 those packages and upgrade anyway.
19169 o Directory authority changes:
19170 - Change IP address for maatuska (v3 directory authority).
19171 - Change IP address for ides (v3 directory authority), and rename
19175 - When building or running with any version of OpenSSL earlier
19176 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
19177 versions have a bug (CVE-2011-4576) in which their block cipher
19178 padding includes uninitialized data, potentially leaking sensitive
19179 information to any peer with whom they make a SSLv3 connection. Tor
19180 does not use SSL v3 by default, but a hostile client or server
19181 could force an SSLv3 connection in order to gain information that
19182 they shouldn't have been able to get. The best solution here is to
19183 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
19184 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
19185 to make sure that the bug can't happen.
19186 - Never use a bridge or a controller-supplied node as an exit, even
19187 if its exit policy allows it. Found by wanoskarnet. Fixes bug
19188 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
19189 and 0.2.0.3-alpha (for bridge-purpose descriptors).
19190 - Only build circuits if we have a sufficient threshold of the total
19191 descriptors that are marked in the consensus with the "Exit"
19192 flag. This mitigates an attack proposed by wanoskarnet, in which
19193 all of a client's bridges collude to restrict the exit nodes that
19194 the client knows about. Fixes bug 5343.
19195 - Provide controllers with a safer way to implement the cookie
19196 authentication mechanism. With the old method, if another locally
19197 running program could convince a controller that it was the Tor
19198 process, then that program could trick the controller into telling
19199 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
19200 authentication method uses a challenge-response approach to prevent
19201 this attack. Fixes bug 5185; implements proposal 193.
19204 - Avoid logging uninitialized data when unable to decode a hidden
19205 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
19206 - Avoid a client-side assertion failure when receiving an INTRODUCE2
19207 cell on a general purpose circuit. Fixes bug 5644; bugfix on
19209 - Fix builds when the path to sed, openssl, or sha1sum contains
19210 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
19212 - Correct our replacements for the timeradd() and timersub() functions
19213 on platforms that lack them (for example, Windows). The timersub()
19214 function is used when expiring circuits, while timeradd() is
19215 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
19216 bugfix on 0.2.2.24-alpha.
19217 - Fix the SOCKET_OK test that we use to tell when socket
19218 creation fails so that it works on Win64. Fixes part of bug 4533;
19219 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
19222 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
19223 Fixes bug 5346; bugfix on 0.0.8pre3.
19224 - Make our number-parsing functions always treat too-large values
19225 as an error, even when those values exceed the width of the
19226 underlying type. Previously, if the caller provided these
19227 functions with minima or maxima set to the extreme values of the
19228 underlying integer type, these functions would return those
19229 values on overflow rather than treating overflow as an error.
19230 Fixes part of bug 5786; bugfix on 0.0.9.
19231 - Older Linux kernels erroneously respond to strange nmap behavior
19232 by having accept() return successfully with a zero-length
19233 socket. When this happens, just close the connection. Previously,
19234 we would try harder to learn the remote address: but there was
19235 no such remote address to learn, and our method for trying to
19236 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
19237 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
19238 - Correct parsing of certain date types in parse_http_time().
19239 Without this patch, If-Modified-Since would behave
19240 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
19241 Esteban Manchado Velázques.
19242 - Change the BridgePassword feature (part of the "bridge community"
19243 design, which is not yet implemented) to use a time-independent
19244 comparison. The old behavior might have allowed an adversary
19245 to use timing to guess the BridgePassword value. Fixes bug 5543;
19246 bugfix on 0.2.0.14-alpha.
19247 - Detect and reject certain misformed escape sequences in
19248 configuration values. Previously, these values would cause us
19249 to crash if received in a torrc file or over an authenticated
19250 control port. Bug found by Esteban Manchado Velázquez, and
19251 independently by Robert Connolly from Matta Consulting who further
19252 noted that it allows a post-authentication heap overflow. Patch
19253 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
19254 bugfix on 0.2.0.16-alpha.
19255 - Fix a compile warning when using the --enable-openbsd-malloc
19256 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
19257 - During configure, detect when we're building with clang version
19258 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
19259 CFLAGS. clang doesn't support them yet.
19260 - When sending an HTTP/1.1 proxy request, include a Host header.
19261 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
19262 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
19263 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
19264 - If we hit the error case where routerlist_insert() replaces an
19265 existing (old) server descriptor, make sure to remove that
19266 server descriptor from the old_routers list. Fix related to bug
19267 1776. Bugfix on 0.2.2.18-alpha.
19269 o Minor bugfixes (documentation and log messages):
19270 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
19271 Fixes bug 4856; bugfix on Tor 0.0.6.
19272 - Update "ClientOnly" man page entry to explain that there isn't
19273 really any point to messing with it. Resolves ticket 5005.
19274 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
19275 directory authority option (introduced in Tor 0.2.2.34).
19276 - Downgrade the "We're missing a certificate" message from notice
19277 to info: people kept mistaking it for a real problem, whereas it
19278 is seldom the problem even when we are failing to bootstrap. Fixes
19279 bug 5067; bugfix on 0.2.0.10-alpha.
19280 - Correctly spell "connect" in a log message on failure to create a
19281 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
19282 - Clarify the behavior of MaxCircuitDirtiness with hidden service
19283 circuits. Fixes issue 5259.
19286 - Directory authorities now reject versions of Tor older than
19287 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
19288 inclusive. These versions accounted for only a small fraction of
19289 the Tor network, and have numerous known security issues. Resolves
19291 - Update to the May 1 2012 Maxmind GeoLite Country database.
19294 - When sending or relaying a RELAY_EARLY cell, we used to convert
19295 it to a RELAY cell if the connection was using the v1 link
19296 protocol. This was a workaround for older versions of Tor, which
19297 didn't handle RELAY_EARLY cells properly. Now that all supported
19298 versions can handle RELAY_EARLY cells, and now that we're enforcing
19299 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
19300 remove this workaround. Addresses bug 4786.
19303 Changes in version 0.2.2.35 - 2011-12-16
19304 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
19305 buffers code. Absolutely everybody should upgrade.
19307 The bug relied on an incorrect calculation when making data continuous
19308 in one of our IO buffers, if the first chunk of the buffer was
19309 misaligned by just the wrong amount. The miscalculation would allow an
19310 attacker to overflow a piece of heap-allocated memory. To mount this
19311 attack, the attacker would need to either open a SOCKS connection to
19312 Tor's SocksPort (usually restricted to localhost), or target a Tor
19313 instance configured to make its connections through a SOCKS proxy
19314 (which Tor does not do by default).
19316 Good security practice requires that all heap-overflow bugs should be
19317 presumed to be exploitable until proven otherwise, so we are treating
19318 this as a potential code execution attack. Please upgrade immediately!
19319 This bug does not affect bufferevents-based builds of Tor. Special
19320 thanks to "Vektor" for reporting this issue to us!
19322 Tor 0.2.2.35 also fixes several bugs in previous versions, including
19323 crash bugs for unusual configurations, and a long-term bug that
19324 would prevent Tor from starting on Windows machines with draconian
19327 With this release, we remind everyone that 0.2.0.x has reached its
19328 formal end-of-life. Those Tor versions have many known flaws, and
19329 nobody should be using them. You should upgrade -- ideally to the
19330 0.2.2.x series. If you're using a Linux or BSD and its packages are
19331 obsolete, stop using those packages and upgrade anyway.
19333 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
19334 longer receive support after some time in early 2012.
19337 - Fix a heap overflow bug that could occur when trying to pull
19338 data into the first chunk of a buffer, when that chunk had
19339 already had some data drained from it. Fixes CVE-2011-2778;
19340 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
19341 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
19342 that it doesn't attempt to allocate a socketpair. This could cause
19343 some problems on Windows systems with overzealous firewalls. Fix for
19344 bug 4457; workaround for Libevent versions 2.0.1-alpha through
19346 - If we mark an OR connection for close based on a cell we process,
19347 don't process any further cells on it. We already avoid further
19348 reads on marked-for-close connections, but now we also discard the
19349 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
19350 which was the first version where we might mark a connection for
19351 close based on processing a cell on it.
19352 - Correctly sanity-check that we don't underflow on a memory
19353 allocation (and then assert) for hidden service introduction
19354 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
19355 bugfix on 0.2.1.5-alpha.
19356 - Fix a memory leak when we check whether a hidden service
19357 descriptor has any usable introduction points left. Fixes bug
19358 4424. Bugfix on 0.2.2.25-alpha.
19359 - Don't crash when we're running as a relay and don't have a GeoIP
19360 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
19361 we've had in the 0.2.3.x branch already.
19362 - When running as a client, do not print a misleading (and plain
19363 wrong) log message that we're collecting "directory request"
19364 statistics: clients don't collect statistics. Also don't create a
19365 useless (because empty) stats file in the stats/ directory. Fixes
19366 bug 4353; bugfix on 0.2.2.34.
19369 - Detect failure to initialize Libevent. This fix provides better
19370 detection for future instances of bug 4457.
19371 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
19372 function. This was eating up hideously large amounts of time on some
19373 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
19374 - Resolve an integer overflow bug in smartlist_ensure_capacity().
19375 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
19377 - Don't warn about unused log_mutex in log.c when building with
19378 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
19379 0.1.0.6-rc which introduced --disable-threads.
19380 - When configuring, starting, or stopping an NT service, stop
19381 immediately after the service configuration attempt has succeeded
19382 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
19383 - When sending a NETINFO cell, include the original address
19384 received for the other side, not its canonical address. Found
19385 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
19386 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
19387 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
19388 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
19389 occurred when a client tried to fetch a descriptor for a bridge
19390 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
19391 - Backport fixes for a pair of compilation warnings on Windows.
19392 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
19393 - If we had ever tried to call tor_addr_to_str on an address of
19394 unknown type, we would have done a strdup on an uninitialized
19395 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
19396 Reported by "troll_un".
19397 - Correctly detect and handle transient lookup failures from
19398 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
19399 Reported by "troll_un".
19400 - Fix null-pointer access that could occur if TLS allocation failed.
19401 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
19402 - Use tor_socket_t type for listener argument to accept(). Fixes bug
19403 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
19406 - Add two new config options for directory authorities:
19407 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
19408 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
19409 that is always sufficient to satisfy the bandwidth requirement for
19410 the Guard flag. Now it will be easier for researchers to simulate
19411 Tor networks with different values. Resolves ticket 4484.
19412 - When Tor ignores a hidden service specified in its configuration,
19413 include the hidden service's directory in the warning message.
19414 Previously, we would only tell the user that some hidden service
19415 was ignored. Bugfix on 0.0.6; fixes bug 4426.
19416 - Update to the December 6 2011 Maxmind GeoLite Country database.
19418 o Packaging changes:
19419 - Make it easier to automate expert package builds on Windows,
19420 by removing an absolute path from makensis.exe command.
19423 Changes in version 0.2.1.32 - 2011-12-16
19424 Tor 0.2.1.32 backports important security and privacy fixes for
19425 oldstable. This release is intended only for package maintainers and
19426 others who cannot use the 0.2.2 stable series. All others should be
19427 using Tor 0.2.2.x or newer.
19429 The Tor 0.2.1.x series will reach formal end-of-life some time in
19430 early 2012; we will stop releasing patches for it then.
19432 o Major bugfixes (also included in 0.2.2.x):
19433 - Correctly sanity-check that we don't underflow on a memory
19434 allocation (and then assert) for hidden service introduction
19435 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
19436 bugfix on 0.2.1.5-alpha.
19437 - Fix a heap overflow bug that could occur when trying to pull
19438 data into the first chunk of a buffer, when that chunk had
19439 already had some data drained from it. Fixes CVE-2011-2778;
19440 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
19443 - Update to the December 6 2011 Maxmind GeoLite Country database.
19446 Changes in version 0.2.2.34 - 2011-10-26
19447 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
19448 can deanonymize Tor users. Everybody should upgrade.
19450 The attack relies on four components: 1) Clients reuse their TLS cert
19451 when talking to different relays, so relays can recognize a user by
19452 the identity key in her cert. 2) An attacker who knows the client's
19453 identity key can probe each guard relay to see if that identity key
19454 is connected to that guard relay right now. 3) A variety of active
19455 attacks in the literature (starting from "Low-Cost Traffic Analysis
19456 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
19457 discover the guard relays that a Tor user visiting the website is using.
19458 4) Clients typically pick three guards at random, so the set of guards
19459 for a given user could well be a unique fingerprint for her. This
19460 release fixes components #1 and #2, which is enough to block the attack;
19461 the other two remain as open research problems. Special thanks to
19462 "frosty_un" for reporting the issue to us!
19464 Clients should upgrade so they are no longer recognizable by the TLS
19465 certs they present. Relays should upgrade so they no longer allow a
19466 remote attacker to probe them to test whether unpatched clients are
19467 currently connected to them.
19469 This release also fixes several vulnerabilities that allow an attacker
19470 to enumerate bridge relays. Some bridge enumeration attacks still
19471 remain; see for example proposal 188.
19473 o Privacy/anonymity fixes (clients):
19474 - Clients and bridges no longer send TLS certificate chains on
19475 outgoing OR connections. Previously, each client or bridge would
19476 use the same cert chain for all outgoing OR connections until
19477 its IP address changes, which allowed any relay that the client
19478 or bridge contacted to determine which entry guards it is using.
19479 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
19480 - If a relay receives a CREATE_FAST cell on a TLS connection, it
19481 no longer considers that connection as suitable for satisfying a
19482 circuit EXTEND request. Now relays can protect clients from the
19483 CVE-2011-2768 issue even if the clients haven't upgraded yet.
19484 - Directory authorities no longer assign the Guard flag to relays
19485 that haven't upgraded to the above "refuse EXTEND requests
19486 to client connections" fix. Now directory authorities can
19487 protect clients from the CVE-2011-2768 issue even if neither
19488 the clients nor the relays have upgraded yet. There's a new
19489 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
19490 to let us transition smoothly, else tomorrow there would be no
19493 o Privacy/anonymity fixes (bridge enumeration):
19494 - Bridge relays now do their directory fetches inside Tor TLS
19495 connections, like all the other clients do, rather than connecting
19496 directly to the DirPort like public relays do. Removes another
19497 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
19498 - Bridges relays now build circuits for themselves in a more similar
19499 way to how clients build them. Removes another avenue for
19500 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
19501 when bridges were introduced.
19502 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
19503 that they initiated. Relays could distinguish incoming bridge
19504 connections from client connections, creating another avenue for
19505 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
19506 Found by "frosty_un".
19509 - Fix a crash bug when changing node restrictions while a DNS lookup
19510 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
19512 - Don't launch a useless circuit after failing to use one of a
19513 hidden service's introduction points. Previously, we would
19514 launch a new introduction circuit, but not set the hidden service
19515 which that circuit was intended to connect to, so it would never
19516 actually be used. A different piece of code would then create a
19517 new introduction circuit correctly. Bug reported by katmagic and
19518 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
19521 - Change an integer overflow check in the OpenBSD_Malloc code so
19522 that GCC is less likely to eliminate it as impossible. Patch
19523 from Mansour Moufid. Fixes bug 4059.
19524 - When a hidden service turns an extra service-side introduction
19525 circuit into a general-purpose circuit, free the rend_data and
19526 intro_key fields first, so we won't leak memory if the circuit
19527 is cannibalized for use as another service-side introduction
19528 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
19529 - Bridges now skip DNS self-tests, to act a little more stealthily.
19530 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
19531 bridges. Patch by "warms0x".
19532 - Fix internal bug-checking logic that was supposed to catch
19533 failures in digest generation so that it will fail more robustly
19534 if we ask for a nonexistent algorithm. Found by Coverity Scan.
19535 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
19536 - Report any failure in init_keys() calls launched because our
19537 IP address has changed. Spotted by Coverity Scan. Bugfix on
19538 0.1.1.4-alpha; fixes CID 484.
19540 o Minor bugfixes (log messages and documentation):
19541 - Remove a confusing dollar sign from the example fingerprint in the
19542 man page, and also make the example fingerprint a valid one. Fixes
19543 bug 4309; bugfix on 0.2.1.3-alpha.
19544 - The next version of Windows will be called Windows 8, and it has
19545 a major version of 6, minor version of 2. Correctly identify that
19546 version instead of calling it "Very recent version". Resolves
19547 ticket 4153; reported by funkstar.
19548 - Downgrade log messages about circuit timeout calibration from
19549 "notice" to "info": they don't require or suggest any human
19550 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
19551 bugfix on 0.2.2.14-alpha.
19554 - Turn on directory request statistics by default and include them in
19555 extra-info descriptors. Don't break if we have no GeoIP database.
19556 Backported from 0.2.3.1-alpha; implements ticket 3951.
19557 - Update to the October 4 2011 Maxmind GeoLite Country database.
19560 Changes in version 0.2.1.31 - 2011-10-26
19561 Tor 0.2.1.31 backports important security and privacy fixes for
19562 oldstable. This release is intended only for package maintainers and
19563 others who cannot use the 0.2.2 stable series. All others should be
19564 using Tor 0.2.2.x or newer.
19566 o Security fixes (also included in 0.2.2.x):
19567 - Replace all potentially sensitive memory comparison operations
19568 with versions whose runtime does not depend on the data being
19569 compared. This will help resist a class of attacks where an
19570 adversary can use variations in timing information to learn
19571 sensitive data. Fix for one case of bug 3122. (Safe memcmp
19572 implementation by Robert Ransom based partially on code by DJB.)
19573 - Fix an assert in parsing router descriptors containing IPv6
19574 addresses. This one took down the directory authorities when
19575 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
19577 o Privacy/anonymity fixes (also included in 0.2.2.x):
19578 - Clients and bridges no longer send TLS certificate chains on
19579 outgoing OR connections. Previously, each client or bridge would
19580 use the same cert chain for all outgoing OR connections until
19581 its IP address changes, which allowed any relay that the client
19582 or bridge contacted to determine which entry guards it is using.
19583 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
19584 - If a relay receives a CREATE_FAST cell on a TLS connection, it
19585 no longer considers that connection as suitable for satisfying a
19586 circuit EXTEND request. Now relays can protect clients from the
19587 CVE-2011-2768 issue even if the clients haven't upgraded yet.
19588 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
19589 that they initiated. Relays could distinguish incoming bridge
19590 connections from client connections, creating another avenue for
19591 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
19592 Found by "frosty_un".
19593 - When receiving a hidden service descriptor, check that it is for
19594 the hidden service we wanted. Previously, Tor would store any
19595 hidden service descriptors that a directory gave it, whether it
19596 wanted them or not. This wouldn't have let an attacker impersonate
19597 a hidden service, but it did let directories pre-seed a client
19598 with descriptors that it didn't want. Bugfix on 0.0.6.
19599 - Avoid linkability based on cached hidden service descriptors: forget
19600 all hidden service descriptors cached as a client when processing a
19601 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
19602 - Make the bridge directory authority refuse to answer directory
19603 requests for "all" descriptors. It used to include bridge
19604 descriptors in its answer, which was a major information leak.
19605 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
19606 - Don't attach new streams to old rendezvous circuits after SIGNAL
19607 NEWNYM. Previously, we would keep using an existing rendezvous
19608 circuit if it remained open (i.e. if it were kept open by a
19609 long-lived stream, or if a new stream were attached to it before
19610 Tor could notice that it was old and no longer in use). Bugfix on
19611 0.1.1.15-rc; fixes bug 3375.
19613 o Minor bugfixes (also included in 0.2.2.x):
19614 - When we restart our relay, we might get a successful connection
19615 from the outside before we've started our reachability tests,
19616 triggering a warning: "ORPort found reachable, but I have no
19617 routerinfo yet. Failing to inform controller of success." This
19618 bug was harmless unless Tor is running under a controller
19619 like Vidalia, in which case the controller would never get a
19620 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
19622 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
19623 enabled. Fixes bug 1526.
19624 - Remove undocumented option "-F" from tor-resolve: it hasn't done
19625 anything since 0.2.1.16-rc.
19626 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
19627 None of the cases where we did this before were wrong, but by making
19628 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
19629 - Fix a rare crash bug that could occur when a client was configured
19630 with a large number of bridges. Fixes bug 2629; bugfix on
19631 0.2.1.2-alpha. Bugfix by trac user "shitlei".
19632 - Correct the warning displayed when a rendezvous descriptor exceeds
19633 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
19635 - Fix an uncommon assertion failure when running with DNSPort under
19636 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
19637 - When warning about missing zlib development packages during compile,
19638 give the correct package names. Bugfix on 0.2.0.1-alpha.
19639 - Require that introduction point keys and onion keys have public
19640 exponent 65537. Bugfix on 0.2.0.10-alpha.
19641 - Do not crash when our configuration file becomes unreadable, for
19642 example due to a permissions change, between when we start up
19643 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
19645 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
19647 - Always NUL-terminate the sun_path field of a sockaddr_un before
19648 passing it to the kernel. (Not a security issue: kernels are
19649 smart enough to reject bad sockaddr_uns.) Found by Coverity;
19650 CID #428. Bugfix on Tor 0.2.0.3-alpha.
19651 - Don't stack-allocate the list of supplementary GIDs when we're
19652 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
19653 could take up to 256K, which is way too much stack. Found by
19654 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
19656 o Minor bugfixes (only in 0.2.1.x):
19657 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
19658 rely on them. Bugfix on 0.2.1.30.
19659 - Use git revisions instead of svn revisions when generating our
19660 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
19662 o Minor features (also included in 0.2.2.x):
19663 - Adjust the expiration time on our SSL session certificates to
19664 better match SSL certs seen in the wild. Resolves ticket 4014.
19665 - Allow nameservers with IPv6 address. Resolves bug 2574.
19666 - Update to the October 4 2011 Maxmind GeoLite Country database.
19669 Changes in version 0.2.2.33 - 2011-09-13
19670 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
19671 TLS handshake that makes relays and bridges that run this new version
19672 reachable from Iran again.
19675 - Avoid an assertion failure when reloading a configuration with
19676 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
19677 3923; bugfix on 0.2.2.25-alpha.
19679 o Minor features (security):
19680 - Check for replays of the public-key encrypted portion of an
19681 INTRODUCE1 cell, in addition to the current check for replays of
19682 the g^x value. This prevents a possible class of active attacks
19683 by an attacker who controls both an introduction point and a
19684 rendezvous point, and who uses the malleability of AES-CTR to
19685 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
19686 that these attacks are infeasible (requiring the attacker to send
19687 on the order of zettabytes of altered cells in a short interval),
19688 but we'd rather block them off in case there are any classes of
19689 this attack that we missed. Reported by Willem Pinckaers.
19692 - Adjust the expiration time on our SSL session certificates to
19693 better match SSL certs seen in the wild. Resolves ticket 4014.
19694 - Change the default required uptime for a relay to be accepted as
19695 a HSDir (hidden service directory) from 24 hours to 25 hours.
19696 Improves on 0.2.0.10-alpha; resolves ticket 2649.
19697 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
19698 authorities to abstain from voting on assignment of the HSDir
19699 consensus flag. Related to bug 2649.
19700 - Update to the September 6 2011 Maxmind GeoLite Country database.
19702 o Minor bugfixes (documentation and log messages):
19703 - Correct the man page to explain that HashedControlPassword and
19704 CookieAuthentication can both be set, in which case either method
19705 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
19706 when we decided to allow these config options to both be set. Issue
19707 raised by bug 3898.
19708 - Demote the 'replay detected' log message emitted when a hidden
19709 service receives the same Diffie-Hellman public key in two different
19710 INTRODUCE2 cells to info level. A normal Tor client can cause that
19711 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
19712 fixes part of bug 2442.
19713 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
19714 level. There is nothing that a hidden service's operator can do
19715 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
19717 - Clarify a log message specifying the characters permitted in
19718 HiddenServiceAuthorizeClient client names. Previously, the log
19719 message said that "[A-Za-z0-9+-_]" were permitted; that could have
19720 given the impression that every ASCII character between "+" and "_"
19721 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
19724 - Provide a substitute implementation of lround() for MSVC, which
19725 apparently lacks it. Patch from Gisle Vanem.
19726 - Clean up some code issues that prevented Tor from building on older
19727 BSDs. Fixes bug 3894; reported by "grarpamp".
19728 - Search for a platform-specific version of "ar" when cross-compiling.
19729 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
19732 Changes in version 0.2.2.32 - 2011-08-27
19733 The Tor 0.2.2 release series is dedicated to the memory of Andreas
19734 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
19735 a founder of the PETS community, a leader in our field, a mentor,
19736 and a friend. He left us with these words: "I had the possibility
19737 to contribute to this world that is not as it should be. I hope I
19738 could help in some areas to make the world a better place, and that
19739 I could also encourage other people to be engaged in improving the
19740 world. Please, stay engaged. This world needs you, your love, your
19741 initiative -- now I cannot be part of that anymore."
19743 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
19744 ready. More than two years in the making, this release features improved
19745 client performance and hidden service reliability, better compatibility
19746 for Android, correct behavior for bridges that listen on more than
19747 one address, more extensible and flexible directory object handling,
19748 better reporting of network statistics, improved code security, and
19749 many many other features and bugfixes.
19751 o Major features (client performance):
19752 - When choosing which cells to relay first, relays now favor circuits
19753 that have been quiet recently, to provide lower latency for
19754 low-volume circuits. By default, relays enable or disable this
19755 feature based on a setting in the consensus. They can override
19756 this default by using the new "CircuitPriorityHalflife" config
19757 option. Design and code by Ian Goldberg, Can Tang, and Chris
19759 - Directory authorities now compute consensus weightings that instruct
19760 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
19761 and no flag. Clients use these weightings to distribute network load
19762 more evenly across these different relay types. The weightings are
19763 in the consensus so we can change them globally in the future. Extra
19764 thanks to "outofwords" for finding some nasty security bugs in
19765 the first implementation of this feature.
19767 o Major features (client performance, circuit build timeout):
19768 - Tor now tracks how long it takes to build client-side circuits
19769 over time, and adapts its timeout to local network performance.
19770 Since a circuit that takes a long time to build will also provide
19771 bad performance, we get significant latency improvements by
19772 discarding the slowest 20% of circuits. Specifically, Tor creates
19773 circuits more aggressively than usual until it has enough data
19774 points for a good timeout estimate. Implements proposal 151.
19775 - Circuit build timeout constants can be controlled by consensus
19776 parameters. We set good defaults for these parameters based on
19777 experimentation on broadband and simulated high-latency links.
19778 - Circuit build time learning can be disabled via consensus parameter
19779 or by the client via a LearnCircuitBuildTimeout config option. We
19780 also automatically disable circuit build time calculation if either
19781 AuthoritativeDirectory is set, or if we fail to write our state
19782 file. Implements ticket 1296.
19784 o Major features (relays use their capacity better):
19785 - Set SO_REUSEADDR socket option on all sockets, not just
19786 listeners. This should help busy exit nodes avoid running out of
19787 useable ports just because all the ports have been used in the
19788 near past. Resolves issue 2850.
19789 - Relays now save observed peak bandwidth throughput rates to their
19790 state file (along with total usage, which was already saved),
19791 so that they can determine their correct estimated bandwidth on
19792 restart. Resolves bug 1863, where Tor relays would reset their
19793 estimated bandwidth to 0 after restarting.
19794 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
19795 should give us approximately 40-50% more Guard-flagged nodes,
19796 improving the anonymity the Tor network can provide and also
19797 decreasing the dropoff in throughput that relays experience when
19798 they first get the Guard flag.
19799 - Directory authorities now take changes in router IP address and
19800 ORPort into account when determining router stability. Previously,
19801 if a router changed its IP or ORPort, the authorities would not
19802 treat it as having any downtime for the purposes of stability
19803 calculation, whereas clients would experience downtime since the
19804 change would take a while to propagate to them. Resolves issue 1035.
19805 - New AccelName and AccelDir options add support for dynamic OpenSSL
19806 hardware crypto acceleration engines.
19808 o Major features (relays control their load better):
19809 - Exit relays now try harder to block exit attempts from unknown
19810 relays, to make it harder for people to use them as one-hop proxies
19811 a la tortunnel. Controlled by the refuseunknownexits consensus
19812 parameter (currently enabled), or you can override it on your
19813 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
19814 based on a variant of proposal 163.
19815 - Add separate per-conn write limiting to go with the per-conn read
19816 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
19817 but never per-conn write limits.
19818 - New consensus params "bwconnrate" and "bwconnburst" to let us
19819 rate-limit client connections as they enter the network. It's
19820 controlled in the consensus so we can turn it on and off for
19821 experiments. It's starting out off. Based on proposal 163.
19823 o Major features (controllers):
19824 - Export GeoIP information on bridge usage to controllers even if we
19825 have not yet been running for 24 hours. Now Vidalia bridge operators
19826 can get more accurate and immediate feedback about their
19827 contributions to the network.
19828 - Add an __OwningControllerProcess configuration option and a
19829 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
19830 that when it exits, Tor will shut down. Implements feature 3049.
19832 o Major features (directory authorities):
19833 - Directory authorities now create, vote on, and serve multiple
19834 parallel formats of directory data as part of their voting process.
19835 Partially implements Proposal 162: "Publish the consensus in
19837 - Directory authorities now agree on and publish small summaries
19838 of router information that clients can use in place of regular
19839 server descriptors. This transition will allow Tor 0.2.3 clients
19840 to use far less bandwidth for downloading information about the
19841 network. Begins the implementation of Proposal 158: "Clients
19842 download consensus + microdescriptors".
19843 - The directory voting system is now extensible to use multiple hash
19844 algorithms for signatures and resource selection. Newer formats
19845 are signed with SHA256, with a possibility for moving to a better
19846 hash algorithm in the future.
19847 - Directory authorities can now vote on arbitrary integer values as
19848 part of the consensus process. This is designed to help set
19849 network-wide parameters. Implements proposal 167.
19851 o Major features and bugfixes (node selection):
19852 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
19853 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
19854 options. Previously, we had been ambiguous in describing what
19855 counted as an "exit" node, and what operations exactly "StrictNodes
19856 0" would permit. This created confusion when people saw nodes built
19857 through unexpected circuits, and made it hard to tell real bugs from
19858 surprises. Now the intended behavior is:
19859 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
19860 a node that delivers user traffic outside the Tor network.
19861 . "Entry", in the context of EntryNodes, means a node used as the
19862 first hop of a multihop circuit. It doesn't include direct
19863 connections to directory servers.
19864 . "ExcludeNodes" applies to all nodes.
19865 . "StrictNodes" changes the behavior of ExcludeNodes only. When
19866 StrictNodes is set, Tor should avoid all nodes listed in
19867 ExcludeNodes, even when it will make user requests fail. When
19868 StrictNodes is *not* set, then Tor should follow ExcludeNodes
19869 whenever it can, except when it must use an excluded node to
19870 perform self-tests, connect to a hidden service, provide a
19871 hidden service, fulfill a .exit request, upload directory
19872 information, or fetch directory information.
19873 Collectively, the changes to implement the behavior fix bug 1090.
19874 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
19875 change during a config reload, mark and discard all our origin
19876 circuits. This fix should address edge cases where we change the
19877 config options and but then choose a circuit that we created before
19879 - Make EntryNodes config option much more aggressive even when
19880 StrictNodes is not set. Before it would prepend your requested
19881 entrynodes to your list of guard nodes, but feel free to use others
19882 after that. Now it chooses only from your EntryNodes if any of
19883 those are available, and only falls back to others if a) they're
19884 all down and b) StrictNodes is not set.
19885 - Now we refresh your entry guards from EntryNodes at each consensus
19886 fetch -- rather than just at startup and then they slowly rot as
19887 the network changes.
19888 - Add support for the country code "{??}" in torrc options like
19889 ExcludeNodes, to indicate all routers of unknown country. Closes
19891 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
19892 a node is listed in both, it's treated as excluded.
19893 - ExcludeNodes now applies to directory nodes -- as a preference if
19894 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
19895 Don't exclude all the directory authorities and set StrictNodes to 1
19896 unless you really want your Tor to break.
19897 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
19898 - ExcludeExitNodes now overrides .exit requests.
19899 - We don't use bridges listed in ExcludeNodes.
19900 - When StrictNodes is 1:
19901 . We now apply ExcludeNodes to hidden service introduction points
19902 and to rendezvous points selected by hidden service users. This
19903 can make your hidden service less reliable: use it with caution!
19904 . If we have used ExcludeNodes on ourself, do not try relay
19905 reachability self-tests.
19906 . If we have excluded all the directory authorities, we will not
19907 even try to upload our descriptor if we're a relay.
19908 . Do not honor .exit requests to an excluded node.
19909 - When the set of permitted nodes changes, we now remove any mappings
19910 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
19912 - We never cannibalize a circuit that had excluded nodes on it, even
19913 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
19914 - Improve log messages related to excluded nodes.
19916 o Major features (misc):
19917 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
19918 to help Tor build correctly for Android phones.
19919 - The options SocksPort, ControlPort, and so on now all accept a
19920 value "auto" that opens a socket on an OS-selected port. A
19921 new ControlPortWriteToFile option tells Tor to write its
19922 actual control port or ports to a chosen file. If the option
19923 ControlPortFileGroupReadable is set, the file is created as
19924 group-readable. Now users can run two Tor clients on the same
19925 system without needing to manually mess with parameters. Resolves
19926 part of ticket 3076.
19927 - Tor now supports tunneling all of its outgoing connections over
19928 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
19929 configuration options. Code by Christopher Davis.
19931 o Code security improvements:
19932 - Replace all potentially sensitive memory comparison operations
19933 with versions whose runtime does not depend on the data being
19934 compared. This will help resist a class of attacks where an
19935 adversary can use variations in timing information to learn
19936 sensitive data. Fix for one case of bug 3122. (Safe memcmp
19937 implementation by Robert Ransom based partially on code by DJB.)
19938 - Enable Address Space Layout Randomization (ASLR) and Data Execution
19939 Prevention (DEP) by default on Windows to make it harder for
19940 attackers to exploit vulnerabilities. Patch from John Brooks.
19941 - New "--enable-gcc-hardening" ./configure flag (off by default)
19942 to turn on gcc compile time hardening options. It ensures
19943 that signed ints have defined behavior (-fwrapv), enables
19944 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
19945 with canaries (-fstack-protector-all), turns on ASLR protection if
19946 supported by the kernel (-fPIE, -pie), and adds additional security
19947 related warnings. Verified to work on Mac OS X and Debian Lenny.
19948 - New "--enable-linker-hardening" ./configure flag (off by default)
19949 to turn on ELF specific hardening features (relro, now). This does
19950 not work with Mac OS X or any other non-ELF binary format.
19951 - Always search the Windows system directory for system DLLs, and
19952 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
19953 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
19954 current and future memory pages via mlockall(). On supported
19955 platforms (modern Linux and probably BSD but not Windows or OS X),
19956 this should effectively disable any and all attempts to page out
19957 memory. This option requires that you start your Tor as root --
19958 if you use DisableAllSwap, please consider using the User option
19959 to properly reduce the privileges of your Tor.
19961 o Major bugfixes (crashes):
19962 - Fix crash bug on platforms where gmtime and localtime can return
19963 NULL. Windows 7 users were running into this one. Fixes part of bug
19964 2077. Bugfix on all versions of Tor. Found by boboper.
19965 - Introduce minimum/maximum values that clients will believe
19966 from the consensus. Now we'll have a better chance to avoid crashes
19967 or worse when a consensus param has a weird value.
19968 - Fix a rare crash bug that could occur when a client was configured
19969 with a large number of bridges. Fixes bug 2629; bugfix on
19970 0.2.1.2-alpha. Bugfix by trac user "shitlei".
19971 - Do not crash when our configuration file becomes unreadable, for
19972 example due to a permissions change, between when we start up
19973 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
19975 - If we're in the pathological case where there's no exit bandwidth
19976 but there is non-exit bandwidth, or no guard bandwidth but there
19977 is non-guard bandwidth, don't crash during path selection. Bugfix
19979 - Fix a crash bug when trying to initialize the evdns module in
19980 Libevent 2. Bugfix on 0.2.1.16-rc.
19982 o Major bugfixes (stability):
19983 - Fix an assert in parsing router descriptors containing IPv6
19984 addresses. This one took down the directory authorities when
19985 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
19986 - Fix an uncommon assertion failure when running with DNSPort under
19987 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
19988 - Treat an unset $HOME like an empty $HOME rather than triggering an
19989 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
19990 - More gracefully handle corrupt state files, removing asserts
19991 in favor of saving a backup and resetting state.
19992 - Instead of giving an assertion failure on an internal mismatch
19993 on estimated freelist size, just log a BUG warning and try later.
19994 Mitigates but does not fix bug 1125.
19995 - Fix an assert that got triggered when using the TestingTorNetwork
19996 configuration option and then issuing a GETINFO config-text control
19997 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
19998 - If the cached cert file is unparseable, warn but don't exit.
20000 o Privacy fixes (relays/bridges):
20001 - Don't list Windows capabilities in relay descriptors. We never made
20002 use of them, and maybe it's a bad idea to publish them. Bugfix
20004 - If the Nickname configuration option isn't given, Tor would pick a
20005 nickname based on the local hostname as the nickname for a relay.
20006 Because nicknames are not very important in today's Tor and the
20007 "Unnamed" nickname has been implemented, this is now problematic
20008 behavior: It leaks information about the hostname without being
20009 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
20010 introduced the Unnamed nickname. Reported by tagnaq.
20011 - Maintain separate TLS contexts and certificates for incoming and
20012 outgoing connections in bridge relays. Previously we would use the
20013 same TLS contexts and certs for incoming and outgoing connections.
20014 Bugfix on 0.2.0.3-alpha; addresses bug 988.
20015 - Maintain separate identity keys for incoming and outgoing TLS
20016 contexts in bridge relays. Previously we would use the same
20017 identity keys for incoming and outgoing TLS contexts. Bugfix on
20018 0.2.0.3-alpha; addresses the other half of bug 988.
20019 - Make the bridge directory authority refuse to answer directory
20020 requests for "all descriptors". It used to include bridge
20021 descriptors in its answer, which was a major information leak.
20022 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
20024 o Privacy fixes (clients):
20025 - When receiving a hidden service descriptor, check that it is for
20026 the hidden service we wanted. Previously, Tor would store any
20027 hidden service descriptors that a directory gave it, whether it
20028 wanted them or not. This wouldn't have let an attacker impersonate
20029 a hidden service, but it did let directories pre-seed a client
20030 with descriptors that it didn't want. Bugfix on 0.0.6.
20031 - Start the process of disabling ".exit" address notation, since it
20032 can be used for a variety of esoteric application-level attacks
20033 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
20035 - Reject attempts at the client side to open connections to private
20036 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
20037 a randomly chosen exit node. Attempts to do so are always
20038 ill-defined, generally prevented by exit policies, and usually
20039 in error. This will also help to detect loops in transparent
20040 proxy configurations. You can disable this feature by setting
20041 "ClientRejectInternalAddresses 0" in your torrc.
20042 - Log a notice when we get a new control connection. Now it's easier
20043 for security-conscious users to recognize when a local application
20044 is knocking on their controller door. Suggested by bug 1196.
20046 o Privacy fixes (newnym):
20047 - Avoid linkability based on cached hidden service descriptors: forget
20048 all hidden service descriptors cached as a client when processing a
20049 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
20050 - On SIGHUP, do not clear out all TrackHostExits mappings, client
20051 DNS cache entries, and virtual address mappings: that's what
20052 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
20053 - Don't attach new streams to old rendezvous circuits after SIGNAL
20054 NEWNYM. Previously, we would keep using an existing rendezvous
20055 circuit if it remained open (i.e. if it were kept open by a
20056 long-lived stream, or if a new stream were attached to it before
20057 Tor could notice that it was old and no longer in use). Bugfix on
20058 0.1.1.15-rc; fixes bug 3375.
20060 o Major bugfixes (relay bandwidth accounting):
20061 - Fix a bug that could break accounting on 64-bit systems with large
20062 time_t values, making them hibernate for impossibly long intervals.
20063 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
20064 - Fix a bug in bandwidth accounting that could make us use twice
20065 the intended bandwidth when our interval start changes due to
20066 daylight saving time. Now we tolerate skew in stored vs computed
20067 interval starts: if the start of the period changes by no more than
20068 50% of the period's duration, we remember bytes that we transferred
20069 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
20071 o Major bugfixes (bridges):
20072 - Bridges now use "reject *:*" as their default exit policy. Bugfix
20073 on 0.2.0.3-alpha. Fixes bug 1113.
20074 - If you configure your bridge with a known identity fingerprint,
20075 and the bridge authority is unreachable (as it is in at least
20076 one country now), fall back to directly requesting the descriptor
20077 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
20079 - Fix a bug where bridge users who configure the non-canonical
20080 address of a bridge automatically switch to its canonical
20081 address. If a bridge listens at more than one address, it
20082 should be able to advertise those addresses independently and
20083 any non-blocked addresses should continue to work. Bugfix on Tor
20084 0.2.0.3-alpha. Fixes bug 2510.
20085 - If you configure Tor to use bridge A, and then quit and
20086 configure Tor to use bridge B instead (or if you change Tor
20087 to use bridge B via the controller), it would happily continue
20088 to use bridge A if it's still reachable. While this behavior is
20089 a feature if your goal is connectivity, in some scenarios it's a
20090 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
20091 - When the controller configures a new bridge, don't wait 10 to 60
20092 seconds before trying to fetch its descriptor. Bugfix on
20093 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
20095 o Major bugfixes (directory authorities):
20096 - Many relays have been falling out of the consensus lately because
20097 not enough authorities know about their descriptor for them to get
20098 a majority of votes. When we deprecated the v2 directory protocol,
20099 we got rid of the only way that v3 authorities can hear from each
20100 other about other descriptors. Now authorities examine every v3
20101 vote for new descriptors, and fetch them from that authority. Bugfix
20103 - Authorities could be tricked into giving out the Exit flag to relays
20104 that didn't allow exiting to any ports. This bug could screw
20105 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
20106 1238. Bug discovered by Martin Kowalczyk.
20107 - If all authorities restart at once right before a consensus vote,
20108 nobody will vote about "Running", and clients will get a consensus
20109 with no usable relays. Instead, authorities refuse to build a
20110 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
20112 o Major bugfixes (stream-level fairness):
20113 - When receiving a circuit-level SENDME for a blocked circuit, try
20114 to package cells fairly from all the streams that had previously
20115 been blocked on that circuit. Previously, we had started with the
20116 oldest stream, and allowed each stream to potentially exhaust
20117 the circuit's package window. This gave older streams on any
20118 given circuit priority over newer ones. Fixes bug 1937. Detected
20119 originally by Camilo Viecco. This bug was introduced before the
20120 first Tor release, in svn commit r152: it is the new winner of
20121 the longest-lived bug prize.
20122 - Fix a stream fairness bug that would cause newer streams on a given
20123 circuit to get preference when reading bytes from the origin or
20124 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
20125 introduced before the first Tor release, in svn revision r152.
20126 - When the exit relay got a circuit-level sendme cell, it started
20127 reading on the exit streams, even if had 500 cells queued in the
20128 circuit queue already, so the circuit queue just grew and grew in
20129 some cases. We fix this by not re-enabling reading on receipt of a
20130 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
20131 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
20133 - Newly created streams were allowed to read cells onto circuits,
20134 even if the circuit's cell queue was blocked and waiting to drain.
20135 This created potential unfairness, as older streams would be
20136 blocked, but newer streams would gladly fill the queue completely.
20137 We add code to detect this situation and prevent any stream from
20138 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
20141 o Major bugfixes (hidden services):
20142 - Apply circuit timeouts to opened hidden-service-related circuits
20143 based on the correct start time. Previously, we would apply the
20144 circuit build timeout based on time since the circuit's creation;
20145 it was supposed to be applied based on time since the circuit
20146 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
20147 - Improve hidden service robustness: When we find that we have
20148 extended a hidden service's introduction circuit to a relay not
20149 listed as an introduction point in the HS descriptor we currently
20150 have, retry with an introduction point from the current
20151 descriptor. Previously we would just give up. Fixes bugs 1024 and
20152 1930; bugfix on 0.2.0.10-alpha.
20153 - Directory authorities now use data collected from their own
20154 uptime observations when choosing whether to assign the HSDir flag
20155 to relays, instead of trusting the uptime value the relay reports in
20156 its descriptor. This change helps prevent an attack where a small
20157 set of nodes with frequently-changing identity keys can blackhole
20158 a hidden service. (Only authorities need upgrade; others will be
20159 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
20160 - Stop assigning the HSDir flag to relays that disable their
20161 DirPort (and thus will refuse to answer directory requests). This
20162 fix should dramatically improve the reachability of hidden services:
20163 hidden services and hidden service clients pick six HSDir relays
20164 to store and retrieve the hidden service descriptor, and currently
20165 about half of the HSDir relays will refuse to work. Bugfix on
20166 0.2.0.10-alpha; fixes part of bug 1693.
20168 o Major bugfixes (misc):
20169 - Clients now stop trying to use an exit node associated with a given
20170 destination by TrackHostExits if they fail to reach that exit node.
20171 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
20172 - Fix a regression that caused Tor to rebind its ports if it receives
20173 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
20174 - Remove an extra pair of quotation marks around the error
20175 message in control-port STATUS_GENERAL BUG events. Bugfix on
20176 0.1.2.6-alpha; fixes bug 3732.
20178 o Minor features (relays):
20179 - Ensure that no empty [dirreq-](read|write)-history lines are added
20180 to an extrainfo document. Implements ticket 2497.
20181 - When bandwidth accounting is enabled, be more generous with how
20182 much bandwidth we'll use up before entering "soft hibernation".
20183 Previously, we'd refuse new connections and circuits once we'd
20184 used up 95% of our allotment. Now, we use up 95% of our allotment,
20185 AND make sure that we have no more than 500MB (or 3 hours of
20186 expected traffic, whichever is lower) remaining before we enter
20188 - Relays now log the reason for publishing a new relay descriptor,
20189 so we have a better chance of hunting down instances of bug 1810.
20190 Resolves ticket 3252.
20191 - Log a little more clearly about the times at which we're no longer
20192 accepting new connections (e.g. due to hibernating). Resolves
20194 - When AllowSingleHopExits is set, print a warning to explain to the
20195 relay operator why most clients are avoiding her relay.
20196 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
20197 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
20198 clients are already deprecated because of security bugs.
20200 o Minor features (network statistics):
20201 - Directory mirrors that set "DirReqStatistics 1" write statistics
20202 about directory requests to disk every 24 hours. As compared to the
20203 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
20204 improvements: 1) stats are written to disk exactly every 24 hours;
20205 2) estimated shares of v2 and v3 requests are determined as mean
20206 values, not at the end of a measurement period; 3) unresolved
20207 requests are listed with country code '??'; 4) directories also
20208 measure download times.
20209 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
20210 number of exit streams and transferred bytes per port to disk every
20212 - Relays that set "CellStatistics 1" write statistics on how long
20213 cells spend in their circuit queues to disk every 24 hours.
20214 - Entry nodes that set "EntryStatistics 1" write statistics on the
20215 rough number and origins of connecting clients to disk every 24
20217 - Relays that write any of the above statistics to disk and set
20218 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
20219 their extra-info documents. Implements proposal 166.
20221 o Minor features (GeoIP and statistics):
20222 - Provide a log message stating which geoip file we're parsing
20223 instead of just stating that we're parsing the geoip file.
20224 Implements ticket 2432.
20225 - Make sure every relay writes a state file at least every 12 hours.
20226 Previously, a relay could go for weeks without writing its state
20227 file, and on a crash could lose its bandwidth history, capacity
20228 estimates, client country statistics, and so on. Addresses bug 3012.
20229 - Relays report the number of bytes spent on answering directory
20230 requests in extra-info descriptors similar to {read,write}-history.
20231 Implements enhancement 1790.
20232 - Report only the top 10 ports in exit-port stats in order not to
20233 exceed the maximum extra-info descriptor length of 50 KB. Implements
20235 - If writing the state file to disk fails, wait up to an hour before
20236 retrying again, rather than trying again each second. Fixes bug
20237 2346; bugfix on Tor 0.1.1.3-alpha.
20238 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
20239 when we switch from being a public relay to a bridge. Otherwise
20240 there will still be clients that see the relay in their consensus,
20241 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
20243 - Update to the August 2 2011 Maxmind GeoLite Country database.
20245 o Minor features (clients):
20246 - When expiring circuits, use microsecond timers rather than
20247 one-second timers. This can avoid an unpleasant situation where a
20248 circuit is launched near the end of one second and expired right
20249 near the beginning of the next, and prevent fluctuations in circuit
20251 - If we've configured EntryNodes and our network goes away and/or all
20252 our entrynodes get marked down, optimistically retry them all when
20253 a new socks application request appears. Fixes bug 1882.
20254 - Always perform router selections using weighted relay bandwidth,
20255 even if we don't need a high capacity circuit at the time. Non-fast
20256 circuits now only differ from fast ones in that they can use relays
20257 not marked with the Fast flag. This "feature" could turn out to
20258 be a horrible bug; we should investigate more before it goes into
20260 - When we run out of directory information such that we can't build
20261 circuits, but then get enough that we can build circuits, log when
20262 we actually construct a circuit, so the user has a better chance of
20263 knowing what's going on. Fixes bug 1362.
20264 - Log SSL state transitions at debug level during handshake, and
20265 include SSL states in error messages. This may help debug future
20266 SSL handshake issues.
20268 o Minor features (directory authorities):
20269 - When a router changes IP address or port, authorities now launch
20270 a new reachability test for it. Implements ticket 1899.
20271 - Directory authorities now reject relays running any versions of
20272 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
20273 known bugs that keep RELAY_EARLY cells from working on rendezvous
20274 circuits. Followup to fix for bug 2081.
20275 - Directory authorities now reject relays running any version of Tor
20276 older than 0.2.0.26-rc. That version is the earliest that fetches
20277 current directory information correctly. Fixes bug 2156.
20278 - Directory authorities now do an immediate reachability check as soon
20279 as they hear about a new relay. This change should slightly reduce
20280 the time between setting up a relay and getting listed as running
20281 in the consensus. It should also improve the time between setting
20282 up a bridge and seeing use by bridge users.
20283 - Directory authorities no longer launch a TLS connection to every
20284 relay as they startup. Now that we have 2k+ descriptors cached,
20285 the resulting network hiccup is becoming a burden. Besides,
20286 authorities already avoid voting about Running for the first half
20287 hour of their uptime.
20288 - Directory authorities now log the source of a rejected POSTed v3
20289 networkstatus vote, so we can track failures better.
20290 - Backport code from 0.2.3.x that allows directory authorities to
20291 clean their microdescriptor caches. Needed to resolve bug 2230.
20293 o Minor features (hidden services):
20294 - Use computed circuit-build timeouts to decide when to launch
20295 parallel introduction circuits for hidden services. (Previously,
20296 we would retry after 15 seconds.)
20297 - Don't allow v0 hidden service authorities to act as clients.
20298 Required by fix for bug 3000.
20299 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
20300 by fix for bug 3000.
20301 - Make hidden services work better in private Tor networks by not
20302 requiring any uptime to join the hidden service descriptor
20303 DHT. Implements ticket 2088.
20304 - Log (at info level) when purging pieces of hidden-service-client
20305 state because of SIGNAL NEWNYM.
20307 o Minor features (controller interface):
20308 - New "GETINFO net/listeners/(type)" controller command to return
20309 a list of addresses and ports that are bound for listeners for a
20310 given connection type. This is useful when the user has configured
20311 "SocksPort auto" and the controller needs to know which port got
20312 chosen. Resolves another part of ticket 3076.
20313 - Have the controller interface give a more useful message than
20314 "Internal Error" in response to failed GETINFO requests.
20315 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
20316 event, to give information on the current rate of circuit timeouts
20317 over our stored history.
20318 - The 'EXTENDCIRCUIT' control port command can now be used with
20319 a circ id of 0 and no path. This feature will cause Tor to build
20320 a new 'fast' general purpose circuit using its own path selection
20322 - Added a BUILDTIMEOUT_SET controller event to describe changes
20323 to the circuit build timeout.
20324 - New controller command "getinfo config-text". It returns the
20325 contents that Tor would write if you send it a SAVECONF command,
20326 so the controller can write the file to disk itself.
20328 o Minor features (controller protocol):
20329 - Add a new ControlSocketsGroupWritable configuration option: when
20330 it is turned on, ControlSockets are group-writeable by the default
20331 group of the current user. Patch by Jérémy Bobbio; implements
20333 - Tor now refuses to create a ControlSocket in a directory that is
20334 world-readable (or group-readable if ControlSocketsGroupWritable
20335 is 0). This is necessary because some operating systems do not
20336 enforce permissions on an AF_UNIX sockets. Permissions on the
20337 directory holding the socket, however, seems to work everywhere.
20338 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
20339 not. This would lead to a cookie that is still not group readable.
20340 Closes bug 1843. Suggested by katmagic.
20341 - Future-proof the controller protocol a bit by ignoring keyword
20342 arguments we do not recognize.
20344 o Minor features (more useful logging):
20345 - Revise most log messages that refer to nodes by nickname to
20346 instead use the "$key=nickname at address" format. This should be
20347 more useful, especially since nicknames are less and less likely
20348 to be unique. Resolves ticket 3045.
20349 - When an HTTPS proxy reports "403 Forbidden", we now explain
20350 what it means rather than calling it an unexpected status code.
20351 Closes bug 2503. Patch from Michael Yakubovich.
20352 - Rate-limit a warning about failures to download v2 networkstatus
20353 documents. Resolves part of bug 1352.
20354 - Rate-limit the "your application is giving Tor only an IP address"
20355 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
20356 - Rate-limit "Failed to hand off onionskin" warnings.
20357 - When logging a rate-limited warning, we now mention how many messages
20358 got suppressed since the last warning.
20359 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
20360 2 no signature, 4 required" messages about consensus signatures
20361 easier to read, and make sure they get logged at the same severity
20362 as the messages explaining which keys are which. Fixes bug 1290.
20363 - Don't warn when we have a consensus that we can't verify because
20364 of missing certificates, unless those certificates are ones
20365 that we have been trying and failing to download. Fixes bug 1145.
20367 o Minor features (log domains):
20368 - Add documentation for configuring logging at different severities in
20369 different log domains. We've had this feature since 0.2.1.1-alpha,
20370 but for some reason it never made it into the manpage. Fixes
20372 - Make it simpler to specify "All log domains except for A and B".
20373 Previously you needed to say "[*,~A,~B]". Now you can just say
20375 - Add a "LogMessageDomains 1" option to include the domains of log
20376 messages along with the messages. Without this, there's no way
20377 to use log domains without reading the source or doing a lot
20379 - Add a new "Handshake" log domain for activities that happen
20380 during the TLS handshake.
20382 o Minor features (build process):
20383 - Make compilation with clang possible when using
20384 "--enable-gcc-warnings" by removing two warning options that clang
20385 hasn't implemented yet and by fixing a few warnings. Resolves
20387 - Detect platforms that brokenly use a signed size_t, and refuse to
20388 build there. Found and analyzed by doorss and rransom.
20389 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
20391 - Add support for statically linking zlib by specifying
20392 "--enable-static-zlib", to go with our support for statically
20393 linking openssl and libevent. Resolves bug 1358.
20394 - Instead of adding the svn revision to the Tor version string, report
20395 the git commit (when we're building from a git checkout).
20396 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
20398 - New --digests command-line switch to output the digests of the
20399 source files Tor was built with.
20400 - Generate our manpage and HTML documentation using Asciidoc. This
20401 change should make it easier to maintain the documentation, and
20402 produce nicer HTML. The build process fails if asciidoc cannot
20403 be found and building with asciidoc isn't disabled (via the
20404 "--disable-asciidoc" argument to ./configure. Skipping the manpage
20405 speeds up the build considerably.
20407 o Minor features (options / torrc):
20408 - Warn when the same option is provided more than once in a torrc
20409 file, on the command line, or in a single SETCONF statement, and
20410 the option is one that only accepts a single line. Closes bug 1384.
20411 - Warn when the user configures two HiddenServiceDir lines that point
20412 to the same directory. Bugfix on 0.0.6 (the version introducing
20413 HiddenServiceDir); fixes bug 3289.
20414 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
20415 do individual connection-level rate limiting of clients. The torrc
20416 config options with the same names trump the consensus params, if
20417 both are present. Replaces the old "bwconnrate" and "bwconnburst"
20418 consensus params which were broken from 0.2.2.7-alpha through
20419 0.2.2.14-alpha. Closes bug 1947.
20420 - New config option "WarnUnsafeSocks 0" disables the warning that
20421 occurs whenever Tor receives a socks handshake using a version of
20422 the socks protocol that can only provide an IP address (rather
20423 than a hostname). Setups that do DNS locally over Tor are fine,
20424 and we shouldn't spam the logs in that case.
20425 - New config option "CircuitStreamTimeout" to override our internal
20426 timeout schedule for how many seconds until we detach a stream from
20427 a circuit and try a new circuit. If your network is particularly
20428 slow, you might want to set this to a number like 60.
20429 - New options for SafeLogging to allow scrubbing only log messages
20430 generated while acting as a relay. Specify "SafeLogging relay" if
20431 you want to ensure that only messages known to originate from
20432 client use of the Tor process will be logged unsafely.
20433 - Time and memory units in the configuration file can now be set to
20434 fractional units. For example, "2.5 GB" is now a valid value for
20436 - Support line continuations in the torrc config file. If a line
20437 ends with a single backslash character, the newline is ignored, and
20438 the configuration value is treated as continuing on the next line.
20441 o Minor features (unit tests):
20442 - Revise our unit tests to use the "tinytest" framework, so we
20443 can run tests in their own processes, have smarter setup/teardown
20444 code, and so on. The unit test code has moved to its own
20445 subdirectory, and has been split into multiple modules.
20446 - Add a unit test for cross-platform directory-listing code.
20447 - Add some forgotten return value checks during unit tests. Found
20449 - Use GetTempDir to find the proper temporary directory location on
20450 Windows when generating temporary files for the unit tests. Patch
20453 o Minor features (misc):
20454 - The "torify" script now uses torsocks where available.
20455 - Make Libevent log messages get delivered to controllers later,
20456 and not from inside the Libevent log handler. This prevents unsafe
20457 reentrant Libevent calls while still letting the log messages
20459 - Certain Tor clients (such as those behind check.torproject.org) may
20460 want to fetch the consensus in an extra early manner. To enable this
20461 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
20462 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
20463 as only certain clients who must have this information sooner should
20465 - Expand homedirs passed to tor-checkkey. This should silence a
20466 coverity complaint about passing a user-supplied string into
20467 open() without checking it.
20468 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
20469 used on bridges, and it makes bridge scanning somewhat easier.
20470 - Create the /var/run/tor directory on startup on OpenSUSE if it is
20471 not already created. Patch from Andreas Stieger. Fixes bug 2573.
20473 o Minor bugfixes (relays):
20474 - When a relay decides that its DNS is too broken for it to serve
20475 as an exit server, it advertised itself as a non-exit, but
20476 continued to act as an exit. This could create accidental
20477 partitioning opportunities for users. Instead, if a relay is
20478 going to advertise reject *:* as its exit policy, it should
20479 really act with exit policy "reject *:*". Fixes bug 2366.
20480 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
20481 - Publish a router descriptor even if generating an extra-info
20482 descriptor fails. Previously we would not publish a router
20483 descriptor without an extra-info descriptor; this can cause fast
20484 exit relays collecting exit-port statistics to drop from the
20485 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
20486 - When we're trying to guess whether we know our IP address as
20487 a relay, we would log various ways that we failed to guess
20488 our address, but never log that we ended up guessing it
20489 successfully. Now add a log line to help confused and anxious
20490 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
20491 - For bandwidth accounting, calculate our expected bandwidth rate
20492 based on the time during which we were active and not in
20493 soft-hibernation during the last interval. Previously, we were
20494 also considering the time spent in soft-hibernation. If this
20495 was a long time, we would wind up underestimating our bandwidth
20496 by a lot, and skewing our wakeup time towards the start of the
20497 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
20498 - Demote a confusing TLS warning that relay operators might get when
20499 someone tries to talk to their ORPort. It is not the operator's
20500 fault, nor can they do anything about it. Fixes bug 1364; bugfix
20502 - Change "Application request when we're believed to be offline."
20503 notice to "Application request when we haven't used client
20504 functionality lately.", to clarify that it's not an error. Bugfix
20505 on 0.0.9.3; fixes bug 1222.
20507 o Minor bugfixes (bridges):
20508 - When a client starts or stops using bridges, never use a circuit
20509 that was built before the configuration change. This behavior could
20510 put at risk a user who uses bridges to ensure that her traffic
20511 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
20513 - Do not reset the bridge descriptor download status every time we
20514 re-parse our configuration or get a configuration change. Fixes
20515 bug 3019; bugfix on 0.2.0.3-alpha.
20516 - Users couldn't configure a regular relay to be their bridge. It
20517 didn't work because when Tor fetched the bridge descriptor, it found
20518 that it already had it, and didn't realize that the purpose of the
20519 descriptor had changed. Now we replace routers with a purpose other
20520 than bridge with bridge descriptors when fetching them. Bugfix on
20521 0.1.1.9-alpha. Fixes bug 1776.
20522 - In the special case where you configure a public exit relay as your
20523 bridge, Tor would be willing to use that exit relay as the last
20524 hop in your circuit as well. Now we fail that circuit instead.
20525 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
20527 o Minor bugfixes (clients):
20528 - We now ask the other side of a stream (the client or the exit)
20529 for more data on that stream when the amount of queued data on
20530 that stream dips low enough. Previously, we wouldn't ask the
20531 other side for more data until either it sent us more data (which
20532 it wasn't supposed to do if it had exhausted its window!) or we
20533 had completely flushed all our queued data. This flow control fix
20534 should improve throughput. Fixes bug 2756; bugfix on the earliest
20535 released versions of Tor (svn commit r152).
20536 - When a client finds that an origin circuit has run out of 16-bit
20537 stream IDs, we now mark it as unusable for new streams. Previously,
20538 we would try to close the entire circuit. Bugfix on 0.0.6.
20539 - Make it explicit that we don't cannibalize one-hop circuits. This
20540 happens in the wild, but doesn't turn out to be a problem because
20541 we fortunately don't use those circuits. Many thanks to outofwords
20542 for the initial analysis and to swissknife who confirmed that
20543 two-hop circuits are actually created.
20544 - Resolve an edge case in path weighting that could make us misweight
20545 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
20546 - Make the DNSPort option work with libevent 2.x. Don't alter the
20547 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
20549 o Minor bugfixes (directory authorities):
20550 - Make directory authorities more accurate at recording when
20551 relays that have failed several reachability tests became
20552 unreachable, so we can provide more accuracy at assigning Stable,
20553 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
20554 - Directory authorities are now more robust to hops back in time
20555 when calculating router stability. Previously, if a run of uptime
20556 or downtime appeared to be negative, the calculation could give
20557 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
20559 - Directory authorities will now attempt to download consensuses
20560 if their own efforts to make a live consensus have failed. This
20561 change means authorities that restart will fetch a valid
20562 consensus, and it means authorities that didn't agree with the
20563 current consensus will still fetch and serve it if it has enough
20564 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
20565 - Never vote for a server as "Running" if we have a descriptor for
20566 it claiming to be hibernating, and that descriptor was published
20567 more recently than our last contact with the server. Bugfix on
20568 0.2.0.3-alpha; fixes bug 911.
20569 - Directory authorities no longer change their opinion of, or vote on,
20570 whether a router is Running, unless they have themselves been
20571 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
20574 o Minor bugfixes (hidden services):
20575 - Log malformed requests for rendezvous descriptors as protocol
20576 warnings, not warnings. Also, use a more informative log message
20577 in case someone sees it at log level warning without prior
20578 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
20579 - Accept hidden service descriptors if we think we might be a hidden
20580 service directory, regardless of what our consensus says. This
20581 helps robustness, since clients and hidden services can sometimes
20582 have a more up-to-date view of the network consensus than we do,
20583 and if they think that the directory authorities list us a HSDir,
20584 we might actually be one. Related to bug 2732; bugfix on
20586 - Correct the warning displayed when a rendezvous descriptor exceeds
20587 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
20589 - Clients and hidden services now use HSDir-flagged relays for hidden
20590 service descriptor downloads and uploads even if the relays have no
20591 DirPort set and the client has disabled TunnelDirConns. This will
20592 eventually allow us to give the HSDir flag to relays with no
20593 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
20594 - Only limit the lengths of single HS descriptors, even when multiple
20595 HS descriptors are published to an HSDir relay in a single POST
20596 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
20598 o Minor bugfixes (controllers):
20599 - Allow GETINFO fingerprint to return a fingerprint even when
20600 we have not yet built a router descriptor. Fixes bug 3577;
20601 bugfix on 0.2.0.1-alpha.
20602 - Send a SUCCEEDED stream event to the controller when a reverse
20603 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
20604 discovered by katmagic.
20605 - Remove a trailing asterisk from "exit-policy/default" in the
20606 output of the control port command "GETINFO info/names". Bugfix
20608 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
20609 2917. Bugfix on 0.1.1.1-alpha.
20610 - When we restart our relay, we might get a successful connection
20611 from the outside before we've started our reachability tests,
20612 triggering a warning: "ORPort found reachable, but I have no
20613 routerinfo yet. Failing to inform controller of success." This
20614 bug was harmless unless Tor is running under a controller
20615 like Vidalia, in which case the controller would never get a
20616 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
20618 - When a controller changes TrackHostExits, remove mappings for
20619 hosts that should no longer have their exits tracked. Bugfix on
20621 - When a controller changes VirtualAddrNetwork, remove any mappings
20622 for hosts that were automapped to the old network. Bugfix on
20624 - When a controller changes one of the AutomapHosts* options, remove
20625 any mappings for hosts that should no longer be automapped. Bugfix
20627 - Fix an off-by-one error in calculating some controller command
20628 argument lengths. Fortunately, this mistake is harmless since
20629 the controller code does redundant NUL termination too. Found by
20630 boboper. Bugfix on 0.1.1.1-alpha.
20631 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
20632 would return "551 Internal error" rather than "552 Unrecognized key
20633 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
20634 - Don't spam the controller with events when we have no file
20635 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
20636 for log messages was already solved from bug 748.)
20637 - Emit a GUARD DROPPED controller event for a case we missed.
20638 - Ensure DNS requests launched by "RESOLVE" commands from the
20639 controller respect the __LeaveStreamsUnattached setconf options. The
20640 same goes for requests launched via DNSPort or transparent
20641 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
20643 o Minor bugfixes (config options):
20644 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
20645 Change the limit to 512 characters by removing base64 newlines.
20646 Fixes bug 2752. Fix by Michael Yakubovich.
20647 - Complain if PublishServerDescriptor is given multiple arguments that
20648 include 0 or 1. This configuration will be rejected in the future.
20649 Bugfix on 0.2.0.1-alpha; closes bug 1107.
20650 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
20651 Bugfix on 0.2.0.13-alpha; closes bug 928.
20653 o Minor bugfixes (log subsystem fixes):
20654 - When unable to format an address as a string, report its value
20655 as "???" rather than reusing the last formatted address. Bugfix
20657 - Be more consistent in our treatment of file system paths. "~" should
20658 get expanded to the user's home directory in the Log config option.
20659 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
20660 feature for the -f and --DataDirectory options.
20662 o Minor bugfixes (memory management):
20663 - Don't stack-allocate the list of supplementary GIDs when we're
20664 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
20665 could take up to 256K, which is way too much stack. Found by
20666 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
20667 - Save a couple bytes in memory allocation every time we escape
20668 certain characters in a string. Patch from Florian Zumbiehl.
20670 o Minor bugfixes (protocol correctness):
20671 - When checking for 1024-bit keys, check for 1024 bits, not 128
20672 bytes. This allows Tor to correctly discard keys of length 1017
20673 through 1023. Bugfix on 0.0.9pre5.
20674 - Require that introduction point keys and onion handshake keys
20675 have a public exponent of 65537. Starts to fix bug 3207; bugfix
20677 - Handle SOCKS messages longer than 128 bytes long correctly, rather
20678 than waiting forever for them to finish. Fixes bug 2330; bugfix
20679 on 0.2.0.16-alpha. Found by doorss.
20680 - Never relay a cell for a circuit we have already destroyed.
20681 Between marking a circuit as closeable and finally closing it,
20682 it may have been possible for a few queued cells to get relayed,
20683 even though they would have been immediately dropped by the next
20684 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
20685 - Never queue a cell for a circuit that's already been marked
20687 - Fix a spec conformance issue: the network-status-version token
20688 must be the first token in a v3 consensus or vote. Discovered by
20689 "parakeep". Bugfix on 0.2.0.3-alpha.
20690 - A networkstatus vote must contain exactly one signature. Spec
20691 conformance issue. Bugfix on 0.2.0.3-alpha.
20692 - When asked about a DNS record type we don't support via a
20693 client DNSPort, reply with NOTIMPL rather than an empty
20694 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
20695 - Make more fields in the controller protocol case-insensitive, since
20696 control-spec.txt said they were.
20698 o Minor bugfixes (log messages):
20699 - Fix a log message that said "bits" while displaying a value in
20700 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
20702 - Downgrade "no current certificates known for authority" message from
20703 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
20704 - Correctly describe errors that occur when generating a TLS object.
20705 Previously we would attribute them to a failure while generating a
20706 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
20708 - Fix an instance where a Tor directory mirror might accidentally
20709 log the IP address of a misbehaving Tor client. Bugfix on
20711 - Stop logging at severity 'warn' when some other Tor client tries
20712 to establish a circuit with us using weak DH keys. It's a protocol
20713 violation, but that doesn't mean ordinary users need to hear about
20714 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
20715 - If your relay can't keep up with the number of incoming create
20716 cells, it would log one warning per failure into your logs. Limit
20717 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
20719 o Minor bugfixes (build fixes):
20720 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
20721 - When warning about missing zlib development packages during compile,
20722 give the correct package names. Bugfix on 0.2.0.1-alpha.
20723 - Fix warnings that newer versions of autoconf produce during
20724 ./autogen.sh. These warnings appear to be harmless in our case,
20725 but they were extremely verbose. Fixes bug 2020.
20726 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
20729 o Minor bugfixes (portability):
20730 - Write several files in text mode, on OSes that distinguish text
20731 mode from binary mode (namely, Windows). These files are:
20732 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
20733 that collect those statistics; 'client_keys' and 'hostname' for
20734 hidden services that use authentication; and (in the tor-gencert
20735 utility) newly generated identity and signing keys. Previously,
20736 we wouldn't specify text mode or binary mode, leading to an
20737 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
20738 the DirRecordUsageByCountry option which would have triggered
20739 the assertion failure was added), although this assertion failure
20740 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
20741 - Selectively disable deprecation warnings on OS X because Lion
20742 started deprecating the shipped copy of openssl. Fixes bug 3643.
20743 - Use a wide type to hold sockets when built for 64-bit Windows.
20745 - Fix an issue that prevented static linking of libevent on
20746 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
20747 where we introduced the "--with-static-libevent" configure option.
20748 - Fix a bug with our locking implementation on Windows that couldn't
20749 correctly detect when a file was already locked. Fixes bug 2504,
20750 bugfix on 0.2.1.6-alpha.
20751 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
20753 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
20754 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
20757 o Minor bugfixes (code correctness):
20758 - Always NUL-terminate the sun_path field of a sockaddr_un before
20759 passing it to the kernel. (Not a security issue: kernels are
20760 smart enough to reject bad sockaddr_uns.) Found by Coverity;
20761 CID #428. Bugfix on Tor 0.2.0.3-alpha.
20762 - Make connection_printf_to_buf()'s behavior sane. Its callers
20763 expect it to emit a CRLF iff the format string ends with CRLF;
20764 it actually emitted a CRLF iff (a) the format string ended with
20765 CRLF or (b) the resulting string was over 1023 characters long or
20766 (c) the format string did not end with CRLF *and* the resulting
20767 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
20768 fixes part of bug 3407.
20769 - Make send_control_event_impl()'s behavior sane. Its callers
20770 expect it to always emit a CRLF at the end of the string; it
20771 might have emitted extra control characters as well. Bugfix on
20772 0.1.1.9-alpha; fixes another part of bug 3407.
20773 - Make crypto_rand_int() check the value of its input correctly.
20774 Previously, it accepted values up to UINT_MAX, but could return a
20775 negative number if given a value above INT_MAX+1. Found by George
20776 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
20777 - Fix a potential null-pointer dereference while computing a
20778 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
20780 - If we fail to compute the identity digest of a v3 legacy keypair,
20781 warn, and don't use a buffer-full of junk instead. Bugfix on
20782 0.2.1.1-alpha; fixes bug 3106.
20783 - Resolve an untriggerable issue in smartlist_string_num_isin(),
20784 where if the function had ever in the future been used to check
20785 for the presence of a too-large number, it would have given an
20786 incorrect result. (Fortunately, we only used it for 16-bit
20787 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
20788 - Be more careful about reporting the correct error from a failed
20789 connect() system call. Under some circumstances, it was possible to
20790 look at an incorrect value for errno when sending the end reason.
20791 Bugfix on 0.1.0.1-rc.
20792 - Correctly handle an "impossible" overflow cases in connection byte
20793 counting, where we write or read more than 4GB on an edge connection
20794 in a single second. Bugfix on 0.1.2.8-beta.
20795 - Avoid a double mark-for-free warning when failing to attach a
20796 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
20798 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
20799 found by "cypherpunks". This bug was introduced before the first
20800 Tor release, in svn commit r110.
20801 - Fix a bug in bandwidth history state parsing that could have been
20802 triggered if a future version of Tor ever changed the timing
20803 granularity at which bandwidth history is measured. Bugfix on
20804 Tor 0.1.1.11-alpha.
20805 - Add assertions to check for overflow in arguments to
20806 base32_encode() and base32_decode(); fix a signed-unsigned
20807 comparison there too. These bugs are not actually reachable in Tor,
20808 but it's good to prevent future errors too. Found by doorss.
20809 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
20811 - Set target port in get_interface_address6() correctly. Bugfix
20812 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
20813 - Fix an impossible-to-actually-trigger buffer overflow in relay
20814 descriptor generation. Bugfix on 0.1.0.15.
20815 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
20817 o Minor bugfixes (code improvements):
20818 - After we free an internal connection structure, overwrite it
20819 with a different memory value than we use for overwriting a freed
20820 internal circuit structure. Should help with debugging. Suggested
20822 - If OpenSSL fails to make a duplicate of a private or public key, log
20823 an error message and try to exit cleanly. May help with debugging
20824 if bug 1209 ever remanifests.
20825 - Some options used different conventions for uppercasing of acronyms
20826 when comparing manpage and source. Fix those in favor of the
20827 manpage, as it makes sense to capitalize acronyms.
20828 - Take a first step towards making or.h smaller by splitting out
20829 function definitions for all source files in src/or/. Leave
20830 structures and defines in or.h for now.
20831 - Remove a few dead assignments during router parsing. Found by
20833 - Don't use 1-bit wide signed bit fields. Found by coverity.
20834 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
20835 None of the cases where we did this before were wrong, but by making
20836 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
20837 - The memarea code now uses a sentinel value at the end of each area
20838 to make sure nothing writes beyond the end of an area. This might
20839 help debug some conceivable causes of bug 930.
20840 - Always treat failure to allocate an RSA key as an unrecoverable
20842 - Add some more defensive programming for architectures that can't
20843 handle unaligned integer accesses. We don't know of any actual bugs
20844 right now, but that's the best time to fix them. Fixes bug 1943.
20846 o Minor bugfixes (misc):
20847 - Fix a rare bug in rend_fn unit tests: we would fail a test when
20848 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
20849 on 0.2.0.10-alpha; fixes bug 1808.
20850 - Where available, use Libevent 2.0's periodic timers so that our
20851 once-per-second cleanup code gets called even more closely to
20852 once per second than it would otherwise. Fixes bug 943.
20853 - Ignore OutboundBindAddress when connecting to localhost.
20854 Connections to localhost need to come _from_ localhost, or else
20855 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
20857 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
20859 - If any of the v3 certs we download are unparseable, we should
20860 actually notice the failure so we don't retry indefinitely. Bugfix
20861 on 0.2.0.x; reported by "rotator".
20862 - When Tor fails to parse a descriptor of any kind, dump it to disk.
20863 Might help diagnosing bug 1051.
20864 - Make our 'torify' script more portable; if we have only one of
20865 'torsocks' or 'tsocks' installed, don't complain to the user;
20866 and explain our warning about tsocks better.
20867 - Fix some urls in the exit notice file and make it XHTML1.1 strict
20868 compliant. Based on a patch from Christian Kujau.
20870 o Documentation changes:
20871 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
20872 - Resolve all doxygen warnings except those for missing documentation.
20874 - Add doxygen documentation for more functions, fields, and types.
20875 - Convert the HACKING file to asciidoc, and add a few new sections
20876 to it, explaining how we use Git, how we make changelogs, and
20877 what should go in a patch.
20878 - Document the default socks host and port (127.0.0.1:9050) for
20880 - Removed some unnecessary files from the source distribution. The
20881 AUTHORS file has now been merged into the people page on the
20882 website. The roadmaps and design doc can now be found in the
20883 projects directory in svn.
20885 o Deprecated and removed features (config):
20886 - Remove the torrc.complete file. It hasn't been kept up to date
20887 and users will have better luck checking out the manpage.
20888 - Remove the HSAuthorityRecordStats option that version 0 hidden
20889 service authorities could use to track statistics of overall v0
20890 hidden service usage.
20891 - Remove the obsolete "NoPublish" option; it has been flagged
20892 as obsolete and has produced a warning since 0.1.1.18-rc.
20893 - Caches no longer download and serve v2 networkstatus documents
20894 unless FetchV2Networkstatus flag is set: these documents haven't
20895 haven't been used by clients or relays since 0.2.0.x. Resolves
20898 o Deprecated and removed features (controller):
20899 - The controller no longer accepts the old obsolete "addr-mappings/"
20900 or "unregistered-servers-" GETINFO values.
20901 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
20902 always on; using them is necessary for correct forward-compatible
20905 o Deprecated and removed features (misc):
20906 - Hidden services no longer publish version 0 descriptors, and clients
20907 do not request or use version 0 descriptors. However, the old hidden
20908 service authorities still accept and serve version 0 descriptors
20909 when contacted by older hidden services/clients.
20910 - Remove undocumented option "-F" from tor-resolve: it hasn't done
20911 anything since 0.2.1.16-rc.
20912 - Remove everything related to building the expert bundle for OS X.
20913 It has confused many users, doesn't work right on OS X 10.6,
20914 and is hard to get rid of once installed. Resolves bug 1274.
20915 - Remove support for .noconnect style addresses. Nobody was using
20916 them, and they provided another avenue for detecting Tor users
20917 via application-level web tricks.
20918 - When we fixed bug 1038 we had to put in a restriction not to send
20919 RELAY_EARLY cells on rend circuits. This was necessary as long
20920 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
20921 active. Now remove this obsolete check. Resolves bug 2081.
20922 - Remove workaround code to handle directory responses from servers
20923 that had bug 539 (they would send HTTP status 503 responses _and_
20924 send a body too). Since only server versions before
20925 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
20926 keep the workaround in place.
20927 - Remove the old 'fuzzy time' logic. It was supposed to be used for
20928 handling calculations where we have a known amount of clock skew and
20929 an allowed amount of unknown skew. But we only used it in three
20930 places, and we never adjusted the known/unknown skew values. This is
20931 still something we might want to do someday, but if we do, we'll
20932 want to do it differently.
20933 - Remove the "--enable-iphone" option to ./configure. According to
20934 reports from Marco Bonetti, Tor builds fine without any special
20935 tweaking on recent iPhone SDK versions.
20938 Changes in version 0.2.1.30 - 2011-02-23
20939 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
20940 change is a slight tweak to Tor's TLS handshake that makes relays
20941 and bridges that run this new version reachable from Iran again.
20942 We don't expect this tweak will win the arms race long-term, but it
20943 buys us time until we roll out a better solution.
20946 - Stop sending a CLOCK_SKEW controller status event whenever
20947 we fetch directory information from a relay that has a wrong clock.
20948 Instead, only inform the controller when it's a trusted authority
20949 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
20950 the rest of bug 1074.
20951 - Fix a bounds-checking error that could allow an attacker to
20952 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
20953 Found by "piebeer".
20954 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
20955 Tor would ignore their RelayBandwidthBurst setting,
20956 potentially using more bandwidth than expected. Bugfix on
20957 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
20958 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
20959 hidserv" in her torrc. The 'hidserv' argument never controlled
20960 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
20963 - Adjust our TLS Diffie-Hellman parameters to match those used by
20965 - Update to the February 1 2011 Maxmind GeoLite Country database.
20968 - Check for and reject overly long directory certificates and
20969 directory tokens before they have a chance to hit any assertions.
20970 Bugfix on 0.2.1.28. Found by "doorss".
20971 - Bring the logic that gathers routerinfos and assesses the
20972 acceptability of circuits into line. This prevents a Tor OP from
20973 getting locked in a cycle of choosing its local OR as an exit for a
20974 path (due to a .exit request) and then rejecting the circuit because
20975 its OR is not listed yet. It also prevents Tor clients from using an
20976 OR running in the same instance as an exit (due to a .exit request)
20977 if the OR does not meet the same requirements expected of an OR
20978 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
20980 o Packaging changes:
20981 - Stop shipping the Tor specs files and development proposal documents
20982 in the tarball. They are now in a separate git repository at
20983 git://git.torproject.org/torspec.git
20984 - Do not include Git version tags as though they are SVN tags when
20985 generating a tarball from inside a repository that has switched
20986 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
20989 Changes in version 0.2.1.29 - 2011-01-15
20990 Tor 0.2.1.29 continues our recent code security audit work. The main
20991 fix resolves a remote heap overflow vulnerability that can allow remote
20992 code execution. Other fixes address a variety of assert and crash bugs,
20993 most of which we think are hard to exploit remotely.
20995 o Major bugfixes (security):
20996 - Fix a heap overflow bug where an adversary could cause heap
20997 corruption. This bug probably allows remote code execution
20998 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
21000 - Prevent a denial-of-service attack by disallowing any
21001 zlib-compressed data whose compression factor is implausibly
21002 high. Fixes part of bug 2324; reported by "doorss".
21003 - Zero out a few more keys in memory before freeing them. Fixes
21004 bug 2384 and part of bug 2385. These key instances found by
21005 "cypherpunks", based on Andrew Case's report about being able
21006 to find sensitive data in Tor's memory space if you have enough
21007 permissions. Bugfix on 0.0.2pre9.
21009 o Major bugfixes (crashes):
21010 - Prevent calls to Libevent from inside Libevent log handlers.
21011 This had potential to cause a nasty set of crashes, especially
21012 if running Libevent with debug logging enabled, and running
21013 Tor with a controller watching for low-severity log messages.
21014 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
21015 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
21016 underflow errors there too. Fixes the other part of bug 2324.
21017 - Fix a bug where we would assert if we ever had a
21018 cached-descriptors.new file (or another file read directly into
21019 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
21020 on 0.2.1.25. Found by doorss.
21021 - Fix some potential asserts and parsing issues with grossly
21022 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
21025 o Minor bugfixes (other):
21026 - Fix a bug with handling misformed replies to reverse DNS lookup
21027 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
21028 bug reported by doorss.
21029 - Fix compilation on mingw when a pthreads compatibility library
21030 has been installed. (We don't want to use it, so we shouldn't
21031 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
21032 - Fix a bug where we would declare that we had run out of virtual
21033 addresses when the address space was only half-exhausted. Bugfix
21035 - Correctly handle the case where AutomapHostsOnResolve is set but
21036 no virtual addresses are available. Fixes bug 2328; bugfix on
21037 0.1.2.1-alpha. Bug found by doorss.
21038 - Correctly handle wrapping around when we run out of virtual
21039 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
21042 - Update to the January 1 2011 Maxmind GeoLite Country database.
21043 - Introduce output size checks on all of our decryption functions.
21046 - Tor does not build packages correctly with Automake 1.6 and earlier;
21047 added a check to Makefile.am to make sure that we're building with
21048 Automake 1.7 or later.
21049 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
21050 because we built it with a too-old version of automake. Thus that
21051 release broke ./configure --enable-openbsd-malloc, which is popular
21052 among really fast exit relays on Linux.
21055 Changes in version 0.2.1.28 - 2010-12-17
21056 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
21057 exploitable bugs. We also took this opportunity to change the IP address
21058 for one of our directory authorities, and to update the geoip database
21062 - Fix a remotely exploitable bug that could be used to crash instances
21063 of Tor remotely by overflowing on the heap. Remote-code execution
21064 hasn't been confirmed, but can't be ruled out. Everyone should
21065 upgrade. Bugfix on the 0.1.1 series and later.
21067 o Directory authority changes:
21068 - Change IP address and ports for gabelmoo (v3 directory authority).
21071 - Update to the December 1 2010 Maxmind GeoLite Country database.
21074 Changes in version 0.2.1.27 - 2010-11-23
21075 Yet another OpenSSL security patch broke its compatibility with Tor:
21076 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
21077 also took this opportunity to fix several crash bugs, integrate a new
21078 directory authority, and update the bundled GeoIP database.
21081 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
21082 No longer set the tlsext_host_name extension on server SSL objects;
21083 but continue to set it on client SSL objects. Our goal in setting
21084 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
21085 bugfix on 0.2.1.1-alpha.
21086 - Do not log messages to the controller while shrinking buffer
21087 freelists. Doing so would sometimes make the controller connection
21088 try to allocate a buffer chunk, which would mess up the internals
21089 of the freelist and cause an assertion failure. Fixes bug 1125;
21090 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
21091 - Learn our external IP address when we're a relay or bridge, even if
21092 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
21093 where we introduced bridge relays that don't need to publish to
21094 be useful. Fixes bug 2050.
21095 - Do even more to reject (and not just ignore) annotations on
21096 router descriptors received anywhere but from the cache. Previously
21097 we would ignore such annotations at first, but cache them to disk
21098 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
21099 - When you're using bridges and your network goes away and your
21100 bridges get marked as down, recover when you attempt a new socks
21101 connection (if the network is back), rather than waiting up to an
21102 hour to try fetching new descriptors for your bridges. Bugfix on
21103 0.2.0.3-alpha; fixes bug 1981.
21106 - Move to the November 2010 Maxmind GeoLite country db (rather
21107 than the June 2009 ip-to-country GeoIP db) for our statistics that
21108 count how many users relays are seeing from each country. Now we'll
21109 have more accurate data, especially for many African countries.
21111 o New directory authorities:
21112 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
21116 - Fix an assertion failure that could occur in directory caches or
21117 bridge users when using a very short voting interval on a testing
21118 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
21120 - Enforce multiplicity rules when parsing annotations. Bugfix on
21121 0.2.0.8-alpha. Found by piebeer.
21122 - Allow handshaking OR connections to take a full KeepalivePeriod
21123 seconds to handshake. Previously, we would close them after
21124 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
21125 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
21127 - When building with --enable-gcc-warnings on OpenBSD, disable
21128 warnings in system headers. This makes --enable-gcc-warnings
21129 pass on OpenBSD 4.8.
21132 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
21133 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
21134 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
21135 Servers can start sending this code when enough clients recognize
21136 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
21137 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
21138 Patch from mingw-san.
21141 - Remove the old debian/ directory from the main Tor distribution.
21142 The official Tor-for-debian git repository lives at the URL
21143 https://git.torproject.org/debian/tor.git
21144 - Stop shipping the old doc/website/ directory in the tarball. We
21145 changed the website format in late 2010, and what we shipped in
21146 0.2.1.26 really wasn't that useful anyway.
21149 Changes in version 0.2.1.26 - 2010-05-02
21150 Tor 0.2.1.26 addresses the recent connection and memory overload
21151 problems we've been seeing on relays, especially relays with their
21152 DirPort open. If your relay has been crashing, or you turned it off
21153 because it used too many resources, give this release a try.
21155 This release also fixes yet another instance of broken OpenSSL libraries
21156 that was causing some relays to drop out of the consensus.
21159 - Teach relays to defend themselves from connection overload. Relays
21160 now close idle circuits early if it looks like they were intended
21161 for directory fetches. Relays are also more aggressive about closing
21162 TLS connections that have no circuits on them. Such circuits are
21163 unlikely to be re-used, and tens of thousands of them were piling
21164 up at the fast relays, causing the relays to run out of sockets
21165 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
21166 their directory fetches over TLS).
21167 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
21168 that claim to be earlier than 0.9.8m, but which have in reality
21169 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
21170 behavior. Possible fix for some cases of bug 1346.
21171 - Directory mirrors were fetching relay descriptors only from v2
21172 directory authorities, rather than v3 authorities like they should.
21173 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
21174 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
21177 - Finally get rid of the deprecated and now harmful notion of "clique
21178 mode", where directory authorities maintain TLS connections to
21182 - In the util/threads test, no longer free the test_mutex before all
21183 worker threads have finished. Bugfix on 0.2.1.6-alpha.
21184 - The master thread could starve the worker threads quite badly on
21185 certain systems, causing them to run only partially in the allowed
21186 window. This resulted in test failures. Now the master thread sleeps
21187 occasionally for a few microseconds while the two worker-threads
21188 compete for the mutex. Bugfix on 0.2.0.1-alpha.
21191 Changes in version 0.2.1.25 - 2010-03-16
21192 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
21193 prevent relays from guessing their IP address correctly. It also fixes
21194 several minor potential security bugs.
21197 - Fix a regression from our patch for bug 1244 that caused relays
21198 to guess their IP address incorrectly if they didn't set Address
21199 in their torrc and/or their address fails to resolve. Bugfix on
21200 0.2.1.23; fixes bug 1269.
21201 - When freeing a session key, zero it out completely. We only zeroed
21202 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
21203 patched by ekir. Fixes bug 1254.
21206 - Fix a dereference-then-NULL-check sequence when publishing
21207 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
21209 - Fix another dereference-then-NULL-check sequence. Bugfix on
21210 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
21211 - Make sure we treat potentially not NUL-terminated strings correctly.
21212 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
21215 Changes in version 0.2.1.24 - 2010-02-21
21216 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
21220 - Work correctly out-of-the-box with even more vendor-patched versions
21221 of OpenSSL. In particular, make it so Debian and OS X don't need
21222 customized patches to run/build.
21225 Changes in version 0.2.1.23 - 2010-02-13
21226 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
21227 again on the latest OS X, and updates the location of a directory
21230 o Major bugfixes (performance):
21231 - We were selecting our guards uniformly at random, and then weighting
21232 which of our guards we'd use uniformly at random. This imbalance
21233 meant that Tor clients were severely limited on throughput (and
21234 probably latency too) by the first hop in their circuit. Now we
21235 select guards weighted by currently advertised bandwidth. We also
21236 automatically discard guards picked using the old algorithm. Fixes
21237 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
21240 - Make Tor work again on the latest OS X: when deciding whether to
21241 use strange flags to turn TLS renegotiation on, detect the OpenSSL
21242 version at run-time, not compile time. We need to do this because
21243 Apple doesn't update its dev-tools headers when it updates its
21244 libraries in a security patch.
21245 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
21246 that could happen on 32-bit platforms with 64-bit time_t. Also fix
21247 a memory leak when requesting a hidden service descriptor we've
21248 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
21252 - Refactor resolve_my_address() to not use gethostbyname() anymore.
21253 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
21256 - Avoid a mad rush at the beginning of each month when each client
21257 rotates half of its guards. Instead we spread the rotation out
21258 throughout the month, but we still avoid leaving a precise timestamp
21259 in the state file about when we first picked the guard. Improves
21260 over the behavior introduced in 0.1.2.17.
21263 Changes in version 0.2.1.22 - 2010-01-19
21264 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
21265 authorities -- it would tell you its whole history of bridge descriptors
21266 if you make the right directory request. This stable update also
21267 rotates two of the seven v3 directory authority keys and locations.
21269 o Directory authority changes:
21270 - Rotate keys (both v3 identity and relay identity) for moria1
21274 - Stop bridge directory authorities from answering dbg-stability.txt
21275 directory queries, which would let people fetch a list of all
21276 bridge identities they track. Bugfix on 0.2.1.6-alpha.
21279 Changes in version 0.2.1.21 - 2009-12-21
21280 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
21281 library. If you use Tor on Linux / Unix and you're getting SSL
21282 renegotiation errors, upgrading should help. We also recommend an
21283 upgrade if you're an exit relay.
21286 - Work around a security feature in OpenSSL 0.9.8l that prevents our
21287 handshake from working unless we explicitly tell OpenSSL that we
21288 are using SSL renegotiation safely. We are, of course, but OpenSSL
21289 0.9.8l won't work unless we say we are.
21290 - Avoid crashing if the client is trying to upload many bytes and the
21291 circuit gets torn down at the same time, or if the flip side
21292 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
21295 - Do not refuse to learn about authority certs and v2 networkstatus
21296 documents that are older than the latest consensus. This bug might
21297 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
21298 Spotted and fixed by xmux.
21299 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
21300 trigger platform-specific option misparsing case found by Coverity
21302 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
21303 trigger assert. Fixes bug 1173.
21306 Changes in version 0.2.1.20 - 2009-10-15
21307 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
21308 services at once, prepares for more performance improvements, and
21309 fixes a bunch of smaller bugs.
21311 The Windows and OS X bundles also include a more recent Vidalia,
21312 and switch from Privoxy to Polipo.
21314 The OS X installers are now drag and drop. It's best to un-install
21315 Tor/Vidalia and then install this new bundle, rather than upgrade. If
21316 you want to upgrade, you'll need to update the paths for Tor and Polipo
21317 in the Vidalia Settings window.
21320 - Send circuit or stream sendme cells when our window has decreased
21321 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
21322 by Karsten when testing the "reduce circuit window" performance
21323 patch. Bugfix on the 54th commit on Tor -- from July 2002,
21324 before the release of Tor 0.0.0. This is the new winner of the
21326 - Fix a remotely triggerable memory leak when a consensus document
21327 contains more than one signature from the same voter. Bugfix on
21329 - Avoid segfault in rare cases when finishing an introduction circuit
21330 as a client and finding out that we don't have an introduction key
21331 for it. Fixes bug 1073. Reported by Aaron Swartz.
21334 - Tor now reads the "circwindow" parameter out of the consensus,
21335 and uses that value for its circuit package window rather than the
21336 default of 1000 cells. Begins the implementation of proposal 168.
21338 o New directory authorities:
21339 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
21341 - Move moria1 and tonga to alternate IP addresses.
21344 - Fix a signed/unsigned compile warning in 0.2.1.19.
21345 - Fix possible segmentation fault on directory authorities. Bugfix on
21347 - Fix an extremely rare infinite recursion bug that could occur if
21348 we tried to log a message after shutting down the log subsystem.
21349 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
21350 - Fix an obscure bug where hidden services on 64-bit big-endian
21351 systems might mis-read the timestamp in v3 introduce cells, and
21352 refuse to connect back to the client. Discovered by "rotor".
21353 Bugfix on 0.2.1.6-alpha.
21354 - We were triggering a CLOCK_SKEW controller status event whenever
21355 we connect via the v2 connection protocol to any relay that has
21356 a wrong clock. Instead, we should only inform the controller when
21357 it's a trusted authority that claims our clock is wrong. Bugfix
21358 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
21359 - We were telling the controller about CHECKING_REACHABILITY and
21360 REACHABILITY_FAILED status events whenever we launch a testing
21361 circuit or notice that one has failed. Instead, only tell the
21362 controller when we want to inform the user of overall success or
21363 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
21365 - Don't warn when we're using a circuit that ends with a node
21366 excluded in ExcludeExitNodes, but the circuit is not used to access
21367 the outside world. This should help fix bug 1090. Bugfix on
21369 - Work around a small memory leak in some versions of OpenSSL that
21370 stopped the memory used by the hostname TLS extension from being
21374 - Add a "getinfo status/accepted-server-descriptor" controller
21375 command, which is the recommended way for controllers to learn
21376 whether our server descriptor has been successfully received by at
21377 least on directory authority. Un-recommend good-server-descriptor
21378 getinfo and status events until we have a better design for them.
21381 Changes in version 0.2.1.19 - 2009-07-28
21382 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
21386 - Make accessing hidden services on 0.2.1.x work right again.
21387 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
21388 part of patch provided by "optimist".
21391 - When a relay/bridge is writing out its identity key fingerprint to
21392 the "fingerprint" file and to its logs, write it without spaces. Now
21393 it will look like the fingerprints in our bridges documentation,
21394 and confuse fewer users.
21397 - Relays no longer publish a new server descriptor if they change
21398 their MaxAdvertisedBandwidth config option but it doesn't end up
21399 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
21400 fixes bug 1026. Patch from Sebastian.
21401 - Avoid leaking memory every time we get a create cell but we have
21402 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
21403 fixes bug 1034. Reported by BarkerJr.
21406 Changes in version 0.2.1.18 - 2009-07-24
21407 Tor 0.2.1.18 lays the foundations for performance improvements,
21408 adds status events to help users diagnose bootstrap problems, adds
21409 optional authentication/authorization for hidden services, fixes a
21410 variety of potential anonymity problems, and includes a huge pile of
21411 other features and bug fixes.
21413 o Major features (clients):
21414 - Start sending "bootstrap phase" status events to the controller,
21415 so it can keep the user informed of progress fetching directory
21416 information and establishing circuits. Also inform the controller
21417 if we think we're stuck at a particular bootstrap phase. Implements
21419 - Clients replace entry guards that were chosen more than a few months
21420 ago. This change should significantly improve client performance,
21421 especially once more people upgrade, since relays that have been
21422 a guard for a long time are currently overloaded.
21423 - Network status consensus documents and votes now contain bandwidth
21424 information for each relay. Clients use the bandwidth values
21425 in the consensus, rather than the bandwidth values in each
21426 relay descriptor. This approach opens the door to more accurate
21427 bandwidth estimates once the directory authorities start doing
21428 active measurements. Implements part of proposal 141.
21430 o Major features (relays):
21431 - Disable and refactor some debugging checks that forced a linear scan
21432 over the whole server-side DNS cache. These accounted for over 50%
21433 of CPU time on a relatively busy exit node's gprof profile. Also,
21434 disable some debugging checks that appeared in exit node profile
21435 data. Found by Jacob.
21436 - New DirPortFrontPage option that takes an html file and publishes
21437 it as "/" on the DirPort. Now relay operators can provide a
21438 disclaimer without needing to set up a separate webserver. There's
21439 a sample disclaimer in contrib/tor-exit-notice.html.
21441 o Major features (hidden services):
21442 - Make it possible to build hidden services that only certain clients
21443 are allowed to connect to. This is enforced at several points,
21444 so that unauthorized clients are unable to send INTRODUCE cells
21445 to the service, or even (depending on the type of authentication)
21446 to learn introduction points. This feature raises the bar for
21447 certain kinds of active attacks against hidden services. Design
21448 and code by Karsten Loesing. Implements proposal 121.
21449 - Relays now store and serve v2 hidden service descriptors by default,
21450 i.e., the new default value for HidServDirectoryV2 is 1. This is
21451 the last step in proposal 114, which aims to make hidden service
21452 lookups more reliable.
21454 o Major features (path selection):
21455 - ExitNodes and Exclude*Nodes config options now allow you to restrict
21456 by country code ("{US}") or IP address or address pattern
21457 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
21458 refinement to decide what config options should take priority if
21459 you ask to both use a particular node and exclude it.
21461 o Major features (misc):
21462 - When building a consensus, do not include routers that are down.
21463 This cuts down 30% to 40% on consensus size. Implements proposal
21465 - New TestingTorNetwork config option to allow adjustment of
21466 previously constant values that could slow bootstrapping. Implements
21467 proposal 135. Patch from Karsten.
21468 - Convert many internal address representations to optionally hold
21469 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
21470 elements. Make resolver code handle nameservers located at IPv6
21472 - More work on making our TLS handshake blend in: modify the list
21473 of ciphers advertised by OpenSSL in client mode to even more
21474 closely resemble a common web browser. We cheat a little so that
21475 we can advertise ciphers that the locally installed OpenSSL doesn't
21477 - Use the TLS1 hostname extension to more closely resemble browser
21480 o Security fixes (anonymity/entropy):
21481 - Never use a connection with a mismatched address to extend a
21482 circuit, unless that connection is canonical. A canonical
21483 connection is one whose address is authenticated by the router's
21484 identity key, either in a NETINFO cell or in a router descriptor.
21485 - Implement most of proposal 110: The first K cells to be sent
21486 along a circuit are marked as special "early" cells; only K "early"
21487 cells will be allowed. Once this code is universal, we can block
21488 certain kinds of denial-of-service attack by requiring that EXTEND
21489 commands must be sent using an "early" cell.
21490 - Resume using OpenSSL's RAND_poll() for better (and more portable)
21491 cross-platform entropy collection again. We used to use it, then
21492 stopped using it because of a bug that could crash systems that
21493 called RAND_poll when they had a lot of fds open. It looks like the
21494 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
21495 at startup, and to call RAND_poll() when we reseed later only if
21496 we have a non-buggy OpenSSL version.
21497 - When the client is choosing entry guards, now it selects at most
21498 one guard from a given relay family. Otherwise we could end up with
21499 all of our entry points into the network run by the same operator.
21500 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
21501 - Do not use or believe expired v3 authority certificates. Patch
21502 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
21503 - Drop begin cells to a hidden service if they come from the middle
21504 of a circuit. Patch from lark.
21505 - When we erroneously receive two EXTEND cells for the same circuit
21506 ID on the same connection, drop the second. Patch from lark.
21507 - Authorities now vote for the Stable flag for any router whose
21508 weighted MTBF is at least 5 days, regardless of the mean MTBF.
21509 - Clients now never report any stream end reason except 'MISC'.
21510 Implements proposal 148.
21512 o Major bugfixes (crashes):
21513 - Parse dates and IPv4 addresses in a locale- and libc-independent
21514 manner, to avoid platform-dependent behavior on malformed input.
21515 - Fix a crash that occurs on exit nodes when a nameserver request
21516 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
21517 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
21519 - Do not assume that a stack-allocated character array will be
21520 64-bit aligned on platforms that demand that uint64_t access is
21521 aligned. Possible fix for bug 604.
21522 - Resolve a very rare crash bug that could occur when the user forced
21523 a nameserver reconfiguration during the middle of a nameserver
21524 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
21525 - Avoid a "0 divided by 0" calculation when calculating router uptime
21526 at directory authorities. Bugfix on 0.2.0.8-alpha.
21527 - Fix an assertion bug in parsing policy-related options; possible fix
21529 - Rate-limit too-many-sockets messages: when they happen, they happen
21530 a lot and end up filling up the disk. Resolves bug 748.
21531 - Fix a race condition that could cause crashes or memory corruption
21532 when running as a server with a controller listening for log
21534 - Avoid crashing when we have a policy specified in a DirPolicy or
21535 SocksPolicy or ReachableAddresses option with ports set on it,
21536 and we re-load the policy. May fix bug 996.
21537 - Fix an assertion failure on 64-bit platforms when we allocated
21538 memory right up to the end of a memarea, then realigned the memory
21539 one step beyond the end. Fixes a possible cause of bug 930.
21540 - Protect the count of open sockets with a mutex, so we can't
21541 corrupt it when two threads are closing or opening sockets at once.
21542 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
21544 o Major bugfixes (clients):
21545 - Discard router descriptors as we load them if they are more than
21546 five days old. Otherwise if Tor is off for a long time and then
21547 starts with cached descriptors, it will try to use the onion keys
21548 in those obsolete descriptors when building circuits. Fixes bug 887.
21549 - When we choose to abandon a new entry guard because we think our
21550 older ones might be better, close any circuits pending on that
21551 new entry guard connection. This fix should make us recover much
21552 faster when our network is down and then comes back. Bugfix on
21553 0.1.2.8-beta; found by lodger.
21554 - When Tor clients restart after 1-5 days, they discard all their
21555 cached descriptors as too old, but they still use the cached
21556 consensus document. This approach is good for robustness, but
21557 bad for performance: since they don't know any bandwidths, they
21558 end up choosing at random rather than weighting their choice by
21559 speed. Fixed by the above feature of putting bandwidths in the
21562 o Major bugfixes (relays):
21563 - Relays were falling out of the networkstatus consensus for
21564 part of a day if they changed their local config but the
21565 authorities discarded their new descriptor as "not sufficiently
21566 different". Now directory authorities accept a descriptor as changed
21567 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
21568 patch by Sebastian.
21569 - Ensure that two circuits can never exist on the same connection
21570 with the same circuit ID, even if one is marked for close. This
21571 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
21572 - Directory authorities were neglecting to mark relays down in their
21573 internal histories if the relays fall off the routerlist without
21574 ever being found unreachable. So there were relays in the histories
21575 that haven't been seen for eight months, and are listed as being
21576 up for eight months. This wreaked havoc on the "median wfu" and
21577 "median mtbf" calculations, in turn making Guard and Stable flags
21578 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
21581 o Major bugfixes (hidden services):
21582 - When establishing a hidden service, introduction points that
21583 originate from cannibalized circuits were completely ignored
21584 and not included in rendezvous service descriptors. This might
21585 have been another reason for delay in making a hidden service
21586 available. Bugfix from long ago (0.0.9.x?)
21588 o Major bugfixes (memory and resource management):
21589 - Fixed some memory leaks -- some quite frequent, some almost
21590 impossible to trigger -- based on results from Coverity.
21591 - Speed up parsing and cut down on memory fragmentation by using
21592 stack-style allocations for parsing directory objects. Previously,
21593 this accounted for over 40% of allocations from within Tor's code
21594 on a typical directory cache.
21595 - Use a Bloom filter rather than a digest-based set to track which
21596 descriptors we need to keep around when we're cleaning out old
21597 router descriptors. This speeds up the computation significantly,
21598 and may reduce fragmentation.
21600 o New/changed config options:
21601 - Now NodeFamily and MyFamily config options allow spaces in
21602 identity fingerprints, so it's easier to paste them in.
21603 Suggested by Lucky Green.
21604 - Allow ports 465 and 587 in the default exit policy again. We had
21605 rejected them in 0.1.0.15, because back in 2005 they were commonly
21606 misconfigured and ended up as spam targets. We hear they are better
21607 locked down these days.
21608 - Make TrackHostExit mappings expire a while after their last use, not
21609 after their creation. Patch from Robert Hogan.
21610 - Add an ExcludeExitNodes option so users can list a set of nodes
21611 that should be be excluded from the exit node position, but
21612 allowed elsewhere. Implements proposal 151.
21613 - New --hush command-line option similar to --quiet. While --quiet
21614 disables all logging to the console on startup, --hush limits the
21615 output to messages of warning and error severity.
21616 - New configure/torrc options (--enable-geoip-stats,
21617 DirRecordUsageByCountry) to record how many IPs we've served
21618 directory info to in each country code, how many status documents
21619 total we've sent to each country code, and what share of the total
21620 directory requests we should expect to see.
21621 - Make outbound DNS packets respect the OutboundBindAddress setting.
21622 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
21623 - Allow separate log levels to be configured for different logging
21624 domains. For example, this allows one to log all notices, warnings,
21625 or errors, plus all memory management messages of level debug or
21626 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
21627 - Update to the "June 3 2009" ip-to-country file.
21629 o Minor features (relays):
21630 - Raise the minimum rate limiting to be a relay from 20000 bytes
21631 to 20480 bytes (aka 20KB/s), to match our documentation. Also
21632 update directory authorities so they always assign the Fast flag
21633 to relays with 20KB/s of capacity. Now people running relays won't
21634 suddenly find themselves not seeing any use, if the network gets
21636 - If we're a relay and we change our IP address, be more verbose
21637 about the reason that made us change. Should help track down
21638 further bugs for relays on dynamic IP addresses.
21639 - Exit servers can now answer resolve requests for ip6.arpa addresses.
21640 - Implement most of Proposal 152: allow specialized servers to permit
21641 single-hop circuits, and clients to use those servers to build
21642 single-hop circuits when using a specialized controller. Patch
21643 from Josh Albrecht. Resolves feature request 768.
21644 - When relays do their initial bandwidth measurement, don't limit
21645 to just our entry guards for the test circuits. Otherwise we tend
21646 to have multiple test circuits going through a single entry guard,
21647 which makes our bandwidth test less accurate. Fixes part of bug 654;
21648 patch contributed by Josh Albrecht.
21650 o Minor features (directory authorities):
21651 - Try not to open more than one descriptor-downloading connection
21652 to an authority at once. This should reduce load on directory
21653 authorities. Fixes bug 366.
21654 - Add cross-certification to newly generated certificates, so that
21655 a signing key is enough information to look up a certificate. Start
21656 serving certificates by <identity digest, signing key digest>
21657 pairs. Implements proposal 157.
21658 - When a directory authority downloads a descriptor that it then
21659 immediately rejects, do not retry downloading it right away. Should
21660 save some bandwidth on authorities. Fix for bug 888. Patch by
21662 - Directory authorities now serve a /tor/dbg-stability.txt URL to
21663 help debug WFU and MTBF calculations.
21664 - In directory authorities' approved-routers files, allow
21665 fingerprints with or without space.
21667 o Minor features (directory mirrors):
21668 - When a download gets us zero good descriptors, do not notify
21669 Tor that new directory information has arrived.
21670 - Servers support a new URL scheme for consensus downloads that
21671 allows the client to specify which authorities are trusted.
21672 The server then only sends the consensus if the client will trust
21673 it. Otherwise a 404 error is sent back. Clients use this
21674 new scheme when the server supports it (meaning it's running
21675 0.2.1.1-alpha or later). Implements proposal 134.
21677 o Minor features (bridges):
21678 - If the bridge config line doesn't specify a port, assume 443.
21679 This makes bridge lines a bit smaller and easier for users to
21681 - If we're using bridges and our network goes away, be more willing
21682 to forgive our bridges and try again when we get an application
21685 o Minor features (hidden services):
21686 - When the client launches an introduction circuit, retry with a
21687 new circuit after 30 seconds rather than 60 seconds.
21688 - Launch a second client-side introduction circuit in parallel
21689 after a delay of 15 seconds (based on work by Christian Wilms).
21690 - Hidden services start out building five intro circuits rather
21691 than three, and when the first three finish they publish a service
21692 descriptor using those. Now we publish our service descriptor much
21693 faster after restart.
21694 - Drop the requirement to have an open dir port for storing and
21695 serving v2 hidden service descriptors.
21697 o Minor features (build and packaging):
21698 - On Linux, use the prctl call to re-enable core dumps when the User
21700 - Try to make sure that the version of Libevent we're running with
21701 is binary-compatible with the one we built with. May address bug
21703 - Add a new --enable-local-appdata configuration switch to change
21704 the default location of the datadir on win32 from APPDATA to
21705 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
21706 entirely. Patch from coderman.
21707 - Build correctly against versions of OpenSSL 0.9.8 or later that
21708 are built without support for deprecated functions.
21709 - On platforms with a maximum syslog string length, truncate syslog
21710 messages to that length ourselves, rather than relying on the
21711 system to do it for us.
21712 - Automatically detect MacOSX versions earlier than 10.4.0, and
21713 disable kqueue from inside Tor when running with these versions.
21714 We previously did this from the startup script, but that was no
21715 help to people who didn't use the startup script. Resolves bug 863.
21716 - Build correctly when configured to build outside the main source
21717 path. Patch from Michael Gold.
21718 - Disable GCC's strict alias optimization by default, to avoid the
21719 likelihood of its introducing subtle bugs whenever our code violates
21720 the letter of C99's alias rules.
21721 - Change the contrib/tor.logrotate script so it makes the new
21722 logs as "_tor:_tor" rather than the default, which is generally
21723 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
21724 - Change our header file guard macros to be less likely to conflict
21725 with system headers. Adam Langley noticed that we were conflicting
21726 with log.h on Android.
21727 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
21728 and stop using a warning that had become unfixably verbose under
21730 - Use a lockfile to make sure that two Tor processes are not
21731 simultaneously running with the same datadir.
21732 - Allow OpenSSL to use dynamic locks if it wants.
21733 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
21735 o Minor features (controllers):
21736 - When generating circuit events with verbose nicknames for
21737 controllers, try harder to look up nicknames for routers on a
21738 circuit. (Previously, we would look in the router descriptors we had
21739 for nicknames, but not in the consensus.) Partial fix for bug 941.
21740 - New controller event NEWCONSENSUS that lists the networkstatus
21741 lines for every recommended relay. Now controllers like Torflow
21742 can keep up-to-date on which relays they should be using.
21743 - New controller event "clients_seen" to report a geoip-based summary
21744 of which countries we've seen clients from recently. Now controllers
21745 like Vidalia can show bridge operators that they're actually making
21747 - Add a 'getinfo status/clients-seen' controller command, in case
21748 controllers want to hear clients_seen events but connect late.
21749 - New CONSENSUS_ARRIVED event to note when a new consensus has
21750 been fetched and validated.
21751 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
21752 controllers to prevent SIGHUP from reloading the configuration.
21754 - Return circuit purposes in response to GETINFO circuit-status.
21756 - Serve the latest v3 networkstatus consensus via the control
21757 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
21758 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
21759 controller can query our current bootstrap state in case it attaches
21760 partway through and wants to catch up.
21761 - Provide circuit purposes along with circuit events to the controller.
21763 o Minor features (tools):
21764 - Do not have tor-resolve automatically refuse all .onion addresses;
21765 if AutomapHostsOnResolve is set in your torrc, this will work fine.
21766 - Add a -p option to tor-resolve for specifying the SOCKS port: some
21767 people find host:port too confusing.
21768 - Print the SOCKS5 error message string as well as the error code
21769 when a tor-resolve request fails. Patch from Jacob.
21771 o Minor bugfixes (memory and resource management):
21772 - Clients no longer cache certificates for authorities they do not
21773 recognize. Bugfix on 0.2.0.9-alpha.
21774 - Do not use C's stdio library for writing to log files. This will
21775 improve logging performance by a minute amount, and will stop
21776 leaking fds when our disk is full. Fixes bug 861.
21777 - Stop erroneous use of O_APPEND in cases where we did not in fact
21778 want to re-seek to the end of a file before every last write().
21779 - Fix a small alignment and memory-wasting bug on buffer chunks.
21781 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
21782 to avoid unused RAM in buffer chunks and memory pools.
21783 - Reduce the default smartlist size from 32 to 16; it turns out that
21784 most smartlists hold around 8-12 elements tops.
21785 - Make dumpstats() log the fullness and size of openssl-internal
21787 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
21788 patch to their OpenSSL, turn it on to save memory on servers. This
21789 patch will (with any luck) get included in a mainline distribution
21791 - Fix a memory leak when v3 directory authorities load their keys
21792 and cert from disk. Bugfix on 0.2.0.1-alpha.
21793 - Stop using malloc_usable_size() to use more area than we had
21794 actually allocated: it was safe, but made valgrind really unhappy.
21795 - Make the assert_circuit_ok() function work correctly on circuits that
21796 have already been marked for close.
21797 - Fix uninitialized size field for memory area allocation: may improve
21798 memory performance during directory parsing.
21800 o Minor bugfixes (clients):
21801 - Stop reloading the router list from disk for no reason when we
21802 run out of reachable directory mirrors. Once upon a time reloading
21803 it would set the 'is_running' flag back to 1 for them. It hasn't
21804 done that for a long time.
21805 - When we had picked an exit node for a connection, but marked it as
21806 "optional", and it turned out we had no onion key for the exit,
21807 stop wanting that exit and try again. This situation may not
21808 be possible now, but will probably become feasible with proposal
21809 158. Spotted by rovv. Fixes another case of bug 752.
21810 - Fix a bug in address parsing that was preventing bridges or hidden
21811 service targets from being at IPv6 addresses.
21812 - Do not remove routers as too old if we do not have any consensus
21813 document. Bugfix on 0.2.0.7-alpha.
21814 - When an exit relay resolves a stream address to a local IP address,
21815 do not just keep retrying that same exit relay over and
21816 over. Instead, just close the stream. Addresses bug 872. Bugfix
21817 on 0.2.0.32. Patch from rovv.
21818 - Made Tor a little less aggressive about deleting expired
21819 certificates. Partial fix for bug 854.
21820 - Treat duplicate certificate fetches as failures, so that we do
21821 not try to re-fetch an expired certificate over and over and over.
21822 - Do not say we're fetching a certificate when we'll in fact skip it
21823 because of a pending download.
21824 - If we have correct permissions on $datadir, we complain to stdout
21825 and fail to start. But dangerous permissions on
21826 $datadir/cached-status/ would cause us to open a log and complain
21827 there. Now complain to stdout and fail to start in both cases. Fixes
21828 bug 820, reported by seeess.
21830 o Minor bugfixes (bridges):
21831 - When we made bridge authorities stop serving bridge descriptors over
21832 unencrypted links, we also broke DirPort reachability testing for
21833 bridges. So bridges with a non-zero DirPort were printing spurious
21834 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
21835 - Don't allow a bridge to publish its router descriptor to a
21836 non-bridge directory authority. Fixes part of bug 932.
21837 - When we change to or from being a bridge, reset our counts of
21838 client usage by country. Fixes bug 932.
21840 o Minor bugfixes (relays):
21841 - Log correct error messages for DNS-related network errors on
21843 - Actually return -1 in the error case for read_bandwidth_usage().
21844 Harmless bug, since we currently don't care about the return value
21845 anywhere. Bugfix on 0.2.0.9-alpha.
21846 - Provide a more useful log message if bug 977 (related to buffer
21847 freelists) ever reappears, and do not crash right away.
21848 - We were already rejecting relay begin cells with destination port
21849 of 0. Now also reject extend cells with destination port or address
21850 of 0. Suggested by lark.
21851 - When we can't transmit a DNS request due to a network error, retry
21852 it after a while, and eventually transmit a failing response to
21853 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
21854 - Solve a bug that kept hardware crypto acceleration from getting
21855 enabled when accounting was turned on. Fixes bug 907. Bugfix on
21857 - When a canonical connection appears later in our internal list
21858 than a noncanonical one for a given OR ID, always use the
21859 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
21861 - Avoid some nasty corner cases in the logic for marking connections
21862 as too old or obsolete or noncanonical for circuits. Partial
21864 - Fix another interesting corner-case of bug 891 spotted by rovv:
21865 Previously, if two hosts had different amounts of clock drift, and
21866 one of them created a new connection with just the wrong timing,
21867 the other might decide to deprecate the new connection erroneously.
21868 Bugfix on 0.1.1.13-alpha.
21869 - If one win32 nameserver fails to get added, continue adding the
21870 rest, and don't automatically fail.
21871 - Fix a bug where an unreachable relay would establish enough
21872 reachability testing circuits to do a bandwidth test -- if
21873 we already have a connection to the middle hop of the testing
21874 circuit, then it could establish the last hop by using the existing
21875 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
21876 circuits no longer use entry guards in 0.2.1.3-alpha.
21878 o Minor bugfixes (directory authorities):
21879 - Limit uploaded directory documents to be 16M rather than 500K.
21880 The directory authorities were refusing v3 consensus votes from
21881 other authorities, since the votes are now 504K. Fixes bug 959;
21882 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
21883 - Directory authorities should never send a 503 "busy" response to
21884 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
21886 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
21887 headers. Bugfix on 0.2.0.10-alpha.
21889 o Minor bugfixes (hidden services):
21890 - When we can't find an intro key for a v2 hidden service descriptor,
21891 fall back to the v0 hidden service descriptor and log a bug message.
21892 Workaround for bug 1024.
21893 - In very rare situations new hidden service descriptors were
21894 published earlier than 30 seconds after the last change to the
21895 service. (We currently think that a hidden service descriptor
21896 that's been stable for 30 seconds is worth publishing.)
21897 - If a hidden service sends us an END cell, do not consider
21898 retrying the connection; just close it. Patch from rovv.
21899 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
21900 service directories if they have no advertised dir port. Bugfix
21903 o Minor bugfixes (tools):
21904 - In the torify(1) manpage, mention that tsocks will leak your
21907 o Minor bugfixes (controllers):
21908 - If the controller claimed responsibility for a stream, but that
21909 stream never finished making its connection, it would live
21910 forever in circuit_wait state. Now we close it after SocksTimeout
21911 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
21912 - Make DNS resolved controller events into "CLOSED", not
21913 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
21915 - The control port would close the connection before flushing long
21916 replies, such as the network consensus, if a QUIT command was issued
21917 before the reply had completed. Now, the control port flushes all
21918 pending replies before closing the connection. Also fix a spurious
21919 warning when a QUIT command is issued after a malformed or rejected
21920 AUTHENTICATE command, but before the connection was closed. Patch
21921 by Marcus Griep. Fixes bugs 1015 and 1016.
21922 - Fix a bug that made stream bandwidth get misreported to the
21925 o Deprecated and removed features:
21926 - The old "tor --version --version" command, which would print out
21927 the subversion "Id" of most of the source files, is now removed. It
21928 turned out to be less useful than we'd expected, and harder to
21930 - RedirectExits has been removed. It was deprecated since
21932 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
21933 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
21934 - Cell pools are now always enabled; --disable-cell-pools is ignored.
21935 - Directory mirrors no longer fetch the v1 directory or
21936 running-routers files. They are obsolete, and nobody asks for them
21937 anymore. This is the first step to making v1 authorities obsolete.
21938 - Take out the TestVia config option, since it was a workaround for
21939 a bug that was fixed in Tor 0.1.1.21.
21940 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
21941 HiddenServiceExcludeNodes as obsolete: they never worked properly,
21942 and nobody seems to be using them. Fixes bug 754. Bugfix on
21943 0.1.0.1-rc. Patch from Christian Wilms.
21944 - Remove all backward-compatibility code for relays running
21945 versions of Tor so old that they no longer work at all on the
21948 o Code simplifications and refactoring:
21949 - Tool-assisted documentation cleanup. Nearly every function or
21950 static variable in Tor should have its own documentation now.
21951 - Rename the confusing or_is_obsolete field to the more appropriate
21952 is_bad_for_new_circs, and move it to or_connection_t where it
21954 - Move edge-only flags from connection_t to edge_connection_t: not
21955 only is this better coding, but on machines of plausible alignment,
21956 it should save 4-8 bytes per connection_t. "Every little bit helps."
21957 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
21958 for consistency; keep old option working for backward compatibility.
21959 - Simplify the code for finding connections to use for a circuit.
21960 - Revise the connection_new functions so that a more typesafe variant
21961 exists. This will work better with Coverity, and let us find any
21962 actual mistakes we're making here.
21963 - Refactor unit testing logic so that dmalloc can be used sensibly
21964 with unit tests to check for memory leaks.
21965 - Move all hidden-service related fields from connection and circuit
21966 structure to substructures: this way they won't eat so much memory.
21967 - Squeeze 2-5% out of client performance (according to oprofile) by
21968 improving the implementation of some policy-manipulation functions.
21969 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
21970 be more efficient. Formerly it was quadratic in the number of
21971 servers; now it should be linear. Fixes bug 509.
21972 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
21973 and n_conn_id_digest fields into a separate structure that's
21974 only needed when the circuit has not yet attached to an n_conn.
21975 - Optimize out calls to time(NULL) that occur for every IO operation,
21976 or for every cell. On systems like Windows where time() is a
21977 slow syscall, this fix will be slightly helpful.
21980 Changes in version 0.2.0.35 - 2009-06-24
21982 - Avoid crashing in the presence of certain malformed descriptors.
21983 Found by lark, and by automated fuzzing.
21984 - Fix an edge case where a malicious exit relay could convince a
21985 controller that the client's DNS question resolves to an internal IP
21986 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
21989 - Finally fix the bug where dynamic-IP relays disappear when their
21990 IP address changes: directory mirrors were mistakenly telling
21991 them their old address if they asked via begin_dir, so they
21992 never got an accurate answer about their new address, so they
21993 just vanished after a day. For belt-and-suspenders, relays that
21994 don't set Address in their config now avoid using begin_dir for
21995 all direct connections. Should fix bugs 827, 883, and 900.
21996 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
21997 that would occur on some exit nodes when DNS failures and timeouts
21998 occurred in certain patterns. Fix for bug 957.
22001 - When starting with a cache over a few days old, do not leak
22002 memory for the obsolete router descriptors in it. Bugfix on
22003 0.2.0.33; fixes bug 672.
22004 - Hidden service clients didn't use a cached service descriptor that
22005 was older than 15 minutes, but wouldn't fetch a new one either,
22006 because there was already one in the cache. Now, fetch a v2
22007 descriptor unless the same descriptor was added to the cache within
22008 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
22011 Changes in version 0.2.0.34 - 2009-02-08
22012 Tor 0.2.0.34 features several more security-related fixes. You should
22013 upgrade, especially if you run an exit relay (remote crash) or a
22014 directory authority (remote infinite loop), or you're on an older
22015 (pre-XP) or not-recently-patched Windows (remote exploit).
22017 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
22018 have many known flaws, and nobody should be using them. You should
22019 upgrade. If you're using a Linux or BSD and its packages are obsolete,
22020 stop using those packages and upgrade anyway.
22023 - Fix an infinite-loop bug on handling corrupt votes under certain
22024 circumstances. Bugfix on 0.2.0.8-alpha.
22025 - Fix a temporary DoS vulnerability that could be performed by
22026 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
22027 - Avoid a potential crash on exit nodes when processing malformed
22028 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
22029 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
22030 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
22033 - Fix compilation on systems where time_t is a 64-bit integer.
22034 Patch from Matthias Drochner.
22035 - Don't consider expiring already-closed client connections. Fixes
22036 bug 893. Bugfix on 0.0.2pre20.
22039 Changes in version 0.2.0.33 - 2009-01-21
22040 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
22041 useful to users. It also finally fixes a bug where a relay or client
22042 that's been off for many days would take a long time to bootstrap.
22044 This update also fixes an important security-related bug reported by
22045 Ilja van Sprundel. You should upgrade. (We'll send out more details
22046 about the bug once people have had some time to upgrade.)
22049 - Fix a heap-corruption bug that may be remotely triggerable on
22050 some platforms. Reported by Ilja van Sprundel.
22053 - When a stream at an exit relay is in state "resolving" or
22054 "connecting" and it receives an "end" relay cell, the exit relay
22055 would silently ignore the end cell and not close the stream. If
22056 the client never closes the circuit, then the exit relay never
22057 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
22058 reported by "wood".
22059 - When sending CREATED cells back for a given circuit, use a 64-bit
22060 connection ID to find the right connection, rather than an addr:port
22061 combination. Now that we can have multiple OR connections between
22062 the same ORs, it is no longer possible to use addr:port to uniquely
22063 identify a connection.
22064 - Bridge relays that had DirPort set to 0 would stop fetching
22065 descriptors shortly after startup, and then briefly resume
22066 after a new bandwidth test and/or after publishing a new bridge
22067 descriptor. Bridge users that try to bootstrap from them would
22068 get a recent networkstatus but would get descriptors from up to
22069 18 hours earlier, meaning most of the descriptors were obsolete
22070 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
22071 - Prevent bridge relays from serving their 'extrainfo' document
22072 to anybody who asks, now that extrainfo docs include potentially
22073 sensitive aggregated client geoip summaries. Bugfix on
22075 - If the cached networkstatus consensus is more than five days old,
22076 discard it rather than trying to use it. In theory it could be
22077 useful because it lists alternate directory mirrors, but in practice
22078 it just means we spend many minutes trying directory mirrors that
22079 are long gone from the network. Also discard router descriptors as
22080 we load them if they are more than five days old, since the onion
22081 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
22084 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
22085 could make gcc generate non-functional binary search code. Bugfix
22087 - Build correctly on platforms without socklen_t.
22088 - Compile without warnings on solaris.
22089 - Avoid potential crash on internal error during signature collection.
22090 Fixes bug 864. Patch from rovv.
22091 - Correct handling of possible malformed authority signing key
22092 certificates with internal signature types. Fixes bug 880.
22093 Bugfix on 0.2.0.3-alpha.
22094 - Fix a hard-to-trigger resource leak when logging credential status.
22096 - When we can't initialize DNS because the network is down, do not
22097 automatically stop Tor from starting. Instead, we retry failed
22098 dns_init() every 10 minutes, and change the exit policy to reject
22099 *:* until one succeeds. Fixes bug 691.
22100 - Use 64 bits instead of 32 bits for connection identifiers used with
22101 the controller protocol, to greatly reduce risk of identifier reuse.
22102 - When we're choosing an exit node for a circuit, and we have
22103 no pending streams, choose a good general exit rather than one that
22104 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
22105 - Fix another case of assuming, when a specific exit is requested,
22106 that we know more than the user about what hosts it allows.
22107 Fixes one case of bug 752. Patch from rovv.
22108 - Clip the MaxCircuitDirtiness config option to a minimum of 10
22109 seconds. Warn the user if lower values are given in the
22110 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
22111 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
22112 user if lower values are given in the configuration. Bugfix on
22113 0.1.1.17-rc. Patch by Sebastian.
22114 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
22115 the cache because we already had a v0 descriptor with the same ID.
22116 Bugfix on 0.2.0.18-alpha.
22117 - Fix a race condition when freeing keys shared between main thread
22118 and CPU workers that could result in a memory leak. Bugfix on
22119 0.1.0.1-rc. Fixes bug 889.
22120 - Send a valid END cell back when a client tries to connect to a
22121 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
22122 840. Patch from rovv.
22123 - Check which hops rendezvous stream cells are associated with to
22124 prevent possible guess-the-streamid injection attacks from
22125 intermediate hops. Fixes another case of bug 446. Based on patch
22127 - If a broken client asks a non-exit router to connect somewhere,
22128 do not even do the DNS lookup before rejecting the connection.
22129 Fixes another case of bug 619. Patch from rovv.
22130 - When a relay gets a create cell it can't decrypt (e.g. because it's
22131 using the wrong onion key), we were dropping it and letting the
22132 client time out. Now actually answer with a destroy cell. Fixes
22133 bug 904. Bugfix on 0.0.2pre8.
22135 o Minor bugfixes (hidden services):
22136 - Do not throw away existing introduction points on SIGHUP. Bugfix on
22137 0.0.6pre1. Patch by Karsten. Fixes bug 874.
22140 - Report the case where all signatures in a detached set are rejected
22141 differently than the case where there is an error handling the
22143 - When we realize that another process has modified our cached
22144 descriptors, print out a more useful error message rather than
22145 triggering an assertion. Fixes bug 885. Patch from Karsten.
22146 - Implement the 0x20 hack to better resist DNS poisoning: set the
22147 case on outgoing DNS requests randomly, and reject responses that do
22148 not match the case correctly. This logic can be disabled with the
22149 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
22150 of servers that do not reliably preserve case in replies. See
22151 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
22153 - Check DNS replies for more matching fields to better resist DNS
22155 - Never use OpenSSL compression: it wastes RAM and CPU trying to
22156 compress cells, which are basically all encrypted, compressed, or
22160 Changes in version 0.2.0.32 - 2008-11-20
22161 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
22162 packages (and maybe other packages) noticed by Theo de Raadt, fixes
22163 a smaller security flaw that might allow an attacker to access local
22164 services, further improves hidden service performance, and fixes a
22165 variety of other issues.
22168 - The "User" and "Group" config options did not clear the
22169 supplementary group entries for the Tor process. The "User" option
22170 is now more robust, and we now set the groups to the specified
22171 user's primary group. The "Group" option is now ignored. For more
22172 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
22173 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
22174 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
22175 - The "ClientDNSRejectInternalAddresses" config option wasn't being
22176 consistently obeyed: if an exit relay refuses a stream because its
22177 exit policy doesn't allow it, we would remember what IP address
22178 the relay said the destination address resolves to, even if it's
22179 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
22182 - Fix a DOS opportunity during the voting signature collection process
22183 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
22185 o Major bugfixes (hidden services):
22186 - When fetching v0 and v2 rendezvous service descriptors in parallel,
22187 we were failing the whole hidden service request when the v0
22188 descriptor fetch fails, even if the v2 fetch is still pending and
22189 might succeed. Similarly, if the last v2 fetch fails, we were
22190 failing the whole hidden service request even if a v0 fetch is
22191 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
22192 - When extending a circuit to a hidden service directory to upload a
22193 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
22194 requests failed, because the router descriptor has not been
22195 downloaded yet. In these cases, do not attempt to upload the
22196 rendezvous descriptor, but wait until the router descriptor is
22197 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
22198 descriptor from a hidden service directory for which the router
22199 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
22203 - Fix several infrequent memory leaks spotted by Coverity.
22204 - When testing for libevent functions, set the LDFLAGS variable
22205 correctly. Found by Riastradh.
22206 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
22207 bootstrapping with tunneled directory connections. Bugfix on
22208 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
22209 - When asked to connect to A.B.exit:80, if we don't know the IP for A
22210 and we know that server B rejects most-but-not all connections to
22211 port 80, we would previously reject the connection. Now, we assume
22212 the user knows what they were asking for. Fixes bug 752. Bugfix
22213 on 0.0.9rc5. Diagnosed by BarkerJr.
22214 - If we overrun our per-second write limits a little, count this as
22215 having used up our write allocation for the second, and choke
22216 outgoing directory writes. Previously, we had only counted this when
22217 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
22218 Bugfix on 0.2.0.x (??).
22219 - Remove the old v2 directory authority 'lefkada' from the default
22220 list. It has been gone for many months.
22221 - Stop doing unaligned memory access that generated bus errors on
22222 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
22223 - Make USR2 log-level switch take effect immediately. Bugfix on
22226 o Minor bugfixes (controller):
22227 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
22228 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
22231 Changes in version 0.2.0.31 - 2008-09-03
22232 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
22233 a big bug we're seeing where in rare cases traffic from one Tor stream
22234 gets mixed into another stream, and fixes a variety of smaller issues.
22237 - Make sure that two circuits can never exist on the same connection
22238 with the same circuit ID, even if one is marked for close. This
22239 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
22240 - Relays now reject risky extend cells: if the extend cell includes
22241 a digest of all zeroes, or asks to extend back to the relay that
22242 sent the extend cell, tear down the circuit. Ideas suggested
22244 - If not enough of our entry guards are available so we add a new
22245 one, we might use the new one even if it overlapped with the
22246 current circuit's exit relay (or its family). Anonymity bugfix
22247 pointed out by rovv.
22250 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
22251 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
22252 - Correctly detect the presence of the linux/netfilter_ipv4.h header
22253 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
22254 - Pick size of default geoip filename string correctly on windows.
22255 Fixes bug 806. Bugfix on 0.2.0.30.
22256 - Make the autoconf script accept the obsolete --with-ssl-dir
22257 option as an alias for the actually-working --with-openssl-dir
22258 option. Fix the help documentation to recommend --with-openssl-dir.
22259 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
22260 - When using the TransPort option on OpenBSD, and using the User
22261 option to change UID and drop privileges, make sure to open
22262 /dev/pf before dropping privileges. Fixes bug 782. Patch from
22263 Christopher Davis. Bugfix on 0.1.2.1-alpha.
22264 - Try to attach connections immediately upon receiving a RENDEZVOUS2
22265 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
22266 on the client side when connecting to a hidden service. Bugfix
22267 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
22268 - When closing an application-side connection because its circuit is
22269 getting torn down, generate the stream event correctly. Bugfix on
22270 0.1.2.x. Anonymous patch.
22273 Changes in version 0.2.0.30 - 2008-07-15
22274 This new stable release switches to a more efficient directory
22275 distribution design, adds features to make connections to the Tor
22276 network harder to block, allows Tor to act as a DNS proxy, adds separate
22277 rate limiting for relayed traffic to make it easier for clients to
22278 become relays, fixes a variety of potential anonymity problems, and
22279 includes the usual huge pile of other features and bug fixes.
22281 o New v3 directory design:
22282 - Tor now uses a new way to learn about and distribute information
22283 about the network: the directory authorities vote on a common
22284 network status document rather than each publishing their own
22285 opinion. Now clients and caches download only one networkstatus
22286 document to bootstrap, rather than downloading one for each
22287 authority. Clients only download router descriptors listed in
22288 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
22290 - Set up moria1, tor26, and dizum as v3 directory authorities
22291 in addition to being v2 authorities. Also add three new ones:
22292 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
22293 dannenberg (run by CCC).
22294 - Switch to multi-level keys for directory authorities: now their
22295 long-term identity key can be kept offline, and they periodically
22296 generate a new signing key. Clients fetch the "key certificates"
22297 to keep up to date on the right keys. Add a standalone tool
22298 "tor-gencert" to generate key certificates. Implements proposal 103.
22299 - Add a new V3AuthUseLegacyKey config option to make it easier for
22300 v3 authorities to change their identity keys if another bug like
22301 Debian's OpenSSL RNG flaw appears.
22302 - Authorities and caches fetch the v2 networkstatus documents
22303 less often, now that v3 is recommended.
22305 o Make Tor connections stand out less on the wire:
22306 - Use an improved TLS handshake designed by Steven Murdoch in proposal
22307 124, as revised in proposal 130. The new handshake is meant to
22308 be harder for censors to fingerprint, and it adds the ability
22309 to detect certain kinds of man-in-the-middle traffic analysis
22310 attacks. The new handshake format includes version negotiation for
22311 OR connections as described in proposal 105, which will allow us
22312 to improve Tor's link protocol more safely in the future.
22313 - Enable encrypted directory connections by default for non-relays,
22314 so censor tools that block Tor directory connections based on their
22315 plaintext patterns will no longer work. This means Tor works in
22316 certain censored countries by default again.
22317 - Stop including recognizeable strings in the commonname part of
22318 Tor's x509 certificates.
22320 o Implement bridge relays:
22321 - Bridge relays (or "bridges" for short) are Tor relays that aren't
22322 listed in the main Tor directory. Since there is no complete public
22323 list of them, even an ISP that is filtering connections to all the
22324 known Tor relays probably won't be able to block all the bridges.
22325 See doc/design-paper/blocking.pdf and proposal 125 for details.
22326 - New config option BridgeRelay that specifies you want to be a
22327 bridge relay rather than a normal relay. When BridgeRelay is set
22328 to 1, then a) you cache dir info even if your DirPort ins't on,
22329 and b) the default for PublishServerDescriptor is now "bridge"
22330 rather than "v2,v3".
22331 - New config option "UseBridges 1" for clients that want to use bridge
22332 relays instead of ordinary entry guards. Clients then specify
22333 bridge relays by adding "Bridge" lines to their config file. Users
22334 can learn about a bridge relay either manually through word of
22335 mouth, or by one of our rate-limited mechanisms for giving out
22336 bridge addresses without letting an attacker easily enumerate them
22337 all. See https://www.torproject.org/bridges for details.
22338 - Bridge relays behave like clients with respect to time intervals
22339 for downloading new v3 consensus documents -- otherwise they
22340 stand out. Bridge users now wait until the end of the interval,
22341 so their bridge relay will be sure to have a new consensus document.
22343 o Implement bridge directory authorities:
22344 - Bridge authorities are like normal directory authorities, except
22345 they don't serve a list of known bridges. Therefore users that know
22346 a bridge's fingerprint can fetch a relay descriptor for that bridge,
22347 including fetching updates e.g. if the bridge changes IP address,
22348 yet an attacker can't just fetch a list of all the bridges.
22349 - Set up Tonga as the default bridge directory authority.
22350 - Bridge authorities refuse to serve bridge descriptors or other
22351 bridge information over unencrypted connections (that is, when
22352 responding to direct DirPort requests rather than begin_dir cells.)
22353 - Bridge directory authorities do reachability testing on the
22354 bridges they know. They provide router status summaries to the
22355 controller via "getinfo ns/purpose/bridge", and also dump summaries
22356 to a file periodically, so we can keep internal stats about which
22357 bridges are functioning.
22358 - If bridge users set the UpdateBridgesFromAuthority config option,
22359 but the digest they ask for is a 404 on the bridge authority,
22360 they fall back to contacting the bridge directly.
22361 - Bridges always use begin_dir to publish their server descriptor to
22362 the bridge authority using an anonymous encrypted tunnel.
22363 - Early work on a "bridge community" design: if bridge authorities set
22364 the BridgePassword config option, they will serve a snapshot of
22365 known bridge routerstatuses from their DirPort to anybody who
22366 knows that password. Unset by default.
22367 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
22368 report sanitized aggregated summaries in their extra-info documents
22369 privately to the bridge authority, listing which countries are
22370 able to reach them. We hope this mechanism will let us learn when
22371 certain countries start trying to block bridges.
22372 - Bridge authorities write bridge descriptors to disk, so they can
22373 reload them after a reboot. They can also export the descriptors
22374 to other programs, so we can distribute them to blocked users via
22375 the BridgeDB interface, e.g. via https://bridges.torproject.org/
22376 and bridges@torproject.org.
22378 o Tor can be a DNS proxy:
22379 - The new client-side DNS proxy feature replaces the need for
22380 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
22381 for DNS requests on port 9999, use the Tor network to resolve them
22382 anonymously, and send the reply back like a regular DNS server.
22383 The code still only implements a subset of DNS.
22384 - Add a new AutomapHostsOnResolve option: when it is enabled, any
22385 resolve request for hosts matching a given pattern causes Tor to
22386 generate an internal virtual address mapping for that host. This
22387 allows DNSPort to work sensibly with hidden service users. By
22388 default, .exit and .onion addresses are remapped; the list of
22389 patterns can be reconfigured with AutomapHostsSuffixes.
22390 - Add an "-F" option to tor-resolve to force a resolve for a .onion
22391 address. Thanks to the AutomapHostsOnResolve option, this is no
22392 longer a completely silly thing to do.
22394 o Major features (relay usability):
22395 - New config options RelayBandwidthRate and RelayBandwidthBurst:
22396 a separate set of token buckets for relayed traffic. Right now
22397 relayed traffic is defined as answers to directory requests, and
22398 OR connections that don't have any local circuits on them. See
22399 proposal 111 for details.
22400 - Create listener connections before we setuid to the configured
22401 User and Group. Now non-Windows users can choose port values
22402 under 1024, start Tor as root, and have Tor bind those ports
22403 before it changes to another UID. (Windows users could already
22405 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
22406 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
22407 on "vserver" accounts. Patch from coderman.
22409 o Major features (directory authorities):
22410 - Directory authorities track weighted fractional uptime and weighted
22411 mean-time-between failures for relays. WFU is suitable for deciding
22412 whether a node is "usually up", while MTBF is suitable for deciding
22413 whether a node is "likely to stay up." We need both, because
22414 "usually up" is a good requirement for guards, while "likely to
22415 stay up" is a good requirement for long-lived connections.
22416 - Directory authorities use a new formula for selecting which relays
22417 to advertise as Guards: they must be in the top 7/8 in terms of
22418 how long we have known about them, and above the median of those
22419 nodes in terms of weighted fractional uptime.
22420 - Directory authorities use a new formula for selecting which relays
22421 to advertise as Stable: when we have 4 or more days of data, use
22422 median measured MTBF rather than median declared uptime. Implements
22424 - Directory authorities accept and serve "extra info" documents for
22425 routers. Routers now publish their bandwidth-history lines in the
22426 extra-info docs rather than the main descriptor. This step saves
22427 60% (!) on compressed router descriptor downloads. Servers upload
22428 extra-info docs to any authority that accepts them; directory
22429 authorities now allow multiple router descriptors and/or extra
22430 info documents to be uploaded in a single go. Authorities, and
22431 caches that have been configured to download extra-info documents,
22432 download them as needed. Implements proposal 104.
22433 - Authorities now list relays who have the same nickname as
22434 a different named relay, but list them with a new flag:
22435 "Unnamed". Now we can make use of relays that happen to pick the
22436 same nickname as a server that registered two years ago and then
22437 disappeared. Implements proposal 122.
22438 - Store routers in a file called cached-descriptors instead of in
22439 cached-routers. Initialize cached-descriptors from cached-routers
22440 if the old format is around. The new format allows us to store
22441 annotations along with descriptors, to record the time we received
22442 each descriptor, its source, and its purpose: currently one of
22443 general, controller, or bridge.
22445 o Major features (other):
22446 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
22447 Tor can warn and/or refuse connections to ports commonly used with
22448 vulnerable-plaintext protocols. Currently we warn on ports 23,
22449 109, 110, and 143, but we don't reject any. Based on proposal 129
22450 by Kevin Bauer and Damon McCoy.
22451 - Integrate Karsten Loesing's Google Summer of Code project to publish
22452 hidden service descriptors on a set of redundant relays that are a
22453 function of the hidden service address. Now we don't have to rely
22454 on three central hidden service authorities for publishing and
22455 fetching every hidden service descriptor. Implements proposal 114.
22456 - Allow tunnelled directory connections to ask for an encrypted
22457 "begin_dir" connection or an anonymized "uses a full Tor circuit"
22458 connection independently. Now we can make anonymized begin_dir
22459 connections for (e.g.) more secure hidden service posting and
22462 o Major bugfixes (crashes and assert failures):
22463 - Stop imposing an arbitrary maximum on the number of file descriptors
22464 used for busy servers. Bug reported by Olaf Selke; patch from
22466 - Avoid possible failures when generating a directory with routers
22467 with over-long versions strings, or too many flags set.
22468 - Fix a rare assert error when we're closing one of our threads:
22469 use a mutex to protect the list of logs, so we never write to the
22470 list as it's being freed. Fixes the very rare bug 575, which is
22471 kind of the revenge of bug 222.
22472 - Avoid segfault in the case where a badly behaved v2 versioning
22473 directory sends a signed networkstatus with missing client-versions.
22474 - When we hit an EOF on a log (probably because we're shutting down),
22475 don't try to remove the log from the list: just mark it as
22476 unusable. (Bulletproofs against bug 222.)
22478 o Major bugfixes (code security fixes):
22479 - Detect size overflow in zlib code. Reported by Justin Ferguson and
22481 - Rewrite directory tokenization code to never run off the end of
22482 a string. Fixes bug 455. Patch from croup.
22483 - Be more paranoid about overwriting sensitive memory on free(),
22484 as a defensive programming tactic to ensure forward secrecy.
22486 o Major bugfixes (anonymity fixes):
22487 - Reject requests for reverse-dns lookup of names that are in
22488 a private address space. Patch from lodger.
22489 - Never report that we've used more bandwidth than we're willing to
22490 relay: it leaks how much non-relay traffic we're using. Resolves
22492 - As a client, do not believe any server that tells us that an
22493 address maps to an internal address space.
22494 - Warn about unsafe ControlPort configurations.
22495 - Directory authorities now call routers Fast if their bandwidth is
22496 at least 100KB/s, and consider their bandwidth adequate to be a
22497 Guard if it is at least 250KB/s, no matter the medians. This fix
22498 complements proposal 107.
22499 - Directory authorities now never mark more than 2 servers per IP as
22500 Valid and Running (or 5 on addresses shared by authorities).
22501 Implements proposal 109, by Kevin Bauer and Damon McCoy.
22502 - If we're a relay, avoid picking ourselves as an introduction point,
22503 a rendezvous point, or as the final hop for internal circuits. Bug
22504 reported by taranis and lodger.
22505 - Exit relays that are used as a client can now reach themselves
22506 using the .exit notation, rather than just launching an infinite
22507 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
22508 - Fix a bug where, when we were choosing the 'end stream reason' to
22509 put in our relay end cell that we send to the exit relay, Tor
22510 clients on Windows were sometimes sending the wrong 'reason'. The
22511 anonymity problem is that exit relays may be able to guess whether
22512 the client is running Windows, thus helping partition the anonymity
22513 set. Down the road we should stop sending reasons to exit relays,
22514 or otherwise prevent future versions of this bug.
22515 - Only update guard status (usable / not usable) once we have
22516 enough directory information. This was causing us to discard all our
22517 guards on startup if we hadn't been running for a few weeks. Fixes
22519 - When our directory information has been expired for a while, stop
22520 being willing to build circuits using it. Fixes bug 401.
22522 o Major bugfixes (peace of mind for relay operators)
22523 - Non-exit relays no longer answer "resolve" relay cells, so they
22524 can't be induced to do arbitrary DNS requests. (Tor clients already
22525 avoid using non-exit relays for resolve cells, but now servers
22526 enforce this too.) Fixes bug 619. Patch from lodger.
22527 - When we setconf ClientOnly to 1, close any current OR and Dir
22528 listeners. Reported by mwenge.
22530 o Major bugfixes (other):
22531 - If we only ever used Tor for hidden service lookups or posts, we
22532 would stop building circuits and start refusing connections after
22533 24 hours, since we falsely believed that Tor was dormant. Reported
22535 - Add a new __HashedControlSessionPassword option for controllers
22536 to use for one-off session password hashes that shouldn't get
22537 saved to disk by SAVECONF --- Vidalia users were accumulating a
22538 pile of HashedControlPassword lines in their torrc files, one for
22539 each time they had restarted Tor and then clicked Save. Make Tor
22540 automatically convert "HashedControlPassword" to this new option but
22541 only when it's given on the command line. Partial fix for bug 586.
22542 - Patch from "Andrew S. Lists" to catch when we contact a directory
22543 mirror at IP address X and he says we look like we're coming from
22544 IP address X. Otherwise this would screw up our address detection.
22545 - Reject uploaded descriptors and extrainfo documents if they're
22546 huge. Otherwise we'll cache them all over the network and it'll
22547 clog everything up. Suggested by Aljosha Judmayer.
22548 - When a hidden service was trying to establish an introduction point,
22549 and Tor *did* manage to reuse one of the preemptively built
22550 circuits, it didn't correctly remember which one it used,
22551 so it asked for another one soon after, until there were no
22552 more preemptive circuits, at which point it launched one from
22553 scratch. Bugfix on 0.0.9.x.
22555 o Rate limiting and load balancing improvements:
22556 - When we add data to a write buffer in response to the data on that
22557 write buffer getting low because of a flush, do not consider the
22558 newly added data as a candidate for immediate flushing, but rather
22559 make it wait until the next round of writing. Otherwise, we flush
22560 and refill recursively, and a single greedy TLS connection can
22561 eat all of our bandwidth.
22562 - When counting the number of bytes written on a TLS connection,
22563 look at the BIO actually used for writing to the network, not
22564 at the BIO used (sometimes) to buffer data for the network.
22565 Looking at different BIOs could result in write counts on the
22566 order of ULONG_MAX. Fixes bug 614.
22567 - If we change our MaxAdvertisedBandwidth and then reload torrc,
22568 Tor won't realize it should publish a new relay descriptor. Fixes
22569 bug 688, reported by mfr.
22570 - Avoid using too little bandwidth when our clock skips a few seconds.
22571 - Choose which bridge to use proportional to its advertised bandwidth,
22572 rather than uniformly at random. This should speed up Tor for
22573 bridge users. Also do this for people who set StrictEntryNodes.
22575 o Bootstrapping faster and building circuits more intelligently:
22576 - Fix bug 660 that was preventing us from knowing that we should
22577 preemptively build circuits to handle expected directory requests.
22578 - When we're checking if we have enough dir info for each relay
22579 to begin establishing circuits, make sure that we actually have
22580 the descriptor listed in the consensus, not just any descriptor.
22581 - Correctly notify one-hop connections when a circuit build has
22582 failed. Possible fix for bug 669. Found by lodger.
22583 - Clients now hold circuitless TLS connections open for 1.5 times
22584 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
22585 rebuild a new circuit over them within that timeframe. Previously,
22586 they held them open only for KeepalivePeriod (5 minutes).
22588 o Performance improvements (memory):
22589 - Add OpenBSD malloc code from "phk" as an optional malloc
22590 replacement on Linux: some glibc libraries do very poorly with
22591 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
22592 ./configure to get the replacement malloc code.
22593 - Switch our old ring buffer implementation for one more like that
22594 used by free Unix kernels. The wasted space in a buffer with 1mb
22595 of data will now be more like 8k than 1mb. The new implementation
22596 also avoids realloc();realloc(); patterns that can contribute to
22597 memory fragmentation.
22598 - Change the way that Tor buffers data that it is waiting to write.
22599 Instead of queueing data cells in an enormous ring buffer for each
22600 client->OR or OR->OR connection, we now queue cells on a separate
22601 queue for each circuit. This lets us use less slack memory, and
22602 will eventually let us be smarter about prioritizing different kinds
22604 - Reference-count and share copies of address policy entries; only 5%
22605 of them were actually distinct.
22606 - Tune parameters for cell pool allocation to minimize amount of
22608 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
22609 for every single inactive connection_t. Free items from the
22610 4k/16k-buffer free lists when they haven't been used for a while.
22611 - Make memory debugging information describe more about history
22612 of cell allocation, so we can help reduce our memory use.
22613 - Be even more aggressive about releasing RAM from small
22614 empty buffers. Thanks to our free-list code, this shouldn't be too
22615 performance-intensive.
22616 - Log malloc statistics from mallinfo() on platforms where it exists.
22617 - Use memory pools to allocate cells with better speed and memory
22618 efficiency, especially on platforms where malloc() is inefficient.
22619 - Add a --with-tcmalloc option to the configure script to link
22620 against tcmalloc (if present). Does not yet search for non-system
22623 o Performance improvements (socket management):
22624 - Count the number of open sockets separately from the number of
22625 active connection_t objects. This will let us avoid underusing
22626 our allocated connection limit.
22627 - We no longer use socket pairs to link an edge connection to an
22628 anonymous directory connection or a DirPort test connection.
22629 Instead, we track the link internally and transfer the data
22630 in-process. This saves two sockets per "linked" connection (at the
22631 client and at the server), and avoids the nasty Windows socketpair()
22633 - We were leaking a file descriptor if Tor started with a zero-length
22634 cached-descriptors file. Patch by "freddy77".
22636 o Performance improvements (CPU use):
22637 - Never walk through the list of logs if we know that no log target
22638 is interested in a given message.
22639 - Call routerlist_remove_old_routers() much less often. This should
22640 speed startup, especially on directory caches.
22641 - Base64 decoding was actually showing up on our profile when parsing
22642 the initial descriptor file; switch to an in-process all-at-once
22643 implementation that's about 3.5x times faster than calling out to
22645 - Use a slightly simpler string hashing algorithm (copying Python's
22646 instead of Java's) and optimize our digest hashing algorithm to take
22647 advantage of 64-bit platforms and to remove some possibly-costly
22649 - When implementing AES counter mode, update only the portions of the
22650 counter buffer that need to change, and don't keep separate
22651 network-order and host-order counters on big-endian hosts (where
22652 they are the same).
22653 - Add an in-place version of aes_crypt() so that we can avoid doing a
22654 needless memcpy() call on each cell payload.
22655 - Use Critical Sections rather than Mutexes for synchronizing threads
22656 on win32; Mutexes are heavier-weight, and designed for synchronizing
22659 o Performance improvements (bandwidth use):
22660 - Don't try to launch new descriptor downloads quite so often when we
22661 already have enough directory information to build circuits.
22662 - Version 1 directories are no longer generated in full. Instead,
22663 authorities generate and serve "stub" v1 directories that list
22664 no servers. This will stop Tor versions 0.1.0.x and earlier from
22665 working, but (for security reasons) nobody should be running those
22667 - Avoid going directly to the directory authorities even if you're a
22668 relay, if you haven't found yourself reachable yet or if you've
22669 decided not to advertise your dirport yet. Addresses bug 556.
22670 - If we've gone 12 hours since our last bandwidth check, and we
22671 estimate we have less than 50KB bandwidth capacity but we could
22672 handle more, do another bandwidth test.
22673 - Support "If-Modified-Since" when answering HTTP requests for
22674 directories, running-routers documents, and v2 and v3 networkstatus
22675 documents. (There's no need to support it for router descriptors,
22676 since those are downloaded by descriptor digest.)
22677 - Stop fetching directory info so aggressively if your DirPort is
22678 on but your ORPort is off; stop fetching v2 dir info entirely.
22679 You can override these choices with the new FetchDirInfoEarly
22682 o Changed config option behavior (features):
22683 - Configuration files now accept C-style strings as values. This
22684 helps encode characters not allowed in the current configuration
22685 file format, such as newline or #. Addresses bug 557.
22686 - Add hidden services and DNSPorts to the list of things that make
22687 Tor accept that it has running ports. Change starting Tor with no
22688 ports from a fatal error to a warning; we might change it back if
22689 this turns out to confuse anybody. Fixes bug 579.
22690 - Make PublishServerDescriptor default to 1, so the default doesn't
22691 have to change as we invent new directory protocol versions.
22692 - Allow people to say PreferTunnelledDirConns rather than
22693 PreferTunneledDirConns, for those alternate-spellers out there.
22694 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
22695 accommodate the growing number of servers that use the default
22696 and are reaching it.
22697 - Make it possible to enable HashedControlPassword and
22698 CookieAuthentication at the same time.
22699 - When a TrackHostExits-chosen exit fails too many times in a row,
22700 stop using it. Fixes bug 437.
22702 o Changed config option behavior (bugfixes):
22703 - Do not read the configuration file when we've only been told to
22704 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
22705 based on patch from Sebastian Hahn.
22706 - Actually validate the options passed to AuthDirReject,
22707 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
22708 - Make "ClientOnly 1" config option disable directory ports too.
22709 - Don't stop fetching descriptors when FetchUselessDescriptors is
22710 set, even if we stop asking for circuits. Bug reported by tup
22712 - Servers used to decline to publish their DirPort if their
22713 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
22714 they look only at BandwidthRate and RelayBandwidthRate.
22715 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
22716 minus 1 byte: the actual maximum declared bandwidth.
22717 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
22718 - Make the NodeFamilies config option work. (Reported by
22719 lodger -- it has never actually worked, even though we added it
22721 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
22722 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
22724 o New config options:
22725 - New configuration options AuthDirMaxServersPerAddr and
22726 AuthDirMaxServersperAuthAddr to override default maximum number
22727 of servers allowed on a single IP address. This is important for
22728 running a test network on a single host.
22729 - Three new config options (AlternateDirAuthority,
22730 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
22731 user selectively replace the default directory authorities by type,
22732 rather than the all-or-nothing replacement that DirServer offers.
22733 - New config options AuthDirBadDir and AuthDirListBadDirs for
22734 authorities to mark certain relays as "bad directories" in the
22735 networkstatus documents. Also supports the "!baddir" directive in
22736 the approved-routers file.
22737 - New config option V2AuthoritativeDirectory that all v2 directory
22738 authorities must set. This lets v3 authorities choose not to serve
22739 v2 directory information.
22741 o Minor features (other):
22742 - When we're not serving v2 directory information, there is no reason
22743 to actually keep any around. Remove the obsolete files and directory
22744 on startup if they are very old and we aren't going to serve them.
22745 - When we negotiate a v2 link-layer connection (not yet implemented),
22746 accept RELAY_EARLY cells and turn them into RELAY cells if we've
22747 negotiated a v1 connection for their next step. Initial steps for
22749 - When we have no consensus, check FallbackNetworkstatusFile (defaults
22750 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
22751 we can start out knowing some directory caches. We don't ship with
22752 a fallback consensus by default though, because it was making
22753 bootstrapping take too long while we tried many down relays.
22754 - Authorities send back an X-Descriptor-Not-New header in response to
22755 an accepted-but-discarded descriptor upload. Partially implements
22757 - If we find a cached-routers file that's been sitting around for more
22758 than 28 days unmodified, then most likely it's a leftover from
22759 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
22761 - When we (as a cache) download a descriptor because it was listed
22762 in a consensus, remember when the consensus was supposed to expire,
22763 and don't expire the descriptor until then.
22764 - Optionally (if built with -DEXPORTMALLINFO) export the output
22765 of mallinfo via http, as tor/mallinfo.txt. Only accessible
22767 - Tag every guard node in our state file with the version that
22768 we believe added it, or with our own version if we add it. This way,
22769 if a user temporarily runs an old version of Tor and then switches
22770 back to a new one, she doesn't automatically lose her guards.
22771 - When somebody requests a list of statuses or servers, and we have
22772 none of those, return a 404 rather than an empty 200.
22773 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
22775 - Add an HSAuthorityRecordStats option that hidden service authorities
22776 can use to track statistics of overall hidden service usage without
22777 logging information that would be as useful to an attacker.
22778 - Allow multiple HiddenServicePort directives with the same virtual
22779 port; when they occur, the user is sent round-robin to one
22780 of the target ports chosen at random. Partially fixes bug 393 by
22781 adding limited ad-hoc round-robining.
22782 - Revamp file-writing logic so we don't need to have the entire
22783 contents of a file in memory at once before we write to disk. Tor,
22786 o Minor bugfixes (other):
22787 - Alter the code that tries to recover from unhandled write
22788 errors, to not try to flush onto a socket that's given us
22790 - Directory mirrors no longer include a guess at the client's IP
22791 address if the connection appears to be coming from the same /24
22792 network; it was producing too many wrong guesses.
22793 - If we're trying to flush the last bytes on a connection (for
22794 example, when answering a directory request), reset the
22795 time-to-give-up timeout every time we manage to write something
22797 - Reject router descriptors with out-of-range bandwidthcapacity or
22798 bandwidthburst values.
22799 - If we can't expand our list of entry guards (e.g. because we're
22800 using bridges or we have StrictEntryNodes set), don't mark relays
22801 down when they fail a directory request. Otherwise we're too quick
22802 to mark all our entry points down.
22803 - Authorities no longer send back "400 you're unreachable please fix
22804 it" errors to Tor servers that aren't online all the time. We're
22805 supposed to tolerate these servers now.
22806 - Let directory authorities startup even when they can't generate
22807 a descriptor immediately, e.g. because they don't know their
22809 - Correctly enforce that elements of directory objects do not appear
22810 more often than they are allowed to appear.
22811 - Stop allowing hibernating servers to be "stable" or "fast".
22812 - On Windows, we were preventing other processes from reading
22813 cached-routers while Tor was running. (Reported by janbar)
22814 - Check return values from pthread_mutex functions.
22815 - When opening /dev/null in finish_daemonize(), do not pass the
22816 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
22817 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
22819 o Controller features:
22820 - The GETCONF command now escapes and quotes configuration values
22821 that don't otherwise fit into the torrc file.
22822 - The SETCONF command now handles quoted values correctly.
22823 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
22824 ask about source, timestamp of arrival, purpose, etc. We need
22825 something like this to help Vidalia not do GeoIP lookups on bridge
22827 - Allow multiple HashedControlPassword config lines, to support
22828 multiple controller passwords.
22829 - Accept LF instead of CRLF on controller, since some software has a
22830 hard time generating real Internet newlines.
22831 - Add GETINFO values for the server status events
22832 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
22834 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
22835 GETINFO for Torstat to use until it can switch to using extrainfos.
22836 - New config option CookieAuthFile to choose a new location for the
22837 cookie authentication file, and config option
22838 CookieAuthFileGroupReadable to make it group-readable.
22839 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
22840 match requests to applications. Patch from Robert Hogan.
22841 - Add a RESOLVE command to launch hostname lookups. Original patch
22843 - Add GETINFO status/enough-dir-info to let controllers tell whether
22844 Tor has downloaded sufficient directory information. Patch from Tup.
22845 - You can now use the ControlSocket option to tell Tor to listen for
22846 controller connections on Unix domain sockets on systems that
22847 support them. Patch from Peter Palfrader.
22848 - New "GETINFO address-mappings/*" command to get address mappings
22849 with expiry information. "addr-mappings/*" is now deprecated.
22851 - Add a new config option __DisablePredictedCircuits designed for
22852 use by the controller, when we don't want Tor to build any circuits
22854 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
22855 so we can exit from the middle of the circuit.
22856 - Implement "getinfo status/circuit-established".
22857 - Implement "getinfo status/version/..." so a controller can tell
22858 whether the current version is recommended, and whether any versions
22859 are good, and how many authorities agree. Patch from "shibz".
22860 - Controllers should now specify cache=no or cache=yes when using
22861 the +POSTDESCRIPTOR command.
22862 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
22863 Robert Hogan. Fixes the first part of bug 681.
22864 - When reporting clock skew, and we know that the clock is _at least
22865 as skewed_ as some value, but we don't know the actual value,
22866 report the value as a "minimum skew."
22868 o Controller bugfixes:
22869 - Generate "STATUS_SERVER" events rather than misspelled
22870 "STATUS_SEVER" events. Caught by mwenge.
22871 - Reject controller commands over 1MB in length, so rogue
22872 processes can't run us out of memory.
22873 - Change the behavior of "getinfo status/good-server-descriptor"
22874 so it doesn't return failure when any authority disappears.
22875 - Send NAMESERVER_STATUS messages for a single failed nameserver
22877 - When the DANGEROUS_VERSION controller status event told us we're
22878 running an obsolete version, it used the string "OLD" to describe
22879 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
22880 "OBSOLETE" in both cases.
22881 - Respond to INT and TERM SIGNAL commands before we execute the
22882 signal, in case the signal shuts us down. We had a patch in
22883 0.1.2.1-alpha that tried to do this by queueing the response on
22884 the connection's buffer before shutting down, but that really
22885 isn't the same thing at all. Bug located by Matt Edman.
22886 - Provide DNS expiry times in GMT, not in local time. For backward
22887 compatibility, ADDRMAP events only provide GMT expiry in an extended
22888 field. "GETINFO address-mappings" always does the right thing.
22889 - Use CRLF line endings properly in NS events.
22890 - Make 'getinfo fingerprint' return a 551 error if we're not a
22891 server, so we match what the control spec claims we do. Reported
22893 - Fix a typo in an error message when extendcircuit fails that
22894 caused us to not follow the \r\n-based delimiter protocol. Reported
22896 - When tunneling an encrypted directory connection, and its first
22897 circuit fails, do not leave it unattached and ask the controller
22898 to deal. Fixes the second part of bug 681.
22899 - Treat some 403 responses from directory servers as INFO rather than
22900 WARN-severity events.
22902 o Portability / building / compiling:
22903 - When building with --enable-gcc-warnings, check for whether Apple's
22904 warning "-Wshorten-64-to-32" is available.
22905 - Support compilation to target iPhone; patch from cjacker huang.
22906 To build for iPhone, pass the --enable-iphone option to configure.
22907 - Port Tor to build and run correctly on Windows CE systems, using
22908 the wcecompat library. Contributed by Valerio Lupi.
22909 - Detect non-ASCII platforms (if any still exist) and refuse to
22910 build there: some of our code assumes that 'A' is 65 and so on.
22911 - Clear up some MIPSPro compiler warnings.
22912 - Make autoconf search for libevent, openssl, and zlib consistently.
22913 - Update deprecated macros in configure.in.
22914 - When warning about missing headers, tell the user to let us
22915 know if the compile succeeds anyway, so we can downgrade the
22917 - Include the current subversion revision as part of the version
22918 string: either fetch it directly if we're in an SVN checkout, do
22919 some magic to guess it if we're in an SVK checkout, or use
22920 the last-detected version if we're building from a .tar.gz.
22921 Use this version consistently in log messages.
22922 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
22923 - Read resolv.conf files correctly on platforms where read() returns
22924 partial results on small file reads.
22925 - Build without verbose warnings even on gcc 4.2 and 4.3.
22926 - On Windows, correctly detect errors when listing the contents of
22927 a directory. Fix from lodger.
22928 - Run 'make test' as part of 'make dist', so we stop releasing so
22929 many development snapshots that fail their unit tests.
22930 - Add support to detect Libevent versions in the 1.4.x series
22932 - Add command-line arguments to unit-test executable so that we can
22933 invoke any chosen test from the command line rather than having
22934 to run the whole test suite at once; and so that we can turn on
22935 logging for the unit tests.
22936 - Do not automatically run configure from autogen.sh. This
22937 non-standard behavior tended to annoy people who have built other
22939 - Fix a macro/CPP interaction that was confusing some compilers:
22940 some GCCs don't like #if/#endif pairs inside macro arguments.
22942 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
22943 Fixes bug 704; fix from Steven Murdoch.
22944 - Correctly detect transparent proxy support on Linux hosts that
22945 require in.h to be included before netfilter_ipv4.h. Patch
22948 o Logging improvements:
22949 - When we haven't had any application requests lately, don't bother
22950 logging that we have expired a bunch of descriptors.
22951 - When attempting to open a logfile fails, tell us why.
22952 - Only log guard node status when guard node status has changed.
22953 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
22954 make "INFO" 75% less verbose.
22955 - When SafeLogging is disabled, log addresses along with all TLS
22957 - Report TLS "zero return" case as a "clean close" and "IO error"
22958 as a "close". Stop calling closes "unexpected closes": existing
22959 Tors don't use SSL_close(), so having a connection close without
22960 the TLS shutdown handshake is hardly unexpected.
22961 - When we receive a consensus from the future, warn about skew.
22962 - Make "not enough dir info yet" warnings describe *why* Tor feels
22963 it doesn't have enough directory info yet.
22964 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
22965 consumers. (We already do this on HUP.)
22966 - Give more descriptive well-formedness errors for out-of-range
22967 hidden service descriptor/protocol versions.
22968 - Stop recommending that every server operator send mail to tor-ops.
22969 Resolves bug 597. Bugfix on 0.1.2.x.
22970 - Improve skew reporting: try to give the user a better log message
22971 about how skewed they are, and how much this matters.
22972 - New --quiet command-line option to suppress the default console log.
22973 Good in combination with --hash-password.
22974 - Don't complain that "your server has not managed to confirm that its
22975 ports are reachable" if we haven't been able to build any circuits
22977 - Detect the reason for failing to mmap a descriptor file we just
22978 wrote, and give a more useful log message. Fixes bug 533.
22979 - Always prepend "Bug: " to any log message about a bug.
22980 - When dumping memory usage, list bytes used in buffer memory
22982 - When running with dmalloc, dump more stats on hup and on exit.
22983 - Put a platform string (e.g. "Linux i686") in the startup log
22984 message, so when people paste just their logs, we know if it's
22985 OpenBSD or Windows or what.
22986 - When logging memory usage, break down memory used in buffers by
22988 - When we are reporting the DirServer line we just parsed, we were
22989 logging the second stanza of the key fingerprint, not the first.
22990 - Even though Windows is equally happy with / and \ as path separators,
22991 try to use \ consistently on Windows and / consistently on Unix: it
22992 makes the log messages nicer.
22993 - On OSX, stop warning the user that kqueue support in libevent is
22994 "experimental", since it seems to have worked fine for ages.
22996 o Contributed scripts and tools:
22997 - Update linux-tor-prio.sh script to allow QoS based on the uid of
22998 the Tor process. Patch from Marco Bonetti with tweaks from Mike
23000 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
23001 Unix users an easy way to script their Tor process (e.g. by
23002 adjusting bandwidth based on the time of the day).
23003 - In the exitlist script, only consider the most recently published
23004 server descriptor for each server. Also, when the user requests
23005 a list of servers that _reject_ connections to a given address,
23006 explicitly exclude the IPs that also have servers that accept
23007 connections to that address. Resolves bug 405.
23008 - Include a new contrib/tor-exit-notice.html file that exit relay
23009 operators can put on their website to help reduce abuse queries.
23011 o Newly deprecated features:
23012 - The status/version/num-versioning and status/version/num-concurring
23013 GETINFO controller options are no longer useful in the v3 directory
23014 protocol: treat them as deprecated, and warn when they're used.
23015 - The RedirectExits config option is now deprecated.
23017 o Removed features:
23018 - Drop the old code to choke directory connections when the
23019 corresponding OR connections got full: thanks to the cell queue
23020 feature, OR conns don't get full any more.
23021 - Remove the old "dns worker" server DNS code: it hasn't been default
23022 since 0.1.2.2-alpha, and all the servers are using the new
23024 - Remove the code to generate the oldest (v1) directory format.
23025 - Remove support for the old bw_accounting file: we've been storing
23026 bandwidth accounting information in the state file since
23027 0.1.2.5-alpha. This may result in bandwidth accounting errors
23028 if you try to upgrade from 0.1.1.x or earlier, or if you try to
23029 downgrade to 0.1.1.x or earlier.
23030 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
23031 it, it had no AES, and it hasn't seen any security patches since
23033 - Stop overloading the circuit_t.onionskin field for both "onionskin
23034 from a CREATE cell that we are waiting for a cpuworker to be
23035 assigned" and "onionskin from an EXTEND cell that we are going to
23036 send to an OR as soon as we are connected". Might help with bug 600.
23037 - Remove the tor_strpartition() function: its logic was confused,
23038 and it was only used for one thing that could be implemented far
23040 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
23041 and TorControl.py, as they use the old v0 controller protocol,
23042 and are obsoleted by TorFlow anyway.
23043 - Drop support for v1 rendezvous descriptors, since we never used
23044 them anyway, and the code has probably rotted by now. Based on
23045 patch from Karsten Loesing.
23046 - Stop allowing address masks that do not correspond to bit prefixes.
23047 We have warned about these for a really long time; now it's time
23048 to reject them. (Patch from croup.)
23049 - Remove an optimization in the AES counter-mode code that assumed
23050 that the counter never exceeded 2^68. When the counter can be set
23051 arbitrarily as an IV (as it is by Karsten's new hidden services
23052 code), this assumption no longer holds.
23053 - Disable the SETROUTERPURPOSE controller command: it is now
23057 Changes in version 0.1.2.19 - 2008-01-17
23058 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
23059 exit policy a little bit more conservative so it's safer to run an
23060 exit relay on a home system, and fixes a variety of smaller issues.
23063 - Exit policies now reject connections that are addressed to a
23064 relay's public (external) IP address too, unless
23065 ExitPolicyRejectPrivate is turned off. We do this because too
23066 many relays are running nearby to services that trust them based
23067 on network address.
23070 - When the clock jumps forward a lot, do not allow the bandwidth
23071 buckets to become negative. Fixes bug 544.
23072 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
23073 on every successful resolve. Reported by Mike Perry.
23074 - Purge old entries from the "rephist" database and the hidden
23075 service descriptor database even when DirPort is zero.
23076 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
23077 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
23078 crashing or mis-answering these requests.
23079 - When we decide to send a 503 response to a request for servers, do
23080 not then also send the server descriptors: this defeats the whole
23081 purpose. Fixes bug 539.
23084 - Changing the ExitPolicyRejectPrivate setting should cause us to
23085 rebuild our server descriptor.
23086 - Fix handling of hex nicknames when answering controller requests for
23087 networkstatus by name, or when deciding whether to warn about
23088 unknown routers in a config option. (Patch from mwenge.)
23089 - Fix a couple of hard-to-trigger autoconf problems that could result
23090 in really weird results on platforms whose sys/types.h files define
23091 nonstandard integer types.
23092 - Don't try to create the datadir when running --verify-config or
23093 --hash-password. Resolves bug 540.
23094 - If we were having problems getting a particular descriptor from the
23095 directory caches, and then we learned about a new descriptor for
23096 that router, we weren't resetting our failure count. Reported
23098 - Although we fixed bug 539 (where servers would send HTTP status 503
23099 responses _and_ send a body too), there are still servers out there
23100 that haven't upgraded. Therefore, make clients parse such bodies
23101 when they receive them.
23102 - Run correctly on systems where rlim_t is larger than unsigned long.
23103 This includes some 64-bit systems.
23104 - Run correctly on platforms (like some versions of OS X 10.5) where
23105 the real limit for number of open files is OPEN_FILES, not rlim_max
23106 from getrlimit(RLIMIT_NOFILES).
23107 - Avoid a spurious free on base64 failure.
23108 - Avoid segfaults on certain complex invocations of
23109 router_get_by_hexdigest().
23110 - Fix rare bug on REDIRECTSTREAM control command when called with no
23111 port set: it could erroneously report an error when none had
23115 Changes in version 0.1.2.18 - 2007-10-28
23116 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
23117 hidden service introduction that were causing huge delays, and a big
23118 bug that was causing some servers to disappear from the network status
23119 lists for a few hours each day.
23121 o Major bugfixes (crashes):
23122 - If a connection is shut down abruptly because of something that
23123 happened inside connection_flushed_some(), do not call
23124 connection_finished_flushing(). Should fix bug 451:
23125 "connection_stop_writing: Assertion conn->write_event failed"
23126 Bugfix on 0.1.2.7-alpha.
23127 - Fix possible segfaults in functions called from
23128 rend_process_relay_cell().
23130 o Major bugfixes (hidden services):
23131 - Hidden services were choosing introduction points uniquely by
23132 hexdigest, but when constructing the hidden service descriptor
23133 they merely wrote the (potentially ambiguous) nickname.
23134 - Clients now use the v2 intro format for hidden service
23135 connections: they specify their chosen rendezvous point by identity
23136 digest rather than by (potentially ambiguous) nickname. These
23137 changes could speed up hidden service connections dramatically.
23139 o Major bugfixes (other):
23140 - Stop publishing a new server descriptor just because we get a
23141 HUP signal. This led (in a roundabout way) to some servers getting
23142 dropped from the networkstatus lists for a few hours each day.
23143 - When looking for a circuit to cannibalize, consider family as well
23144 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
23145 circuit cannibalization).
23146 - When a router wasn't listed in a new networkstatus, we were leaving
23147 the flags for that router alone -- meaning it remained Named,
23148 Running, etc -- even though absence from the networkstatus means
23149 that it shouldn't be considered to exist at all anymore. Now we
23150 clear all the flags for routers that fall out of the networkstatus
23151 consensus. Fixes bug 529.
23154 - Don't try to access (or alter) the state file when running
23155 --list-fingerprint or --verify-config or --hash-password. Resolves
23157 - When generating information telling us how to extend to a given
23158 router, do not try to include the nickname if it is
23159 absent. Resolves bug 467.
23160 - Fix a user-triggerable segfault in expand_filename(). (There isn't
23161 a way to trigger this remotely.)
23162 - When sending a status event to the controller telling it that an
23163 OR address is reachable, set the port correctly. (Previously we
23164 were reporting the dir port.)
23165 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
23166 command. Bugfix on 0.1.2.17.
23167 - When loading bandwidth history, do not believe any information in
23168 the future. Fixes bug 434.
23169 - When loading entry guard information, do not believe any information
23171 - When we have our clock set far in the future and generate an
23172 onion key, then re-set our clock to be correct, we should not stop
23173 the onion key from getting rotated.
23174 - On some platforms, accept() can return a broken address. Detect
23175 this more quietly, and deal accordingly. Fixes bug 483.
23176 - It's not actually an error to find a non-pending entry in the DNS
23177 cache when canceling a pending resolve. Don't log unless stuff
23178 is fishy. Resolves bug 463.
23179 - Don't reset trusted dir server list when we set a configuration
23180 option. Patch from Robert Hogan.
23183 Changes in version 0.1.2.17 - 2007-08-30
23184 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
23185 X bundles. Vidalia 0.0.14 makes authentication required for the
23186 ControlPort in the default configuration, which addresses important
23187 security risks. Everybody who uses Vidalia (or another controller)
23190 In addition, this Tor update fixes major load balancing problems with
23191 path selection, which should speed things up a lot once many people
23194 o Major bugfixes (security):
23195 - We removed support for the old (v0) control protocol. It has been
23196 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
23197 become more of a headache than it's worth.
23199 o Major bugfixes (load balancing):
23200 - When choosing nodes for non-guard positions, weight guards
23201 proportionally less, since they already have enough load. Patch
23203 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
23204 will allow fast Tor servers to get more attention.
23205 - When we're upgrading from an old Tor version, forget our current
23206 guards and pick new ones according to the new weightings. These
23207 three load balancing patches could raise effective network capacity
23208 by a factor of four. Thanks to Mike Perry for measurements.
23210 o Major bugfixes (stream expiration):
23211 - Expire not-yet-successful application streams in all cases if
23212 they've been around longer than SocksTimeout. Right now there are
23213 some cases where the stream will live forever, demanding a new
23214 circuit every 15 seconds. Fixes bug 454; reported by lodger.
23216 o Minor features (controller):
23217 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
23218 is valid before any authentication has been received. It tells
23219 a controller what kind of authentication is expected, and what
23220 protocol is spoken. Implements proposal 119.
23222 o Minor bugfixes (performance):
23223 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
23224 greatly speeding up loading cached-routers from disk on startup.
23225 - Disable sentinel-based debugging for buffer code: we squashed all
23226 the bugs that this was supposed to detect a long time ago, and now
23227 its only effect is to change our buffer sizes from nice powers of
23228 two (which platform mallocs tend to like) to values slightly over
23229 powers of two (which make some platform mallocs sad).
23231 o Minor bugfixes (misc):
23232 - If exit bandwidth ever exceeds one third of total bandwidth, then
23233 use the correct formula to weight exit nodes when choosing paths.
23234 Based on patch from Mike Perry.
23235 - Choose perfectly fairly among routers when choosing by bandwidth and
23236 weighting by fraction of bandwidth provided by exits. Previously, we
23237 would choose with only approximate fairness, and correct ourselves
23238 if we ran off the end of the list.
23239 - If we require CookieAuthentication but we fail to write the
23240 cookie file, we would warn but not exit, and end up in a state
23241 where no controller could authenticate. Now we exit.
23242 - If we require CookieAuthentication, stop generating a new cookie
23243 every time we change any piece of our config.
23244 - Refuse to start with certain directory authority keys, and
23245 encourage people using them to stop.
23246 - Terminate multi-line control events properly. Original patch
23248 - Fix a minor memory leak when we fail to find enough suitable
23249 servers to choose a circuit.
23250 - Stop leaking part of the descriptor when we run into a particularly
23251 unparseable piece of it.
23254 Changes in version 0.1.2.16 - 2007-08-01
23255 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
23256 remote attacker in certain situations to rewrite the user's torrc
23257 configuration file. This can completely compromise anonymity of users
23258 in most configurations, including those running the Vidalia bundles,
23259 TorK, etc. Or worse.
23261 o Major security fixes:
23262 - Close immediately after missing authentication on control port;
23263 do not allow multiple authentication attempts.
23266 Changes in version 0.1.2.15 - 2007-07-17
23267 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
23268 problems, fixes compilation on BSD, and fixes a variety of other
23269 bugs. Everybody should upgrade.
23271 o Major bugfixes (compilation):
23272 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
23274 o Major bugfixes (crashes):
23275 - Try even harder not to dereference the first character after
23276 an mmap(). Reported by lodger.
23277 - Fix a crash bug in directory authorities when we re-number the
23278 routerlist while inserting a new router.
23279 - When the cached-routers file is an even multiple of the page size,
23280 don't run off the end and crash. (Fixes bug 455; based on idea
23282 - Fix eventdns.c behavior on Solaris: It is critical to include
23283 orconfig.h _before_ sys/types.h, so that we can get the expected
23284 definition of _FILE_OFFSET_BITS.
23286 o Major bugfixes (security):
23287 - Fix a possible buffer overrun when using BSD natd support. Bug
23289 - When sending destroy cells from a circuit's origin, don't include
23290 the reason for tearing down the circuit. The spec says we didn't,
23291 and now we actually don't. Reported by lodger.
23292 - Keep streamids from different exits on a circuit separate. This
23293 bug may have allowed other routers on a given circuit to inject
23294 cells into streams. Reported by lodger; fixes bug 446.
23295 - If there's a never-before-connected-to guard node in our list,
23296 never choose any guards past it. This way we don't expand our
23297 guard list unless we need to.
23299 o Minor bugfixes (guard nodes):
23300 - Weight guard selection by bandwidth, so that low-bandwidth nodes
23301 don't get overused as guards.
23303 o Minor bugfixes (directory):
23304 - Correctly count the number of authorities that recommend each
23305 version. Previously, we were under-counting by 1.
23306 - Fix a potential crash bug when we load many server descriptors at
23307 once and some of them make others of them obsolete. Fixes bug 458.
23309 o Minor bugfixes (hidden services):
23310 - Stop tearing down the whole circuit when the user asks for a
23311 connection to a port that the hidden service didn't configure.
23314 o Minor bugfixes (misc):
23315 - On Windows, we were preventing other processes from reading
23316 cached-routers while Tor was running. Reported by janbar.
23317 - Fix a possible (but very unlikely) bug in picking routers by
23318 bandwidth. Add a log message to confirm that it is in fact
23319 unlikely. Patch from lodger.
23320 - Backport a couple of memory leak fixes.
23321 - Backport miscellaneous cosmetic bugfixes.
23324 Changes in version 0.1.2.14 - 2007-05-25
23325 Tor 0.1.2.14 changes the addresses of two directory authorities (this
23326 change especially affects those who serve or use hidden services),
23327 and fixes several other crash- and security-related bugs.
23329 o Directory authority changes:
23330 - Two directory authorities (moria1 and moria2) just moved to new
23331 IP addresses. This change will particularly affect those who serve
23332 or use hidden services.
23334 o Major bugfixes (crashes):
23335 - If a directory server runs out of space in the connection table
23336 as it's processing a begin_dir request, it will free the exit stream
23337 but leave it attached to the circuit, leading to unpredictable
23338 behavior. (Reported by seeess, fixes bug 425.)
23339 - Fix a bug in dirserv_remove_invalid() that would cause authorities
23340 to corrupt memory under some really unlikely scenarios.
23341 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
23342 - Avoid segfaults when reading from mmaped descriptor file. (Reported
23345 o Major bugfixes (security):
23346 - When choosing an entry guard for a circuit, avoid using guards
23347 that are in the same family as the chosen exit -- not just guards
23348 that are exactly the chosen exit. (Reported by lodger.)
23350 o Major bugfixes (resource management):
23351 - If a directory authority is down, skip it when deciding where to get
23352 networkstatus objects or descriptors. Otherwise we keep asking
23353 every 10 seconds forever. Fixes bug 384.
23354 - Count it as a failure if we fetch a valid network-status but we
23355 don't want to keep it. Otherwise we'll keep fetching it and keep
23356 not wanting to keep it. Fixes part of bug 422.
23357 - If all of our dirservers have given us bad or no networkstatuses
23358 lately, then stop hammering them once per minute even when we
23359 think they're failed. Fixes another part of bug 422.
23362 - Actually set the purpose correctly for descriptors inserted with
23363 purpose=controller.
23364 - When we have k non-v2 authorities in our DirServer config,
23365 we ignored the last k authorities in the list when updating our
23367 - Correctly back-off from requesting router descriptors that we are
23368 having a hard time downloading.
23369 - Read resolv.conf files correctly on platforms where read() returns
23370 partial results on small file reads.
23371 - Don't rebuild the entire router store every time we get 32K of
23372 routers: rebuild it when the journal gets very large, or when
23373 the gaps in the store get very large.
23376 - When routers publish SVN revisions in their router descriptors,
23377 authorities now include those versions correctly in networkstatus
23379 - Warn when using a version of libevent before 1.3b to run a server on
23380 OSX or BSD: these versions interact badly with userspace threads.
23383 Changes in version 0.1.2.13 - 2007-04-24
23384 This release features some major anonymity fixes, such as safer path
23385 selection; better client performance; faster bootstrapping, better
23386 address detection, and better DNS support for servers; write limiting as
23387 well as read limiting to make servers easier to run; and a huge pile of
23388 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
23390 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
23391 of the Freenode IRC network, remembering his patience and vision for
23392 free speech on the Internet.
23394 o Major features, client performance:
23395 - Weight directory requests by advertised bandwidth. Now we can
23396 let servers enable write limiting but still allow most clients to
23397 succeed at their directory requests. (We still ignore weights when
23398 choosing a directory authority; I hope this is a feature.)
23399 - Stop overloading exit nodes -- avoid choosing them for entry or
23400 middle hops when the total bandwidth available from non-exit nodes
23401 is much higher than the total bandwidth available from exit nodes.
23402 - Rather than waiting a fixed amount of time between retrying
23403 application connections, we wait only 10 seconds for the first,
23404 10 seconds for the second, and 15 seconds for each retry after
23405 that. Hopefully this will improve the expected user experience.
23406 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
23407 to open a stream fails; now we do in more cases. This should
23408 make clients able to find a good exit faster in some cases, since
23409 unhandleable requests will now get an error rather than timing out.
23411 o Major features, client functionality:
23412 - Implement BEGIN_DIR cells, so we can connect to a directory
23413 server via TLS to do encrypted directory requests rather than
23414 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
23415 config options if you like. For now, this feature only works if
23416 you already have a descriptor for the destination dirserver.
23417 - Add support for transparent application connections: this basically
23418 bundles the functionality of trans-proxy-tor into the Tor
23419 mainline. Now hosts with compliant pf/netfilter implementations
23420 can redirect TCP connections straight to Tor without diverting
23421 through SOCKS. (Based on patch from tup.)
23422 - Add support for using natd; this allows FreeBSDs earlier than
23423 5.1.2 to have ipfw send connections through Tor without using
23424 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
23426 o Major features, servers:
23427 - Setting up a dyndns name for your server is now optional: servers
23428 with no hostname or IP address will learn their IP address by
23429 asking the directory authorities. This code only kicks in when you
23430 would normally have exited with a "no address" error. Nothing's
23431 authenticated, so use with care.
23432 - Directory servers now spool server descriptors, v1 directories,
23433 and v2 networkstatus objects to buffers as needed rather than en
23434 masse. They also mmap the cached-routers files. These steps save
23436 - Stop requiring clients to have well-formed certificates, and stop
23437 checking nicknames in certificates. (Clients have certificates so
23438 that they can look like Tor servers, but in the future we might want
23439 to allow them to look like regular TLS clients instead. Nicknames
23440 in certificates serve no purpose other than making our protocol
23441 easier to recognize on the wire.) Implements proposal 106.
23443 o Improvements on DNS support:
23444 - Add "eventdns" asynchronous dns library originally based on code
23445 from Adam Langley. Now we can discard the old rickety dnsworker
23446 concept, and support a wider variety of DNS functions. Allows
23447 multithreaded builds on NetBSD and OpenBSD again.
23448 - Add server-side support for "reverse" DNS lookups (using PTR
23449 records so clients can determine the canonical hostname for a given
23450 IPv4 address). Only supported by servers using eventdns; servers
23451 now announce in their descriptors if they don't support eventdns.
23452 - Workaround for name servers (like Earthlink's) that hijack failing
23453 DNS requests and replace the no-such-server answer with a "helpful"
23454 redirect to an advertising-driven search portal. Also work around
23455 DNS hijackers who "helpfully" decline to hijack known-invalid
23456 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
23457 lets you turn it off.
23458 - Servers now check for the case when common DNS requests are going to
23459 wildcarded addresses (i.e. all getting the same answer), and change
23460 their exit policy to reject *:* if it's happening.
23461 - When asked to resolve a hostname, don't use non-exit servers unless
23462 requested to do so. This allows servers with broken DNS to be
23463 useful to the network.
23464 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
23465 useless IPv6 DNS resolves.
23466 - Specify and implement client-side SOCKS5 interface for reverse DNS
23467 lookups (see doc/socks-extensions.txt). Also cache them.
23468 - When we change nameservers or IP addresses, reset and re-launch
23469 our tests for DNS hijacking.
23471 o Improvements on reachability testing:
23472 - Servers send out a burst of long-range padding cells once they've
23473 established that they're reachable. Spread them over 4 circuits,
23474 so hopefully a few will be fast. This exercises bandwidth and
23475 bootstraps them into the directory more quickly.
23476 - When we find our DirPort to be reachable, publish a new descriptor
23477 so we'll tell the world (reported by pnx).
23478 - Directory authorities now only decide that routers are reachable
23479 if their identity keys are as expected.
23480 - Do DirPort reachability tests less often, since a single test
23481 chews through many circuits before giving up.
23482 - Avoid some false positives during reachability testing: don't try
23483 to test via a server that's on the same /24 network as us.
23484 - Start publishing one minute or so after we find our ORPort
23485 to be reachable. This will help reduce the number of descriptors
23486 we have for ourselves floating around, since it's quite likely
23487 other things (e.g. DirPort) will change during that minute too.
23488 - Routers no longer try to rebuild long-term connections to directory
23489 authorities, and directory authorities no longer try to rebuild
23490 long-term connections to all servers. We still don't hang up
23491 connections in these two cases though -- we need to look at it
23492 more carefully to avoid flapping, and we likely need to wait til
23493 0.1.1.x is obsolete.
23495 o Improvements on rate limiting:
23496 - Enable write limiting as well as read limiting. Now we sacrifice
23497 capacity if we're pushing out lots of directory traffic, rather
23498 than overrunning the user's intended bandwidth limits.
23499 - Include TLS overhead when counting bandwidth usage; previously, we
23500 would count only the bytes sent over TLS, but not the bytes used
23502 - Servers decline directory requests much more aggressively when
23503 they're low on bandwidth. Otherwise they end up queueing more and
23504 more directory responses, which can't be good for latency.
23505 - But never refuse directory requests from local addresses.
23506 - Be willing to read or write on local connections (e.g. controller
23507 connections) even when the global rate limiting buckets are empty.
23508 - Flush local controller connection buffers periodically as we're
23509 writing to them, so we avoid queueing 4+ megabytes of data before
23511 - Revise and clean up the torrc.sample that we ship with; add
23512 a section for BandwidthRate and BandwidthBurst.
23514 o Major features, NT services:
23515 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
23516 command-line flag so that admins can override the default by saying
23517 "tor --service install --user "SomeUser"". This will not affect
23518 existing installed services. Also, warn the user that the service
23519 will look for its configuration file in the service user's
23520 %appdata% directory. (We can't do the "hardwire the user's appdata
23521 directory" trick any more, since we may not have read access to that
23523 - Support running the Tor service with a torrc not in the same
23524 directory as tor.exe and default to using the torrc located in
23525 the %appdata%\Tor\ of the user who installed the service. Patch
23527 - Add an --ignore-missing-torrc command-line option so that we can
23528 get the "use sensible defaults if the configuration file doesn't
23529 exist" behavior even when specifying a torrc location on the
23531 - When stopping an NT service, wait up to 10 sec for it to actually
23532 stop. (Patch from Matt Edman; resolves bug 295.)
23534 o Directory authority improvements:
23535 - Stop letting hibernating or obsolete servers affect uptime and
23537 - Stop listing hibernating servers in the v1 directory.
23538 - Authorities no longer recommend exits as guards if this would shift
23539 too much load to the exit nodes.
23540 - Authorities now specify server versions in networkstatus. This adds
23541 about 2% to the size of compressed networkstatus docs, and allows
23542 clients to tell which servers support BEGIN_DIR and which don't.
23543 The implementation is forward-compatible with a proposed future
23544 protocol version scheme not tied to Tor versions.
23545 - DirServer configuration lines now have an orport= option so
23546 clients can open encrypted tunnels to the authorities without
23547 having downloaded their descriptors yet. Enabled for moria1,
23548 moria2, tor26, and lefkada now in the default configuration.
23549 - Add a BadDirectory flag to network status docs so that authorities
23550 can (eventually) tell clients about caches they believe to be
23551 broken. Not used yet.
23552 - Allow authorities to list nodes as bad exits in their
23553 approved-routers file by fingerprint or by address. If most
23554 authorities set a BadExit flag for a server, clients don't think
23555 of it as a general-purpose exit. Clients only consider authorities
23556 that advertise themselves as listing bad exits.
23557 - Patch from Steve Hildrey: Generate network status correctly on
23558 non-versioning dirservers.
23559 - Have directory authorities allow larger amounts of drift in uptime
23560 without replacing the server descriptor: previously, a server that
23561 restarted every 30 minutes could have 48 "interesting" descriptors
23563 - Reserve the nickname "Unnamed" for routers that can't pick
23564 a hostname: any router can call itself Unnamed; directory
23565 authorities will never allocate Unnamed to any particular router;
23566 clients won't believe that any router is the canonical Unnamed.
23568 o Directory mirrors and clients:
23569 - Discard any v1 directory info that's over 1 month old (for
23570 directories) or over 1 week old (for running-routers lists).
23571 - Clients track responses with status 503 from dirservers. After a
23572 dirserver has given us a 503, we try not to use it until an hour has
23573 gone by, or until we have no dirservers that haven't given us a 503.
23574 - When we get a 503 from a directory, and we're not a server, we no
23575 longer count the failure against the total number of failures
23576 allowed for the object we're trying to download.
23577 - Prepare for servers to publish descriptors less often: never
23578 discard a descriptor simply for being too old until either it is
23579 recommended by no authorities, or until we get a better one for
23580 the same router. Make caches consider retaining old recommended
23581 routers for even longer.
23582 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
23583 headers for content, so that we can work better in the presence of
23584 caching HTTP proxies.
23585 - Stop fetching descriptors if you're not a dir mirror and you
23586 haven't tried to establish any circuits lately. (This currently
23587 causes some dangerous behavior, because when you start up again
23588 you'll use your ancient server descriptors.)
23590 o Major fixes, crashes:
23591 - Stop crashing when the controller asks us to resetconf more than
23592 one config option at once. (Vidalia 0.0.11 does this.)
23593 - Fix a longstanding obscure crash bug that could occur when we run
23594 out of DNS worker processes, if we're not using eventdns. (Resolves
23596 - Fix an assert that could trigger if a controller quickly set then
23597 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
23598 - Avoid crash when telling controller about stream-status and a
23599 stream is detached.
23600 - Avoid sending junk to controllers or segfaulting when a controller
23601 uses EVENT_NEW_DESC with verbose nicknames.
23602 - Stop triggering asserts if the controller tries to extend hidden
23603 service circuits (reported by mwenge).
23604 - If we start a server with ClientOnly 1, then set ClientOnly to 0
23605 and hup, stop triggering an assert based on an empty onion_key.
23606 - Mask out all signals in sub-threads; only the libevent signal
23607 handler should be processing them. This should prevent some crashes
23608 on some machines using pthreads. (Patch from coderman.)
23609 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
23611 o Major fixes, anonymity/security:
23612 - Automatically avoid picking more than one node from the same
23613 /16 network when constructing a circuit. Add an
23614 "EnforceDistinctSubnets" option to let people disable it if they
23615 want to operate private test networks on a single subnet.
23616 - When generating bandwidth history, round down to the nearest
23617 1k. When storing accounting data, round up to the nearest 1k.
23618 - When we're running as a server, remember when we last rotated onion
23619 keys, so that we will rotate keys once they're a week old even if
23620 we never stay up for a week ourselves.
23621 - If a client asked for a server by name, and there's a named server
23622 in our network-status but we don't have its descriptor yet, we
23623 could return an unnamed server instead.
23624 - Reject (most) attempts to use Tor circuits with length one. (If
23625 many people start using Tor as a one-hop proxy, exit nodes become
23626 a more attractive target for compromise.)
23627 - Just because your DirPort is open doesn't mean people should be
23628 able to remotely teach you about hidden service descriptors. Now
23629 only accept rendezvous posts if you've got HSAuthoritativeDir set.
23630 - Fix a potential race condition in the rpm installer. Found by
23632 - Do not log IPs with TLS failures for incoming TLS
23633 connections. (Fixes bug 382.)
23635 o Major fixes, other:
23636 - If our system clock jumps back in time, don't publish a negative
23637 uptime in the descriptor.
23638 - When we start during an accounting interval before it's time to wake
23639 up, remember to wake up at the correct time. (May fix bug 342.)
23640 - Previously, we would cache up to 16 old networkstatus documents
23641 indefinitely, if they came from nontrusted authorities. Now we
23642 discard them if they are more than 10 days old.
23643 - When we have a state file we cannot parse, tell the user and
23644 move it aside. Now we avoid situations where the user starts
23645 Tor in 1904, Tor writes a state file with that timestamp in it,
23646 the user fixes her clock, and Tor refuses to start.
23647 - Publish a new descriptor after we hup/reload. This is important
23648 if our config has changed such that we'll want to start advertising
23649 our DirPort now, etc.
23650 - If we are using an exit enclave and we can't connect, e.g. because
23651 its webserver is misconfigured to not listen on localhost, then
23652 back off and try connecting from somewhere else before we fail.
23654 o New config options or behaviors:
23655 - When EntryNodes are configured, rebuild the guard list to contain,
23656 in order: the EntryNodes that were guards before; the rest of the
23657 EntryNodes; the nodes that were guards before.
23658 - Do not warn when individual nodes in the configuration's EntryNodes,
23659 ExitNodes, etc are down: warn only when all possible nodes
23660 are down. (Fixes bug 348.)
23661 - Put a lower-bound on MaxAdvertisedBandwidth.
23662 - Start using the state file to store bandwidth accounting data:
23663 the bw_accounting file is now obsolete. We'll keep generating it
23664 for a while for people who are still using 0.1.2.4-alpha.
23665 - Try to batch changes to the state file so that we do as few
23666 disk writes as possible while still storing important things in
23668 - The state file and the bw_accounting file get saved less often when
23669 the AvoidDiskWrites config option is set.
23670 - Make PIDFile work on Windows.
23671 - Add internal descriptions for a bunch of configuration options:
23672 accessible via controller interface and in comments in saved
23674 - Reject *:563 (NNTPS) in the default exit policy. We already reject
23675 NNTP by default, so this seems like a sensible addition.
23676 - Clients now reject hostnames with invalid characters. This should
23677 avoid some inadvertent info leaks. Add an option
23678 AllowNonRFC953Hostnames to disable this behavior, in case somebody
23679 is running a private network with hosts called @, !, and #.
23680 - Check for addresses with invalid characters at the exit as well,
23681 and warn less verbosely when they fail. You can override this by
23682 setting ServerDNSAllowNonRFC953Addresses to 1.
23683 - Remove some options that have been deprecated since at least
23684 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
23685 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
23686 to set log options. Mark PathlenCoinWeight as obsolete.
23687 - Stop accepting certain malformed ports in configured exit policies.
23688 - When the user uses bad syntax in the Log config line, stop
23689 suggesting other bad syntax as a replacement.
23690 - Add new config option "ResolvConf" to let the server operator
23691 choose an alternate resolve.conf file when using eventdns.
23692 - If one of our entry guards is on the ExcludeNodes list, or the
23693 directory authorities don't think it's a good guard, treat it as
23694 if it were unlisted: stop using it as a guard, and throw it off
23695 the guards list if it stays that way for a long time.
23696 - Allow directory authorities to be marked separately as authorities
23697 for the v1 directory protocol, the v2 directory protocol, and
23698 as hidden service directories, to make it easier to retire old
23699 authorities. V1 authorities should set "HSAuthoritativeDir 1"
23700 to continue being hidden service authorities too.
23701 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
23702 - Make TrackExitHosts case-insensitive, and fix the behavior of
23703 ".suffix" TrackExitHosts items to avoid matching in the middle of
23705 - New DirPort behavior: if you have your dirport set, you download
23706 descriptors aggressively like a directory mirror, whether or not
23707 your ORPort is set.
23710 - Create a new file ReleaseNotes which was the old ChangeLog. The
23711 new ChangeLog file now includes the notes for all development
23713 - Add a new address-spec.txt document to describe our special-case
23714 addresses: .exit, .onion, and .noconnnect.
23715 - Fork the v1 directory protocol into its own spec document,
23716 and mark dir-spec.txt as the currently correct (v2) spec.
23718 o Packaging, porting, and contrib
23719 - "tor --verify-config" now exits with -1(255) or 0 depending on
23720 whether the config options are bad or good.
23721 - The Debian package now uses --verify-config when (re)starting,
23722 to distinguish configuration errors from other errors.
23723 - Adapt a patch from goodell to let the contrib/exitlist script
23724 take arguments rather than require direct editing.
23725 - Prevent the contrib/exitlist script from printing the same
23726 result more than once.
23727 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
23728 - In the hidden service example in torrc.sample, stop recommending
23729 esoteric and discouraged hidden service options.
23730 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
23731 values before failing, and always enables eventdns.
23732 - Try to detect Windows correctly when cross-compiling.
23733 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
23734 Try to fix this in configure.in by checking for most functions
23735 before we check for libevent.
23736 - Update RPMs to require libevent 1.2.
23737 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
23738 or later. Log when we are doing this, so we can diagnose it when
23739 it fails. (Also, recommend libevent 1.1b for kqueue and
23740 win32 methods; deprecate libevent 1.0b harder; make libevent
23741 recommendation system saner.)
23742 - Build with recent (1.3+) libevents on platforms that do not
23743 define the nonstandard types "u_int8_t" and friends.
23744 - Remove architecture from OS X builds. The official builds are
23745 now universal binaries.
23746 - Run correctly on OS X platforms with case-sensitive filesystems.
23747 - Correctly set maximum connection limit on Cygwin. (This time
23749 - Start compiling on MinGW on Windows (patches from Mike Chiussi
23751 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
23752 - Finally fix the openssl warnings from newer gccs that believe that
23753 ignoring a return value is okay, but casting a return value and
23754 then ignoring it is a sign of madness.
23755 - On architectures where sizeof(int)>4, still clamp declarable
23756 bandwidth to INT32_MAX.
23758 o Minor features, controller:
23759 - Warn the user when an application uses the obsolete binary v0
23760 control protocol. We're planning to remove support for it during
23761 the next development series, so it's good to give people some
23763 - Add STREAM_BW events to report per-entry-stream bandwidth
23764 use. (Patch from Robert Hogan.)
23765 - Rate-limit SIGNEWNYM signals in response to controllers that
23766 impolitely generate them for every single stream. (Patch from
23767 mwenge; closes bug 394.)
23768 - Add a REMAP status to stream events to note that a stream's
23769 address has changed because of a cached address or a MapAddress
23771 - Make REMAP stream events have a SOURCE (cache or exit), and
23772 make them generated in every case where we get a successful
23773 connected or resolved cell.
23774 - Track reasons for OR connection failure; make these reasons
23775 available via the controller interface. (Patch from Mike Perry.)
23776 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
23777 can learn when clients are sending malformed hostnames to Tor.
23778 - Specify and implement some of the controller status events.
23779 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
23780 - Reimplement GETINFO so that info/names stays in sync with the
23782 - Implement "GETINFO fingerprint".
23783 - Implement "SETEVENTS GUARD" so controllers can get updates on
23784 entry guard status as it changes.
23785 - Make all connections to addresses of the form ".noconnect"
23786 immediately get closed. This lets application/controller combos
23787 successfully test whether they're talking to the same Tor by
23788 watching for STREAM events.
23789 - Add a REASON field to CIRC events; for backward compatibility, this
23790 field is sent only to controllers that have enabled the extended
23791 event format. Also, add additional reason codes to explain why
23792 a given circuit has been destroyed or truncated. (Patches from
23794 - Add a REMOTE_REASON field to extended CIRC events to tell the
23795 controller why a remote OR told us to close a circuit.
23796 - Stream events also now have REASON and REMOTE_REASON fields,
23797 working much like those for circuit events.
23798 - There's now a GETINFO ns/... field so that controllers can ask Tor
23799 about the current status of a router.
23800 - A new event type "NS" to inform a controller when our opinion of
23801 a router's status has changed.
23802 - Add a GETINFO events/names and GETINFO features/names so controllers
23803 can tell which events and features are supported.
23804 - A new CLEARDNSCACHE signal to allow controllers to clear the
23805 client-side DNS cache without expiring circuits.
23806 - Fix CIRC controller events so that controllers can learn the
23807 identity digests of non-Named servers used in circuit paths.
23808 - Let controllers ask for more useful identifiers for servers. Instead
23809 of learning identity digests for un-Named servers and nicknames
23810 for Named servers, the new identifiers include digest, nickname,
23811 and indication of Named status. Off by default; see control-spec.txt
23812 for more information.
23813 - Add a "getinfo address" controller command so it can display Tor's
23814 best guess to the user.
23815 - New controller event to alert the controller when our server
23816 descriptor has changed.
23817 - Give more meaningful errors on controller authentication failure.
23818 - Export the default exit policy via the control port, so controllers
23819 don't need to guess what it is / will be later.
23821 o Minor bugfixes, controller:
23822 - When creating a circuit via the controller, send a 'launched'
23823 event when we're done, so we follow the spec better.
23824 - Correct the control spec to match how the code actually responds
23825 to 'getinfo addr-mappings/*'. Reported by daejees.
23826 - The control spec described a GUARDS event, but the code
23827 implemented a GUARD event. Standardize on GUARD, but let people
23828 ask for GUARDS too. Reported by daejees.
23829 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
23830 clear the corresponding on_circuit variable, and remember later
23831 that we don't need to send a redundant CLOSED event. (Resolves part
23833 - Report events where a resolve succeeded or where we got a socks
23834 protocol error correctly, rather than calling both of them
23836 - Change reported stream target addresses to IP consistently when
23837 we finally get the IP from an exit node.
23838 - Send log messages to the controller even if they happen to be very
23840 - Flush ERR-level controller status events just like we currently
23841 flush ERR-level log events, so that a Tor shutdown doesn't prevent
23842 the controller from learning about current events.
23843 - Report the circuit number correctly in STREAM CLOSED events. Bug
23844 reported by Mike Perry.
23845 - Do not report bizarre values for results of accounting GETINFOs
23846 when the last second's write or read exceeds the allotted bandwidth.
23847 - Report "unrecognized key" rather than an empty string when the
23848 controller tries to fetch a networkstatus that doesn't exist.
23849 - When the controller does a "GETINFO network-status", tell it
23850 about even those routers whose descriptors are very old, and use
23851 long nicknames where appropriate.
23852 - Fix handling of verbose nicknames with ORCONN controller events:
23853 make them show up exactly when requested, rather than exactly when
23855 - Controller signals now work on non-Unix platforms that don't define
23856 SIGUSR1 and SIGUSR2 the way we expect.
23857 - Respond to SIGNAL command before we execute the signal, in case
23858 the signal shuts us down. Suggested by Karsten Loesing.
23859 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
23861 o Minor features, code performance:
23862 - Major performance improvement on inserting descriptors: change
23863 algorithm from O(n^2) to O(n).
23864 - Do not rotate onion key immediately after setting it for the first
23866 - Call router_have_min_dir_info half as often. (This is showing up in
23867 some profiles, but not others.)
23868 - When using GCC, make log_debug never get called at all, and its
23869 arguments never get evaluated, when no debug logs are configured.
23870 (This is showing up in some profiles, but not others.)
23871 - Statistics dumped by -USR2 now include a breakdown of public key
23872 operations, for profiling.
23873 - Make the common memory allocation path faster on machines where
23874 malloc(0) returns a pointer.
23875 - Split circuit_t into origin_circuit_t and or_circuit_t, and
23876 split connection_t into edge, or, dir, control, and base structs.
23877 These will save quite a bit of memory on busy servers, and they'll
23878 also help us track down bugs in the code and bugs in the spec.
23879 - Use OpenSSL's AES implementation on platforms where it's faster.
23880 This could save us as much as 10% CPU usage.
23882 o Minor features, descriptors and descriptor handling:
23883 - Avoid duplicate entries on MyFamily line in server descriptor.
23884 - When Tor receives a router descriptor that it asked for, but
23885 no longer wants (because it has received fresh networkstatuses
23886 in the meantime), do not warn the user. Cache the descriptor if
23887 we're a cache; drop it if we aren't.
23888 - Servers no longer ever list themselves in their "family" line,
23889 even if configured to do so. This makes it easier to configure
23890 family lists conveniently.
23892 o Minor fixes, confusing/misleading log messages:
23893 - Display correct results when reporting which versions are
23894 recommended, and how recommended they are. (Resolves bug 383.)
23895 - Inform the server operator when we decide not to advertise a
23896 DirPort due to AccountingMax enabled or a low BandwidthRate.
23897 - Only include function names in log messages for info/debug messages.
23898 For notice/warn/err, the content of the message should be clear on
23899 its own, and printing the function name only confuses users.
23900 - Remove even more protocol-related warnings from Tor server logs,
23901 such as bad TLS handshakes and malformed begin cells.
23902 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
23903 when the IP address is mapped through MapAddress to a hostname.
23904 - Fix misleading log messages: an entry guard that is "unlisted",
23905 as well as not known to be "down" (because we've never heard
23906 of it), is not therefore "up".
23908 o Minor fixes, old/obsolete behavior:
23909 - Start assuming we can use a create_fast cell if we don't know
23910 what version a router is running.
23911 - We no longer look for identity and onion keys in "identity.key" and
23912 "onion.key" -- these were replaced by secret_id_key and
23913 secret_onion_key in 0.0.8pre1.
23914 - We no longer require unrecognized directory entries to be
23916 - Drop compatibility with obsolete Tors that permit create cells
23917 to have the wrong circ_id_type.
23918 - Remove code to special-case "-cvs" ending, since it has not
23919 actually mattered since 0.0.9.
23920 - Don't re-write the fingerprint file every restart, unless it has
23923 o Minor fixes, misc client-side behavior:
23924 - Always remove expired routers and networkstatus docs before checking
23925 whether we have enough information to build circuits. (Fixes
23927 - When computing clock skew from directory HTTP headers, consider what
23928 time it was when we finished asking for the directory, not what
23930 - Make our socks5 handling more robust to broken socks clients:
23931 throw out everything waiting on the buffer in between socks
23932 handshake phases, since they can't possibly (so the theory
23933 goes) have predicted what we plan to respond to them.
23934 - Expire socks connections if they spend too long waiting for the
23935 handshake to finish. Previously we would let them sit around for
23936 days, if the connecting application didn't close them either.
23937 - And if the socks handshake hasn't started, don't send a
23938 "DNS resolve socks failed" handshake reply; just close it.
23939 - If the user asks to use invalid exit nodes, be willing to use
23941 - Track unreachable entry guards correctly: don't conflate
23942 'unreachable by us right now' with 'listed as down by the directory
23943 authorities'. With the old code, if a guard was unreachable by us
23944 but listed as running, it would clog our guard list forever.
23945 - Behave correctly in case we ever have a network with more than
23946 2GB/s total advertised capacity.
23947 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
23948 - Fix a memory leak when we ask for "all" networkstatuses and we
23949 get one we don't recognize.
23952 Changes in version 0.1.1.26 - 2006-12-14
23953 o Security bugfixes:
23954 - Stop sending the HttpProxyAuthenticator string to directory
23955 servers when directory connections are tunnelled through Tor.
23956 - Clients no longer store bandwidth history in the state file.
23957 - Do not log introduction points for hidden services if SafeLogging
23961 - Fix an assert failure when a directory authority sets
23962 AuthDirRejectUnlisted and then receives a descriptor from an
23963 unlisted router (reported by seeess).
23966 Changes in version 0.1.1.25 - 2006-11-04
23968 - When a client asks us to resolve (rather than connect to)
23969 an address, and we have a cached answer, give them the cached
23970 answer. Previously, we would give them no answer at all.
23971 - We were building exactly the wrong circuits when we predict
23972 hidden service requirements, meaning Tor would have to build all
23973 its circuits on demand.
23974 - If none of our live entry guards have a high uptime, but we
23975 require a guard with a high uptime, try adding a new guard before
23976 we give up on the requirement. This patch should make long-lived
23977 connections more stable on average.
23978 - When testing reachability of our DirPort, don't launch new
23979 tests when there's already one in progress -- unreachable
23980 servers were stacking up dozens of testing streams.
23982 o Security bugfixes:
23983 - When the user sends a NEWNYM signal, clear the client-side DNS
23984 cache too. Otherwise we continue to act on previous information.
23987 - Avoid a memory corruption bug when creating a hash table for
23989 - Avoid possibility of controller-triggered crash when misusing
23990 certain commands from a v0 controller on platforms that do not
23991 handle printf("%s",NULL) gracefully.
23992 - Avoid infinite loop on unexpected controller input.
23993 - Don't log spurious warnings when we see a circuit close reason we
23994 don't recognize; it's probably just from a newer version of Tor.
23995 - Add Vidalia to the OS X uninstaller script, so when we uninstall
23996 Tor/Privoxy we also uninstall Vidalia.
23999 Changes in version 0.1.1.24 - 2006-09-29
24001 - Allow really slow clients to not hang up five minutes into their
24002 directory downloads (suggested by Adam J. Richter).
24003 - Fix major performance regression from 0.1.0.x: instead of checking
24004 whether we have enough directory information every time we want to
24005 do something, only check when the directory information has changed.
24006 This should improve client CPU usage by 25-50%.
24007 - Don't crash if, after a server has been running for a while,
24008 it can't resolve its hostname.
24009 - When a client asks us to resolve (not connect to) an address,
24010 and we have a cached answer, give them the cached answer.
24011 Previously, we would give them no answer at all.
24014 - Allow Tor to start when RunAsDaemon is set but no logs are set.
24015 - Don't crash when the controller receives a third argument to an
24016 "extendcircuit" request.
24017 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
24018 response; fix error code when "getinfo dir/status/" fails.
24019 - Fix configure.in to not produce broken configure files with
24020 more recent versions of autoconf. Thanks to Clint for his auto*
24022 - Fix security bug on NetBSD that could allow someone to force
24023 uninitialized RAM to be sent to a server's DNS resolver. This
24024 only affects NetBSD and other platforms that do not bounds-check
24026 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
24027 methods: these are known to be buggy.
24028 - If we're a directory mirror and we ask for "all" network status
24029 documents, we would discard status documents from authorities
24030 we don't recognize.
24033 Changes in version 0.1.1.23 - 2006-07-30
24035 - Fast Tor servers, especially exit nodes, were triggering asserts
24036 due to a bug in handling the list of pending DNS resolves. Some
24037 bugs still remain here; we're hunting them.
24038 - Entry guards could crash clients by sending unexpected input.
24039 - More fixes on reachability testing: if you find yourself reachable,
24040 then don't ever make any client requests (so you stop predicting
24041 circuits), then hup or have your clock jump, then later your IP
24042 changes, you won't think circuits are working, so you won't try to
24043 test reachability, so you won't publish.
24046 - Avoid a crash if the controller does a resetconf firewallports
24047 and then a setconf fascistfirewall=1.
24048 - Avoid an integer underflow when the dir authority decides whether
24049 a router is stable: we might wrongly label it stable, and compute
24050 a slightly wrong median stability, when a descriptor is published
24052 - Fix a place where we might trigger an assert if we can't build our
24053 own server descriptor yet.
24056 Changes in version 0.1.1.22 - 2006-07-05
24058 - Fix a big bug that was causing servers to not find themselves
24059 reachable if they changed IP addresses. Since only 0.1.1.22+
24060 servers can do reachability testing correctly, now we automatically
24061 make sure to test via one of these.
24062 - Fix to allow clients and mirrors to learn directory info from
24063 descriptor downloads that get cut off partway through.
24064 - Directory authorities had a bug in deciding if a newly published
24065 descriptor was novel enough to make everybody want a copy -- a few
24066 servers seem to be publishing new descriptors many times a minute.
24068 - Fix a rare bug that was causing some servers to complain about
24069 "closing wedged cpuworkers" and skip some circuit create requests.
24070 - Make the Exit flag in directory status documents actually work.
24073 Changes in version 0.1.1.21 - 2006-06-10
24074 o Crash and assert fixes from 0.1.1.20:
24075 - Fix a rare crash on Tor servers that have enabled hibernation.
24076 - Fix a seg fault on startup for Tor networks that use only one
24077 directory authority.
24078 - Fix an assert from a race condition that occurs on Tor servers
24079 while exiting, where various threads are trying to log that they're
24080 exiting, and delete the logs, at the same time.
24081 - Make our unit tests pass again on certain obscure platforms.
24084 - Add support for building SUSE RPM packages.
24085 - Speed up initial bootstrapping for clients: if we are making our
24086 first ever connection to any entry guard, then don't mark it down
24088 - When only one Tor server in the network is labelled as a guard,
24089 and we've already picked him, we would cycle endlessly picking him
24090 again, being unhappy about it, etc. Now we specifically exclude
24091 current guards when picking a new guard.
24092 - Servers send create cells more reliably after the TLS connection
24093 is established: we were sometimes forgetting to send half of them
24094 when we had more than one pending.
24095 - If we get a create cell that asks us to extend somewhere, but the
24096 Tor server there doesn't match the expected digest, we now send
24097 a destroy cell back, rather than silently doing nothing.
24098 - Make options->RedirectExit work again.
24099 - Make cookie authentication for the controller work again.
24100 - Stop being picky about unusual characters in the arguments to
24101 mapaddress. It's none of our business.
24102 - Add a new config option "TestVia" that lets you specify preferred
24103 middle hops to use for test circuits. Perhaps this will let me
24104 debug the reachability problems better.
24106 o Log / documentation fixes:
24107 - If we're a server and some peer has a broken TLS certificate, don't
24108 log about it unless ProtocolWarnings is set, i.e., we want to hear
24109 about protocol violations by others.
24110 - Fix spelling of VirtualAddrNetwork in man page.
24111 - Add a better explanation at the top of the autogenerated torrc file
24112 about what happened to our old torrc.
24115 Changes in version 0.1.1.20 - 2006-05-23
24116 o Crash and assert fixes from 0.1.0.17:
24117 - Fix assert bug in close_logs() on exit: when we close and delete
24118 logs, remove them all from the global "logfiles" list.
24119 - Fix an assert error when we're out of space in the connection_list
24120 and we try to post a hidden service descriptor (reported by Peter
24122 - Fix a rare assert error when we've tried all intro points for
24123 a hidden service and we try fetching the service descriptor again:
24124 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
24125 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
24126 out and refuse the setconf if it would fail.
24127 - If you specify a relative torrc path and you set RunAsDaemon in
24128 your torrc, then it chdir()'s to the new directory. If you then
24129 HUP, it tries to load the new torrc location, fails, and exits.
24130 The fix: no longer allow a relative path to torrc when using -f.
24131 - Check for integer overflows in more places, when adding elements
24132 to smartlists. This could possibly prevent a buffer overflow
24133 on malicious huge inputs.
24135 o Security fixes, major:
24136 - When we're printing strings from the network, don't try to print
24137 non-printable characters. Now we're safer against shell escape
24138 sequence exploits, and also against attacks to fool users into
24139 misreading their logs.
24140 - Implement entry guards: automatically choose a handful of entry
24141 nodes and stick with them for all circuits. Only pick new guards
24142 when the ones you have are unsuitable, and if the old guards
24143 become suitable again, switch back. This will increase security
24144 dramatically against certain end-point attacks. The EntryNodes
24145 config option now provides some hints about which entry guards you
24146 want to use most; and StrictEntryNodes means to only use those.
24147 Fixes CVE-2006-0414.
24148 - Implement exit enclaves: if we know an IP address for the
24149 destination, and there's a running Tor server at that address
24150 which allows exit to the destination, then extend the circuit to
24151 that exit first. This provides end-to-end encryption and end-to-end
24152 authentication. Also, if the user wants a .exit address or enclave,
24153 use 4 hops rather than 3, and cannibalize a general circ for it
24155 - Obey our firewall options more faithfully:
24156 . If we can't get to a dirserver directly, try going via Tor.
24157 . Don't ever try to connect (as a client) to a place our
24158 firewall options forbid.
24159 . If we specify a proxy and also firewall options, obey the
24160 firewall options even when we're using the proxy: some proxies
24161 can only proxy to certain destinations.
24162 - Make clients regenerate their keys when their IP address changes.
24163 - For the OS X package's modified privoxy config file, comment
24164 out the "logfile" line so we don't log everything passed
24166 - Our TLS handshakes were generating a single public/private
24167 keypair for the TLS context, rather than making a new one for
24168 each new connection. Oops. (But we were still rotating them
24169 periodically, so it's not so bad.)
24170 - When we were cannibalizing a circuit with a particular exit
24171 node in mind, we weren't checking to see if that exit node was
24172 already present earlier in the circuit. Now we are.
24173 - Require server descriptors to list IPv4 addresses -- hostnames
24174 are no longer allowed. This also fixes potential vulnerabilities
24175 to servers providing hostnames as their address and then
24176 preferentially resolving them so they can partition users.
24177 - Our logic to decide if the OR we connected to was the right guy
24178 was brittle and maybe open to a mitm for invalid routers.
24180 o Security fixes, minor:
24181 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
24182 Ian Goldberg can prove things about our handshake protocol more
24184 - Make directory authorities generate a separate "guard" flag to
24185 mean "would make a good entry guard". Clients now honor the
24186 is_guard flag rather than looking at is_fast or is_stable.
24187 - Try to list MyFamily elements by key, not by nickname, and warn
24188 if we've not heard of a server.
24189 - Start using RAND_bytes rather than RAND_pseudo_bytes from
24190 OpenSSL. Also, reseed our entropy every hour, not just at
24191 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
24192 - Refuse server descriptors where the fingerprint line doesn't match
24193 the included identity key. Tor doesn't care, but other apps (and
24194 humans) might actually be trusting the fingerprint line.
24195 - We used to kill the circuit when we receive a relay command we
24196 don't recognize. Now we just drop that cell.
24197 - Fix a bug found by Lasse Overlier: when we were making internal
24198 circuits (intended to be cannibalized later for rendezvous and
24199 introduction circuits), we were picking them so that they had
24200 useful exit nodes. There was no need for this, and it actually
24201 aids some statistical attacks.
24202 - Start treating internal circuits and exit circuits separately.
24203 It's important to keep them separate because internal circuits
24204 have their last hops picked like middle hops, rather than like
24205 exit hops. So exiting on them will break the user's expectations.
24206 - Fix a possible way to DoS dirservers.
24207 - When the client asked for a rendezvous port that the hidden
24208 service didn't want to provide, we were sending an IP address
24209 back along with the end cell. Fortunately, it was zero. But stop
24212 o Packaging improvements:
24213 - Implement --with-libevent-dir option to ./configure. Improve
24214 search techniques to find libevent, and use those for openssl too.
24215 - Fix a couple of bugs in OpenSSL detection. Deal better when
24216 there are multiple SSLs installed with different versions.
24217 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
24218 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
24220 - Make unit tests (and other invocations that aren't the real Tor)
24221 run without launching listeners, creating subdirectories, and so on.
24222 - The OS X installer was adding a symlink for tor_resolve but
24223 the binary was called tor-resolve (reported by Thomas Hardly).
24224 - Now we can target arch and OS in rpm builds (contributed by
24225 Phobos). Also make the resulting dist-rpm filename match the
24227 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
24228 if you log to syslog and want something other than LOG_DAEMON.
24229 - Fix the torify (tsocks) config file to not use Tor for localhost
24231 - Start shipping socks-extensions.txt, tor-doc-unix.html,
24232 tor-doc-server.html, and stylesheet.css in the tarball.
24233 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
24234 They are useless now.
24235 - Add Peter Palfrader's contributed check-tor script. It lets you
24236 easily check whether a given server (referenced by nickname)
24237 is reachable by you.
24238 - Add BSD-style contributed startup script "rc.subr" from Peter
24241 o Directory improvements -- new directory protocol:
24242 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
24243 - Authorities and caches publish individual descriptors (by
24244 digest, by fingerprint, by "all", and by "tell me yours").
24245 - Clients don't download or use the old directory anymore. Now they
24246 download network-statuses from the directory authorities, and
24247 fetch individual server descriptors as needed from mirrors.
24248 - Clients don't download descriptors of non-running servers.
24249 - Download descriptors by digest, not by fingerprint. Caches try to
24250 download all listed digests from authorities; clients try to
24251 download "best" digests from caches. This avoids partitioning
24252 and isolating attacks better.
24253 - Only upload a new server descriptor when options change, 18
24254 hours have passed, uptime is reset, or bandwidth changes a lot.
24255 - Directory authorities silently throw away new descriptors that
24256 haven't changed much if the timestamps are similar. We do this to
24257 tolerate older Tor servers that upload a new descriptor every 15
24258 minutes. (It seemed like a good idea at the time.)
24259 - Clients choose directory servers from the network status lists,
24260 not from their internal list of router descriptors. Now they can
24261 go to caches directly rather than needing to go to authorities
24262 to bootstrap the first set of descriptors.
24263 - When picking a random directory, prefer non-authorities if any
24265 - Add a new flag to network-status indicating whether the server
24266 can answer v2 directory requests too.
24267 - Directory mirrors now cache up to 16 unrecognized network-status
24268 docs, so new directory authorities will be cached too.
24269 - Stop parsing, storing, or using running-routers output (but
24270 mirrors still cache and serve it).
24271 - Clients consider a threshold of "versioning" directory authorities
24272 before deciding whether to warn the user that he's obsolete.
24273 - Authorities publish separate sorted lists of recommended versions
24274 for clients and for servers.
24275 - Change DirServers config line to note which dirs are v1 authorities.
24276 - Put nicknames on the DirServer line, so we can refer to them
24277 without requiring all our users to memorize their IP addresses.
24278 - Remove option when getting directory cache to see whether they
24279 support running-routers; they all do now. Replace it with one
24280 to see whether caches support v2 stuff.
24281 - Stop listing down or invalid nodes in the v1 directory. This
24282 reduces its bulk by about 1/3, and reduces load on mirrors.
24283 - Mirrors no longer cache the v1 directory as often.
24284 - If we as a directory mirror don't know of any v1 directory
24285 authorities, then don't try to cache any v1 directories.
24287 o Other directory improvements:
24288 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
24289 fifth authoritative directory servers.
24290 - Directory authorities no longer require an open connection from
24291 a server to consider him "reachable". We need this change because
24292 when we add new directory authorities, old servers won't know not
24293 to hang up on them.
24294 - Dir authorities now do their own external reachability testing
24295 of each server, and only list as running the ones they found to
24296 be reachable. We also send back warnings to the server's logs if
24297 it uploads a descriptor that we already believe is unreachable.
24298 - Spread the directory authorities' reachability testing over the
24299 entire testing interval, so we don't try to do 500 TLS's at once
24301 - Make the "stable" router flag in network-status be the median of
24302 the uptimes of running valid servers, and make clients pay
24303 attention to the network-status flags. Thus the cutoff adapts
24304 to the stability of the network as a whole, making IRC, IM, etc
24305 connections more reliable.
24306 - Make the v2 dir's "Fast" flag based on relative capacity, just
24307 like "Stable" is based on median uptime. Name everything in the
24308 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
24309 - Retry directory requests if we fail to get an answer we like
24310 from a given dirserver (we were retrying before, but only if
24311 we fail to connect).
24312 - Return a robots.txt on our dirport to discourage google indexing.
24314 o Controller protocol improvements:
24315 - Revised controller protocol (version 1) that uses ascii rather
24316 than binary: tor/doc/control-spec.txt. Add supporting libraries
24317 in python and java and c# so you can use the controller from your
24318 applications without caring how our protocol works.
24319 - Allow the DEBUG controller event to work again. Mark certain log
24320 entries as "don't tell this to controllers", so we avoid cycles.
24321 - New controller function "getinfo accounting", to ask how
24322 many bytes we've used in this time period.
24323 - Add a "resetconf" command so you can set config options like
24324 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
24325 a config option in the torrc with no value, then it clears it
24326 entirely (rather than setting it to its default).
24327 - Add a "getinfo config-file" to tell us where torrc is. Also
24328 expose guard nodes, config options/names.
24329 - Add a "quit" command (when when using the controller manually).
24330 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
24331 stop using any currently-dirty circuits for new streams, so we
24332 don't link new actions to old actions. This also occurs on HUP
24333 or "signal reload".
24334 - If we would close a stream early (e.g. it asks for a .exit that
24335 we know would refuse it) but the LeaveStreamsUnattached config
24336 option is set by the controller, then don't close it.
24337 - Add a new controller event type "authdir_newdescs" that allows
24338 controllers to get all server descriptors that were uploaded to
24339 a router in its role as directory authority.
24340 - New controller option "getinfo desc/all-recent" to fetch the
24341 latest server descriptor for every router that Tor knows about.
24342 - Fix the controller's "attachstream 0" command to treat conn like
24343 it just connected, doing address remapping, handling .exit and
24344 .onion idioms, and so on. Now we're more uniform in making sure
24345 that the controller hears about new and closing connections.
24346 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
24347 the controller. Also, rotate dns and cpu workers if the controller
24348 changes options that will affect them; and initialize the dns
24349 worker cache tree whether or not we start out as a server.
24350 - Add a new circuit purpose 'controller' to let the controller ask
24351 for a circuit that Tor won't try to use. Extend the "extendcircuit"
24352 controller command to let you specify the purpose if you're starting
24353 a new circuit. Add a new "setcircuitpurpose" controller command to
24354 let you change a circuit's purpose after it's been created.
24355 - Let the controller ask for "getinfo dir/server/foo" so it can ask
24356 directly rather than connecting to the dir port. "getinfo
24357 dir/status/foo" also works, but currently only if your DirPort
24359 - Let the controller tell us about certain router descriptors
24360 that it doesn't want Tor to use in circuits. Implement
24361 "setrouterpurpose" and modify "+postdescriptor" to do this.
24362 - If the controller's *setconf commands fail, collect an error
24363 message in a string and hand it back to the controller -- don't
24364 just tell them to go read their logs.
24366 o Scalability, resource management, and performance:
24367 - Fix a major load balance bug: we were round-robin reading in 16 KB
24368 chunks, and servers with bandwidthrate of 20 KB, while downloading
24369 a 600 KB directory, would starve their other connections. Now we
24370 try to be a bit more fair.
24371 - Be more conservative about whether to advertise our DirPort.
24372 The main change is to not advertise if we're running at capacity
24373 and either a) we could hibernate ever or b) our capacity is low
24374 and we're using a default DirPort.
24375 - We weren't cannibalizing circuits correctly for
24376 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
24377 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
24378 build those from scratch. This should make hidden services faster.
24379 - Predict required circuits better, with an eye toward making hidden
24380 services faster on the service end.
24381 - Compress exit policies even more: look for duplicate lines and
24383 - Generate 18.0.0.0/8 address policy format in descs when we can;
24384 warn when the mask is not reducible to a bit-prefix.
24385 - There used to be two ways to specify your listening ports in a
24386 server descriptor: on the "router" line and with a separate "ports"
24387 line. Remove support for the "ports" line.
24388 - Reduce memory requirements in our structs by changing the order
24389 of fields. Replace balanced trees with hash tables. Inline
24390 bottleneck smartlist functions. Add a "Map from digest to void*"
24391 abstraction so we can do less hex encoding/decoding, and use it
24392 in router_get_by_digest(). Many other CPU and memory improvements.
24393 - Allow tor_gzip_uncompress to extract as much as possible from
24394 truncated compressed data. Try to extract as many
24395 descriptors as possible from truncated http responses (when
24396 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
24397 - Make circ->onionskin a pointer, not a static array. moria2 was using
24398 125000 circuit_t's after it had been up for a few weeks, which
24399 translates to 20+ megs of wasted space.
24400 - The private half of our EDH handshake keys are now chosen out
24401 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
24402 - Stop doing the complex voodoo overkill checking for insecure
24403 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
24404 - Do round-robin writes for TLS of at most 16 kB per write. This
24405 might be more fair on loaded Tor servers.
24406 - Do not use unaligned memory access on alpha, mips, or mipsel.
24407 It *works*, but is very slow, so we treat them as if it doesn't.
24409 o Other bugfixes and improvements:
24410 - Start storing useful information to $DATADIR/state, so we can
24411 remember things across invocations of Tor. Retain unrecognized
24412 lines so we can be forward-compatible, and write a TorVersion line
24413 so we can be backward-compatible.
24414 - If ORPort is set, Address is not explicitly set, and our hostname
24415 resolves to a private IP address, try to use an interface address
24416 if it has a public address. Now Windows machines that think of
24417 themselves as localhost can guess their address.
24418 - Regenerate our local descriptor if it's dirty and we try to use
24419 it locally (e.g. if it changes during reachability detection).
24420 This was causing some Tor servers to keep publishing the same
24421 initial descriptor forever.
24422 - Tor servers with dynamic IP addresses were needing to wait 18
24423 hours before they could start doing reachability testing using
24424 the new IP address and ports. This is because they were using
24425 the internal descriptor to learn what to test, yet they were only
24426 rebuilding the descriptor once they decided they were reachable.
24427 - It turns out we couldn't bootstrap a network since we added
24428 reachability detection in 0.1.0.1-rc. Good thing the Tor network
24429 has never gone down. Add an AssumeReachable config option to let
24430 servers and authorities bootstrap. When we're trying to build a
24431 high-uptime or high-bandwidth circuit but there aren't enough
24432 suitable servers, try being less picky rather than simply failing.
24433 - Newly bootstrapped Tor networks couldn't establish hidden service
24434 circuits until they had nodes with high uptime. Be more tolerant.
24435 - Really busy servers were keeping enough circuits open on stable
24436 connections that they were wrapping around the circuit_id
24437 space. (It's only two bytes.) This exposed a bug where we would
24438 feel free to reuse a circuit_id even if it still exists but has
24439 been marked for close. Try to fix this bug. Some bug remains.
24440 - When we fail to bind or listen on an incoming or outgoing
24441 socket, we now close it before refusing, rather than just
24442 leaking it. (Thanks to Peter Palfrader for finding.)
24443 - Fix a file descriptor leak in start_daemon().
24444 - On Windows, you can't always reopen a port right after you've
24445 closed it. So change retry_listeners() to only close and re-open
24446 ports that have changed.
24447 - Workaround a problem with some http proxies that refuse GET
24448 requests that specify "Content-Length: 0". Reported by Adrian.
24449 - Recover better from TCP connections to Tor servers that are
24450 broken but don't tell you (it happens!); and rotate TLS
24451 connections once a week.
24452 - Fix a scary-looking but apparently harmless bug where circuits
24453 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
24454 servers, and never switch to state CIRCUIT_STATE_OPEN.
24455 - Check for even more Windows version flags when writing the platform
24456 string in server descriptors, and note any we don't recognize.
24457 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
24458 get a better idea of why their circuits failed. Not used yet.
24459 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
24460 We don't use them yet, but maybe one day our DNS resolver will be
24461 able to discover them.
24462 - Let people type "tor --install" as well as "tor -install" when they
24463 want to make it an NT service.
24464 - Looks like we were never delivering deflated (i.e. compressed)
24465 running-routers lists, even when asked. Oops.
24466 - We were leaking some memory every time the client changed IPs.
24467 - Clean up more of the OpenSSL memory when exiting, so we can detect
24468 memory leaks better.
24469 - Never call free() on tor_malloc()d memory. This will help us
24470 use dmalloc to detect memory leaks.
24471 - Some Tor servers process billions of cells per day. These
24472 statistics are now uint64_t's.
24473 - Check [X-]Forwarded-For headers in HTTP requests when generating
24474 log messages. This lets people run dirservers (and caches) behind
24475 Apache but still know which IP addresses are causing warnings.
24476 - Fix minor integer overflow in calculating when we expect to use up
24477 our bandwidth allocation before hibernating.
24478 - Lower the minimum required number of file descriptors to 1000,
24479 so we can have some overhead for Valgrind on Linux, where the
24480 default ulimit -n is 1024.
24481 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
24482 and its existence is confusing some users.
24484 o Config option fixes:
24485 - Add a new config option ExitPolicyRejectPrivate which defaults
24486 to on. Now all exit policies will begin with rejecting private
24487 addresses, unless the server operator explicitly turns it off.
24488 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
24489 - Add new ReachableORAddresses and ReachableDirAddresses options
24490 that understand address policies. FascistFirewall is now a synonym
24491 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
24492 - Start calling it FooListenAddress rather than FooBindAddress,
24493 since few of our users know what it means to bind an address
24495 - If the user gave Tor an odd number of command-line arguments,
24496 we were silently ignoring the last one. Now we complain and fail.
24497 This wins the oldest-bug prize -- this bug has been present since
24498 November 2002, as released in Tor 0.0.0.
24499 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
24500 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
24501 it would silently ignore the 6668.
24502 - If we get a linelist or linelist_s config option from the torrc,
24503 e.g. ExitPolicy, and it has no value, warn and skip rather than
24504 silently resetting it to its default.
24505 - Setconf was appending items to linelists, not clearing them.
24506 - Add MyFamily to torrc.sample in the server section, so operators
24507 will be more likely to learn that it exists.
24508 - Make ContactInfo mandatory for authoritative directory servers.
24509 - MaxConn has been obsolete for a while now. Document the ConnLimit
24510 config option, which is a *minimum* number of file descriptors
24511 that must be available else Tor refuses to start.
24512 - Get rid of IgnoreVersion undocumented config option, and make us
24513 only warn, never exit, when we're running an obsolete version.
24514 - Make MonthlyAccountingStart config option truly obsolete now.
24515 - Correct the man page entry on TrackHostExitsExpire.
24516 - Let directory authorities start even if they don't specify an
24517 Address config option.
24518 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
24519 reflect the updated flags in our v2 dir protocol.
24521 o Config option features:
24522 - Add a new config option FastFirstHopPK (on by default) so clients
24523 do a trivial crypto handshake for their first hop, since TLS has
24524 already taken care of confidentiality and authentication.
24525 - Let the user set ControlListenAddress in the torrc. This can be
24526 dangerous, but there are some cases (like a secured LAN) where it
24528 - New config options to help controllers: FetchServerDescriptors
24529 and FetchHidServDescriptors for whether to fetch server
24530 info and hidserv info or let the controller do it, and
24531 PublishServerDescriptor and PublishHidServDescriptors.
24532 - Also let the controller set the __AllDirActionsPrivate config
24533 option if you want all directory fetches/publishes to happen via
24534 Tor (it assumes your controller bootstraps your circuits).
24535 - Add "HardwareAccel" config option: support for crypto hardware
24536 accelerators via OpenSSL. Off by default, until we find somebody
24537 smart who can test it for us. (It appears to produce seg faults
24538 in at least some cases.)
24539 - New config option "AuthDirRejectUnlisted" for directory authorities
24540 as a panic button: if we get flooded with unusable servers we can
24541 revert to only listing servers in the approved-routers file.
24542 - Directory authorities can now reject/invalidate by key and IP,
24543 with the config options "AuthDirInvalid" and "AuthDirReject", or
24544 by marking a fingerprint as "!reject" or "!invalid" (as its
24545 nickname) in the approved-routers file. This is useful since
24546 currently we automatically list servers as running and usable
24547 even if we know they're jerks.
24548 - Add a new config option TestSocks so people can see whether their
24549 applications are using socks4, socks4a, socks5-with-ip, or
24550 socks5-with-fqdn. This way they don't have to keep mucking
24551 with tcpdump and wondering if something got cached somewhere.
24552 - Add "private:*" as an alias in configuration for policies. Now
24553 you can simplify your exit policy rather than needing to list
24554 every single internal or nonroutable network space.
24555 - Accept "private:*" in routerdesc exit policies; not generated yet
24556 because older Tors do not understand it.
24557 - Add configuration option "V1AuthoritativeDirectory 1" which
24558 moria1, moria2, and tor26 have set.
24559 - Implement an option, VirtualAddrMask, to set which addresses
24560 get handed out in response to mapaddress requests. This works
24561 around a bug in tsocks where 127.0.0.0/8 is never socksified.
24562 - Add a new config option FetchUselessDescriptors, off by default,
24563 for when you plan to run "exitlist" on your client and you want
24564 to know about even the non-running descriptors.
24565 - SocksTimeout: How long do we let a socks connection wait
24566 unattached before we fail it?
24567 - CircuitBuildTimeout: Cull non-open circuits that were born
24568 at least this many seconds ago.
24569 - CircuitIdleTimeout: Cull open clean circuits that were born
24570 at least this many seconds ago.
24571 - New config option SafeSocks to reject all application connections
24572 using unsafe socks protocols. Defaults to off.
24574 o Improved and clearer log messages:
24575 - Reduce clutter in server logs. We're going to try to make
24576 them actually usable now. New config option ProtocolWarnings that
24577 lets you hear about how _other Tors_ are breaking the protocol. Off
24579 - Divide log messages into logging domains. Once we put some sort
24580 of interface on this, it will let people looking at more verbose
24581 log levels specify the topics they want to hear more about.
24582 - Log server fingerprint on startup, so new server operators don't
24583 have to go hunting around their filesystem for it.
24584 - Provide dire warnings to any users who set DirServer manually;
24585 move it out of torrc.sample and into torrc.complete.
24586 - Make the log message less scary when all the dirservers are
24587 temporarily unreachable.
24588 - When tor_socketpair() fails in Windows, give a reasonable
24589 Windows-style errno back.
24590 - Improve tor_gettimeofday() granularity on windows.
24591 - We were printing the number of idle dns workers incorrectly when
24593 - Handle duplicate lines in approved-routers files without warning.
24594 - We were whining about using socks4 or socks5-with-local-lookup
24595 even when it's an IP address in the "virtual" range we designed
24596 exactly for this case.
24597 - Check for named servers when looking them up by nickname;
24598 warn when we're calling a non-named server by its nickname;
24599 don't warn twice about the same name.
24600 - Downgrade the dirserver log messages when whining about
24602 - Correct "your server is reachable" log entries to indicate that
24603 it was self-testing that told us so.
24604 - If we're trying to be a Tor server and running Windows 95/98/ME
24605 as a server, explain that we'll likely crash.
24606 - Provide a more useful warn message when our onion queue gets full:
24607 the CPU is too slow or the exit policy is too liberal.
24608 - Don't warn when we receive a 503 from a dirserver/cache -- this
24609 will pave the way for them being able to refuse if they're busy.
24610 - When we fail to bind a listener, try to provide a more useful
24611 log message: e.g., "Is Tor already running?"
24612 - Only start testing reachability once we've established a
24613 circuit. This will make startup on dir authorities less noisy.
24614 - Don't try to upload hidden service descriptors until we have
24615 established a circuit.
24616 - Tor didn't warn when it failed to open a log file.
24617 - Warn when listening on a public address for socks. We suspect a
24618 lot of people are setting themselves up as open socks proxies,
24619 and they have no idea that jerks on the Internet are using them,
24620 since they simply proxy the traffic into the Tor network.
24621 - Give a useful message when people run Tor as the wrong user,
24622 rather than telling them to start chowning random directories.
24623 - Fix a harmless bug that was causing Tor servers to log
24624 "Got an end because of misc error, but we're not an AP. Closing."
24625 - Fix wrong log message when you add a "HiddenServiceNodes" config
24626 line without any HiddenServiceDir line (reported by Chris Thomas).
24627 - Directory authorities now stop whining so loudly about bad
24628 descriptors that they fetch from other dirservers. So when there's
24629 a log complaint, it's for sure from a freshly uploaded descriptor.
24630 - When logging via syslog, include the pid whenever we provide
24631 a log entry. Suggested by Todd Fries.
24632 - When we're shutting down and we do something like try to post a
24633 server descriptor or rendezvous descriptor, don't complain that
24634 we seem to be unreachable. Of course we are, we're shutting down.
24635 - Change log line for unreachability to explicitly suggest /etc/hosts
24636 as the culprit. Also make it clearer what IP address and ports we're
24637 testing for reachability.
24638 - Put quotes around user-supplied strings when logging so users are
24639 more likely to realize if they add bad characters (like quotes)
24641 - NT service patch from Matt Edman to improve error messages on Win32.
24644 Changes in version 0.1.0.17 - 2006-02-17
24645 o Crash bugfixes on 0.1.0.x:
24646 - When servers with a non-zero DirPort came out of hibernation,
24647 sometimes they would trigger an assert.
24649 o Other important bugfixes:
24650 - On platforms that don't have getrlimit (like Windows), we were
24651 artificially constraining ourselves to a max of 1024
24652 connections. Now just assume that we can handle as many as 15000
24653 connections. Hopefully this won't cause other problems.
24655 o Backported features:
24656 - When we're a server, a client asks for an old-style directory,
24657 and our write bucket is empty, don't give it to him. This way
24658 small servers can continue to serve the directory *sometimes*,
24659 without getting overloaded.
24660 - Whenever you get a 503 in response to a directory fetch, try
24661 once more. This will become important once servers start sending
24662 503's whenever they feel busy.
24663 - Fetch a new directory every 120 minutes, not every 40 minutes.
24664 Now that we have hundreds of thousands of users running the old
24665 directory algorithm, it's starting to hurt a lot.
24666 - Bump up the period for forcing a hidden service descriptor upload
24667 from 20 minutes to 1 hour.
24670 Changes in version 0.1.0.16 - 2006-01-02
24671 o Crash bugfixes on 0.1.0.x:
24672 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
24673 corrupting the heap, losing FDs, or crashing when we need to resize
24674 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
24675 - It turns out sparc64 platforms crash on unaligned memory access
24676 too -- so detect and avoid this.
24677 - Handle truncated compressed data correctly (by detecting it and
24679 - Fix possible-but-unlikely free(NULL) in control.c.
24680 - When we were closing connections, there was a rare case that
24681 stomped on memory, triggering seg faults and asserts.
24682 - Avoid potential infinite recursion when building a descriptor. (We
24683 don't know that it ever happened, but better to fix it anyway.)
24684 - We were neglecting to unlink marked circuits from soon-to-close OR
24685 connections, which caused some rare scribbling on freed memory.
24686 - Fix a memory stomping race bug when closing the joining point of two
24687 rendezvous circuits.
24688 - Fix an assert in time parsing found by Steven Murdoch.
24690 o Other bugfixes on 0.1.0.x:
24691 - When we're doing reachability testing, provide more useful log
24692 messages so the operator knows what to expect.
24693 - Do not check whether DirPort is reachable when we are suppressing
24694 advertising it because of hibernation.
24695 - When building with -static or on Solaris, we sometimes needed -ldl.
24696 - One of the dirservers (tor26) changed its IP address.
24697 - When we're deciding whether a stream has enough circuits around
24698 that can handle it, count the freshly dirty ones and not the ones
24699 that are so dirty they won't be able to handle it.
24700 - When we're expiring old circuits, we had a logic error that caused
24701 us to close new rendezvous circuits rather than old ones.
24702 - Give a more helpful log message when you try to change ORPort via
24703 the controller: you should upgrade Tor if you want that to work.
24704 - We were failing to parse Tor versions that start with "Tor ".
24705 - Tolerate faulty streams better: when a stream fails for reason
24706 exitpolicy, stop assuming that the router is lying about his exit
24707 policy. When a stream fails for reason misc, allow it to retry just
24708 as if it was resolvefailed. When a stream has failed three times,
24709 reset its failure count so we can try again and get all three tries.
24712 Changes in version 0.1.0.15 - 2005-09-23
24713 o Bugfixes on 0.1.0.x:
24714 - Reject ports 465 and 587 (spam targets) in default exit policy.
24715 - Don't crash when we don't have any spare file descriptors and we
24716 try to spawn a dns or cpu worker.
24717 - Get rid of IgnoreVersion undocumented config option, and make us
24718 only warn, never exit, when we're running an obsolete version.
24719 - Don't try to print a null string when your server finds itself to
24720 be unreachable and the Address config option is empty.
24721 - Make the numbers in read-history and write-history into uint64s,
24722 so they don't overflow and publish negatives in the descriptor.
24723 - Fix a minor memory leak in smartlist_string_remove().
24724 - We were only allowing ourselves to upload a server descriptor at
24725 most every 20 minutes, even if it changed earlier than that.
24726 - Clean up log entries that pointed to old URLs.
24729 Changes in version 0.1.0.14 - 2005-08-08
24730 o Bugfixes on 0.1.0.x:
24731 - Fix the other half of the bug with crypto handshakes
24733 - Fix an assert trigger if you send a 'signal term' via the
24734 controller when it's listening for 'event info' messages.
24737 Changes in version 0.1.0.13 - 2005-08-04
24738 o Bugfixes on 0.1.0.x:
24739 - Fix a critical bug in the security of our crypto handshakes.
24740 - Fix a size_t underflow in smartlist_join_strings2() that made
24741 it do bad things when you hand it an empty smartlist.
24742 - Fix Windows installer to ship Tor license (thanks to Aphex for
24743 pointing out this oversight) and put a link to the doc directory
24745 - Explicitly set no-unaligned-access for sparc: it turns out the
24746 new gcc's let you compile broken code, but that doesn't make it
24750 Changes in version 0.1.0.12 - 2005-07-18
24751 o New directory servers:
24752 - tor26 has changed IP address.
24754 o Bugfixes on 0.1.0.x:
24755 - Fix a possible double-free in tor_gzip_uncompress().
24756 - When --disable-threads is set, do not search for or link against
24757 pthreads libraries.
24758 - Don't trigger an assert if an authoritative directory server
24759 claims its dirport is 0.
24760 - Fix bug with removing Tor as an NT service: some people were
24761 getting "The service did not return an error." Thanks to Matt
24765 Changes in version 0.1.0.11 - 2005-06-30
24766 o Bugfixes on 0.1.0.x:
24767 - Fix major security bug: servers were disregarding their
24768 exit policies if clients behaved unexpectedly.
24769 - Make OS X init script check for missing argument, so we don't
24770 confuse users who invoke it incorrectly.
24771 - Fix a seg fault in "tor --hash-password foo".
24772 - The MAPADDRESS control command was broken.
24775 Changes in version 0.1.0.10 - 2005-06-14
24777 - Make NT services work and start on startup on Win32 (based on
24778 patch by Matt Edman). See the FAQ entry for details.
24779 - Make 'platform' string in descriptor more accurate for Win32
24780 servers, so it's not just "unknown platform".
24781 - REUSEADDR on normal platforms means you can rebind to the port
24782 right after somebody else has let it go. But REUSEADDR on Win32
24783 means you can bind to the port _even when somebody else already
24784 has it bound_! So, don't do that on Win32.
24785 - Clean up the log messages when starting on Win32 with no config
24787 - Allow seeding the RNG on Win32 even when you're not running as
24788 Administrator. If seeding the RNG on Win32 fails, quit.
24790 o Assert / crash bugs:
24791 - Refuse relay cells that claim to have a length larger than the
24792 maximum allowed. This prevents a potential attack that could read
24793 arbitrary memory (e.g. keys) from an exit server's process
24795 - If unofficial Tor clients connect and send weird TLS certs, our
24796 Tor server triggers an assert. Stop asserting, and start handling
24797 TLS errors better in other situations too.
24798 - Fix a race condition that can trigger an assert when we have a
24799 pending create cell and an OR connection attempt fails.
24802 - Use pthreads for worker processes rather than forking. This was
24803 forced because when we forked, we ended up wasting a lot of
24804 duplicate ram over time.
24805 - Also switch to foo_r versions of some library calls to allow
24806 reentry and threadsafeness.
24807 - Implement --disable-threads configure option. Disable threads on
24808 netbsd and openbsd by default, because they have no reentrant
24809 resolver functions (!), and on solaris since it has other
24811 - Fix possible bug on threading platforms (e.g. win32) which was
24812 leaking a file descriptor whenever a cpuworker or dnsworker died.
24813 - Fix a minor memory leak when somebody establishes an introduction
24814 point at your Tor server.
24815 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
24817 - Add ./configure --with-dmalloc option, to track memory leaks.
24818 - And try to free all memory on closing, so we can detect what
24821 o Protocol correctness:
24822 - When we've connected to an OR and handshaked but didn't like
24823 the result, we were closing the conn without sending destroy
24824 cells back for pending circuits. Now send those destroys.
24825 - Start sending 'truncated' cells back rather than destroy cells
24826 if the circuit closes in front of you. This means we won't have
24827 to abandon partially built circuits.
24828 - Handle changed router status correctly when dirserver reloads
24829 fingerprint file. We used to be dropping all unverified descriptors
24830 right then. The bug was hidden because we would immediately
24831 fetch a directory from another dirserver, which would include the
24832 descriptors we just dropped.
24833 - Revise tor-spec to add more/better stream end reasons.
24834 - Revise all calls to connection_edge_end to avoid sending 'misc',
24835 and to take errno into account where possible.
24836 - Client now retries when streams end early for 'hibernating' or
24837 'resource limit' reasons, rather than failing them.
24838 - Try to be more zealous about calling connection_edge_end when
24839 things go bad with edge conns in connection.c.
24841 o Robustness improvements:
24842 - Better handling for heterogeneous / unreliable nodes:
24843 - Annotate circuits with whether they aim to contain high uptime
24844 nodes and/or high capacity nodes. When building circuits, choose
24846 - This means that every single node in an intro rend circuit,
24847 not just the last one, will have a minimum uptime.
24848 - New config option LongLivedPorts to indicate application streams
24849 that will want high uptime circuits.
24850 - Servers reset uptime when a dir fetch entirely fails. This
24851 hopefully reflects stability of the server's network connectivity.
24852 - If somebody starts his tor server in Jan 2004 and then fixes his
24853 clock, don't make his published uptime be a year.
24854 - Reset published uptime when we wake up from hibernation.
24855 - Introduce a notion of 'internal' circs, which are chosen without
24856 regard to the exit policy of the last hop. Intro and rendezvous
24857 circs must be internal circs, to avoid leaking information. Resolve
24858 and connect streams can use internal circs if they want.
24859 - New circuit pooling algorithm: keep track of what destination ports
24860 we've used recently (start out assuming we'll want to use 80), and
24861 make sure to have enough circs around to satisfy these ports. Also
24862 make sure to have 2 internal circs around if we've required internal
24863 circs lately (and with high uptime if we've seen that lately too).
24864 - Turn addr_policy_compare from a tristate to a quadstate; this should
24865 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
24866 for google.com" problem.
24867 - When a client asks us for a dir mirror and we don't have one,
24868 launch an attempt to get a fresh one.
24869 - First cut at support for "create-fast" cells. Clients can use
24870 these when extending to their first hop, since the TLS already
24871 provides forward secrecy and authentication. Not enabled on
24874 o Reachability testing.
24875 - Your Tor server will automatically try to see if its ORPort and
24876 DirPort are reachable from the outside, and it won't upload its
24877 descriptor until it decides at least ORPort is reachable (when
24878 DirPort is not yet found reachable, publish it as zero).
24879 - When building testing circs for ORPort testing, use only
24880 high-bandwidth nodes, so fewer circuits fail.
24881 - Notice when our IP changes, and reset stats/uptime/reachability.
24882 - Authdirservers don't do ORPort reachability detection, since
24883 they're in clique mode, so it will be rare to find a server not
24884 already connected to them.
24885 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
24889 - Now we allow two unverified servers with the same nickname
24890 but different keys. But if a nickname is verified, only that
24891 nickname+key are allowed.
24892 - If you're an authdirserver connecting to an address:port,
24893 and it's not the OR you were expecting, forget about that
24894 descriptor. If he *was* the one you were expecting, then forget
24895 about all other descriptors for that address:port.
24896 - Allow servers to publish descriptors from 12 hours in the future.
24897 Corollary: only whine about clock skew from the dirserver if
24898 he's a trusted dirserver (since now even verified servers could
24899 have quite wrong clocks).
24900 - Require servers that use the default dirservers to have public IP
24901 addresses. We have too many servers that are configured with private
24902 IPs and their admins never notice the log entries complaining that
24903 their descriptors are being rejected.
24905 o Efficiency improvements:
24906 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
24907 and /dev/poll), and hopefully work better on Windows too.
24908 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
24909 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
24910 - Find libevent even if it's hiding in /usr/local/ and your
24911 CFLAGS and LDFLAGS don't tell you to look there.
24912 - Be able to link with libevent as a shared library (the default
24913 after 1.0d), even if it's hiding in /usr/local/lib and even
24914 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
24915 assuming you're running gcc. Otherwise fail and give a useful
24917 - Switch to a new buffer management algorithm, which tries to avoid
24918 reallocing and copying quite as much. In first tests it looks like
24919 it uses *more* memory on average, but less cpu.
24920 - Switch our internal buffers implementation to use a ring buffer,
24921 to hopefully improve performance for fast servers a lot.
24922 - Reenable the part of the code that tries to flush as soon as an
24923 OR outbuf has a full TLS record available. Perhaps this will make
24924 OR outbufs not grow as huge except in rare cases, thus saving lots
24925 of CPU time plus memory.
24926 - Improve performance for dirservers: stop re-parsing the whole
24927 directory every time you regenerate it.
24928 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
24929 it much faster to look up a circuit for each relay cell.
24930 - Remove most calls to assert_all_pending_dns_resolves_ok(),
24931 since they're eating our cpu on exit nodes.
24932 - Stop wasting time doing a case insensitive comparison for every
24933 dns name every time we do any lookup. Canonicalize the names to
24934 lowercase when you first see them.
24937 - Handle unavailable hidden services better. Handle slow or busy
24938 hidden services better.
24939 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
24940 circ as necessary, if there are any completed ones lying around
24941 when we try to launch one.
24942 - Make hidden services try to establish a rendezvous for 30 seconds
24943 after fetching the descriptor, rather than for n (where n=3)
24944 attempts to build a circuit.
24945 - Adjust maximum skew and age for rendezvous descriptors: let skew
24946 be 48 hours rather than 90 minutes.
24947 - Reject malformed .onion addresses rather then passing them on as
24948 normal web requests.
24951 - More Tor controller support. See
24952 http://tor.eff.org/doc/control-spec.txt for all the new features,
24953 including signals to emulate unix signals from any platform;
24954 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
24955 closestream; closecircuit; etc.
24956 - Encode hashed controller passwords in hex instead of base64,
24957 to make it easier to write controllers.
24958 - Revise control spec and implementation to allow all log messages to
24959 be sent to controller with their severities intact (suggested by
24960 Matt Edman). Disable debug-level logs while delivering a debug-level
24961 log to the controller, to prevent loop. Update TorControl to handle
24962 new log event types.
24964 o New config options/defaults:
24965 - Begin scrubbing sensitive strings from logs by default. Turn off
24966 the config option SafeLogging if you need to do debugging.
24967 - New exit policy: accept most low-numbered ports, rather than
24968 rejecting most low-numbered ports.
24969 - Put a note in the torrc about abuse potential with the default
24971 - Add support for CONNECTing through https proxies, with "HttpsProxy"
24973 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
24974 based on patch from Adam Langley (basic auth only).
24975 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
24976 the fast servers that have been joining lately. (Clients are now
24977 willing to load balance over up to 2 MB of advertised bandwidth
24979 - New config option MaxAdvertisedBandwidth which lets you advertise
24980 a low bandwidthrate (to not attract as many circuits) while still
24981 allowing a higher bandwidthrate in reality.
24982 - Require BandwidthRate to be at least 20kB/s for servers.
24983 - Add a NoPublish config option, so you can be a server (e.g. for
24984 testing running Tor servers in other Tor networks) without
24985 publishing your descriptor to the primary dirservers.
24986 - Add a new AddressMap config directive to rewrite incoming socks
24987 addresses. This lets you, for example, declare an implicit
24988 required exit node for certain sites.
24989 - Add a new TrackHostExits config directive to trigger addressmaps
24990 for certain incoming socks addresses -- for sites that break when
24991 your exit keeps changing (based on patch from Mike Perry).
24992 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
24993 which describes how often we retry making new circuits if current
24994 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
24995 how long we're willing to make use of an already-dirty circuit.
24996 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
24997 a config option "ShutdownWaitLength" (when using kill -INT on
24999 - Fix an edge case in parsing config options: if they say "--"
25000 on the commandline, it's not a config option (thanks weasel).
25001 - New config option DirAllowPrivateAddresses for authdirservers.
25002 Now by default they refuse router descriptors that have non-IP or
25003 private-IP addresses.
25004 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
25005 smart" default value: low for servers and high for clients.
25006 - Some people were putting "Address " in their torrc, and they had
25007 a buggy resolver that resolved " " to 0.0.0.0. Oops.
25008 - If DataDir is ~/.tor, and that expands to /.tor, then default to
25009 LOCALSTATEDIR/tor instead.
25010 - Implement --verify-config command-line option to check if your torrc
25011 is valid without actually launching Tor.
25013 o Logging improvements:
25014 - When dirservers refuse a server descriptor, we now log its
25015 contactinfo, platform, and the poster's IP address.
25016 - Only warn once per nickname from add_nickname_list_to_smartlist()
25017 per failure, so an entrynode or exitnode choice that's down won't
25019 - When we're connecting to an OR and he's got a different nickname/key
25020 than we were expecting, only complain loudly if we're an OP or a
25021 dirserver. Complaining loudly to the OR admins just confuses them.
25022 - Whine at you if you're a server and you don't set your contactinfo.
25023 - Warn when exit policy implicitly allows local addresses.
25024 - Give a better warning when some other server advertises an
25025 ORPort that is actually an apache running ssl.
25026 - If we get an incredibly skewed timestamp from a dirserver mirror
25027 that isn't a verified OR, don't warn -- it's probably him that's
25029 - When a dirserver causes you to give a warn, mention which dirserver
25031 - Initialize libevent later in the startup process, so the logs are
25032 already established by the time we start logging libevent warns.
25033 - Use correct errno on win32 if libevent fails.
25034 - Check and warn about known-bad/slow libevent versions.
25035 - Stop warning about sigpipes in the logs. We're going to
25036 pretend that getting these occasionally is normal and fine.
25038 o New contrib scripts:
25039 - New experimental script tor/contrib/exitlist: a simple python
25040 script to parse directories and find Tor nodes that exit to listed
25042 - New experimental script tor/contrib/ExerciseServer.py (needs more
25043 work) that uses the controller interface to build circuits and
25044 fetch pages over them. This will help us bootstrap servers that
25045 have lots of capacity but haven't noticed it yet.
25046 - New experimental script tor/contrib/PathDemo.py (needs more work)
25047 that uses the controller interface to let you choose whole paths
25049 "<hostname>.<path,separated by dots>.<length of path>.path"
25050 - New contributed script "privoxy-tor-toggle" to toggle whether
25051 Privoxy uses Tor. Seems to be configured for Debian by default.
25052 - Have torctl.in/tor.sh.in check for location of su binary (needed
25056 - chdir() to your datadirectory at the *end* of the daemonize process,
25057 not the beginning. This was a problem because the first time you
25058 run tor, if your datadir isn't there, and you have runasdaemon set
25059 to 1, it will try to chdir to it before it tries to create it. Oops.
25060 - Fix several double-mark-for-close bugs, e.g. where we were finding
25061 a conn for a cell even if that conn is already marked for close.
25062 - Stop most cases of hanging up on a socks connection without sending
25064 - Fix a bug in the RPM package: set home directory for _tor to
25065 something more reasonable when first installing.
25066 - Stop putting nodename in the Platform string in server descriptors.
25067 It doesn't actually help, and it is confusing/upsetting some people.
25068 - When using preferred entry or exit nodes, ignore whether the
25069 circuit wants uptime or capacity. They asked for the nodes, they
25071 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
25072 artificially capped at 500kB.
25073 - Cache local dns resolves correctly even when they're .exit
25075 - If we're hibernating and we get a SIGINT, exit immediately.
25076 - tor-resolve requests were ignoring .exit if there was a working circuit
25077 they could use instead.
25078 - Pay more attention to the ClientOnly config option.
25079 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
25080 installer screens; and don't put stuff into StartupItems unless
25081 the user asks you to.
25084 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
25085 rather than just rejecting it.
25086 - If our clock jumps forward by 100 seconds or more, assume something
25087 has gone wrong with our network and abandon all not-yet-used circs.
25088 - When an application is using socks5, give him the whole variety of
25089 potential socks5 responses (connect refused, host unreachable, etc),
25090 rather than just "success" or "failure".
25091 - A more sane version numbering system. See
25092 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
25093 - Change version parsing logic: a version is "obsolete" if it is not
25094 recommended and (1) there is a newer recommended version in the
25095 same series, or (2) there are no recommended versions in the same
25096 series, but there are some recommended versions in a newer series.
25097 A version is "new" if it is newer than any recommended version in
25099 - Report HTTP reasons to client when getting a response from directory
25100 servers -- so you can actually know what went wrong.
25101 - Reject odd-looking addresses at the client (e.g. addresses that
25102 contain a colon), rather than having the server drop them because
25104 - Stop publishing socksport in the directory, since it's not
25105 actually meant to be public. For compatibility, publish a 0 there
25107 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
25108 cookies to disk and doesn't log each web request to disk. (Thanks
25109 to Brett Carrington for pointing this out.)
25110 - Add OSX uninstall instructions. An actual uninstall script will
25112 - Add "opt hibernating 1" to server descriptor to make it clearer
25113 whether the server is hibernating.
25116 Changes in version 0.0.9.10 - 2005-06-16
25117 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
25118 - Refuse relay cells that claim to have a length larger than the
25119 maximum allowed. This prevents a potential attack that could read
25120 arbitrary memory (e.g. keys) from an exit server's process
25124 Changes in version 0.0.9.9 - 2005-04-23
25125 o Bugfixes on 0.0.9.x:
25126 - If unofficial Tor clients connect and send weird TLS certs, our
25127 Tor server triggers an assert. This release contains a minimal
25128 backport from the broader fix that we put into 0.1.0.4-rc.
25131 Changes in version 0.0.9.8 - 2005-04-07
25132 o Bugfixes on 0.0.9.x:
25133 - We have a bug that I haven't found yet. Sometimes, very rarely,
25134 cpuworkers get stuck in the 'busy' state, even though the cpuworker
25135 thinks of itself as idle. This meant that no new circuits ever got
25136 established. Here's a workaround to kill any cpuworker that's been
25137 busy for more than 100 seconds.
25140 Changes in version 0.0.9.7 - 2005-04-01
25141 o Bugfixes on 0.0.9.x:
25142 - Fix another race crash bug (thanks to Glenn Fink for reporting).
25143 - Compare identity to identity, not to nickname, when extending to
25144 a router not already in the directory. This was preventing us from
25145 extending to unknown routers. Oops.
25146 - Make sure to create OS X Tor user in <500 range, so we aren't
25147 creating actual system users.
25148 - Note where connection-that-hasn't-sent-end was marked, and fix
25149 a few really loud instances of this harmless bug (it's fixed more
25153 Changes in version 0.0.9.6 - 2005-03-24
25154 o Bugfixes on 0.0.9.x (crashes and asserts):
25155 - Add new end stream reasons to maintenance branch. Fix bug where
25156 reason (8) could trigger an assert. Prevent bug from recurring.
25157 - Apparently win32 stat wants paths to not end with a slash.
25158 - Fix assert triggers in assert_cpath_layer_ok(), where we were
25159 blowing away the circuit that conn->cpath_layer points to, then
25160 checking to see if the circ is well-formed. Backport check to make
25161 sure we dont use the cpath on a closed connection.
25162 - Prevent circuit_resume_edge_reading_helper() from trying to package
25163 inbufs for marked-for-close streams.
25164 - Don't crash on hup if your options->address has become unresolvable.
25165 - Some systems (like OS X) sometimes accept() a connection and tell
25166 you the remote host is 0.0.0.0:0. If this happens, due to some
25167 other mis-features, we get confused; so refuse the conn for now.
25169 o Bugfixes on 0.0.9.x (other):
25170 - Fix harmless but scary "Unrecognized content encoding" warn message.
25171 - Add new stream error reason: TORPROTOCOL reason means "you are not
25172 speaking a version of Tor I understand; say bye-bye to your stream."
25173 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
25174 into the future, now that we are more tolerant of skew. This
25175 resolves a bug where a Tor server would refuse to cache a directory
25176 because all the directories it gets are too far in the future;
25177 yet the Tor server never logs any complaints about clock skew.
25178 - Mac packaging magic: make man pages useable, and do not overwrite
25179 existing torrc files.
25180 - Make OS X log happily to /var/log/tor/tor.log
25183 Changes in version 0.0.9.5 - 2005-02-22
25184 o Bugfixes on 0.0.9.x:
25185 - Fix an assert race at exit nodes when resolve requests fail.
25186 - Stop picking unverified dir mirrors--it only leads to misery.
25187 - Patch from Matt Edman to make NT services work better. Service
25188 support is still not compiled into the executable by default.
25189 - Patch from Dmitri Bely so the Tor service runs better under
25190 the win32 SYSTEM account.
25191 - Make tor-resolve actually work (?) on Win32.
25192 - Fix a sign bug when getrlimit claims to have 4+ billion
25193 file descriptors available.
25194 - Stop refusing to start when bandwidthburst == bandwidthrate.
25195 - When create cells have been on the onion queue more than five
25196 seconds, just send back a destroy and take them off the list.
25199 Changes in version 0.0.9.4 - 2005-02-03
25200 o Bugfixes on 0.0.9:
25201 - Fix an assert bug that took down most of our servers: when
25202 a server claims to have 1 GB of bandwidthburst, don't
25204 - Don't crash as badly if we have spawned the max allowed number
25205 of dnsworkers, or we're out of file descriptors.
25206 - Block more file-sharing ports in the default exit policy.
25207 - MaxConn is now automatically set to the hard limit of max
25208 file descriptors we're allowed (ulimit -n), minus a few for
25210 - Give a clearer message when servers need to raise their
25211 ulimit -n when they start running out of file descriptors.
25212 - SGI Compatibility patches from Jan Schaumann.
25213 - Tolerate a corrupt cached directory better.
25214 - When a dirserver hasn't approved your server, list which one.
25215 - Go into soft hibernation after 95% of the bandwidth is used,
25216 not 99%. This is especially important for daily hibernators who
25217 have a small accounting max. Hopefully it will result in fewer
25218 cut connections when the hard hibernation starts.
25219 - Load-balance better when using servers that claim more than
25220 800kB/s of capacity.
25221 - Make NT services work (experimental, only used if compiled in).
25224 Changes in version 0.0.9.3 - 2005-01-21
25225 o Bugfixes on 0.0.9:
25226 - Backport the cpu use fixes from main branch, so busy servers won't
25227 need as much processor time.
25228 - Work better when we go offline and then come back, or when we
25229 run Tor at boot before the network is up. We do this by
25230 optimistically trying to fetch a new directory whenever an
25231 application request comes in and we think we're offline -- the
25232 human is hopefully a good measure of when the network is back.
25233 - Backport some minimal hidserv bugfixes: keep rend circuits open as
25234 long as you keep using them; actually publish hidserv descriptors
25235 shortly after they change, rather than waiting 20-40 minutes.
25236 - Enable Mac startup script by default.
25237 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
25238 - When you update AllowUnverifiedNodes or FirewallPorts via the
25239 controller's setconf feature, we were always appending, never
25241 - When you update HiddenServiceDir via setconf, it was screwing up
25242 the order of reading the lines, making it fail.
25243 - Do not rewrite a cached directory back to the cache; otherwise we
25244 will think it is recent and not fetch a newer one on startup.
25245 - Workaround for webservers that lie about Content-Encoding: Tor
25246 now tries to autodetect compressed directories and compression
25247 itself. This lets us Proxypass dir fetches through apache.
25250 Changes in version 0.0.9.2 - 2005-01-04
25251 o Bugfixes on 0.0.9 (crashes and asserts):
25252 - Fix an assert on startup when the disk is full and you're logging
25254 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
25255 style address, then we'd crash.
25256 - Fix an assert trigger when the running-routers string we get from
25257 a dirserver is broken.
25258 - Make worker threads start and run on win32. Now win32 servers
25260 - Bandaid (not actually fix, but now it doesn't crash) an assert
25261 where the dns worker dies mysteriously and the main Tor process
25262 doesn't remember anything about the address it was resolving.
25264 o Bugfixes on 0.0.9 (Win32):
25265 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
25266 name out of the warning/assert messages.
25267 - Fix a superficial "unhandled error on read" bug on win32.
25268 - The win32 installer no longer requires a click-through for our
25269 license, since our Free Software license grants rights but does not
25271 - Win32: When connecting to a dirserver fails, try another one
25272 immediately. (This was already working for non-win32 Tors.)
25273 - Stop trying to parse $HOME on win32 when hunting for default
25275 - Make tor-resolve.c work on win32 by calling network_init().
25277 o Bugfixes on 0.0.9 (other):
25278 - Make 0.0.9.x build on Solaris again.
25279 - Due to a fencepost error, we were blowing away the \n when reporting
25280 confvalue items in the controller. So asking for multiple config
25281 values at once couldn't work.
25282 - When listing circuits that are pending on an opening OR connection,
25283 if we're an OR we were listing circuits that *end* at us as
25284 being pending on every listener, dns/cpu worker, etc. Stop that.
25285 - Dirservers were failing to create 'running-routers' or 'directory'
25286 strings if we had more than some threshold of routers. Fix them so
25287 they can handle any number of routers.
25288 - Fix a superficial "Duplicate mark for close" bug.
25289 - Stop checking for clock skew for OR connections, even for servers.
25290 - Fix a fencepost error that was chopping off the last letter of any
25291 nickname that is the maximum allowed nickname length.
25292 - Update URLs in log messages so they point to the new website.
25293 - Fix a potential problem in mangling server private keys while
25294 writing to disk (not triggered yet, as far as we know).
25295 - Include the licenses for other free software we include in Tor,
25296 now that we're shipping binary distributions more regularly.
25299 Changes in version 0.0.9.1 - 2004-12-15
25300 o Bugfixes on 0.0.9:
25301 - Make hibernation actually work.
25302 - Make HashedControlPassword config option work.
25303 - When we're reporting event circuit status to a controller,
25304 don't use the stream status code.
25307 Changes in version 0.0.9 - 2004-12-12
25308 o Bugfixes on 0.0.8.1 (Crashes and asserts):
25309 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
25310 write() call will fail and we handle it there.
25311 - When we run out of disk space, or other log writing error, don't
25312 crash. Just stop logging to that log and continue.
25313 - Fix isspace() and friends so they still make Solaris happy
25314 but also so they don't trigger asserts on win32.
25315 - Fix assert failure on malformed socks4a requests.
25316 - Fix an assert bug where a hidden service provider would fail if
25317 the first hop of his rendezvous circuit was down.
25318 - Better handling of size_t vs int, so we're more robust on 64
25321 o Bugfixes on 0.0.8.1 (Win32):
25322 - Make windows sockets actually non-blocking (oops), and handle
25323 win32 socket errors better.
25324 - Fix parse_iso_time on platforms without strptime (eg win32).
25325 - win32: when being multithreaded, leave parent fdarray open.
25326 - Better handling of winsock includes on non-MSV win32 compilers.
25327 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
25329 - Make unit tests work on win32.
25331 o Bugfixes on 0.0.8.1 (Path selection and streams):
25332 - Calculate timeout for waiting for a connected cell from the time
25333 we sent the begin cell, not from the time the stream started. If
25334 it took a long time to establish the circuit, we would time out
25335 right after sending the begin cell.
25336 - Fix router_compare_addr_to_addr_policy: it was not treating a port
25337 of * as always matching, so we were picking reject *:* nodes as
25338 exit nodes too. Oops.
25339 - When read() failed on a stream, we would close it without sending
25340 back an end. So 'connection refused' would simply be ignored and
25341 the user would get no response.
25342 - Stop a sigpipe: when an 'end' cell races with eof from the app,
25343 we shouldn't hold-open-until-flush if the eof arrived first.
25344 - Let resolve conns retry/expire also, rather than sticking around
25346 - Fix more dns related bugs: send back resolve_failed and end cells
25347 more reliably when the resolve fails, rather than closing the
25348 circuit and then trying to send the cell. Also attach dummy resolve
25349 connections to a circuit *before* calling dns_resolve(), to fix
25350 a bug where cached answers would never be sent in RESOLVED cells.
25352 o Bugfixes on 0.0.8.1 (Circuits):
25353 - Finally fix a bug that's been plaguing us for a year:
25354 With high load, circuit package window was reaching 0. Whenever
25355 we got a circuit-level sendme, we were reading a lot on each
25356 socket, but only writing out a bit. So we would eventually reach
25357 eof. This would be noticed and acted on even when there were still
25358 bytes sitting in the inbuf.
25359 - Use identity comparison, not nickname comparison, to choose which
25360 half of circuit-ID-space each side gets to use. This is needed
25361 because sometimes we think of a router as a nickname, and sometimes
25362 as a hex ID, and we can't predict what the other side will do.
25364 o Bugfixes on 0.0.8.1 (Other):
25365 - Fix a whole slew of memory leaks.
25366 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
25367 - If we are using select, make sure we stay within FD_SETSIZE.
25368 - When poll() is interrupted, we shouldn't believe the revents values.
25369 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
25370 and smartlist_len, which are two major profiling offenders.
25371 - If do_hup fails, actually notice.
25372 - Flush the log file descriptor after we print "Tor opening log file",
25373 so we don't see those messages days later.
25374 - Hidden service operators now correctly handle version 1 style
25375 INTRODUCE1 cells (nobody generates them still, so not a critical
25377 - Handle more errnos from accept() without closing the listener.
25378 Some OpenBSD machines were closing their listeners because
25379 they ran out of file descriptors.
25380 - Some people had wrapped their tor client/server in a script
25381 that would restart it whenever it died. This did not play well
25382 with our "shut down if your version is obsolete" code. Now people
25383 don't fetch a new directory if their local cached version is
25385 - Make our autogen.sh work on ksh as well as bash.
25386 - Better torrc example lines for dirbindaddress and orbindaddress.
25387 - Improved bounds checking on parsed ints (e.g. config options and
25388 the ones we find in directories.)
25389 - Stop using separate defaults for no-config-file and
25390 empty-config-file. Now you have to explicitly turn off SocksPort,
25391 if you don't want it open.
25392 - We were starting to daemonize before we opened our logs, so if
25393 there were any problems opening logs, we would complain to stderr,
25394 which wouldn't work, and then mysteriously exit.
25395 - If a verified OR connects to us before he's uploaded his descriptor,
25396 or we verify him and hup but he still has the original TLS
25397 connection, then conn->nickname is still set like he's unverified.
25399 o Code security improvements, inspired by Ilja:
25400 - tor_snprintf wrapper over snprintf with consistent (though not C99)
25402 - Replace sprintf with tor_snprintf. (I think they were all safe, but
25404 - Replace strcpy/strncpy with strlcpy in more places.
25405 - Avoid strcat; use tor_snprintf or strlcat instead.
25407 o Features (circuits and streams):
25408 - New circuit building strategy: keep a list of ports that we've
25409 used in the past 6 hours, and always try to have 2 circuits open
25410 or on the way that will handle each such port. Seed us with port
25411 80 so web users won't complain that Tor is "slow to start up".
25412 - Make kill -USR1 dump more useful stats about circuits.
25413 - When warning about retrying or giving up, print the address, so
25414 the user knows which one it's talking about.
25415 - If you haven't used a clean circuit in an hour, throw it away,
25416 just to be on the safe side. (This means after 6 hours a totally
25417 unused Tor client will have no circuits open.)
25418 - Support "foo.nickname.exit" addresses, to let Alice request the
25419 address "foo" as viewed by exit node "nickname". Based on a patch
25420 from Geoff Goodell.
25421 - If your requested entry or exit node has advertised bandwidth 0,
25423 - Be more greedy about filling up relay cells -- we try reading again
25424 once we've processed the stuff we read, in case enough has arrived
25425 to fill the last cell completely.
25426 - Refuse application socks connections to port 0.
25427 - Use only 0.0.9pre1 and later servers for resolve cells.
25429 o Features (bandwidth):
25430 - Hibernation: New config option "AccountingMax" lets you
25431 set how many bytes per month (in each direction) you want to
25432 allow your server to consume. Rather than spreading those
25433 bytes out evenly over the month, we instead hibernate for some
25434 of the month and pop up at a deterministic time, work until
25435 the bytes are consumed, then hibernate again. Config option
25436 "MonthlyAccountingStart" lets you specify which day of the month
25437 your billing cycle starts on.
25438 - Implement weekly/monthly/daily accounting: now you specify your
25439 hibernation properties by
25440 AccountingMax N bytes|KB|MB|GB|TB
25441 AccountingStart day|week|month [day] HH:MM
25442 Defaults to "month 1 0:00".
25443 - Let bandwidth and interval config options be specified as 5 bytes,
25444 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
25446 o Features (directories):
25447 - New "router-status" line in directory, to better bind each verified
25448 nickname to its identity key.
25449 - Clients can ask dirservers for /dir.z to get a compressed version
25450 of the directory. Only works for servers running 0.0.9, of course.
25451 - Make clients cache directories and use them to seed their router
25452 lists at startup. This means clients have a datadir again.
25453 - Respond to content-encoding headers by trying to uncompress as
25455 - Clients and servers now fetch running-routers; cache
25456 running-routers; compress running-routers; serve compressed
25458 - Make moria2 advertise a dirport of 80, so people behind firewalls
25459 will be able to get a directory.
25460 - Http proxy support
25461 - Dirservers translate requests for http://%s:%d/x to /x
25462 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
25463 be routed through this host.
25464 - Clients ask for /tor/x rather than /x for new enough dirservers.
25465 This way we can one day coexist peacefully with apache.
25466 - Clients specify a "Host: %s%d" http header, to be compatible
25467 with more proxies, and so running squid on an exit node can work.
25468 - Protect dirservers from overzealous descriptor uploading -- wait
25469 10 seconds after directory gets dirty, before regenerating.
25471 o Features (packages and install):
25472 - Add NSI installer contributed by J Doe.
25473 - Apply NT service patch from Osamu Fujino. Still needs more work.
25474 - Commit VC6 and VC7 workspace/project files.
25475 - Commit a tor.spec for making RPM files, with help from jbash.
25476 - Add contrib/torctl.in contributed by Glenn Fink.
25477 - Make expand_filename handle ~ and ~username.
25478 - Use autoconf to enable largefile support where necessary. Use
25479 ftello where available, since ftell can fail at 2GB.
25480 - Ship src/win32/ in the tarball, so people can use it to build.
25481 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
25484 o Features (ui controller):
25485 - Control interface: a separate program can now talk to your
25486 client/server over a socket, and get/set config options, receive
25487 notifications of circuits and streams starting/finishing/dying,
25488 bandwidth used, etc. The next step is to get some GUIs working.
25489 Let us know if you want to help out. See doc/control-spec.txt .
25490 - Ship a contrib/tor-control.py as an example script to interact
25491 with the control port.
25492 - "tor --hash-password zzyxz" will output a salted password for
25493 use in authenticating to the control interface.
25494 - Implement the control-spec's SAVECONF command, to write your
25495 configuration to torrc.
25496 - Get cookie authentication for the controller closer to working.
25497 - When set_conf changes our server descriptor, upload a new copy.
25498 But don't upload it too often if there are frequent changes.
25500 o Features (config and command-line):
25501 - Deprecate unofficial config option abbreviations, and abbreviations
25502 not on the command line.
25503 - Configuration infrastructure support for warning on obsolete
25505 - Give a slightly more useful output for "tor -h".
25506 - Break DirFetchPostPeriod into:
25507 - DirFetchPeriod for fetching full directory,
25508 - StatusFetchPeriod for fetching running-routers,
25509 - DirPostPeriod for posting server descriptor,
25510 - RendPostPeriod for posting hidden service descriptors.
25511 - New log format in config:
25512 "Log minsev[-maxsev] stdout|stderr|syslog" or
25513 "Log minsev[-maxsev] file /var/foo"
25514 - DirPolicy config option, to let people reject incoming addresses
25515 from their dirserver.
25516 - "tor --list-fingerprint" will list your identity key fingerprint
25518 - Make tor --version --version dump the cvs Id of every file.
25519 - New 'MyFamily nick1,...' config option for a server to
25520 specify other servers that shouldn't be used in the same circuit
25521 with it. Only believed if nick1 also specifies us.
25522 - New 'NodeFamily nick1,nick2,...' config option for a client to
25523 specify nodes that it doesn't want to use in the same circuit.
25524 - New 'Redirectexit pattern address:port' config option for a
25525 server to redirect exit connections, e.g. to a local squid.
25526 - Add "pass" target for RedirectExit, to make it easier to break
25527 out of a sequence of RedirectExit rules.
25528 - Make the dirservers file obsolete.
25529 - Include a dir-signing-key token in directories to tell the
25530 parsing entity which key is being used to sign.
25531 - Remove the built-in bulky default dirservers string.
25532 - New config option "Dirserver %s:%d [fingerprint]", which can be
25533 repeated as many times as needed. If no dirservers specified,
25534 default to moria1,moria2,tor26.
25535 - Make 'Routerfile' config option obsolete.
25536 - Discourage people from setting their dirfetchpostperiod more often
25537 than once per minute.
25539 o Features (other):
25540 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
25541 get back to normal.)
25542 - Accept *:706 (silc) in default exit policy.
25543 - Implement new versioning format for post 0.1.
25544 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
25545 log more informatively.
25546 - Check clock skew for verified servers, but allow unverified
25547 servers and clients to have any clock skew.
25548 - Make sure the hidden service descriptors are at a random offset
25549 from each other, to hinder linkability.
25550 - Clients now generate a TLS cert too, in preparation for having
25551 them act more like real nodes.
25552 - Add a pure-C tor-resolve implementation.
25553 - Use getrlimit and friends to ensure we can reach MaxConn (currently
25554 1024) file descriptors.
25555 - Raise the max dns workers from 50 to 100.
25558 Changes in version 0.0.8.1 - 2004-10-13
25560 - Fix a seg fault that can be triggered remotely for Tor
25561 clients/servers with an open dirport.
25562 - Fix a rare assert trigger, where routerinfos for entries in
25563 our cpath would expire while we're building the path.
25564 - Fix a bug in OutboundBindAddress so it (hopefully) works.
25565 - Fix a rare seg fault for people running hidden services on
25566 intermittent connections.
25567 - Fix a bug in parsing opt keywords with objects.
25568 - Fix a stale pointer assert bug when a stream detaches and
25570 - Fix a string format vulnerability (probably not exploitable)
25571 in reporting stats locally.
25572 - Fix an assert trigger: sometimes launching circuits can fail
25573 immediately, e.g. because too many circuits have failed recently.
25574 - Fix a compile warning on 64 bit platforms.
25577 Changes in version 0.0.8 - 2004-08-25
25579 - Made our unit tests compile again on OpenBSD 3.5, and tor
25580 itself compile again on OpenBSD on a sparc64.
25581 - We were neglecting milliseconds when logging on win32, so
25582 everything appeared to happen at the beginning of each second.
25583 - Check directory signature _before_ you decide whether you're
25584 you're running an obsolete version and should exit.
25585 - Check directory signature _before_ you parse the running-routers
25586 list to decide who's running.
25587 - Check return value of fclose while writing to disk, so we don't
25588 end up with broken files when servers run out of disk space.
25589 - Port it to SunOS 5.9 / Athena
25590 - Fix two bugs in saving onion keys to disk when rotating, so
25591 hopefully we'll get fewer people using old onion keys.
25592 - Remove our mostly unused -- and broken -- hex_encode()
25593 function. Use base16_encode() instead. (Thanks to Timo Lindfors
25594 for pointing out this bug.)
25595 - Only pick and establish intro points after we've gotten a
25597 - Fix assert triggers: if the other side returns an address 0.0.0.0,
25598 don't put it into the client dns cache.
25599 - If a begin failed due to exit policy, but we believe the IP
25600 address should have been allowed, switch that router to exitpolicy
25601 reject *:* until we get our next directory.
25603 o Protocol changes:
25604 - 'Extend' relay cell payloads now include the digest of the
25605 intended next hop's identity key. Now we can verify that we're
25606 extending to the right router, and also extend to routers we
25607 hadn't heard of before.
25610 - Tor nodes can now act as relays (with an advertised ORPort)
25611 without being manually verified by the dirserver operators.
25612 - Uploaded descriptors of unverified routers are now accepted
25613 by the dirservers, and included in the directory.
25614 - Verified routers are listed by nickname in the running-routers
25615 list; unverified routers are listed as "$<fingerprint>".
25616 - We now use hash-of-identity-key in most places rather than
25617 nickname or addr:port, for improved security/flexibility.
25618 - AllowUnverifiedNodes config option to let circuits choose no-name
25619 routers in entry,middle,exit,introduction,rendezvous positions.
25620 Allow middle and rendezvous positions by default.
25621 - When picking unverified routers, skip those with low uptime and/or
25622 low bandwidth, depending on what properties you care about.
25623 - ClientOnly option for nodes that never want to become servers.
25624 - Directory caching.
25625 - "AuthoritativeDir 1" option for the official dirservers.
25626 - Now other nodes (clients and servers) will cache the latest
25627 directory they've pulled down.
25628 - They can enable their DirPort to serve it to others.
25629 - Clients will pull down a directory from any node with an open
25630 DirPort, and check the signature/timestamp correctly.
25631 - Authoritative dirservers now fetch directories from other
25632 authdirservers, to stay better synced.
25633 - Running-routers list tells who's down also, along with noting
25634 if they're verified (listed by nickname) or unverified (listed
25636 - Allow dirservers to serve running-router list separately.
25637 This isn't used yet.
25638 - You can now fetch $DIRURL/running-routers to get just the
25639 running-routers line, not the whole descriptor list. (But
25640 clients don't use this yet.)
25641 - Clients choose nodes proportional to advertised bandwidth.
25642 - Clients avoid using nodes with low uptime as introduction points.
25643 - Handle servers with dynamic IP addresses: don't just replace
25644 options->Address with the resolved one at startup, and
25645 detect our address right before we make a routerinfo each time.
25646 - 'FascistFirewall' option to pick dirservers and ORs on specific
25647 ports; plus 'FirewallPorts' config option to tell FascistFirewall
25648 which ports are open. (Defaults to 80,443)
25649 - Try other dirservers immediately if the one you try is down. This
25650 should tolerate down dirservers better now.
25651 - ORs connect-on-demand to other ORs
25652 - If you get an extend cell to an OR you're not connected to,
25653 connect, handshake, and forward the create cell.
25654 - The authoritative dirservers stay connected to everybody,
25655 and everybody stays connected to 0.0.7 servers, but otherwise
25656 clients/servers expire unused connections after 5 minutes.
25657 - When servers get a sigint, they delay 30 seconds (refusing new
25658 connections) then exit. A second sigint causes immediate exit.
25659 - File and name management:
25660 - Look for .torrc if no CONFDIR "torrc" is found.
25661 - If no datadir is defined, then choose, make, and secure ~/.tor
25663 - If torrc not found, exitpolicy reject *:*.
25664 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
25665 - If no nickname is defined, derive default from hostname.
25666 - Rename secret key files, e.g. identity.key -> secret_id_key,
25667 to discourage people from mailing their identity key to tor-ops.
25668 - Refuse to build a circuit before the directory has arrived --
25669 it won't work anyway, since you won't know the right onion keys
25671 - Parse tor version numbers so we can do an is-newer-than check
25672 rather than an is-in-the-list check.
25673 - New socks command 'resolve', to let us shim gethostbyname()
25675 - A 'tor_resolve' script to access the socks resolve functionality.
25676 - A new socks-extensions.txt doc file to describe our
25677 interpretation and extensions to the socks protocols.
25678 - Add a ContactInfo option, which gets published in descriptor.
25679 - Write tor version at the top of each log file
25680 - New docs in the tarball:
25682 - Document that you should proxy your SSL traffic too.
25683 - Log a warning if the user uses an unsafe socks variant, so people
25684 are more likely to learn about privoxy or socat.
25685 - Log a warning if you're running an unverified server, to let you
25686 know you might want to get it verified.
25687 - Change the default exit policy to reject the default edonkey,
25688 kazaa, gnutella ports.
25689 - Add replace_file() to util.[ch] to handle win32's rename().
25690 - Publish OR uptime in descriptor (and thus in directory) too.
25691 - Remember used bandwidth (both in and out), and publish 15-minute
25692 snapshots for the past day into our descriptor.
25693 - Be more aggressive about trying to make circuits when the network
25694 has changed (e.g. when you unsuspend your laptop).
25695 - Check for time skew on http headers; report date in response to
25697 - If the entrynode config line has only one node, don't pick it as
25699 - Add strict{entry|exit}nodes config options. If set to 1, then
25700 we refuse to build circuits that don't include the specified entry
25702 - OutboundBindAddress config option, to bind to a specific
25703 IP address for outgoing connect()s.
25704 - End truncated log entries (e.g. directories) with "[truncated]".
25707 Changes in version 0.0.7.3 - 2004-08-12
25708 o Stop dnsworkers from triggering an assert failure when you
25709 ask them to resolve the host "".
25712 Changes in version 0.0.7.2 - 2004-07-07
25713 o A better fix for the 0.0.0.0 problem, that will hopefully
25714 eliminate the remaining related assertion failures.
25717 Changes in version 0.0.7.1 - 2004-07-04
25718 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
25719 since internally we use 0.0.0.0 to signify "not yet resolved".
25722 Changes in version 0.0.7 - 2004-06-07
25723 o Fixes for crashes and other obnoxious bugs:
25724 - Fix an epipe bug: sometimes when directory connections failed
25725 to connect, we would give them a chance to flush before closing
25727 - When we detached from a circuit because of resolvefailed, we
25728 would immediately try the same circuit twice more, and then
25729 give up on the resolve thinking we'd tried three different
25731 - Limit the number of intro circuits we'll attempt to build for a
25732 hidden service per 15-minute period.
25733 - Check recommended-software string *early*, before actually parsing
25734 the directory. Thus we can detect an obsolete version and exit,
25735 even if the new directory format doesn't parse.
25736 o Fixes for security bugs:
25737 - Remember which nodes are dirservers when you startup, and if a
25738 random OR enables his dirport, don't automatically assume he's
25739 a trusted dirserver.
25741 - Directory connections were asking the wrong poll socket to
25742 start writing, and not asking themselves to start writing.
25743 - When we detached from a circuit because we sent a begin but
25744 didn't get a connected, we would use it again the first time;
25745 but after that we would correctly switch to a different one.
25746 - Stop warning when the first onion decrypt attempt fails; they
25747 will sometimes legitimately fail now that we rotate keys.
25748 - Override unaligned-access-ok check when $host_cpu is ia64 or
25749 arm. Apparently they allow it but the kernel whines.
25750 - Dirservers try to reconnect periodically too, in case connections
25752 - Fix some memory leaks in directory servers.
25753 - Allow backslash in Win32 filenames.
25754 - Made Tor build complain-free on FreeBSD, hopefully without
25755 breaking other BSD builds. We'll see.
25756 - Check directory signatures based on name of signer, not on whom
25757 we got the directory from. This will let us cache directories more
25759 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
25762 - Doxygen markup on all functions and global variables.
25763 - Make directory functions update routerlist, not replace it. So
25764 now directory disagreements are not so critical a problem.
25765 - Remove the upper limit on number of descriptors in a dirserver's
25766 directory (not that we were anywhere close).
25767 - Allow multiple logfiles at different severity ranges.
25768 - Allow *BindAddress to specify ":port" rather than setting *Port
25769 separately. Allow multiple instances of each BindAddress config
25770 option, so you can bind to multiple interfaces if you want.
25771 - Allow multiple exit policy lines, which are processed in order.
25772 Now we don't need that huge line with all the commas in it.
25773 - Enable accept/reject policies on SOCKS connections, so you can bind
25774 to 0.0.0.0 but still control who can use your OP.
25775 - Updated the man page to reflect these features.
25778 Changes in version 0.0.6.2 - 2004-05-16
25779 o Our integrity-checking digest was checking only the most recent cell,
25780 not the previous cells like we'd thought.
25781 Thanks to Stefan Mark for finding the flaw!
25784 Changes in version 0.0.6.1 - 2004-05-06
25785 o Fix two bugs in our AES counter-mode implementation (this affected
25786 onion-level stream encryption, but not TLS-level). It turns
25787 out we were doing something much more akin to a 16-character
25788 polyalphabetic cipher. Oops.
25789 Thanks to Stefan Mark for finding the flaw!
25790 o Retire moria3 as a directory server, and add tor26 as a directory
25794 Changes in version 0.0.6 - 2004-05-02
25796 - Hidden services and rendezvous points are implemented. Go to
25797 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
25798 hidden services. (This only works via a socks4a proxy such as
25799 Privoxy, and currently it's quite slow.)
25800 - We now rotate link (tls context) keys and onion keys.
25801 - CREATE cells now include oaep padding, so you can tell
25802 if you decrypted them correctly.
25803 - Retry stream correctly when we fail to connect because of
25804 exit-policy-reject (should try another) or can't-resolve-address.
25805 - When we hup a dirserver and we've *removed* a server from the
25806 approved-routers list, now we remove that server from the
25807 in-memory directories too.
25808 - Add bandwidthburst to server descriptor.
25809 - Directories now say which dirserver signed them.
25810 - Use a tor_assert macro that logs failed assertions too.
25811 - Since we don't support truncateds much, don't bother sending them;
25812 just close the circ.
25813 - Fetch randomness from /dev/urandom better (not via fopen/fread)
25814 - Better debugging for tls errors
25815 - Set Content-Type on the directory and hidserv descriptor.
25816 - Remove IVs from cipher code, since AES-ctr has none.
25818 - Fix an assert trigger for exit nodes that's been plaguing us since
25819 the days of 0.0.2prexx (thanks weasel!)
25820 - Fix a bug where we were closing tls connections intermittently.
25821 It turns out openssl keeps its errors around -- so if an error
25822 happens, and you don't ask about it, and then another openssl
25823 operation happens and succeeds, and you ask if there was an error,
25824 it tells you about the first error.
25825 - Fix a bug that's been lurking since 27 may 03 (!)
25826 When passing back a destroy cell, we would use the wrong circ id.
25827 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
25828 - Some versions of openssl have an SSL_pending function that erroneously
25829 returns bytes when there is a non-application record pending.
25830 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
25831 o We were using an array of length zero in a few places.
25832 o Win32's gethostbyname can't resolve an IP to an IP.
25833 o Win32's close can't close a socket.
25834 o Handle windows socket errors correctly.
25836 - check for <sys/limits.h> so we build on FreeBSD again, and
25837 <machine/limits.h> for NetBSD.
25840 Changes in version 0.0.5 - 2004-03-30
25841 o Install torrc as torrc.sample -- we no longer clobber your
25843 o Fix mangled-state bug in directory fetching (was causing sigpipes).
25844 o Only build circuits after we've fetched the directory: clients were
25845 using only the directory servers before they'd fetched a directory.
25846 This also means longer startup time; so it goes.
25847 o Fix an assert trigger where an OP would fail to handshake, and we'd
25848 expect it to have a nickname.
25849 o Work around a tsocks bug: do a socks reject when AP connection dies
25850 early, else tsocks goes into an infinite loop.
25851 o Hold socks connection open until reply is flushed (if possible)
25852 o Make exit nodes resolve IPs to IPs immediately, rather than asking
25853 the dns farm to do it.
25854 o Fix c99 aliasing warnings in rephist.c
25855 o Don't include server descriptors that are older than 24 hours in the
25857 o Give socks 'reject' replies their whole 15s to attempt to flush,
25858 rather than seeing the 60s timeout and assuming the flush had failed.
25859 o Clean automake droppings from the cvs repository
25860 o Add in a 'notice' log level for things the operator should hear
25861 but that aren't warnings
25864 Changes in version 0.0.4 - 2004-03-26
25865 o When connecting to a dirserver or OR and the network is down,
25869 Changes in version 0.0.3 - 2004-03-26
25870 o Warn and fail if server chose a nickname with illegal characters
25871 o Port to Solaris and Sparc:
25872 - include missing header fcntl.h
25873 - have autoconf find -lsocket -lnsl automatically
25874 - deal with hardware word alignment
25875 - make uname() work (solaris has a different return convention)
25876 - switch from using signal() to sigaction()
25877 o Preliminary work on reputation system:
25878 - Keep statistics on success/fail of connect attempts; they're published
25879 by kill -USR1 currently.
25880 - Add a RunTesting option to try to learn link state by creating test
25881 circuits, even when SocksPort is off.
25882 - Remove unused open circuits when there are too many.
25885 Changes in version 0.0.2 - 2004-03-19
25886 - Include strlcpy and strlcat for safer string ops
25887 - define INADDR_NONE so we compile (but still not run) on solaris
25890 Changes in version 0.0.2pre27 - 2004-03-14
25892 - Allow internal tor networks (we were rejecting internal IPs,
25893 now we allow them if they're set explicitly).
25894 - And fix a few endian issues.
25897 Changes in version 0.0.2pre26 - 2004-03-14
25899 - If a stream times out after 15s without a connected cell, don't
25900 try that circuit again: try a new one.
25901 - Retry streams at most 4 times. Then give up.
25902 - When a dirserver gets a descriptor from an unknown router, it
25903 logs its fingerprint (so the dirserver operator can choose to
25904 accept it even without mail from the server operator).
25905 - Inform unapproved servers when we reject their descriptors.
25906 - Make tor build on Windows again. It works as a client, who knows
25908 - Clearer instructions in the torrc for how to set up a server.
25909 - Be more efficient about reading fd's when our global token bucket
25910 (used for rate limiting) becomes empty.
25912 - Stop asserting that computers always go forward in time. It's
25914 - When we sent a cell (e.g. destroy) and then marked an OR connection
25915 expired, we might close it before finishing a flush if the other
25916 side isn't reading right then.
25917 - Don't allow dirservers to start if they haven't defined
25918 RecommendedVersions
25919 - We were caching transient dns failures. Oops.
25920 - Prevent servers from publishing an internal IP as their address.
25921 - Address a strcat vulnerability in circuit.c
25924 Changes in version 0.0.2pre25 - 2004-03-04
25926 - Put the OR's IP in its router descriptor, not its fqdn. That way
25927 we'll stop being stalled by gethostbyname for nodes with flaky dns,
25930 - If the user typed in an address that didn't resolve, the server
25934 Changes in version 0.0.2pre24 - 2004-03-03
25936 - Fix an assertion failure in dns.c, where we were trying to dequeue
25937 a pending dns resolve even if it wasn't pending
25938 - Fix a spurious socks5 warning about still trying to write after the
25939 connection is finished.
25940 - Hold certain marked_for_close connections open until they're finished
25941 flushing, rather than losing bytes by closing them too early.
25942 - Correctly report the reason for ending a stream
25943 - Remove some duplicate calls to connection_mark_for_close
25944 - Put switch_id and start_daemon earlier in the boot sequence, so it
25945 will actually try to chdir() to options.DataDirectory
25946 - Make 'make test' exit(1) if a test fails; fix some unit tests
25947 - Make tor fail when you use a config option it doesn't know about,
25948 rather than warn and continue.
25949 - Make --version work
25950 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
25953 Changes in version 0.0.2pre23 - 2004-02-29
25955 - Print a statement when the first circ is finished, so the user
25956 knows it's working.
25957 - If a relay cell is unrecognized at the end of the circuit,
25958 send back a destroy. (So attacks to mutate cells are more
25960 - New config option 'excludenodes' to avoid certain nodes for circuits.
25961 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
25962 so you can collect coredumps there.
25964 - Fix a bug in tls flushing where sometimes data got wedged and
25965 didn't flush until more data got sent. Hopefully this bug was
25966 a big factor in the random delays we were seeing.
25967 - Make 'connected' cells include the resolved IP, so the client
25968 dns cache actually gets populated.
25969 - Disallow changing from ORPort=0 to ORPort>0 on hup.
25970 - When we time-out on a stream and detach from the circuit, send an
25971 end cell down it first.
25972 - Only warn about an unknown router (in exitnodes, entrynodes,
25973 excludenodes) after we've fetched a directory.
25976 Changes in version 0.0.2pre22 - 2004-02-26
25978 - Servers publish less revealing uname information in descriptors.
25979 - More memory tracking and assertions, to crash more usefully when
25981 - If the default torrc isn't there, just use some default defaults.
25982 Plus provide an internal dirservers file if they don't have one.
25983 - When the user tries to use Tor as an http proxy, give them an http
25984 501 failure explaining that we're a socks proxy.
25985 - Dump a new router.desc on hup, to help confused people who change
25986 their exit policies and then wonder why router.desc doesn't reflect
25988 - Clean up the generic tor.sh init script that we ship with.
25990 - If the exit stream is pending on the resolve, and a destroy arrives,
25991 then the stream wasn't getting removed from the pending list. I
25992 think this was the one causing recent server crashes.
25993 - Use a more robust poll on OSX 10.3, since their poll is flaky.
25994 - When it couldn't resolve any dirservers, it was useless from then on.
25995 Now it reloads the RouterFile (or default dirservers) if it has no
25997 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
25998 many users don't even *have* a /usr/local/sbin/.
26001 Changes in version 0.0.2pre21 - 2004-02-18
26003 - There's a ChangeLog file that actually reflects the changelog.
26004 - There's a 'torify' wrapper script, with an accompanying
26005 tor-tsocks.conf, that simplifies the process of using tsocks for
26006 tor. It even has a man page.
26007 - The tor binary gets installed to sbin rather than bin now.
26008 - Retry streams where the connected cell hasn't arrived in 15 seconds
26009 - Clean up exit policy handling -- get the default out of the torrc,
26010 so we can update it without forcing each server operator to fix
26012 - Allow imaps and pop3s in default exit policy
26014 - Prevent picking middleman nodes as the last node in the circuit
26017 Changes in version 0.0.2pre20 - 2004-01-30
26019 - We now have a deb package, and it's in debian unstable. Go to
26020 it, apt-getters. :)
26021 - I've split the TotalBandwidth option into BandwidthRate (how many
26022 bytes per second you want to allow, long-term) and
26023 BandwidthBurst (how many bytes you will allow at once before the cap
26024 kicks in). This better token bucket approach lets you, say, set
26025 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
26026 performance while not exceeding your monthly bandwidth quota.
26027 - Push out a tls record's worth of data once you've got it, rather
26028 than waiting until you've read everything waiting to be read. This
26029 may improve performance by pipelining better. We'll see.
26030 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
26031 from failed circuits (if they haven't been connected yet) and attach
26033 - Expire old streams that haven't managed to connect. Some day we'll
26034 have them reattach to new circuits instead.
26037 - Fix several memory leaks that were causing servers to become bloated
26039 - Fix a few very rare assert triggers. A few more remain.
26040 - Setuid to User _before_ complaining about running as root.
26043 Changes in version 0.0.2pre19 - 2004-01-07
26045 - Fix deadlock condition in dns farm. We were telling a child to die by
26046 closing the parent's file descriptor to him. But newer children were
26047 inheriting the open file descriptor from the parent, and since they
26048 weren't closing it, the socket never closed, so the child never read
26049 eof, so he never knew to exit. Similarly, dns workers were holding
26050 open other sockets, leading to all sorts of chaos.
26051 - New cleaner daemon() code for forking and backgrounding.
26052 - If you log to a file, it now prints an entry at the top of the
26053 logfile so you know it's working.
26054 - The onionskin challenge length was 30 bytes longer than necessary.
26055 - Started to patch up the spec so it's not quite so out of date.
26058 Changes in version 0.0.2pre18 - 2004-01-02
26060 - Fix endian issues with the 'integrity' field in the relay header.
26061 - Fix a potential bug where connections in state
26062 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
26065 Changes in version 0.0.2pre17 - 2003-12-30
26067 - Made --debuglogfile (or any second log file, actually) work.
26068 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
26069 adversary could force us into an infinite loop.
26072 - Each onionskin handshake now includes a hash of the computed key,
26073 to prove the server's identity and help perfect forward secrecy.
26074 - Changed cell size from 256 to 512 bytes (working toward compatibility
26076 - Changed cell length to 2 bytes, and moved it to the relay header.
26077 - Implemented end-to-end integrity checking for the payloads of
26079 - Separated streamid from 'recognized' (otherwise circuits will get
26080 messed up when we try to have streams exit from the middle). We
26081 use the integrity-checking to confirm that a cell is addressed to
26083 - Randomize the initial circid and streamid values, so an adversary who
26084 breaks into a node can't learn how many circuits or streams have
26088 Changes in version 0.0.2pre16 - 2003-12-14
26090 - Fixed a bug that made HUP trigger an assert
26091 - Fixed a bug where a circuit that immediately failed wasn't being
26092 counted as a failed circuit in counting retries.
26095 - Now we close the circuit when we get a truncated cell: otherwise we're
26096 open to an anonymity attack where a bad node in the path truncates
26097 the circuit and then we open streams at him.
26098 - Add port ranges to exit policies
26099 - Add a conservative default exit policy
26100 - Warn if you're running tor as root
26101 - on HUP, retry OR connections and close/rebind listeners
26102 - options.EntryNodes: try these nodes first when picking the first node
26103 - options.ExitNodes: if your best choices happen to include any of
26104 your preferred exit nodes, you choose among just those preferred
26106 - options.ExcludedNodes: nodes that are never picked in path building
26109 Changes in version 0.0.2pre15 - 2003-12-03
26110 o Robustness and bugfixes:
26111 - Sometimes clients would cache incorrect DNS resolves, which would
26112 really screw things up.
26113 - An OP that goes offline would slowly leak all its sockets and stop
26115 - A wide variety of bugfixes in exit node selection, exit policy
26116 handling, and processing pending streams when a new circuit is
26118 - Pick nodes for a path only from those the directory says are up
26119 - Choose randomly from all running dirservers, not always the first one
26120 - Increase allowed http header size for directory fetch.
26121 - Stop writing to stderr (if we're daemonized it will be closed).
26122 - Enable -g always, so cores will be more useful to me.
26123 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
26126 - Wrote a man page. It lists commonly used options.
26129 - Change default loglevel to warn.
26130 - Make PidFile default to null rather than littering in your CWD.
26131 - OnionRouter config option is now obsolete. Instead it just checks
26133 - Moved to a single unified torrc file for both clients and servers.
26136 Changes in version 0.0.2pre14 - 2003-11-29
26137 o Robustness and bugfixes:
26138 - Force the admin to make the DataDirectory himself
26139 - to get ownership/permissions right
26140 - so clients no longer make a DataDirectory and then never use it
26141 - fix bug where a client who was offline for 45 minutes would never
26142 pull down a directory again
26143 - fix (or at least hide really well) the dns assert bug that was
26144 causing server crashes
26145 - warnings and improved robustness wrt clockskew for certs
26146 - use the native daemon(3) to daemonize, when available
26147 - exit if bind() fails
26148 - exit if neither socksport nor orport is defined
26149 - include our own tor_timegm (Win32 doesn't have its own)
26150 - bugfix for win32 with lots of connections
26151 - fix minor bias in PRNG
26152 - make dirserver more robust to corrupt cached directory
26155 - Wrote the design document (woo)
26157 o Circuit building and exit policies:
26158 - Circuits no longer try to use nodes that the directory has told them
26160 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
26161 bitcounts (18.0.0.0/8).
26162 - Make AP connections standby for a circuit if no suitable circuit
26163 exists, rather than failing
26164 - Circuits choose exit node based on addr/port, exit policies, and
26165 which AP connections are standing by
26166 - Bump min pathlen from 2 to 3
26167 - Relay end cells have a payload to describe why the stream ended.
26168 - If the stream failed because of exit policy, try again with a new
26170 - Clients have a dns cache to remember resolved addresses.
26171 - Notice more quickly when we have no working circuits
26174 - APPort is now called SocksPort
26175 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
26177 - RecommendedVersions is now a config variable rather than
26178 hardcoded (for dirservers)
26179 - Reloads config on HUP
26180 - Usage info on -h or --help
26181 - If you set User and Group config vars, it'll setu/gid to them.
26183 Changes in version 0.0.2pre13 - 2003-10-19
26184 o General stability:
26185 - SSL_write no longer fails when it returns WANTWRITE and the number
26186 of bytes in the buf has changed by the next SSL_write call.
26187 - Fix segfault fetching directory when network is down
26188 - Fix a variety of minor memory leaks
26189 - Dirservers reload the fingerprints file on HUP, so I don't have
26190 to take down the network when I approve a new router
26191 - Default server config file has explicit Address line to specify fqdn
26194 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
26195 - Make listener connections not ever alloc bufs
26197 o Autoconf improvements:
26198 - don't clobber an external CFLAGS in ./configure
26199 - Make install now works
26200 - create var/lib/tor on make install
26201 - autocreate a tor.sh initscript to help distribs
26202 - autocreate the torrc and sample-server-torrc with correct paths
26204 o Log files and Daemonizing now work:
26205 - If --DebugLogFile is specified, log to it at -l debug
26206 - If --LogFile is specified, use it instead of commandline
26207 - If --RunAsDaemon is set, tor forks and backgrounds on startup